Skip to content
Create account
or
Sign in
The Stripe Docs logo
/
Ask AI
Create account
Sign in
Get started
Payments
Revenue
Platforms and marketplaces
Money management
Developer resources
Overview
About Stripe payments
Upgrade your integration
Payments analytics
Online payments
OverviewFind your use caseManaged Payments
Use Payment Links
Build a checkout page
Build an advanced integration
Build an in-app integration
Payment methods
Add payment methods
Manage payment methods
Faster checkout with Link
Payment interfaces
Payment Links
Checkout
Web Elements
In-app Elements
Payment scenarios
Handle multiple currencies
Custom payment flows
Flexible acquiring
Orchestration
In-person payments
Terminal
    Overview
    Accept in-person payments
    Integration design
    Select your reader
    Design an integration
    Quickstart
    Example applications
    Testing
    Terminal setup
    Set up your integration
    Connect to a reader
    Accepting a payment
    Collect card payments
    Additional payment methods
    Accept offline payments
    Mail order and telephone order payments
    Regional considerations
    During checkout
    Collect tips
    Collect and save payment details for future use
    Flexible authorizations
    After checkout
    Refund transactions
    Provide receipts
    Customize checkout
    Cart display
    Collect on-screen inputs
    Collect swiped data
    Collect tapped data for NFC instruments
    Apps on devices
    Manage readers
    Order, return, replace readers
    Register readers
    Manage locations and zones
    Configure readers
    Monitor Readers
    Encryption
    References
    API references
    Mobile readers
    Smart readers
    SDK migration guide
    Deployment checklist
    Stripe Terminal reader product sheets
Beyond payments
Incorporate your company
Crypto
Financial Connections
Climate
Understand fraud
Radar fraud protection
Manage disputes
Verify identities
HomePaymentsTerminal

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, use this guide to learn about country-specific requirements for Terminal.

Note

To process Terminal payments, both the Stripe account receiving the funds and the location associated with the reader must be in the same country, accepting local currency only.

Country

Availability

Refer to the following table to understand which readers and SDK platforms you can use in each country.

CountryAndroid**iOS**JavaScriptServer-Driven
Ireland
WisePad 3
Bluetooth or USB
Stripe Reader S700
Smart
WisePOS E
Smart
Tap to Pay
Embedded
WisePad 3
Bluetooth
Stripe Reader S700
Smart
WisePOS E
Smart
Tap to Pay
Embedded
Stripe Reader S700
Smart
WisePOS E
Smart
WisePOS E
Smart
**Compatibility for this mobile SDK also applies when used with React Native.

Integrate Terminal in Ireland

Stripe supports Visa, Mastercard, American Express, and Discover payments in Ireland. All transactions must be made in euros (EUR). To accept Terminal charges in Ireland, either your platform account or connected account must be in Ireland.

Use locations

Create Locations for your business with addresses in Ireland and associate your readers to them. This will ensure that they automatically download the configuration needed to properly process charges in Ireland. A valid address for a Location in Ireland must contain the line1, postal_code, and country properties.

Command Line
curl
Ruby
Python
PHP
Java
Node
Go
.NET
No results
curl https://api.stripe.com/v1/terminal/locations \ -u
sk_test_BQokikJOvBiI2HlWgH4olfQ2
:
\ -d "display_name"="HQ" \ -d "address[line1]"="Grand Canal Street Lower" \ -d "address[city]"="Dublin" \ -d "address[country]"="IE" \ -d "address[postal_code]"="D02 H210" \

Reader software version

BBPOS WisePOS E readers operating in Ireland must use the reader software version 1.5.0.0 or later. Read about BBPOS WisePOS E software updates for details.

Similarly, BBPOS WisePad 3 readers must use the reader software version 4.01.00.54_Prod_EU_W1_off_v23_510001 or later. Read about BBPOS WisePad 3 software updates for details.

Strong Customer Authentication

Strong Customer Authentication (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 (EEA). For more information about this European regulation, you can read Stripe’s PSD2: SCA guide.

Transactions below 50 euros (or the local currency equivalent) are considered low value and may 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 Ireland, 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, may 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 is not 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.

Was this page helpful?
YesNo
  • Need help? Contact Support.
  • Join our early access program.
  • Check out our changelog.
  • Questions? Contact Sales.
  • LLM? Read llms.txt.
  • Powered by Markdoc