/api/v0 request fails, the API returns an HTTP error status and the full
response envelope. The stable, machine-readable code
is in errors[0].code.
The HTTP status always matches the error code in
errors[0].code.
Code format
Codes followERR<MODULE>_<4-digit number> — ERRWLT_1000. This matches the
platform’s core codes, ERRCORE_####.
Stability guarantee
Error codes are permanent. An existing code is never changed, reused for a different meaning, removed, or renumbered. A new error always gets the next unused number in its module. Only the human-readable message may be reworded.Fallback rules
Field validation errors
Some requests can fail validation on several fields at once — creating a wallet, generating a quote, adding a recipient. Those return abad_request with a list of field errors, not a single module code.
Retries
On the Partner API surface, most error codes are not retryable — fix the request before sending it again. These are the exceptions:ERRCORE_1006, the per-key rate limit, also clears on its own — retry after the window.
Webhooks is the exception. Several of its codes are transient: a DNS failure
on a target (
ERRWHK_1308), a lost re-arm race (ERRWHK_1104), the rate limits,
and the 502/503 edge codes. See
Retrying safely.Wallet errors
A bad wallet reference is not a wallet error. A malformed
wlt_… id is
400 ERRREF_1000, and a well-formed one that matches no wallet is
404 ERRREF_1001. The ERRWLT_ codes apply once the reference has resolved.ERRWLT_1000
404 · Wallet not found · constant WALLET_NOT_FOUND
The reference resolved to a wallet, but this API cannot act on it.
Returned when
- The wallet has been deleted. A second delete of the same wallet lands here too.
- The wallet belongs to a different customer. For security, access to another customer’s wallet is always reported as not found.
- A custodial wallet is not operable by this API — for example, it has not been created on the network yet and has no provider wallet id. External wallets never have one and are not affected.
GET /{userId}/{walletId}GET /{userId}/{walletId}/balancePATCH /{userId}/{walletId}DELETE /{userId}/{walletId}
ERRWLT_1001
400 · Wallet id is required · constant WALLET_ID_REQUIRED
The walletId was blank or missing at the layer that raises this code.
ERRWLT_1002
400 · User id is required · constant USER_ID_REQUIRED
The userId was blank or missing at the layer that raises this code.
ERRWLT_1003
400 · Unsupported network · constant UNSUPPORTED_NETWORK
The network is not one this endpoint will act on. The message lists the supported
networks.
Returned when
- Create wallet is asked for a network it will not create on — reported on
field: "network". (Before a recent server change this was a genericERRCORE_1001with a null field.) - Create wallet with
type: EXTERNALis given a missingnetwork, or one outside the EVM and TRON networks custodial wallets may be created on in this environment. For external wallets the name is matched case-insensitively. - Get wallet balance is called for a wallet whose network isn’t supported and
isn’t the aggregate value
all.
POST /{userId}GET /{userId}/{walletId}/balance
A missing
network on a custodial Create wallet is not this code — it is
ERRCORE_1001, the field-validation error. The two are easy to conflate: absent
is ERRCORE_1001, present but unusable is ERRWLT_1003. On an external
create, a missing network is ERRWLT_1003.ERRWLT_1004
400 · Transfer body is required
A transfer was requested with no body.
ERRWLT_1005
403 · KYC not completed · constant KYC_NOT_COMPLETED
The customer must complete KYC before a wallet can be created — custodial or external.
Returned when
- The customer’s KYC status is not
COMPLETED. - The customer has no KYC record.
POST /{userId}
ERRWLT_1006
500 · Wallet created at the provider but not recorded
Create wallet made the wallet at the provider, but it could not be recorded on Endl’s
side.
Returned when
- The provider created the wallet and the local record was not written.
POST /{userId}
ERRWLT_1007
400 · Invalid wallet type · constant INVALID_WALLET_TYPE
type must be CUSTODIAL or EXTERNAL.
Returned when
- Create wallet is sent a
typethat is neitherCUSTODIALnorEXTERNAL(case-insensitive). The response carriesfield: "type".
POST /{userId}
ERRWLT_1008
400 · Invalid wallet address · constant INVALID_WALLET_ADDRESS
The address is missing or is not a valid address for the requested network.
Returned when
- Create wallet with
type: EXTERNALhas noaddress, or one that does not match the network’s format:^0x[a-fA-F0-9]{40}$on EVM networks,^T[A-Za-z1-9]{33}$on TRON networks. The response carriesfield: "address".
POST /{userId}
ERRWLT_1009
409 · Wallet address already registered · constant WALLET_ADDRESS_ALREADY_EXISTS
This customer already has an active wallet with this address on this network.
Returned when
- Create wallet with
type: EXTERNALnames anaddressthe same customer already has as a non-deleted wallet on the samenetwork. EVM addresses are compared case-insensitively, TRON addresses exactly. The response carriesfield: "address".
POST /{userId}
The check is per customer and per network. The same address on a different
network, or registered by a different customer, is allowed. Use the existing
wallet’s
walletId from List wallets instead of registering again.ERRWLT_1010
400 · Unsupported currency for network · constant UNSUPPORTED_CURRENCY_FOR_NETWORK
The requested currency is not supported on this network.
Returned when
- Create wallet with
type: EXTERNALsends acurrencyother thanUSDCorUSDT, or one the network does not carry: TRON networks carryUSDTonly; Polygon, Base, Arbitrum and Optimism carryUSDConly; Ethereum carries both. The response carriesfield: "currency".
POST /{userId}
ERRWLT_1011
400 · Operation not supported for external wallets · constant EXTERNAL_WALLET_OPERATION_NOT_SUPPORTED
External wallets are only usable as account settlement destinations; this
operation needs a custodial wallet.
Returned when
- Get wallet balance is called for an external wallet — Endl holds no key for it and tracks no balance.
- An external wallet is named as
walletIdto fund a transaction: theCRYPTOdeposit rail on the pre-transaction call, orwalletIdon a wallet-funded submit. The response carriesfield: "walletId". - An external wallet is named for card enrolment, a card deposit from the Endl
wallet, or a card withdrawal. The response carries
field: "walletId".
GET /{userId}/{walletId}/balance- Transactions (pre-transaction and submit), standard and POBO
- Cards (enrolment, deposits and withdrawals)
ERRWLT_1012
409 · Wallet is linked to active accounts · constant WALLET_HAS_ACTIVE_ACCOUNTS
The wallet is the settlement destination of one or more live accounts. Move them
to another wallet, or close or deactivate them, before deleting the wallet.
Returned when
- Delete wallet is called while any live account settles to the wallet.
“Live” means any account status other than
CLOSEDor deactivated — an account still being created counts. Applies to custodial and external wallets alike. The response carriesfield: "walletId".
DELETE /{userId}/{walletId}
ERRWLT_1013
403 · Test token minting is not available · constant MINT_TEST_NOT_AVAILABLE
Test tokens can only be minted in the sandbox environment.
Returned when
- Mint test tokens is called in production. It is checked before the body or the wallet.
POST /{userId}/{walletId}/mint-test
ERRWLT_1014
400 · Invalid mint test request · constant INVALID_MINT_TEST_REQUEST
token/tokens must be USDC or USDT and amount must be a positive number within the sandbox limit.
Returned when
tokenor an entry intokensis notUSDCorUSDT, ortokensis empty or not an array.- Both
tokenandtokensare sent. amountis zero, negative, not a number, or above10(the per-token sandbox cap).- The body is not a JSON object.
amount must not exceed 10 per token in sandbox. The response carries field: null.
Endpoints
POST /{userId}/{walletId}/mint-test
A malformed or unknown
wlt_… id returns a reference error (ERRREF_1000 or ERRREF_1001).Reference errors
v0 endpoints identify records by reference ids such ascus_…, wlt_…, acct_…, rec_…, qut_…, txn_… and snd_…. These codes are returned when a reference id can’t be resolved, so they can appear on any module’s endpoints.
ERRREF_1000
400 · Invalid reference id · constant INVALID_REFERENCE
The reference id is missing, blank, malformed, or the wrong type.
Returned when
- It’s missing or blank. For example,
GET /api/v0/railswith nouserId(userId is required). - It’s malformed and doesn’t match the
<prefix>_<id>format, for example'abc' is not a valid wallet id. - It’s the wrong type. For example, a
cus_…id sent where awlt_…id is expected.
ERRREF_1000: accountId, walletId, recipientId, senderId, quoteId, transaction ids, depositId and invoice file ids. A well-formed one that doesn’t exist is 404 ERRREF_1001.
Customer ids (cus_…) never return ERRREF_1000, with one exception: GET /api/v0/rails without userId. Any customer id that isn’t blank but doesn’t resolve — malformed, unknown, deleted or another partner’s — is 404 ERRREF_1001, field userId.
A blank userId is checked separately, and the result depends on the endpoint:
A completely empty path segment, such as
/api/v0/accounts//acct_x, never reaches the endpoint: it is 400 ERRCORE_1001, The request path is not a valid URL.
Endpoints
Any path, query or body field that takes a reference id
ERRREF_1001
404 · Reference not found · constant REFERENCE_NOT_FOUND
The reference id is correctly formatted but doesn’t match any record.
Returned when
- The id never existed, has been deleted, or belongs to a different environment. The message names the entity, for example
Recipient 'rec_x' not found. - A
cus_…customer id is malformed, unknown, deleted or belongs to another partner — for exampleUser with ID 'abc' not found, fielduserId. Another partner’s customer is reported exactly like a customer that does not exist —User with ID '{id}' not found— on every endpoint that takes a customer id, so one partner cannot discover another’s customers.
Any v0 endpoint that takes a reference id
Reference errors vs module errors: if a reference id doesn’t resolve at all, the API returns
ERRREF_1001. If it resolves but the caller can’t access the record (for example, a quote owned by a different user), the API returns that module’s own code, such as ERRQUO_1000 or ERRREC_1000.Quote errors
Raised byPOST /api/v0/quotes/{userId}/generate and GET /api/v0/quotes/{userId}/{quoteId}, and by the POBO equivalents.
Every quote rejection carries one of these codes in errors[0].code, with the specific reason in errors[0].message. The top-level message stays "GetQuote failed!" on all of them — it is not the reason, and branching on it tells you nothing. Read errors[0].
Checks run in a fixed order, and the first failure is the one you are told about. A request that breaks two rules reports the earlier one, so fixing one problem can reveal the next. The order is: currency pair → chains → rails → country → amounts → pricing.
ERRQUO_1000
404 · Quote not found · constant QUOTE_NOT_FOUND
The quote doesn’t exist or doesn’t belong to this user.
Returned when
- The
qut_…id resolves but no matching quote exists. - The quote belongs to a different customer. For security, access to another customer’s quote is always reported as not found.
- A POBO pre-transaction or submit request refers to a quote that can’t be found.
GET /quotes/{userId}/{quoteId}POST /pobo/transactions/pre-txnPOST /pobo/transactions/submit
A malformed or unknown
qut_… id returns a reference error (ERRREF_1000 or ERRREF_1001) rather than this code.ERRQUO_1001
400 · Required quote field missing · constant QUOTE_FIELD_REQUIRED
A field the quote cannot be priced without was not supplied.
ERRQUO_1002
400 · Quote amount invalid · constant QUOTE_AMOUNT_INVALID
Supply a positive amount on exactly one of source or destination.
Returned when
- Neither leg carried an amount — “Source or Destination amount is required”.
- An amount was supplied but is zero or negative — “Source amount must be greater than 0”, or the destination equivalent.
ERRQUO_1003
400 · Amount below the minimum · constant QUOTE_AMOUNT_BELOW_MINIMUM
The amount is below the minimum this account type and rail allow.
Returned when
- Below the 100 USD floor for either account type — “Min allowed Source amount is 100”.
- Below the 15,200 USD floor that SWIFT adds on either leg — “Min allowed Source amount is 15200”. Checked before the account-type floor.
- A reverse quote whose derived source amount lands under the floor. A business is allowed down to 50 USD there; an individual is not.
ERRQUO_1004
400 · Amount above the maximum · constant QUOTE_AMOUNT_ABOVE_MAXIMUM
The amount exceeds the ceiling this account type allows — 100,000 USD for INDIVIDUAL, 500,000 USD for BUSINESS.
Unlike the floor, this ceiling still applies to stablecoin → stablecoin.
ERRQUO_1005
400 · Amount not supported · constant QUOTE_AMOUNT_NOT_SUPPORTED
The amount is larger than a quote can carry: a source amount above 999,999.9999, or a destination amount above 99,999,999.99.
This is a structural limit, not a commercial one — nothing is exempt from it. Because the account-type ceiling is checked first, you only reach this code on a route that skips that check.
ERRQUO_1006
400 · Rail limit exceeded · constant QUOTE_RAIL_LIMIT_EXCEEDED
The amount exceeds the published maximum for this payout rail and currency.
Where several providers serve the same rail, the widest cap applies, so only an amount no provider could serve is rejected here.
ERRQUO_1007
400 · Currency not supported · constant QUOTE_CURRENCY_NOT_SUPPORTED
The currency is not available for this leg of the transfer — unknown to us, or configured but not active for that direction.
A currency can be payable but not fundable, so this is judged per leg: the source leg is checked for a forward quote, the destination leg for a reverse one.
ERRQUO_1008
400 · Currency not supported in this country · constant QUOTE_CURRENCY_NOT_SUPPORTED_IN_COUNTRY
The currency is not enabled for the country this customer is registered in — “Source currency X is not supported in your country”, or the destination equivalent.
Skipped entirely when the customer has no country on file.
ERRQUO_1009
400 · Currency pair not supported · constant QUOTE_CURRENCY_PAIR_NOT_SUPPORTED
Both currencies are supported, but not as this pair, or not by the provider that serves it.
Returned when
USDT→EUR. UseUSDCas the source for EUR payouts.USDT→GBP. UseUSDCas the source.- The destination currency is not one the routed provider serves.
ERRQUO_1010
400 · Chain required · constant QUOTE_CHAIN_REQUIRED
A stablecoin leg must name the network it settles on — “source.chain is required for USDC/T deposits”.
Applies to the stablecoin source on a stablecoin → fiat quote. On stablecoin → stablecoin the chain is optional per leg, and a chain you do send is validated.
ERRQUO_1011
400 · Chain not supported · constant QUOTE_CHAIN_NOT_SUPPORTED
The network is not one we settle on, or does not carry this currency.
Returned when
- The chain is not a network we run on — “valid source.chain is required for USDC/T deposits”. Known chains are
ethereum,tron,polygon,solana,base,arbitrum,optimism,xrp. - The currency is not issued on that network — “USDT is not supported on the base network (source.chain)”.
USDTexists only onethereumandtron;troncarries onlyUSDT. - A SWIFT quote funded from a chain other than Ethereum or TRON.
Testnet names (
basesepolia, tronnile, …) are accepted in sandbox and QA only, each judged as the mainnet it mirrors. Production rejects them with this code.ERRQUO_1012
400 · Payout rail not supported · constant QUOTE_PAYOUT_RAIL_NOT_SUPPORTED
This payout rail does not serve the destination currency.
Returned when
- The rail is not published for that currency — “
<RAIL>payoutRail does not apply for destinationCurrency = X, or is not enabled”. SWIFTis aimed at a stablecoin destination. SWIFT settles to banks only — use theCRYPTOpayout rail.
ERRQUO_1013
400 · Deposit rail not supported · constant QUOTE_DEPOSIT_RAIL_NOT_SUPPORTED
This deposit rail does not serve the source currency — “<RAIL> depositRail is not supported for source currency X, or is not enabled”.
Three combinations are always allowed regardless: ENDL_ACCOUNT and TOPUP_FIAT for USD and EUR, and IMPS / UPI for INR.
ERRQUO_1014
400 · Rail not permitted for this account · constant QUOTE_RAIL_NOT_PERMITTED
The rail exists and serves the currency, but this account may not use it.
Returned when
- SWIFT on an individual account — “SWIFT payout rail is only available for Business accounts”. Both the customer record and the
accountTypeyou send must sayBUSINESS. - SWIFT on a business account that does not have SWIFT enabled — “SWIFT rail is not supported / enabled for user”. Being a business is necessary, not sufficient.
ERRQUO_1015
400 · Account type invalid · constant QUOTE_USER_TYPE_INVALID
The customer’s account type cannot be priced, because fee slabs are selected from it. Raised against the stored customer record, not the accountType in your request — contact support if you see it.
ERRQUO_1016
400 · Supported rails unavailable · constant QUOTE_RAILS_UNAVAILABLE
The rails available for this customer’s country could not be determined, so no rail can be validated. This is the one quote code marked retryable.
ERRQUO_1017
400 · Route cannot be priced · constant QUOTE_PRICING_UNAVAILABLE
No fee or rate configuration covers this route and amount. The corridor and the rails are all valid — there is simply nothing to price with.
Not something a different request body fixes, unless the amount falls outside every configured band. Report it.
ERRQUO_1018
500 · Quote provider error · constant QUOTE_PROVIDER_ERROR
The provider pricing this route could not complete the request.
Retryable. No quote is created when this fires, so a retry is safe. The message is deliberately generic — the cause is in our logs, not your response. Quote the X-Request-ID when reporting one.
ERRQUO_1019
400 · Quote parameter invalid · constant QUOTE_PARAMETER_INVALID
A value on the quote request failed validation.
ERRQUO_1020
400 · Quote generation failed · constant QUOTE_GENERATION_FAILED
The catch-all, so that no quote failure is ever codeless. If you receive it, the rejection has a reason we have not yet given its own code — send us the X-Request-ID and errors[0].message.
Recipient errors
ERRREC_1000
404 · Recipient not found · constant RECIPIENT_NOT_FOUND
The recipient doesn’t exist, was deleted, or doesn’t belong to this user.
Returned when
- This user has no active (non-deleted) recipient with this id.
- The recipient belongs to a different user. For security, access to another user’s recipient is always reported as not found.
GET /recipients/{userId}/{recipientId}DELETE /recipients/{userId}/{recipientId}
A malformed or unknown
rec_… id returns a reference error. A recipient field that fails validation on add is ERRREC_1001.ERRREC_1001
400 · Validation failed
A recipient field fails validation.
Returned when
- A field on an add-recipient request fails validation. Each failing field is its own
errors[]entry:messagegives the reason — for exampleFirst name is required— andfieldnames the field, for examplefirstName.
POST /api/v0/recipients/{userId}POST /api/v0/pobo/recipients
Account errors
Raised by the endpoints under/api/v0/accounts. Every one of them is
documented end to end, with worked bodies, on
Accounts errors.
ERRACC_1000
400 · User id is required
The {userId} path segment is blank or whitespace.
Field
userId
openlistgetbalanceactivityavailable-for-openingupdateactivatedeactivate
ERRACC_1001
404 · Account not found
The account reference resolved, but no such account belongs to this customer.
Field
accountId
- Balance
- Update account — also for a crypto account, which this API does not expose
- Activate
- Deactivate
ERRACC_1002
409 · Account is deactivated. Reactivate it before using it
Get Account or Update account was called on a deactivated account. Use List to see it, or Activate to bring it back.
Field
accountId
- Get account
- Update account
ERRACC_1003
409 · This operation is not available for this account
The account sits with a provider that has no integration for what you asked, or
is a kind of account the operation does not apply to. The message names the
specific reason:
AED accounts cannot be activated or deactivated — both calls return this code
rather than silently doing nothing.
Field
- Not field-specific —
fieldisnull— except on Update account, where it isaccountId.
- Get balance
- Update account
- Activate
- Deactivate
ERRACC_1004
502 · The status change could not be accepted. Please try again in a moment
Reserved — not currently raised on /api/v0. A status change the provider cannot
accept comes back as ERRACC_1012 when the provider is unavailable,
or ERRACC_1017 when it answers and refuses.
ERRACC_1005
400 · Unsupported status ’…’. Expected one of: ACTIVE, PENDING, DEACTIVATED, CLOSED, FROZEN, UNDER_REVIEW, DORMANT
An unknown value was passed in ?status=.
Field
status
- List accounts
ERRACC_1006
409 · An account already exists for this currency
The customer already has an active or pending account in that currency.
Field
- Not field-specific —
fieldisnull.
- Open account
ERRACC_1008
400 · The selected network is not supported for this account’s currency
The wallet’s network does not fit the account. The message names the specific
reason:
Field
walletIdorchainCode, whichever is at fault.
- Open account
- Update account
ERRACC_1009
400 · Unsupported account category. Expected one of: FIAT, CRYPTO, ONRAMP
accountCategory is not FIAT or ONRAMP.
Field
accountCategory
- Open account
ERRACC_1011
502 · The balance could not be retrieved. Please try again in a moment
The provider answered but returned no balance.
Field
- Not field-specific —
fieldisnull.
- Get balance
ERRACC_1012
503 · The account provider is temporarily unavailable. Please try again later
The provider threw or timed out.
Field
- Not field-specific —
fieldisnull.
- Get balance
- Update account — the provider is down or timed out, and the wallet change did not apply
- Activate
- Deactivate
ERRACC_1013
400 · Account category is required. Expected one of: FIAT, ONRAMP
accountCategory is missing or blank. An unrecognised value is
ERRACC_1009 instead.
Field
accountCategory
- Open account
ERRACC_1014
400 · walletId is required
walletId is missing or blank — on Open account, for an ONRAMP account (message
A wallet id is required for this account category); on Update account, always.
Field
walletId
- Open account
- Update account
ERRACC_1015
400 · Wallet not found or does not belong to this customer
The wallet does not exist, belongs to another customer, or has been deleted.
Field
walletId
- Open account
- Update account
ERRACC_1016
400 · That currency is not available for account opening
The currency cannot be opened on demand through this endpoint. Use
List accounts available for opening
to see what can be opened.
Field
currency
- Open account
ERRACC_1017
400 · The account provider refused this status change
The provider answered and refused the activation or deactivation. Distinct from
ERRACC_1012, where the provider could not be reached.
Field
- Not field-specific —
fieldisnull.
- Activate
- Deactivate
ERRACC_1018
409 · Account limit reached for this currency
Customers can hold up to 10 accounts per currency, counting active and pending
accounts combined. Requests beyond this limit are refused.
Field
currency
- Open account
ERRACC_1019
409 · Account is closed and can no longer be used
The account exists but has been closed. Unlike a deactivated account, a closed one
cannot be reactivated.
Field
accountId
- Update account
ERRACC_1020
409 · Account with this name and walletId already exists
The customer already holds a live account with this account’s name on the target
wallet.
Field
walletId
- Open account
- Update account
ERRACC_1021
400 · The account provider refused this update
The provider answered and refused the wallet change. The message carries the
provider’s user-facing reason when it gives one. Distinct from
ERRACC_1012, where the provider could not be reached.
Field
walletId
- Update account
ERRACC_1004, ERRACC_1007 and ERRACC_1010 are reserved and are not raised on
the partner surface. A malformed or unknown acct_… id returns a reference error
(ERRREF_1000 / ERRREF_1001), not an account error, and request-body validation
on Open account comes back as field-level ERRCORE_1001 entries.Transaction errors
ERRTXN_* codes are returned by the /api/v0 transaction endpoints. ERRTXN_1000 and ERRTXN_1001 apply to POBO transactions only; ERRTXN_1002 and ERRTXN_1003 apply to both standard and POBO transactions.
ERRTXN_1000
400 · Sender id is required · constant SENDER_ID_REQUIRED
A POBO pre-transaction or submit request is sent without a senderId.
Returned when
- A pre-transaction or submit request doesn’t include a
senderId(snd_…). Every POBO transaction needs one.
POST /pobo/transactions/pre-txnPOST /pobo/transactions/submit
ERRTXN_1001
400 · Payout rail not supported · constant RAIL_NOT_SUPPORTED
The currency or payout rail doesn’t support POBO.
Returned when
- A POBO quote or transaction would go through a payout rail that doesn’t support POBO, such as ACH, FEDWIRE, SEPA or SWIFT.
POBO quote generationPOST /pobo/transactions/pre-txnPOST /pobo/transactions/submit
ERRTXN_1002
400 · Wallet id is required
A wallet-funded transaction is sent without a walletId. Reported on field: "walletId".
Returned when
- Create pre-transaction: no
walletId, and the quote’sdepositRailisCRYPTO. - Submit transaction: no
walletId, andendlTransactionModeisSTABLE_COIN_TO_FIAT,STABLE_COIN_TO_STABLE_COINorTOP_UP.
POST /api/v0/transactions/{userId}/pre-txnPOST /api/v0/transactions/{userId}/submitPOST /api/v0/pobo/transactions/pre-txnPOST /api/v0/pobo/transactions/submit
ERRTXN_1003
400 · Wallet not found
The walletId names a wallet this customer cannot use.
Returned when
- The
walletIdresolves to a wallet that is deleted or belongs to another customer. - POBO Submit transaction only: the wallet behind the quote’s deposit is no longer active.
POST /api/v0/transactions/{userId}/pre-txnPOST /api/v0/transactions/{userId}/submitPOST /api/v0/pobo/transactions/pre-txnPOST /api/v0/pobo/transactions/submit
A malformed
walletId returns ERRREF_1000; a well-formed one that matches no wallet returns ERRREF_1001 (404).Related codes: an unknown
txn_… id returns ERRREF_1001, a missing POBO quote returns ERRQUO_1000, and a missing partner context returns ERRCORE_1004. Validation errors for amounts, currencies and purpose codes are returned as field-level bad_request errors.Card errors
Returned by the Cards endpoints under/api/v0/cards and /api/v0/customer/…/card-users.
Each code, when it is returned and what to do is on
Card errors.
ERRCRD_1038, ERRCRD_1039 and ERRCRD_1040 are not HTTP errors: they appear in an
enrolment’s reason.code. See
Enrolment reason codes.
Shared core codes
ERRCORE_ codes are raised anywhere on the platform, not by one module.
Webhook errors
Returned by the Webhooks endpoints. Codes are banded by area, so the first two digits tell you where the failure came from.The tables below list the partner-visible codes. The ingest, registry and
gateway bands exist in the same numbering but are raised on internal surfaces —
a partner never sees them.
ERRWHK_1700, for instance, is converted to
502 ERRWHK_1900 before it leaves the gateway.