Braintreepayments Braintree GraphQL API
✓ Official Vendor SpecPaymentsPayment Processingbearer, basic1 EndpointsREST
For Agents
Tokenize payment methods and charge cards, PayPal, Venmo, and digital wallets through Braintree's GraphQL endpoint, with refunds, captures, and customer management in one mutation surface.
Use for: I want to charge a credit card through Braintree, Process a PayPal payment for an order, Refund a Braintree transaction by transaction id, Tokenize a card into a single-use payment token
Not supported: Does not handle accounting, tax filing, payroll, or invoicing — use for processing card, wallet, and bank payments only.
The Braintree GraphQL API is PayPal's payment processing platform exposed as a single GraphQL endpoint, supporting credit cards, PayPal, Venmo, Apple Pay, Google Pay, Samsung Pay, US bank accounts, and local payment methods. All operations are submitted as POST requests to /graphql with a JSON body containing a GraphQL query or mutation plus variables. The API covers tokenizing payment instruments, charging and authorizing transactions, capturing and refunding, managing customers and payment methods, and running searches across the merchant's transaction history. It is designed for online merchants and platforms that need a unified payments backend across cards and alternative payment methods.
Install Jentic One Beta
Connect the Braintree GraphQL API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Braintree GraphQL API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Braintree GraphQL API.
Charge a card or PayPal account by sending a chargePaymentMethod mutation to POST /graphql
Authorize a payment and capture it later via authorizePaymentMethod and captureTransaction mutations
Refund a settled transaction in full or partially with the refundTransaction mutation
Tokenize raw card details into a single-use payment method via tokenizeCreditCard before charging
Vault customers and their payment methods so subsequent charges run against a stored token
Search transactions, customers, and disputes by id, status, or date range using GraphQL queries
Issue a client token for the Drop-in or hosted fields UI via createClientToken
Use Cases
Patterns agents use Braintree GraphQL API for, with concrete tasks.
★ E-commerce checkout with cards and wallets
Accept payments on a storefront across credit cards, PayPal, Venmo, Apple Pay, and Google Pay through one Braintree GraphQL endpoint. The frontend collects a payment method via Drop-in or hosted fields, the backend exchanges it for a single-use token, and a chargePaymentMethod mutation posts the charge in one round trip. Settlement, fraud screening, and 3D Secure are handled by Braintree behind the scenes.
Send a chargePaymentMethod mutation to POST /graphql with a single-use token and amount '49.99' USD, then read transaction.status from the response to confirm SUBMITTED_FOR_SETTLEMENT.
Authorize-then-capture for shippable goods
Hold funds on a buyer's card at checkout and only capture them when the order ships. The merchant sends authorizePaymentMethod for the order amount, then captureTransaction once the warehouse confirms dispatch. This avoids charging customers for items that turn out to be out of stock and limits exposure to refund fees on cancellations.
Call authorizePaymentMethod for amount '120.00', store the returned transaction.id, then on shipment call captureTransaction with that id and amount '120.00'.
Refunds and dispute resolution
When a customer requests a refund, send refundTransaction with the original transaction id and the amount to return. For partial refunds, pass a smaller amount; the API handles the linkage to the parent transaction and returns the refund's settlement status. Disputes can be looked up via the dispute search query to inspect status and evidence requirements.
Send refundTransaction with transactionId={original_id} and amount '25.00' to POST /graphql and confirm refund.status is SUBMITTED_FOR_SETTLEMENT in the response.
Vaulted customer with stored payment methods
Create a Braintree customer record, attach one or more payment methods, and charge that vaulted method on subsequent orders without re-collecting card data. This is the foundation for one-click checkout, subscriptions, and account-on-file billing, and keeps card data inside Braintree's PCI scope rather than the merchant's.
Run createCustomer with email and name, then chargePaymentMethod against the returned customer's vaulted paymentMethod.id for amount '14.99'.
AI agent integration via Jentic
An agent that needs to take a payment can discover Braintree through Jentic search, load the GraphQL operation schema, and execute the chargePaymentMethod mutation without ever holding the merchant's API keys in its context. Jentic injects credentials at runtime so the agent only sees inputs and outputs.
Through Jentic, search for 'process a credit card payment', load the chargePaymentMethod operation, and execute it with paymentMethodId and amount supplied by the caller.
Key Endpoints
1 endpoints — the braintree graphql api is paypal's payment processing platform exposed as a single graphql endpoint, supporting credit cards, paypal, venmo, apple pay, google pay, samsung pay, us bank accounts, and local payment methods.
METHOD
PATH
DESCRIPTION
POST
/graphql
Single GraphQL endpoint for all queries and mutations (charge, refund, vault, search)
POST
/graphql
Single GraphQL endpoint for all queries and mutations (charge, refund, vault, search)
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Braintree merchant public_key/private_key pairs and OAuth bearer tokens are stored encrypted in the Jentic vault and attached to POST /graphql at execution time. Agents call payment operations by intent and never see raw merchant credentials, which keeps PCI scope away from agent logs.
Intent-based discovery
Agents search Jentic for intents like 'process a credit card payment' or 'refund a transaction' and Jentic returns the relevant Braintree GraphQL operation (chargePaymentMethod, refundTransaction, etc.) with input variables typed, so the agent does not need to learn the GraphQL schema.
Time to first call
Direct Braintree integration: 3-7 days to handle GraphQL request shaping, authentication mode selection, sandbox parity, and webhook reconciliation. Through Jentic: under 1 hour — search, load, execute against the same /graphql endpoint.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Braintree GraphQL API through Jentic.
What authentication does the Braintree GraphQL API use?
The API supports HTTP bearer tokens (OAuth access tokens or client tokens) and HTTP basic auth using base64-encoded public_key:private_key. Through Jentic, those keys live in the encrypted vault and are attached to the Authorization header on POST /graphql at execution time, so they never appear in agent prompts.
Can I refund a transaction with the Braintree GraphQL API?
Yes. Send a refundTransaction mutation to POST /graphql with the original transaction id and an optional amount for partial refunds. The response returns refund.id and refund.status, which moves to SUBMITTED_FOR_SETTLEMENT once Braintree queues it.
What payment methods does the Braintree GraphQL API support?
Credit and debit cards, PayPal, Venmo, Apple Pay, Google Pay, Samsung Pay, US bank accounts (ACH), and local payment methods. They are all charged through the same chargePaymentMethod mutation by passing the appropriate single-use token or vaulted payment method id.
What are the rate limits for the Braintree GraphQL API?
Braintree does not publish a public per-endpoint rate limit — quotas are tied to merchant account configuration. For high-volume processing, contact Braintree support to confirm thresholds and enable burst handling on /graphql.
How do I charge a card with the Braintree GraphQL API through Jentic?
Install the SDK with pip install jentic, then await client.search('process a credit card payment'), await client.load on the chargePaymentMethod operation, and await client.execute with paymentMethodId and amount. Jentic posts the GraphQL mutation to /graphql with vaulted credentials.
Does the Braintree GraphQL API support sandbox testing?
Yes. Point requests at https://sandbox.braintreegateway.com instead of the production base URL and use sandbox merchant credentials. The schema and mutations are identical, so the same chargePaymentMethod and refundTransaction calls work end-to-end.
GET STARTED