# 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 # United Kingdom (GB) ## Integrate Terminal in the United Kingdom Stripe supports Visa, Mastercard, American Express, and Discover payments in the United Kingdom. All transactions must be made in British pounds (GBP). To accept Terminal charges in United Kingdom, either your platform account or connected account must be in United Kingdom. ### Use locations Create [Locations](https://docs.stripe.com/api/terminal/locations/create.md) for your business with addresses in GB 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 GB. A valid [address for a Location](https://docs.stripe.com/api/terminal/locations/create.md#create_terminal_location-address) in GB must contain the properties. #### curl ```bash curl https://api.stripe.com/v1/terminal/locations \ -u <>: \ -d "display_name"="HQ" \ -d "address[line1]"="448A Crownhill Rd" \ -d "address[city]"="Plymouth" \ -d "address[country]"="GB" \ -d "address[postal_code]"="PL5 2QT" \ ``` ### Reader software version BBPOS WisePOS E readers operating in the United Kingdom must use the reader software version `1.5.0.0` or later. Read about [BBPOS WisePOS E software updates](https://docs.stripe.com/terminal/readers/bbpos-wisepos-e.md#reader-software-version) for details. Similarly, BBPOS WisePad 3 readers must use the reader software version `4.01.04.00_Prod_EU_W1_off_v23_510001` 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. ### 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 GB, contact transactions authenticated with a PIN satisfy the SCA requirements. The chip represents the first authentication element of the transaction (possession) and the PIN represents the second (knowledge). Contactless card transactions, however, might require initiating an authenticated Chip and PIN contact transaction to comply with the SCA requirements. When using Terminal hardware, the reader prompts the customer to insert their card for a chip-and-PIN transaction. You see two charges associated with these transactions if the customer re-enters their card. The first is a soft-declined charge with an `offline_pin_required` decline message and `contactless_emv` read method. The second is the authorized or hard-declined charge with `contact_emv` read method. 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).