Server-driven integration mode enables you to build in-person payment experiences using the Stripe API, instead of requiring the Android, iOS, or JavaScript SDK.

WHAT ARE THE BENEFITS OF SERVER-DRIVEN INTEGRATION?

With Server-driven integration, you can:

• Use Terminal even if your infrastructure doesn’t support our native iOS, Android, or JS SDKs.
• Build an integration that’s powered by your own middleware or cloud-based infrastructure.
• Improve reader network connections using an internet connection instead of the local area network.

This integration mode requires using the BBPOS WisePOS E or the S700, Terminal’s screen-enabled smart readers which supports both countertop and mobile use cases.

WHAT ARE THE LIMITATIONS?

Server-driven integration doesn’t support:

• Stripe Terminal Bluetooth readers
• Collect payments while offline

WHERE WILL SERVER-DRIVEN BE AVAILABLE?

See which readers and integration modes you can use in each country.

WHAT IS REQUIRED TO GET STARTED?

See our integration documentation and sample integration code.

CAN I CONTINUE USING TERMINAL ANDROID, IOS, JAVASCRIPT SDKS?

Yes, we’ll continue supporting and making updates to the Android, iOS, and JavaScript SDKs.

You can choose to use server-driven integration as your only integration mode. You can also choose to use an SDK integration alongside server-driven; the WisePOS E will respond to requests from both integration types depending on preference - no additional configuration is needed.

WHAT ARE THE BENEFITS TO NETWORK CONNECTIVITY?

Server-driven allows you to avoid local network issues and DNS issues by using the Stripe API as the intermediary between your point of sale application and the reader.