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
  • Intro to Braintree GraphQL
  • Understanding the In-Person GraphQL Object Relationships
  • What Card Reader models are supported?
  • High-Level Functionality Summary

Was this helpful?

  1. About

Technical Overview

This section is designed to give you a high-level overview of integrating with the Braintree In-Person product and its architecture.

PreviousSolution ArchitectureNextSolution Coverage

Last updated 1 year ago

Was this helpful?

Intro to Braintree GraphQL

If you're new to GraphQL, you should familiarize yourself with some basic GraphQL concepts before digging into our In-Person documentation. For a quick introduction, see the section. To get more in-depth, there are many great resources to learn GraphQL — to start with, we recommend and .

The In-Person capabilities are simply an additional set of GraphQL Objects and Mutations. All resources in the will be applicable and can be leveraged during your integration with Braintree In-Person.

Understanding the In-Person GraphQL Object Relationships

The API caller will act on behalf of a and can create as many as required using the mutation. The InStoreLocation object is designed to represent a physical location that will contain card readers. You will receive a dynamically generatedInStoreLocation.idto store for future changes to this location.

are then paired to a specific using the mutation. Multiple readers can be paired to a single . You will receive a dynamically generated InStoreReader.id to store for initializing this reader.

are created using the requestChargeFromInStoreReader mutation by providing the total checkout amount and the InStoreReader.id you want to initialize the transaction. The response will return a uniqueInStoreContext.idto reference while your application waits for the customer to interact with the reader.

Your application will check on an interval the status of the , and once the customer is finished interacting with the device, you will receive a object in the response.

What Card Reader models are supported?

Braintree has partnered with Verifone to offer best-in-class payment terminal (card reader) hardware. This means that although Verifone might manufacture the hardware, most of the functionality and software running on the device is actually developed by Braintree. We currently support the below-listed hardware models. We will continue to update this documentation as we expand our hardware offering. For more information on how our hardware ordering and logistics process works, please consult your Solutions Engineer or Integration Engineer.

and have the same behavior. However, they are not interchangeable. Only special test cards work on the sandbox card readers. Test cards do not work on production card readers. More info on the hardware specs is available .

Card Reader
Description
Availability

The P400 card reader is a fixed lane device that is tethered to a power source. However, the device offers flexibility for network connection methods including both Ethernet and WiFi capabilities.

Available

The E285 card reader is a mobile device that does not require tethering to a power source. This device relies on WiFi network connectivity.

Available

The M400 reader is a fixed lane device that is tethered to a power source. The reader offers flexibility for network connection methods including both Ethernet and WiFi.

Available

High-Level Functionality Summary

Feature Name
Description
Link to Documentation

Sale

Facilitate an auth + capture in one request from your customer using the card reader

Authorize

Facilitate an authorization from your customer using the card reader

Refunds

Perform either a referenced or unreferenced refund to the customer

Vaulting

Retrieve a payment method token for future use or vault your customer information with Braintree

Line Item Display

Display sale line items on the card reader screen during scanning

Custom Prompts

Display custom text (surveys, terms & conditions, address confirmation, etc...) and collect customer input (boolean) or signature from the card reader

Card Data Collection

Swipe non-PCI Gift Cards or PLCC cards on the reader to collect the magstripe track data

QR Code Payments

Accept Venmo and PayPal using scannable QR codes on the card reader screen

Offline Processing

Accept payments while your internet is down

Verifone P400
Verifone E285
Verifone M400
Initiating an Authorization
Vaulting Payment Methods
Collect Customer Input
Read Magstripe Card Data
QR Code Based Payments
Offline Processing
Basic Concepts
Introduction to GraphQL
How to GraphQL
detailed Braintree GraphQL guides
Merchant
InStoreLocations
createInStoreLocation
InStoreReaders
InStoreLocation
pairInStoreReader
InStoreLocation
InStoreContexts
InStoreContext
Transaction
Sandbox card readers
Production card readers
here
Display Line Items
Initiating a Sale
Perform Refunds