EzyPayment - as a Service (EPaaS)

High level User/API flow

Integration with EzyPayment (Payment as a Service) has two main parts. 1. The user redirections for the payment triggering. 2. Backend communications for exchange payment transaction data.

1. User accessing the external party web application and came to the page where payment is required.
2. User proceeds to pay with EzyPayment and redirection happens for EzyPayment web portal. EzyPayment will show the invoice/bill amount and the reference number and description if necessary. EzyPayment will give user two options.1. Pay by a card. 2. Pay via Paynow (coming soon)
3. Once user chooses to pay by card, EzyPayment shows a UI to enter card detials. *Note that EzyPayment is not storing or capturing the card details. Instead, we capture only a token. Therefore, the data privacy is protected.
4. Once user submit the card details and paid, the payment will be validated and if success then proceed to next redirections.
5. User will be redirected to an intermediate page for a fraction of second to capture details and to make sure data are secure.
6. User will be redirected to the External Party web application for a pre-configured URL with the payment status.
7. Parallelly, EzyPayment will store the transaction details to transaction database for later reporting and billing purpose.
8. Stored data will be optionally synced to External Party backend services for further actions from External party.

Following are the APIs to be integrated for steps. (External party only have to integrate few points of the flow)

API_R01 → For step (2) → Redirection to EzyPayment - Initiate Payment Redirection

API_R02 → For step (6) → Redirect back from EzyPayment - Payment Response Redirection

API_B01 → For step (8) → Payment status update from EzyPayment - Payment Response Callback