--- title: "Braintree Integration" description: "Process payments through Braintree, the PayPal-owned gateway. Agents charge vaulted payment methods or client nonces, capture and void authorizations, issue full or partial refunds, and search transactions for reconciliation via the GraphQL API." url: https://flowrunner.ai/integrations/braintree date_modified: 2026-08-01T02:40:32-07:00 --- # Braintree [Payments](https://flowrunner.ai/integrations/category/finance-accounting) Process payments through Braintree, the PayPal-owned gateway. Agents charge vaulted payment methods or client nonces, capture and void authorizations, issue full or partial refunds, and search transactions for reconciliation via the GraphQL API. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 8 actions · Basic auth · available [Braintree website](https://braintreepayments.com/) · [Platform Documentation](https://developer.paypal.com/braintree/docs) · Capability data verified 2026-08-12 1. A refund request arrives through the support workflow with an order reference attached 2. Get Transaction retrieves the transaction's status, amount, and settlement history 3. The agent verifies the claim: amount within the original charge, transaction actually settled, no prior refund on record 4. Settlement state routes the path, Refund Transaction for settled charges, Void Transaction for authorizations that have not settled 5. Above the team's threshold, or on a second refund for the same customer, the finance owner approves the amount before money moves 6. The approved refund or void executes against the gateway 7. The outcome posts to the finance channel with the transaction ID, and the reconciliation sheet gains its row ## What This Integration Enables Payment operations fail in two directions: too slow, and refunds become support escalations; too loose, and money moves without anyone checking the claim. This connector, built on Braintree's GraphQL API, lets FlowRunner agents be fast and strict at once. Agents charge vaulted payment methods and nonces, run two-step authorize-and-capture flows, route refunds and voids by settlement state, and search transactions for reconciliation, with every money-moving step gated exactly as tightly as your finance policy says it should be. - Charge vaulted payment methods or client nonces, immediately or authorize-first - Complete two-step checkouts with capture, full or partial, up to the authorized amount - Issue full or partial refunds on settled transactions, gated by amount - Void authorizations before settlement to release customer funds fast - Search and retrieve transactions for daily reconciliation and reporting - Reach any uncovered corner of the gateway with raw GraphQL when needed Money movement is the canonical case for FlowRunner's [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) orchestration: verification at machine speed, authorization by a person. A note on the two-step pattern, because it is underused: authorizing at order time and capturing at fulfillment keeps you from charging for what you cannot ship, and it is exactly the kind of sequencing that falls apart when humans run it manually across days. An agent holds the authorization, watches the fulfillment event, and captures or voids on the outcome, with the timing rules written once in the flow. The gateway supports the pattern natively; orchestration is what makes it operationally practical. ### Without FlowRunner **Refunds queue behind whoever has gateway access**: A simple refund waits days because two people share the Braintree login **Void versus refund confused constantly**: Unsettled transactions get refunded instead of voided, holding funds longer than anyone intended **Reconciliation is a month-end export**: Someone downloads transactions and rebuilds the same spreadsheet every close ### With FlowRunner **Refunds verified in seconds, approved deliberately**: Agents check settlement state and history instantly; a person clears the money movement **The settlement state picks the path**: Agents route to void before settlement and refund after, automatically, every time **Reconciliation accrues daily**: Settled transactions flow to the ledger sheet continuously, so close reads instead of rebuilds ## Use Case Scenarios ### Checkout that charges and confirms in one motion An order completes and the flow calls Charge Payment Method against the customer's vaulted payment method, submitted for settlement immediately. On success, a receipt with the transaction ID and amount goes out through [Gmail](https://flowrunner.ai/integrations/gmail-service), and the order system updates. On decline, the order holds and the customer gets a clear next step instead of silence. No one touches the gateway console for the happy path. ### The refund desk with a threshold Support approves a return. The agent pulls the charge with Get Transaction, confirms it settled and has no prior refund, and checks the amount. Under the threshold, Refund Transaction fires and the customer is notified. Over it, the request pauses in [Slack](https://flowrunner.ai/integrations/slack) with the transaction history and the agent's verification attached; the finance owner approves or adjusts, and only then does money move. Every refund, either path, lands in the log with who authorized it. ### Reconciliation that happens while you sleep Nightly, Search Transactions pulls the day's transactions by created-at range, cursors through the pages, and writes each settled charge, refund, and void to [Google Sheets](https://flowrunner.ai/integrations/google-sheets) with status and amount. Discrepancies against the order system, a charge with no order, an order with no charge, post to the finance channel before breakfast. Month-end close starts from a ledger that already exists. ## Human-in-Loop Highlight Refund Transaction moves real money out of your account and back to a customer, and once it executes there is no API call that reverses generosity. The failure mode is rarely fraud; it is process: a double-submitted request refunding the same charge twice, a typo refunding 500.00 instead of 50.00, a partial refund issued as a full one. So FlowRunner agents do the verification no rushed human consistently does, Get Transaction to confirm settlement and check refund history, amount validated against the original charge, and then apply the threshold: routine amounts flow, anything above the line or anomalous pauses for the finance owner with the evidence assembled. The approval takes ten seconds because the agent already did the hour of checking. The mistakes that used to cost real money now cost nothing, because the irreversible step always had a person in front of it. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 8 actions ### Charging 2 - **Charge Payment Method** Creates and submits a sale against a vaulted payment method ID or a single-use client nonce, settling immediately by default or authorizing only when Submit for Settlement is off. The revenue-side workhorse. - **Capture Transaction** Submits a previously authorized transaction for settlement, optionally for a partial amount up to the authorization. The second half of authorize-then-capture checkouts. ### Reversals 2 - **Refund Transaction** Refunds a settled or settling transaction, fully or partially, returning funds to the customer. The operation this page's human gate exists for. - **Void Transaction** Cancels an authorized or submitted transaction before settlement, releasing the hold on customer funds. The faster, cleaner reversal when settlement has not happened; maps to Braintree's reverseTransaction. ### Lookup and Reconciliation 2 - **Get Transaction** Retrieves a transaction by its GraphQL ID with status, amount, timestamps, and status history. The verification step before any reversal. - **Search Transactions** Searches transactions with status and created-at date filters, cursor-paginated. The engine behind daily reconciliation. ### Utility 2 - **Ping** Runs the gateway's built-in ping query to verify keys and environment, sandbox versus production, before flows depend on them. - **Run GraphQL** Executes any raw Braintree GraphQL query or mutation with variables, for gateway capabilities not exposed as dedicated actions. The escape hatch, wielded deliberately. ## Frequently Asked Questions ### What can FlowRunner do with Braintree? FlowRunner agents can run Charge Payment Method, Refund Transaction, and Capture Transaction in Braintree, plus 5 more actions. ### Does connecting Braintree to FlowRunner require OAuth? No. Braintree connects to FlowRunner with basic authentication (a username and password), no OAuth flow required. ### Can Braintree trigger a FlowRunner workflow automatically? Braintree doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Braintree?** This integration exposes Braintree to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/braintree. Site index: https://flowrunner.ai/llms.txt