Additional Features/
Braintree Marketplace/
Testing and Go Live

Testing and Go Live

Sandbox testingAnchorIcon

Braintree Marketplace webhooksAnchorIcon

Sub-merchant approvalAnchorIcon

To trigger a SubMerchantAccountApprovedconfirmation webhook, provide the following constant as the first name of the Sub Merchant:
  1. Python
import braintree.test.merchant_account

result = gateway.merchant_account.create({
    "individual": {
        "first_name": braintree.test.merchant_account.Approve,
        // ...
    }
    // ...
})

Sub-merchant declineAnchorIcon

To trigger a SubMerchantAccountDeclinedconfirmation webhook, provide an error code for the first name of the sub-merchant. You will receive the provided error in the webhook.

For example, this would trigger the Applicant declined due to OFAC error:
  1. Python
result = gateway.merchant_account.create({
    "individual": {
        "first_name": braintree.ErrorCodes.MerchantAccount.ApplicantDetails.DeclinedOFAC,
        // ...
    }
    // ...
})
See our Python library for a list of errors.

Bank routing numbersAnchorIcon

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

Go liveAnchorIcon

Create an API userAnchorIcon

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 do not recommend including an individual user's API credentials. If you ever need to delete or suspend that user, this could break your connection to Braintree and result in failed transactions.

Instead, create a new user specifically designated as the API user, whose API keys can be used for your integration. This user should be set up with an email address that is not associated with a single employee and should have Account Admin permissions in order to avoid issues such as an authorization error .

Get production credentialsAnchorIcon

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 settingsAnchorIcon

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 configurationAnchorIcon

In your server code, update your configuration to production values:
  1. Python
gateway = braintree.BraintreeGateway(
    braintree.Configuration(
        braintree.Environment.Production,
        merchant_id="use_your_merchant_id",
        public_key="use_your_public_key",
        private_key="use_your_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 productionAnchorIcon

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.