LogoLogo
API ReferencesGithubSupport CenterStatus pageBecome a Partner
  • Getting Started
    • Welcome
    • Our Products
  • Integration Process
  • Devices
    • Dejavoo
    • PAX
    • ID TECH
  • Become a Partner
  • Developer Resources
    • Overview
    • Sandbox & Production Environments
  • Testing Integration
    • Test Cards & ACH Accounts
    • Onboarding API Result Codes
    • Transaction Error Generation Data
    • Card Response & Result Codes
      • Card Error Response Codes
      • Card Transaction Result Codes
      • CSC Response Codes
      • AVS Response Codes
      • Duplicate Transaction Settings
    • ACH Request Validation & Return Codes
      • ACH Request Validation Codes
      • ACH Return Codes
  • API Catalog
    • Merchant Onboarding APIs
    • Transaction (Quest) APIs
    • Automated Merchant Onboarding Setup API
    • Reporting API
  • Webhooks
    • Prerequisites
    • Register Endpoint
    • Webhook Subscriptions
    • Working with Webhooks
      • Transaction Webhook
      • Onboarding Webhooks
        • Application Status
        • Application Fixes
      • Equipment Tracking & Activation Webhooks
        • Equipment Tracking
        • Equipment Activation
  • Merchant Onboarding
    • Overview
  • Automated Merchant Onboarding
    • Prerequisites
    • Working with Automated Merchant Onboarding
      • Generating a Merchant Application
      • Completing the Application
      • Modifying Default Merchant Pricing
        • Retrieving Existing Pricing Templates
        • Modifying Pricing Fees & Completing Merchant Application Record
    • Merchant Onboarding Status Webhooks
    • Configuring Automated Merchant Onboarding
  • Merchant Onboarding via Partner Portal
    • Starting New Application
    • Adding Hierarchy & Compensation Details
    • Entering Business Information
    • Entering Profile Details
    • Conducting the Site Survey
    • Configuring Pricing Details
    • Adding Banking Information
    • Adding Equipment
    • Submitting Signature
    • Reviewing & Submitting Application
    • Viewing Application Summary
  • Merchant Onboarding via API
    • Prerequisites
    • Understanding Integration
    • Working with Merchant Onboarding API
      • Creating a Merchant Profile
      • Completing the Merchant Application
        • Gathering Merchant Demographics
        • Configuring Merchant Pricing
        • Ordering and Setting Up Equipment
      • Submitting the Signature
      • Submitting the Application
  • Payment Processing Solutions
    • Overview
    • JavaScript SDK
      • Prerequisites
        • Browser Support
      • Working with JavaScript SDK
        • Adding the Payment Form
        • Formatting the Payment Form
        • Processing the Payment
        • Apple Pay for Web
        • Google Pay for Web
        • Using IDTech VP8300
      • Card Validations
        • Card Number Validation
        • Card Expiration Date Validation
        • Card CSC/CVC Validation
      • Configuring with JavaScript SDK
        • Using Members
        • Using Methods
  • Hosted Payments
    • Prerequisites
      • Browser Support
    • Integrating the Hosted Payments
      • Configuring the Pay Now Button
      • Configuring Payment Page with an Amount Field
      • Configuring Payment Page with an Optional Billing Address and Headline Text
      • Configuring Payment Page with the Save Card Option
      • Configuring the Add Payment Method Button
      • Styling Your Brand on the Payment Page
      • Configuring Apple Pay for Web
      • Configuring Hosted Payment Page Using Members
      • Configuring Hosted Payment Page Using Methods
      • Configuring Hosted Payment Page Using Functions
    • Transaction Responses
      • Successful Transaction Response
      • Successful Transaction Response for a Billing Address
      • Failed Transaction Response
      • Unauthorized Request Response
      • Successful Transaction Response for a Token
      • Successful Token Request Response
    • Response Validations
      • Successful Transaction Response Validation
      • Failed Transaction Response Validation
    • Card Validations
  • Mobile EMV SDK
    • VP3300 Mobile Card Reader
      • Charging the card reader
      • Reading the card data
    • iOS Framework
      • iOS Framework Pre-requisites
      • Processing payments in your iOS app
        • Optional settings
        • Starting a Bluetooth connection
        • Pairing the card reader with an iOS device
        • Integrating the iOS framework into your app
        • Setting up the iOS framework in your Objective-C app
        • Starting a transaction in your iOS app
        • Receiving feedback messages
    • Android Framework
      • Integrating the Android framework into your app
      • Additional settings
      • Generating a JSON Web Token
      • Disabling default EMV configuration
  • ACH Transactions
    • Submitting the payment request
    • Creating an ACH token
    • Getting an ACH transaction
    • ACH transaction statuses
    • ACH transaction return codes
  • Paylink
    • Getting the paylink settings
    • Creating the paylink
    • Sending the paylink
    • Paylink URL
  • Virtual Terminal
    • Working with the Virtual Terminal
      • Accessing Virtual Terminal
      • Adding or Ordering the Equipment
      • Recurring Payments
        • Adding a New Customer
        • Adding a Payment Method
        • Adding a New Payment Plan
        • Viewing the Plans
      • Processing Sales Transaction
      • Processing ACH Transaction
      • Transaction Search
        • Viewing Transactions
        • Viewing Transaction Receipt
        • Printing Transaction Receipt
        • Emailing Transaction Receipt
        • Void a Transaction
        • Refund a Transaction
        • Processing Pending Transactions
      • Open Batches
        • Viewing Batches
      • VT Settings
        • Merchant
        • Terminal
        • External Terminal
        • Address Verification (AVS)
        • Card Security Code (CSC)
        • Hosted Payment Page (HPP)
  • Cloud EMV
    • Working with Cloud EMV
      • Direct Data Transfer to Cloud
      • Payment Authorization Process via Quest Payment Gateway
  • Financial Management
    • Overview
    • Merchant Pricing
  • Merchant Billing & Funding
  • Financial Reporting
  • Disputes Management
    • Understanding Disputes
    • Managing Disputes via Merchant Portal
    • Managing Disputes via API (Pilot Mode)
  • Reporting
    • Overview
  • Reporting Solutions
  • Working with Reporting API
    • Accessing Reports
    • Retrieving Reports
    • Exporting Reports
  • Support Ticketing
    • Overview
    • Benefits of Support Ticketing System
    • Accessing Support in the Portals
    • Working with Support Ticketing via Partner Portal
      • Types of Support Tickets
      • Submitting a Support Ticket via Partner Portal
  • Working with Support Ticketing via Merchant Portal
    • Types of Support Tickets
    • Submitting a Support Ticket via Merchant Portal
  • Partner & Merchant Solutions
    • Overview
    • Accessing the Portals
    • Navigating the User Interface
    • Working with the Partner Portal
      • Monitoring Performance with Dashboards
      • Managing Merchant Applications
      • Managing Merchants
      • Accessing Reports & Managing Subscriptions
        • Accessing Reports
        • Managing Subscriptions
      • Submitting a Support Ticket
  • Working with the Merchant Portal
    • Monitoring Home Page
    • Accessing Batches
    • Managing Transactions
    • Managing Funding Transactions
    • Managing Virtual Terminal
    • Viewing Chargebacks
    • Managing Disputes
    • Managing Statements & Tax Forms
    • Managing Account Settings
    • Managing User Notifications
    • Managing Support Tickets
  • Security Solutions
    • Overview
    • PCI Compliance
    • Tokenization
    • Encryption
    • Advanced Compliance & Security Measures & Programs
Powered by GitBook

Resources

  • Contact
  • Support Site
  • Campus

Terms & Policies

  • Terms
  • Privacy Policy
  • Disclosures
  • Merchant Agreement

Cookies

  • Cookie List
  • Cookies Settings

Site Info

  • Sitemap

© 2025 Clearent, LLC is a registered agent for Central Bank of St. Louis, MO; Citizens Bank, N.A., Providence, RI; and Pathward, N.A., Sioux Falls, SD.

On this page

Was this helpful?

Export as PDF
  1. ACH Transactions

Getting an ACH transaction

To get an ACH transaction:

1

Use the GET method with the /rest/v2/ach/transactions endpoint.

2

Enter the ID returned in the ACH payment response in the search criteria to find the transaction.

The ach-transaction returns the following response:

{ 
 "ach-transaction": 
  [ 
   { 
    "check-field": "invoice", 
    "client-ip": "111.22.22.333", 
    "dob-year": "dob-year", 
    "email-receipt": "true", 
    "software-type-version": "1.0", 
    "type": "Debit", 
    "validate-account": "true", 
    "amount": "string", 
    "routing-number": "string", 
    "account-number": "string", 
    "account-type": "Checking", 
    "standard-entry-class-code": "PPD", 
    "check-number": "string", 
    "create-token": "false", 
    "create-description": "false", 
    "individual-name": "string", 
    "token-id": "1188888888888888", 
    "id": "string", 
    "status": "Pending", 
    "billing": 
     { 
      "city": "City", 
      "company": "Company", 
      "country": "Country", 
      "first-name": "John", 
      "last-name": "Doe", 
      "phone": "Phone", 
      "state": "State", 
      "street": "Street", 
      "street2": "Street2", 
      "zip": "Zip" 
     }, 
      "shipping": 
       { 
        "city": "City", 
        "company": "Company", 
        "country": "Country", 
        "first-name": "John", 
        "last-name": "Doe", 
        "phone": "Phone", 
        "state": "State", 
        "street": "Street", 
        "street2": "Street2", 
        "zip": "Zip" 
       }, 
        "invoice": "string", 
        "purchase-order": "string", 
        "customer-id": "string", 
        "order-id": "string", 
        "email-address": "string", 
        "description": "string", 
        "comments": "string", 
        "billing-is-shipping": "true", 
        "status-change-date": "string", 
        "display-message": "string", 
        "provider-transaction-id": "string", 
        "trace-number": "string", 
        "settled-date": "string", 
        "returned-date": "string", 
        "returned-code": "string", 
        "returned-message": "string", 
        "ach-token": 
         { 
          "account-number": "1111", 
          "account-type": "Checking", 
          "created": "1100000000000000", 
          "customer-key": "customer123", 
          "default": true, 
          "individual-name": "John Doe", 
          "last-used": "1100000000000000", 
          "merchant-id": "000008888", 
          "routing-number": "081009813", 
          "times-used": 14, 
          "token-description": "Travel checking account", 
          "token-id": "1100000000000000", 
          "updated": "1100000000000000" 
         }, 
          "merchant-id": "string", 
          "terminal-id": "string", 
          "software-type": "MySoftware_Version1.3", 
          "paya-authorization": "string" 
   } 
  ] 
}

The following table describes the fields in the response body:

Name
Data type
Description

ach-transaction

Array of strings

Contains the details of the ACH transaction.

check-field

String

Specifies the field used for check identification, such as an invoice number.

client-ip

String

The IP address of the client initiating the request.

dob-year

String

The customers year of birth.

email-receipt

String

Indicates whether to send an email receipt.

software-type-version

String

The version of the software used to initiate the transaction.

type

String

The transaction type. For example, Debit.

validate-account

String

Indicates whether to validate the bank account.

amount

String

The transaction amount.

routing-number

String

The bank routing number.

account-number

String

The bank account number.

account-type

String

The type of bank account. For example, Checking or Savings.

standard-entry-class-code

String

The ACH standard entry class code. For example, PPD.

check-number

String

The check number associated with the transaction.

create-token

String

Indicates whether to create a reusable token.

create-description

String

Indicates whether to create a transaction description.

individual-name

String

The name of the individual associated with the transaction.

token-id

String

The unique identifier of the token.

id

String

The unique identifier of the transaction.

status

String

The current status of the transaction. For example, Pending.

billing

Object

Contains billing address details.

billing.city

String

The billing city.

billing.company

String

The billing company.

billing.country

String

The billing country.

billing.first-name

String

The first name of the billing contact.

billing.last-name

String

The last name of the billing contact.

billing.phone

String

The phone number of the billing contact.

billing.state

String

The billing state.

billing.street

String

The billing street address.

billing.street2

String

The second line of the billing street address.

billing.zip

String

The billing ZIP code.

shipping

Object

Contains shipping address details.

shipping.city

String

The shipping city.

shipping.company

String

The shipping company.

shipping.country

String

The shipping country.

shipping.first-name

String

The first name of the shipping contact.

shipping.last-name

String

The last name of the shipping contact.

shipping.phone

String

The phone number of the shipping contact.

shipping.state

String

The shipping state.

shipping.street

String

The shipping street address.

shipping.street2

String

The second line of the shipping street address.

shipping.zip

String

The shipping ZIP code.

invoice

String

The invoice number associated with the transaction.

purchase-order

String

The purchase order number associated with the transaction.

customer-id

String

The unique identifier of the customer.

order-id

String

The unique identifier of the order.

email-address

String

The email address of the customer.

description

String

A description of the transaction.

comments

String

Additional comments about the transaction.

billing-is-shipping

String

Indicates whether the billing address is the same as the shipping address. Use true or false.

status-change-date

String

The date when the transaction status last changed.

display-message

String

A message to be displayed to the user.

provider-transaction-id

String

The unique identifier of the transaction from the payment provider.

trace-number

String

The trace number associated with the transaction.

settled-date

String

The date when the transaction was settled.

returned-date

String

The date when the transaction was returned.

returned-code

String

The code indicating the reason for the transaction return.

returned-message

String

The message indicating the reason for the transaction return.

ach-token

Object

Contains details of the ACH token.

ach-token.account-number

String

The masked bank account number associated with the token.

ach-token.account-type

String

The type of bank account. For example, Checking or Savings.

ach-token.created

String

The timestamp when the ACH token was created.

ach-token.customer-key

String

The unique key of the customer associated with the ACH token.

ach-token.default

Boolean

Indicates whether the ACH token is the default token.

ach-token.individual-name

String

The name of the individual associated with the ACH token.

ach-token.last-used

String

The timestamp when the ACH token was last used.

ach-token.merchant-id

String

The unique identifier of the merchant associated with the ACH token.

ach-token.routing-number

String

The bank routing number associated with the account.

ach-token.times-used

String

The number of times the ACH token has been used.

ach-token.token-description

String

A description of the ACH token, such as the accounts purpose.

ach-token.token-id

String

The unique identifier of the ACH token.

ach-token.updated

String

The timestamp when the ACH token was last updated.

merchant-id

String

The unique identifier of the merchant.

terminal-id

String

The unique identifier of the terminal.

software-type

String

The name and version of the software initiating the request.

paya-authorization

String

The authorization code from Paya.

The ach-transaction returns the following status and error codes:

Code
Description

401

If the ACH token has expired or the signature does not match the token.

204

Not found.

200

The ACH transaction list was generated successfully.

PreviousCreating an ACH tokenNextACH transaction statuses

Last updated 9 days ago

Was this helpful?