Request and response codes

sec codes a sec code indicates the standard entry class required by nacha for every ach transaction when you send payment by api, you enter this code in the seccode field of the request the table below explains common sec codes learn more about sec codes on the nacha website which code should i use? your operations support team will guide with this based on the use case you are trying to support code name description type transaction type credit/debit arc accounts receivable entry a single debit entry to an account initiated for purchases or payments that are made in person, via us mail, or placing the payment in a dropbox consumer or non consumer mail order or retail single entry debit only boc back office conversion entry a single debit entry to an account for in person purchases or payments made at the point of purchase check is not returned to check writer consumer or non consumer retail single entry debit only ccd corporate credit/debit entry funds are transferred between unrelated corporate entities or transferred as intra company cash concentration and disbursement transactions non consumer single or recurring entry credit/debit proof of authorization for transactions ran on the web using ccd will adhere to the same requirements as a web transaction retail, phone order, ecommerce, and mail order single or recurring entry credit/debit cie customer initiated entry a single credit entry initiated by a consumer (originator) to a non consumer account cie is a consumer initiated credit entry, a credit push to a merchant, typically used by a financial institution's or third party's bill pay service and would be not be originated by a merchant consumer single entry credit only cor notification of change, or refused notification of change this standard entry class code is used by an rdfi or odfi when originating a notification of change or refused notification of change in automated format it is also used by the ach operator that converts paper notifications of change to automated format consumer or non consumer n/a n/a ctx corporate trade exchange used to transfer funds between a buyer's and a seller's bank accounts non consumer single or recurring entry credit/debit dne (federal govt agency use only) death notification entry a non monetary entry from a federal government agency notifies the financial institution that the recipient of a government benefit has passed away consumer n/a n/a enr automated enrollment entry a non monetary entry that triggers the origination of ach credit or debit transactions to the account holder at the dfi the enr process allows dfis to transmit information to federal government agencies, on behalf of their account holders, that serves as enrollment for either ach credit or debit activity non consumer (federal government agency) n/a n/a iat international ach transaction credit or debit entry is part of a payment transaction that involves a financial agency's office not located within the territorial jurisdiction of the united states note this sec code is implemented only for very specific merchants and is not generally available consumer or non consumer single or recurring entry credit/debit pos point of sale payments see request and response codes /#pos card transaction types consumer single entry credit/debit ppd prearranged payment and deposit entry a single or recurring credit transaction for payment of payroll, expense reimbursement, dividends, retirement, interest, etc consumer single or recurring entry credit/debit rck re presented check entry a re presented check entry with security measures in place consumer single entry debit tel telephone initiated entry a single or recurring debit transaction initiated orally via the telephone consumer single or recurring entry debit web internet initiated entry credit a single or recurring credit transaction from the account of a natural person to the account of a natural person cannot be used for business to consumer transactions debit a single or recurring debit transaction initiated during a secure (minimum 128 bit encryption) internet or mobile session consumer ecommerce single or recurring entry credit or debit rejection codes these codes are returned in the details of the ach payment rejected webhook in the postingcode field code description err general error res account restriction nsf insufficient funds anf account not found cls account closed ina account inactive drm account dormant esc account in escheatment chr account in charge off status stp stop payment active payment types this value appears in the paymenttype field in ach payment responses the paymenttype value tells you what kind of payment was sent do not confuse it with the extendeddetails paymenttype ! type code description origination 0 a new payment originating from either cross river or another bank most payments are of this type return 1 related to a previous origination that has been returned by the receiving bank dishonoredreturn 2 related to a previous return, that has been dishonored by the receiving bank contested return 3 related to a previous origination the receiving bank accepted the original payment but is now notifying you of information you should correct next time you send a payment to this receiver (e g use a different account number) noc 4 notification of change the payment was sent with bad info but the receiving fi fixed it and sent back the information (noc) refused noc 5 payment status this value appears in the status field in ach payment responses status description created we have received the payment, but have not started processing it yet this status should only appear briefly under normal circumstances pending the payment is waiting to be batched and sent to the federal reserve hold payment is being held at the moment and reviewed by our operations team batched the payment has been batched is a final review is being done before we send it out in a file to the federal reserve processing for inbound payments, we are attempting to post the payment to the receiving account for outbound payments, the payment has been sent to the federal reserve, but has not posted yet an outbound standard payment may remain in this status for a day or more same day payments will transition to complete soon after processing completed the payment has been posted and accepted by the federal reserve (in the case of outbound payments) this is a final status rejected our operations team wasn't able to process the payment and has rejected it in the case of inbound, the payment has been returned to the originating bank this is a final status canceled an outbound payment has been canceled at the request of the partner a payment may only be canceled while either pending or on hold this is a final status blocked the cr compliance team blocked the payment return codes sometimes an ach payment is returned by the receiving bank a returncode value appears in the details object of the extended ach return received webhook event code description r01 insufficient funds r02 account closed r03 no account or unable to locate account r04 invalid account number r05 unauthorized debit to consumer account r06 returned per odfi's request r07 authorization revoked by customer r08 payment stopped or stop payment on item r09 uncollected funds r10 customer advises not authorized r11 customer advises entry not in accordance with the terms of the authorization r12 branch sold to another dfi r13 invalid ach routing number r14 representment payee deceased or unable to continue in that capacity r15 beneficiary of account holder deceased r16 account frozen r17 file record edit criteria r18 improper effective entry date r19 amount field error r20 non transaction account r21 invalid company identification r22 invalid individual id number r23 credit entry refused by receiver r24 duplicate entry r25 addenda error r26 mandatory field error r27 trace number error r28 routing number or check digit error r29 corporate customer advises not authorized r30 rdfi not participant in check truncation program r31 permissible return entry r32 rdfi nonsettlement r33 return of xck entry r34 limited participation dfi r35 return of improper debit entry r36 return of improper credit entry r37 source document presented for payment r38 stop payment on source document r39 improper source document r40 return of enr r41 invalid transaction code r42 routing no / check digit error r43 invalid dfi account no r44 invalid individual id no r45 invalid individual / company name r46 invalid representative payee indicator r47 duplicate enrollment r50 state law affecting rck acceptance r51 ineligible / improper item related to rck r52 stop payment on item related to rck r53 item and rck presented for payment r73 timely original return r74 corrected return r75 return not duplicate r76 no errors found r77 non acceptance of r62 r80 iat coding error r81 non participant in iat program r82 invalid foreign rdfi identification r83 foreign rdfi unable to settle r84 not processed by gateway r85 incorrectly coded outbound int’l payment dishonored returns code description r61 misrouted return r62 return of erroneous or reversing debit r63 incorrect dollar amount r64 incorrect individual identification r65 incorrect transaction code r66 incorrect company identification r67 duplicate return r68 untimely return r69 multiple errors r70 permissible return entry not accepted r71 misrouted dishonored return r72 untimely dishonored return ach correction codes there are times when cross river receives an ach notification of change (noc) related to an outbound payment the reasoncode field in the extended ach noc received webhook event provides the correction code indicating what information was wrong and needed to be changed for the payment to settle code description c01 incorrect dfi account number c02 incorrect routing number c03 incorrect routing number and incorrect dfi number c04 incorrect individual name/receiving company name c05 incorrect transaction code c06 incorrect dfi account number and incorrect transaction code c07 incorrect routing number, incorrect dfi account number, and incorrect transaction code c08 incorrect receiving dfi identification (iat only) c09 incorrect identification number c13 addenda format error c14 incorrect sec code for outbound international payment pos card transaction types if the request and response codes /#sec codes value in the request is pos , in the extendeddetails object you must include a value for the cardtransactiontype type description 01 purchase of goods 02 cash 03 return reversal 11 purchase reversal 12 cash reversal 13 return 21 adjustment 99 misc transaction iat transaction types when sending an iat transaction, you must also supply a code for the transaction type in the iatdetails transactiontypecode field code description ann annuity bus business/commercial dep deposit loa loan mis miscellaneous mor mortgage pen pension rem remittance rls rent/lease sal salary/payroll tax tax arc accounts receivable entry boc back office conversion entry mte machine transfer entry pop point of purchase entry pos point of sale entry rck re presented check entry tel telephone initiated entry web internet initiated entry nacha field mappings this table presents field names as they appear in a nacha record and how they appear in cr apis nacha record nacha field cross river api field batch company name originator name batch company discretionary data originator data batch company identification originator identification batch standard entry class code seccode batch company entry description description batch company descriptive date n/a batch effective entry date effectivedate batch settlement date settlementdate batch originator status code n/a batch originating dfi identification originator routingnumber entry transaction code transactiontype / receiver accounttype entry receiving dfi identification receiver routingnumber entry dfi account number receiver accountnumber entry amount amount entry individual identification number receiver identification entry individual name receiver name entry discretionary data receiver data /extendeddetails paymenttype (web/tel only) entry trace number tracenumber addenda (05) payment related information addenda (only one informational addenda record is supported)