Skip to main content
CriticalSecretsOWASP A07:2021CWE-798

How to fix: Braintree API token in source

Braintree access tokens (production + sandbox) grant full payment processing, refund, and customer data access.

Why it matters

An exposed Braintree API token grants full access to your merchant account: creating charges, issuing refunds to attacker bank accounts, accessing all payment methods and customer PII (names, emails, masked card numbers) stored in the vault.

Braintree access tokens (production + sandbox) grant full payment processing, refund, and customer data access.

How to fix it

  1. 1Rotate via Braintree Control Panel → Account → API Keys
  2. 2Enable IP allowlisting in Braintree to restrict API key usage to your server IPs
  3. 3Keep all Braintree credentials server-side; use client tokens (not private keys) in browsers

Code examples

Correct: generate client token server-side, use private key never in browser

TypeScript
import braintree from 'braintree';

// Server-only Braintree gateway
const gateway = new braintree.BraintreeGateway({
  environment: braintree.Environment.Production,
  merchantId: process.env.BRAINTREE_MERCHANT_ID!,
  publicKey:  process.env.BRAINTREE_PUBLIC_KEY!,
  privateKey: process.env.BRAINTREE_PRIVATE_KEY!,  // server-only
});

// Generate a one-time client token for the browser
export async function generateClientToken() {
  const { clientToken } = await gateway.clientToken.generate({});
  return clientToken;  // safe to send to browser, not the private key
}

References

Detected automatically by VulnRadar. The check id is secret-braintree-token, stable across every scan so you can filter or diff on it.

See every secrets check

Questions

How severe is Braintree API token in source?
VulnRadar rates this critical severity in the secrets category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
Does VulnRadar check for this automatically?
Yes. It runs as part of every scan under the check id secret-braintree-token, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does Braintree API token in source map to?
It maps to CWE-798. In the OWASP Top 10 it falls under A07:2021.

Missing a check?

The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.

Propose a checkHow a check is built

Scan your own site for braintree api token in source

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

How to fix: Braintree API token in source | VulnRadar