Opuspay and gateway mapping is illustrated in this version.
Merchant report generation is described as an enhancement.
Important Notes
The system must be designed with multi-lingual and multi-tenant capabilities. Should also optionally allow for multiple connected databases at a tenant level.
All master creation/delete/edit must be added to an auditable log file - user, date, time, ip address, before, after, record id
All transactions must be have auditable data added - user, date, time, ip address, before, after, record id
Must handle high concurrent volume
The entire database must be encrypted
All passwords must be salted and hashed
Field validation error messages at field level will populate on exit from the field
Form validation rules will display error messages on selection of submission button
Security should be applied to avoid scripting in entry fields e.g. JS, HTML - anything that can inject a security risk
Copy database of countries, states, towns, postcodes, etc. from byondcloud to opuspay database
Missing
Inbound / Outbound API specifications (calls from byondpro and byondcloud - and other systems)
Test function for the gateway API configurations
Payment functions for byondpro payment plans
byondcloud - currently no functions exist in bcloud requiring payments
The contents of OP Version 2.1_Merchant Statement V 1
