Bank of Ayudhya
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 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 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 refund result | ❌ |
Payment flow | Redirect | Time to return payment result | Real-time |
Minimum payment amount | 1 THB | Chargeback/Dispute | ❌ |
Maximum payment amount | 2 million THB | Default timeout | 14 minutes |
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 refund result | ❌ |
Payment flow | Redirect | Time to return payment result | Real-time |
Minimum payment amount | 1 THB | Chargeback/Dispute | ❌ |
Maximum payment amount | 2 million THB (ATM: 0.5 million THB) | 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.
- The buyer selects BAY to pay.
- The buyer completes the payment on the BAY page.
- The buyer is redirected to the merchant result page.
Supported online payment integrations
Antom offers a range of integration options tailored to each payment method. Each payment method may support different online payment integration options, allowing for flexibility based on your business requirements. The table below provides detailed information about the specific integrations available for each payment method:
Supported online payments | Supported integrations | Payment method manual |
Checkout Payment | ✔️ API-onlyNot supported on PC ❌ Hosted Checkout Page ❌ Embedded Checkout Page ❌ Mobile Element ❌ Web Element ❌ Pay-by-Link | |
Auto Debit | ❌ | None |
Subscription Payment | ❌ | None |
EasySafePay | ❌ | None |
Scan to Link | ❌ | None |
Integration considerations
The following section outlines integration considerations for various payment types, detailing customized integration solutions and payment method features.
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 normalUrl is opened to enter the name and password for payment.
- WAP: The returned normalUrl is 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.
- When the buyer selects the online banking method for payment, the bank charges the buyer a handling fee for each transaction. Regarding the specific amount of the handling fee, consult the bank for detailed information.
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.