AppFrontier

iATS Payments Salesforce Integration Chargent

Integrating iATS Payments and Salesforce using Chargent


Easily connect iATS and Salesforce with Chargent,

the leading payments app on the Salesforce AppExchange. See all iATS transactions, manage refunds, send payment links and more, all inside Salesforce.

Not yet a Chargent customer?
Contact us for a no-obligation 30 day trial, and see for yourself!






Overview

iATS Payments provides payment processing services to more than 10,000 nonprofits worldwide. This exclusive focus enables iATS Payments to empower and serve their nonprofit clients.

In addition, iATS Payments provides extensive international capabilities to nonprofits for credit card donations in more than 35 countries, as well as the ability to settle in dozens of currencies for nonprofits who have registered offices in the country of a local currency.

With Chargent Payment Processing for Salesforce's prebuilt iATS Payments integration, nonprofit organizations can now connect Salesforce to iATS Payments in just a few steps. Nonprofits can then take advantage of Chargent's many features for automating and streamlining payment processes in Salesforce:

  • Flexible recurring billing capabilities for donations
  • See all donations and total amount given per donor at a glance
  • Embedded buttons in the Chargent Order (Donation) for one-time or new donation processing
  • Real-time payment results for phone pledge drives at the click of a button
  • Send Payment Request emails for donors to make a payment or update billing details

Plus additional benefits:

  • Control donation receipts and other communication with the power of Salesforce templates and workflow rules
  • Easy connection to iATS Payments services with no additional transaction fees
  • FormAssembly integration for easy web site donation forms

logo

Prior to setting up iATS in Salesforce

  1. Install both the Base Package and the Chargent Orders Transaction Package into your Salesforce org.

  2. Configure Chargent according to the Quick Start Guide.

For Chargent versions prior to 5.57 you may need to activate the Remote Site Settings in Salesforce if they aren’t already active for iATS.

    • Click the gear icon on the top right and select Settings
    • Under Security select Remote Site Settings
    • Locate iATS and click edit
    • Check the Active box
    • Click Save


Setting Up Salesforce For Integration with iATS

For testing, you can either use your own test credentials with iATS or setup your gateway using the test credentials iATS provides:

User ID: TEST88
Password: TEST88

Add an iATS Gateway record in Salesforce using Chargent’s Gateway Wizard.

  1. Click on the App Launcher on the top left side in Salesforce.

  2. applauncher

  3. Select Chargent as the App

  4. Select the Chargent Settings Tab

  5. Choose Chargent Setup Wizard

  6. chargent settings

  7. Do you have a Payment Gateway account - Select Yes

  8. Select iATS as your Payment gateway.

  9. Select Test Transactions for testing or Live Transactions if you are looking to process real time payments.

  10. Follow the prompts to configure your gateway.

You will need the following information:

  • Add your credentials based on your Sandbox (Test) or Production Live iATS account.

    • User ID:This is your iATS Source Key
    • Password This is the iATS Password


Other information that will be asked:

  • Will you be using tokenization? (recommended)

  • What currency will you be using? (USD, CAN, etc.)

  • What payment methods will you be accepting?

  • Credit cards and/or Direct Debit / ACH (electronic check)

    • What Credit Card types will you be accepting? (Visa, Mastercard, etc…)

  • Payment Console Setup (Premium feature for Platform Edition)

    • Show Charge Button
    • Show / Create Update Token Button
    • Show Authorize Button


Direct Debit Network (version 6.15 and higher)

Starting with Chargent version 6.15, you can now select the Bank Account network for your region during the gateway setup process. This will allow for the correct Direct Debit Network fields to be displayed on Payment Requests and Payment Console based on your region.

You have the following Direct Debit Networks to choose from based on your region.

  • US - ACH (also known as echeck or electronic check)
  • Canada - EFT (ACSS) Electronic Funds Transfer
  • Australia - BECS
  • Europe - SEPA


Select the Payment Methods You Accept

Once you have your Direct Debit Network set, you will see the appropriate field names on your Payment Request that are sent as well as your internal Payment Console.

Payment Request Bank Account


Add an iATS Gateway record in Salesforce (Chargent versions prior to 5.40)

  1. Click on the AppLauncher on the top left side in Salesforce.

  2. applauncher

  3. In the Search for apps or items box, Search for Gateways and select

  4. gateways

  5. Click New and select iATS as the Gateway Type

  6. Map the following fields in Chargent with your credentials from iATS:

    • Merchant ID: iATS User ID (Agent Code)

    • Merchant Security Key: iATS Password

  7. Setup the following Gateway fields

    • Check the Active box - To make the Gateway active

    • Use Tokenization - If you are planning on using iATS tokenization (recommended)

    • Available Card Types - Select the cards you will be accepting (this is based on your gateway settings and what card types they can process - Visa, Mastercard, American Express, etc..)

    • Available Payment Methods - Will you be accepting just Credit Cards or Direct Debit / ACH

    • Available Currencies - What currencies will you accept (this is based on your payment gateway and the currencies they accept payment in.

    • Credit Card / Bank Account Data Handling - This lets Chargent know when to clear the information in Salesforce. You have 4 options.

      • Never Clear
      • Clear After Successful Charge
      • Clear After All Transactions
      • Clear When Token is Present (recommended)

      • new gateway

When using Payment Requests or Payment Console the following should also be set. Please note these features come with Sites and Platform edition & require activation in your Production Org.

  • Available PR Transaction Types

    • Charge Full Amount - Charges the credit card immediately
    • Authorize Full Amount - This option won’t charge the card but only holds the funds available until you capture them.
    • Authorize Minimum Amount - This option won’t charge the card but only holds the minimum amount that your gateway will allow. You will need to charge the correct amount in order to capture the transaction

    • card types


  • Show Charge Button
  • Show Authorize Button

  • pr


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

test gateway



Testing the Integration

Now that you have created the iATS gateway record in Salesforce, it is time to run some test transactions to ensure it was set up correctly, and understand how Chargent works to charge credit cards within Salesforce.

Create a Chargent Order in Salesforce to run test transactions

  1. Click on the App Launcher in the top left side and select Chargent as the App.

  2. app chargent

  3. Click the Chargent Orders Tab.

  4. Click on New

  5. Enter in the following information:

    • Account: The Account the Chargent Order should be associated with.

    • Payment Type should be either credit card or check depending on if you are testing credit cards or Direct Debit / ACH (electronic check)

    • Billing Information
      • Billing First Name
      • Billing Last Name
      • Billing Address
      • Billing City
      • Billing State / Province
      • Billing Zip Code / Postal Code
      • Billing Email Address (if you want to test the email receipt that gets triggered upon a successful transaction)

    • Charge Amount- The charge amount determines the test results whether you have an approved transaction or a declined transaction. See the iATS test amounts for testing. $1.00 with 4111 1111 1111 1111 as the credit card number will return an Approved response.

    • Manual Charge checkbox to enter a specific amount. If you are entering Subtotal, Tax, and Shipping then the Charge Amount will be automatically calculated and the Manual Charge box does not need to be checked).

    • Credit Card Number = See iATS test credit card information. iATS uses different test credit card numbers to determine the response message and whether it’s approved or declined for specific reasons. For Direct Debit / ACH testing see iATS’s iATS test credit cardTest Direct Debit / ACH Account and Routing Numbers..

    • Card type (Visa, MasterCard, etc..) or Bank Account Type for Direct Debit / ACH (Checking or Savings).

    • Card Expiration Month and Card Expiration Year should be in the future

    • order


  6. Click Save

  7. Click the Charge button. You will receive a pop-up asking for the CSC (Card Security Code). This can be any 3 digits for Visa, MasterCard or Discover or 4 digits for American Express when testing in the Sandbox.

  8. charge

  9. Press the Charge button

  10. You should receive a popup that shows the test transaction was approved.

    trx



iATS Payments Test Cards

Credit Card Type Card Number
Visa 4111111111111111 - Allows you to test both Authorizations, Charges, and Rejections based on specific amounts listed below.
Visa 4222222222222220 - Allows you to test Authorizations, Charges, and Refunds using any amount.
MasterCard 5111111111111118
American Express 371111111111114
Discover 6011111111111117
CVV2 Any arbitrary 3 digits (4 digits for Amex)
Expiry Date Any arbitrary date later than today's date


iATS Test Amounts

Amount: Response
$1.00 OK: 678594
$2.00 REJ: 15
$15.00 If CVV2 = 1234 the response is OK: 678594: Y If no CVV2 is entered the response is REJ: 19
$16.00 REJ: 2
$17.00 REJ: 22
$192.00 (NA Only) If sent via API (iATSLink or WebService)

  • a) IP address is invalid format: Rej: 5.
  • b) IP address is valid format: OK: 678594
All Other Amounts REJ: 15
All Refunds Amounts REJ: 15
Any Sale Amount OK: 678594


iATS ACH testing

For North American ACH / Direct Debit testing, any bank details can be used in the Chargent fields in Salesforce, but the following test data is recommended:

Canada
Bank Number 123
Transit Number 00000
Account Number 123456


US
Routing Number 111111111
Account Number 12345678


Understanding Transactions

When a transaction occurs between Chargent and the iATS gateway, a new transaction record is created in Salesforce. The listing of transactions can be found in the Transaction section under the Related tab.

related

On the Related tab, 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 iATS sends in its response, including the transaction Type (Charge, Authorize, Refund or Void), the Response Status (Approved, Declined, Error), and any related approval or error messages.

details

billing

By altering the amount in the Charge Amount field in Salesforce, you can trigger different responses from the iATS Payments test environment.

Lists of responses can be found here: http://home.iatspayments.com/developers/test-credentials



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

https://www.iatspayments.com/NetGate/

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



Going Live

Once you have completed some test transactions to see how Chargent works, you are almost ready to go live.

You may wish to set up a daily recurring batch as a test if you will be doing recurring or subscription billing, to be sure that it is configured properly and behaves as you expect before going live with real customer subscriptions.

In addition, at this point you can complete any customizations to the Chargent system or Salesforce configuration you might want to do, such as workflow automation, email template customization, triggers, etc.

To process real transactions with iATS Payments from Salesforce, you will need to add a new Gateway record in Salesforce with the production credentials provided by iATS Payments. Make sure that either your test gateway is deactivated otherwise you will need to select the correct gateway in the Chargent Order.

Setup iATS using the Gateway Wizard
Setup iATS in Chargent version 5.40 and earlier

You should always test a live transaction with a real credit card, just to make sure everything is working smoothly, prior to going live with Chargent. Run small dollar amount transactions, and VOID them immediately after, so there are no settled charges. Using your own or company credit cards for live tests is recommended, as customers could still see notifications of a charge even if voided.

Note that Transaction fees are incurred in the live environment, so any testing should be kept to a minimum.



Tokenization

Chargent stores iATS Payments customer code tokens in the Token field, which does not need to be encrypted so the Token can be copied to new Chargent Order from the same donor, or even integrated with other systems that may connect to iATS Payments.

This tokenization feature is essential in limiting the scope of PCI compliance for your organization. Because iATS securely stores sensitive credit card account numbers, it will return a customer token which can be used to process payments. This allows you to clear the credit card information in Salesforce. The token will only work with iATS Payments for that customer.

Chargent stores iATS Payments customer code tokens in the Token field, which does not need to be encrypted so the Token can be copied to new Chargent Order from the same donor, or even integrated with other systems that may connect to iATS Payments.

Chargent can also automatically delete credit card and account numbers from Salesforce upon a successful transaction and creation of a customer code token.

To enable iATS Payments Customer Code Tokens for Payments in Salesforce:


  • Click the App Launcher on the top left

  • Search and select Gateways

  • Click on the iATS gateway record

  • Click Edit

  • Check the Use Tokenization checkbox

  • Set the Credit Card Handling field (unless you are using Payment Console)

    • Never Clear: Chargent will not remove any card data automatically.
    • Clear After Successful Charge: Chargent will clear the credit card number, expiration dates and card security code only after a successful charge is run.
    • Clear After All Transactions: The credit card number, expiration date and card security code will be erased after any transaction (Charge, Void, Refund)
    • Clear When Token Present: Only when a token is present in the token field, will the credit card number, expiration date and card security code be cleared.

The optional Payment Console feature available in the Platform Edition of Chargent can create iATS Payments tokens without ever saving sensitive data to the Salesforce database, greatly reducing PCI Compliance scope.

Please contact us for additional information on security and PCI compliance options for Salesforce.



Field Mapping

Here are some useful fields and their mappings between the Chargent software in Salesforce and the iATS Payments system.

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

You have now completed the integration of Salesforce and the iATS Payments service with Chargent. You can begin processing one-time or recurring credit card and Direct Debit / ACH payments through iATS Payments directly from Salesforce.

If you need help or have questions, please contact us.