Document Control

Introduction

This guide provides an explanation of all the available iATS ProcessLink Web services, how they work, and how to set them up.

Below is a diagram on how ProcessLink fits with other web services from iATS (orange boxes)

Please contact iATS directly for information on how to setup UK Direct Debit processing at webservice@iatspayments.com. This method of payment is highly regulated by BACS and has a number of best practices.

Functions available in ProcessLink that are explained in this guide:

Available actions include:

• Processing ACH or Credit Card transactions
• Processing ACH or Credit Card transactions and tokenizing the payment data
• Processing ACH or Credit Card refund transactions
• Processing Batches of ACH or Credit Card transactions
• Processing UK Direct Debit re-presentments

North American API Directory: https://www.iatspayments.com/netgate/processlinkv4.asmx

UK/Int’l API Directory: https://www.uk.iatspayments.com/netgate/ProcessLinkv2.asmx

1.  How Do iATS Web Services Work?

How iATS Web Services Work

When clients sign up with iATS they are provided with a unique merchant account. With this account and once you set up the Web services you require, you will be able to process transactions directly from your donor database, website, or online fundraising solution (without having to negotiate with individual credit card companies and payment processing vendors).

Our Web services are standard SOAP messages that are supported by a server-side programming language. If your Web server is Microsoft Internet Information Server (MS IIS), you can use C# to write the server side code to use the Web service. If your server is PHP-based, you can write PHP code to use the Web service.

A SOAP message is an XML file that contains the following elements:

• An envelope element that identifies the XML document as a SOAP message
• A header element that contains header information
• A body element that contains call and response information
• A fault element containing errors and status information

For a full explanation of SOAP messages, please see https://www.w3schools.com/xml/xml_soap.asp.

A C# sample of an iATS consumer Web service is available for download here. In order to run the sample code, you will need Microsoft Visual Studio 2008 or later installed. The sample calls “GetCreditCardJournalCSVV1” method from our ReportLink.asmx Web service to get details (a journal) of a successful credit card transaction in csv type.

A PHP wrapper is available on our Github repository here. The base SOAP request and response structure for the specific services are explained below. To implement the services, you need to complete the code with your information and then integrate the code into your site or software platform. (Please note that all code will be hosted on your servers.) Once the calls are tested, you are good to go!

We have created a sample client code that allows you to test our payment systems. Please see, “Appendix A: Testing iATS Payments Systems” for details on how to use it. For technical assistance, please email webservice@iatspayments.com.

ProcessLink services are usually used in conjunction with our CustomerLink services (which are explained in the CustomerLink Web Services Guide).

For example, CustomerLink is primarily used for creating, updating, and deleting credit card and ACHEFT (ACH or direct debit) Tokens (Customer Codes) to setup recurring transactions. ProcessLink, meanwhile, is for processing single and batch transactions and handling refunds. It is also possible to use it to create a Token (Customer Code) at the same time as doing a transaction if required.

Creating Tokens (Customer Codes) allows future transactions to be carried out using the same credentials without the need to store sensitive credit card or ACH information on local servers.

2. Calls to Process Credit Card Transactions

Process a Single Credit Card Transaction

This service is for when you want to process a onetime credit card transaction.

• ProcessCreditCard

This call is available on either our NA or UK system.

SOAP Request and Response Server Addresses:

Depending on which server you require, you can find the SOAP request and response structures at the following URLs:

• North America
• UK/International

SOAP Request and Response Structure:

The code below shows the SOAP request and response structure for the North American version of “ProcessCreditCard”.

Notes:

• This code corresponds to SOAP 1.2 shown at the NA server address above.
• The addresses above also contain the code for SOAP 1.1 if you require it.
• The request parameter placeholders shown (e.g., “string”, “dateTime,” etc.) need to be replaced with actual values.

Request (NA server; please use link above for UK server)

Response

Sample Reply Message Format

The table below describes what can be expected for each of the return values: 

Back to Top

Create a Token (Customer Code) and Charge Credit Card

This service is for when you want to create a credit card Token (Customer Code) for payment storage purposes only and to process a onetime credit card transaction at the same time.

• CreateCustomerCodeAndProcessCreditCard

• Please refer to the CustomerLink Guide or reach out to webservice@iatspayments.com for more details on best practices for creating a new Recurring Customer Code token.
• If you will be using the new token for a recurring schedule in the future, please avoid using any sub-codes ending in 90-99 (for example ABDC99) as these will affect future scheduled transactions. We recommend using an 80 level code (for example, ABDC80) for online webpage initiated schedules and a 01 level code (for example, ABCD01) for offline software initiated schedules.

SOAP Request and Response Server Addresses:

Depending on which server you require, you can find the SOAP request and response structures at the following URLs:

• North America
• UK/International

SOAP Request and Response Structure:

The code below shows the SOAP request and response structure for the North American version of “CreateCustomerCodeAndProcessCreditCard”.

Notes:

• This code corresponds to SOAP 1.2 shown at the NA server address above.
• The addresses above also contain the code for SOAP 1.1 if you require it.
• The request parameter placeholders shown (e.g., “string”, “dateTime,” etc.) need to be replaced with actual values.

Request (NA server, please use UK link above for UK server)

Response

Overview of Request Parameters

Here is an overview of the request parameters for “CreateCustomerCodeAndProcessCreditCard,” above. Parameters in red are mandatory.

Sample Reply Message Format

The table below describes what can be expected for each of the return values:

Back to Top

Process a Credit Card Transaction Using an Existing Token (Customer Code)

This service is for when you want to charge a credit card transaction using a Customer Code Token that already exists.

• ProcessCreditCardWithCustomerCode
  

This call is available on either our NA or UK system.

SOAP Request and Response Server Addresses:

Depending on which server you require, you can find the SOAP request and response structures at the following URLs:

• North America
• UK/International

SOAP Request and Response Structure:

The code below shows the SOAP request and response structure for the North American version of “ProcessCreditCardWithCustomerCode”.

Notes:

• This code corresponds to SOAP 1.2 shown at the NA server address above.
• The addresses above also contain the code for SOAP 1.1 if you require it.
• The request parameter placeholders shown (e.g., “string”, “dateTime,” etc.) need to be replaced with actual values.

Request (NA server; please use UK link above for UK server)

Response

Overview of Request Parameters

Here is an overview of the request parameters for “ProcessCreditCardWithCustomerCode,” above. Parameters in red are mandatory.

Sample Reply Message Format

The table below describes what can be expected for each of the return values:

Back to Top

Process Numerous Credit Card Transactions in a Batch

This service is for when you wish to process multiple credit card transactions (made on multiple credit cards) in one request. Your request will include a range of details for each credit card, as is described in detail below in the sections. Once uploaded, use the GetBatchProcessResultFile call details located in the section “Obtain the Results of a Credit Card Batch File”.

• ProcessCreditCardBatch
  

This call is available on either our NA or UK system.

iATS Payments – ProcessLink Web Services 20

Overview of Request Parameters

Here is an overview of the request parameters for “ProcessCreditCardBatch,” above. Parameters in red are mandatory.

Sample Reply Message Format

The table below describes what can be expected for each fo the return values:

Explanation of base64Binary Format

Any binary text (“friendly” readable text) is converted or encoded into Base64 format so that the batch file can be processed by the web service.

Web service does not understand binary data so it needs to convert the friendly language to something that web service can understand. We encode the binary data into characters, and Base64 is one of these types of encodings.

Example Base64 format:

To produce these results, you will need to make the xml doc a binary object of type base64. Depending on the programming language you are using, you’ll use a Convert method to encode binary to base64 format. As shown in result above.

In C#, you can convert to base64 string using this:

Convert.ToBase64String(byteArray)

In XML message, put the base64 string between <batchFile> and </batchFile>
Example including formatting from Request section above--this is what the request should look like:

To produce these results, you will need to make the xml doc a binary object of type base64. Depending on the programming language you are using, you’ll use a Convert method to encode binary to base64 format. As shown in result above.

In C#, you can convert to base64 string using this:

In XML message, put the base64 string between <batchFile> and </batchFile>

Example including formatting from Request section above, this is what the request should look like:

Explanation of Batch File types:

Batch file format for U.S. and U.K credit cards

Format:
Date, Invoice, First Name, Last Name, Street, City, State, Zip Code, Amount, MOP, Credit Card #, Expiry

Example:
10/28/11, 00001,Joe,Smith,123 Any St,Anytown,ST,10023,25.00,AMX,300000000000001,0708

• Batch file format for Canadian credit cards

Format:

Date, Invoice, Full Name, Amount, MOP, Credit Card #, Expiry

Example:
10/28/11, 00001,Joe Smith,25.00,AMX,300000000000001,0708

Notes:

• If any fields must be omitted (the invoice number for example), the comma separators must still be included. For example,
  10/28/11,,Joe,Smith,123 Any St,Anytown,ST,10023,25.00,AMX,300000000000001,0708
• Credit card abbreviations must all be capitalized and in these formats:
• NA: VISA, MC, AMX, DSC
• UK: VISA, MC, AMX, MAESTR
• Batch file format using Tokens (Customer Codes)

Format:

Invoice Number, Token (Customer Code), Amount, Comment

Example:

a123467,A168786,1.10,comment1

Notes:

• This is for all currencies.
• If any fields must be omitted (the invoice number for example), the comma separators must still be included. For example. ,,A168786,1.10,comment1

Obtain the Results of a Credit Card Batch File

This service is for when you wish to look at the results (rejects and approvals) processing multiple credit card transactions (made on multiple credit cards) in one request from section “Process Numerous Credit Card Transactions in a Batch”.

• GetBatchProcessResultFile

This call is available on either our NA or UK system.

SOAP Request and Response Server Addresses:

Depending on which server you require, you can find the SOAP request and response structures at the following URLs:

• North America
• UK/International

SOAP Request and Response Structure:

The code below shows the SOAP request and response structure for the North American version of “GetBatchProcessResultFile”.

Notes:

• This code corresponds to SOAP 1.2 shown at the NA server address above.
• The addresses above also contain the code for SOAP 1.1 if you require it.
• The request parameter placeholders shown (e.g., “string”, “dateTime,” etc.) need to be replaced with actual values.

Request for NA system; for UK see link above:

Response

Overview of Request Parameters

Here is an overview of the request parameters for “GetBatchProcessResultFile,” above. Parameters in red are mandatory.

Sample Reply Message Format

The table below describes what can be expected for each of the return values:

Explanation of Processed Batch file

Batch file results

These messages are appended to the end of the request batch file:

• OK: + 6 digits
• REJECT: TIMEOUT
• WRONG FORMAT
• Duplicated
• ...

Example request:

Example:

a123467,A168786,1.10,comment1

Example results:

a123467,A168786,1.10,comment1, OK:555555

Back to Top

3. Calls for Processing Bank Debit Transactions

Explanation of ACH Processing Stages

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 donors 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, even though you receive a successful ACH Transaction ID immediately:

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 1 business day.
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 (Journal for approvals, ACH Reject for rejections)

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 iATS Return record is added to the iATS Journal reports (ACH Returns) and a notification email is sent to the client. These returns can be pulled using our WebService ReportLink options if desired.

Process a Single Bank Debit Transaction

This service is for when you want to process a onetime ACH Bank Debit transaction for USD, CDN, or AUD currency. This call is for our North American and AUD portion of the UK International system only. For UK Direct Debit or SEPA transactions, see the CustomerLink Guide.

• ProcessACHEFT
  

This call is only available on our NA, and AUD portion of our UK system.

SOAP Request and Response Server Addresses:

Depending on which server you require, you can find the SOAP request and response structures at the following URLs:

• North America
• AUD/International

SOAP Request and Response Structure:

The code below shows the SOAP request and response structure for the North American version of “ProcessACHEFT”.

Notes:

• This code corresponds to SOAP 1.2 shown at the NA server address above.
• The addresses above also contain the code for SOAP 1.1 if you require it.
• The request parameter placeholders shown (e.g., “string”, “dateTime,” etc.) need to be replaced with actual values.

Request (NA server; for the UK server see link above)

Response

Overview of Request Parameters

Here is an overview of the request parameters for “ProcessACHEFT,” above. Parameters in red are mandatory.

Sample Reply Message Format

Back to Top

Create a Token (Bank Debit) and Charge Account

This service is for when you want to create a Bank Debit Token (Customer Code) for payment storage purposes only and to process a onetime Bank Debit transaction at the same time.

• CreateCustomerCodeAndProcessACHEFT
  

This call is only available on our NA, and AUD portion of our UK system.

The Token (Customer Code) can only be used to process single transactions in the future unless you update the recurring field values separately using the Update API calls from CustomerLink.

• Please refer to the CustomerLink Guide or reach out to webservice@iatspayments.com for more details on best practises for creating a new Recurring Customer Code token.
• If you will be using the new token for a recurring schedule in the future, please avoid using any sub-codes ending in 90-99 (for example ABDC99) as these will affect future scheduled transactions. We recommend using an 80 level code (for example, ABDC80) for online webpage initiated schedules and a 01 level code (for example, ABCD01) for offline software initiated schedules.

SOAP Request and Response Server Addresses:

Depending on which server you require, you can find the SOAP request and response structures at the following URLs:

• North America
• AUD/International

SOAP Request and Response Structure:

The code below shows the SOAP request and response structure for the North American version of “CreateCustomerCodeAndProcessACHEFT”.

Notes:

• This code corresponds to SOAP 1.2 shown at the NA server address above.
• The addresses above also contain the code for SOAP 1.1 if you require it.
• The request parameter placeholders shown (e.g., “string”, “dateTime,” etc.) need to be replaced with actual values.

Request

Response

Overview of Request Parameters

Here is an overview of the request parameters for “CreateCustomerCodeAndProcessACHEFT” above. Parameters in red are mandatory.

Sample Reply Message Format

The table below describes what can be expected for each of the return values:

Back to Top

Process a Bank Debit Transaction Using an Existing Token (Customer Code)

This service is for when you want to charge a credit card transaction using a Customer Code Token that already exists.

• ProcessACHEFTWithCustomerCode
  

This call is only available on our NA, and AUD portion of our UK system.

SOAP Request and Response Server Addresses:

Depending on which server you require, you can find the SOAP request and response structures at the following URLs:

• North America
• AUD/International

SOAP Request and Response Structure:

The code below shows the SOAP request and response structure for the North American version of “ProcessACHEFTWithCustomerCode”.

Notes:

• This code corresponds to SOAP 1.2 shown at the NA server address above.
• The addresses above also contain the code for SOAP 1.1 if you require it.
• The request parameter placeholders shown (e.g., “string”, “dateTime,” etc.) need to be replaced with actual values.

Request (NA; for AUD International see link above)

Response

Overview of Request Parameters

Here is an overview of the request parameters for “ProcessACHEFTWithCustomerCode,” above. Parameters in red are mandatory.

Sample Reply Message Format

The table below describes what can be expected for each of the return values:

Back to Top

Process Multiple Bank Debit Transactions in a Batch

This service is for when you wish to process multiple Bank Debit transactions (made on multiple bank accounts) in one request. Your request will include a range of details for each bank account, as is described in detail below in the sections. Once uploaded, use the GetBatchProcessResultFile call details located in section “Obtain the Results of a Bank Debit Batch File” on page 46.

• ProcessACHEFTChargeBatch

SOAP Request and Response Server Addresses:

Depending on which server you require, you can find the SOAP request and response structures at the following URLs:

• North America
• UK/International

SOAP Request and Response Structure:

The code below shows the SOAP request and response structure for the North American version of “ProcessACHEFTChargeBatch”.

Notes:

• This code corresponds to SOAP 1.2 shown at the NA server address above.
• The addresses above also contain the code for SOAP 1.1 if you require it.
• The request parameter placeholders shown (e.g., “string”, “dateTime,” etc.) need to be replaced with actual values.

Request for NA system, for AUD International see link above:

Response

Overview of Request Parameters

Here is an overview of the request parameters for “ProcessACHEFTChargeBatch,” above. Parameters in red are mandatory.

Sample Reply Message Format

The table below describes what can be expected for each of the return values:

Explanation of base64Binary Format

Any binary text (“friendly” readable text) is converted or encoded into Base64 format so that the batch file can be processed by the web service.

Web service does not understand binary data so it needs to convert the friendly language to something that web service can understand. We encode the binary data into characters, and Base64 is one of these types of encodings.

Example Base64 format:

To produce these results, you will need to make the xml doc a binary object of type base64. Depending on the programming language you are using, you’ll use a Convert method to encode binary to base64 format. As shown in result above.

In C#, you can convert to base64 string using this:

In the XML message, put the base64 string between <batchFile> and </batchFile>
Example including formatting from Request section above--this is what the request should look like:

Explanation of Batch File Types

Format:
Invoice, First Name, Last Name, Account Type, Account # (no spaces or dashes), Amount (no $), Comment

Example: a1234,Joe,Smith,CHECKING,00567890567890,1.00,comment1

• USD: Routing no. (9 digits) + account no. (# of digits varies)
• CAD: Bank no. (3 digits) + transit no. (5 digits) + account no. (# of digits varies)
• AUD: BIC (Bank ID) + IBAN (Account)

* Order must be followed with NO spaces/dashes. Ie: 12312345123456789 *

Batch file format using Tokens (Customer Codes)

Format:
Invoice Number, Token (Customer Code), Amount, Comment

Example: a123467,A168786,1.10,comment1

Notes:

• Applies to all currencies.
• If any fields must be omitted (the invoice number for example), the comma separators must

still be included. For example, ,,Joe,Smith,CHECKING,00567890567890,1.00,comment1 ,,A168786,1.10,comment1

This service is for when you wish to look at the results (rejects and approvals) processing multiple bank debit transactions (made on multiple credit cards) in one request from Section 3.4.

• GetBatchProcessResultFile

SOAP Request and Response Server Addresses:

Depending on which server you require, you can find the SOAP request and response structures at the following URLs:

• North America
• UK/International

SOAP Request and Response Structure:

The code below shows the SOAP request and response structure for the North American version of “GetBatchProcessResultFile”.

Notes:

• This code corresponds to SOAP 1.2 shown at the NA server address above.
• The addresses above also contain the code for SOAP 1.1 if you require it.
• The request parameter placeholders shown (e.g., “string”, “dateTime,” etc.) need to be replaced with actual values.

Request for NA system; for UK see link above:

Response

Overview of Request Parameters

Here is an overview of the request parameters for “GetBatchProcessResultFile,” above. Parameters in red are mandatory.

Sample Reply Message Format

The table below describes what can be expected for each of the return values:

Explanation of Processed Batch File

Batch file results:
These messages are appended to the end of the request batch file:

• OK: + 6 digits
• REJECT: TIMEOUT
• WRONG FORMAT
• Duplicated
• ...

Example request:

a1234,Joe,Smith,CHECKING,00567890567890,-1.00,comment1 a2224,Tony,,CHECKING,00567890560000,-20.00,comment2

Example results:

a1234,Joe,Smith,CHECKING,00567890567890,-1.00,comment1, REJECT:TIMEOUT a2224,Tony,,CHECKING,00567890560000,-20.00,comment2, OK:555555

Back to Top

4. Calls to Refund Credit Card and Bank Debit Transactions

Refunding a Credit Card Transaction

This service is for when you want to refund a credit card transaction using its Transaction ID.  ProcessCreditCardRefundWithTransactionId

This call is available on either our NA or UK system.

SOAP Request and Response Server Addresses:

Depending on which server you require, you can find the SOAP request and response structures at the following URLs:

• North America
• UK/International

SOAP Request and Response Structure:

The code below shows the SOAP request and response structure for the North American version of “ProcessCreditCardRefundWithTransactionId”.

Notes:

• This code corresponds to SOAP 1.2 shown at the NA server address above.
• The addresses above also contain the code for SOAP 1.1 if you require it.
• The request parameter placeholders shown (e.g., “string”, “dateTime,” etc.) need to be replaced with actual values.

Request (NA server; please use UK link above for UK server)

Response

Overview of Request Parameters

Here is an overview of the request parameters for “ProcessCreditCardRefundWithTransactionId” above. Parameters in red are mandatory.

Sample Reply Message Format

The table below describes what can be expected for each of the return values:

Sample Reply Message Format

The table below describes what can be expected for each of the return values:

Overview of Request Parameters

Here is an overview of the request parameters for “ProcessACHEFTRefundBatch,” above. Parameters in red are mandatory.

Explanation of based64Binary Format

Any binary text (“friendly” readable text) is converted or encoded into Base64 format so that the batch file can be processed by the web service.

Web service does not understand binary data so it needs to convert the friendly language to something that web service can understand. We encode the binary data into characters, and Base64 is one of these types of encodings.

Example Base64 format:

To produce these results, you will need to make the xml doc a binary object of type base64. Depending on the programming language you are using, you’ll use a Convert method to encode binary to base64 format. As shown in result above.

In C#, you can convert to base64 string using this:

In the XML message, put the base64 string between <batchFile> and </batchFile>

Example including formatting from the Request section above--this is what the request should look like:

Explanation of Batch file types:

Format:
Invoice, First Name, Last Name, Account Type, Account # (no spaces or dashes), Amount (no $), Comment

Example:

a1234,Joe,Smith,CHECKING,00567890567890,1.00,comment1

• USD: Routing no. (9 digits) + account no. (# of digits varies)
• CAD: Bank no. (3 digits) + transit no. (5 digits) + account no. (# of digits varies)
• AUD: BIC (Bank ID) + IBAN (Account)

* Order must be followed with NO spaces/dashes. Ie: 12312345123456789 *

Back to Top

Obtain the Results of a Credit Card Batch File

This service is for when you wish to look at the results (rejects and approvals) processing multiple bank debit transactions (made on multiple credit cards) in one request from Section 3.4.

• GetBatchProcessResultFile

This call is available on either our NA or UK system.

SOAP Request and Response Server Addresses

Depending on which server you require, you can find the SOAP request and response structures at the following URLs:

• North America
• UK/International

SOAP Request and Response Structure

The code below shows the SOAP request and response structure for the North American version of “GetBatchProcessResultFile”.

Notes:

• This code corresponds to SOAP 1.2 shown at the NA server address above.
• The addresses above also contain the code for SOAP 1.1 if you require it.
• The request parameter placeholders shown (e.g., “string”, “dateTime,” etc.) need to be replaced with actual values.

Request for NA system; for UK see link above:

Response

Overview of Request Parameters

Here is an overview of the request parameters for “GetBatchProcessResultFile,” above. Parameters in red are mandatory.

Sample Reply Message Format:

The table below describes what can be expected for each of the return values:

5. Process a UK Direct Debit Representment

Debits that appear in a BACS ARUDD report (see ReportLink for call to pull this from iATS) contain debits that were uncollectable. Only those with reason code 0 (Refer to Payer) may be represented again for collection provided the collection is made within one calendar month of the original failed collection.

Bacs guidelines suggest that the payer should be contacted before the debit is represented to ensure the payer has sufficient funds in their account, but this is not mandatory.

• ProcessDirectDebitRepresentment This call is available on our UK system.

SOAP Request and Response Server Addresses:
Depending on which server you require, you can find the SOAP request and response structures at the following URLs:

• UK/International

SOAP Request and Response Structure:

The code below shows the SOAP request and response structure for the UK version of “ProcessDirectDebitRepresentment”.

Notes:

• This code corresponds to SOAP 1.2 shown at the UK server address above.
• The addresses above also contain the code for SOAP 1.1 if you require it.
• The request parameter placeholders shown (e.g., “string”, “dateTime,” etc.) need to be replaced with actual values.

Request (UK Only)

Response

Overview of Request Parameters

Here is an overview of the request parameters for “ProcessDirectDebitRepresentment,” above. Parameters in red are mandatory.

6. Appendix A: Testing iATS Payments Systems

The TEST88 and AURA88 iATS Client Codes have been created to allow for testing iATS Payments systems, now available for both Credit Card and dynamic North American ACH/EFT processing.

These accounts are not live merchant accounts, therefore Authorization and Rejection results are not real.

Please note that this test information is provided to many clients, therefore please do not modify or delete any pre-existing Aura Event’s or change the password of this code.

User ID = TEST88

Password = TEST88

OR
User ID = AURA88

Password = AURA88

URL:          NA = www.iatspayments.com

                    UK = www.uk.iatspayments.com

Credit Card Testing

Notes on Credit Card processing:

• To test the Authorization and Rejection responses related to a Charge, use
  • Visa number 411111111111111
  • MC number 5111111111111118
  • AMX number 371111111111114
  • DSC number 6011111111111117
• To test the Auth responses related to both Charges and Refunds, use credit card number

      4222222222222220

• If needed, use any 3 digit CVV2 for Visa, MC and DSC. Use any 4 digit CVV2 for AMX.

Please note there is a transaction limit of $2000.00 (£2000.00) per charge. Amounts above will be Rej:39

• For Direct Post Method, the NA and UK TEST88 Process Key credentials are: PA0940D765F2BD67BD97B82EFAA4D72BE9

North American ACH/EFT Debit Testing

Notes on ACH Processing:

• ACH/EFT Transaction processing is not processed in “Real Time” like credit card transactions and there can be processing delays while the data is moving between iATS, our Bank and the donors Bank.
• Live and Test ACH/EFT processing is sent to the 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)
  • No files are sent over the weekend or on US bank holidays.
• When ACH/EFT transactions are sent to iATS for processing, there are three stages which each transaction will go through:
  • “Tobesent” - The transaction is waiting to be sent to iATS’ bank as per above schedule.
  • “Pending” - The transactions have been sent to the bank, but final approval/rejection has not been received from the bank (1 Business day in general).
  • “OK:BankAccept”, or “OK:Reject” – The final results from the bank indicating approval or decline. Check the Details of the Reject Journal on the iATS Portal for more information.
  • “Return” - A separate Return record may be recorded on the iATS Journal report. These may be posted at any future date, and has been issued by the bank or donor. Check the Details of the Return report on the iATS Portal for more information.
• For North American ACH testing, any account details can be used however we recommend:

ACH Dynamic Testing Parameters:

Back to Top

7. Appendix B: Definition of XML Element Abbreviations

The elements in the below table may or may not apply directly to the ProcessLink WebServices. All possible element options which are currently available within the different CustomerLink, ProcessLink, AuraLink, and ReportLink API calls are listed below.

For more information or if you have any questions, please reach out to iATS at webservice@iatspayments.com.