Solution Architecture

Understanding the flexibility of cloud-based reader configurations.

In-Store Reader Configurations

Any device that can make a web-based API call can initialize and create a transaction on the reader. Eliminating direct communication between POS hardware and the reader allows developers to create a flexible range of platform-independent, integrated POS configurations.

Traditional Fixed POS 1:1 Configuration Example

Today, a common configuration would be to have a dedicated card reader for each POS device.

Mobile POS with Fixed Readers Example

Another configuration includes a single fixed reader at the back of the store shared by two fixed POS registers. An additional POS device can be located at a convenient spot at the front of the store. Sales associates given tablets can wirelessly initialize and share the front store reader while working with the customer.

Dual-lane Checkout Example

It's also possible to create a many-readers-to-single-POS configuration, as seen in dual-lane, single-POS scenarios.

Payment Method Abstraction

The goal of the Braintree In-Person solution is to allow a single integration for all payment methods across all channels (in-store and online) through a unified platform. Our solution abstracts all payment methods for current and future payment types.

A developer can work within a consistent interaction flow using PaymentMethod and Transaction objects without requiring additional work as new payment methods become available. Future payment methods can be rolled out via the Braintree control panel without any change to the POS integration.

Omnichannel Capabilities

The Braintree In-Person reader solution is only one channel of the enterprise offering. Combining Braintree In-Person with Braintree's best-in-class "card not present" and "vault" solutions will allow developers to build cohesive capabilities across all channels. To learn more about the overall suite, see Braintree Direct.