Use the credit card values below to trigger different responses from the gateway.

No credit card errors

The following credit card values will not trigger specific credit card errors, but this does not mean that your test transaction will be successful. Values passed with the transaction (e.g. amount) can be used to trigger other types of gateway responses. See Test Amounts for more details.

Unsuccessful credit card verification

The following credit card numbers will simulate an unsuccessful card verification response.

Card type indicators

The following card numbers can be used to simulate various types of cards. Using any of the card numbers below will force the corresponding card type indicator to return "Yes" and the others to return "No" or "Unknown":

Disputes

While anyone can simulate a dispute in the sandbox Control Panel, the way you manage chargebacks in production depends on your account setup. Not all accounts will have disputes available in the Control Panel in production.

The following card number can be used to simlute an open dispute:

You can simulate winning or losing a dispute in the Control Panel:

1. Log into the sandbox Control Panel
2. Navigate to Disputes
3. Click Dispute on the chargeback you would like to dispute
4. Under the Additional Dispute Evidence field enter:
   • compelling_evidence to simulate a won dispute
   • losing_evidence to simulate a lost dispute
5. Click Submit Dispute

Other card information

Go live

Create an API user

Production API credentials, including your API keys, must be entered into your server-side code to connect API calls to the Braintree gateway. While each user in your gateway has their own unique set of API keys, only one set can be included in your integration.

We recommend creating a new user specifically designated as the API user, whose API keys can be used for your integration. This user should have Account Admin permissions in order to avoid issues such as an authorization error.

Get production credentials

Log into your production account as the API user to obtain your API credentials. You'll need the:

• Production merchant ID
• Production public key
• Production private key

Keep in mind that public and private keys are both environment- and user-specific.

Update production account settings

Make sure your production account settings mirror the ones in your tested sandbox configuration. Be sure to recreate any recurring billing plans or settings if you plan to use recurring billing in production.

Update live server configuration

In your server code, update your configuration to production values:

Braintree::Configuration.environment = :production
Braintree::Configuration.merchant_id = "YOUR_PRODUCTION_MERCHANT_ID"
Braintree::Configuration.public_key = "YOUR_PRODUCTION_PUBLIC_KEY"
Braintree::Configuration.private_key = "YOUR_PRODUCTION_PRIVATE_KEY"

Once you have updated these values and configured your preferred processing settings, the live production environment will function similarly to the sandbox environment you've been using for development. Learn more about the differences between production and the sandbox.

On the client side, no configuration updates are needed when you make the switch to production – your client obtains its client token from your server, which is all the configuration it needs.

Test transactions in production

It is important to test your production account by creating a couple of low-value sale transactions for each of the payment method types you plan to accept. Be sure to submit the transactions for settlement, and then confirm that the funds have deposited into your bank account. This typically happens a few days after they have settled.

See also

• Accepted payment methods
• Accepted currencies
• Credit card response object
• Payment method request
• Payment method response object