Legacy 3D Secure
The Braintree sandbox allows end-to-end testing for each of the card brands supported in our 3D Secure integration. The following is a list of test numbers for various card brands:
|Status and Scenario||Card brand specific test values|
Cardholder enrolled, authentication successful, and signature verification successful.
Cardholder enrolled, authentication successful, and signature verification unsuccessful
Cardholder enrolled, authentication unsuccessful, and signature verification successful
An error occurred while attempting to lookup enrollment
Cardholder not enrolled, and issuing bank not participating
Authentication unavailable for this transaction
Merchant not able to execute transactions
Cardholder enrolled, but there was error when attempting to authenticate
Cardholder enrolled, but authentication is not available for this transaction
Bypass used to simulate a scenario where merchant has elected to bypass the consumer authentication flow via CardinalCommerce Rules Engine configuration
See the guide from CardinalCommerce, our 3D Secure authentication provider, for more details on the test card numbers above.
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.
- Production merchant ID
- Production public key
- Production private key
Keep in mind that public and private keys are both environment- and user-specific.
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.
In your server code, update your configuration to production values:
gateway = Braintree::Gateway.new( :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.
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.