Redirect Payment API is supporting these following transaction service functions:
Fig 3-1. Payment page screen on Redirect Payment API – desktop interface.
Fig 3-2. Payment page screen on Redirect Payment API – mobile interface.
Redirect API (RAPI) is Red Dot Payment (RDP) web service that’s handling payment service with the payment page can be either managed by third party processor or payment gateway, such as Red Dot Payment (Hosted Order Page – HOP mode), or managed and handled by the merchant itself (Silent Order Page – SOP mode).
The following are those benefits for using Redirect Payment API HOP mode:
While, below are those benefits or advantages for using Redirect Payment API SOP mode:
Some requirements for Redirect Payment API (RAPI):
RDP heavily discourages iFrame to be used for Redirect Payment API.
You will bear the risks for any issues and problems encountered on iFrame.
The process flow for ‘Redirect Payment API’ is differentiated or distinguished into 2 flows, depends on who host or own the payment page. And those 2 process flows are mentioned or elaborated below.
The process flow for Redirect Payment API Hosted Order Page (HOP) consists of these several
By the end of a successful first request, merchant shall receive a payment page URL.
Fig 3-3. Merchant send request for payment page URL construction in first phase.
Fig 3-4. Merchant’s customer is redirected to RDP hosted payment page URL
Fig 3-5. RDP process and send the complete payment Information to respective bank or acquirer.
Fig 3-6. RDP payment gateway sends ‘Push Notification’ to merchant’s notification URL.
Fig 3-7. Merchant do transaction query to RDP payment gateway.
The process flow for Redirect Payment API Silent Order Page (SOP) consists of these several steps below:
Fig 3-8. Customers enter their credit card details in merchant’s payment page.
By the end of a successful first request, merchant shall receive a payment URL.
Fig 3-9. Merchant send request for payment URL together with customer’s card details.