What's New
Below are the changes made for each release.
Version 17.0 (April 2026)
Changes
- Added new InstantPaymentsCreditSend method that will create a real time, irrevocable credit to a customer’s checking or savings account.
Version 16.5 (October 2025)
Changes
- Added new companyEntryDescription parameter to the request for the following web methods:
- CreditToBankAccount
- RecurringSaleFromBankAccount
- SaleFromBankAccount
- SDCreditToBankAccount
- SDSaleFromBankAccount
- SetupRecurringPayment
- UpdateRecurringPayment
- Added new companyEntryDescription parameter to the response for the following web methods:
- GetRecurringResponse
- GetRecurringForCustomerResponse
- GetTransactionResponse
- GetTransactionByTransactionNumberResponse
- GetTransactionByTransactionNumber2Response
- Updated WSAccountType object definition to include new "Virtual_Card" enum value
Version 16.4 (January 2025)
Changes
- Updated WSSettlementType object definition from Faster_Payments to Instant_Payments enum value
Version 16.3 (July 2024)
Changes
- Updated WSPaymentOrigin object definition to include new Credit_Send","Request_for_Payment","Return_Request" enum values
- Updated WSAccountType object definition to include new "FedNow®" enum value
- Updated WSOperationType object definition to include new "CreditSend" and "RequestForPayment" enum values
- Updated WSSettlementType object definition to include new "Faster_Payments" enum values
- Updated WSTransactionStatus object definition to include new "Pending" enum values
- New CVV int parameter in RegisterCardAccount, UpdateCardAccount Request
- Updated WSStoredCredential object definition to remove "INITIAL" enum value, update "UNSCHEDULED" enum to "UNSCHEDULEDMERCHANT", update "CUSTOMER" enum to "UNSCHEDULEDCUSTOMER"
Version 16.2 (October 2023)
Changes
- Updated WSOperationType object definition to include new “Reversal” enum value
Version 16.1 (August 2022)
Changes
- Corrected Request parameter capitalization in AcctVerifyCreditToBankAccount and AcctVerifySaleFromBankAccount web methods.
Version 16.0 (August 2022)
Changes
- Added new AcctVerifyCreditToBankAccount method that will create a micro credit to a customer's checking or savings account for account verification purposes.
- Added new AcctVerifySaleFromBankAccount method that will create a micro sale to a customer's checking or savings account for account verification purposes.
- Updated the template, font, formatting.
Version 15.4 (February 2022)
Changes
-
Updated Section Special Requirements that Nacha™ rule increase the pertransaction dollar limit for same-day ACH transactions from $100k to $1,000,000 (1 Million).
-
Enhanced the same-day ACH credit (SDCredit) and debit (SDSale) transactions error message, that it cannot exceed $1,000,000 (1 Million) instead of $100K in the below methods.
For example, when a user submits SD ACH transaction which exceed $1,000,000 amount limit, a Response Code (Data_Not_Valid) is displayed with message “Amount must be less than or equal to $1,000,000 for Same Day ACH transactions.”
Version 15.3 (November 2022)
Changes
- Updated Copyright.
(September 2021)
Changes
- Corrected response message for Error_Unknown response code from "Account Invalid" to "Account failed SmartDetect validation" in RegisterAccount, and UpdateAccount web methods.
Version 15.2 (August 2021)
Changes
- Corrected response message for Account_Invalid response code from "Used by Third Party Processor" to "Account failed SmartDetect validation" in SaleFromBankAccount, RecurringSaleFromBankAccount and SDSaleFromBankAccount web methods.
(June 2021)
Changes
- Added optional parameter “bypassSmartDetect” to the RegisterAccount and UpdateAccount web methods.
Version 15.1 (May 2021)
Changes
- Cleaned up the ResponseMessage parameter from all the web methods and added comment “This field will provide supplemental information based on each response code listed above.”
Version 15.0 (March 2021)
Changes
- Added new three web methods to associate customer with location.
Version 14.5 (April 2021)
Changes
- Corrected storedCredential in section Optional Data Elements. This section incorrectly labled Unscheduled as Merchant.
- Updated section Credit Card Processing – Credential on File (Card on File) to include Card Gateway – First Data Terminal Settlement (Nashville) and Card Gateway – Global Payments.
Version 14.5 (March 2021)
Changes
- Updated comments on bypassSmartDetect parameter, added response code and message to the SaleFromBankAccount, SDSaleFromBankAccount, RecurringSaleFromBankAccount.
Version 14.4 (December 2020)
Changes
- Added optional parameter “bypassSmartDetect” to the SaleFromBankAccount, SDSaleFromBankAccount, RecurringSaleFromBankAccount Web Methods.
Version 14.3 (June 2020)
Changes
- Added new web method ForgetCustomer in support of Data Privacy Project. Added section Data Privacy ForgetCustomer in support of Data Privacy (ForgetCustomer).
Version 14.3 (May 2020)
Changes
- Added new web methods RegisterCardAccount and UpdateCardAccount in support of Credential on File. Added a new optional parameter “storedCredential” to SaleFromCardAccount in support of Credential on File. Added storedCredential to section Optional Data Elements . Added section Credit Card Processing – Credential on File (Card on File) in support of Credential on File.
Version 14.2 (March 2020)
Changes
- Added a new method called RefundCardTransaction that allows for a specified refund amount up to the full amount of a given card transaction
Version 14.2 (January 2020)
Changes
- Updated Section Special Requirements that Nacha™ rule increase the pertransaction dollar limit for same-day ACH transactions from $25,000 to $100,000.
- Added a validation on the “Amount” parameter for same-day ACH credit (SDCredit) and debit (SDSale) transactions cannot exceed $100,000 ($100k) in the below methods. For example, when a user submits SD ACH transaction which exceed $100,00 amount limit, a Response Code (Data_Not_Valid) is displayed with message “Amount must be less than or equal to $100,000 for Same Day ACH transactions.”
Version 14.1 (November 2019)
Changes
- Corrected the “GetTransactionByTransactionNumber2 Response”, added a disclaimer that “No data is returned in the response if there is no other customer information available” in these parameters: BillingAddress1, BillingAddress2, BillingCity, BillingStateRegion, BillingPostalCode, BillingCountry, BillingPhone, IPAddressOfOriginator, EmailAddress, SSN, DLState and DLNumber.
- Added an Optional Parameter “isSameDayACH” to the CreateProcessingBatch web method. Enhanced the Response Error Message (Error_Invalid_Batch) in the below methods, if the transaction is not associated with the correct batch number. For example, when a user submits the SDCreditToBankAccount method and provides a regular batch number (in other words, the batch number was created using the CreateProcessingBatch method with isSameDayACH = False).
- Added an Optional Parameters “isSameDayACH” to the response.
Version 14.0 (May 2019)
Changes
- Added a new method called GetAccounts which will retrieve account details by searching by the accountRefID. Note: An Authorized User must have the View a Customer Account permission to access this method.
Version 13.4 (April 2019)
Changes
- Updated the template and copyright
Version 13.3 (November 2018)
Changes
- Added optional parameter “holdDays” to the CreditToBankAccount Web Method
Version 13.2 (August 2018)
Changes
- Added optional parameter “holdDays” to the SaleFromBankAccount Web Method
Version 13.1 (August 2017)
Changes
- Added Section Special Requirements re: $25k limit requirement for Same Day ACH transactions.
Version 13.0 (May 2017)
Changes
- Added new web method, SDSaleFromBankAccount, to allow for the creation of Same Day ACH Debits; added new OperationType “SDSale” to allow for reporting of Same Day Debit transactions; updated detail for FaceFeeType.
Version 12.2 (October 2016)
Changes
- Added new web method, SDCreditToBankAccount, to allow for the specific creation of Same Day ACH credits; removed “For future use” from SDCredit (OperationType).
Version 12.1 (August 2016)
Changes
- Adding new options to OperationType, SettlementStatus, and TransactionStatus elements to accommodate reporting of Same Day ACH and Unauthorized Return transactions; updated document template.
Version 12.0 (June 2016)
Changes
- Added information regarding credit card and ACH email notifications; clarified the dateTime data type with respect to the EffectiveDate element.
Version 12.0 (May 2016)
Changes
- Added a new method called GetTransactionByTransactionNumber2 that will include the transaction reference number in the response.
- Updated ReferenceNumber Type and Length descriptions throughout document.
Version 11.0 (December 2014)
Changes
- Added Data limitation disclaimer section Data Returned Limitation
Version 10.0 (January 2014)
Changes
- Updated PresentmentNumber element definition
Version 10.0 (December 2013)
Changes
- Added “Resolved” as a possible WSTransactionStatus response value
Version 10.0 (November 2013)
Changes
- “Refund” added as a possible Operation Type response in 2 Get Transaction report methods.
Version 9.2 (July 2013)
Changes
- Added “Corporate_Trade_Exchange” option to GetTransactionByTransactionNumberResponse and GetTransactionResponse
Version 9.1 (January 2013)
Changes
- Updated template; added the batchNumber element to the 5 transaction methods.
Version 9.0 (December 2012)
Changes
- Updates made to all the transaction methods (CreditToBankAccount , CreditToCardAccount , SaleFromBankAccount, SaleFromCardAccount) to capture the source application (ownerApplication) and return it in the appropriate responses. Text added regarding validation of check images.
- Added new method RecurringSaleFromBankAccount (request and response). Updated the list of possible responses for the ResponseCode element.
Version 8.1 (May 2012)
Changes
- Added samples of the new reports.
- Document Template updated.
Version 8.1 (May 2012)
Changes
- Document Template updated; updated the UpdateRecurringPayment description and requirement regarding the recurringReferenceId element; corrected RefundTransaction to not allow Check21 transactions to be refunded and modified the possible OriginatedAs responses.
Version 8.0 (January 2012)
Changes
- Added TEL payment origins to Setup and Update Recurring Payment request methods and GetRecurringResponse and GetRecurringForCustomerResponse . Copyright page and footer updated.
Version 8.0 (November 2011)
Changes
- Corrected the format of AccountType: Discover_Novus – added 2nd underline.
Version 7.1 (May 2011)
Changes
- Updated comment on AccountName element in RegisterCustomer request to reflect it can’t be null but can be empty.
Version 7.0 (January 2011)
Changes
- Split the original document sections into separate documents; updated and corrected field/parameter values; updated table formats; alphabetized WSDL list. Added element and table descriptions.
Version 6.0 (October 2010)
Changes
- Formatting, font, and updated TOC. Changed to version 6.0.
Version 5.2 (October 2010)
Changes
- Reviewed and Merged Document. Updated where Transaction # is not a required field.
Version 4.0 (July 2010)
Changes
- Added new frequencies for recurring transactions.
- Added text to the Check Number field - Required if Payment Origin is Bounced_Check.
Version 2.0 (July 2009)
Changes
- Created