Using the Chargent payment processing plug-in, you can integrate your Salesforce.com environment with the Fat Zebra payment gateway. Accept credit card and direct debit payments from your customers in Australia and worldwide, all directly from inside Salesforce.
This guide contains easy—yet complete—instructions for performing this integration. Click a link to go directly to one of these sections:
Fat Zebra is an Australian provider of technology-enabled payment processing for merchants and suppliers. It provides simple methods for merchants to accept credit card payments online while still maintaining a strong focus on security, reliability, and great user experience. The Fat Zebra online payment gateway gives merchants all the features and benefits they expect, with no hidden fees or charges.
Using the simple instructions in this guide, it’s easy to connect Salesforce to the Fat Zebra gateway with Chargent Integrated Payments for Salesforce. Chargent has many features to offer, including automating and streamlining Salesforce payment processes, support for both Credit Card and Direct Debit transactions, easy subscription management, click-to-charge buttons, payment request emails, and more.
Integrating Fat Zebra with Chargent gives you the ability to easily build a seamless process for completing payment for orders that you manage in Salesforce. The integration connects the Fat Zebra gateway directly to Salesforce. Optionally, Chargent enables gateway tokenization for processing credit card payments, and also offers support for direct debit payments in Australia. See Setting Up Salesforce For Integration for additional information on the gateways.
The first task is to get a test account from Fat Zebra so that you can run test transactions from Salesforce. To request a sandbox account, complete the form on the Registration Page page.
Upon approval, you’ll receive an email that contains these testing credentials:
Production account: You’ll also need to register for a production account. Use the contact information in the enrollment email messages to work with Fat Zebra Support and obtain the same set of credentials for your production account.
NOTE: You must get each of these gateway credentials from Fat Zebra before moving on to the steps in the next section, Configuring Salesforce For Integration.
Follow the steps below to configure Salesforce to integrate with Fat Zebra:
|Gateway Page Field||Value|
|Gateway Name||Enter an easily recognizable name for this gateway, such as “Fat Zebra Test”.|
|Merchant ID||Your username.|
|Merchant Security Key||Your password|
|Test Endpoint||Check this box|
|Active||Check this box|
This section contains the procedure for testing the integration that you set up according to the procedure given in Setting Up Salesforce For Integration, using your Fat Zebra sandbox credentials.
Valid currencies: AUD is the primary currency for this gateway. Contact Fat Zebra Support if you need to use another Asian currency.
Follow these steps to test that the integration functions correctly.
See the figure below, which indicates Chargent Orders for the purpose of illustration. (If you installed the Chargent Opportunities or Cases package, you would use that object for testing).
|Card Type||Card Number||Expiry||CVV||Amount||Response|
|MasterCard||5123 4567 8901 2346||05/2023||123||Any||Approved|
|MasterCard||5313 5810 0012 3430||05/2023||123||Any||Declined|
|MasterCard||5555 5555 5555 4444||05/2023||123||Varying||Depends on cent amount|
|VISA||4005 5500 0000 0001||05/2023||123||Any||Approved|
|VISA||4557 0123 4567 8902||05/2023||123||Any||Declined|
|VISA||4111 1111 1111 1111||05/2023||123||Varying||Depends on cent amount|
|AMEX||3456 7890 1234 564||05/2023||1234||Any||Approved|
|AMEX||3714 4963 5398 431||05/2023||1234||Any||Declined|
|AMEX||3787 3449 3671 000||05/2023||1234||Varying||Depends on cent amount|
|JCB||3530 1113 3330 0000||05/2023||123||Any||Approved|
|JCB||3566 0020 2036 0505||05/2023||123||Any||Declined|
|JCB||3569 9900 0000 0009||05/2023||123||Varying||Depends on cent amount|
|Order Source Field Value||Fat Zebra value||‘ecm’ value|
|Corporate Cash Disbursement||N/A||N/A|
|E-commerce||Internet order (Single)||31|
|Installment||Internet order (Installment)||33|
|Mail order (Single)||21|
|Prearranged Payment and Deposit||N/A||N/A|
|Recurring||Internet order (Recurring)||32|
|Recurring Mail||Mail order (Recurring)||22|
|Recurring Telephone||Telephone order (Recurring)||12|
|Telephone||Telephone order (Single)||11|
When Chargent is installed in a Salesforce Sandbox, transactions are always sent to the payment gateway's test / sandbox / development environment, regardless of whether Chargent's Test Endpoint checkbox is checked. This is done as a security precaution, to prevent real transactions from being accidentally sent from a Salesforce Sandbox.
When Chargent is installed in a production or developer Salesforce org, the Test Endpoint checkbox on the Gateway record will select between sending to the payment gateway's live and test environments. (There are a few exceptions, such as Stripe, which has a single endpoint to send transactions to, and different credentials for live versus test transactions).
If you wish to send live transactions from a Salesforce Sandbox, as a final step in testing, simply use Chargent's Endpoint Override field on the Gateway record, and enter the production endpoint of your chosen gateway there.
Here is the production endpoint URL for Chargent's integration with Fat Zebra:
Note that the full endpoint URL must be entered in the Endpoint Override field, and the domain must be present in the Remote Site Settings (for standard Chargent integrations it should be already present).
When a transaction occurs between Chargent and the Fat Zebra gateway, a new transaction record is created in Salesforce. The listing of transactions can be found in the Transaction section near the bottom of the Chargent Order page (or Opportunities or Cases, if you are using those packages). See the figure above.
On the order page, scroll down to that Transactions section and click a Transaction ID link to see the details, as shown in the figure below. This transaction record contains the entire set of data that Fat Zebra sends in its response, including transaction Type (Charge, Authorize, Refund or Void), the Response Status (Approved, Declined, Error), and any related approval or error messages.
You can compare the transaction records in Salesforce with the records in your Fat Zebra administrative app. As shown in the figure below, click the Processing menu category, then click Transactions > Transaction List. Then click the link for a specific transaction to view details.
The Date is the timestamp for the submission to Fat Zebra, and the Gateway ID field corresponds to the Fat Zebra Transaction ID for use in reconciliation between two systems.
This table contains the mapping information between Fat Zebra and Salesforce fields.
|Salesforce field||Direction||Fat Zebra field|
|Gateway ID||<||Transaction ID|
|Invoice Number||>||Invoice Number|
|Order/Opp/Case Record ID||>||Customer ID|
|Order Information||>||Order Information (credit cards) or Description (Direct Debit)|
This section contains the procedure for configuring the integration in a production system.
NOTE: Do not proceed here until the testing procedure described in Testing the Integration is successful.
Chargent supports Fat Zebra tokenization for credit card transactions (though not for direct debit, which is the Australian version of ACH/eCheck). This section contains the procedure for configuring the use of tokens that pass between Chargent and Fat Zebra. Tokens are used to improve security by replacing account numbers in Salesforce, and referencing the data securely stored at Fat Zebra.
NOTE: After your first successful transaction, the token is stored in the Chargent Token field in Salesforce and the credit card fields are handled according to the choice in the Credit Card Data Handling field.