Merchant e-Solutions is a merchant acquirer and global processor that processes over $17 billion in transactions annually in 150 different global currencies.
Integrating Merchant e-Solutions (MeS) 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 e-Solutions payment gateway directly to Salesforce. The Chargent integration uses the tokenization of the gateway tokenization for processing credit card payments, but does not currently support ACH/eCheck payments. See Setting Up Salesforce For Integration for additional information on the gateways.
In this section and the next, you’ll find the procedures for configuring the integrations for both Merchant e-Solutions and Salesforce. It’s important to follow each of the steps carefully, and in the correct order.
Begin by contacting Merchant e-Solutions to obtain a merchant account and get credentials—for both a sandbox account and a production account.
You should get these two credentials for each account:
NOTE: You must get gateway credentials from Merchant e-Solutions before moving on to the steps in the next section, Configuring Salesforce For Integration.
Follow these instructions for configuring e-Solutions for integration with Salesforce:
This subsection contains the procedure for setting up Salesforce for the integration with Merchant e-Solutions.
Follow the steps below to configure Salesforce to integrate with Merchant e-Solutions:
This section contains the procedure for testing the integration set up in Setting Up Salesforce For Integration, using your Merchant e-Solutions sandbox credentials in Salesforce.
Follow the steps below to ensure that the integration is correct.
|Card Type||Length||Card Number|
|Street Address||ZIP Code||AVS Result Code|
|123||55555||Y - street and postal code match|
|123||999991111||Y - street and postal code match (Visa) X - street and postal code match (MasterCard)|
|123||EH8 9ST||D - exact match, international|
|123||Other Zip||A - address match, zip mismatch|
|234||Any ZIP||U - address unavailable|
|345||Any ZIP||G - verification unavailable due to international issuer non-participation (Visa and MasterCard only)|
|456||Any ZIP||R - issuer system unavailable, retry|
|235||Any ZIP||S - AVS not supported|
|Other Address||55555||Z - address mismatch, 5-digit zip match|
|Other Address||EH8 9ST||Z - address mismatch, international zip match|
|Other Address||999991111||Z - address mismatch, zip match (Visa) W - address mismatch, zip match (MasterCard)|
|Other Address||Other ZIP||N - address and zip mismatch|
|CVV / CVC Value||Result Code|
|123||M - Match|
|234||P - Not Processed|
|345||U - Issuer is not certified|
|else||N - No Match|
|Amount||Response Code||Auth response text||Reason/Description|
|0.00||085||"Card OK"||For card verification testing, submit a transaction code=A|
|0.01||001||"Call"||Refer to issuer|
|0.02||002||"Call"||Refer to issuer - special condition|
|0.04||004||"Hold-call"||Pick up card (no fraud)|
|0.05||005||"Decline"||Do not honor|
|0.07||007||"Hold-call"||Pick up card (fraud)|
|0.14||014||"Card No. Error"||Invalid card number|
|0.15||015||"No Such Issuer"||Invalid card number|
|0.19||019||"RE Enter"||Re-enter transaction|
|0.41||041||"Hold-call"||Pick up card (fraud: lost card)|
|0.43||043||"Hold-call"||Pick up card (fraud: stolen card)|
|0.54||054||"Expired Card"||Issuer indicates card is expired|
|0.57||057||"Serv Not Allowed"||Transaction not permitted to cardholder|
|0.59||059||"Suspected Fraud"||Do not honor card|
|0.84||084||"Invalid Auth"||Invalid Authorization Life Cycle|
|0.86||086||"Can't Verify P"||System is unable to validate the Pin #|
|1.00||0TA||"CT NOT ALLOWED"||Merchant does not accept this type of card|
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 e-Solutions:
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 e-Solutions gateway, a new transaction record is created, which 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).
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 e-Solutions sends in its response, including transaction Type (Charge, Authorize, Refund or Void), the Response Status (Approved, Declined, Error).
The Gateway Date is the timestamp for the submission to Merchant e-Solutions, and the Gateway ID field corresponds to the Merchant e-Solutions Transaction ID for use in reconciliation between two systems.
NOTE: Merchant e-Solutions does not provide an online reporting interface for test / sandbox accounts. Online reporting is only available for production accounts.
See the figure below.
The figure below depicts how the same transaction appears in the Merchant e-Solutions Transactions page:
This table contains the mapping information between some key Merchant e-Solutions and Salesforce fields.
|Salesforce field||Direction||Merchant e-Solutiions field|
|Gateway ID||<||Transaction ID|
|Invoice Number||>||Invoice Number|
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.
NOTE: Remember to void the transaction after testing, if you are using a real credit card and want to prevent the charge from settling.
This section contains the procedure for configuring the use of tokens that pass between Chargent and Merchant e-Solutions. Merchant e-Solutions uses a token system to maximize data security.
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.