# Regional considerations Learn about regional considerations for integrating Terminal in different countries. ​​For the most part, you’ll be able to use a single Terminal integration in all supported countries. However, due to local payment methods or regulations there are some country-specific requirements. After going through the [sample integration](https://docs.stripe.com/terminal/quickstart.md), use this guide to learn about country-specific requirements for Terminal. > To process Terminal payments, both the Stripe account receiving the funds and the [location](https://docs.stripe.com/terminal/fleet/locations-and-zones.md) associated with the reader must be in the same country, accepting local currency only. ## Availability Refer to the following table to understand which readers you can use in each country. | Country | [Smart readers](https://docs.stripe.com/terminal/smart-readers.md) | [Mobile readers](https://docs.stripe.com/terminal/mobile-readers.md) | [Tap to Pay](https://docs.stripe.com/terminal/payments/setup-reader/tap-to-pay.md) | | ----------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------- | ---------------------------------------------------------------------------------- | | US | - BBPOS WisePOS E - Stripe Reader S710 - Stripe Reader S700 - Verifone readers (Public preview) | - Stripe Reader M2 | - Tap to Pay on Android - Tap to Pay on iPhone | | - AU - BE - NZ | - BBPOS WisePOS E - Stripe Reader S710 - Stripe Reader S700 | - BBPOS WisePad 3 | - Tap to Pay on Android - Tap to Pay on iPhone | | CA | - BBPOS WisePOS E - Stripe Reader S710 - Stripe Reader S700 - Verifone readers (Public preview) | - BBPOS WisePad 3 | - Tap to Pay on Android - Tap to Pay on iPhone | | - IE - GB | - BBPOS WisePOS E - Stripe Reader S710 - Stripe Reader S700 - Verifone V660p, UX700, P630 (Private preview) | - BBPOS WisePad 3 | - Tap to Pay on Android - Tap to Pay on iPhone | | SG | - BBPOS WisePOS E - Stripe Reader S710 - Stripe Reader S700 - Verifone V660p, P630 (Private preview) | - BBPOS WisePad 3 | - Tap to Pay on Android - Tap to Pay on iPhone | | - AT - CZ - DK - FI - FR - IT - LU - NL - NO - PL - PT - ES - SE - CH | - BBPOS WisePOS E - Stripe Reader S710 - Stripe Reader S700 | - BBPOS WisePad 3 | - Tap to Pay on Android - Tap to Pay on iPhone | | DE | - BBPOS WisePOS E - Stripe Reader S700 | - BBPOS WisePad 3 | - Tap to Pay on Android - Tap to Pay on iPhone | | JP | - Stripe Reader S700 | - BBPOS WisePad 3 | - Tap to Pay on iPhone | | MY | - BBPOS WisePOS E - Stripe Reader S710 - Stripe Reader S700 | - BBPOS WisePad 3 | - Tap to Pay on Android - Tap to Pay on iPhone (Public preview) | | - LI - CY - EE - HR - LT - LV - MT - SI - SK - HU - RO - BG | | | - Tap to Pay on Android - Tap to Pay on iPhone | | - GI | | | - Tap to Pay on Android | ## Regional considerations by country Select a country to view its specific regional considerations # France (FR) ## Integrate Terminal in France Stripe supports Visa, Mastercard, American Express, Discover, and Cartes Bancaires payments in France. All transactions must be made in euros (EUR). To accept Terminal charges in France, either your platform account or connected account must be in France. ### Reader software version BBPOS WisePad 3 readers operating in France must use the reader software version `4.01.04.00_FR_v26_511001` or later. Read about [BBPOS WisePad 3 software updates](https://docs.stripe.com/terminal/payments/connect-reader.md?reader-type=bluetooth#update-reader) for details. ## Cartes Bancaires payments Cartes Bancaires is the interbank network that handles routing of debit payments in France. Consumer debit cards in France are branded with a Cartes Bancaires logo and might also be co-badged with Visa or Mastercard. You can process these cards using either Cartes Bancaires or the international network. Terminal supports processing Cartes Bancaires cards by insert or NFC-based mechanisms, such as tap and mobile wallets (Apple Pay, Google Pay, and Samsung Pay). ### Enable Cartes Bancaires French Stripe accounts can process Cartes Bancaires payments after providing their business tax ID in the Dashboard settings. If you’re a Connect platform, and your connected accounts don’t have access to the full Stripe Dashboard (includes Express and Custom accounts) you must request the `cartes_bancaires_payments` [capability](https://docs.stripe.com/connect/account-capabilities.md#payment-methods) on behalf of your connected accounts. ### Integration requirements To accept Cartes Bancaires payments, you must use: - [BBPOS WisePad 3](https://stripe.com/fr/terminal/wisepad3) reader - [Stripe Reader S700](https://stripe.com/fr/terminal/s700) - [Stripe Reader S710](https://stripe.com/fr/terminal/s710) - [Tap to Pay on Android](https://docs.stripe.com/terminal/payments/setup-reader/tap-to-pay.md?platform=android) - [Tap to Pay on iPhone](https://docs.stripe.com/terminal/payments/setup-reader/tap-to-pay.md?platform=ios) If you use the BBPOS WisePad 3 reader, you must use the following minimum Terminal SDK versions: - [iOS SDK](https://github.com/stripe/stripe-terminal-ios/releases) 3.2.0: Released on 17 November 2023 - [Android SDK](https://github.com/stripe/stripe-terminal-android/releases) 3.2.0: Released on 17 November 2023 - [React Native SDK](https://github.com/stripe/stripe-terminal-react-native/releases) v0.0.1-beta.14: Released on 6 December 2023 The minimum supported SDK versions for Tap to Pay are: - Tap to Pay on Android: [Android SDK](https://github.com/stripe/stripe-terminal-android/releases) 5.2.0 - Tap to Pay on iPhone: [iOS SDK](https://github.com/stripe/stripe-terminal-ios/releases) 4.6.0 If you use the Terminal [JavaScript SDK](https://docs.stripe.com/terminal/payments/setup-integration.md?terminal-sdk-platform=js) or [server-driven integration](https://docs.stripe.com/terminal/payments/setup-integration.md?terminal-sdk-platform=server-driven), you don’t need to make any changes. The [BBPOS WisePOS E](https://stripe.com/fr/terminal/wisepose) reader doesn’t support the Cartes Bancaires network, and processes transactions from co-badged cards through only the international network. ### Routing co-badged debit cards Co-badged Cartes Bancaires cards support both Cartes Bancaires and international card networks. If your integration supports Cartes Bancaires, you can choose to process the payment directly through Cartes Bancaires or through the international network. When you create a PaymentIntent, specify your choice in the [requested_priority](https://docs.stripe.com/api/payment_intents/create.md#create_payment_intent-payment_method_options-card_present-routing-requested_priority) parameter. [SetupIntents](https://docs.stripe.com/payments/setup-intents.md), which collect card details without charging the card, always process using the international network. | Routing | Setting | Result | | ---------------------- | -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------- | | Cartes Bancaires | Set `requested_priority` to `domestic`. | - Co-badged Cartes Bancaires cards prioritize the Cartes Bancaires network. - All other cards process normally. | | International networks | Set `requested_priority` to `international`. | - Co-badged Cartes Bancaires cards prioritize the international network. - All other cards process normally. | Stripe Terminal provides default support for [compliance with customer card brand choice](https://docs.stripe.com/co-badged-cards-compliance.md) on the [BBPOS WisePad 3](https://stripe.com/fr/terminal/wisepad3), [Stripe Reader S700](https://stripe.com/fr/terminal/s700), and [Stripe Reader S710](https://stripe.com/fr/terminal/s710) readers. Customers who use a co-badged Cartes Bancaires card on a supported device can override your priority selection and choose their preferred network routing option, as shown in the following image. ![An application selection screen showing two card brands, one with Cartes Bancaires (CB) and the other Visa, on the WisePad 3 device.](https://b.stripecdn.com/docs-statics-srv/assets/wisepad-cartes-bancaires-account-selection.2fd265691dfd796993dacff5b16c95bc.png) BBPOS WisePad 3 ![An application selection screen showing two card brands, one with Cartes Bancaires (CB) and the other Visa, on the Stripe Reader S700/S710 device.](https://b.stripecdn.com/docs-statics-srv/assets/s700-cartes-bancaires-selection-screen.a31c1b71a4952564fd49e19482b70f7c.png) Stripe Reader S700/S710 If you use [Tap to Pay on iPhone](https://docs.stripe.com/terminal/payments/setup-reader/tap-to-pay.md?platform=ios) to accept payments on co-badged cards, your integration must facilitate [card brand choice](https://docs.stripe.com/co-badged-cards-compliance.md) by allowing customers to select their preferred network at any point before initiating the tap. You must also pass the relevant [requested_priority](https://docs.stripe.com/api/payment_intents/create.md#create_payment_intent-payment_method_options-card_present-routing-requested_priority) to Stripe before the customer initiates the tap. ### Refund a Cartes Bancaires payment You can refund Cartes Bancaires payments through the [API](https://docs.stripe.com/refunds.md?dashboard-or-api=api) or [Dashboard](https://docs.stripe.com/refunds.md?dashboard-or-api=dashboard). Refunds don’t require the cardholder to present their card again at the point of sale. ### Identify the network To identify which network a payment was processed on, inspect the [network](https://docs.stripe.com/api/charges/object.md#charge_object-payment_method_details-card-network) value of the [Charge](https://docs.stripe.com/api/charges/object.md) object associated with a successful [PaymentIntent](https://docs.stripe.com/api/payment_intents/object.md). ```javascript { "id": "ch_1Ff52K2eZvKYlo2CWe10i0s7", "object": "charge", ... "payment_method_details": { "card_present": { "brand": "visa", ..."network": "cartes_bancaires", }, "type": "card_present" } } ``` ### Provide receipts For Cartes Bancaires payments, Stripe includes additional metadata in the [prebuilt receipts](https://docs.stripe.com/terminal/features/receipts.md#prebuilt). For [custom receipts](https://docs.stripe.com/terminal/features/receipts.md#custom), the following required fields are available in the PaymentIntent as soon as the payment is [confirmed](https://docs.stripe.com/terminal/payments/collect-card-payment.md#confirm-payment). | Field | Description | | --------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `transaction_trace_number` | The transaction number generated by the acceptance system. | | `siret_number` | The [système d’identification du répertoire des établissements (establishment directory identification system)](https://support.stripe.com/questions/siren-and-siret-numbers) code assigned to the business. | | `bank_code` | The code for the bank that issued the card. | | `acceptor_identifier` | The acceptor identifier. | | `acceptance_system_terminal_application_identifier` | The identifier for the terminal application used to process the transaction. | | `card_acceptor_logical_number` | The logical number of the card acceptance point. | | `system_acceptor_logical_number` | The logical number of the acceptance system. | ## Use locations Create [Locations](https://docs.stripe.com/api/terminal/locations/create.md) for your business with addresses in FR and [associate your readers to them](https://docs.stripe.com/terminal/fleet/locations-and-zones.md). This will ensure that they automatically download the configuration needed to properly process charges in FR. A valid [address for a Location](https://docs.stripe.com/api/terminal/locations/create.md#create_terminal_location-address) in FR must contain the properties. #### curl ```bash curl https://api.stripe.com/v1/terminal/locations \ -u <>: \ -d "display_name"="HQ" \ -d "address[line1]"="19 Rue de Vienne" \ -d "address[city]"="Paris" \ -d "address[country]"="FR" \ -d "address[postal_code]"="75008" \ ``` ## Translation Language regulations require that services, including point-of-sale services, be provided in French unless English has been agreed upon by the cardholder and their card issuer. Terminal is built to help you comply with these requirements if they apply to your business. #### Default reader language The [BBPOS WisePOS E](https://docs.stripe.com/terminal/readers/bbpos-wisepos-e.md) and [Stripe Reader S700/S710](https://docs.stripe.com/terminal/readers/stripe-reader-s700-s710.md) support changing reader language in the Settings panel. Swipe right across the screen to access the Settings panel, and select your language. The [BBPOS WisePad 3](https://docs.stripe.com/terminal/readers/bbpos-wisepad3.md) supports changing reader language directly in the reader interface. After you have registered your reader to a [Location](https://docs.stripe.com/api/terminal/locations.md) with an address in FR, the reader installs a language pack relevant for your region if one isn’t already in place. To view available language options and to select a language, click the **Power / Settings** button and scroll down using the arrow keys until you reach the language selection menu. Highlight your desired language and press the green **Enter** key. #### Other translations If you’re required to provide services in or would like to translate text into French in addition to English, ensure that any of your [custom reader screens](https://docs.stripe.com/terminal/features/display.md) and [receipts](https://docs.stripe.com/terminal/features/receipts.md) display the appropriate translations. ## Strong Customer Authentication *Strong Customer Authentication* (Strong Customer Authentication (SCA) is a regulatory requirement in effect as of September 14, 2019, that impacts many European online payments. It requires customers to use two-factor authentication like 3D Secure to verify their purchase) (SCA) is a European regulatory requirement to reduce fraud and make payments more secure. SCA is or will be required for *customer-initiated* electronic payments within the *European Economic Area* (The European Economic Area is a regional single market with free movement of labor, goods, and capital. It encompasses the European Union member states and three additional states that are part of the European Free Trade Association) (EEA). For more information about this European regulation, you can read Stripe’s [PSD2: SCA guide](https://stripe.com/guides/strong-customer-authentication). Transactions below 50 euros (or the local currency equivalent) are considered *low value* and might be exempted from SCA. However, banks need to request authentication if the *low value* exemption has been used five times since the cardholder’s last successful authentication or if the sum of previously exempted payments exceeds 150 euros (or the local currency equivalent). In FR, all transactions authenticated with a PIN satisfy the SCA requirements. The card represents the first authentication element of the transaction (possession) and the PIN represents the second (knowledge). Some contactless cards might support PIN validation with a single tap; however, others might require initiating an authenticated Chip and PIN contact transaction to comply with the SCA requirements, which requires inserting the card into the reader. When using Terminal hardware, the reader prompts the customer to enter their PIN or insert their card for a chip-and-PIN transaction. You see two charges associated with SCA-authenticated transactions. The first is a soft-declined charge with an error message `online_or_offline_pin_required` or `offline_pin_required`, depending on the card’s capabilities. The second is the authorized or hard-declined charge. When using Tap to Pay, the device prompts the customer to enter their PIN if contactless PIN validation is supported. If contactless PIN is supported, you see two charges associated with SCA-authenticated transactions. The first is a soft-declined charge with an error message `online_or_offline_pin_required`. The second is the authorized or hard-declined charge. If contactless PIN isn’t supported, the payment will be hard-declined before the PIN screen appears, with the reason `online_or_offline_pin_required` or `offline_pin_required`. If the card is hard-declined we recommend asking the customer to try a different card or collecting payment in a different way. For example, by sending a [Payment Link](https://docs.stripe.com/payment-links.md).