braintreepayments.com
Braintree is a payments platform from PayPal for accepting payments, storing payment methods, and managing transactions, disputes, reporting, and related commerce workflows. It supports direct merchant integrations as well as delegated partner integrations through OAuth and client SDK authorization.
Braintree exposes a GraphQL payments API, a server-side gateway HTTP API documented through SDK/reference pages, and client-side authorization artifacts for its SDKs; authentication uses merchant gateway API keys, OAuth bearer tokens for delegated access, and client tokenization credentials.
- Braintree Server-Side Gateway APIdiscovered
- Braintree GraphQL APIdiscovered
Log in to the appropriate Braintree Control Panel for your environment — sandbox or production. Open the gear menu, choose API, and copy your public key, private key, and merchant ID from the API Keys section as described in Important Gateway Credentials. Keep the environment (sandbox or production) with the keys, since Braintree issues different credentials per environment.
Create or configure a Braintree OAuth application from the Braintree OAuth docs starting at OAuth overview. Implement the merchant-facing OAuth flow to obtain an access token for each connected merchant, then use that token as a bearer token in API calls. For in-person integrations, Braintree’s API Authentication guide confirms this bearer-token option for third-party applications.
Log in to the relevant Braintree Control Panel, open the gear menu, choose API, then go to the Tokenization Keys section. If no key exists, click Generate New Tokenization Key as described in Important Gateway Credentials. Tokenization keys are environment-specific and are used by Braintree client SDKs for reduced-privilege client-side authorization.
Generate a client token from your server using Braintree’s server-side API / SDK as documented in Client Token: Generate and explained in Client Token. This token is short-lived and is typically minted per session/request by your backend after it authenticates to Braintree with gateway credentials.
conventions · 0/7 published
- integrations.json——
- llms.txt✗
/llms.txt - API catalog✗
/.well-known/api-catalog - OpenAPI document✗
/api/schema/, /openapi.json, /swagger.json, /api/openapi.json, or /v1/openapi.json - MCP server card✗
/.well-known/mcp/server-card.json - OAuth protected resource✗
/.well-known/oauth-protected-resource - Agent card✗
/.well-known/agent-card.json - Agent skills✗
/.well-known/agent-skills/index.json
Publish these signals → /publishing