AppFrontier

☰ Menu

USAePay Salesforce Integration Chargent


Integrating USAePay with Salesforce using Chargent

Overview


USAePay has provided a secure credit card and check processing gateway for over 15 years. The gateway supports all major credit card platforms and most leading check platforms. The gateway is Level 1 PC1 compliant, enforcing the latest and strictest security requirements for the payment industry.

Integration of USAePay with Chargent Payment Processing for Salesforce allows the ability to provide a seamless process for completing payment for orders managed in Salesforce. The connection of Salesforce and USAePay allows real-time and recurring payments between the two systems. Chargent tokenizes credit cards and stores them in Salesforce for future use by the merchant (ACH/eChecks are not tokenized through USAePay). See Setting Up Salesforce For Integration for additional information on the gateway.

USAePay Logo

Setting Up Integration


This section contains the procedures for setting up the integration between USAePay and Salesforce. Each subsection under this section contains a separate procedure, however, the procedures must be completed in the order presented.

Setting Up USAePay for Integration

This subsection contains the procedure for setting up USAePay for the integration with Salesforce. Note: This procedure must be completed before starting Setting up Salesforce.

Setting Up USAePay Testing Integration

This subsection contains the procedure needed for Testing the Integration.

  1. Register up for a developer’s account at https://www.usaepay.com/developer/login if don’t have a developer’s account. Note: You will receive an Email containing your sandbox (test) credentials.

  2. Log into your sandbox using the credentials received in step 1 at https://sandbox.usaepay.com/login.

  3. Click Settings in Merchant’s console.

    USAePay Testing Merchant console

  4. Click Source Keys

    USAePay Source Key

  5. Click Add Source

    USAePay Add Key

  6. Enter Name and Pin. Click Apply.

    USAePay Name and Pin

  7. Note Key and Pin to be used for Setting Up Salesforce For Integration. Click Save. Note: This Key and Pin will be used for Testing the Integration.

    USAePay Key and Pin

Setting Up USAePay Live Integration

This subsection contains the procedure needed for Going Live.

  1. Merchant signs up for payment processing account with a USAePay reseller. USAePay works through resellers and does not provide payment gateway accounts directly to merchants.

  2. Note: Merchant will receive the credentials for signing into the Merchant’s Console in a letter or Email after signing up for gateway account.

  3. Merchant logs into gateway account in letter or Email containing credentials.

  4. Click Settings in Merchant’s console.

    USAePay Testing Merchant console

  5. Click Source Keys

    USAePay Source Key

  6. Click Add Source

    USAePay Add Key

  7. Enter Name and Pin. Click Apply.

    USAePay Name and Pin

  8. Note Key and Pin to be used for Setting Up Salesforce For Integration. Click Save. Note: This Key and Pin will be used for Testing the Integration.

    USAePay Key and Pin


Setting Up Salesforce For Integration with USAePay

This subsection contains the procedure for setting up Salesforce for the integration with USAePay.

Notes:

  1. Install Chargent’s Gateway Package in Salesforce as described at Chargent Installation. Note: The production installation includes a free 30 day trial license. The sandbox installation has a free developer’s license.

  2. Install one of Chargent’s Transaction Packages in Salesforce as described at Chargent Installation. Note: The Transaction Packages are Chargent Orders, Opportunities, or Cases.

  3. Configure the basics of Chargent, such as assigning user licenses and updating page layouts. For more information please consult our Quick Start Guide.

  4. Select Chargent app in upper right hand corner of Salesforce.

    Chargent

  5. Click the Gateways tab.

    Chargent

  6. Click New.

    Chargent

  7. Select USAePay record type. Click Continue.

    Chargent

  8. Select USAePay record type. Click Continue.
    • Gateway Name - Internal Salesforce name for gateway. You can name it any name that you wish.
    • Merchant ID - Key retrieved in Setting Up USAePay For Integration.
    • Merchant Security Key - PIN retrieved in Setting Up USAePay For Integration.
    • Active - should be checked.
    • Test Endpoint - should be checked when using your USAePay Sandbox account, unchecked when going live with your production credentials.


    Chargent

  9. Click Save.


Testing the Integration


This section contains the procedure for testing the integration set up in Setting Up AvidiaPay/Salesforce Integration. This section contains the procedure for testing the integration set up in Setting Up USAePay Testing Integration, using USAePay’s test credentials in Salesforce.

  1. Click on tab that corresponds to the Chargent Transaction Package that was installed during the Setting Up Salesforce procedure. For the purposes of this example, Order was installed.

    Testing Chargent Orders

  2. Click New.

    Testing Chargent New

  3. Enter Subtotal / Amount, Gateway (entered during Setting Up Salesforce For Integration), Payment Information, Billing Information (including Email), and Credit Card fields and click Save.

  4. Test Credit Cards -- These credit card numbers are only for USAePay Test accounts. Real credit card numbers should not be used in the test environment.:

    • The following credit cards will return with approved transaction status regardless of amount: Note: All of the credit card numbers have the expiration date 09/19.

      • 4000100011112224 and 4000100111112223 with the CVV “123”
      • These credit card numbers all have the CVV “999”

        • 4000100211112222, 4000100311112221, 4000100411112220, 4000100511112229, 4000100611112228, 4000100711112227, 4000100811112226, 4000100911112225, 4000101011112222, 4000101111112221, 4000101211112220, 4000101311112229, 4000101411112228, 4000101511112227, 4000101611112226

        • 4000300011112220, 4000300001112222, 4000300111112229, 4000300211112228, 4000300311112227, 4000300411112226, 4000300511112225, 4000300611112224, 4000300711112223, 4000300811112222, 4000300911112221, 4000301011112228, 4000301111112227, 4000301211112226, 4000301311112225

        • 4000600011112223, 4000600111112222, 4000600211112221, 4000600311112220, 4000600411112229, 4000600511112228, 4000600611112227, 4000600711112226, 4000600811112225, 4000600911112224, 4000601011112221, 4000601111112220

        • 4000700011112221, 4000700111112220, 4000700211112229, 4000700311112228, 4000700411112227, 4000700511112226, 4000700611112225, 4000700711112224, 4000700811112223, 4000700911112222, 4000701011112229, 4000701111112228, 4000701211112227, 4000701311112226, 4000701411112225, 4000701511112224, 4000701611112223, 4000701711112222, 4000701811112221, 4000701911112220

      • These credit card numbers will accept any CVV

        • 4000200011112222, 4000200111112221, 4000200211112220, 4000200311112229, 4000200411112228, 4000200511112227

        • 5555444433332226, 5555444433332234, 5555444433332242, 5555444433332259, 5555444433332267, 5555444433332275

        • 3711222233322225, 3711222233322233, 3711222233322241

        • 6011222233332224, 6011222233332232, 6011222233332240, 6011222233332257, 6011222233332265, 6011222233332273

    • ACH / check processing test data:

      • Routing number 987654321 with any account number and amount will return an invalid routing number error.
      • Amount 5.99 with any routing and account numbers will return a returned check for this account decline.
      • Amount 9999.99 with with any routing and account number will return an allocated monthly transaction volume warning.


    Testing Chargent Charge

  5. Click Charge.

    Testing Chargent Charge

  6. Verify successful transaction and click OK.

    Testing Chargent Successful Transaction

  7. A Transaction record is created, containing the response messages and details received from USAePay.

Going Live


This section contains the procedure for making the integration available for production systems. This procedure should not occur until the testing procedure described in Testing the Integration is successful.

  1. Complete Setting Up USAePay Live Integration.
  2. Repeat Setting Up Salesforce For Integration for production Salesforce.
  3. Repeat Testing the Integration for production integration using the production Key and PIN obtained during Setting Up USAePay Live Integration, at least one real credit card transaction, and one real ACH transaction using company or personal accounts. Note: Void the transaction after test if needed.

Understanding Transactions


When a successful transaction is generated in USAePay from Chargent / Salesforce, a Transaction record is created in Salesforce with the results. This transaction record contains a complete set of data returned from USAePay, such as the type of transaction (Charge, Authorize, Refund or Void), the Response Message (Approved, Declined, Error) as well as various response and result codes (detailed below).

The Salesforce Transaction Gateway Date shows the date and time it was submitted to USAePay, and Chargent’s Gateway ID field in Salesforce corresponds to the Transaction ID in USAePay for use in reconciling systems.

A Transaction Record from Chargent in Salesforce:

Chargent Transaction

The Corresponding Transaction record in USAePay:

Chargent Transaction


Troubleshooting & Response Codes

Common Errors

  1. Gateway Message: “Customer Name Not Submitted”
    Make sure you have the Name and Billing Address completed in your Opportunity, Case, or Chargent Order record. Incomplete information can create this error.

  2. Transaction Authentication Failed
    This indicates that either your USAePay key / pin combination entered in the Chargent Gateway record in Salesforce are incorrect, or that you may be sending to the wrong environment to match your credentials. When using the USAePay Sandbox for testing, make sure “Test Endpoint” is checked in the Gateway record, and for production usage make sure it is unchecked.

AVS Codes

USAePay will return AVS codes with their transactions. The following are the list of codes and their definitions:

Code Alternates Meaning
YYY Y, YYA, YYD Address: Match & 5 Digit Zip: Match
NYZ Z Address: No Match & 5 Digit Zip: Match
YNA A, YNY Address: Match & 5 Digit Zip: No Match
NNN N, NN Address: No Match & 5 Digit Zip: No Match
YYX X Address: Match & 9 Digit Zip: Match
NYW W Address: No Match & 9 Digit Zip: Match
XXW Card Number Not On File
XXU Address Information not verified for domestic transaction
XXR R, U, E Retry / System Unavailable
XXS S Service Not Supported
XXE Address Verification Not Allowed For Card Type
XXG G,C,I Global Non-AVS participant
YYG B, M International Address: Match & Zip: Not Compatible
GGG D International Address: Match & Zip: Match
YGG P International Address: No Compatible & Zip: Match

CVV2 Response Codess

USAePay will return CVV2 response codes with their transactions. The following are the list of codes and their definitions:

Code Meaning
M Match
N No Match
P Not Processed
S Should be on card but not so indicated
U Issuer Not Certified
X No response from association
(blank) No CVV2/CVC data available for transaction.

CAVV Response Codes

USAePay will return CAVV response codes with their transactions. The following are the list of codes and their definitions:

Code Meaning
0 Failed validation – authentication
1 Failed validation – authentication
2 Passed validation – authentication
3 Passed validation – attempt (Authentication was attempted)
4 Failed validation – attempt (Authentication was attempted)
5 Reserved – not used
6 Not validated, issuer not participating
7 Failed validation - attempt (Authentication attempt was performed)
8 Passed validation – attempt (Authentication attempt was performed)
9 Failed validation - attempt (Visa generated, issuer’s ACS was not available)
A Passed validation – attempt (Visa generated, issuer’s ACS was not available)
B Passed validation - information only, no liability shift. (Card or transaction type not eligible for the 3-D Secure service.)
C Not validated – attempt (Issuer did not return a CAVV results code in the authorization response)
D Not validated - authentication (Issuer did not return a CAVV results code in the authorization response)

Card Level Codes

USAePay will return card level codes with their transactions. The following are the list of codes and their definitions:

Code Description
A Visa Traditional
B Visa Traditional Rewards
C Visa Signature
D Visa Signature Preferred
G Visa Business
H Visa Consumer Check Card
I Visa Commerce
K Visa Corporate
M MasterCard/EuroCard and Diners
S Visa Purchasing
U Visa TravelMoney
G1 Visa Signature Business
G2 Visa Business Check Card
J1 Visa General Prepaid
J2 Visa Prepaid Gift Card
J3 Visa Prepaid Healthcare
J4 Visa Prepaid Commercial
K1 Visa GSA Corporate T&E
S1 Visa Purchasing with Fleet
S2 Visa GSA Purchasing
S3 Visa GSA Purchasing with Fleet
DI Discover
AX American Express

Decline Codes

USAePay will return decline codes with declined transactions. The following are the list of codes and their definitions:

Decline Code Message
- Declined
04 Pickup Card
05 Do not Honor
12 Invalid Transaction
15 Invalid Issuer
25 Unable to locate Record
51 Insufficient funds
55 Invalid Pin
57 Transaction Not Permitted
62 Restricted Card
65 Excess withdrawal count
75 Allowable number of pin tries exceeded
78 No checking account
97 Declined for CVV failure

Error Codes

The following is the list of error codes that can be returned with transactions that generate an error.

Numeric Code Description Additional Information
00001 Password/Username Incorrect. Sent by login screen when the username and/or the password are incorrect.
00002 Access to page denied. The user has attempted to access a page they don't have permission to access.
00003 Transaction type [type] not supported. Please contact support. Is returned by /console/vterm.php when an unknown transaction type (sale, credit, etc) is attempted.
00004 Processing gateway currently offline. Please try back in a few moments. Return by processing engine when the gateway cannot establish a connection with the processing backend.
00005 Error in verification module [module]. Please contact support. The given fraud module was did not load correctly. An upgrade may be in progress.
00006 Merchant not found. The system was not able to locate the requested merchant.
00007 Merchant has been deactivated. Merchant account has been marked as deactivate. Contact USAePay customer service.
00008 Unable to retrieve current batch. Failed to get the id of the current batch. Typically this indicates that the merchant account is not active or batches are out of sync. Verify all merchant account info provided to usaepay.
00009 Unable To Create Transaction. Please Contact Support. Internal database error, system may be in the process of failing over to backup database server. Retry transaction.
00010 Unable To Allocate Transaction Slot. Please contact support. Internal database error, system may be in the process of failing over to backup database server. Retry transaction.
00011 Invalid Card Number (1) The cardnumber contains illegal characters. A card number may only include numbers.
00012 Invalid Card Number (2) Card Number was not between 13 and 16 digits.
00013 Invalid Card Number (3) Cardnumber failed Luhn Mod-10 Checkdigit Method (ISO 2894/ANSI 4.13)
00014 Invalid Credit Card Number (1) Cardnumber passed length, format and checkdigit tests but didn't match any of the cardnumber profiles enabled in the system. Contact USAePay to verify support of cardtype.
00015 Invalid expiration date. Must be in MMYY format. Expiration contains invalid characters (nothing but numbers allowed)
00016 Invalid expiration date. Must be in MMYY format. Could not guess format of date. It wasn't MMYY or MMYYYY or MMDDYYYY or even MMDDYY format.
00017 Credit card has expired. The credit card expiration date has passed.
00018 Gateway temporarily offline. Please try again shortly. Unable to contact processor backend. Failed bank link maybe in the process of coming back up. Retry transaction.
00019 Gateway temporarily offline for maintenance. Please try again in a few minutes. Processor backend is offline for maintenance. Retry transaction.
00020 User not configured correctly, please contact support. User not configured correctly. Remove the user and readd.
00021 Invalid username. The merchant didn't type in a valid username when adding a new user.
00022 You do not have access to this page. The user tried to access a page they don't have permission to access.
00023 Specified source key not found. The source key provided did not match any of the currently active keys.
00024 Transaction already voided. The transaction was already marked as voided and wasn't going to be settled anyway.
00025 Unable to find transaction in batch. The batchid on the transaction references a batch that doesn't exist. If there isn't a valid batch then trying to void a transaction isn't going to do much.
00026 The batch has already been closed. Please apply a credit instead. The specified transaction has already been settled. Once a transaction has been sent in for settlement it can not be voided.
00027 Gateway temporarily offline. Please try again shortly. (2) Error communicating with the processing backend. Retry transaction.
00028 Unable to verify source. VerifySource couldn't find the source or the source was disabled.
00029 Unable to generate security key. VerifySource wasn't able to create a source on the fly. Trouble finding a key.
00030 Source has been blocked from processing transactions. Merchant has disabled the specified source key.
00031 Duplicate transaction, wait at least [minutes] minutes before trying again. The duplicate transaction fraud module detected a dupe.
00032 The maximum order amount is $[amount]. Fraud module response.
00033 The minimum order amount is $[amount]. Fraud module response.
00034 Your billing information does not match your credit card. Please check with your bank. AVS Response fraud module blocked this transaction.
00035 Unable to locate transaction. Was not able to find the requested transaction for voiding.
00036 Gateway temporarily offline for maintenance. Please try again in a few minutes. VeriCheck link has been brought down for maintenance. Retry transaction.
00037 Customer Name not submitted. Cardholder field was blank.
00038 Invalid Routing Number. Check Routing number did not meet requirement of 9 digits.
00039 Invalid Checking Account Number. Check Account number is not at least 4 digits long.
00040 Merchant does not currently support check transactions. The merchant doesn't have a valid tax id or password entered for check processing.
00041 Check processing temporarily offline. Please try again shortly. Internal system error encountered while communicating with check processor. Please contact USAePay support.
00042 Temporarily unable to process transaction. Please try again shortly. A corrupted response (unparsable) was received from vericheck.
00043 Transaction Requires Voice Authentication. Please Call-In. Processor returned a referral.
00044 Merchant not configured properly (CardAuth) The merchant has payment authentication enabled but does not have a processorid/merchantid entered.
00045 Auth service unavailable. Internal system error was encountered while connecting to authentication platform. Contact USAePay support.
00046 Auth service unavailable (6). A corrupted response was received from the authentication platform.
00050 Invalid SSN. Social Security number must be 9 digits.
00070 Transaction exceeds maximum amount. Transaction exceeds the maximum allowable amount of $99,999.
00071 Transaction out of balance. Transaction does not add up correctly: subtotal + tip + tax + shipping - discount must equal the amount.
00080 Transaction type not allowed from this source. The requested command (sale, authonly, etc) was blocked by the merchant's source key. The command must be checked on source key settings screen to be accepted by the gateway.
02034 Your billing address does not match your credit card. Please check with your bank. The AVS result received from the platform was blocked by the Merchant's fraud preferences. Funds were not held for this transaction.
10001 Processing Error Please Try Again Error from FDMS Nashville. Invalid Transaction Code
10003 Merchant does not accept this type of card (1) Error from FDMS Nashville: Terminal ID not setup for settlement on this Card Type.
10004 Merchant does not accept this type of card (2) Error from FDMS Nashville: Terminal ID not setup for authorization on this Card Type.
10005 Invalid Card Expiration Date Error from FDMS Nashville Terminal ID not setup for settlement on this Card Type.
10006 Merchant does not accept this type of card (3) Error from FDMS Nashville. Invalid Process Code, Authorization Type or Card Type.
10007 Invalid amount Error from FDMS Nashville Invalid Transaction or Other Dollar Amount.
10008 Processing Error Please Try Again (08) Error from FDMS Nashville. Invalid Entry Mode.
10009 Processing Error Please Try Again (09) Error from FDMS Nashville Invalid Card Present Flag.
10010 Processing Error Please Try Again (10) Error from FDMS Nashville Invalid Customer Present Flag.
10011 Processing Error Please Try Again (11) Error from FDMS Nashville Invalid Transaction Count Value.
10012 Processing Error Please Try Again (12) Error from FDMS Nashville Invalid Terminal Type.
10013 Processing Error Please Try Again (13) Error from FDMS Nashville Invalid Terminal Capability.
10014 Processing Error Please Try Again (14) Error from FDMS Nashville Invalid Source ID.
10015 Processing Error Please Try Again (15) Error from FDMS Nashville Invalid Summary ID.
10016 Processing Error Please Try Again (16) Error from FDMS Nashville Invalid Mag Strip Data.
10017 Invalid Invoice Number (17) Error from FDMS Nashville Invalid Invoice Number.
10018 Invalid Transaction Date or Time (18) Error from FDMS Nashville Invalid Transaction Date or Time.
10019 Processing Error Please Try Again (19) Error from FDMS Nashville Invalid bankcard merchant number in First Data database.
10020 Processing Error Please Try Again (20) Error from FDMS Nashville File Access Error in First Data database.
10026 Merchant has been deactivated (26) Error from FDMS Nashville Terminal flagged as Inactive in First Data database.
10027 Invalid Merchant Account (27) Error from FDMS Nashville. Invalid Merchant/Terminal ID combination, verify numbers are accurate.
10030 Processing Error Please Try Again (30) Error from FDMS Nashville. Unrecoverable database error from an authorization process (usually means the Merchant/Terminal ID was already in use).
10031 Processing Error Please Retry Transaction (31) Error from FDMS Nashville. Database access lock encountered, retry transaction.
10033 Processing Error Please Try Again (33) Error from FDMS Nashville. Database error in summary process, retry transaction.
10043 Sequence Error, Please Contact Support (43) Error from FDMS Nashville. Transaction ID invalid, incorrect or out of sequence.
10051 Merchant has been deactivated (51) Error from FDMS Nashville. Terminal flagged as not usable (violated) in First Data database, Call Customer Support.
10054 Merchant has not been setup correctly (54) Error from FDMS Nashville. Terminal ID not set up on First Data database for leased line access.
10057 Merchant does not support this card type (57) Error from FDMS Nashville. Terminal is not programmed for this service, call customer support.
10059 Processing Error Please Try Again (59) Error from FDMS Nashville. Settle Trans for Summary ID where earlier Summary ID still open.
10060 Invalid Account Number (60) Error from FDMS Nashville. Invalid account number found by authorization process.
10061 Processing Error Please Try Again (61) Error from FDMS Nashville. Invalid settlement data found in summary process (trans level).
10062 Processing Error Please Try Again (62) Error from FDMS Nashville. Invalid settlement data (i.e., 'future' date found, erroneous Pserve data found) (summary level).
10080 Processing Error Please Try Again (80) Error from FDMS Nashville. Invalid Payment Service data found in summary process (trans level).
10098 Processing Error Please Try Again (98) Error from FDMS Nashville. General System Error.
10099 Session timed out. Please re-login. Session timed out - (checkout timeout setting).
10100 Your account has been locked for excessive login attempts. The user failed login too many times. Their account has been locked for 60 minutes.
10101 Your username has been de-activated due to inactivity for 90 days. Please contact support to re-activate your account. VISA Cisp requires locking of accounts that have not been accessed in the past 90 days.
10102 Unable to open certificate. Unable to load required certificate. Contact Support.
10103 Unable to read certificate. Unable to load required certificate. Contact Support.
10104 Error reading certificate. Unable to load required certificate. Contact support.
10105 Unable to find original transaction. A capture or void operation was not able to locate the original transaction.
10106 You have tried too many card numbers, please contact merchant. The transaction was blocked by the MultipleCardTries module.
10107 Invalid billing zip code. The ZipCodeVerification module was not able to locate the billing zip code.
10108 Invalid shipping zip code. The ZipCodeValidation fraud module was not able to find module.
10109 Billing state does not match billing zip code. ZipCodeVerification database came up with a conflict.
10110 Billing city does not match billing zip code. ZipCodeVerification database came up with a conflict.
10111 Billing area code does not match billing zip code. ZipCodeVerification database came up with a conflict.
10112 Shipping state does not match shipping zip code. ZipCodeVerification database came up with a conflict.
10113 Shipping city does not match shipping zip code. ZipCodeVerification database came up with a conflict.
10114 Shipping area code does not match shipping zip code. ZipCodeVerification database came up with a conflict.
10115 Merchant does not accept transactions from [country]. IpCountry module blocked transaction.
10116 Unable to verify card ID number. CVV2, CID, etc result was blocked by CVVresponse fraud module.
10117 Transaction authentication required. The merchant has set a pin for this transaction but the api did not receive a UMmd5hash. They need to either upgrade their software to send the hash or they need to remove the pin on the source.
10118 Transaction authentication failed. The UMmd5hash did not match the hash that was calculated for the transaction.
10119 Unable to parse mag stripe data. Could not determine the mag data format that was sent in.
10120 Unable to locate valid installation. Please contact support. A wireless transaction came in with an install id that wasn't found in the system.
10121 Wireless key disabled. Please contact support. The install id submitted has been deleted/disabled.
10122 Wireless key mismatch. The wireless key submitted does not correspond to the source id created for this installation.
10123 Success Operation was successful. -
10124 Unsupported transaction type. Only authonly, sales and voids may be captured. An attempt was made to settle a transaction that can not be captured. This error will occur if you attempt to capture an echeck transaction.
10125 Original transaction not approved. You are trying to capture (settle) a transaction that was declined or resulted in an error. You can only capture approved transactions.
10126 Transactions has already been settled. You are trying to capture a transaction that has already been settled.
10127 Card Declined Hard decline from First Data. -
10128 Processor Error ([response]) Unknown response code from First Data Nashville.
10129 Invalid transaction data. PHP Library detected missing or invalid fields.
10130 Library Error. CURL support not found PHP Library was not able to find curl support. You must compile php with curl and openssl.
10131 Library Error. Unable to initialize CURL PHP Library was unable to initialize CURL. SSL support may be missing or incorrectly configured.
10132 Error reading from card processing gateway. PHP Library was received a bad response from the gateway.

Tokenization

This section contains the procedure for setting up using the tokens that are passed between Chargent and USAePay. USAePay uses a token system in order to maximize security of credit card data.

  1. Select Chargent app

    Tokenization Chargent App

  2. Click Gateway tab in Chargent app.

    Tokenization Gateway

  3. Click on Gateway used for integration

    Tokenization Gateway

  4. Double click on Use Tokenization field.

    Tokenization Gateway

  5. Click Use Tokenization checkbox.

    Tokenization Gateway

  6. Double click on Credit Card Data Handling field.

    Tokenization Gateway

  7. Click on Credit Card Data Handling field and click on value. The results of the values are:
    • Never Clear - Chargent will not automatically remove card data.
    • Clear After Successful Charge - Chargent will clear the credit card number, expiration dates, and card security code only after a successful charge has occurred for the card.
    • Clear After All Transactions - Chargent will erase the credit card number, expiration date, and card security code after any approved transaction (Charge, Void, Refund) has occurred for the card.
    • Clear When Token Present - Chargent will erase the credit card number, expiration date, and card security code after any approved transaction (Charge, Void, Refund) for the card when a token is present in the token field.

    Credit Card Data Handling

  8. Click Save.

Note: The token is stored in Chargent's Token field in Salesforce after your first successful transaction, and the credit card fields are handled as specified in the procedure.

Field Mapping

This section contains mapping information between eSELECTplus and Salesforce fields.

Salesforce Direction iATS Payments
Gateway ID < Transaction ID
Token < Customer Code
Order Information > Comment
Invoice Number > Invoice Number