# Stripe  - Alternate Payments

{% hint style="info" %}
The Stripe V2 gateway supports multiple alternate payment options

* Afterpay
* Alipay
* Amazon Pay
* Bancontact
* BLIK
* EPS
* FPX
* iDEAL
* KakaoPay
* Klarna
* MobilePay
* Naver Pay
* P24
* PayPay
* Revolut Pay
* Satispay
* SEPA
* Swish
* TWINT
* WeChat Pay
  {% endhint %}

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

No card details are stored for merchants using Stripe’s alternate payment options

SEPA, iDEAL, Bancontact, Klarna, KakaoPay, Naver Pay, Amazon Pay, and Revolut Pay support recurring billing/subscriptions. All other options will only work for one-time purchases and will NOT work for recurring billing/subscriptions.

SEPA, iDEAL, Bancontact, Klarna, KakaoPay, Naver Pay, Amazon Pay, and Revolut Pay support one-click upsells (using the original payment token on each upsell). All other options require the consumer to go through the full checkout again.

These payments will work with Checkout Champ hosted pages or sites that connect via Direct API. This will NOT work with form-code or via Order Entry.
{% endhint %}

**STEP 1**

Go to **Gateways** | **Gateway Integrations** and select StripeV2. Click on **+Activate**. Follow instructions [here ](/crm/gateway-setup/gateway-integrations/stripe.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.\ <br>

**STEP 2**

{% hint style="danger" %}
Step 2 is not relevant if using Checkout Champ hosted pages. The payment options are built into the application. Drag the appropriate button(s) to your checkout page.
{% endhint %}

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 call

* paySource = PREPAID
* forceMerchantId = the Stripe V2 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

* Afterpay
  * prepaidType = AFTERPAY
* Alipay
  * prepaidType = ALIPAY
* Amazon Pay
  * prepaidType = AMAZONPAY
* Bancontact
  * prepaidType = BANCONTACT
* BLIK
  * prepaidType = BLIK
* iDEAL
  * prepaidType = IDEAL
* EPS
  * prepaidType = EPS
* FPX
  * prepaidType = FPX
* KakaoPay
  * KAKAOPAY
* Klarna
  * prepaidType = KLARNA
* Naver Pay
  * prepaidType = NAVERPAY
* P24
  * prepaidType = P24
* PayPay
  * prepaidType = PAYPAY
* Revolut Pay
  * prepaidType = REVOLUTPAY
* Satispay
  * prepaidType = SATISPAY
* SEPA
  * prepaidType = SEPA\_DEBIT
* Swish
  * prepaidType = SWISH
* TWINT
  * prepaidType = TWINT
* MobilePay
  * prepaidType = MOBILEPAY
* WeChat Pay
  * prepaidType = WECHATPAY

{% 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: 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/stripe/stripe-alternate-payments.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.