# eMerchantPay V3

{% hint style="danger" %}
Do not create a new eMerchantPay or eMerchantPay V2 gateway. Use only the V3 gateway.
{% endhint %}

<figure><img src="/files/xcZbQjrCGPx9YR6wmQbs" alt="" width="375"><figcaption></figcaption></figure>

**Step 1**

Activate the eMerchantPay V3 gateway tile

**Step 2**

Enter eMerchantPay V3 credentials on your account

<figure><img src="/files/Fdn5vHfZbXwjq21FRmtC" alt="" width="375"><figcaption></figcaption></figure>

Enter **username** and **password** from your eMerchantPay account

Check the **enhancedRebill** box to process using eMerchantPay’s new recurring workflow. This workflow passes the recurring\_type parameter.

Obtain tokens from eMerchantPay and enter the values that correspond to your transaction processing requirements.

* **terminalToken3DS** is required when **secure3DS** is set to Yes
* **terminalTokenNon3DS** is required when **secure3DS** is set to No
* **terminalTokenRebill** is required to rebill. It is also required to process upsells using a token (without this upsells will be run with the card).
* **terminalTokenAPM** is required to process Bancontact, giropay, iDEAL, P24, EPS, and Sofort. Enter the name of the payment method, a colon (:), and the terminal token for the payment type. Enter a new line for each type. The final result will look something like this (do not copy this as the tokens in this screenshot are dummy):

<figure><img src="/files/o0BpZlUg0LdSqjE4mhMF" alt=""><figcaption></figcaption></figure>

&#x20;If using ApplePay or GooglePay then include similar for each in **terminalTokenAPM**. These payment methods require a separate entry if rebills will be processed through Apple or Google. However the value may be the same (for example, APPLEPAY and APPLEPAY\_REBILL may be the same token, and there must be an entry for each if recurring transactions are needed).

* APPLEPAY:xxxxxxxxxxxxxxxxxxxx
* APPLEPAY\_REBILL:xxxxxxxxxxxxxxxxxxxx
* GOOGLEPAY:xxxxxxxxxxxxxxxxxx
* GOOGLEPAY\_REBILL:xxxxxxxxxxxxxxxxxx

**Step 3**

{% hint style="info" %}
browserData must be passed from the page on orders. Below is one option to do that. If using hosted CheckoutChamp pages then this section can be skipped.
{% endhint %}

Please follow the below instructions to setup eMerchantPay on your checkout page and pass browserData on the Import Order API call

Add a hidden input for `browserData`.

```
<input type="hidden" name="browserData" value="" id="browserData">
```

Add below script before the closing “body” tag.

```
<script type="text/javascript">
    const navigator = window.navigator;
    const browserData = {
        acceptHeader: 'application/json',
        userAgent: navigator.userAgent,
        language: navigator.language,
        timezone: (new Date()).getTimezoneOffset().toString(),
        colorDepth: screen.colorDepth,
        screen: {
            height: screen.height.toString(),
            width: screen.width.toString()
        },
        javaScriptEnabled: true,
        javaEnabled: navigator.javaEnabled()
    };
    document.getElementById('browserData').value = JSON.stringify(browserData);
</script> 
```

For **secure3DS** your checkout and upsale pages must support standard merchant redirect handling

[Basic 3DS Instructions](/crm/gateway-setup/direct-api-3ds-instructions.md)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.checkoutchamp.com/crm/gateway-setup/gateway-integrations/emerchantpay-v3.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.