Forte is a merchant acquirer and global processor. Forte offers unique and scalable enterprise-class solutions, and helps organizations of all sizes build, manage, and perfect the way they take payments.
Integrating Forte 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 Forte payment gateway directly to Salesforce. The Chargent integration uses the tokenization of the gateway for processing credit card payments, and also offers support for ACH/eCheck payments.
In this section and the next, you’ll find the procedures for configuring the integrations for both Forte and Salesforce. It’s important to follow each of the steps carefully, and in the correct order.Begin by contacting Forte to obtain a merchant account and get credentials—for both a sandbox account and a production account. Many payment companies resell Forte as their payment gateway, so you may also receive credentials from a Forte partner.
It’s essential that you get these credentials for each account:
NOTE: You must get gateway credentials from Forte before moving on to the steps in the next section, Configuring Salesforce For Integration.
Follow these instructions for configuring Forte for integration with Salesforce:
This section contains the procedure for setting up Salesforce for the integration with Forte.
Follow the steps below to configure Salesforce to integrate with Forte:
|Gateway Page Field||Forte Credential|
|Merchant ID||REST Account ID, from your enrollment email message|
|Merchant Security Key||Location ID, from your enrollment email message|
|Merchant Reference||API Login ID (API Access ID), from https://console.forte.net/apis|
|Transaction Security Key||API Secure Key, from https://console.forte.net/apis|
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 Forte sandbox credentials.
Follow the steps below to verify that the integration is correct.
|Card Type||Card Number|
|American Express Corporate||378734493671000|
Note : Even though this number has a different character count than the other test numbers, it is the correct and functional number.
|AVS Result Code||AVS Result Definition|
|Y||Street Address and 5-digit Zip Code both match|
|X||Street Address and 5-digit Zip Code both match|
|A||Partial Match: Street Address matches, but both 5-digit and 9-digit Zip Code do not match|
|W||Partial Match: Street Address does not match, but 9-digit Zip Code matches|
|Z||Partial Match: Street Address does not match, but 5-digit Zip Code matches|
|N||No Match: Street Address, 5-digit Zip Code, and 9-digit Zip Code all do not match|
|U||System Unavailable: Address information unavailable. Forte returns this response if the Street Address is a non-US address, if the AVS service is unavailable, or if the AVS service for a particular US bank is not properly functioning.|
|R||System Unavailable: Forte will retry the AVS check because the issuer's system is unavailable or the request times out.|
|E||Invalid: AVS data is invalid|
|S||Not Supported: The US issuing bank does not support AVS checks.|
|CVV Value||CVV Result Definition|
|E||Error (Unrecognized or Unknown Response)|
|I||Invalid or Null|
|S||Service Not Supported|
|U||Issuer Unable to Process|
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 Forte:
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 Forte gateway, a new transaction record is created. 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.
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 Forte 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 Forte, and the Gateway ID field corresponds to the Forte Transaction ID for use in reconciliation between two systems.
Access your Forte Virtual Terminal to search for transactions and generate reports. Documentation is available for the Virtual Terminal.
To search for transactions: As shown in the figure below, click the Transactions item in the menu on the left, then click the Search button. In the Search Transactions panel, choose From and To dates, and then click the Search button.
The figure below shows how transaction details appear in the Forte Transactions page:
This table contains the mapping information between Forte and Salesforce fields.
|Salesforce field||Direction||Forte field|
|Gateway ID||<||Transaction ID|
|Invoice Number||>||Order ID|
|Order Information||>||Wallet ID|
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 Forte. Forte 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.