Callback and Redirect Url
Redirect URL (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.
Callback URL (callback_url)
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.
Parameter from redirect and callback URL
This parameters will be sent the URL by using POST method.
gatweway_type
The payment method used to complete a transaction, such as FPX or DuitNow.
FPX
payment
Transaction details, including amount, status, gateway used, environment, and reference identifiers for tracking
currency
Currency used for the payment.
order_number
Custom order number that is generated by merchant
seller_order_number
Seller order no is generated by SecurePay Platform
exchange_number
Exchange order no is generated by SecurePay Platform
buyer_name
Buyer name
fpx_debit _auth_code
00 success, 99 - pending approval, other codes - unsuccessful .. If perform B2B1, there will be code 99, after approval the server will send callback with code 00.
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).
Guide to generate checksum
Compulsory to use function that automatically sort the key and later replace with the value. Params will keep updating time to time.
Example
Last updated