Integration Guides/
Payment Flows In-Store and Omnichannel

Payment Flows In-Store and Omnichannel

This page is for product, engineering, and operations teams who need to know where to go next in the documentation set. Use it as a guide to which in-store and omnichannel payment flows are supported across your POS, Verifone, and Braintree, and where to find details on how to configure, build, and monitor each flow.

How payments move through the systemAnchorIcon

At a high level, all supported in-store payment flows follow the same pattern and share a common backend across POS, Verifone, and Braintree:

  • Your POS initiates the payment.
  • Verifone terminals collect card or wallet data.
  • Braintree processes card transactions and is responsible for authorization, settlement, and disputes.
  • Verifone sends in-store card traffic to your Braintree gateway.
  • Other methods, such as gift cards or private label cards, are processed by Verifone and still appear in your reporting.

This gives you one unified backend for card processing and a single system of record for ecommerce, in-store, and omnichannel activity. You can rely on the same core payment lifecycle and data model across all channels, rather than managing separate systems.

Your POS integrates with Verifone via POS Cloud or PSDK to start in-store payments and receive results. Choosing between these integration options determines how your POS connects to Verifone terminals and exchanges transaction data.

Canonical flows at a glanceAnchorIcon

Use this list to see the core flows supported by the integration before drilling into dedicated pages for each scenario.

  • In-store Sale → POS → Verifone terminal → Braintree
  • In-store Refund → POS → Verifone terminal (or original Transaction ID) → Braintree
  • In-store Pre-Auth and Completion → POS → Verifone terminal → Braintree auth → POS/OMS capture → Braintree
  • BOPIS (Buy Online, Pick Up In Store) → supported omnichannel flow where authorization happens online and capture happens when the order is fulfilled in store
  • BORIS (Buy Online, Return In Store) → supported omnichannel flow where the original sale happens online and the return is initiated and refunded in store
  • Endless Aisle → POS in store → Verifone terminal → Braintree auth → OMS → Verifone → Braintree capture

Where to learn about specific flowsAnchorIcon

Use this section to find the right place in the documentation for each flow. It points you to the pages that describe how specific in-store and omnichannel scenarios work and how to implement them in your systems.

  • If you need to understand in-store behavior: Use In-Store Payment Use Cases to see common in-store journeys from the cashier and customer perspective, with step-by-step call sequences. Examples include standard card sale, pre-authorization and completion, card-on-file, refunds, and voids.
  • If you are designing omnichannel flows: Review Canonical flows at a glance to see which omnichannel scenarios (such as BOPIS and BORIS) are supported and how they fit into your overall payment architecture. For merchant-specific designs, work with your PayPal and Verifone teams.
  • If you are implementing POS calls to Verifone: Use Verifone Operations to see which Verifone operations your POS calls and the request/response fields for each. Examples include Sale, Refund, Pre-Auth, Completion, and Reversal/Void.
  • If you are mapping data and identifiers: Use Braintree Passthrough Fields and Braintree GraphQL API ID Format to see how Braintree data appears in Verifone responses, which fields your systems can safely act on, and how to convert human-readable identifiers into GraphQL global IDs.

How flows show up in reporting and supportAnchorIcon

Braintree provides a single reporting and reconciliation surface for both in-store and ecommerce payments. In-store transactions include additional metadata so you can slice data by location, device, and entry method.

  • In the Braintree Control Panel and reports, in-store transactions are tagged with fields such as Transaction Origin (In-Person), Store ID, Reader ID, and Entry Mode (chip, tap, swipe, manual).
  • Reporting and Analytics pages describe which reports to use for daily reconciliation, settlement tracking, and performance analysis across channels, including Net Settlement where applicable.
  • Support / Getting Help pages explain when to contact PayPal (Braintree) versus Verifone, and what information to provide, such as Merchant ID, MAIDs, Transaction IDs, Store ID, and device details.