Skip to content
Create account
 or
Sign in
The Stripe Docs logo
/
Create account
Sign in
OverviewUpgrade your integration
Online payments
OverviewFind your use caseManaged Payments
Payment methods
Payment interfaces
Payment scenarios
In-person payments
Terminal
Beyond payments

Design a custom POS integration

Choose your country, reader, and integration type to learn how to build your custom point-of-sale.

Country:
Reader:
Architecture:

Reader details

For more information about the differences between readers, see Select your reader.

S700 reader

  • All-in-one, Android-based smart reader that can run your custom application
  • For handheld or countertop use; optional dock available for mounted or countertop use cases
  • Contactless, chip, and swipe payments

Use it in a server-driven integration

  • Write your point-of-sale app for any device
  • Access Stripe features using the Stripe API
  • Communicate with the reader using Stripe and your server

Limitations

Server-driven integration doesn’t support:

If you don’t write code, you can find a Stripe partner who supports Terminal.

Architecture

In a server-driven integration, your POS device connects to your server. Your server then makes Stripe API calls, and Stripe updates the reader and returns the result.

The structure of the integration looks like this:

Server-driven integration architecture

Note

You can build a working example of an integration like this using the Terminal Quickstart-no reader hardware required.

Prototyping

Using the simulated reader

When you begin writing your application, you can test it with a simulated reader and simulated cards. This lets you build and verify your complete integration without needing physical hardware. The Terminal Quickstart demonstrates an app at this stage of development.

Using a physical reader

When you’re ready to work with actual hardware, you can extend your integration to a physical device. Follow these steps:

  1. Order a Stripe Reader S700 and physical test cards
  2. Connect to the reader over the internet
  3. Test your logic with physical test cards

Organize readers and locations

Stripe requires a Location to be associated with every Terminal reader, including a simulated reader. Before you connect a reader to a Terminal integration, you must create one or more Locations, either in the Dashboard or using the API. When you connect to your reader, specify one of those locations.

Locations represent physical places where your readers operate. Stripe needs location information to process payments correctly and keep your reader up to date. If your business requires you to move your readers frequently, your locations can use addresses that represent a primary place of business.

Next steps

Was this page helpful?
YesNo