Developers

Developer FAQs

Below are some commonly asked questions received from Developers.

Q. What is CustomerLink?

CustomerLink is a SOAP service that lets you create and update iATS customer records from within your own software applications.

Q. What is a Customer Code Token?

A Customer Code token refers to credit card or bank account data that has been securely stored on the iATS servers and encrypted to process future transactions, such as recurring payments.

iATS issues a unique Client Code and password to our clients instead of a traditional merchant number like you may have received from other payment processors. This client code is a six digit alpha-numeric code, for example TEST88, which is used to process payments and by third party software systems to communicate with iATS’s servers. You will receive a Client Code when you sign up for an iATS merchant account.

If you’re interested in opening an iATS Payments merchant account, simply contact us by phone at 1-866-300-4287, email or by visiting this page.

In general there are three recurring management options available to our partners:

Partner stores all recurring schedule, amount and payment details in their system, and sends iATS individual transactions as per the recurring schedule. This method involves implementing the ProcessLink web service.

Partner stores all recurring schedule and amount details, but sends a request to iATS to store the payment details via a Customer Code token. When a transaction needs to be processed, the partner will send iATS a transaction request using the Customer Code token as per the recurring schedule. This method involves implementing the CustomerLink and ProcessLink web service.

Partner initially sets up a Customer Code token with iATS to store all recurring schedule, amount and payment details securely in our system. iATS then auto-processes recurring transactions as per the recurring schedule. The Approval/Reject responses are not automatically sent back to the partner in this scenario unless the ReportLink web service is implemented. This method involves implementing both the CustomerLink and ReportLink web services.

Yes. This data belongs to your organization. The iATS Customer Care team can help you through the process of accessing your recurring transaction data via an export of your iATS customer database should you ever need it.

Q. What countries do you support?

We process and settle in five primary currencies – USD$, CAD$, GBP£, EUR€ and CHF (Swiss Francs). Additionally, we provide gateway services to 180 additional currencies worldwide. Learn more about our international processing services here.

Q. What is the difference between ‘Payment Gateway’ and ‘Merchant Account’?

The payment gateway provides a connection between the payment medium (ie: website) and the merchant account. Some companies only provide a payment gateway and not the merchant account and others provide both. iATS Payments provides all clients with a payment gateway and a merchant account.

Q. What server do I use?

Transactions for USD$ and CAD$ should be processed from our North America (NA) server. All other transactions (including GBP£, EUR€ and the rest of the world) should be processed from the UK server.

Q. Can I process single ACH transactions?

iATS can accommodate both single and recurring ACH transactions, as well as both single and recurring credit card transactions for North American merchants. Please note that single ACH (Direct Debit) transactions in the UK are not allowed as per BACS regulations. For more information on our UK Direct Debit process, please contact us.

iATS Payments supports direct debit transactions in the UK. The process for accepting and processing direct debit transactions in the UK is highly controlled by Bankers’ Automated Clearing Services (BACS). iATS Payments uses a direct debiting bureau called Smart Debit to process direct debit transactions. For more information on our Direct Debit processes, please review the CustomerLink documentation or contact us.

Q. What should I expect when processing credit card test transactions using TEST88?

Credit card processing is in real-time, which means you get an immediate response of either approved or rejected. When using our test documentation, the approval and rejection responses are pre-programed to assist with testing.

Q. What should I expect when processing ACH test transactions using the test account TEST88?

Unlike credit card processing, ACH transactions are not processed in real time. When an ACH transaction is submitted, iATS provides a general response of OK:555555, which indicates iATS has received the transaction attempt and that the request is pending approval.

Q. What are the steps involved for processing live ACH transactions?

As ACH/EFT Transaction processing is not processed in “real time” like credit card transactions. There can be processing delays while the data is moving between iATS, our bank and the donor's bank.

When ACH/EFT transactions are submitted to iATS, we will submit them to our processing bank as per the following schedule:

Monday and Tuesday: File sent twice per day (3am and 3pm)
Wednesday to Friday: File sent once per day (3pm)

When ACH/EFT transactions are sent to iATS for processing, there are three stages which each transaction will go through:

1.) Immediately following the submission, each transaction will be listed as “Tobesent” within iATS systems. This stage indicates the transaction is waiting to be sent to iATS’ bank as per above schedule.

2.) Once the transactions have been sent to the bank, but before final approval/rejection has been received, each transaction will be listed as “Pending”. A response should be received within one business day. Once a response has been received, each transaction will be listed as EITHER OK:BankAccept, or OK:Reject. These results can be pulled using our WebService ReportLink options if desired.

3.) Once a response has been received, each transaction will be listed as EITHER OK:BankAccept, or OK:Reject. These results can be pulled using our WebService ReportLink options if desired.

All transactions with the result “OK:Bank Accept” will be sent to the donor’s bank for final approval. At this point, the donor or the donor’s bank may refuse the debit, for example because of an account closure or insufficient funds.

If this occurs, a separate return is recorded on the iATS Journal report and a notification email is sent to the client. These returns can be pulled using our WebService ReportLink options if desired.

Q. What is the formatting difference between CDN, USD and UK bank account details?

USD bank account details consist of a routing number (9 digits) and an account number (# of digits varies).

CAD bank account details consist of a bank ID (3 digits), a transit number (5 digits), and an account number (# of digits varies).

UK bank account details consist of a cheque number, a branch sort code and an account number.