This page provides reference information for processing ACH payments with one of Maast's APIs. For guidance on implementation, see the ACH section in the appropriate API's guide.

For information on processing ACH payments through Hosted Checkout, see the Hosted Checkout implementation guide. For more information on processing ACH payments through the Maast Virtual Terminal, see ACH Payments in the Maast Knowledge Base.

Sample Consent Statement

Below is a sample consent statement that you may use if you add ACH payment capacity through the Payment Gateway API, Recurring Billing API, or embedded fields:

I authorize <name of your business> to initiate a one-time electronic funds transfer for the payment described above from my bank account under the terms of this authorization on <today’s date>, which will be processed on the next business day. This payment can be revoked by calling <your business phone number>.

Payment Gateway API Conventions for ACH

This section provides conventions for handling ACH payments through the Payment Gateway API.

ACH Sale Conventions

The table below describes the fields used to configure ACH payments in a Payment Gateway API sale request. See Sale (Auth + Capture) in API Reference for more information and the Payment Gateway API Sale guide for instructions on sending a sale request:

Field	Format	Description
`merchant_id`	Variable length, up to 12 N	Unique identifier in the Maast system.
`dda_number`	Variable length, 5 to 17 N	The owner's account number at the bank.
`tr_number`	Fixed length, 9 N	The bank transit/routing number.
`type_id`	Fixed length, 1 AN	The bank account type. Possible values: • C = Personal checking account • S = Personal savings account • K = Business checking account • V = Business savings account
`amt_tran`	Variable length, up to 12,2 N	The total amount of the transaction including sales tax (`amt_tax`) and convenience fee (`amt_convenience_fee`) if applicable. Note: • For ACH payments, the max transaction amount is $99,999.99 USD. • USD is the only supported currency for ACH payments.
`amt_convenience_fee`	Variable length, up to 8,2 N, optional	The amount of the convenience fee. A convenience fee is a flat/fixed fee charged to your customer for the privilege of paying for a product or service using a non-standard method of payment. This field tracks the convenience fee amount for display purposes, but the amount of the fee must be included in `amt_tran`.
`cardholder_name`	Variable length, up to 64 AN	Your customer’s name. When provided in a tokenize request, the cardholder’s name is stored along with the card number and expiration date. For ACH payments, this field is required and must contain the name on the account at the financial institution; if longer than 22 characters, it is truncated before being sent to the financial institution
`tran_currency`	Fixed length, 3 N, optional	The ISO numeric currency code for the transaction. For ACH payments this must be set to `840` or omitted.
`tokenize`	Boolean, optional	The merchant can set this to `true` in an authorization, credit, force, sale, or verify request. The payment gateway then stores the card data and provides a `card_id` in the response. If the `card_number` or `card_id` in the request is already saved, this flag instructs the payment gateway to update any associated data provided (e.g. `avs_address`, `avs_zip`, `exp_date`).

ACH Void Conventions

The table below shows the field used in a Payment Gateway API void request to void an ACH transaction. See Void a Previously Authorized Transaction in API Reference for more information and the Payment Gateway API Void guide for instructions on sending a void request:

Field	Format	Description
`merchant_id`	Fixed length, 12 N	Unique identifier in the Maast system.

ACH Refund Conventions

The table below shows the fields used to configure ACH payments in a Payment Gateway API refund request. See Refund Previously Captured Transaction in API Reference for more information and the Payment Gateway API Refund guide for instructions on sending a refund request:

Field	Format	Description
`merchant_id`	Fixed length, 12 N	Unique identifier in the Maast system.
`amt_tran`	Variable length, up to 12,2 N	The total amount to refund. Partial refunds are allowed by providing an amount in this field that is less than the total original transaction amount.

Checkout API Conventions for ACH

When creating a dynamic checkout payment link, the following fields are available in the preferences object to specify ACH payments options. See Create a Checkout Link in API Reference for more information and the Dynamic Link Method guide for integration instructions:

Field	Format	Description
`allow_ach_payment`	Boolean	Applicable only if your merchant account is configured to take ACH payments. If set to `true`, the checkout page will present ACH as one of the possible payment modes. By default, this is set to `false`.
`request_type`	Fixed length, 4 A	Identifies the type of request when the customer submits the payment data on the checkout page. For ACH payments, this must be set to `sale`.

Invoicing API Conventions for ACH

Maast’s Invoicing API resource uses Maast invoice settings. The following field is available for configuring ACH payment options through the Invoicing API resource. See Create an Invoice in API Reference for more information and the Invoice API Create an Invoice guide for instructions on sending the request:

Field	Format	Description
`allow_ach_payment`	Boolean	Applicable only if your merchant account is configured to take ACH payments. If set to `true`, the checkout page will present ACH as a possible payment mode. By default, this is set to `false`.

Embedded Fields Conventions for ACH

The following field is available to configure ACH payment options for embedded fields. See the Embedded Fields Payments guide for instructions on setting up embedded fields and populating this JSON:

Field	Format	Description
`achConfig`	JSON, optional	If your account is enabled to process ACH payments, this controls the display of an ACH payment option on the embedded form.

Customer Vault Conventions for ACH

This section provides conventions for using ACH payment information with our Customer Vault API resource.

New Customer with ACH Billing Method

The table below shows the fields available for adding a customer with ACH payment information using the Customer Vault API. See Add a Customer in API Reference for more information and the Customer Vault API Add a Customer guide for instructions:

Field	Format	Description
`customer_first_name`	Variable length, up to 32 AN	The customer's first name.
`customer_last_name`	Variable length, up to 32 AN	The customer's last name.
`customer_id`	Variable length, up to 32 AN	Unique customer ID value established by the merchant. This can be used to add subscriptions through the Recurring Billing API or make payments through the Payment Gateway API. Once established, this ID cannot be updated. This field is case sensitive. Only letters and numbers are allowed in a customer ID. Conditional Requirement: Either `customer_id` or `auto_generate_customer_id` is required to add a new customer.
`auto_generate_customer_id`	Boolean	Boolean flag that indicates if the customer ID should be auto-generated. By default, this is `false`. When set to `true`, we will generate a unique customer ID, returned as `customer_id` in the response. Use it to manage the customer through the API. Conditional Requirement: Either `customer_id` or `auto_generate_customer_id` is required to add a new customer.
`billing_cards`	Array	An array of payment methods (cards or ACH). One of the methods should be designated as the default, if not, the system will choose one of the methods to be the default. See the `billing_cards` Array Fields table below.

`billing_cards` Array Fields: New Customer with ACH

When using the Customer Vault API 'Add a Customer' request, the following fields are available in the billing_cards array to send ACH payment information. See Add a Customer in API Reference for more information and the Customer Vault API Add a Customer guide for instructions:

Field	Format	Description
`billing_first_name`	Variable length, up to 32 AN	The billing first name. This is required when adding an ACH account number.
`billing_last_name`	Variable length, up to 32 AN	The billing last name. This is required when adding an ACH account number.
`dda_number`	Variable length, 5 to 17 N	The owner's account number at the bank. This is required when adding an ACH account number.
`tr_number`	Fixed length, 9 N	The bank transit/routing number. This is required when adding an ACH account number.
`type_id`	Fixed length, 1 AN	The bank account type. Possible values: • `C` - Personal checking account • `S` - Personal savings account • `K` - Business checking account • `V` - Business savings account

Add ACH Billing Method to an Existing Customer

When sending a Customer Vault API 'Add a Payment Method' request, the following fields are available to send ACH payment information. See Add a Payment Method in API Reference for more information and the Customer Vault API Add a Payment Method guide for instructions:

Field	Format	Description
`type_id`	Fixed length, 1 AN	The bank account type. Possible values: • `C` - Personal checking account • `S` - Personal savings account • `K` - Business checking account • `V` - Business savings account
`dda_number`	Variable length, 5 to 17 N	The owner's account number at the bank. This is required when adding an ACH account number.
`tr_number`	Fixed length, 9 N	The bank transit/routing number. This is required when adding an ACH account number.
`billing_first_name`	Variable length, 32 AN	The billing first name. This is required when adding an ACH account number.
`billing_last_name`	Variable length, 32 AN	The billing last name. This is required when adding an ACH account number.

Webhooks ACH Conventions

When configuring a webhook, the following event is available to configure notifications of ACH payment status updates such as a reject or late return. See the Webhooks API Add an Event guide for instructions:

Event	Event Schema	Description
`transaction_status_updated`	`transactions`	Returns an array of data on the transactions whose status has been updated by the nightly settlement and funding runs.

ACH Payment and Validation Response Codes

This section provides response conventions for ACH payment and validation requests.

ACH Authorization Code Responses

The table below shows information on all ACH authorization codes that can appear in the auth_code field of a sale or authorization response. See ACH Validation for more information:

ACH Authorization Code	Response is Considered	Response Text	Description
2222	Ok	Pass AMEX	AMEX Cheque - The account was found to be an open and valid American Express account.
3333	Ok	Pass NPP	Non-Participant Provider - This account was reported with acceptable, positive data found in recent or current transactions.
5555	Ok	Pass SAV	Savings Account Verified - The savings account was found to be an open and valid account.
7777	Ok	Pass AV	Account Verified - The checking account was found to be open and have a positive history.
8888	Ok	Pass SAV	Savings Account Verified - The savings account was found to be open and have a positive history.
9999	Ok	Pass NPP	This account was reported with acceptable, positive data found in recent transactions. Positive history exists for multiple transactions.
GN01	Ok	Negative Data	Negative information was found.
GN05	Decline	Unassigned Routing Number	The routing number supplied is reported as not assigned to a financial institution.
GP01	Ok	Private Bad Checks List - Variable	The value for Details will vary depending on the value set for CheckReject reason in the Private Bad Checks List.
GS01	Decline	Invalid Routing Number	The routing number supplied does not match the format of a valid routing number.
GS02	Decline	Invalid Account Number	The account number supplied does not match the format of a valid account number.
GS03	Decline	Invalid Check Number	The check number supplied does not match the format of a valid check number.
GS04	Decline	Invalid Amount	The amount supplied does not match the format of a valid amount.
ND00	Ok	No Data	No positive or negative information has been reported on the account. This could be a small or regional bank that does not report.
ND01	Ok	No Data - US Government Only	No positive or negative information has been reported on the account. This routing number can only be valid for U.S. Government financial institutions. Please verify this item with its issuing authority.
RT00	Ok	No Information Found	The routing number appears to be accurate; however, no positive or negative information has been reported on the account. Please contact the customer to ensure that the correct account information was entered.
RT01	Decline	Declined	This account should be returned based on the risk factor being reported.
RT02	Ok	Reject Item	This item should be returned based on the risk factor being reported.
RT03	Ok	Accept With Risk	Current negative data exists on this account. Accept transaction with risk. (Ex: Checking or savings accounts in NSF status, recent returns, or outstanding items.)
RT04	Decline	Non Demand Deposit Account	This is a Non Demand Deposit Account (post no debits), Credit Card Check, Line of Credit, Home Equity, or a Brokerage check.
RT05	Ok	Accept With Risk	Recent negative data exists on this account. Accept transaction with risk. (Ex: Checking or savings accounts in NSF status, recent returns, or outstanding items.)

ACH Response Code 119 Detail Codes and Descriptions

The table below shows all detail codes and descriptions that can be appended to a reason code (rcode) 119, "ACH payment data is invalid," in an ACH payment or verification response. See ACH Validation for more information:

ACH Response Code 119 Detail Code	ACH Response Code 119 Detail Description
C01	Incorrect bank account number
C02	Incorrect transit/routing number
C03	Incorrect transit/routing number and bank account number
C06	Incorrect bank account number and transit code
C07	Incorrect transit/routing number, bank account number, and payment code
I08	Invalid routing number
I24	Previously received R02, R03, R04, R20 on this account
R02	Bank account closed
R03	No bank account, or unable to locate account
R04	Invalid bank account number
R12	Branch sold to another RDFI
R13	RDFI not qualified to participate
R14	Representative payee deceased or unable to continue in that capacity
R15	Beneficiary or bank account holder deceased
R16	Bank account frozen
R20	Non-payment bank account
R28	Transit routing number check digit error

ACH Payment Reject Codes

ACH payment rejections can be received up to 60 days after an ACH transaction. The table below shows the possible reject codes with their reasons and descriptions:

Reason	Description
R01 - Insufficient Funds	The available balance is not sufficient to cover the dollar value of the debit entry.
R02 - Account Closed	This is a previously active account that has been closed by the customer or RDFI.
R03 - No Account/Unable to Locate Account	The account number structure is valid and passes the editing process, but it does not correspond to an individual, or it is not an open account.
R04 - Invalid Account Number	The account number structure not valid. The entry may fail check digit validation or may contain an incorrect number of digits.
R05 - Unauthorized Debit Entry	Account number structure not valid. The entry may fail check digit validation or may contain incorrect number of digits.
R06 - Returned per ODFI's Request	ODFI has requested RDFI to return the ACH entry. (This is optional for RDFI. ODFI indemnifies RDFI.)
R07 - Authorization Revoked by Customer	This is a previously-authorized ACH payment. The consumer has revoked authorization from the Originator. This must be returned no later than 60 days from settlement date, and the customer must sign the affidavit.
R08 - Payment Stopped or Stop Payment on Item	The Receiver of a recurring debit transaction has stopped payment on a specific ACH debit. When a request for stop payment is made, RDFI should verify the Receiver's intent to ensure this is not meant to be a revocation of the authorization.
R09 - Uncollected Funds	A sufficient book or ledger balance exists to satisfy the dollar value of the transaction, but the dollar value of transactions in the process of collection (i.e., uncollected checks) brings the available and/or cash reserve balance below the dollar value of the debit entry.
R10 - Customer Advises Not Authorized; Item Is Ineligible, Notice Not Provided, Signatures Not Genuine, or Item Altered	The consumer has advised RDFI that the Originator of the transaction is not authorized to the debit account. This must be returned no later than 60 days from the settlement date of original entry, and the customer must sign the affidavit.
R11 - Check Truncation Entry Return	Used when returning a check truncation entry. This reason for return should be used only if no other return reason code is applicable. RDFI should use the appropriate field in addenda record to specify the reason for return (i.e., "exceeds dollar limit," "stale date," etc.).
R12 - Branch Sold to Another DFI	A financial institution may continue to receive entries destined for an account at a branch that has been sold to another financial institution. Because the RDFI no longer maintains the account and is unable to post the entry, it should return the entry to the ODFI.
R13 - RDFI Not Qualified to Participate	The financial institution is not qualified to participate in ACH or the routing number is incorrect.
R14 - Representative Payee Deceased or Unable to Continue in that Capacity	The representative payee is a person or institution authorized to accept entries on behalf of one or more other persons, such as legally incapacitated adults or minor children. The representative payee is either deceased or unable to continue in that capacity. The beneficiary is not deceased.
R15 - Beneficiary or Account Holder (Other Than a Representative Payee) Deceased	One of the following has occurred: • The beneficiary is the person entitled to the benefits and is deceased. The beneficiary may or may not be the account holder; or • The account holder (acting in a non-representative payee capacity) is an owner of the account and is deceased.
R16 - Account Frozen	Funds are unavailable due to legal action or specific action by the RDFI.
R17 - File Record Edit Criteria	Some fields that are not edited by the ACH Operator are edited by the RDFI. If the entry cannot be processed by the RDFI, the field(s) causing the processing error must be identified in the addenda record information field of the return.
R18 - Improper Effective Entry Date	The effective entry date for a credit entry is over two banking days after the banking day of processing as established by the ODFI, or the effective entry date for a debit entry is more than one banking day after the processing date.
R19 - Amount Field Error	The amount field is unable to be recorded. This typically arises because the amount field is non-numeric, zero, or exceeding $25,000.
R20 - Non-Transaction Account	The ACH entry is destined for a non-transaction account (i.e., an account against which transactions are prohibited or limited).
R21 - Invalid Company Identification	The identification number used in the company identification field is not valid. This is generally used on CIE transactions.
R22 - Invalid Individual ID Number	The Receiver has indicated to the RDFI that the number with which the Originator was identified is not correct. In CIE and MTE entries, the individual ID number is used by the Receiver to identify the account.
R23 - Credit Entry Refused by Receiver	The Receiver refuses the credit entry due to one of the following conditions: • The minimum amount required by the Receiver has not been remitted. • The exact amount required has not been remitted. • The account is subject to litigation, and the Receiver will not accept the transaction. • Acceptance of transaction would result in an overpayment. • The Originator is not known by the Receiver. • The Receiver has not authorized the credit entry.
R24 - Duplicate Entry	The RDFI has received what appears to be a duplicate entry: the trace number, date, dollar amount, and/or other identifying data match another transaction.
R25 - Addenda Error	Addenda record indicator value is incorrect.
R26 - Mandatory Field Error	Erroneous data or missing data in a mandatory field.
R27 - Trace Number Error	One of the following is the case: • Original entry trace number is not present in the addenda record on a return or notification of change entry. • The trace number of an addenda record is not the same as the trace number of the preceding entry detail record.
R28 - Routing Number Check Digit Error	The check digit for a routing number is invalid. This is the routing number of the institution receiving the return and is found in the entry detail record.
R29 - Corporate Customer Advises Not Authorized	The RDFI has been notified by the Receiver (non-consumer) that the Originator of a given transaction has not been authorized to debit the Receiver’s account.
R30 - RDFI Not Participant in Check Truncation Program	The RDFI doesn’t participate in a check truncation program. (A check truncation program makes it possible to clear a check electronically.)
R31 - Permissible Return Entry (CCD and CTX only)	The RDFI has been notified by the ODFI that the ODFI agrees to accept a return entry beyond the normal return deadline.
R32 - RDFI Non-Settlement	The RDFI is unable to settle the entry.
R33 - Return of XCK Entry	The RDFI, at its discretion, returns a destroyed check (XCK) entry. XCK entries may be returned up to 60 days after the settlement date.
R34 - Limited Participation DFI	The RDFI's participation has been limited by a federal or state supervisor.
R35 - Return of Improper Debit Entry	Debit entries are not permitted for CIE entries or to loan accounts (except Reversals).
R36 - Return of Improper Credit	ACH credit entries are not permitted for ARC, BOC, POP, RCK, TEL or XCK entries (except Reversals).
R37 - Source Doc Presented for Payment	The source document (the check) to which an ACH entry relates has been presented for payment.
R38 - Stop Payment on Source Document	A stop payment order was placed on the source document (the check); however, the item cleared and the RDFI’s system did not catch it.
R39 - Improper Document/Source Document Presented for Payment	The source document presented for payment was incorrect.
R40 - Return of ENR Entry by Federal Government Agency	The Federal Government agency indicated in the ENR does not participate in the Automated Enrollment Program.
R41 - Invalid Transaction Code (ENR only)	The transaction code does not conform to ACH record format specifications, or it is not appropriate with regard to an ENR.
R42 - Routing Number/Check Digit Error (ENR only)	The routing number and/or the check digit is not a valid number, or it does not conform to the proper format.
R43 - Invalid DFI Account Number (ENR only)	The Receiver’s account number is missing, or it exceeds 17 N, or it contains invalid characters.
R44 - Invalid Individual ID Number or Identification Number (ENR only)	The Individual Identification Number or the Identification Number provided does not match a corresponding ID number in the Federal Government agency’s records.
R45 - Invalid Individual Name or Company Name (ENR only)	The name of the Receiver either does not match Federal agency records or fails to include at least one alphanumeric character.
R46 - Invalid Representative Payee Indicator (ENR only)	The Representative Payee Indicator Code has been omitted or is not consistent with the Federal Agency’s records.
R47 - Duplicate Enrollment (ENR only)	The Federal agency has received duplicated ENR entries from the same DFI.
R48 - Reserved	No description is available.
R49 - Reserved	No description is available.
R50 - State Law Affecting RCK Acceptance	One of the following is true: • The RDFI is located in a state that does not allow for electronic presentment. • The RDFI is located within a state that requires all canceled checks to a specific type of account to be returned to the Receiver within the periodic statement.
R51 - Item Related to RCK Entry Is Ineligible or RCK Entry Is Improper	One of the following has occurred: • The RCK item is considered ineligible. • The originator did not give notice of the RCK policy. • The signature on the item was not genuine. • The item has been altered. • The amount was not accurately obtained from the item.
R52 - Stop Payment on Item Related to RCK Entry	A stop payment order has been placed on the item (the check) to which the RCK entry relates.
R53 - Item and RCK Entry Presented for Payment	In addition to the RCK entry, the item (the check) to which the RCK entry relates has also been presented for payment.
R54 - Reserved	No description is available.
R55 - Reserved	No description is available.
R56 - Reserved	No description is available.
R57 - Reserved	No description is available.
R58 - Reserved	No description is available.
R59 - Reserved	No description is available.
R60 - Reserved	No description is available.
R61 - Misrouted Return	The financial institution preparing the return entry (the RDFI of the original entry) has placed the incorrect transit/routing number in the receiving DFI identification field. May be used for all entries except IAT.
R62 - Return of Erroneous or Reversing Debit	The ODFI’s use of the reversal process has resulted in or failed to correct an unintended credit to the receiver. One of the following is true: • An erroneous debit entry and a subsequent credit-reversing entry were both transmitted to the receiver’s account. The erroneous debit entry is being returned, but the credit-reversing entry is posted and made available to the receiver. • An erroneous credit entry and a subsequent debit-reversing entry were both transmitted to the receiver’s account. The debit-reversing entry is being returned, but the erroneous credit entry is posted and made available to the receiver. May be used for all entries except IAT.
R63 - Incorrect Dollar Amount	The dollar amount in the entry detail record of the return is different from the dollar amount of the original entry.
R64 - Incorrect Individual Identification	The individual ID number reflected in the entry detail record of the return is different from the individual ID number used in the original entry.
R65 - Incorrect Transaction Code	The transaction code in the entry detail record of the return is not the return equivalent of the transaction code in the original entry. (All entries must be returned as received, i.e., credit as credit, debit as debit, demand as demand, savings as savings.)
R66 - Incorrect Company Identification	The company ID number used in the company/batch header record of the return is different from the ID number used in the original entry.
R67 - Duplicate Return	The ODFI has received more than one return for the same entry. May be used for all entries except IAT.
R68 - Untimely Return	The return was not sent within the time frame established by the rules. May be used for all entries except IAT.
R69 - Field Error(s)	One or more of the following field requirements are incorrect: • DFI account number • Original entry trace number • Dollar amount • Individual Identification Number/Identification Number • Transaction code • Company Identification Number • Effective entry date May be used for all entries except IAT.
R70 - Permissible Return Entry Not Accepted or Return Not Requested by ODFI	The ODFI has received a return entry identified by the RDFI as being returned with the permission of, or at the request of, the ODFI; however, the ODFI has not agreed to accept the entry or has not requested the return of the entry. This code may be used only to dishonor return entries containing return reason codes R06 and R31. May be used for all entries except IAT.
R71 - Misrouted Dishonored Return	The ODFI of the original entry has placed the incorrect routing number in the receiving DFI identification field. May be used for all entries except IAT.
R72 - Untimely Dishonored Return	The dishonored return entry has not been sent within the designated timeframe. May be used for all entries except IAT.
R73 - Timely Original Return	The RDFI is certifying that the original return entry was sent within the timeframe designated in the rules. May be used for all entries except IAT.
R74 - Corrected Return	The RDFI is correcting a previous return entry that was dishonored using return reason code R69 ('Field Error(s)') because it contained incomplete or incorrect information. Data must be obtained from the following fields in the original company batch header record, entry detail record or addenda record: • DFI account number • Trace number • Amount • Individual Identification Number/Identification Number • Transaction code • Company identification • Effective entry date May be used for all entries except IAT.
R77 - Non-Acceptance of R62 Dishonored Return	One of the following has occurred: • The RDFI returned both the erroneous entry and the related reversing entry. • The funds relating to the R62 dishonored return are not receivable from the Receiver. May be used for all entries except IAT.
R80 - IAT Entry Coding Error	The IAT entry is being returned because one of the following is invalid: • DFI/bank branch country code • DFI/Bank Identification Number qualifier • Foreign exchange indicator • ISO originating currency code • ISO destination currency code • ISO destination country code • Transaction type code For gateway use with outbound IAT entries only.
R81 - Non-Participant in IAT Program	The IAT entry is being returned because the gateway does not have an agreement with either the ODFI or the gateway’s customer to transmit IAT entries. For gateway use with outbound IAT entries only.
R82 - Invalid Foreign Receiving DFI Identification	The reference used to identify the foreign receiving DFI of an outbound IAT entry is invalid. For gateway use with outbound IAT entries only.
R83 - Foreign Receiving DFI Unable to Settle	The IAT entry is being returned due to settlement problems in the foreign payment system. For gateway use with outbound IAT entries only.
I00 - Previously Received R02, R03, R04, R20 on This Account (RCK)	No description is available.
I01 - Invalid Amount	No description is available.
I02 - Transaction Still Pending	No description is available.
I03 - Check Represented Maximum Times	No description is available.
I04 - Max Check Amount Exceeded	No description is available.
I05 - Max Fee Exceeded	No description is available.
I06 - Invalid Date	No description is available.
I07 - Transaction Too Old	No description is available.
I08 - Invalid Routing Number	No description is available.
I09 - Duplicate in Batch	No description is available.
I10 - Duplicate from Other Customer	No description is available.
I11 - Fee Rejected for Invalid Check	No description is available.
I12 - Duplicate in POS Batch	No description is available.
I13 - Voided POS Transaction	No description is available.
I14 - Invalid Account Number	No description is available.
I15 - Invalid Check Number	No description is available.
I16 - Missing Amount	No description is available.
I17 - Invalidated per Request	No description is available.
I18 - Item Paid	No description is available.
I19 - Reserved	No description is available.
I20 - Item Refunded	No description is available.
I22 - Invalid POS Transaction	No description is available.
I23 - Previously Received ARC/LBX Transaction	No description is available.
I24 - Previously Received R02, R03, R04, R20 on This Account (RCK)	No description is available.
I25 - Previously Received R02, R03, R04, R20 on This Account (EFT)	No description is available.
I26 - EFT Received Within Window	No description is available.
I27 - EFT Too Old	No description is available.
I28 - Void Transaction Successful	No description is available.
I29 - Void Could Not Be Matched	No description is available.
I30 - POS Batch Duplicated (Re-processed)	No description is available.
I31 - Lockbox Amount Over 5000	No description is available.
I32 - RCK Name Missing	No description is available.
I33 - Remote Deposit Amount Over Limit	No description is available.
I34 - Max ARC/BOC Amount Exceeded	No description is available.
I35 - Not In LBX System	No description is available.
I40 - Previously Received R07, R08, R10 on This Account	No description is available.
I41 - RCK Over 120 Days Old	No description is available.

ACH Testing

The Maast sandbox accepts any real routing number (tr_number) and any 5-17 digit account number (dda_number). Most banks list their routing numbers on their websites. To simulate a failure, enter a routing number that does not exist (0000000).