Testing

RubySDK

• Current Braintree Languages
• Java
• .NET
• Node.js
• PHP
• Python
• Ruby

Use the test values below to test functionality in the Braintree sandbox.

Transaction amounts

When working with transactions, you can pass specific amounts to simulate different processor responses. Each test amount below will trigger the associated authorization response, regardless of the processing currency.

Credit card numbers

The sandbox environment only accepts specific test credit card numbers. Use the credit card values below to trigger different responses from the gateway.

Learn more about the difference between transactions and verifications.

Valid card numbers

These credit card numbers will not trigger specific credit card errors.

*Diners Club cards are processed as Discover cards.

Card numbers for unsuccessful verification

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

*Diners Club cards are processed as Discover cards.

Card numbers with type indicators

The following card numbers can be used to simulate various types of cards, such as prepaid, commercial, or healthcare. 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":

Payment method nonces

In order to simplify testing your server side code, we provide static payment_method_nonce values for you to use in sandbox. Credit card nonces come with a billing postal code already filled in for AVS testing purposes. If you do not want to include a billing address in your testing or if you'd like to use a specific billing address ID instead, use fake-valid-no-billing-address-nonce.

Collect device data from the client and include the device_data_from_the_client in the transaction.

result = gateway.transaction.sale({
    amount: '10.00',
    payment_method_nonce: 'fake-valid-nonce',
    device_data: device_data_from_the_client,
    options: {
        submit_for_settlement: true
    }
});

Nonces representing cards

Nonces representing alternative payment methods

Nonces for testing card verification

Processor rejected nonces

The following payment method nonces represent credit cards that simulate an unsuccessful card verification response with a status of processor_declined.

Gateway rejected nonces

The following payment method nonces represent credit cards that simulate an unsuccessful card verification response with a status of gateway_rejected.

CVV-only nonces

The following payment method nonces represent credit card CVV or CID values collected on the client side to verify cards already stored in your Vault. The test nonce you use determines which cvv_response_code you receive in the sandbox.

For details on generating CVV-only nonces in your client-side integration, see the client SDK references:

3D Secure nonces and authentication IDs

You can use these nonces or authentication IDs to test your integration under various 3D Secure scenarios for Visa cards. Authentication IDs are an alternate way of specifying a 3D Secure authentication to use for a transaction if no authentication is attached to the payment method. See the 3D Secure guide for more information on different status codes.

Nonce objects

When writing integrations tests against the Braintree sandbox environment, you may also use these nonce objects in place of the nonce that would normally be returned from the client side integration.

Braintree::Test::Nonce::Transactable
Braintree::Test::Nonce::Consumed
Braintree::Test::Nonce::PayPalOneTimePayment
Braintree::Test::Nonce::PayPalFuturePayment

Settlement status

Settlement routes have been exposed to aid with the testing of transactions and the transition between the different statuses. These settlement routes will allow a transaction that has been submitted_for_settlement to transition to settled, or settlement_declined. See the transaction statuses page for additional information on each response.

Example code to change the status of a transaction to settled:

sale_result = gateway.transaction.sale({
    amount: "100",
    payment_method_nonce: nonce_from_the_client,
    options: {
        submit_for_settlement: true
    }
});

result = gateway.testing.settle(sale_result.transaction.id);
result.success?.should == true;
result.transaction.status.should == Braintree::Transaction::Status::Settled;

Example code to change the status of a transaction to settlement_declined:

sale_result = gateway.transaction.sale({
    amount: "100",
    payment_method_nonce: nonce_from_the_client,
    options: {
        submit_for_settlement: true
    }
});

result = gateway.testing.settlement_decline(sale_result.transaction.id);
result.success?.should == true;
result.transaction.status.should == Braintree::Transaction::Status::SettlementDeclined;

Disputes

Creating a disputed test transaction

You can use the following test card number in the sandbox to create sale transactions of any amount* that are instantly disputed:

*Some transaction amounts trigger specific dispute behavior in the sandbox; see creating test disputes that require compelling evidence below. In addition to creating a test dispute, using this test card to create sandbox transactions will allow you to:

• Receive a dispute email notification
• Receive a Dispute Opened webhook (if set up)
• Search for or find the dispute in the Control Panel or via the API
• Respond to the dispute in the Control Panel or via the API with specific evidence that will update the dispute status to or

Creating test disputes that require compelling evidence

The following transaction amounts will set the dispute reason_code accordingly:

Creating test disputes for Venmo transactions

When creating a Venmo test transaction with the fake-venmo-account-nonce payment method nonce, the following transaction amounts will create and set the dispute status accordingly:

Managing test disputes via the API

To simulate winning or losing a dispute with any reason code via the API:

1. Find the dispute
2. Add text evidence using one of the following strings:
   • compelling_evidence to simulate a won dispute
   • losing_evidence to simulate a lost dispute
3. Finalize the dispute

Managing test disputes via the Control Panel

To simulate winning or losing most disputes in the Control Panel:

1. Log into the sandbox Control Panel
2. Click on Disputes in the navigation bar
3. On the row for the dispute you're testing, click the expand button on the far right side of the row, and choose Submit Evidence from the menu of options
4. Under the Provide Evidence field, enter the following text:
   • compelling_evidence to simulate a won dispute
   • losing_evidence to simulate a lost dispute
5. Click the Submit Dispute To Processor button

Fraud-related disputes

To simulate winning or losing fraud-related disputes in the Control Panel:

1. Log into the sandbox Control Panel
2. Click on Disputes in the navigation bar
3. On the row for the dispute you're testing, click the expand button on the far right side of the row, and choose Submit Evidence from the menu of options
4. Under the Include Evidence section, select Proof of recurring transaction history as your compelling evidence
5. Select any date and time
6. In the Recurring transaction ID field, enter the following text:
   • compelling_evidence to simulate a won dispute
   • losing_evidence to simulate a lost dispute
7. Click the Submit Dispute to Processor button

Venmo disputes

To simulate winning or losing Venmo disputes in the Control Panel:

1. Log into the sandbox Control Panel
2. Click on Disputes in the navigation bar
3. On the row for the dispute you're testing, click the expand button on the far right side of the row, and choose Submit Evidence from the menu of options
4. Under the Evidence Type section, select Other as your evidence type
5. In the Provide Evidence text field, enter the following text:
   • compelling_evidence to simulate a won dispute
   • losing_evidence to simulate a lost dispute
6. Click the Submit Dispute button

3D Secure

Test credit card numbers for 3D Secure transactions are provided by our 3D Secure authentication provider, CardinalCommerce. See the PDF provided in the 3D Secure guide for a complete list.

Fraud tools

You can use the following test card number in the sandbox to simulate Premium Fraud Management Tools flagging a transaction as pending review. This feature is only available for Fraud Protection Advanced.

You can use the following test card numbers in the sandbox to simulate Premium Fraud Management Tools or risk threshold rules rejecting a request.

Otherwise, you will receive an Unrecognized status for the gateway rejection.

The following payment method nonces represent payment methods that will be gateway rejected by Braintree's various fraud tools.

AVS and CVV/CID responses

CVV/CID responses

AVS error responses

AVS postal code responses

AVS street address responses

Bank routing numbers

Bank routing numbers must pass a checksum, much like credit card numbers. The following routing numbers are valid, and can be passed to the sandbox:

• 071101307
• 071000013

IBAN numbers

To generate bank account numbers (IBANs) for sandbox testing, please refer to IBAN generator page.

PayPal One Touch

To make it easier to test out the app switch-based flows for PayPal One Touch on iOS, we created a fake iOS wallet that you can run on the iOS simulator. Clone or download it from GitHub and make sure it's installed on the same simulator you're using for development. To test the One Touch flows on Android, we recommend installing the latest PayPal app on your test device or simulator.

Purge sandbox data

You can purge all of the following data from your sandbox:

• Transactions
• Customers
• Payment methods
• Addresses
• Disputes
• Subscriptions
• Sub-merchant accounts (if you are using Braintree Marketplace)

To purge your sandbox data:

1. Log into your sandbox Control Panel
2. Click on the gear icon in the top right corner
3. Click any option from the drop-down menu to access the settings pages
4. Click Purge Test Data in the navigation bar
5. Click the Yes button to confirm your choice