Map three currencies before choosing a price
Source facts: Stripe distinguishes the customer's payment-method currency, such as the currency of a credit card or bank account; the charge currency, called presentment currency; and the currency accepted by the destination bank account or debit card, called settlement currency.[3] These are different roles, even when their currency codes happen to match. Editorial recommendation: start a currency decision record with three separate fields rather than one ambiguous field called currency. Record the intended customer funding currency only when it is actually known, the currency you intend to charge, and the intended settlement destination. Treat unknown customer funding details as unknown rather than deriving them from a website language. This guide addresses currency-selection architecture for eligible Stripe account countries and supported payment methods, not universal availability. Verified 2026-09-20; the source does not specify a publication date.
Locate the customer-side mismatch
Source facts: when the charge currency differs from the customer's payment-method currency, the customer's bank or card issuer might charge that customer a foreign-exchange fee.[3] Editorial recommendation: compare the first two fields separately from your merchant settlement decision. In a hypothetical eligible card flow, a customer with a EUR-denominated card paying a USD charge has a customer-side currency mismatch; changing your own payout destination does not change those two labels. The example illustrates the comparison, not a guaranteed fee or a verified transaction. Explain the possibility of issuer-side costs without claiming to know a particular cardholder's conversion rate. Stripe's wording is conditional, so neither a mismatch nor its absence establishes a universal customer fee schedule. Ask customers to consult their own issuer for issuer-specific charges rather than presenting merchant pricing as the issuer's tariff.
Do not equate matching currencies with a domestic payment
Source facts: a customer's bank or card issuer might also charge the customer when the payment method and the business are in different countries, regardless of the currency used.[3] Editorial recommendation: keep geography as a separate review field instead of treating a shared currency as proof of a domestic transaction. A hypothetical EUR charge funded by a EUR card still requires a separate country comparison; this example makes no assertion that any specific issuer will charge a fee. Avoid checkout wording such as no international fees merely because you charge in the customer's funding currency. A more careful explanation separates the charge currency you control from fees that the customer's institution may apply. This distinction also keeps support conversations focused: matching currency codes do not, by themselves, disprove a customer's report of an issuer charge.
Locate the merchant-side conversion
Source facts: if the charge currency differs from the settlement currency, Stripe converts the charge to the settlement currency.[3] The documentation points to Stripe pricing for conversion costs rather than specifying a universal conversion rate on this page.[3] Editorial recommendation: compare the second and third fields independently of the customer-side comparison. Assuming an eligible configuration, a EUR-funded customer paying a EUR charge that settles in USD has matching customer and charge currencies but a different merchant settlement currency. Conversely, a EUR-funded customer paying a USD charge that settles in USD has a customer-side mismatch without that charge-to-settlement mismatch. These are explanatory scenarios, not promises about total fees, exchange rates, or account eligibility. Do not describe every foreign-exchange cost as a Stripe charge: identify which side of the payment is being discussed before estimating a cost or assigning an owner to investigate it.
Check eligibility before adding a settlement destination
Source facts: Stripe says settlement in additional currencies may be supported in certain countries; where supported, businesses needing liquidity in those currencies can enable that settlement and add a bank account in Dashboard payout settings.[3] Additional payment-method availability also depends on the Stripe account's country.[3] Editorial recommendation: evaluate a proposed currency route as a combination of account country, payment method, charge currency, and supported settlement destination. Do not assume that a bank account capable of holding a currency is sufficient proof that your Stripe configuration can settle into it. Before adopting an additional settlement currency, identify the actual business need, such as planned spending in that currency, and confirm current account-specific support and pricing. Those are decision criteria, not a claim that every merchant should maintain multiple currency balances or that additional settlement currencies eliminate all costs.
Keep integration terminology and platform scope explicit
Source facts: Stripe defines integration currency as the currency set on a Price or PaymentIntent; it appears in Dashboard and is used by Stripe Tax when recording tax liability in its reports.[3] The same page flags additional currency-conversion considerations for Connect platforms and directs them to dedicated Connect documentation.[3] Editorial recommendation: add the integration currency to the implementation handoff as a named field, without replacing the three-role map with it or inventing a fourth conversion event. If another currency-localization feature participates in the flow, document its actual behavior before assuming every visible currency label means the same thing. For a Connect business, stop short of treating this general guide as a complete design for platform and connected-account flows. Escalate those questions to a separate review of the dedicated documentation. The cited page establishes the need for that review, not the full routing behavior of every platform setup.
Use a decision checklist, not a fee guarantee
Editorial decision checklist, not a Stripe-mandated procedure: first, name the target account country and intended payment method; second, record known customer funding currency and any uncertainty; third, choose the charge currency deliberately; fourth, confirm an eligible settlement destination; fifth, compare funding versus charge and charge versus settlement separately; sixth, review the payment-method country versus business country; seventh, confirm applicable pricing and approve customer-facing wording. Keep the rationale with the proposed configuration so product, engineering, and finance are discussing the same currency roles. Source boundary: customer-side foreign-exchange fees and cross-border issuer charges are possibilities, while Stripe documents conversion when charge and settlement currencies differ.[3] Do not turn those statements into an exact fee forecast without additional applicable evidence. This checklist is editorial guidance, not an executed test, a product announcement, or a measured claim that choosing a particular currency improves commercial results.
Sources and dates
Verified on 2026-09-20. Source dates distinguish explicitly stated publication and update dates; an unspecified date does not mean the source was published today. This is public-document research, not a live payment test, security audit or accessibility certification. Vendor facts apply to the cited vendor; proposed workflows are editorial synthesis.
More new articles
Customer cash balance is not invoice credit—or a wallet →
A saved payment method is not blanket permission to charge later →
All field guides →