Adaptive Pricing

Adaptive Pricing is always enabled for Payment Links. Manage Adaptive Pricing for Checkout in your payment settings in the Dashboard. You can enable Adaptive Pricing in a sandbox and live mode. Disabling Adaptive Pricing doesn’t affect Checkout Sessions that have already been converted.

Adaptive Pricing can increase the usage of local payment methods by ensuring customers have the option to pay in their local 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. You can configure which payment methods you accept in your payment methods settings if you use dynamic payment methods. Adaptive Pricing unlocks access to the following payment methods that require presenting in local currency:

• Bancontact
• EPS
• iDEAL
• Link
• P24

Adaptive Pricing can affect some parts of your integration, such as event destinations and reporting. Review your integration to make sure any event destinations can handle PaymentIntent objects with local currencies.

• Use the Checkout Session object’s currency and total amount to determine what your customer paid in your integration currency, which is the currency you specified for your prices.
• Use the presentment_details hash on the Checkout Session object to determine what your customer paid in their local currency.

The Checkout Session and the underlying PaymentIntent objects reflect your integration currency and amount.

If a customer pays in their local currency, the checkout.session.completed event contains a presentment_details hash that includes the presentment_amount, presentment_currency. The amount and currency reflect what your customer paid in the local currency.

{
  "id": 
'{{EVENT_ID}}',
  "object": "event",
  "type": "checkout.session.completed",
  "data": {
    "object": {
      "id": 
'{{SESSION_ID}}',
      "object": "checkout.session",
      "currency": "usd",
      "amount_total": 1000,
      "amount_subtotal": 1000,
      "presentment_details": {
        "presentment_amount": 1370,
        "presentment_currency": "cad"
      }
    }
  }
}

To test local currency presentment for Checkout and Payment Links, 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 or Payment Link 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_BQokikJOvBiI2HlWgH4olfQ2: \
  -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="test+location_FR@example.com"

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.

Adaptive Pricing is currently not available for businesses using Connect or Elements with the Payment Intents API.

Additionally, Adaptive Pricing requires the currency for your prices to be one of your settlement currencies. 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 doesn’t 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.
• Use custom amounts.

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