# Aquiring - Start a test

- In the test environment, to facilitate merchants in debugging the processing flows for different payment results during the integration process, PayerMax provides a comprehensive simulation strategy.

- During the joint debugging phase, merchants can select a payment method, enter payment information that meets the format requirements, and then proceed to the simulation interface to complete the simulated payment.

- The test environment does not perform actual deductions. User account information is only verified for format compliance, not for authenticity.

## 1. Simulation Rules for Integration Modes

Please note that the test amount you set must fall within the current payment method's limit range.

### 1.1 General Rules for Direct Card Payments

- Payment methods: CARD, APPLEPAY, GOOGLEPAY.

::: warning The payment result can be mocked by specifying the following values for the `subject` parameter when placing an order:
- Success: `subject = SUCCESS` or any other value
- Failure: `subject = FAILED`
- Pending: `subject = PENDING`
:::

- 3DS Mock: `subject = 3DS`

    - Supported integration modes: Pure API Payment, Frontend Components
    - Payment method: CARD
    - On the 3DS page, selecting successful authentication results in a successful payment, while selecting failed authentication results in a failed payment.

![](https://img-cdn-sg.payermax.com/public/20250528-1b79839f-3dde-4a93-a060-820f378c4a02.png)

### 1.2 Cashier Payment and PayByLink

#### 1.2.1 APM

- Redirect URL Interaction: In the production environment, users are redirected to the external payment page. In the test environment, it will jump to the result selection page.

  - List of payment methods:

| Country | Payment Method Type | Target Institution |
| ------- | ------------------- | ------------------ |
| CN      | WALLET              | ALIPAY             |
| ......  |                     |                    |

  - Mocking scheme:

::: warning Jump Link:
- Select "Successful": Redirects to the success page, triggers a callback notification, and the order status is set to `SUCCESS`.
- Select "Failed": Redirects to the failure page. Users can close the order by clicking the "Close" button on the result page, or wait for the order to expire, after which a callback notification will be triggered, and the order status will be set to `FAILED`.
- Select "Pending": Redirects to the pending page. A callback notification will be triggered after the order expires.
:::

![](https://img-cdn-sg.payermax.com/public/20250528-ff4cd37c-e26b-487e-a067-2577fdd84303.png)

- OTP Interaction: Enter the SMS verification code to directly obtain the payment result.

  - List of payment methods:

| Country | Payment Method Type | Target Institution |
| ------- | ------------------- | ------------------ |
| SA      | WALLET              | STCPAY             |

  - Mocking scheme: By default, the payment result is returned as successful. If the `subject` field is specified, the result will be returned accordingly.

::: warning The payment result can be mocked by specifying the following values for the `subject` parameter when placing an order:
- Success: `subject = SUCCESS` or any other value
- Failure: `subject = FAILED`
- Pending: `subject = PENDING`
:::

### 1.3 Direct API Payment

#### 1.3.1 APM

- Most payment methods **return a `redirectUrl` when placing an order**, redirecting users to the payment page: In the production environment, users are redirected to the external payment page. In the test environment, users are redirected to the payment result selection page.

  - List of payment methods:

| Country | Payment Method Type | Target Institution |
| ------- | ------------------- | ------------------ |
| ID      | WALLET              | LINKAJA            |
| ......  |                     |                    |

![](https://img-cdn-sg.payermax.com/public/20250528-4123fec0-b950-4957-ba5f-d3d7a172829f.png)

- **Returns a `qrCode` when placing an order**:

  - List of payment methods:

| Country | Payment Method Type | Target Institution |
| ------- | ------------------- | ------------------ |
| ID      | BANK_TRANSFER       | BCA/BRI/BTPN...    |
| BR      | REALTIME_PAYMENT    | PIX                |
| SG      | REALTIME_PAYMENT    | PAYNOW             |
| PH      | REALTIME_PAYMENT    | QRPH               |

  - Mocking scheme: Returns a QR code when placing an order. The payment result depends on the `subject` parameter (`subject = SUCCESS` or `subject = FAILED`).

- **Returns a `vaCode` when placing an order**:

  - List of payment methods:

| Country | Payment Method Type | Target Institution |
| ------- | ------------------- | ------------------ |
| TW      | BANK_TRANSFER       | YUSHANBANK/...     |
| TW      | OTC                 | 7-ELEVEN/......    |

  - Mocking scheme: Returns a VA code normally. The payment result depends on the `subject` parameter (`subject = SUCCESS` or `subject = FAILED`).

### 1.4 Front-end Components

Please refer to [1.1 General Rules for Direct Card Payments](https://docs.payermax.com/en/202606-version/receipt/test-cases.md#_1-1-general-rules-for-direct-card-payments).

### 1.5 Tokenization Payments

- When a user makes their first payment and tokenization is returned:

  - Checkout Payment: Please refer to [1.2 Cashier Payment and PayByLink](https://docs.payermax.com/en/202606-version/receipt/test-cases.md#_1-2-cashier-payment-and-paybylink).

  - Pure API Payment: Please refer to [1.3 Direct API Payment](https://docs.payermax.com/en/202606-version/receipt/test-cases.md#_1-3-direct-api-payment).

- For subsequent payments:

  - Please refer to [1.3 Direct API Payment](https://docs.payermax.com/en/202606-version/receipt/test-cases.md#_1-3-direct-api-payment).

## 2. User Account Information Simulation

### 2.1 APM

The account information must meet the format requirements. Some examples are provided below, and others can be found online.

| Email                              | Brazil                                                        | Egypt                                                   | Chile         |
| ---------------------------------- | ------------------------------------------------------------- | ------------------------------------------------------- | ------------- |
| Any valid email: Example@gmail.com | CPF (11 digits): 12345678909 CNPJ (14 digits): 12345678000195 | Mobile Number (11 digits starting with 01): 01234567899 | CI: 123456785 |

### 2.2 Card

For card payments, the following test card numbers can be used in the test environment:

| **Visa**            | **Master**          | **JCB**          | **Discover**          | **DinersClub**          |
|---------------------|---------------------|---------------------|---------------------|---------------------|
| Card Number: 4444333322221111 | Card Number: 5555555555554444 | Card Number: 2131 4324 2974 3027 | Card Number: 6011000000000012 | Card Number: 30569309025904 |
| Name: James Smith      | Name: Allen Black      | Name: James Smith      | Name: James Smith      | Name: James Smith      |
| Expiry Year: 30            | Expiry Year: 26            | Expiry Year: 30            | Expiry Year: 30            | Expiry Year: 30            |
| Expiry Month: 03            | Expiry Month: 11            | Expiry Month: 03            | Expiry Month: 03            | Expiry Month: 03            |
| CVV: 123             | CVV: 357             | CVV: 123             | CVV: 123             | CVV: 123             |

| **Saudi Mada**          | **Kuwait Knet**         | **Qatar Naps**         | **Bahrain Benefit**       | **Pakistan**            |
|---------------------|---------------------|---------------------|---------------------|---------------------|
| Card Number: 5297412542005689 | Card Number: 4507785555554449 | Card Number: 4215375500883243 | Card Number: 5326774027281753 | Card Number: 4919713330643198 |
| Name: William Harris   | Name: Jacob Thomas     | Name: Olivia Taylor    | Name: Brown Jenny      | Name: Patric berg      |
| Expiry Year: 30            | Expiry Year: 26            | Expiry Year: 26            | Expiry Year: 30            | Expiry Year: 2027          |
| Expiry Month: 05            | Expiry Month: 11            | Expiry Month: 06            | Expiry Month: 08            | Expiry Month: 06            |
| CVV: 350             | CVV: 357             | CVV: 123             | CVV: 927             | CVV/CVC: 135         |

| **Uzbekistan Humo**          | **Uzbekistan UZCARD**         | **Brazil Elo**         |
|---------------------|---------------------|---------------------|
| Card Number: 9860133336475222 | Card Number: 8600480114230171 | Card Number: 5067058340733606 | 
| Name: William Harris   | Name: Jacob Thomas     | Name: Olivia Taylor    |
| Expiry Year: 30            | Expiry Year: 30            | Expiry Year: 30            | 
| Expiry Month: 03            | Expiry Month: 03            | Expiry Month: 03            | 
| CVV: 123             | CVV: 123             | CVV: 123             |

### 2.3 ApplePay

- Merchants should create a sandbox Apple account for development. Refer to the [official documentation](https://developer.apple.com/cn/apple-pay/sandbox-testing/).

- Select Apple Pay at the checkout to launch the payment form.

- After authorizing and completing the payment via Apple Pay, the payment result is returned based on the `subject` field. For details, refer to [ApplePay Sandbox Testing Process](https://img-cdn-sg.payermax.com/public/20250529-53286836-207f-4c9c-9746-b1bfcb84bf5d.pdf).

::: warning Note: Apple Pay is supported under the following conditions (subject to the official ApplePay documentation):
- On Safari browsers of Apple devices (MacBook, iPad, iPhone, etc.).
- Within Apple's own webview kernel.
:::

### 2.4 GooglePay

- Select Google Pay at the checkout to launch the payment form.

- Log in to your Google Pay account on the payment form. You can add your Gmail account to the Google Pay test card suite (https://groups.google.com/g/googlepay-test-mode-stub-data) for payment simulation.

- After authorizing and completing the payment via Google Pay, the payment result (success or failure) is returned based on the `subject` field. For details, refer to [GooglePay Test Environment Simulation Process](https://img-cdn-sg.payermax.com/public/20250528-443892ae-ee63-4c25-85da-6fa43fd6c31a.pdf).

::: warning Note:
Google Pay cannot be launched within a WebView. Please use the default browser.
:::

## 3. API Refund Request Simulation

- Success: Any amount except for the fixed amounts listed below.

- Failure - Fixed Amounts (Local Currency): 10000 or 102 (refund failure callback will be triggered after approximately 1 minute).

- Pending - Fixed Amounts (Local Currency): 20000 or 202.