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
    • Cloud EMV
      • Working with Cloud EMV
        • Direct Data Transfer to Clearent's Cloud
        • Payment Authorization Process via Clearent's Quest Payment Gateway
    • 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
    • Working with 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
    • The Paylink URL
    • Working with the Paylink
      • Setting up the Paylink
      • Configuring the Paylink URL
      • Using the Paylink Settings API
        • Request Parameters
      • Getting the Paylink Settings
      • Applying the Paylink Settings
      • Sending the Paylink SMS
  • 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)
  • Financial Management
    • Overview
    • Merchant Pricing
  • Merchant Billing & Funding
  • Financial Reporting
  • Disputes Management
    • Understanding Charge Disputes
    • Managing Disputes in Merchant Portal
    • Managing Disputes via API (Coming Soon!)
  • 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

ACH transaction return codes

The following table describes the codes returned by the receiving bank for ACH transactions:

Code
Message
Description

R02

Account closed.

A previously open account is now closed.

R03

No account or unable to locate account.

The account number does not correspond to the individual identified in the entry or a valid account.

R04

Invalid account number.

The account number fails the check digit validation or may contain an incorrect number of digits

R05

Unauthorized debit to consumer account.

A business debit entry was transmitted to a members consumer account, and the member had not authorized the entry.

R06

Returned per ODFI’s request.

The ODFI has requested that the RDFI return the entry.

R07

Authorization revoked by customer.

The member who previously authorized an entry has revoked authorization with the Originator.

R08

Payment stopped or stop payment on item.

The member had previously requested a stop payment of a single or recurring entry

R09

Uncollected funds.

Available balance is sufficient, but collected balance is not sufficient to cover the entry.

R10

Customer advises not authorized.

The member advises not authorized, notice not provided, improper source document, or amount of entry not accurately obtained from source document

R11

Check truncation entry return.

To be used when returning a check truncation entry.

R12

Branch sold to another DFI.

RDFI unable to post entry destined for a bank account maintained at a branch sold to another financial institution.

R13

Invalid ACH routing number.

The financial institution does not receive commercial ACH entries.

R14

Representment payee deceased or unable to continue in that capacity.

The representative payee is deceased or unable to continue in that capacity, beneficiary is not deceased.

R15

Beneficiary of account holder deceased.

The beneficiary or account Holder Deceased.

R16

Account frozen.

Access to account is restricted due to specific action taken by the RDFI or by legal action.

R17

File record edit criteria.

Fields rejected by RDFI processing. (identified in return addenda)

R18

Improper effective entry date.

Entries have been presented prior to the first available processing window for the effective date.

R19

Amount field error.

Improper formatting of the amount field.

R20

Non transaction account.

Policies or regulations (such as Regulation D) prohibit or limit activity to the account indicated.

R21

Invalid company identification.

The company ID information not valid. (normally CIE entries)

R22

Invalid individual ID number.

The individual id used by receiver is incorrect. (CIE entries)

R23

Credit entry refused by receiver.

Receiver returned entry because minimum or exact amount not remitted, bank account is subject to litigation, or payment represents an overpayment, originator is not known to receiver or receiver has not authorized this credit entry to this bank account.

R24

Duplicate entry.

RDFI has received a duplicate entry.

R25

Addenda error.

Improper formatting of the addenda records information.

R26

Mandatory field error.

Improper information in one of the mandatory fields.

R27

Trace number error.

Original entry trace number is not valid for return entry; or addenda trace numbers do not correspond with entry detail record.

R28

Routing number or check digit error.

Check digit for the transit routing number is incorrect.

R29

Corporate customer advises not authorized.

RDFI has been notified by business account holder that a specific transaction is unauthorized.

R30

RDFI not participant in check truncation program.

The financial institution not participating in automated check safekeeping application.

R31

Permissible return entry.

RDFI has been notified by business account holder that a specific transaction is unauthorized.

R32

RDFI non settlement.

RDFI is not able to settle the entry.

R33

Return of XCK entry.

RDFI determines at its sole discretion to return an XCK entry; an XCK return entry may be initiated by midnight of the sixtieth day following the settlement date if the XCK entry.

R34

Limited participation DFI.

RDFI participation has been limited by a federal or state supervisor.

R35

Return of improper debit entry.

ACH debit not permitted for use with the CIE standard entry class code. (except for reversals)

R36

Return of improper credit entry.

None

R37

Source Document Presented for Payment Check used for an ARC, BOC or POP entry has also been presented for payment.

None

R38

Stop payment on source document.

Stop payment has been placed on a check used for an ARC entry.

R40

Return of ENR entry by federal government agency. (ENR only)

None

R41

Invalid transaction code. (ENR only)

None

R42

Routing number or check digit error. (ENR only)

None

R43

Invalid DFI account number. (ENR only)

None

R44

Invalid individual ID number. (ENR only)

None

R45

Invalid individual name/company name. (ENR only)

None

R46

Invalid representative payee indicator. (ENR only)

None

R47

Duplicate enrollment.

None

R50

State law affecting RCK acceptance.

None

R51

Item is ineligible, notice not provided, signature not genuine.

None

R52

Stop payment on item.

None

R61

Misrouted return.

Return entry was sent by RDFI to an incorrect ODFI routing/transit number.

R62

Incorrect trace number.

None

R63

Incorrect dollar amount.

None

R64

Incorrect individual identification.

None

R65

Incorrect transaction code.

None

R66

Incorrect company identification.

None

R67

Duplicate return.

ODFI has received more than one return entry for the same original entry.

R68

Untimely return.

Return entry did not meet the return deadline.

R69

Multiple errors.

None

R70

Permissible return entry not accepted.

None

R71

Misrouted dishonored return.

None

R72

Untimely dishonored return.

None

R73

Timely original return.

None

R74

Corrected return.

None

R80

Cross-border payment coding error.

None

R81

Nonparticipant in cross-border program.

None

R82

Invalid foreign receiving DFI identification.

None

PreviousACH transaction statusesNextPaylink

Last updated 1 day ago

Was this helpful?