Error Reference

Ingo Payments APIs return a numeric status code on every request. Understanding the code structure helps you build reliable integrations that handle outcomes correctly — distinguishing between codes that require retry, codes that require corrected input, and codes that require no action.

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–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+`	Product-Specific Codes	Codes specific to Banking Platform, Notify — Managed Parties, or platform routing	See the relevant product’s documentation

The codes below are API response codes — returned synchronously in the response body. Webhook event codes are a separate namespace and are documented on each product’s webhooks page.

API Response 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–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)

OFAC

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

Auth & Request Errors (400–415, 516, 530, 609, 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
`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, 706–763, 900–901, 990, 999)

These codes indicate a timeout, routing failure, or unexpected system error. Retry with exponential backoff. 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
`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

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
`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 (511, 514, 752)

Code	Description
`511`	OFAC timeout
`514`	OFAC unknown error
`752`	OFAC declined — do not honor; potential OFAC match confirmed

Code 130 (OFAC Suspended) appears in the Soft Verification Results section — it is returned as a success-class code indicating the transaction is under review. Codes 1106 (suspended), 1107 (cleared), and 1108 (failure) are webhook event codes delivered asynchronously and are documented on the IngoPay Webhooks page.

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 — Managed Parties (1120)

Code	Description
`1120`	Unknown party — the specified party could not be identified for this transaction

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

Explore

Guides

Documentation

Trust & Compliance

Code families at a glance

API Response Code Reference

Explore

Guides

Documentation

Trust & Compliance

Documentation Index

​Code families at a glance

​API Response Code Reference

Code families at a glance

API Response Code Reference