# 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 # Germany (DE) ## Integrate Terminal in Germany Stripe supports Visa, Mastercard, American Express, Discover, and girocard payments in Germany. All transactions must be made in euros (EUR). To accept Terminal charges in Germany, either your platform account or connected account must be in Germany. ## girocard payments [girocard](https://www.girocard.eu/) is an interbank network that handles routing of debit card payments in Germany. Most consumer debit cards in Germany are branded with a girocard logo and co-badged with Visa or Mastercard (or their sub-brands like V-Pay or Maestro). You can process these cards over either supported network. ### Integration requirements To accept girocard payments, you must use one of the following readers: - [BBPOS WisePad 3](https://stripe.com/de/terminal/wisepad3) with the following minimum Terminal SDK versions: - [iOS SDK](https://github.com/stripe/stripe-terminal-ios/releases) 2.17.0: Released on 31 January 2023 - [Android SDK](https://github.com/stripe/stripe-terminal-android/releases) 2.17.0: Released on 2 February 2023 - [React Native SDK](https://github.com/stripe/stripe-terminal-react-native/releases) 0.0.1-beta.12: Released on 1 June 2023 - [Stripe Reader S700](https://stripe.com/de/terminal/s700) The [BBPOS WisePOS E](https://stripe.com/de/terminal/wisepose) reader doesn’t support girocard. This device can continue to process transactions from co-badged cards with Visa and Mastercard. ### Routing co-badged debit cards Co-badged girocard debit cards support both girocard and international card networks. If your integration supports girocard, then when you create a PaymentIntent you can choose whether to process the payment directly through girocard or the co-badged network. To do so, set the [requested_priority](https://docs.stripe.com/api/payment_intents/create.md#create_payment_intent-payment_method_options-card_present-routing-requested_priority) on the nested `payment_method_options.card_present.routing` attribute for this purpose. | Routing | Implementation | Result | | ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | | girocard | Set [requested_priority](https://docs.stripe.com/api/payment_intents/create.md#create_payment_intent-payment_method_options-card_present-routing-requested_priority) on the nested `payment_method_options.card_present.routing` attribute to `domestic` | For co-badged girocard cards, the girocard network is prioritized. All other cards will be processed as-is. | | International networks | Set [requested_priority](https://docs.stripe.com/api/payment_intents/create.md#create_payment_intent-payment_method_options-card_present-routing-requested_priority) on the nested `payment_method_options.card_present.routing` attribute to `international` | For co-badged girocard cards, the international network is prioritized. All other cards will be processed as-is. | Stripe Terminal also supports customer [card brand choice](https://docs.stripe.com/co-badged-cards-compliance.md) by default to help you meet [applicable requirements](https://docs.stripe.com/co-badged-cards-compliance.md). Customers who insert a co-badged girocard card into a supported device can override your priority selection to exercise choice by selecting their preferred network routing option. ![wisepad-3](https://b.stripecdn.com/docs-statics-srv/assets/wisepad-girocard-account-selection.5458c78bb5e14a2b9685df5790f111da.png) [SetupIntents](https://docs.stripe.com/payments/setup-intents.md), which are used to collect card details without charging the card, are always routed to the international network. This is because girocard doesn’t support [off-session](https://support.stripe.com/questions/what-is-the-difference-between-on-session-and-off-session-and-why-is-it-important) payments initiated by a business. ### Refund a girocard payment You can refund girocard 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). The cardholder isn’t required to present their card again at the point of sale. The girocard network doesn’t natively support refunds. As a workaround, Stripe sends the refund by SEPA transfer to the customer’s bank account, using the IBAN associated with their girocard. To check the status of the transfer, inspect the [Refund](https://docs.stripe.com/api/refunds/object.md) object. Be aware that the refund might fail—for instance, if the customer closes their bank account or the transfer can’t be processed. ### 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": "girocard" }, "type": "card_present" } } ``` ### Use locations Create [Locations](https://docs.stripe.com/api/terminal/locations/create.md) for your business with addresses in DE 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 DE. A valid [address for a Location](https://docs.stripe.com/api/terminal/locations/create.md#create_terminal_location-address) in DE must contain the properties. #### curl ```bash curl https://api.stripe.com/v1/terminal/locations \ -u <>: \ -d "display_name"="HQ" \ -d "address[line1]"="Jarrestrasse 80" \ -d "address[city]"="Hamburg" \ -d "address[country]"="DE" \ -d "address[postal_code]"="22303" \ ``` ### Reader software version BBPOS WisePad 3 readers operating in Germany must use the reader software version `4.01.04.00_DE_v31_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. ### Translation Language regulations require that services, including point-of-sale services, be provided in German 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 DE, 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 German 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 DE, 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).