Skip to main content

What's New

Below are the changes made for each release.

Version 16.4 (October 2025)​

Changes

  • Added new companyEntryDescription parameter to the request for the following web methods:
    • AuthorizeRecurringTransaction
    • AuthorizeTransaction
    • AuthorizeTransactionWithAddenda
    • AuthorizeTransactionWithCustomer
  • Added new companyEntryDescription parameter to the response for the following web methods:
    • GetTransaction
    • GetTransactionByField1
    • GetTransactionByTransactionNumber
    • GetTransactionByTransactionNumber2
    • GetTransactionWithAddenda
  • Updated WSAccountType object definition to include new "Virtual_Card" enum value

Version 16.3 (January 2025)​

Changes

  • Updated WSSettlementType object definition from Faster_Payments to Instant_Payments enum value

Version 16.2 (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&reg" 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

Version 16.1 (October 2023)​

Changes

Updated WSOperationType object definition to include new “Reversal” enum value

Version 16.0 (August 2022)​

Changes

Added new AuthorizeAcctVerifyTransaction method that will create a (debit or credit) micro entry transaction for account verification purposes.

(March 2022)

Changes

  • Corrected AuthorizeTransactionWithAddenda and GetTransactionWithAddenda web methods to capture a valid data in the response for IsHealthcareClaimPmt optional parameter when it is set to True
  • For example, When a user submits CCD + transaction only and they set IsHealthcareClaimPmt parameter to ‘True’. It should capture as health payment, the value “HCClaimPmt” will be programmically placed in the first 4 positions of the transaction data Field3.

Version 15.3 (February 2022)​

Changes

  • Updated Section Special Requirements that Nacha™ rule increase the per-transaction 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.”
  • Corrected Response Messages for ValidateAccount web method.

Version 15.2 (November 2021)​

Changes

  • Updated Copyright.

(September 2021)

Changes

  • Corrected response message for Account_Invalid response code from "Account Invalid" to "Account failed SmartDetect validation" in ValidateAccount Web Method.

Version 15.1 (September 2021)​

Changes

(June 2021)

Changes

  • Added new method “ValidateAccount” that will validate an ACH account prior to submitting a web transaction when the SmartDetect service is enabled.

(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 (April 2021)​

Changes

##Version 14.6 (March 2021)

Changes

Version 14.5 (December 2020)​

Changes

Version 14.4 (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.4 (January 2020)​

Changes

  • Updated Section Special Requirements that Nacha rule increase the per-transaction dollar limit for same-day ACH transactions from $25,000 to $100,000. Added a validation on the “TotalAmount” 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.3 (October 2019)​

Changes

Version 14.2 (April 2019)​

Changes

  • Updated the template and copyright

Version 14.2 (August 2018)​

Changes

Version 14.1 (August 2017)​

Changes

##Version 14.0 (July 2017)

Changes

  • Updated definition of new depositSlipId element.

Version 14.0 (June 2017)​

Changes

Version 14.0 (May 2017)​

Changes

  • Removed text “For future use” from OperationType “SDCredit”; added new Operation Type “SDSale” to accommodate same-day ACH Debits; updated FaceFee definition; updated copyright.

Version 13.1 (October 2016)​

Changes

  • Added new options to OperationType, SettlementStatus, and TransactionStatus elements to accommodate same-day ACH and Unauthorized transactions; updated document template.

Version 13.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 13.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 12.0 (December 2015)​

Changes

  • Enhanced PresentmentNumber element descriptions throughout document to cover “RETRY PYMT” Nacha™ requirement.

Version 11.1 (August 2015)​

Changes

  • Updated PaymentOrigin to include Represented_Check; “Sale” element description; FaceFeeType description; PresentmentNumber description.

Version 11.0 (December 2014)​

Changes

Version 11.0 (November 2014)​

Changes

  • Updated template and copyright.
  • Audit request: Removed URL access to WSDL

Version 10.0 (January 2014)​

Changes

  • Updated PresentmentNumber element description.

Version 10.0 (December 2013)​

Changes

  • Added “Resolved” as a possible WSTransactionStatus response value.

Version 10.0 (November 2013)​

Changes

  • Added “Refund” as a possible operation type in the 4 Get Transaction report methods.

Version 9.2 (September 2013)​

Changes

  • Added new GetTransactionWithAddenda method to request CTX or CCD+ transactions with addenda.

Version 9.2 (August 2013)​

Changes

  • Added new AuthorizeTransactionWithAddenda method to accommodate transactions with addenda (CTX, CCD+); some cosmetic changes

Version 9.2 (July 2013)​

Changes

  • Updated document format; added “Corporate_Trade_Exchange” to enum WSPaymentOrigin and WSRecurringPaymentOrigin.

Version 9.1 (July 2013)​

Changes

  • Corrected misspelling of enum WSPaymentOrigin (from PaymentOriginal)

Version 9.0 (December 2012)​

Changes

Version 8.1 (May 2012)​

Changes

  • Updated template; corrected RefundTransaction to not allow Check21 transactions to be refunded and modified the possible OriginatedAs responses.

Version 8.0 (January 2012)​

Changes

  • Updated Copyright information; added documentation re: recurring TEL transaction restrictions to business customers; added recurring transaction sample SOAP to workflow example.

Version 8.0 (December 2011)​

Changes

  • Updated CustomerNumber to be required when UpdateCustomerIfExists is ‘Yes’.

Version 8.0 (November 2011)​

Changes

  • Added new method to support recurring transactions – AuthorizeRecurringTransaction; corrected the format of AccountType: Discover__Novus; updated the copyright page. Updated TransactionProcessing WS definition.

Version 7.2 (July, August 2011)​

Changes

Version 7.1 (July 2011)​

Changes

  • Added available PaymentOrigin options and corrected the comments of the elements affected by them: CheckMICRLine, CheckNumber, CheckFrontImageBytes, AccountNumber, RoutingNumber and PresentmentNumber

Version 7.0 (February 2011)​

Changes

  • Updated and corrected field/parameter values; updated table formats; alphabetized WSDL list and added element and table descriptions to TransactionProcessing, TransactionReporting and RemoteDepositReporting versions.

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 and added element and table descriptions to Payment Vault version.

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