Errors
Payment Errors
Error codes with the payments- prefix. See the
Errors overview for the response format and the code convention.
Payments
| Error Code | HTTP Status | Error Message | Description |
|---|---|---|---|
payments-0007 | 500 | Tesser stopped a balance update for this account because the stored balance is, or would become, inconsistent, and changed nothing. This is a fault at Tesser: contact Tesser support with the request_id; retrying won't help | Tesser never records an available balance above an account's total balance. A balance update that found such a stored balance, or would have written one, was stopped and nothing changed. Only Tesser can correct the balance. Contact Tesser support with the request_id. Retrying won't help. |
payments-0008 | 500 | Tesser hit an internal error while updating a balance and changed nothing. This is a fault at Tesser: contact Tesser support with the request_id; retrying won't help | A balance update inside Tesser received an invalid amount, so it was stopped and nothing changed. This is a fault at Tesser, not in the request. Contact Tesser support with the request_id. Retrying won't help. |
payments-1000 | 404 | Payment not found | The specified payment ID does not exist |
payments-1001 | 404 | Payment transfer step not found | The step does not exist or does not belong to this payment |
payments-1002 | 404 | Destination account not found | to_account did not resolve to an account in this workspace |
payments-2001 | 422 | Cross-ramp payments aren't enabled for this workspace. Tesser enables them per workspace: contact Tesser support to request access; retrying won't help until then | Cross-ramp payments are enabled per workspace, and this workspace doesn't have them yet. Nothing was created. Contact Tesser support to request access. Retrying won't help until Tesser enables them. Payments that already exist keep running if access is later turned off. |
payments-3000 | 400 | from_network must equal to_network | User provides different networks for from_network and to_network |
payments-3001 | 400 | desired.from.amount or desired.to.amount isn't a valid amount for its currency, so Tesser didn't create the payment. Send a positive decimal amount of at least the currency's smallest unit; retrying the same request won't help | Returned when a payment's amount isn't a positive decimal number, or is smaller than one smallest unit of its currency, so it rounds to zero (for example 0.0000004 USDC, which has 6 decimals). A payment Tesser quotes when it's created also gets this code for an amount with more decimals than its currency has. The field param names the amount when Tesser can tell which. Nothing was created. Fix the amount and send the request again; retrying the same request won't help. |
payments-3002 | 400 | Either from_amount or to_amount must be provided. Cannot create payment without an amount. | User does not provide either from_amount or to_amount |
payments-3004 | 400 | desired.from.network is required for this payment. Send the network the funds are sent from and resend | A payment from a stablecoin needs desired.from.network, the network its funds are sent from. Nothing was created. Add desired.from.network and resend. Retrying without it won't help. |
payments-3005 | 400 | desired.to.network is required for this payment. Send the network the destination receives on and resend | A payment to a stablecoin destination needs desired.to.network, the network the destination receives on. Nothing was created or changed. Add desired.to.network and resend. Retrying without it won't help. |
payments-3007 | 400 | desired.from.currency isn't a currency Tesser supports. Correct it and resend | desired.from.currency must be a stablecoin or fiat currency code that Tesser supports. Nothing was created. Correct desired.from.currency and resend. Retrying with the same value won't help. A payment that sends and delivers the same fiat currency gets payments-3078 instead. |
payments-3008 | 400 | desired.to.currency isn't a currency Tesser supports. Correct it and resend | desired.to.currency must be a stablecoin or fiat currency code that Tesser supports. Nothing was created. Correct desired.to.currency and resend. Retrying with the same value won't help. |
payments-3009 | 400 | funding_account_id not found | User provides a funding_account_id that does not exist |
payments-3010 | 400 | to_account_id not found | User provides a to_account_id that does not exist |
payments-3011 | 400 | from_account_id not found | User provides a from_account_id that does not exist |
payments-3012 | 400 | Missing input parameter is_approved | User submits a payment review without the required is_approved parameter |
payments-3015 | 400 | The exchange rate quote has expired. Create a new payment to get a fresh quote. | User attempts to execute a payment with an expired exchange rate quote. Quote lifetimes vary by provider, from about 10 seconds to 24 hours. |
payments-3017 | 422 | The destination wallet isn't an active Circle recipient on this network yet, so Tesser can't pay it out from a Circle ledger. Circle has to approve the wallet first: send the request again once it does, or contact Tesser support if it stays pending | A payout from a Circle ledger to an external wallet needs the wallet to be an active Circle recipient on desired.to.network. Tesser registers each external wallet with Circle when it's created, or when Circle is set up for the workspace, and Circle then approves it. The wallet isn't registered yet or Circle hasn't approved it. Send the request again once Circle approves the wallet; retrying before that won't help. If it stays pending, contact Tesser support with the account id from the message. A wallet registered with Circle on other networks but not this one gets payments-3121 instead. |
payments-3018 | 400 | from_account_id and to_account_id should not both be managed accounts for payments. Use /v1/treasury/rebalances instead. | Transfers between two managed accounts are treasury operations. Use /v1/treasury/rebalances instead. |
payments-3019 | 400 | desired.from.account_id doesn't hold desired.from.currency on desired.from.network, so it can't fund this payment. Send from an account that holds this currency on this network, or change the currency or network, and resend; contact Tesser support if the account should hold it | The source account isn't set up to hold the payment's currency on the payment's network. A wallet holds each currency per network; a ledger holds a currency on no particular network, so for a ledger only the currency has to match. Nothing was created or changed. Send from an account that holds the currency (on that network, for a wallet), or change desired.from.currency or desired.from.network, and resend. If you expected the account to hold it, contact Tesser support. Retrying the same request won't help. |
payments-3020 | 400 | desired.to.account_id can't receive desired.to.currency on desired.to.network: the account isn't set up to hold that currency on that network. Choose a destination that can receive it and resend; contact Tesser support if this account should | The destination account can't receive the payment's currency on the payment's network. Either it is a Tesser-managed wallet or ledger that isn't set up for that currency and network, or it isn't a wallet that can receive stablecoins at all, such as a bank account. External (unmanaged) wallets are set up automatically and never get this error. Nothing was created or changed. Choose a destination that can receive the currency on that network and resend. If you expected this account to receive it, contact Tesser support. Retrying the same request won't help. |
payments-3021 | 400 | Amounts not yet calculated. Payment may still be processing. | Payment amounts have not been calculated yet, the payment may still be processing |
payments-3022 | 500 | This payment has no currencies recorded at Tesser, so its accounts can't be attached. This is a fault at Tesser, not in your request: contact Tesser support with the payment id; retrying won't help | The payment is missing its currencies at Tesser, so accounts can't be attached to it and nothing was changed. This is a fault at Tesser, not in the request. Contact Tesser support with the payment id. Retrying won't help. |
payments-3029 | 400 | Details needed to lock this cross-ramp payment are missing: the beneficiary's bank account number, part of the beneficiary's address, or an owner for one of the accounts. Add them to the account or counterparty, then send the request again | Locking a cross-ramp payment sends the beneficiary's bank account number and full address to the provider, and every account in the payment has to belong to a counterparty or tenant. The error_message ends with the account and what is missing. Add the missing details to that account or its counterparty, then send the request again. |
payments-3031 | 400 | To account is not a fiat account | The to account is not the expected fiat_bank type for offramp payments |
payments-3041 | 400 | No provider Tesser works with can send this payment from desired.from.account_id to desired.to.account_id in this currency and network. Use a source and destination this payment supports and resend, or contact Tesser support if you expected this route to work; retrying won't help | No provider Tesser works with can execute this payment. A same-currency payment is sent from a managed wallet or a Circle Mint ledger to a destination that isn't a bank account, and some networks are served only from managed wallets. Nothing was created or changed. Check desired.from.account_id, desired.to.account_id and the network, then resend. When a provider recognises the payment but refuses it, the response carries that provider's error instead. If you expected this route to be supported, contact Tesser support. Retrying the same request won't help. |
payments-3052 | 400 | direction must be 'inbound' or 'outbound' | GET /v1/payments only filters transfers by direction; rebalance and other internal directions are rejected |
payments-3053 | 400 | Simulated inbound payments are not available in production | Inbound payment simulation is not available in production environments |
payments-3054 | 400 | This network isn't supported for simulated inbound payments on this endpoint. Send one of the testnets the endpoint lists and resend | Each simulate-inbound endpoint accepts only the testnets its reference lists. Nothing was simulated. Send one of those networks and resend. Retrying with the same network won't help. |
payments-3055 | 400 | to_account can't receive a simulated inbound payment: it must be a managed stablecoin_ethereum wallet with an on-chain address. Send such a wallet as to_account and resend | Simulated inbound payments can only go to a managed stablecoin_ethereum wallet in the workspace that has an on-chain address. Nothing was simulated. Send the id of such a wallet as to_account and resend. Retrying with the same account won't help. |
payments-3060 | 409 | This payment step isn't waiting for a signature: it doesn't take one, isn't ready yet, or was already signed or ended. Get the payment and sign the step only while its status is signature_requested; resending this signature won't help | Only a step whose status is signature_requested accepts a signature. This one doesn't take signatures, hasn't requested one yet, or was already signed (possibly by a concurrent request), failed or completed. Nothing was signed or sent by this request. Get the payment to read the step's current status; sign it when it shows signature_requested. Resending the same signature won't help. |
payments-3061 | 500 | This payment step is waiting for a signature, but Tesser has no complete transaction for it to sign. This is a fault at Tesser: contact Tesser support; retrying won't help | The step is waiting for a signature, but Tesser's prepared transaction for it is incomplete, so nothing can be signed or sent. This is a fault at Tesser. Contact Tesser support with the payment and step ids. Retrying won't help. |
payments-3062 | 500 | This payment step is missing its amount or currency at Tesser, so it can't be signed and nothing was sent. This is a fault at Tesser: contact Tesser support; retrying won't help | The step's amount or currency is missing at Tesser, so it can't be signed and nothing was sent. This is a fault at Tesser, not in the request. Contact Tesser support with the payment and step ids. Retrying won't help. |
payments-3063 | 409 | The source wallet doesn't have enough funds for this payment: its on-chain balance, or what's left after funds reserved for other transfers, is below the amount. Nothing was sent and the step still waits for a signature. Fund the wallet, then sign again before the payment expires | Tesser checks the source wallet's funds when the step is signed. Its on-chain balance, or its balance after funds reserved for other transfers from the same wallet, is below the payment amount. Nothing was sent and the step stays signature_requested. The payment's balance_status becomes awaiting_funds, unless it is already reserved or awaiting_funds (for example a payout from a pre-funded ledger), in which case balance_status and balance_reserved_at don't change. Fund the wallet, then sign again before the payment expires. Signing again without funding won't help. |
payments-3064 | 400 | Turnkey rejected the signing request, so nothing was signed or sent. Check that the stamp covers the exact request body and uses an API key registered for this wallet in Turnkey, then sign again | Turnkey refused the stamped sign_transaction request Tesser forwarded for this payment step. Usually the stamp doesn't match the request body byte for byte, the API key isn't registered for the wallet in Turnkey, or the wallet belongs to another Turnkey organization. The step still waits for a signature: fix the request and sign again. |
payments-3066 | 400 | Signed transaction does not match the payment details | The destination address or amount in the signed transaction does not match the prepared payment step |
payments-3067 | 400 | Signature is not a valid base64-encoded {body, stamp} envelope | The signature field must be base64-encoded JSON containing the Turnkey activity body and stamp header value |
payments-3068 | 500 | Tesser can't sign payments in this currency on this network, so nothing was sent. Tesser accepted the payment, so this is a fault at Tesser: contact Tesser support; retrying won't help | Tesser has no token contract for the payment's currency on its network, so it can't verify or send the signed transaction. Nothing was sent. Because Tesser accepted the payment, this is a fault at Tesser, not in the request. Contact Tesser support. Retrying won't help. |
payments-3069 | 500 | Tesser can't sign payments on this network, so nothing was sent. Tesser accepted the payment, so this is a fault at Tesser: contact Tesser support; retrying won't help | Tesser has no signing configuration for the payment's network, so it can't verify or send the signed transaction. Nothing was sent. Because Tesser accepted the payment, this is a fault at Tesser, not in the request. Contact Tesser support. Retrying won't help. |
payments-3070 | 400 | Stamped activity type does not match the expected type | The stamped Turnkey activity must be ACTIVITY_TYPE_SIGN_TRANSACTION_V2 to sign a payment step |
payments-3071 | 400 | Stamped activity unsigned transaction does not match the payment step | The unsigned transaction inside the stamped Turnkey activity must equal the unsigned transaction prepared by the payment step |
payments-3072 | 400 | Stamped activity sign_with address does not match the payment source wallet | The sign_with parameter inside the stamped Turnkey activity must equal the source wallet's on-chain address |
payments-3073 | 400 | Stamped activity transaction type does not match the expected type | The transaction type inside the stamped Turnkey activity must match the payment network's Turnkey transaction type |
payments-3074 | 400 | The signed request's organizationId isn't this workspace's Turnkey organization, so nothing was signed or sent. Stamp the request with the workspace's Turnkey organization and sign again; resending the same signature won't help | The organizationId inside the stamped sign_transaction activity must be the Turnkey organization of the workspace that owns the payment. It differs when the request was stamped in a Turnkey session or with an API key that belongs to another workspace, for example after switching workspaces in the dashboard. Nothing was signed or sent, and the step still waits for a signature. Stamp the request again with this workspace's Turnkey organization and sign again before the payment expires. Resending the same signature won't help. Also returned when Tesser has no Turnkey organization on record for the workspace; then contact Tesser support. |
payments-3075 | 400 | desired.from.network can't be used in this environment: production moves funds on mainnet networks only, and sandbox on testnet networks only. Create the payment with a network this environment supports; retrying won't help | Tesser's production environment moves funds on mainnet networks only, and sandbox on their testnet counterparts only. The payment's desired.from.network belongs to the other environment. The check runs on payments from a managed wallet, when they are created with accounts and on the PATCH that attaches them, and on every payment on a quote-first corridor. Nothing was created or changed. Create the payment again with a network this environment supports. Retrying the same request won't help. A payout that has to be funded on one network gets payments-3122 instead. |
payments-3076 | 400 | desired.from.account_id can't fund this payment: this payment can't be sent from that account. Choose a source account this payment supports and resend | The source account can't fund this payment. Same-currency payments are sent from a managed wallet or a provider-backed ledger, such as the Circle Mint ledger. Stablecoin payouts to a bank account are sent from a managed wallet with an on-chain address. Payouts from a pre-funded fiat ledger are sent from the workspace's Kraken ledger. Nothing was created or changed. Choose a source account that fits and resend. Retrying with the same account won't help. |
payments-3077 | 400 | A required CPN compliance field could not be resolved from the payment's counterparty/account data | The Circle Payments Network quote requires a travel-rule or beneficiary-account field for which no value (or no mapping) exists on the originator, beneficiary, beneficiary bank account, or OFI identity. Tesser validates existing data and fails fast rather than collecting new data. |
payments-3078 | 400 | Tesser doesn't support payments between this from_currency and to_currency. Use a supported currency pair; retrying won't help | No provider Tesser works with serves payments from this from_currency to this to_currency. Payments in a single currency move stablecoins only, so a payment that sends and delivers the same fiat currency gets this code too. Use a currency pair Tesser supports. Retrying the same request won't help. When the pair is supported but not enabled for your workspace, the payment gets payments-3120 instead. |
payments-3079 | 409 | Payment accounts can no longer be changed; the payment has already been planned. | PATCH attempted account changes after the payment's steps were planned; accounts are frozen once planning runs |
payments-3080 | 409 | The on-chain transaction was rejected because its nonce was already used by another transaction from this wallet. This payment is now in a failed state. You must create a new payment in order to try again. | Another transaction from the same wallet consumed this nonce before the signed transaction reached the network. The step is already failed and its signed transaction carries the spent nonce, so this payment cannot be retried — create a new payment, which is planned against a fresh nonce. |
payments-3081 | 500 | The network refused the signed transaction, so this payment step failed, nothing was sent and its reserved funds were released. Create a new payment; contact Tesser support if it fails again | Tesser sent the transaction you signed to the network, and the network refused it for a reason other than a nonce conflict. The step failed, nothing was sent and the reserved funds were released; the network's reason is in the message and on the step's status_reasons. This payment can't continue: create a new payment. If it fails the same way again, contact Tesser support with the request_id. When the network doesn't answer (a timeout or a lost connection), Tesser doesn't fail the step: it keeps the funds reserved and settles the step from the chain by its transaction_hash. |
payments-3082 | 409 | This payment waited for earlier payments from the same wallet to be submitted, but the wait expired. This payment is now in a failed state. You must create a new payment in order to try again. | The signed transaction's nonce was ahead of the wallet's submission watermark and the missing lower nonces were not submitted within the wait window. The step is already failed; a new payment is planned against a fresh nonce. |
payments-3083 | 422 | Travel Rule inbound payments aren't enabled for this organization, so Tesser can't simulate one. Contact Tesser support to enable them; retrying won't help until then | Tesser turns on Travel Rule inbound processing per organization, and it's off for this one, so a simulated Travel Rule inbound could never get a decision. Nothing was simulated. Contact Tesser support to enable it. Retrying won't help until then. |
payments-3084 | 503 | Travel Rule inbound simulation isn't set up in this environment. This is on Tesser's side, not in your request: contact Tesser support if you need it here; retrying won't help until Tesser sets it up | Tesser hasn't set up Travel Rule inbound simulation in this environment, so nothing was simulated. Nothing in the request can fix it. Contact Tesser support if you need it here. Retrying won't help until Tesser sets it up. |
payments-3085 | 422 | This organization's Travel Rule identity isn't set up with Tesser yet, so a simulated Travel Rule inbound can't be addressed to it. Contact Tesser support to finish Travel Rule onboarding; retrying won't help until then | Tesser sets up each organization's Travel Rule identity during onboarding, and this organization doesn't have one yet. Nothing was simulated. Contact Tesser support to finish Travel Rule onboarding. Retrying won't help until then. |
payments-3086 | 400 | Tesser found no name for the owner of to_account to claim as the beneficiary. Send claimed_beneficiary_name, or give the account's owner a name, and resend | Without claimed_beneficiary_name, the simulated counterparty claims the destination owner's own name, and Tesser found none for to_account. Nothing was simulated. Send claimed_beneficiary_name, or give the counterparty or tenant that owns the account a name (business_legal_name, or individual first and last name), and resend. Retrying the same request won't help. |
payments-3087 | 400 | Cross-ramp payments are quoted by the delivery amount. Provide desired.to.amount instead of desired.from.amount. | User creates a cross-currency payment on a served corridor with only the source amount; the quote-first provider quotes by the target amount |
payments-3088 | 409 | This originator already has a locked cross-ramp awaiting funds. Wait for it to be funded or expire, then retry. | Serialization guard (launch default): only one locked, awaiting-funds cross-ramp per originator, so concurrent deposits to the shared MXN VA cannot be confused. Retriable once the in-flight order funds or expires. |
payments-3089 | 422 | The originator behind desired.from.account_id isn't onboarded for cross-ramp payments yet. Tesser onboards originators outside the API: contact Tesser support. Retrying won't help until then; if this payment's quote has expired by then, create a new payment | Before a cross-ramp payment can be locked, its originator must be onboarded with the cross-ramp provider. Tesser does this outside the API, once per originator. Nothing was locked and the quote wasn't used. Contact Tesser support to onboard the originator. Retrying won't help until then; if the quote has expired by then, create a new payment. |
payments-3090 | 422 | The originator behind desired.from.account_id hasn't passed the cross-ramp provider's business verification (KYB) yet. Have the originator finish it through their verification link, then retry, or create a new payment if this one's quote has expired; contact Tesser support if verification stays pending or was rejected | The originator is onboarded, but the cross-ramp provider hasn't verified the business yet, so Tesser refused the lock before calling the provider; nothing was locked. Forward the originator's kyb_link from onboarding and wait for verification. In sandbox it completes in seconds, in production it can take days. Then send the PATCH again, or create a new payment if the quote has expired. Contact Tesser support if verification stays pending. |
payments-3093 | 500 | Tesser couldn't get a quote for this cross-ramp payment, so it failed before any funds moved. This is on Tesser's side, not in your request, and a new payment with the same currencies fails the same way: contact Tesser support | Tesser couldn't produce a quote for the cross-ramp payment's currency pair because of a gap on Tesser's side. The payment failed before any funds moved: its single step is failed with this code. A new payment with the same currencies fails the same way. Contact Tesser support. |
payments-3094 | 400 | This corridor is quoted by the send amount. Provide desired.from.amount and leave desired.to.amount empty. | User creates a cross-currency payment on a corridor priced forward from the source amount (e.g. CAD to NGN) with the delivery amount instead. Nothing was created. |
payments-3095 | 400 | This field cannot be set when requesting a quote on this corridor | The corridor is quoted without accounts or networks: Tesser chooses the network of every leg. Payments on this corridor carry a quote only and cannot yet be accepted: PATCH returns a 409 conflict and attaches no accounts. Nothing was created. |
payments-3096 | 409 | The payment has started executing; organization_reference_id and payment_info can no longer be changed. | PATCH repeated the committed accounts with a different organization_reference_id or payment_info after the commit started execution. Nothing was changed; resend the committed values or omit them. |
payments-3097 | 400 | funding_account_id must be the originator's bank or generic account, owned by a tenant or counterparty. Send that account as funding_account_id and resend; retrying with this account won't help | On a payout funded from a pre-funded fiat ledger, funding_account_id names the originator for the Travel Rule, so it must be a bank or generic account that belongs to the originator's tenant or counterparty. Nothing was changed. Send the originator's bank or generic account as funding_account_id and resend. Retrying with the same account won't help. |
payments-3098 | 422 | Tesser hasn't finished setting up this workspace for this payment: an account Tesser manages for it is missing. This isn't a problem with your request. Contact Tesser support; retrying won't help until Tesser sets it up | A payment that Zuba pays out moves funds through accounts Tesser creates and manages for the workspace: its Default Wallet, created with the workspace, and its Zuba ledger, created when Tesser sets the workspace up for Zuba payouts. The account named at the end of the error_message is missing. The PATCH attached nothing, and the payment still waits for its accounts. Contact Tesser support. Retrying won't help until Tesser sets the account up; then send the same PATCH again, or create a new payment if this one has expired. A payment funded on the wrong network gets payments-3122 instead. |
payments-3099 | 400 | funding_account_id must belong to a counterparty or tenant | User provides a funding_account_id owned by the workspace |
payments-3100 | 400 | reason must be at least 20 characters when reviewing as a dashboard user | A dashboard user submitted a review with no reason, or one shorter than 20 characters after trimming whitespace. API callers may omit the reason. |
payments-3101 | 409 | The payment expired before it could be reviewed | An outbound payment is past its expiry, so a review can no longer take effect. Nothing was changed and no review was recorded. Inbound payments never expire and are not affected. |
payments-3102 | 409 | The payment has failed and cannot be reviewed | An outbound payment has a failed step, so approving or rejecting it can no longer change the outcome. Nothing was changed and no review was recorded. Inbound payments are not affected: their review only records a compliance decision. |
payments-3103 | 400 | reason must be at most 500 characters | The review reason is longer than 500 characters after trimming whitespace. Applies to every caller. |
payments-3104 | 409 | The payment has already been decided | The payment's risk status is already final (automatically or manually approved or rejected), so a further review is refused and nothing is changed. The first decision stands: its reviewer, time and reason are not overwritten. |
payments-3105 | 409 | Payment is not awaiting a risk review | A review is only accepted while the payment's risk_status is awaiting_decision. A payment that has not been screened cannot be approved or rejected. |
payments-3106 | 400 | Unknown status in a payments list filter | risk_status takes compliance statuses and funds_status takes execution statuses, comma-separated, at most 50 items; any other value is rejected |
payments-3107 | 400 | Invalid amount in a payments list filter | from_amount_min, from_amount_max, to_amount_min and to_amount_max each take one non-negative decimal number with at most 30 integer and 18 fraction digits, in major units of from_currency or to_currency. Returned when a bound isn't such a number. Fix it and send the request again. A currency Tesser doesn't know returns payments-3112. |
payments-3108 | 400 | An amount filter needs its currency | from_amount_min/from_amount_max need from_currency and to_amount_min/to_amount_max need to_currency, because amounts are in that currency's major units |
payments-3109 | 400 | Invalid owner in a payments list filter | belongs_to takes comma-separated tenant ids (uuids) or the literal 'workspace', at most 100 items |
payments-3110 | 400 | Invalid search in a payments list filter | search takes a single text value of at most 200 characters without control characters; send it once |
payments-3111 | 400 | Invalid date in a payments list filter | start_date and end_date each take a single value, either a calendar date in YYYY-MM-DD format (whole UTC days) or a UTC date-time in YYYY-MM-DDTHH:mm |
payments-3112 | 400 | Invalid currency in a payments list filter | from_currency and to_currency each take one currency code of at most 64 characters without control characters. Returned when one is longer, contains control characters or is sent more than once, and when it's a code Tesser doesn't know while an amount bound on the same side is set. Fix it and send the request again. |
payments-3113 | 400 | Invalid date range in a payments list filter | start_date must not be later than end_date, comparing instants: a date-only start is that day at 00:00:00.000Z, a date-only end is that day at 23:59:59.999Z; equal instants are valid |
payments-3114 | 400 | Invalid amount range in a payments list filter | An amount minimum must not be greater than its maximum for the same currency |
payments-3115 | 400 | Invalid network in a payments list filter | network takes comma-separated network names of at most 64 characters without control characters, at most 50 items |
payments-3116 | 400 | Invalid payment type in a payments list filter | payment_type takes deposit, withdrawal or transfer, and must be sent once |
payments-3117 | 400 | funding_account_id, desired.from.account_id and desired.to.account_id must be provided together | User creates a payment with one or two of funding_account_id, desired.from.account_id and desired.to.account_id. Send all three or none; on corridors that take accounts only after the quote, send none and attach them with PATCH. Nothing was created. |
payments-3118 | 409 | This cross-ramp payment has no quote to lock yet: the quote is still being prepared, or it failed. Get the payment to see its status, then send the request again once the quote is ready, or create a new payment if it failed | Cross-ramp payments are quoted after they're created, so the quote isn't there right away. The request came before the quote was ready, or the quote failed. Get the payment: once its quote is ready, send the request again; if the payment failed, its status_reasons say why, and you create a new payment. |
payments-3119 | 500 | Tesser couldn't pay the network fee for this signed transaction, so the step failed and nothing was sent. The signature was valid. Create a new payment; contact Tesser support if it happens again | On Tempo, Tesser pays the network fee for the signed transaction. That failed, so the step failed and nothing was sent; the signature itself was valid. The payment can't continue: create a new one. If it fails the same way again, contact Tesser support with the request_id. |
payments-3120 | 422 | Payments between this from_currency and to_currency aren't enabled for your workspace yet, or the provider isn't taking new payments for them right now. Contact Tesser support to enable them; retrying won't help until then | Tesser supports payments between these currencies, but they aren't enabled for your workspace: the corridor isn't rolled out to it, its provider setup isn't complete, or the provider isn't taking new payments for it. Contact Tesser support to enable it. Retrying won't help until Tesser does. |
payments-3121 | 422 | The destination wallet is a Circle recipient only on other networks, not on desired.to.network, so Tesser can't pay it out from a Circle ledger on that network. Send the payment on a network the wallet is registered on, or contact Tesser support to register it on this one; retrying won't help | A payout from a Circle ledger to an external wallet needs the wallet to be a Circle recipient on desired.to.network. The wallet is registered with Circle on other networks, which the registered param lists as Circle chains, but not on this one: Circle may not support this network, or the wallet was registered before Tesser added it. Send the payment on a network the wallet is registered on, or contact Tesser support to register it on this one. Retrying the same request won't help. |
payments-3122 | 400 | This payout is funded on one network only, and desired.from.network isn't it. Create the payment with desired.from.network set to required_network; retrying won't help | A payout that Zuba completes from a managed wallet is funded on Tempo only (Tempo Moderato outside production), the one network Tesser's Zuba deposit address is on. The payment's desired.from.network names another network. Nothing was created, or, when the accounts were attached with PATCH, nothing was changed. Create the payment again with desired.from.network set to the network the error_message names as required_network. Retrying the same request won't help. |
payments-3123 | 500 | Tesser couldn't plan this payment because it has no amount recorded for it, so nothing was sent. This is a fault at Tesser, not in your request. Contact Tesser support with the payment id; retrying won't help | Tesser plans a payment between two Tesser-managed wallets from the amount it recorded when the payment was created. That amount is missing, so the payment can't be planned and nothing is sent. This is a fault at Tesser. Contact Tesser support with the payment id; retrying won't help. |
Last modified on