Sign in
An image of the Stripe logo
Create account
Sign in
Home
Payments
Business operations
Financial services
Developer tools
No-code
All products
Home
Payments
Business operations
Home
Payments
Business operations
Financial services
Developer tools
Support
Overview
Online payments
Products and prices
Invoicing
Subscriptions
Quotes
In-person payments
    Overview
    What is Terminal
    Design an integration
    Example applications
    Quickstart
    Accept an in-person payment
    Set up your reader
    Set up your integration
    Connect to a reader
    Collect payments
    Regional considerations
    Supported card brands
    Terminal payments features
    Multiparty payments with Connect
    Collect tips
    Save cards for future use
    Refund transactions
    Provide receipts
    Cart display
    Incremental authorizations
    Extended authorizations
    Operate offline
    Deploy at scale
    Order hardware
    Manage locations
    Configure readers
    References
    API references
    Bluetooth readers
    Smart readers
    SDK migration guide
    Testing
    Deployment checklist
    Stripe Terminal reader product sheets
Multiparty payments
After the payment
Add payment methods
Payment Links
Stripe Checkout
Stripe Elements
About the APIs
Regulation support
Implementation guides
Testing
Terminal
·
HomePaymentsIn-person payments

Set up your integration

Set up a Stripe Terminal SDK or server-driven integration to accept in-person payments.

The server-driven integration is generally available in the United States and Canada. To request access to the server-driven integration in countries other than the US and CA, please email stripe-terminal-betas@stripe.com.

Server-driven integrations use the Stripe API instead of a Terminal SDK to connect to smart readers and collect in-person payments. This allows you to:

  • Use Terminal even if your infrastructure doesn’t support iOS, Android, or JavaScript SDKs
  • Build a Terminal integration that’s powered by your custom middleware or cloud-based infrastructure
  • Integrate a .NET-based point of sale to Terminal
  • Improve reader network connections using an internet connection instead of the local area network
  • Make curl requests to prototype an integration

You can start your server-driven integration with the following components:

  • Your point of sale application — The operator-facing UI that employees see when creating a transaction.
  • Your backend infrastructure — Mediates requests from your point of sale application and makes requests to the Stripe API during the transaction.
  • The Stripe API — Receives requests and forwards them to a BBPOS WisePOS E reader. Stripe also sends webhooks to your backend infrastructure with the payment status.
  • A BBPOS WisePOS E reader or simulated reader — Prompts the cardholder for payment and communicates with Stripe and our financial infrastructure in order to process the payment. You can create a simulated reader if you don’t yet have a physical reader.
Server-driven integration architecture

See also

  • Connect to a reader
Was this page helpful?
Questions? Contact us.
Watch our developer tutorials.
Check out our product changelog.
Powered by Markdoc
You can unsubscribe at any time. Read our privacy policy.
Stripe Shell
Test mode
Welcome to the Stripe Shell! Stripe Shell is a browser-based shell with the Stripe CLI pre-installed. Login to your Stripe account and press Control + Backtick on your keyboard to start managing your Stripe resources in test mode. - View supported Stripe commands: - Find webhook events: - Listen for webhook events: - Call Stripe APIs: stripe [api resource] [operation] (e.g. )
The Stripe Shell is best experienced on desktop.
$