☰ Menu

PayTrace Salesforce Integration Chargent

Integrating PayTrace with Salesforce using Chargent

This guide contains instructions for integrating your environment with the PayTrace payment gateway—using the Chargent payment processing plug-in.

Please note that the following PayTrace instructions will also work for any payment gateways that support AIM emulation. You will simply need to use different endpoints.

Click a link to go directly to one of these sections:


PayTrace Inc. is motivated by the challenge of delighting merchants. We empower sales partners by offering high value SaaS technology solutions to businesses. Processing over $22B annually, PayTrace is committed to delighting merchants with 5-star service while providing comprehensive, easy to use payment solutions that lower processing costs and increase security.


Using the step-wise instructions in this guide, it’s easy to connect Salesforce to the PayTrace gateway with Chargent Payment Processing using emulation. 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 PayTrace 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 PayTrace gateway directly to Salesforce.

Obtain a PayTrace Sandbox Account

The first task is to get a test account from PayTrace so that you can run test transactions from Salesforce.

To request a sandbox account, complete the form on the Sandbox Account Request page.

PayTrace Request Sandbox

Upon approval, you’ll receive an email that contains these testing credentials:

  • Username
  • Password

If you need any help, contact PayTrace through their Support page, email at, or by phone at 888-806-6545.

Production account: You’ll also need to register for a production account. Use the contact information in the enrollment email messages to work with PayTrace Support and obtain the same set of credentials for your production account.

NOTE: You must get each of these gateway credentials from PayTrace before moving on to the steps in the next section, Configuring Salesforce For Integration.

Configuring Salesforce for PayTrace Integration

NOTE: You must get each of these gateway credentials from PayTrace before moving on to the steps in the next section, Configuring Salesforce For Integration.

  • The steps in this section are written with the assumption that Chargent has not already been installed into your Salesforce account.

  • Before moving on to the procedure below, you must successfully complete all of the steps given in the previous section, Obtain a PayTrace Sandbox Account.

Follow the steps below to configure Salesforce to integrate with PayTrace:

  1. Install the Chargent Base Package into Salesforce, as we describe on the Chargent Installation page.

    NOTE: Both the sandbox and production installations of Chargent include a free, 30-day trial license.

  2. Install the Chargent Orders Transaction Package in Salesforce, as we describe on the Chargent Installation page.

  3. Complete the basic Chargent setup, such as assigning user licenses and updating page layouts. For more information, please consult our Quick Start Guide.

  4. As shown in the figure at right, select the Chargent item in upper-right corner of Salesforce.

  5. Go the Gateways tab, then click the Create New drop-down, and then select Gateway.

    PayTrace Gateways

  6. Chargent uses emulation to for integrating PayTrace with Salesforce. In the Gateway Record Type panel, select the item from the Record Type drop-down, and then click the Continue button.

    PayTrace Record Type

  7. On the Gateway Edit page, enter the Gateway Name (such as “PayTrace”), which is an internal Salesforce name that you choose for the gateway.

  8. Use the table below for guidance when entering the test credentials that can be found in the email from PayTrace Support:

    Gateway Page Field Value
    Gateway Name Enter an easily recognizable name for this gateway, such as “PayTrace”.
    Merchant ID Your gateway account Username
    Merchant Security Key Your gateway account Password
    Endpoint Override
    Active Check this box

  9. In Salesforce, it’s necessary to add the remote site entry for PayTrace as we explain in the next section ( Enabling a Remote Site in Salesforce).

  10. Your Gateway page should look similar to the figure below. Click the Save button to commit your changes.

    PayTrace Gateway Detail

Enabling a Remote Site in Salesforce

Follow these steps to connect your Salesforce environment to the PayTrace endpoint:

  1. In the left-side menu in Salesforce, navigate to Setup > Administer / Security Controls > Remote Site Settings.

  2. Click the New Remote Site button (see the figure below).

    PayTrace Remote Site

  3. For the new remote site, enter “PayTrace” for the Remote Site Name.

  4. Enter “” for the Remote Site URL.

  5. Click Save.

Testing the PayTrace Integration

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 PayTrace sandbox credentials.

Follow the steps below to verify that the integration is correct.

  1. In the upper-left corner of the Salesforce page, click the + tab to open the All Tabs page.

  2. In the tabs listing, locate the link that corresponds to the Chargent Transaction Package that you installed during the Configuring Salesforce For Integration procedure.

  3. 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).

    PayTrace Testing All Tabs

  4. On the next page, click the New button (see the figure below).

  5. As shown on the PayTrace Testing Information page, these are valid test credit card numbers.

    Card Type Card Number CSC
    Visa 4012000098765439 999
    MasterCard 5499740000000057 998
    Discover 6011000993026909 996
    American Express 371449635392376 9997
  6. On the PayTrace Testing Information page, these is test data for Bank Account. However it doesn’t work with Chargent.

    Account Number Routing Number
    123456 325070760
  7. For PayTrace, submission of $0.50, $1.00 or more amount (except $1.12, $1.13) should give an approval response. Amounts such as $0.20, $0.21, $0.29 will cause the return of a DECLINE message. The full list of testing amounts can be found on PayTrace Testing Information page in Testing Amount section.

  8. Expiration dates in the future are returned as valid; expiration dates in the past are returned as invalid.

  9. In the Chargent Order Edit page, enter or select information to correctly complete the essential parts of the form, including:

    • Gateway
    • Billing First Name
    • Billing Last Name
    • Billing Address (City, State, Zipcode)
    • Billing Email Address (to get a receipt)
    • Charge Amount (check Manual Charge if this amount is not calculated from Subtotal + Tax + Shipping)
    • Payment Method
    • Card Type
    • Card Number
    • Card Expiration Month
    • Card Expiration Year (use a future year)
    • Card Last 4

  10. See the figure below for the placement of these fields.

    PayTrace Testing Fields

  11. Click the Save button to commit the changes on the form. On the next page, click the Charge button (as shown below).

    Paysafe Charge

  12. When the transaction is complete, you see a small pop-up as shown in this figure. Click the OK button to close the pop-up window, then scroll to the bottom of the Order page.

    PayTrace Approve Sale

  13. A record is created for each error and each successful transaction, and this record contains the response messages and details that are sent back from PayTrace. See the figure below for an example.
    PayTrace Transactions

Sending Live Transactions from a Salesforce Sandbox

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 PayTrace:

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).

Understanding Transactions

When a transaction occurs between Chargent and the PayTrace 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 PayTrace 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.

PayTrace Chargent Order Detail

You can compare the transaction records in Salesforce with the records in your PayTrace administrative app. As shown in the figure below, click the Dashboard menu category, then click View Transactions. Then click the link for a specific transaction to view details.

PayTrace Dashboard

On the opened form perform search of the transaction using any available field, e.g. Order ID. When the transaction is found, click on the ID link in Search Results section to view the transaction details.

PayTrace View Transactions


Correspondence in the Transaction Fields

The Gateway Date is the timestamp for the submission to PayTrace, and the Gateway ID field corresponds to the PayTrace Transaction ID for use in reconciliation between two systems.

This table contains the mapping information between PayTrace and Salesforce fields.

Salesforce field Direction Gateway field
Gateway ID < Transaction ID
Invoice Number > Invoice
PO Number > Customer Reference

Going Live

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.

  1. First, obtain the production credentials for the PayTrace production gateway account (similar to the method given for sandbox credentials in Obtain a PayTrace Sandbox Account.

  2. Get these production credentials from your enrollment email message:
    • Username
    • Password

  3. Repeat the steps in the Configuring Salesforce for PayTrace Integration section above, but substitute the production credentials.

  4. For the production Endpoint Override field, enter the production endpoint received from PayTrace support team

  5. Repeat the steps in the Testing the PayTrace Integration section above with respect to the SalesForce production environment, using the production credentials.

  6. Void the transactions: If you’re using an actual credit card and want to prevent the charge from settling, remember to void the transaction after testing.

  7. Be sure to successfully transmit at least one real credit card transaction using company or personal accounts. We recommend that you submit a transaction with a very small amount and then void that transaction afterwards. This ensures that the system works with your production credentials.