This guide contains instructions for integrating your Salesforce.com environment with the Merchant Warrior payment gateway—using the Chargent payment processing plug-in.
Click a link to go directly to one of these sections:
Merchant Warrior is an Australia based payment provider that offers a range of online payment solutions to merchants worldwide. Merchant Warrior prides itself in establishing and maintaining a healthy relationship with each of its clients, achieving this by working in synergy with its clients to gain insight into their individual requirements and by providing them with a solution that caters wholly to those requirements.
Using the stepwise instructions in this guide, it’s easy to connect Salesforce to the Merchant Warrior gateway with Chargent Payment Processing. Chargent has many features to offer, including automating and streamlining Salesforce payment processes, easy subscription management, click-to-charge buttons, payment request emails, and more.
Integrating Merchant Warrior 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 Merchant Warrior gateway directly to Salesforce. Chargent also supports Merchant Warrior gateway tokenization for processing credit card payments. See Configuring Salesforce for Merchant Warrior Integration for additional information on the gateways.
The first task is to get a sandbox / test account from Merchant Warrior so that you can run test transactions from Salesforce.
To request a sandbox account, complete the form on the Test Account Application page.
Upon approval, you’ll receive an email that contains these testing credentials:
From the Merchant Warrior main page, click the Merchant Login button—as shown in the figure below.
Login with your username and temporary password, and then continue to the next section.
Need help? Contact Merchant Warrior through the options given on their Support page.
On your first successful login, you’ll get a prompt to enter a permanent password of your own choosing. The password must be:
When you log in with your permanent password, you’ll see Merchant Warriot dashboard. Click the Direct API menu item along the left side, as shown in the figure.
Take note of the three identifying elements on the Direct API page. You will need each of these to configure the gateway connection in Salesforce:
See the next section, Configuring Salesforce for Merchant Warrior Integration.
Production account: You’ll also need to register for a production account. When you’re ready, use the contact information in the enrollment email messages to work with Merchant Warrior Support and obtain the same set of credentials for your production account.
NOTE: You must get each of these gateway credentials from Merchant Warrior before moving on to the steps in the next section, Configuring Salesforce for Merchant Warrior Integration.
Follow the steps below to configure Salesforce to integrate with Merchant Warrior:
NOTE: Both the sandbox and production installation of Chargent include a free, 30-day trial license.
|Gateway Page Field||Value|
|Gateway Name||Enter an easily recognizable name for this gateway, such as “Merchant Warrior Test”.|
|Merchant ID||Merchant Warrior UUID|
|Merchant Security Key||Merchant Warrior API Key|
|Merchant Reference||Merchant Warrior API Passphrase|
|Test Endpoint||Check this box|
|Active||Check this box|
NOTE: The Merchant Warrior UUID, API Key, and API Passphrase are taken from your Merchant Warrior dashboard. See the section above, Get your Merchant ID, API Key, and Passphrase.
This section contains the procedure for testing the integration that you set up according to the procedure given in Configuring Salesforce for Merchant Warrior Integration, using your Merchant Warrior sandbox credentials.
Follow the steps below to verify that the integration is correct.
See the figure to the right, 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 Date||CVN|
|XXX.01||Transaction declined - contact issuing bank|
|XXX.05||Transaction declined – contact issuing bank|
|XXX.10||Transaction could not be processed|
|XXX.54||Card has expired|
|XXX.68||No reply from Processing Host|
|Anything Else||Transaction could not be processed|
See the figure below for the placement of these fields.
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 Merchant Warrior:
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 Merchant Warrior 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 Merchant Warrior 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 Merchant Warrior dashboard. Login to Merchant Warrior, and then click Reports > Transaction Summary. See the figure below.
Click anywhere on the transaction row to see all details for that transaction.
The Gateway Date is the timestamp for the submission to Merchant Warrior, and the Gateway ID field corresponds to the Merchant Warrior Transaction ID for use in reconciliation between two systems.
This table contains the mapping information between Merchant Warrior and Salesforce fields.
|Salesforce field||Direction||Gateway field|
|Gateway ID||<||Transaction ID|
|Invoice Number||>||Transaction Product|
This section contains the procedure for configuring the integration in a production system.
NOTE: It’s important that you do not proceed here until the testing procedure described in Testing the Integration is successful.
Chargent supports Merchant Warrior 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 Merchant Warrior. Tokens are used to improve security by replacing account numbers in Salesforce, and referencing the data securely stored at Merchant Warrior.
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.