Set up your integration

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

Server-driven integrations use the Stripe API instead of a Terminal SDK to connect to WisePOS E, Stripe Reader the related setting/the related setting, and Verifone 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 any device including 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

Server-driven integration doesn’t support:

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

Your point of sale application : The operator-facing UI that employees see when creating a transaction.
Your back-end 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 smart reader, such as the the related setting WisePOS E reader , Stripe Reader the related setting/the related setting , or a Verifone reader . Stripe also sends webhooks to your back-end infrastructure with the payment status.
A the related setting WisePOS E reader, Stripe Reader the related setting/the related setting, Verifone reader, or simulated reader : Prompts the cardholder for payment and communicates with Stripe and our financial infrastructure to process the payment. You can create a simulated reader if you don’t yet have a physical reader.