Short answer

Braintree test card v6 refers to the current set of sandbox-only card numbers used to simulate approvals, declines, and AVS or CVV mismatches in a Braintree test account. These numbers pass format validation but are never chargeable, and they only work when your API keys point at the sandbox environment. The response you get depends on two things: the card number itself and the transaction amount you submit.

braintree test card v4

Prerequisites

• A Braintree sandbox account (created from the Control Panel signup, not a live merchant account)
• Sandbox merchant ID, public key, and private key from Settings > API Keys
• A test checkout page or a direct API client such as curl or Postman
• The current test values page open in a second tab, since Braintree revises the list

Step-by-step

1. Sign in to the Braintree Control Panel and check that the environment switch at the top reads Sandbox.
2. Copy the sandbox merchant ID, public key, and private key into your integration's config or environment variables.
3. Open the Braintree test values reference and pick a card from the v6 table for the brand you want to test.
4. Enter the number in your checkout form. Commonly used sandbox numbers include 4111111111111111 for Visa, 5555555555554444 for Mastercard, 378282246310005 for American Express, and 6011111111111117 for Discover.
5. Set the expiration date to any month and year in the future. Expired-date handling is tested with dedicated numbers, not by typing a past date.
6. Enter the CVV listed next to that card. Visa, Mastercard, and Discover use a three-digit value such as 123; American Express uses a four-digit value such as 1234.
7. Choose the amount that maps to the result you want. Small standard amounts return an approval, while specific amounts in the documented range return declines such as do not honor, insufficient funds, or expired card.
8. Submit the transaction and open it in the Control Panel under Transactions to read the status, response code, and processor response text.
9. Check your webhook endpoint to confirm the transaction settlement or decline notification arrived with the expected status.
10. Repeat with an AVS mismatch number when you need to confirm your postal code and street address checks behave correctly.
11. Swap the sandbox credentials for production keys only when you are done testing, and never submit test numbers against live keys.

Common mistakes

• Running sandbox card numbers through a production account. Live processors reject them, and repeated attempts can flag the account.
• Assuming one number covers every failure mode. Decline, AVS failure, and CVV failure each have their own entry in the table.
• Storing the CVV after authorization. Card network rules forbid retaining it once the transaction is complete, even in a test environment where you are rehearsing production behavior.
• Ignoring the amount field. In Braintree sandbox, the amount is often the switch that triggers a decline when the card number alone returns an approval.

Notes on legality

Card numbers published by a payment processor for its own sandbox are safe to use because they map to no real account. Anything sold as live card data, sometimes labeled CVV or fullz, is stolen payment credentials. Buying, selling, or using that data is a federal crime in the United States and carries jail time, so the only card numbers worth typing into a Braintree form are the ones printed in the processor's own test documentation.

braintree test card v4