Design an integration

Choose a reader and platform and see how they work together.

Copy page

Country:

Reader:

Architecture:

Reader details

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

WisePOS E reader

Smart reader with touchscreen
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:

Not a coder? Find a Stripe partner who supports Terminal.

Architecture

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

The structure of the integration looks like this:

You can build a working example of an integration like this using the Terminal Quickstart.

Organize readers and locations

Before you connect a reader to a Terminal integration, you must create one or more Locations, either in the Dashboard or using the API. Then, 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 may use addresses that represent a primary place of business.

Prototyping

When you first begin writing your application, you can test it with a simulated reader and simulated cards. The Terminal Quickstart demonstrates an app at this stage of development.

When you’re ready to work with actual hardware,

Next steps

See Terminal Quickstart for a full code example
Set up your integration to start writing code
Order readers, accessories, and test cards when you’re ready to work with physical hardware