In-Person
Braintree SandboxContact SalesGet Help
  • Braintree In-Person
  • About
    • Solution Architecture
    • Technical Overview
    • Solution Coverage
  • Hardware
    • Verifone P400
    • Verifone M400
    • Verifone E285
    • Verifone V400m
  • Get Started
    • Integration Checklist
    • Request Dev Kit
    • Configure Sandbox
    • Account Structure
  • Integration Guides
    • API Authentication
    • Setup Reader
    • Initiate a Sale or Refund
      • Initiate a Card Present Authorization
      • Level 2 and Level 3 Data Processing
      • Passing Lodging Data
    • Vaulting and Customers
    • PayPal and Venmo QRC
    • Display Information
    • Custom Prompts
    • Card Data Collection
    • GraphQL Error Handling
    • Offline Transactions
    • Additional API Calls
    • Receipt Printing API
    • Reporting and Reconciliation
    • Testing Your Integration
    • Ready for Launch?
  • Partner Considerations
    • Overview
  • Support
    • Reader Management System (RMS) - Available in Beta Only
    • Managing Firmware Updates
    • Troubleshooting
    • Network Connection Test
    • Support/Contact Us
  • Reference
    • Firmware Version Release Notes
    • Verifone Device Reference
    • EMV Receipt Reference
    • General Payments Terminology
    • GraphQL Docs
    • PayPal Braintree Sub-processors
    • FAQ
Powered by GitBook
On this page
  • In-Store Reader Configurations
  • Traditional Fixed POS 1:1 Configuration Example
  • Mobile POS with Fixed Readers Example
  • Dual-lane Checkout Example
  • Payment Method Abstraction
  • Omnichannel Capabilities

Was this helpful?

  1. About

Solution Architecture

Understanding the flexibility of cloud-based reader configurations.

PreviousBraintree In-PersonNextTechnical Overview

Last updated 1 year ago

Was this helpful?

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.

Omnichannel Capabilities

A developer can work within a consistent interaction flow using and 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.

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 .

PaymentMethod
Transaction
Braintree Direct