Bank of Ayudhya (BAY) was founded in 1945 by Chinese businessman Chen Gongkun. BAY is the fifth largest commercial bank in Thailand with 601 domestic branches.
BAY has more than 5.4 million Thai users. Currently, the bank supports two different ways for users to pay: online banking and bank transfer via offline ATMs.
Properties
The properties of the BAY payment method are shown in the following table based on different payment types:
Payment property
Product property
Payment type
Online banking
Acquirer
AlipaySG, AlipayUS
Refund
❌
Merchant entity location
SG, AU, HK, US
Partial refund
❌
Buyer country/region
Thailand
Refund period
❌
Processing currency
THB
Time to return the Refund result
❌
Payment flow
Redirect
Time to return the payment result
Real-time
Minimum payment amount
1 THB
Chargeback/Dispute
❌
Maximum payment amount
2M THB
Payment property
Product property
Payment type
Bank transfer
Acquirer
AlipaySG, AlipayUS
Refund
❌
Merchant entity location
SG, AU, HK, US
Partial refund
❌
Buyer country/region
Thailand
Refund period
❌
Processing currency
THB
Time to return the Refund result
❌
Payment flow
Redirect
Time to return the payment result
Real-time
Minimum payment amount
1 THB
Chargeback/Dispute
❌
Maximum payment amount
2M THB (ATM 0.5M)
Default timeout
48 hours
Customize the timeout
✔️
User experience
Note: The following payment flows on different terminals are reference only, and represent this payment method's flow on different terminal types. For supported merchants' terminal types, consult Antom Technical Support.
The following graphics show the user experience for the App terminal in different scenarios.
Online banking
Bank transfer
The user selects BAY to pay.
The user completes the payment on the BAY page.
The user is redirected to the merchant result page.
The user selects BAY to pay.
The user is redirected to the payment code page.
The user opens the bank app manually.
The user selects the order bill to pay on the bank page.
The user searches the bill code on the bank page.
The user enters the bank account and payment code.
The user confirms the order information.
The bank page displays the payment result.
The user manually switches back to the merchant result page and obtains the payment result.
Integration considerations
The following section outlines integration considerations for various payment types, detailing customized integration solutions and payment method features.
Online banking
Bank transfer
About normalUrl
For Web, WAP, and App terminals, normalUrl is returned in the response of the pay API.Different terminal types have specific integration features when returning normalUrl:
Web: The returned normalUrlis opened to enter the username and password for payment.
WAP: The returned normalUrlis opened to enter the Email/Phone number and PIN for payment. The buyer is redirected to the bank payment page to log in and complete the payment.
App: The returned normalUrl does not trigger the payment method app.It is recommended to render the bank middle page URL directly within the merchant app and set the merchant result page to the browser link instead of the app's scheme. If you use the external redirection to open the bank middle page URL, set the merchant result page to the merchant app's scheme or redirect the browser link to the scheme or deeplink.
After payments
This payment method does not support refunds. It is recommended to communicate directly with the buyer offline.
Default timeout
If the buyer does not complete the payment, Antom sends you an asynchronous notification of the payment result at the 14th minute. The timeout period for the merchant to wait for the asynchronous notification or inquire about the result must be greater than 14 minutes.
About normalUrl
When accepting payments from BAY, you can choose whether to use normalUrl:
If choosing not to use normalUrl, you can directly render the codeValue in the API response on the merchant page to display the QR code or payment code, reducing page redirections and improving the payment experience.
If choosing to use normalUrl, redirect your buyer to the address specified by normalUrl and proceed the payment process as indicated in User experience.
For Web, WAP, and App terminals, normalUrl is returned in the response of the pay API. The buyer is redirected to the address specified by normalUrl and uses the payment code displayed on the page to proceed with the payment within the mobile banking app or on the offline ATM device. After the payment is completed, the middle page automatically redirects to the merchant result page.
Different terminal types have specific integration features when returning normalUrl.
WAP: The returned normalUrl is the payment code and payment operation display page. The buyer copies the payment code and proceeds to the bank app or the ATM based on the payment operation or the screenshot to complete the payment.
App: The returned normalUrl does not trigger the payment method app. It is recommended that you render the URL page directly within the merchant app and provide payment operation steps to guide buyers to complete the payment.
After payments
After the buyer completes the payment in the bank app, the banking app will not automatically redirect to the merchant's results page. The buyer needs to manually navigate to the transaction initiation app (the merchant app or browser).
This payment method does not support refunds. It is recommended to communicate directly with the buyer offline.
Obtain the payment result from the payment result notification (notifyPayment) or by making inquiries (inquiryPayment). Handle the redirection and display of the payment result page to avoid duplicate payments.
Default timeout
The QR code returned by Antom will not be refreshed automatically. When displaying the QR code, add the expireTime parameter in the API response to display the timeout time. When displaying the payment code, enable the copy function for the payment code and allow the buyer to conveniently paste the payment code into the payment method app.
Response sample
The following is a code example in the payment response:
