Introduction
Welcome to our Payment Gateway System
Our powerful web-based online payment services platform, a trusted solution utilized by numerous renowned companies and organizations in the region. Our system offers a secure, multi-channel, multi-lingual, and multi-currency payment experience.
Integration Methods:
Choose the integration method that best suits your needs:
Web Integration | Mobile Integration |
Client Post through Browser (e.g. Shopping Cart) This method is favoured by merchants for its simplicity and speed. It enables swift website integration, ensuring a seamless user experience with a streamlined transaction flow. | This section explains the integration of PaySDK Android SDK in merchant android mobile application. |
Tailored for Online Shopping Carts, this method uses HTML and JavaScript for broad compatibility, ensuring a seamless experience | This section explains integration of PaySDK iOS SDK in merchant iOS mobile application. |
Server Side Direct Connection (e.g. IVR System, Mobile App) Merchants request payment authorization via our gateway, pending bank approval. They integrate their IVR or app, and create a custom payment page | Merchants can seek direct payment authorization from the bank via our gateway, pending acquiring bank approval. They'll set up a custom payment page to collect information like credit card details, which will be sent to a specific URL provided by the acquiring bank. Customers won't encounter a bank payment page in this process. |
Purpose of this Document:
This technical specification document prescribes the constituent parts of specification for integration of an e-commerce web site with PayDollar/SiamPay/PesoPay e-commerce service, the on-line payment service by AsiaPay (HK) Limited, by subscribed merchants of the service. This document has been created to ensure that all technical specifications contain sufficient information to enable a merchant to design and modify the codes of an existing on-line shopping architecture or software to cater for the payment –enabling service. It also provides a checklist to enable the reviewers of specifications to conduct tests on the functionalities of the integration.
Enhanced Security with 3DS 2.0:
There is an extra parameter section under each connection method. That section is especially designed for 3DS 2.0 (Three Domain Secure 2.0). 3DS authentication is an additional security layer for card-not-present transactions. With 3DS 2.0, it is aimed to achieve a better, stronger fraud-detection intelligence.
Merchant API Functions:
In a later section, we'll provide an in-depth description of the various API functions available to subscribed merchants, ensuring a seamless integration process.
Thank you for choosing our payment gateway system. Let's get started.
Web Integration
Following are the three methods of Web Integration
Client Post Through Browser
Introduction
This method stands as the preferred choice among merchants for its simplicity and speed. It offers a swift integration process, allowing merchants to launch their website seamlessly. The transaction flow is ready-made, streamlining the payment process for an optimal user experience.
This method is characterized by its:
- Simplicity: With an intuitive integration process, merchants can swiftly incorporate our payment gateway into their website.
- Speed: The connection is established quickly, ensuring a seamless checkout experience for customers.
- Ready-to-Use Flow: The payment transaction flow is pre-configured, saving merchants time and effort.
Additionally, this method supports small-scale integrations, enabling merchants to set up their website promptly.
Scope and Compatibility (Requirement)
Sample Code
Kick Off
After the integration has been completed, it is ready to launch your e-commerce web to serve your customers.
Please copy the following TESTING URL for client post method:
Payment Gateway | Testing URL |
PayDollar | https://test.paydollar.com/b2cDemo/eng/payment/payForm.jsp |
SiamPay | https://test.siampay.com/b2cDemo/eng/payment/payForm.jsp |
PesoPay | https://test.pesopay.com/b2cDemo/eng/payment/payForm.jsp |
Base URL
Payment Gateway | SandBox |
PayDollar | https://test.paydollar.com/b2cDemo/eng/payment |
SiamPay | https://test.siampay.com/b2cDemo/eng/payment |
PesoPay | https://test.pesopay.com/b2cDemo/eng/payment |
The following is an example of integration of shopping cart routine with the payment routine of our payment gateway in HTML. It is noteworthy that the portion in bold typeface as follows is mandatory for successful integration. In the following sample form, hidden fields are used to hold the values. Please change the action URL to integrate with your preferred gateway
<form name="payFormCcard" method="post" action="
https://test.paydollar.com/b2cDemo/eng/payment/payForm.jsp">
<input type="hidden" name="merchantId" value="1">
<input type="hidden" name="amount" value="3000" >
<input type="hidden" name="orderRef" value="000000000014">
<input type="hidden" name="currCode" value="344" >
<input type="hidden" name="mpsMode" value="NIL" >
<input type="hidden" name="successUrl"
value="http://www.yourdomain.com/Success.html">
<input type="hidden" name="failUrl" value="http://www.yourdomain.com/Fail.html">
<input type="hidden" name="cancelUrl"
value="http://www.yourdomain.com/Cancel.html">
<input type="hidden" name="payType" value="N">
<input type="hidden" name="lang" value="E">
<input type="hidden" name="payMethod" value="CC">
<input type="hidden" name="secureHash"
value="44f3760c201d3688440f62497736bfa2aadd1bc0">
<input type="submit" name="submit">
</form> Integration Parameters
The following are the parameters for integration. Our payment gateway system is case sensitive. Make sure the typeface is correct. When a transaction is finished, the system will return customer a payment message. Merchant can create static HTML pages to display the message. If merchant’s web site supports datafeed, the system can return payment message as shown in the following table.
3DS 2.0
The following are the parameters especially for 3DS 2.0. Merchant shall fulfill the parameters requirement to start using 3DS 2.0. The parameters are case sensitive and should be in UTF-8 encoding.
Basic Parameters
Parameters | Data Type | Mandatory | Descriptions |
threeDSTransType | Text (2) | No | Transaction type. Select the most suitable one. “01” – Goods/ Service Purchase *Default value if threeDSTransType not provided. “03” – Check Acceptance “10” – Account Funding “11” – Quasi-Cash Transaction “28” – Prepaid Activation and Load |
threeDSCustomerEmail | Text (254) | Yes | The customer’s email address *Strongly suggest to provide if available. Shall meet requirements of Section 3.4 of IETF RFC 5322 |
threeDSMobilePhoneCountryCode | Text (3) | Yes | Customer’s mobile phone number country code. Provide if available. If “threeDSMobilePhoneCountryCode” is provided, “threeDSMobilePhoneNumber” should also be provided. e.g. “852” – Hong Kong |
threeDSMobilePhoneNumber | Text (15) | Yes | Customer’s mobile phone number. Provide if available. If “threeDSMobilePhoneNumber” is provided, “threeDSMobilePhoneCountryCode” should also be provided. |
threeDSHomePhoneCountryCode | Text (3) | No | Customer’s home phone number country code. Provide if available. If “threeDSHomePhoneCountryCode” is provided, “threeDSHomePhoneNumber” should also be provided. e.g. “852” – Hong Kong |
threeDSHomePhoneNumber | Text (15) | No | Customer’s home phone number. Provide if available. If “threeDSHomePhoneNumber” is provided, “threeDSHomePhoneCountryCode” should also be provided. |
threeDSWorkPhoneCountryCode | Text (3) | No | Customer’s work phone number country code. Provide if available. If “threeDSWorkPhoneCountryCode” is provided, “threeDSWorkPhoneNumber” should also be provided. e.g. “852” – Hong Kong |
threeDSWorkPhoneNumber | Text (15) | No | Customer’s work phone number. Provide if available. If “threeDSWorkPhoneNumber” is provided, “threeDSWorkPhoneCountryCode” should also be provided. |
threeDSIsFirstTimeItemOrder | Text (1) | No | Flag to show if the customer is re-ordering the item / product. i.e. purchasing the same item / product Provide only if the payment related to purchase item / product. “T” – It is the first time the customer purchases this item / product. “F” – It is the NOT the first time the customer purchases the item / product, it is re-ordering. |
threeDSChallengePreference | Text(2) | No | Indicates whether a challenge is requested for this transaction. “01” – No preference *Default value if threeDSChallengePreference not provided. “02” – No challenge requested * “03” – Challenge requested (Merchant preference) “04” – Challenge requested (Mandate) “05” – No challenge requested (transactional risk analysis is already performed) * “06” – No challenge requested (Data share only)* “07” – No challenge requested (strong consumer authentication is already performed) * “08” – No challenge requested (utilise whitelist exemption if no challenge required) * “09” – Challenge requested (whitelist prompt requested if challenge required) ** If “No challenge requested” options are selected, the chargeback liability shift to merchant. |
Recurring / Installment
Provide only if it is a recurring / installment payment
Parameters | Data Type | Mandatory | Descriptions |
threeDSRecurringFrequency | Text (4) | Yes (Only for recurring / installment payment) | Minimum number of days between payment. e.g. “30” – 30 days between payments. |
threeDSRecurringExpiry | Text (8) | Yes (Only for recurring / installment payment) | Date after which no further payment shall be performed. Format: YYYYMMDD e.g. “20190401” |
Billing Address
Provide only if billing address is available
Parameters | Data Type | Mandatory | Descriptions |
threeDSBillingCountryCode | Text (3) | No | Payment cardholder billing country. Shall be the ISO 3166-1 numeric three-digit country code. e.g. “344” – Hong Kong, “840” – US Note: Required if "threeDSBillingState" is present |
threeDSBillingState | Text (3) | No | Payment cardholder billing state Should be the country subdivision code defined in ISO 3166-2. Provide if available, as some countries do not have subdivision code. e.g. “PE” – Prince Edward Island of California |
threeDSBillingCity | Text (50) | No | Payment cardholder billing city e.g. “Hong Kong” |
threeDSBillingLine1 | Text (50) | No | Payment cardholder billing address line 1 |
threeDSBillingLine2 | Text (50) | No | Payment cardholder billing address line 2 Provide if available |
threeDSBillingLine3 | Text (50) | No | Payment cardholder billing address line 3 Provide if available |
threeDSBillingPostalCode | Text (16) | No | Payment cardholder billing postal code Provide if available |
Shipping / Delivery
Provide only if the payment requires shipping / delivery
Parameters | Data Type | Mandatory | Descriptions |
threeDSDeliveryTime | Text (2) | Yes | The delivering time for this purchase. “01” – Electronic Delivery “02” – Same day shipping “03” – Overnight shipping “04” – Two-day or more shipping |
threeDSDeliveryEmail | Text (254) | No | The email recipient of the purchased product. Provide only if the purchased product is using electronic delivery. |
threeDSShippingDetails | Text (2) | No | Shipping details / type. Select the most suitable one. “01” – Ship to cardholder’s billing address “02” – Ship to another verified address stored in merchant “03” – Ship to address that is different than the cardholder’s billing address “04” – Ship to Store / Pick-up at local store (Store address shall be populated in shipping address fields) “05” – Digital goods (includes online services, electronic gift cards and redemption codes) “06” – Travel and Event tickets, not shipped “07” – Other (for example, Gaming, digital services not shipped, e-media subscriptions, etc.) |
threeDSShippingCountryCode | Text (3) | No | Shipping / delivery country. Shall be the ISO 3166-1 numeric three-digit country code. e.g. “344” – Hong Kong, “840” – US Note: Required if "threeDSShippingState" is present |
threeDSShippingState | Text (3) | No | Shipping / delivery state Should be the country subdivision code defined in ISO 3166-2 e.g. “PE” – Prince Edward Island of California |
threeDSShippingCity | Text (50) | No | Shipping / delivery city. e.g. “Hong Kong” |
threeDSShippingLine1 | Text (50) | No | Shipping / delivery address line 1 |
threeDSShippingLine2 | Text (50) | No | Shipping / delivery address line 2 Provide (if available). |
threeDSShippingLine3 | Text (50) | No | Shipping / delivery address line 3 Provide (if available). |
threeDSShippingPostalCode | Text (16) | No | Shipping / delivery postal code Provide (if available). |
threeDSIsAddrMatch | Text (1) | No | Flag for comparing the billing address and shipping address. Provide (if available). “T” – Shipping address matches billing address “F” – Shipping address NOT match billing address |
Gift Card / Prepaid Card
Provide only if the purchase related to gift card / prepaid card
Parameters | Data Type | Mandatory | Descriptions |
threeDSGiftCardAmount | Text (15) | No | Gift card / prepaid card purchase amount. |
threeDSGiftCardCurr | Text (3) | No | Gift card / prepaid card purchase currency. ISO 4217 three-digit currency code. e.g. “344” – HKD |
threeDSGiftCardCount | Text (2) | No | Number of gift card / prepaid card purchasing. e.g. “12” – Purchasing 12 gift cards |
Pre-Order Purchase
Provide only if the payment is related to Pre-Order
Parameters | Data Type | Mandatory | Descriptions |
threeDSPreOrderReason | Text (2) | No | The pre-order reasons. “01” – The pre-order is due to merchant availability, i.e. the purchasing product is not available due to the insufficient stock in the merchant. “02” – The pre-order is for future release product, i.e. the purchasing product is going to be released on future date. |
threeDSPreOrderReadyDate | Text (8) | No | The expected ready date of the pre-order. Format: YYYYMMDD e.g. “20190401” |
Account Info
Provide only if there is user account in merchant
Parameters | Data Type | Mandatory | Descriptions |
threeDSAcctCreateDate | Text(8) | No | Date that the cardholder opened the account. Format: YYYYMMDD e.g. “20190401” |
threeDSAcctAgeInd | Text(2) | No | Length of time that the cardholder has had the account. • 01 = No account (guest check-out) • 02 = Created during this transaction • 03 = Less than 30 days • 04 = 30−60 days • 05 = More than 60 days |
threeDSAcctLastChangeDate | Text(8) | No | Date that the cardholder’s account was last changed, including Billing or Shipping address, new payment account, or new user(s) added. Format: YYYYMMDD e.g. “20190401” |
threeDSAcctLastChangeInd | Text(2) | No | Length of time since the cardholder’s account information was last changed, including Billing or Shipping address, new payment account, or new user(s) added. • 01 = Changed during this transaction • 02 = Less than 30 days • 03 = 30−60 days • 04 = More than 60 days |
threeDSAcctPwChangeDate | Text(8) | No | Date that cardholder’s account had a password change or account reset. Format: YYYYMMDD e.g. “20190401” |
threeDSAcctPwChangeInd | Text(2) | No | Indicates the length of time since the cardholder’s account had a password change or account reset. • 01 = No change • 02 = Changed during this transaction • 03 = Less than 30 days • 04 = 30−60 days • 05 = More than 60 days |
threeDSAcctPurchaseCount | Text(4) | No | Number of purchases with this cardholder account during the previous six months. e.g. “13” – Purchased 13 times during the previous six months |
threeDSAcctCardProvisionAttempt | Text(3) | No | Number of Add Card attempts in the last 24 hours. e.g. “2” – Tried add card 2 times |
threeDSAcctNumTransDay | Text(3) | No | Number of transactions (successful and abandoned) for this cardholder account across all payment accounts in the previous 24 hours. e.g. “2” – Processed 2 transactions |
threeDSAcctNumTransYear | Text(3) | No | Number of transactions (successful and abandoned) for this cardholder account across all payment accounts in the previous year. e.g. “10” – Processed 10 transactions |
threeDSAcctPaymentAcctDate | Text(8) | No | Date that the payment account was enrolled in the cardholder’s account. Format: YYYYMMDD e.g. “20190401” |
threeDSAcctPaymentAcctInd | Text(2) | No | Indicates the length of time that the payment account was enrolled in the cardholder’s account. • 01 = No account (guest check-out) • 02 = During this transaction • 03 = Less than 30 days • 04 = 30−60 days • 05 = More than 60 days |
threeDSAcctShippingAddrLastChangeDate | Text(8) | No | Date when the shipping address used for this transaction was first used. Format: YYYYMMDD e.g. “20190401” |
threeDSAcctShippingAddrLastChangeInd | Text(2) | No | Indicates when the shipping address used for this transaction was first used • 01 = This transaction • 02 = Less than 30 days • 03 = 30−60 days • 04 = More than 60 days |
threeDSAcctIsShippingAcctNameSame | Text(1) | No | Indicates if the Cardholder Name on the account is identical to the shipping Name used for this transaction. “T” – Account name identical to shipping name “F” – Account name different than shipping name |
threeDSAcctIsSuspiciousAcct | Text(1) | No | Indicates whether has experienced suspicious activity (including previous fraud) on the cardholder account. “T” – Suspicious activity has been observed “F” – No suspicious activity has been observed |
Account Authentication Info
Provide only if there is user account in merchant
Parameters | Data Type | Mandatory | Descriptions |
threeDSAcctAuthMethod | Text(2) | No | Mechanism used by the Cardholder to authenticate. • 01 = No authentication occurred (i.e. cardholder “logged in” as guest) • 02 = Login to the cardholder account at the merchant system using merchant‘s own credentials • 03 = Login to the cardholder account at the merchant system using federated ID • 04 = Login to the cardholder account at the merchant system using issuer credentials • 05 = Login to the cardholder account at the merchant system using third-party authentication • 06 = Login to the cardholder account at the merchant system using FIDO Authenticator |
threeDSAcctAuthTimestamp | Text(8) | No | Date and time in UTC of the cardholder authentication. Format: YYYYMMDD e.g. “20190401” |
Pay Token
Provide only if the card info is de-tokenized from pay token
Parameters | Data Type | Mandatory | Descriptions |
threeDSPayTokenInd | Text(1) | No | Indicates that the transaction was de-tokenized. *Only provide when de-tokenized happened “T” – The card info is de-tokenized from pay token |
Redirect URL
successUrl, failUrl and cancelUrl Output
Parameters | Data Type | Descriptions |
Ref | Text | Merchant’s Order Reference Number (For display purpose only. DO NOT use this URL to update your system. Please use DataFeed for this purpose.) |
Direct Client Side Connection
Introduction
This connection method is tailored for merchants utilizing an Online Shopping Cart System. It relies on HTML and JavaScript, ensuring wide applicability across various online shopping cart software and architectures. While the intricate technical specifications and variations of these systems are beyond the scope of this document, this integration method guarantees a seamless experience.
Compatibility with Shopping Cart Software
For detailed compatibility with specific shopping cart software, we recommend referring to our comprehensive documentation available on our platform. This resource provides extensive information to facilitate a smooth integration process with your preferred shopping cart system.
3-D Secure Verification Process
In cases where the customer's credit card is enrolled in 3-D Secure, an additional layer of security is implemented. The customer will be prompted to provide either a static or one-time password to verify their identity. This 3-D Secure protocol, implemented by major credit card brands such as VISA ("Verified By VISA"), MasterCard ("MasterCard SecureCode"), JCB ("J/Secure"), and AMEX ("AMEX SafeKey"), significantly reduces fraudulent online transactions.
Integration with Verified By VISA (3-D Secure)
This document uses Verified By VISA as an illustrative example to demonstrate the verification process in detail, emphasizing its standardized approach across all major brand types.
SSL Certificate Requirement
For merchants opting for this connection method, a 128-bit SSL server certificate must be installed to ensure data encryption. The system strictly requires encrypted data for processing.
Our payment gateway system employs an Extended Validation (EV) SSL Certificate to enhance security. To ensure seamless functionality, it's crucial to verify if your certificate store recognizes the VeriSign intermediate CA certificate - Secure SitePro / Managed PKI for SSL Premium with EV Certificates. If not, please install the VeriSign intermediate CA certificate in your certificate store.
Server Side Direct Connection
Introduction
This connection method is for merchant to request payment authorization from bank directly through our payment gateway system and subject to approval of acquiring bank. For example, merchant’s IVR system or mobile application can directly integrate to us. And in this connection, merchants need to build their own payment information collection page to collect payment information, such as credit card number, expire data, holder’s name and etc. Then, payment information has to be sent to a defined URL provided by the acquiring bank. Customer of the merchant, therefore, will not see any bank’s payment page.
For merchant who chooses this method of connection, 128-bit SSL cert must be installed for data encryption. The system does not accept non-encrypted data.
Our payment gateway system uses Extended Validation (EV) SSL Certificate. To ensure your system function properly, please check your certificate store can recognize VeriSign intermediate CA certificate - Secure Site Pro/Managed PKI for SSL Premium with EV Certificates. If not, you are required to install the VeriSign intermediate CA certificate in your certificate store.
Please download the primary and secondary VeriSign EV SSL Intermediate CA certificates from the following link then import the 2 certificates into the keystore of your environment. http://www.verisign.com/support/verisign-intermediate-ca/extended-validation-pro/index.html
(Please be reminded that you should choose the option “Issued After May 17th, 2009”)
We use Server Side Direct Connection for App 2 App integration and wallet payment direct integration. For the detail, please reference with "Integration Guide (Wallet Direct Connection)”
Mobile Integration
Data Feed Handling
To use data feed function, merchant has to create a data feed page and inform payment gateway system about the location of your page (e.g. http://www.yourdomain.com/datafeed.jsp). Merchant can enable or disable this function in the merchant administration site.
Transaction Security By Secure Hash
Multi-Currency Processing Service
Functions Of Merchant API
Exceptional Transaction Handling
This section explains various scenarios of transactions, other than good and successful transactions that may occur.
Payment Methods by Regions/Countries
Australia
Payment Options | Payment Methods |
Credit and Debit Card | American Express, China UnionPay, Mastercard, Visa |
Internet Banking | PayTo, PayID |
Digital Wallet | Alipay, PayPal, PayID, WechatPay |
Buy Now Pay Later | AfterPay, Humm, Zip |
China
Payment Options | Payment Methods |
Credit and Debit Card | American Express, JCB, Mastercard, Visa |
Digital Wallet | Alipay, WechatPay |
Hong Kong
Payment Options | Payment Methods |
Credit and Debit Card | American Express, China UnionPay, Diners, Discover, JCB, Mastercard, Visa |
Digital Wallet | Alipay, Alipay HK, WeChat Pay, Paypal, BoC Pay, PayMe, Octopus, FPS, PPS, Google Pay, Samsung Pay, Apple Pay |
Bank Account and Net Banking | FPS, PPS |
Global (no grouping) | Apple Pay, Google Pay, Samsung Pay, Click to Pay |
Installment | Visa Instalment |
India
Payment Options | Payment Methods |
Credit and Debit Card | American Express, Mastercard, RuPay, Visa |
Bank Account and Net Banking | NetBanking, UPI |
Digital Wallet | ITZ Cash Card, Mobikwik, PhonePe, Yes Bank Wallet |
Installment | EMI |
Indonesia
Payment Options | Payment Methods |
Credit and Debit Card | American Express, JCB, Mastercard, Visa |
Bank Account and Net Banking | BCA KlikPay, BNI Virtual Account, CIMB Clicks, Danamon Virtual Account, Mandiri Clickpay, Permata Virtual Account |
Over-the-counter | Alfamart Group, Indomaret |
Digital Wallet | Dana |
Buy Now Pay Later | Kredivo, Indodana |
Japan
Payment Options | Payment Methods |
Digital Wallet | Alipay HK |
Korea
Payment Options | Payment Methods |
Credit and Debit Card | MasterCard, Virtual Account, Visa |
Digital Wallet | Naver Pay, Kakao Pay, PayCo |
Others | Toss |
Macau
Payment Options | Payment Methods |
Credit and Debit Card | American Express, JCB, Mastercard, Visa |
Crypto | BNB (Binance), BTC (Bitcoin), ETH (Ethereum), LBTC (Lightning Bitcoin), USDC (USD Coin), USDT (Tether) |
Others | ALIPAYHKONL, WECHATONL |
Malaysia
Payment Options | Payment Methods |
Credit and Debit Card | American Express, China UnionPay, Discover, JCB, Mastercard, Visa |
Bank Account and Net Banking | FPX |
Crypto | BNB (BINANCE), BTC (Bitcoin), ETH (Ethereum), LBTC (Lightning Bitcoin), USDC (USD Coin), USDT (Tether) |
Digital Wallet | Alipay, WechatPay, PayPal , BOOST, TouchnGo, Scan & Pay by MAE, GrabPay, Shopback Pay |
Buy Now Pay Later | Atome, PayLater by Grab |
Philippines
Payment Options | Payment Methods |
Credit and Debit Card | American Express, China UnionPay, Diners, Dicover, JCB, Mastercard, Visa |
Bank Account and Net Banking | BDO (Brankas), BPI, Landbank (Brankas), Metrobank (Brankas), RCBC (Brankas), Unionbank (Brankas) |
Digital Wallet | Gcash, Grabpay, ShopeePay, MAYA, Alipay, Wechatpay |
Over-the-counter | Bayad Center, BDO, Cebuana, ECPay, RCBC |
Others | PayPal |
Buy Now Pay Later | TendoPay |
Singapore
Payment Options | Payment Methods |
Credit and Debit Card | American Express, China UnionPay, Diners, Discover, JCB, Mastercard, Visa |
Bank Account and Net Banking | ENETS, PayNow |
Crypto | BNB (Binance), BTC (Bitcoin), ETH (Ethereum), LBTC (Lightning Bitcoin), USDC (USD Coin), USDT (Tether) |
Digital Wallet | GrabPay, Shopback Pay, ShopeePay, Alipay, Wechatpay, SGQR, PayPal |
Buy Now Pay Later | Atome, PayLater by Grab, Shopee SPayLater |
Taiwan
Payment Options | Payment Methods |
Global (no grouping) | Apple Pay, Google Pay, Samsung Pay |
Credit and Debit Card | JCB, MasterCard, Visa |
Digital Wallet | Linepay, Jkopay, Apple Pay , Google Pay |
Thailand
Payment Options | Payment Methods |
Global (no grouping) | GooglePay |
Credit and Debit Card | American Express, China UnionPay, JCB, Mastercard, Visa |
Bank Account and Net Banking | BAY, BBL, KBANK, SCB, TMB, UOB |
Digital Wallet | Paypal |
Buy Now Pay Later | Atome |
Over-the-counter | BBL, Kbank, KTB, Lotus, Mpay, TTB, UOB |
Vietnam
Payment Options | Payment Methods |
Credit and Debit Card | American Express, JCB, Mastercard, Visa |
Internet Banking | NAPAS (43 banks), OnePay |
Buy Now Pay Later | Kredivo |
Digital Wallet | MoMo |