Callback and Redirect URL
Merchant/partner can set redirect_url during sending payment POST parameters. Redirect URL is browser to browser communication. After the bank transaction from the browser. The user will be redirected to this URL, merchant can set their own page. Information will be posted (POST method) to the URL. By default user will be redirected to SecurePay status page if the redirect URL is nil.
Merchant/partner can set callback_url during sending payment POST parameters. Callback URL is server to server communication. SecurePay server sends the transaction status to the merchant callback server (based on callback URL). It's very important, if error occur on the redirect URL.
This parameters will be sent to the URL by using POST method.
Parameter | Description |
source | FPX or Credit Card |
payment_status | True or False |
currency | RM or other currency |
transaction_amount | Transaction amount |
transaction_amount_received | Amount received, if payment_status false set to 0.00 |
order_number | Order number send previously by merchant partner |
merchant_reference_number | This number is generated by SecurePay Platform |
exchange_number | This number is generated by SecurePay Platform |
buyer_name | Buyer name |
buyer_phone | Buyer phone |
buyer_email | Buyer email |
payment_id | For reference |
client_ip | Client IP address |
status_url | SecurePay status URL |
retry_url | Any failed payment, can make retry using this links |
receipt_url | SecurePay PDF receipt URL |
checksum | Checksum generated by SecurePay for verification by merchant/partner |
Checksum is use to verify message that are received by SecurePay Platform for redirect and callback. The verification will be done on the merchant/partner side. (the string also need to include uid).
