# Pre-front solution

> Follow the best practices to guide you in presenting bank lists, payment details, QR codes, or payment passwords on your page.

In standard integration experiences, buyers are required to redirect to a payment method page to complete certain actions, such as selecting a specific bank payment method, entering payment details, or scanning/copying payment passwords. The following best practices guide you in presenting bank lists, payment details, QR codes, or payment passwords on your page, reducing the need for page redirection during the payment process and improving the buyer experience.

-   [Bank pre-front solution](#GK7ay)
-   [Payment element pre-front solution](#cfUcW)
-   [QR code/password pre-front solution](#b2zaW)

## Bank pre-front solution

In a standard integration solution, buyers need to select a specific online banking option on the payment method page before being redirected to the online banking page. However, this process can be time-consuming and often leads to higher buyer drop-off rates. The bank pre-front solution allows buyers to directly redirect to the bank page after selecting a bank on the merchant page, rather than redirecting to the Antom intermediate page to select a specific bank and then redirect to the bank, which optimizes the payment experience of online banking.

### User experience

This pre-front capability supports integration on web, WAP, and app platforms. The following figure compares the user experience between the standard solution and the optimized solution for a buyer using the [Przelewy24](https://docs.antom.com/ac/antomop/przelewy24.md) payment method on the merchant's app platform.

| **Standard Solution** | **Optimized Solution** |
| --- | --- |
| ![image.png](https://idocs-assets.marmot-cloud.com/storage/idocs87c36dc8dac653c1/yuque/idocs/2025/png/e46061a3-9f0c-49ac-9909-b38fe616dace.png) | ![image.png](https://idocs-assets.marmot-cloud.com/storage/idocs87c36dc8dac653c1/yuque/idocs/2025/png/051eec1d-f3d9-428f-af96-9f7d2a15d2bf.png) |
| **Merchant page**: Select a payment method. **Antom** **intermediate page**: Select a specific bank. **Bank page**: Complete the payment. | **Merchant page**: Select a payment method and specific bank. **Bank page**: Complete the payment. |

  Table 1. Comparison of user experience between standard solution and bank pre-front solution

The differences between the standard solution and the optimized solution:

-   **Standard Solution**: Buyers need to redirect to an intermediate Przelewy24 page to select a specific bank.
-   **Optimized Solution**: Buyers can directly select a bank on the merchant's page, eliminating the need to redirect to an intermediate Przelewy24 page and reducing buyer drop-off.

### Integration considerations

The integration steps for this solution are consistent with the standard integration process, requiring only minor adjustments to the input and output parameters of the API.

-   When calling the [**consult**](https://docs.antom.com/ac/ams/consult.md) API to obtain the list of payment methods, for payment methods that support bank pre-front solution, the _supportBanks list_ is returned in the _paymentOptionDetail_ field. Taking the payment method Przelewy24 as an example, the available bank list for this payment method will be displayed in the sub-parameters _bankIdentifierCode_ and _bankShortName_ of _paymentOptionDetail.supportBanks_. Additionally, you can contact Antom Technical Support to obtain the corresponding logo.
-   When calling the [**pay**](https://docs.antom.com/ac/ams/payment_cashier.md) API, you need to pass the payment method and specify the bank. For example, for the Przelewy24 payment method, if the buyer selects ING Bank Śląski as the bank under the Przelewy24 channel, you need to include the following parameters in the input of the **pay** API:

-   _paymentMethod.paymentMethodType_: `P24`
-   _paymentMethod.paymentMethodMetaData.bankIdentifierCode_: `49`

The following is the code sample:

```json
"paymentMethod": {
        "paymentMethodType": "P24",
        "paymentMethodMetaData": {
            "bankIdentifierCode": "49"
        }
    }
```

### Supported payment methods

The following table shows the payment method enumeration values, bank abbreviations, and specific bank enumeration values corresponding to the payment methods supported by the bank pre-front solution.

| **Payment methods** | **Payment method enumeration values** | **Abbreviation of bank name** | **Specific bank enumeration** |
| --- | --- | --- | --- |
| **Payment methods** | _**paymentMethodType**_ | _**bankShortName**_ | _**bankIdentifierCode**_ |
| [FPX](https://docs.antom.com/ac/antomop/fpx.md) | `ONLINEBANKING_FPX` | `Maybank` | `MYM2U` |
| [FPX](https://docs.antom.com/ac/antomop/fpx.md) | `ONLINEBANKING_FPX` | `Bank Islam` | `MYBISM` |
| [FPX](https://docs.antom.com/ac/antomop/fpx.md) | `ONLINEBANKING_FPX` | `RHB Bank` | `MYRHB` |
| [FPX](https://docs.antom.com/ac/antomop/fpx.md) | `ONLINEBANKING_FPX` | `Hong Leong Bank` | `MYHLB` |
| [FPX](https://docs.antom.com/ac/antomop/fpx.md) | `ONLINEBANKING_FPX` | `CIMB Bank` | `MYCIMBCLICKS` |
| [FPX](https://docs.antom.com/ac/antomop/fpx.md) | `ONLINEBANKING_FPX` | `AmBank` | `MYAMB` |
| [FPX](https://docs.antom.com/ac/antomop/fpx.md) | `ONLINEBANKING_FPX` | `Public Bank` | `MYPBB` |
| [FPX](https://docs.antom.com/ac/antomop/fpx.md) | `ONLINEBANKING_FPX` | `Affin Bank` | `MYABB` |
| [FPX](https://docs.antom.com/ac/antomop/fpx.md) | `ONLINEBANKING_FPX` | `Agro Bank` | `MYAGB` |
| [FPX](https://docs.antom.com/ac/antomop/fpx.md) | `ONLINEBANKING_FPX` | `Alliance Bank` | `MYABMB` |
| [FPX](https://docs.antom.com/ac/antomop/fpx.md) | `ONLINEBANKING_FPX` | `Bank Muamalat` | `MYBMMB` |
| [FPX](https://docs.antom.com/ac/antomop/fpx.md) | `ONLINEBANKING_FPX` | `Bank of China` | `MYBOC` |
| [FPX](https://docs.antom.com/ac/antomop/fpx.md) | `ONLINEBANKING_FPX` | `Bank Rakyat` | `MYBKRM` |
| [FPX](https://docs.antom.com/ac/antomop/fpx.md) | `ONLINEBANKING_FPX` | `Bank Simpanan Nasional` | `MYBSN` |
| [FPX](https://docs.antom.com/ac/antomop/fpx.md) | `ONLINEBANKING_FPX` | `HSBC Bank` | `MYHSBC` |
| [FPX](https://docs.antom.com/ac/antomop/fpx.md) | `ONLINEBANKING_FPX` | `Kuwait Finance House` | `MYKFH` |
| [FPX](https://docs.antom.com/ac/antomop/fpx.md) | `ONLINEBANKING_FPX` | `OCBC Bank` | `MYOCBC` |
| [FPX](https://docs.antom.com/ac/antomop/fpx.md) | `ONLINEBANKING_FPX` | `Standard Chartered Bank` | `MYSCB` |
| [FPX](https://docs.antom.com/ac/antomop/fpx.md) | `ONLINEBANKING_FPX` | `UOB Bank` | `MYUOB` |
| [Przelewy24](https://docs.antom.com/ac/antomop/przelewy24.md) | `P24` | `Santander-Przelew24` | `20` |
| [Przelewy24](https://docs.antom.com/ac/antomop/przelewy24.md) | `P24` | `Pay with Inteligo` | `26` |
| [Przelewy24](https://docs.antom.com/ac/antomop/przelewy24.md) | `P24` | `Płacę z iPKO (PKO BP)` | `31` |
| [Przelewy24](https://docs.antom.com/ac/antomop/przelewy24.md) | `P24` | `BNP Paribas` | `33` |
| [Przelewy24](https://docs.antom.com/ac/antomop/przelewy24.md) | `P24` | `Bank PEKAO S.A` | `43` |
| [Przelewy24](https://docs.antom.com/ac/antomop/przelewy24.md) | `P24` | `Credit Agricole` | `45` |
| [Przelewy24](https://docs.antom.com/ac/antomop/przelewy24.md) | `P24` | `ING Bank Śląski` | `49` |
| [Przelewy24](https://docs.antom.com/ac/antomop/przelewy24.md) | `P24` | `Konto Inteligo` | `52` |
| [Przelewy24](https://docs.antom.com/ac/antomop/przelewy24.md) | `P24` | `Bank PKO BP (iPKO)` | `53` |
| [Przelewy24](https://docs.antom.com/ac/antomop/przelewy24.md) | `P24` | `Santander` | `54` |
| [Przelewy24](https://docs.antom.com/ac/antomop/przelewy24.md) | `P24` | `Toyota Bank` | `64` |
| [Przelewy24](https://docs.antom.com/ac/antomop/przelewy24.md) | `P24` | `Bank PEKAO S.A.` | `65` |
| [Przelewy24](https://docs.antom.com/ac/antomop/przelewy24.md) | `P24` | `Volkswagen Bank` | `69` |
| [Przelewy24](https://docs.antom.com/ac/antomop/przelewy24.md) | `P24` | `Bank Millennium` | `85` |
| [Przelewy24](https://docs.antom.com/ac/antomop/przelewy24.md) | `P24` | `Pay with Alior Bank` | `88` |
| [Przelewy24](https://docs.antom.com/ac/antomop/przelewy24.md) | `P24` | `Nest Bank` | `90` |
| [Przelewy24](https://docs.antom.com/ac/antomop/przelewy24.md) | `P24` | `Credit Agricole` | `95` |
| [Przelewy24](https://docs.antom.com/ac/antomop/przelewy24.md) | `P24` | `Pay with BOŚ` | `99` |
| [Przelewy24](https://docs.antom.com/ac/antomop/przelewy24.md) | `P24` | `Pay with ING` | `112` |
| [Przelewy24](https://docs.antom.com/ac/antomop/przelewy24.md) | `P24` | `Pay with CitiHandlowy` | `119` |
| [Przelewy24](https://docs.antom.com/ac/antomop/przelewy24.md) | `P24` | `Alior - Raty` | `129` |
| [Przelewy24](https://docs.antom.com/ac/antomop/przelewy24.md) | `P24` | `Pay with Plus Bank` | `131` |
| [Przelewy24](https://docs.antom.com/ac/antomop/przelewy24.md) | `P24` | `mBank - Raty` | `136` |
| [Przelewy24](https://docs.antom.com/ac/antomop/przelewy24.md) | `P24` | `e-transfer Pocztowy24` | `141` |
| [Przelewy24](https://docs.antom.com/ac/antomop/przelewy24.md) | `P24` | `Banki Spółdzielcze` | `143` |
| [Przelewy24](https://docs.antom.com/ac/antomop/przelewy24.md) | `P24` | `Bank Nowy BFG S.A.` | `144` |
| [Przelewy24](https://docs.antom.com/ac/antomop/przelewy24.md) | `P24` | `Getin Bank` | `153` |
| [Przelewy24](https://docs.antom.com/ac/antomop/przelewy24.md) | `P24` | `BLIK` | `154` |
| [Przelewy24](https://docs.antom.com/ac/antomop/przelewy24.md) | `P24` | `Noble Pay` | `158` |
| [Przelewy24](https://docs.antom.com/ac/antomop/przelewy24.md) | `P24` | `Pay with IdeaBank` | `161` |
| [Przelewy24](https://docs.antom.com/ac/antomop/przelewy24.md) | `P24` | `NestPrzelew` | `222` |
| [Przelewy24](https://docs.antom.com/ac/antomop/przelewy24.md) | `P24` | `BNP Paribas Płacę z Pl@net` | `223` |
| [Przelewy24](https://docs.antom.com/ac/antomop/przelewy24.md) | `P24` | `mBank - mTransfer` | `243` |
| [Przelewy24](https://docs.antom.com/ac/antomop/przelewy24.md) | `P24` | `P24now` | `266` |
| [Przelewy24](https://docs.antom.com/ac/antomop/przelewy24.md) | `P24` | `mBank (PIS)` | `270` |
| [Przelewy24](https://docs.antom.com/ac/antomop/przelewy24.md) | `P24` | `ING Bank Śląski (PIS)` | `271` |
| [Przelewy24](https://docs.antom.com/ac/antomop/przelewy24.md) | `P24` | `BNP Paribas (PIS)` | `272` |
| [Przelewy24](https://docs.antom.com/ac/antomop/przelewy24.md) | `P24` | `Bank PKO BP (PIS)` | `274` |
| [Przelewy24](https://docs.antom.com/ac/antomop/przelewy24.md) | `P24` | `Santander (PIS)` | `275` |
| [Przelewy24](https://docs.antom.com/ac/antomop/przelewy24.md) | `P24` | `Konto Inteligo (PIS)` | `279` |
| [Przelewy24](https://docs.antom.com/ac/antomop/przelewy24.md) | `P24` | `Alior Bank (PIS)` | `280` |
| [Pay by Bank](https://docs.antom.com/ac/antomop/pay_by_bank.md) | `ONLINEBANKING_YAPILY` | `monzo_ob` | `ipay-monzo ` |
| [Pay by Bank](https://docs.antom.com/ac/antomop/pay_by_bank.md) | `ONLINEBANKING_YAPILY` | `santander_uk` | `ipay-santander ` |
| [Pay by Bank](https://docs.antom.com/ac/antomop/pay_by_bank.md) | `ONLINEBANKING_YAPILY` | `hsbc_uk` | `ipay-hsbc ` |
| [Pay by Bank](https://docs.antom.com/ac/antomop/pay_by_bank.md) | `ONLINEBANKING_YAPILY` | `lloyds` | `ipay-lloyds ` |
| [Pay by Bank](https://docs.antom.com/ac/antomop/pay_by_bank.md) | `ONLINEBANKING_YAPILY` | `revolut` | `ipay-revolut ` |
| [Pay by Bank](https://docs.antom.com/ac/antomop/pay_by_bank.md) | `ONLINEBANKING_YAPILY` | `barclays` | `ipay-barclays ` |
| [Pay by Bank](https://docs.antom.com/ac/antomop/pay_by_bank.md) | `ONLINEBANKING_YAPILY` | `natwest` | `ipay-natwest ` |
| [Pay by Bank](https://docs.antom.com/ac/antomop/pay_by_bank.md) | `ONLINEBANKING_YAPILY` | `nationwide` | `ipay-nationwide ` |

Table 2. Supported payment methods for bank pre-front solution

## Payment element pre-front solution

In a standard integration solution, buyers need to navigate to the payment method page to enter payment elements (such as login credentials, dynamic passwords, etc.) before completing the payment. However, this process can be time-consuming and often leads to higher buyer drop-off rates. To avoid this, this solution directly redirects to the payment method page or receives a push notification from the mobile phone after entering the buyer's mobile account, payment password, email address and personal tax number on the merchant page, rather than redirecting to the Antom intermediate page to collect the buyer payment information and then redirect to the payment method page, reducing the need for redirection and minimizing buyer drop-off.

### User experience

This pre-front capability also supports integration on web, WAP, and app platforms. The following figure compares the user experience between the standard solution and the optimized solution for a buyer using the [Pay-easy](https://docs.antom.com/ac/antomop/payeasy.md) payment method on the merchant's app.

| **Standard Solution** | **Optimized Solution** |
| --- | --- |
| ![image.png](https://idocs-assets.marmot-cloud.com/storage/idocs87c36dc8dac653c1/yuque/idocs/2025/png/3cef1a82-1e91-4c44-90dd-2e9091bd5c01.png) | ![image.png](https://idocs-assets.marmot-cloud.com/storage/idocs87c36dc8dac653c1/yuque/idocs/2025/png/581838e2-8338-46cc-8bf4-1996003e63d4.png) |
| **Merchant page**: Select the payment method. **Antom** **intermediate page**: Enter the buyer information. **Bank page**: Complete the payment. | **Merchant page**: Select the payment method and enter the buyer information. **Bank page**: Complete the payment. |

Table 3. Comparison of user experience between standard solution and payment element pre-front solution

The differences between the standard solution and the optimized solution:

-   **Standard Solution**: Buyers need to redirect to an intermediate Antom page to enter their Pay-easy account information.
-   **Optimized Solution**: Buyers can directly input their account information on the merchant's page, eliminating the need to redirect to an intermediate Antom page and reducing buyer drop-off.

### Integration considerations

The integration steps for this solution are consistent with the standard integration process, requiring only minor adjustments to note:

When calling the [**pay**](https://docs.antom.com/ac/ams/payment_cashier.md) API, you need to specify the payment method and buyer information. For example, for the Pay-easy payment method, if the buyer enters the personal information under the Pay-easy channel on the merchant page, you need to include the following parameters in the **pay** API.

```json
"buyer": {
  "buyerEmail": "gaga@gaga.com",
  "buyerName": {
    "firstName": "lady",
    "lastName": "gaga"
  },
  "buyerPhoneNo": "12345678901"
}
```

### Supported payment methods

The following table shows the payment methods supported by the payment element pre-front solution, the payment elements they collect, the corresponding parameter names for the payment elements, and the best practices for implementing this solution.

| **Payment methods** | **Collect payment** **components** | **Payment component parameter name** | **Best practices** |
| --- | --- | --- | --- |
| [OVO](https://docs.antom.com/ac/antomop/ovo.md) | OVO mobile account | - _order.buyer.buyerPhoneNo_ | Guide the buyer to input their OVO mobile account on the merchant page, with the suggested message: Manually open the OVO application and complete the payment within 55 seconds.。 |
| [BLIK](https://docs.antom.com/ac/antomop/blik.md) | BLIK 6-digit dynamic password, client device IP address, buyer browser agent | - _paymentMethodMetaData.blikCode_ - _env.clientIp_ - _env.browserInfo.userAgent_ | Guide the buyer to input their BLIK code on the merchant page, with the suggested message: How to obtain BLIK code: Please find the BLIK code in the BLIK application; How to pay: Manually open the BLIK application and complete the payment within 15 seconds. |
| [Przelewy24](https://docs.antom.com/ac/antomop/przelewy24.md) | Buyer's email | - _paymentMethodMetaData.payerEmail_ | 1. Guide the buyer to input their email on the merchant page or use a previously stored buyer email. 2. Use the payment API's returned payment method link to redirect the buyer to the payment method page. |
| [Mercado Pago](https://docs.antom.com/ac/antomop/mp_mdx.md) (Brazil) | Brazilian individual tax ID | - _paymentMethodMetaData.cpf_ | Guide buyers to input Brazilian individual tax ID on the merchant page and manually open the Mercado Pago application to complete the payment. |
| [Mercado Pago](https://docs.antom.com/ac/antomop/mp_mdx.md) (Brazil, Mexico, Chile, and Peru) | Buyer's email | - _paymentMethodMetaData.payerEmail_ | Guide buyers to input email on the merchant page and manually open the Mercado Pago application to complete the payment. |
| [BANCOMAT Pay](https://docs.antom.com/ac/antomop/bancomatpay.md) | BANCOMAT Pay mobile account | - _order.buyer.buyerPhoneNo_ | Guide buyers to input their BANCOMAT Pay mobile account on the merchant page, with the suggested message: Only support the registration of Bancomat Pay in the EU mobile number. The mobile phone format is +39\*\*\*\*\*\*, and no more than 20 characters. |
| [Pay-easy](https://docs.antom.com/ac/antomop/payeasy.md) | Buyer's name, phone number, and email | - _order.buyer.buyerName.firstName_ - _order.buyer.buyerName.lastName_ - _order.buyer.buyerEmail_ - _order.buyer.buyerPhoneNo_ | Guide buyers to input the personal information on the merchant page: Name, phone number, and email address. |
| [Konbini](https://docs.antom.com/ac/antomop/Konbini_mdx.md) | Buyer's name, phone number, email, and store name | - _order.buyer.buyerName.firstName_ - _order.buyer.buyerName.lastName_ - _order.buyer.buyerEmail_ - _order.buyer.buyerPhoneNo_ - _paymentMethod.paymentMethodMetaData.storeName_ | Guide buyers to input the personal information on the merchant page: Name, phone number, email address, and store name. |
| [Konbini (7-Eleven)](https://docs.antom.com/ac/antomop/Konbini_711_mdx.md) | Buyer's name, phone number, and email | - _order.buyer.buyerName.firstName_ - _order.buyer.buyerName.lastName_ - _order.buyer.buyerEmail_ - _order.buyer.buyerPhoneNo_ | Guide buyers to input the personal information on the merchant page: Name, phone number, and email address. |
| [MB WAY](https://docs.antom.com/ac/antomop/mbway.md) | Buyer's phone number | - _paymentMethod.paymentMethodMetaData.payerPhoneNo_ | Guide buyers to input their MB WAY mobile account on the merchant page. The mobile phone format is +35\* \*\*\*\*\*\*\*\*\*. |

Table 4. Supported payment methods for payment element pre-front solution

## QR code/password pre-front solution

In a standard integration solution, buyers need to navigate to the payment method page to scan a QR code or enter a payment password to complete the payment. However, this process can be time-consuming and often leads to higher buyer drop-off rates. To mitigate this, you can display the payment QR code or payment password on the merchant's page, reducing the need for redirection and minimizing buyer drop-off.

### User experience

This pre-front capability supports integration on web, WAP, and app platforms. The following figure compares the user experience, best practices, and the standard and optimized solutions for a buyer using the [AlipayHK](https://docs.antom.com/ac/antomop/aplusalipayhk.md) payment method on the merchant's web platform for QR code pre-front mode and the bank transfer payment method on the merchant's app platform for password pre-front mode.

| **Pre-front mode** | **Standard solution** | **Optimized solution** | **Best practices** |
| --- | --- | --- | --- |
| QR code pre-front solution | ![image.png](https://idocs-assets.marmot-cloud.com/storage/idocs87c36dc8dac653c1/yuque/idocs/2025/png/42b4a14b-a519-4a0a-8c2c-03d5315f0f8f.png) | ![image.png](https://idocs-assets.marmot-cloud.com/storage/idocs87c36dc8dac653c1/yuque/idocs/2025/png/b2354dd3-b054-47bb-9abe-152f05624014.png) | - It is recommended that you specify the _orderCodeForm.expireTime_ parameter to set the timeout period and display the payment QR code expiration countdown on the merchant page. - It is recommended that you use a floating layer to display the payment QR code. - For payment methods AlipayHK, Alipay, GCash, Touch'n Go eWallet, Kakao Pay, LINE Pay, TrueMoney, you need to present the QR code in a floating layer according to the brand specification and display the " powered by A+" at the bottom of the code page. - Payment methods of QRIS, PayNow, and PromptPay have a code-scanning experience on all three platforms (Web, WAP, and App), and you can provide this capability to these payment methods on all three platforms. - For other payment methods, it is recommended to display the QR code on the Web only, and use the evoke app payment or password payment experience on the WAP and App. |
| Password pre-front solution | ![image.png](https://idocs-assets.marmot-cloud.com/storage/idocs87c36dc8dac653c1/yuque/idocs/2025/png/a389d1d1-dab4-4ceb-b65a-1d8793489054.png) | ![image.png](https://idocs-assets.marmot-cloud.com/storage/idocs87c36dc8dac653c1/yuque/idocs/2025/png/fe264568-9d25-412b-aa2f-5cdeb60fc3f3.png) | - It is recommended that you specify the _orderCodeForm.expireTime_ parameter to set the timeout period and display the payment QR code expiration countdown on the merchant page. - It is recommended that you use a floating layer to display the payment password. The floating layer supports buyers to copy passwords and provides operation tips for buyers. |

Table 5. Comparison of user experience between standard solution and QR Code/Password Pre-Front Solution

The differences between the standard solution and the optimized solution:

-   **Standard solution**: Buyers need to redirect to an intermediate Antom page to scan the QR code or retrieve the password.
-   **Optimized solution**: Buyers can directly scan the QR code or retrieve the password on the merchant's page, eliminating the need to redirect to an intermediate Antom page and reducing buyer drop-off.

### Integration considerations

Although the integration steps for this solution are consistent with the standard integration process, there are some key differences to note:

In the response of the payment request, you can obtain the payment QR code or payment password through the _orderCodeForm.codeDetails.codeValue_ field. The payment QR code can be provided in text format (_displayType_ = `TEXT/MIDDLEIMAGE/SMALLIMAGE/BIGIMAGE`). The payment password is provided in `TEXT` format (When the `TEXT` type is a link, it means that the QR code needs to be processed separately). You can display the payment QR code or payment password on the merchant's page as needed, and show the expiration time according to the _orderCodeForm.expireTime_ field. When the buyer's payment is completed, the merchant side controls the redirect to the payment result page to ensure that the buyer can check the payment status timely.

The following is a code example:

```json
"orderCodeForm": {
    "codeDetails": [
      {
        "codeValue": "5461581653",
        "displayType": "TEXT"
      },
      {
        "codeValue": "https://global.alipay.com/merchant/order/showQrImage.htm?code=https%3A%2F%2Fglobal.alipay.com%2F281002040091leOl1lerj31tHD30nPg8YNIS&picSize=L",
        "displayType": "BIGIMAGE"
      },
      {
        "codeValue": "https://global.alipay.com/merchant/order/showQrImage.htm?code=https%3A%2F%2Fglobal.alipay.com%2F281002040091leOl1lerj31tHD30nPg8YNIS&picSize=M",
        "displayType": "MIDDLEIMAGE"
      },
      {
        "codeValue": "https://global.alipay.com/merchant/order/showQrImage.htm?code=https%3A%2F%2Fglobal.alipay.com%2F281002040091leOl1lerj31tHD30nPg8YNIS&picSize=S",
        "displayType": "SMALLIMAGE"
      },
      {
        "codeValue": "|010555303610000 0000005461581653 0000005461581653 3500",
        "displayType": "TEXT"
      }
    ],
    "expireTime": "2025-03-27T23:26:06-07:00"
  },
```

### Supported payment methods

The following table shows the payment methods supported by the QR code/password pre-front solution and the recommended merchant-side implementation type for this capability.

| **Pre-front mode** | **Supported payment methods** | **Recommended merchant-side implementation type** |
| --- | --- | --- |
| QR code pre-front solution | [QRIS](https://docs.antom.com/ac/antomop/qris.md), [PayNow](https://docs.antom.com/ac/antomop/paynow.md), [PromptPay](https://docs.antom.com/ac/antomop/promptpay.md), [Konbini](https://docs.antom.com/ac/antomop/konbini_mdx.md) | Web, WAP, App |
| QR code pre-front solution | [AlipayHK](https://docs.antom.com/ac/antomop/aplusalipayhk.md), [Alipay](https://docs.antom.com/ac/antomop/alipay_cn.md), [GCash](https://docs.antom.com/ac/antomop/gcash.md), [Touch'n Go eWallet](https://docs.antom.com/ac/antomop/touchngo.md), [Kakao Pay](https://docs.antom.com/ac/antomop/kakaopay.md), [LINE Pay](https://docs.antom.com/ac/antomop/rabbitlinepay.md), [TrueMoney](https://docs.antom.com/ac/antomop/truemoney.md), [ShopeePay](https://docs.antom.com/ac/antomop/shopeepay.md), [Pay by Bank](https://docs.antom.com/ac/antomop/pay_by_bank.md) | Web |
| Password pre-front solution | [Pix](https://docs.antom.com/ac/antomop/pix.md) | Web, WAP, App |
| Password pre-front solution | [Bangkok Bank](https://docs.antom.com/ac/antomop/bangkok_bank.md) | Web, WAP, App |
| Password pre-front solution | [Siam Commercial Bank](https://docs.antom.com/ac/antomop/scb.md) | Web, WAP, App |
| Password pre-front solution | [Bank of Ayudhya](https://docs.antom.com/ac/antomop/bay.md) | Web, WAP, App |
| Password pre-front solution | [KrungThai Bank](https://docs.antom.com/ac/antomop/kyb.md) | Web, WAP, App |
| Password pre-front solution | [Kbank](https://docs.antom.com/ac/antomop/kbank.md) | Web, WAP, App |
| Password pre-front solution | [Government Savings Bank](https://docs.antom.com/ac/antomop/gsb.md) | Web, WAP, App |

Table 6. Supported payment methods for QR Code and Password Pre-Front Solution

> **Note**: Pay by bank requires the bank pre-front to be implemented first, after which Antom will return the QR codes for each bank.