Payment Flow Codes
2C2P allows payment acceptance through different platforms and channels, as well as through various implementations such as embedded iframes, app deeplinks, or webviews. To ensure smooth and seamless payments across various implementations, merchants are given payment flow codes to indicate particular results or actions to take note of during the payment process.
Refer to the list below for each code's definition.
List of payment flow code
Response Code | Platform | Payment Flow | Action Required |
---|---|---|---|
1000 | Web / Mobile | Load redirect URL with IFrame / Webview. | Client should close the iframe when the URL is loading RESULT URL and read the BODY message. |
1001 | Web / Mobile | Full redirection to web page | Do full redirection to 3rd party web page. |
1002 | Web / Mobile |
| Mobile :
WEB:
Refer to Transaction Status Inquiry API |
1003 | Web / Mobile | Get and display the payslip information and waiting customer to pay it |
|
1004 | Mobile | Redirect to external app with app scheme, and back with app call back. |
|
1005 | Web / Mobile |
|
Refer to Transaction Status Inquiry API |
2000 | Web / Mobile | Transaction completed and merchant require to display payment result. | For merchants who implement backend response :
For merchants who do not implement backend response :
|
Other CodeRefer to API Response Code | Web / Mobile | Transaction failed or rejected, perform payment inquiry to get payment status and full response. | Get payment result, and display result to customer. End of payment flow. |
Updated almost 2 years ago