Adaptive Pricing

Businesses in supported regions can automatically convert prices to the local currencies of their customers in the following markets:

You can configure which payment methods you accept in your payment methods settings.

Adaptive Pricing can increase the usage of local payment methods by ensuring customers have the option to pay in their currency and with payment methods most relevant to them. As an example, 70% of all e-commerce transactions in the Netherlands use iDEAL, but it only works with EUR.

Adaptive Pricing enables the following payment methods:

• Alipay
• Bancontact
• BLIK
• Canadian pre-authorized debit
• EPS
• iDEAL
• PayPal
• P24
• SEPA Debit
• Sofort
• Swish
• WeChat Pay

Currently, Adaptive Pricing doesn’t work with Connect or Elements with the Payment Intents API.

Additionally, Adaptive Pricing requires the currency for your prices to be the same as your default settlement currency. Prices automatically convert during checkout. This applies to prices you create and reference with a price ID and prices you create inline with price_data when you create a Checkout Session.

Adaptive Pricing does not apply for Checkout Sessions that:

• Contain explicitly defined manual currency prices.
• Are in subscription mode.
• Use Connect parameters like application_fee_amount, on_behalf_of, and transfer_data.
• Use capture_method as manual.
• Set the currency value on creation.
• Present the customer a local currency that is also configured as a settlement currency. For example, suppose an account settles in both EUR and GBP. If they price in EUR, customers with local currency GBP don’t see Adaptive Pricing. Customers with a local currency other than EUR or GBP, such as JPY, see Adaptive Pricing.

In Sessions that aren’t supported by Adaptive Pricing, Checkout presents prices in the original currency that you’ve set your prices in.

• You pay 0%
• Your buyers pay 2–4%

Details: You (the business) don’t directly pay any additional fees for Adaptive Pricing, as all such fees are paid for by your customers. Stripe applies a conversion fee of between 2–4% to the exchange rate you present to your customers, increasing their purchase price by a corresponding amount. The fee applied is determined by Stripe and varies for the purposes of increasing customer conversion. Stripe typically charges a fee of 4% for orders under 500 USD, 3% for 500–1,500 USD, and 2% for orders over 1,500 USD. For detailed information about current Stripe fees, see our pricing page.

Stripe uses the mid-market exchange rate and applies a fee to guarantee the rate for the duration of the Checkout Session (up to 24 hours) through settlement. If the exchange rate changes by more than 5% in that time, Stripe might use the updated exchange rate to calculate your payout.

Learn more about how Stripe handles currency conversions and Adaptive Pricing fees.

Stripe pays out refunds in the currency your customer pays in using the latest Stripe-provided exchange rate. This means that you might pay more or less to cover the refund depending on how the exchange rate changes.

Example refund

We ignore Stripe fees in this example for simplicity. Suppose:

1. You’re a US business that uses Checkout to sell a product for 100 USD and have activated Adaptive Pricing.
2. A customer in Canada views your Checkout page, sees the localized price of 137 CAD at an exchange rate of 1.37 CAD per 1 USD, and completes the purchase.
3. Stripe processes the payment, converting the 137 CAD to 100 USD to pay you in your settlement currency.
4. Later, when the exchange rate has changed to 1.40 CAD per 1 USD, you issue a full refund to the customer.
5. Stripe deducts 97.86 USD from your account, exchanging it at 1.40 CAD per 1 USD to pay out the 137 CAD refund.

Learn more about how Stripe helps you manage refunds.

Depending on the user-selected currency, both the Checkout Session and the underlying PaymentIntent objects update automatically to reflect the selected currency and amount. After a user pays in local currency, the Checkout Session object’s currency and total amount is in local currency and contains a currency_conversion hash to reflect what the user would have paid in the default currency. Learn more about what’s deposited in your account after fees.

The checkout.session.completed event contains a currency_conversion hash that includes the amount_total and amount_subtotal in the source_currency. The amounts reflect what your customer would have paid in the source currency.

{
  "id": 
'{{EVENT_ID}}',
  "object": "event",
  "type": "checkout.session.completed",
  "data": {
    "object": {
      "id": 
'{{SESSION_ID}}',
      "object": "checkout.session",
      "currency": "cad",
      "amount_total": 2055,
      "amount_subtotal": 2055,
      "currency_conversion": {
        "amount_subtotal": 1500,
        "amount_total": 1500,
        "source_currency": "usd",
        "fx_rate": "1.37"
      }
    }
  }
}

To test local currency presentment for Checkout, Payment Links, and the pricing table, pass in a location-formatted customer email that includes a suffix in a +location_XX format in the local part of the email. XX must be a valid two-letter ISO country code.

For example, to test currency presentment for a customer in France, pass in an email like test+location_FR@example.com.

When you visit the URL for a Checkout Session, Payment Link, or pricing table created with a location-formatted email, you see the same currency as a customer does in the specified country.

Testing Checkout

When you create a Checkout Session, pass the location-formatted email as customer_email to simulate Checkout from a particular country.

curl https://api.stripe.com/v1/checkout/sessions \
  -u 
sk_test_4eC39HqLyjWDarjtT1zdp7dc: \
  -d "line_items[0][price]"="{{PRICE_ID}}" \
  -d "line_items[0][quantity]"=1 \
  -d mode=payment \
  -d success_url="https://example.com/success" \
  --data-urlencode customer_email="[email protected]"

You can also create a Customer and specify their email that contains the +location_XX suffix. Stripe test cards work as usual.

When it’s possible to present the customer’s local currency in Checkout, the Checkout Session object changes. Fields like currency, payment_method_types, and amount_total reflect the local currency and price.

Testing Payment Links

For Payment Links, pass the location-formatted email as the prefilled_email URL parameter to test currency presentment for customers in different countries.

Testing Pricing table

For the pricing table, pass the location-formatted email as the customer-email attribute to test currency presentment for customers in different countries.