Code Reference

Ingo Payments returns numeric status codes across both synchronous API responses and asynchronous webhook events. Understanding the code structure helps you build reliable integrations that handle outcomes correctly — whether the code arrives in a response body or a webhook payload, the category and description apply the same way.

Ingo codes are normalized. Where an outcome originates with an upstream provider — a card network, an issuer, a bank, or a verification vendor — Ingo maps that provider’s response into a single Ingo code set before returning it to you. Integrate against Ingo values rather than provider-specific ones: your contract stays stable when a provider changes its response format and when Ingo adds support for an additional provider.

Code families at a glance

Every response code falls into a family that signals the category of outcome. Use this table to understand the meaning of any code range at a high level and determine the right action for your integration.

Code Range	Category	Meaning	Recommended Action
`100–110`	Success	Transaction completed, in progress, or idempotent result returned	No action required
`111–129, 131–132`	Soft Verification Results	Transaction approved; a verification check returned a partial or inconclusive result	Proceed; review the specific code if downstream action is needed
`4xx`	Request & Auth Errors	The request was rejected due to bad input, invalid credentials, or a suspended account	Fix the request before retrying — these errors will not self-resolve
`5xx`	System & Communication Failures	A timeout, routing failure, or unexpected error occurred	Retry with exponential backoff; contact Ingo support if persistent
`600–616`	Validation & Velocity Errors	A field failed validation or a program limit was reached	Correct the field value, amount, or transaction timing
`700–742`	Transaction & Routing	A transaction-level outcome — destination unavailable, limit exceeded, or routing issue	Check the specific code; most are terminal for the current attempt
`750–815`	Card Data & Token Errors	Card input is invalid, a token is missing or incorrect, or track data is required	Correct input or re-tokenize the account
`851–867`	Card Issuer Declines	The card issuer rejected the transaction	Do not retry automatically; direct the recipient to contact their card issuer
`9xx`	General System Errors	An unclassified internal error occurred	Contact Ingo support; include the timestamp and `participant_unique_id1`
`780–787`	Notify Transaction Status	A Notify disbursement is in an incompatible state for the requested action	Check the transaction’s current state before retrying
`1100–1170`	Notify — Auth, Verification & Payment Events	Authentication, identity verification, OFAC screening, and payment status codes shared across all Notify products	Informational — review the specific code for the lifecycle stage
`1123–1124, 1171–1172`	Notify — Managed Parties Approvals	Approval decision, completion, and payment suspended codes specific to multi-party disbursement flows	Informational — approval decisions gate payment release
`1200–1246`	Notify — Notification Events	Email and SMS notification delivery codes sent to recipients and parties throughout the disbursement lifecycle	Informational — confirms what communication was sent
`1300–1303`	Banking Platform	Entity, ledger, transaction, and hold lookup failures specific to the Ingo Banking Platform	Check the specific resource identifier in the request
`1310–1320`	ACH Reinitiation	Eligibility failures returned when an ACH debit is submitted for reinitiation	Review the specific reason — most are terminal for the referenced transaction

Codes in the 1100–1246 range are Notify product event codes. They appear in webhook payloads and, in some cases, synchronous API responses depending on the integration point. Codes in the 130 and 1106–1108 range appear in both contexts depending on your program configuration.

Status & Event Code Reference

Success & Idempotency (100–110)

Code	Message	Applicable Call	Description
`100`	Success	Verify, Process, Search	Transaction completed successfully.
`101`	Success — Idempotent Response	Verify, Process	The `participant_unique_id1` was previously processed successfully. No new transaction was created.
`102`	Success — Pending Issuer Response	Process	Response from issuer not received within the configured timeout. Applicable to push transactions.
`103`	Success — Payment Request Queued	Async Process	Async process request accepted and queued for processing.
`104`	In Progress — Idempotent Response	Process	A prior request with this `participant_unique_id1` is still processing. No new posting attempt was initiated.

Soft Verification Results (111–129, 131–132)

These codes indicate the transaction was approved but a verification check returned a partial, inconclusive, or non-matching result. Review the specific code to determine whether downstream action is appropriate for your program configuration.Card — AVS (Address Verification Service)

Code	Description
`111`	Street address matches; zip does not
`112`	Street address matches; zip could not be verified (incompatible format)
`113`	Street address and zip could not be verified (incompatible formats)
`114`	Issuer is not an AVS participant or did not return a result
`115`	Address information not verified
`116`	No Match
`117`	Zip matches; street address could not be verified (incompatible format)
`118`	Issuer unavailable or timed out
`119`	Zip matches; street address does not

Card — ANI (Account Name Identification)

Code	Description
`127`	Account name partial match
`128`	Account name no match
`131`	Match not performed
`132`	Match not supported

Bank Account — ANV / NAV (Account & Name Validation)

Code	Description
`122`	No data available or non-participating issuer (ANV)
`123`	No data available from issuer (NAV)
`124`	Address did not match (NAV)
`125`	Customer name or name and address did not match (NAV)
`126`	Customer or business name did not match (NAV)

Auth & Request Errors (400–415, 516, 530, 609–610, 612–614)

These codes indicate the request was rejected before processing. Correct the issue before retrying — they will not self-resolve.

Code	Message	Description
`400`	Transaction Failure	One or more required parameters are missing or null
`401`	Transaction Failure	Request parameters are incorrect
`402`	Transaction Failure	Timestamp in signature is too distant from current time (clock skew)
`403`	Transaction Failure	API key does not exist
`404`	Transaction Failure	API key has been suspended
`405`	Transaction Failure	Client has been temporarily suspended
`406`	Transaction Failure	Participant ID does not exist
`407`	Transaction Failure	Participant signature does not match expected value
`408`	Transaction Failure	Authorization failure
`412`	Transaction Failure	Unsupported HTTP method
`413`	Transaction Failure	Invalid S2P type
`414`	Transaction Failure	Invalid debit type
`415`	Transaction Failure	Route API disabled
`516`	Transaction Failure	Unauthorized distribution type
`530`	Transaction Failure	Unauthorized account type
`609`	Transaction Failure	Invalid request to payment gateway
`610`	Unauthorized	Auth token has been used the maximum permitted number of times — create a new auth token
`612`	Unauthorized	Invalid or unauthorized value for `source_of_funds`
`613`	Unauthorized	Participant not enabled for `third_party_token`
`614`	Unsupported	Third-party token provider not currently supported

System & Communication Failures (500–502, 523–525, 706–763, 900–901, 990, 999)

These codes indicate a timeout, routing failure, or unexpected system error. They are transient and retry-eligible. See the Retry Logic guide for recommended retry intervals based on your customer experience model. Contact Ingo support if the error persists, and include the timestamp and participant_unique_id1 from the failed request.

Code	Description
`500`	General error — contact Ingo Payments support immediately
`501`	Response from endpoint was invalid
`502`	Process timeout
`523`	AVS service connection error
`524`	AVS response parse failure
`525`	AVS response bad structure
`706`	Transaction routing failure
`707`	Transaction routing failure
`709`	Transaction routing failure
`717`	Transaction routing failure
`718`	Transaction routing failure
`750`	Response from endpoint not recognized
`751`	Response from endpoint not defined
`763`	Route not configured for client processing
`802`	Banking Platform transaction routing failure
`900`	Account identity lookup error
`901`	Account identity lookup error
`990`	General error — contact Ingo Payments support
`999`	General error — contact Ingo Payments support

Validation & Velocity Errors (600–616, 711–725, 975)

These codes indicate a field validation failure or a program limit has been reached. Correct the field value, transaction amount, or verify the transaction is within your configured program limits before retrying.

Code	Description
`600`	Field validation error — see validation error details in the response
`603`	Transaction amount is outside your allowed range (above max or below min)
`604`	Insufficient funds — amount exceeds prefund balance or daily processing cap
`615`	Invalid transaction amount
`616`	Invalid transaction type
`711`	Exceeds single transaction amount limit
`712`	Exceeds daily transaction amount limit
`713`	Exceeds rolling 7-day transaction amount limit
`714`	Exceeds rolling 30-day transaction amount limit
`715`	Exceeds maximum transactions per rolling 30-day period
`716`	Exceeds rolling 15-day transaction amount limit
`719`	Transaction amount is below the issuer minimum
`720`	Transaction amount is above the issuer maximum
`722`	Exceeds maximum amount per store daily limit (retail clients)
`723`	Exceeds maximum transactions per store daily limit (retail clients)
`724`	Store not authorized for this transaction type (retail clients)
`975`	Routing disabled by sponsor bank — contact Ingo support

Transaction & Routing (700–742, 790, 1130)

Code	Description
`700`	Account not currently available for processing
`701`	Payment destination no longer available for processing
`703`	Issuer or Payee ID does not exist
`708`	Transaction attempted is invalid
`710`	Issuer declined — customer should contact their card issuer
`721`	Payment causes card balance to exceed the total allowable limit
`790`	Declined — Stand In; issuer response not received within timeout (pull transactions)
`1130`	Real-Time Payments (RTP) attempted; retried via standard bank account network

Card Verification Declines (510–515, 753–815, 1041–1042)

Hard declines from card verification services. These are terminal for the current attempt — the recipient’s card data does not pass the configured verification checks.AVS Hard Declines

Code	Description
`510`	AVS timeout
`513`	AVS unknown error
`753`	Declined — street matches, zip does not
`754`	Declined — street matches, zip incompatible format
`755`	Declined — street and zip incompatible formats
`756`	Declined — issuer not participant or no result
`757`	Declined — address not verified
`758`	Declined — no match
`759`	Declined — zip matches, street incompatible format
`760`	Declined — retry; issuer unavailable or timed out
`764`	Declined — zip matches, street does not

An AVS failure may be reported with any of five codes depending on the failure mode. Integrations that only handle 510 should be prepared to also receive 523 (connection error), 524 (parse failure), and 525 (bad structure). 510 and 513 are AVS verification outcomes and are terminal for the current attempt; 523, 524, and 525 are infrastructure-level failures and are retry-eligible. See the Retry Logic guide for retry intervals.A timeout on the AVS call is reported as 510, regardless of what the AVS service returns in the response body.

CVV Hard Declines

Code	Description
`512`	CVV timeout
`515`	CVV unknown error
`765`	CVV declined

ANI Hard Declines

Code	Description
`788`	Declined — account name partial match
`789`	Declined — account name no match
`791`	Declined — match not supported
`792`	Declined — match not performed

Card Data & Token Errors

Code	Description
`800`	Card swipe required — track data required for this card type
`801`	Invalid track1 data — retry card swipe
`802`	Invalid track2 data — retry card swipe
`803`	Invalid card expiration date
`804`	Invalid token
`805`	Token not found — the supplied token does not exist
`806`	PAN data unavailable — the token is valid but no account (PAN) data could be retrieved; re-tokenize the account
`815`	Invalid BillPay token — invalid token used with BP account type
`1041`	Bad check digit test
`1042`	Check digit rejected — account number failed validation

Bank Account Verification Declines (743, 767–779)

Hard declines from bank account verification services (Routing Number Validation, Account Number Validation, Name on Account Validation). These are terminal for the current attempt.RNV — Routing Number Validation

Code	Description
`743`	Invalid routing number — not available or incorrect

ANV — Account Number Validation

Code	Description
`767`	Declined — no data or non-participating issuer
`768`	Declined — invalid routing number
`769`	Declined — invalid account number

NAV — Name on Account Validation

Code	Description
`776`	Declined — no data from issuer
`777`	Declined — address did not match
`778`	Declined — customer name or name and address did not match
`779`	Declined — customer or business name did not match

Card Issuer Declines (851–867)

The card issuer rejected the transaction. Do not retry automatically. Direct the recipient to contact their card issuer for more information. The specific decline reason may indicate a card status issue (lost, stolen, restricted) or an account limit that cannot be resolved without issuer action.

Code	Description
`851`	Issuer declined — do not honor
`852`	Issuer declined — invalid account number (no such number)
`853`	Issuer declined — invalid transaction
`854`	Issuer declined — transaction not permitted to cardholder
`855`	Network routing failure — issuer not found, not supported, or routing unknown
`856`	Issuer declined — stolen card; pick up requested
`857`	Issuer declined — pick up card requested
`858`	Issuer declined — exceeds account approval amount limit
`859`	Issuer declined — restricted card
`860`	Issuer declined — lost card; pick up requested
`861`	Routing network inoperative or malfunctioning
`862`	Issuer declined — insufficient funds
`863`	Issuer declined — exceeds account frequency limit
`864`	Issuer declined — no checking or credit account
`865`	Issuer declined — invalid transaction amount
`866`	Account blocked by cardholder
`867`	Account blocked by Ingo

OFAC (130, 511, 514, 752)

Workflow Events

Code	Description
`130`	OFAC Suspended — initial hit detected; transaction processing suspended pending review by Ingo Risk Services

System Errors

Code	Description
`511`	OFAC timeout
`514`	OFAC unknown error

Hard Decline

Code	Description
`752`	OFAC declined — potential match confirmed; do not honor

Code 130 is a success-class code — the transaction was accepted but is held pending OFAC review. It is distinct from 752, which is a terminal decline. Codes 1106 (suspended), 1107 (cleared), and 1108 (failure) are the corresponding Notify webhook event codes and are documented in the Notify — Verification & Payment Events section above.

Check Operations (540–541, 744–749)

Code	Description
`540`	Check Stop service error — request unsupported by endpoint
`541`	Check Stop unknown error — endpoint timeout or error
`744`	Check Cancel failure — check already canceled or in a non-cancelable state
`745`	Check Stop failure — check already stopped or in a non-stoppable state
`746`	Check Stop failure — check already posted today
`747`	Check Stop failure — teller check hold on account
`748`	Check Stop failure — error locating DDA
`749`	Check Stop failure — temporarily unable to place stop; retry

Notify — Transaction Status (780–787)

These codes are returned by the Notify API when a staged disbursement is in an incompatible state for the requested action. Check the transaction’s current state before retrying.

Code	Description
`780`	Transaction has already been claimed by the recipient
`781`	Transaction is not in a claimable state
`782`	Transaction has already been terminated
`783`	Staged transaction amount and process amount do not match
`784`	Unauthorized to use staged transactions
`786`	Transaction in progress — awaiting network response
`787`	Transaction has already been canceled

Notify — Authentication Events (1100–1102, 1131, 1151–1164)

Shared across Notify — Classic and Notify — Managed Parties.Party Authentication

Code	Message	Description
`1100`	Authentication Success	Recipient or party successfully authenticated to the Digital Payment Center
`1101`	Authentication Soft Failure	Authentication succeeded with a soft failure condition
`1102`	Authentication Failure	Recipient or party failed authentication to the Digital Payment Center
`1131`	SSO Authentication Success	Recipient successfully authenticated via Single Sign-On

OTAC (One-Time Authentication Code)

Code	Message	Description
`1151`	OTAC Send Limit Reached	Maximum number of OTACs for this transaction, party, and role has been reached — no further OTACs can be generated
`1152`	OTAC Authentication Failure	Provided OTAC did not match the outstanding code for this transaction, party, and role
`1153`	OTAC Generated — SMS	A new OTAC was generated and sent via SMS
`1154`	OTAC Generated — Email	A new OTAC was generated and sent via email
`1155`	OTAC Authentication Success	Provided OTAC matched the outstanding code

Overall Authentication Outcome

Code	Message	Description
`1160`	Overall Authentication Success	User completed authentication and was granted access
`1161`	Overall Authentication Failure	Maximum failed attempts for dynamic party authentication reached — access not granted
`1162`	Overall Authentication Failure	OTAC send limit reached — access not granted
`1163`	Overall Authentication Failure	OTAC inaccessible — access not granted
`1164`	Overall Authentication Failure	Maximum failed OTAC attempts reached — access not granted

Notify — Verification & Payment Events (1103–1139, 1148–1150, 1170)

Shared across Notify — Classic and Notify — Managed Parties.Recipient Verification — RVDM

Code	Message	Description
`1103`	RVDM Success	Recipient Verification Data Matching completed successfully
`1104`	RVDM Soft Failure	RVDM succeeded with a soft failure condition
`1105`	RVDM Failure	Recipient Verification Data Matching failed

Recipient Verification — OFAC

Code	Message	Description
`1106`	OFAC Suspended	Initial OFAC hit detected; transaction processing suspended pending review
`1107`	OFAC Cleared	OFAC hit cleared as false positive; processing resumes
`1108`	OFAC Failure	OFAC hit confirmed; transaction processing terminated

Account Verification — PayPal

Code	Message	Description
`1148`	Account Verification Success	PayPal account verification completed successfully
`1149`	Account Verification Soft Failure	PayPal account verification succeeded with a soft failure condition
`1150`	Account Verification Failure	PayPal account verification failed

Payment Events

Code	Message	Description
`1109`	Disbursement Expired	Disbursement reached the configured expiration period without being claimed — payment terminated
`1110`	Disbursement Canceled	Disbursement canceled by the client
`1111`	Check Disbursement — Address Verified	Recipient confirmed the address provided by the client
`1112`	Check Disbursement — Address Not Verified	Recipient did not confirm the address provided by the client
`1113`	Payment Terminated	Recipient could not complete a payment transaction — request terminated
`1114`	Payment Returned	Previously processed payment was returned by the account issuer
`1125`	Payment Success — Card	Card payment to recipient completed
`1126`	Payment Success — ACH	ACH payment to recipient completed
`1132`	Payment Terminated	Transaction canceled by recipient
`1133`	Payment Success — Check	Check payment originated to recipient
`1134`	Payment Success — PayPal	PayPal payment to recipient completed
`1135`	Elected Termination	Recipient elected not to receive disbursement — cancellation requested
`1136`	Elected Termination	Recipient elected not to receive disbursement — direct vendor disbursement requested
`1137`	Elected Termination	Recipient elected not to receive disbursement — alternate recipient requested
`1138`	Elected Termination	Recipient elected not to receive disbursement — reason unspecified
`1139`	Elected Termination	Recipient elected not to receive disbursement — reason indicated by reported reason code
`1170`	Payment Success — Real-Time Payment	RTP payment to recipient completed

Notify — Managed Parties (1120, 1123–1124, 1171–1172)

Codes specific to multi-party disbursement flows. These do not appear in Notify — Classic.

Code	Message	Description
`1120`	Unknown Party	Specified party could not be identified for this transaction
`1123`	Approval — Approved	Approver acted and approved the disbursement
`1124`	Approval — Declined	Approver acted and declined the disbursement
`1171`	Approvals Complete	All designated approvers have acted; disbursement released for processing
`1172`	Approvals — Payment Suspended	Transaction could not complete due to pending approvals; system will attempt to complete upon receipt of pending approvals

Notify — Notification Events (1200–1246)

These codes confirm the email or SMS notification that was sent to a recipient, joint recipient, or approver at each stage of the disbursement lifecycle. They appear in webhook event payloads. Codes marked Managed Parties do not appear in Notify — Classic.

Code	Notification	Delivery
`1200`	Payment notification	Email
`1201`	Payment notification	SMS
`1202`	Payment notification reminder	Email
`1203`	Payment notification reminder	SMS
`1204`	Notification timeout	Email
`1206`	Authentication failure	Email
`1208`	RVDM terminal failure	Email
`1210`	Account not supported — terminal failure	Email
`1212`	OFAC clearing failure	Email
`1214`	Account verification terminal failure	Email
`1216`	Payment processing terminal failure	Email
`1217`	Payment processing terminal failure	SMS — Managed Parties
`1218`	Transaction receipt — digital transfers	Email
`1219`	Transaction receipt — digital transfers	SMS — Managed Parties
`1222`	Payment return	Email
`1224`	Transaction receipt — check by mail	Email
`1226`	Transaction terminated	Email
`1228`	Transaction cancelled	Email
`1232`	Transaction cancelled — beneficiary	Email
`1234`	Transaction cancelled — beneficiary invalid address	Email
`1236`	Check cancelled — client-internal request	Email
`1238`	Check payment stop	Email
`1240`	Approval pending notice	Email — Managed Parties
`1241`	Approver no consent notice	Email — Managed Parties
`1243`	Payment notice	Email — Managed Parties
`1244`	Consent approval alert	Email — Managed Parties
`1245`	Consent approval alert reminder	Email — Managed Parties
`1246`	Consent approval confirmation	Email — Managed Parties

Code 1242 (Delegated Payment Confirmation) is reserved for role delegation, which is not yet available. It will be documented here when role delegation ships.

Banking Platform (552, 617, 620–621, 793, 820, 1300–1303)

These codes are specific to the Ingo Banking Platform API.

Code	Description
`552`	Multiple Banking Platform requests running simultaneously
`617`	Duplicate Banking Platform idempotent key
`620`	Duplicate Banking Platform request
`621`	Banking Platform validation error
`793`	Banking Platform transaction limit exceeded
`820`	Banking Platform route failure
`1300`	Banking entity not found
`1301`	Banking ledger not found
`1302`	Banking transaction not found
`1303`	Banking hold not found

ACH Reinitiation (1310–1320)

These codes are returned when an ACH debit transaction is submitted for reinitiation and fails an eligibility check. Each eligibility rule has its own code so you can act on the specific reason rather than a generic rejection. Every response is returned with HTTP 200 — the outcome is in response.status.

Code	Description
`1310`	The transaction was not found
`1311`	Reinitiation allowed only for ACH debit transactions
`1312`	Reinitiation allowed only against original transactions, not reinitiation transactions
`1313`	Cannot reinitiate against an unreturned transaction
`1314`	Cannot reinitiate — reinitiation must occur within 180 days of the original transaction
`1315`	Transaction not eligible for reinitiation, based on ACH return reason code
`1316`	Cannot reinitiate — there is already an outstanding, unreturned reinitiation
`1317`	Transaction no longer eligible for reinitiation, based on the ACH return reason code associated with a subsequent reinitiation attempt
`1318`	Cannot reinitiate — NSF and/or uncollected funds limit reached for reinitiation
`1319`	Nothing to reinitiate — the most recent reinitiation was collected successfully
`1320`	Cannot reinitiate — the account associated with the original transaction is no longer available

1310 is also returned when the referenced transaction belongs to a different participant. This is intentional — a distinct “not found for this participant” code would confirm that another client’s transaction ID exists.

Explore

Guides

Documentation

Trust & Compliance

Code families at a glance

Status & Event Code Reference

​Code families at a glance

​Status & Event Code Reference

Code families at a glance

Status & Event Code Reference