Once you have completed some test transactions to see how Chargent works, you are almost ready to go live.
If you will be doing recurring or subscription billing, you should have the option to set up the recurring batch when you setup your gateway. If not, you should set up the Apex batch and a few records with the Chargent recurring fields set correctly, so you can use the test Braintree gateway to be sure that everything is configured properly and behaves as you expect before going live with real customer transactions.
In addition, at this point you can complete any customizations to the Chargent system or Salesforce configuration you might want to do, such as workflow automation, email template customization, triggers, etc.
To process real transactions with Braintree from Salesforce, you will need to deactivate the test gateway record (uncheck the Active field), and create a new live Gateway record in Salesforce with the production credentials provided by Braintree.
Note that the Sandbox and Production accounts are completely separate, so you will need to make sure any settings in Sandbox are reapplied in your Production account.
If you have not applied for a Braintree production account, you can sign up here.
- Setup your payment gateway in Production via the instructions above – v5.40 or older or using the Gateway Setup Wizard in current versions
- Create a Transaction Record using real credit card data
You may wish to test a few live transaction with a real credit card, just to make sure everything is working smoothly.
Real credit card numbers must be used in production. The test cards for the Sandbox will not work.
Run small dollar amount transactions — you can either VOID them immediately after, to minimize any impact, or allow them to settle to confirm the small amounts are deposited into your bank account
Using your own or company credit cards for live tests is recommended, as customers could still see notifications of a charge even if voided
Note that Transaction fees are incurred in the live environment, so extensive testing in production is not recommended. Run a small number of small value transactions to complete your testing.