> For the complete documentation index, see [llms.txt](https://help.checkoutchamp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.checkoutchamp.com/crm/gateway-setup/gateway-integrations/emerchantpay-v3/emerchantpay-alternate-payments.md).

# eMerchantPay - Alternate Payments

{% hint style="info" %}
The eMerchantPay gateway supports multiple alternative payment options

* Bancontact
* EPS
* P24
  {% endhint %}

{% hint style="danger" %}
**Disclaimers:**

No card details are stored for merchants using alternative payment options

These payments will work with Checkout Champ pages and landers that connect to Checkout Champ via Direct API. This will NOT work with Order Entry.

Alternate payment options are one-time use. There is no recurring billing.

Alternate payment options do not support and auth/capture workflow.
{% endhint %}

**STEP 1**

Go to **Gateways** | **Gateway Integrations** and select eMerchantPay. Click on **+Activate**. Follow instructions [here ](/crm/gateway-setup/gateway-integrations/emerchantpay-v3.md)for setup.

Click the green **Create Gateway** button to save your changes and create the gateway. Note the ID of the gateway on the gateway list page, for use in Step 2.

&#x20;

**STEP 2**

The checkout page must be secure HTTPS. A non-secured call will be rejected. Pass the following parameters on the Import Order or Import Upsale API calls

* paySource = PREPAID
* forceMerchantId = the eMerchantPay id from Step 1
* redirectsTo = the url where the browser should redirect on a successful transaction
* errorRedirectsTo = the url where the browser should redirect on a failed transaction

Then include the **prepaidType** parameter based on the payment option

* Bancontact
  * prepaidType = BANCONTACT
* EPS
  * prepaidType = EPS
* P24
  * prepaidType = P24

{% hint style="info" %}
Your checkout and upsale pages must support standard merchant redirect handling

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

{% hint style="info" %}
For more info on the API calls, refer to our [API Documentation.](https://apidocs.checkoutchamp.com)
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
