transfers-9101 | 500 | Tesser couldn't send this step because Tesser has no destination account recorded for it, so the step failed and no funds moved for it. This is a fault at Tesser, not in your request. Contact Tesser support with the payment id; retrying the same transfer won't help | Tesser planned the step without a destination account, which is a fault at Tesser. The step fails before Tesser calls the provider, so no funds move for it, and the transfer's later steps fail with it. Retrying the same transfer won't help; contact Tesser support with the payment id. |
transfers-9102 | 500 | Tesser couldn't send this step because it couldn't load the step's destination account, so the step failed and no funds moved for it. This is a fault at Tesser, not in your request. Contact Tesser support with the payment id; retrying the same transfer won't help | Tesser couldn't load the destination account recorded on the step when it went to send it, which is a fault at Tesser. The step fails before Tesser calls the provider, so no funds move for it, and the transfer's later steps fail with it. Retrying the same transfer won't help; contact Tesser support with the payment id. |
transfers-9103 | 500 | Tesser couldn't send this step because data Tesser needs for it is missing, so the step failed and no funds moved for it. This is a fault at Tesser, not in your request. Contact Tesser support with the payment id; retrying the same transfer won't help | When Tesser went to send the step, data it should have set while planning the transfer was missing: the step's source account, amount or currency, its destination, or the provider wallet behind one of its accounts. This is a fault at Tesser. The step fails before Tesser calls the provider, so no funds move for it, and the transfer's later steps fail with it. The error_message ends with what was missing. Retrying the same transfer won't help; contact Tesser support with the payment id. |
transfers-9104 | 500 | Tesser couldn't send this step because it couldn't load the step's source account, so the step failed and no funds moved for it. This is a fault at Tesser, not in your request. Contact Tesser support with the payment id; retrying the same transfer won't help | Tesser couldn't load the source account recorded on the step when it went to send it, which is a fault at Tesser. The step fails before Tesser calls the provider, so no funds move for it, and the transfer's later steps fail with it. Retrying the same transfer won't help; contact Tesser support with the payment id. |
transfers-9105 | 500 | Tesser couldn't send this step because the source OpenFX ledger isn't linked to its OpenFX account at Tesser, so the step failed and no funds moved for it. This is a fault in Tesser's setup, not in your request. Contact Tesser support with the payment id; retrying won't help until Tesser fixes the ledger | The OpenFX ledger the step sends from has no OpenFX account linked at Tesser, so Tesser can't ask OpenFX to send the withdrawal. This is a fault in Tesser's setup. The step fails before Tesser calls OpenFX, so no funds move for it, and the transfer's later steps fail with it. Retrying won't help until Tesser fixes the ledger; contact Tesser support with the payment id. |
transfers-9106 | 500 | Tesser couldn't send this step because it couldn't load the step's destination account, so the step failed and no funds moved for it. This is a fault at Tesser, not in your request. Contact Tesser support with the payment id; retrying the same transfer won't help | Tesser couldn't load the destination bank account or wallet recorded on the step when it went to send it, which is a fault at Tesser. The step fails before Tesser calls the provider, so no funds move for it, and the transfer's later steps fail with it. Retrying the same transfer won't help; contact Tesser support with the payment id. |
transfers-9107 | 500 | Tesser couldn't send this bank withdrawal step because the currency of the funds it holds doesn't match the currency Tesser planned for it, so the step failed and no funds moved for it. This is a fault at Tesser, not in your request. Contact Tesser support with the payment id; retrying the same transfer won't help | The funds the step would send, as the previous step delivered them, are in a different currency than the one Tesser planned for this bank withdrawal. Sending them would pay the wrong amount, so Tesser stops. This is a fault at Tesser. The step fails before Tesser calls the provider, so no funds move for it, and the transfer's later steps fail with it. Retrying the same transfer won't help; contact Tesser support with the payment id. |
transfers-9108 | 500 | Tesser couldn't prepare the transaction for you to sign for this step because Tesser has no destination address or network recorded for it, so the step failed and no funds moved for it. This is a fault at Tesser, not in your request. Contact Tesser support with the payment id; retrying the same transfer won't help | Before asking you to sign a wallet step, Tesser builds its transaction from the destination address and network it recorded when planning the transfer. One of them was missing, which is a fault at Tesser. The step fails before anything is signed or sent, so no funds move for it, and the transfer's later steps fail with it. Retrying the same transfer won't help; contact Tesser support with the payment id. |
transfers-9109 | 500 | Tesser couldn't prepare the transaction for you to sign for this step because it couldn't resolve the step's source wallet or amount, so the step failed and no funds moved for it. This is a fault at Tesser, not in your request. Contact Tesser support with the payment id; retrying the same transfer won't help | Before asking you to sign a wallet step, Tesser resolves the wallet and amount it sends from: the amount the previous step delivered, or the planned amount for the first step. One of them, or the source wallet's address, was missing, which is a fault at Tesser. The step fails before anything is signed or sent, so no funds move for it, and the transfer's later steps fail with it. Retrying the same transfer won't help; contact Tesser support with the payment id. |
transfers-9110 | 500 | Tesser can't send this step's currency on its network from a managed wallet, so the step failed before anything was signed or sent. This is a Tesser setup problem, not a problem with your request. Contact Tesser support with the step's payment or transfer id; retrying won't help | A step that sends from a managed wallet failed when Tesser prepared its transaction, because Tesser can't send the step's currency on the step's network (on Tempo it can only send USDC). Nothing was signed or sent for the step. This is a gap in Tesser's setup, not a problem with the request. Contact Tesser support with the id of the payment or transfer; retrying or creating the same one again won't help until Tesser fixes it. A sandbox OpenFX settlement in a currency other than USDC gets transfers-9316 instead. |
transfers-9111 | 500 | Tesser's sandbox can't simulate settlement of this OpenFX withdrawal on the destination network, so the step failed and no test funds were sent. This is a limit of Tesser's sandbox and doesn't happen in production. Create a new transfer to a wallet on a network the sandbox supports, or contact Tesser support; retrying on this network won't help | Sandbox only. OpenFX's sandbox doesn't settle withdrawals on-chain, so Tesser sends test USDC to the destination wallet in its place, and it can do that only on the testnets it supports. The step's destination network isn't one of them. Nothing was sent, the step failed and the transfer's later steps fail with it. Retrying on this network won't help: create a new transfer to a wallet on a supported network, or contact Tesser support. |
transfers-9112 | 500 | Tesser couldn't work out where to send this step's funds: the destination account has no address Tesser can send to, or the provider can't send to that kind of account. The step failed and no funds moved for it. This is a fault at Tesser, not in your request. Contact Tesser support with the payment id; retrying the same transfer won't help | When Tesser went to send the step, it couldn't resolve its destination: the destination account had no address recorded, or it is a kind of account the provider sending the step can't pay. Tesser should have caught this when planning the transfer, so it is a fault at Tesser. The step fails before anything is sent, so no funds move for it, and the transfer's later steps fail with it. Retrying the same transfer won't help; contact Tesser support with the payment id. |
transfers-9113 | 500 | Tesser couldn't plan this transfer, so it failed before any funds moved and nothing stays reserved for it. The detail, and cause_code when there is one, give the reason and who has to act. Retrying the same transfer won't help: fix what they name and create a new one, or contact Tesser support with the payment id if the cause is on Tesser's side | Tesser rejected the transfer while planning it, for a reason that retrying won't change: the provider refused the planned operation (for example an amount below its minimum), or something the transfer needs isn't set up yet, at the provider or at Tesser (for example missing provider permissions or a deposit address Tesser hasn't registered). The error_message ends with cause_code, the code of the underlying error, and its detail; that code's own entry says who has to act. The transfer fails with no funds moved, and any balance reserved for it is released. Fix the cause and create a new transfer, or contact Tesser support with the payment id when the cause is on Tesser's side. |
transfers-9114 | 500 | Tesser couldn't price this Kraken to Zuba payment yet because Kraken or Zuba couldn't quote it, so nothing is reserved and no funds moved. Tesser prices it again on the next balance change in the source Kraken ledger, so there is nothing to retry; if it is still unpriced at expires_at, it expires and you can create a new payment | Kraken to Zuba payments only. Before reserving funds, Tesser prices the payment with Kraken (its price, trade fee and withdrawal fee) and checks that Zuba still quotes the committed amount. When one of them can't quote it, for example because Kraken or Zuba is temporarily unavailable, Zuba won't quote the same amount again, or Kraken's withdrawal fee or minimum no longer fits the amount, the payment waits in awaiting_funds with nothing reserved, and its first step stays created with this reason, announced by payment.balance_updated. The next balance change in the source Kraken ledger prices it again and clears the reason. If it is still unpriced at expires_at, it expires as usual and no funds move; create a new payment then. The error_message ends with the provider's reason when there is one. There is nothing to retry. |
transfers-9201 | 500 | An upstream step failed, so this step was not executed | A prior step in the transfer failed and the failure cascaded to this downstream step. |
transfers-9202 | 500 | The inbound transaction was reorganized away before finality | A confirmed inbound step was dropped by a chain reorganization before reaching finality. |
transfers-9203 | 500 | Tesser's compliance screening rejected this payment, so its steps that hadn't been sent failed and no funds moved for them. Retrying or creating the same payment again won't help; contact Tesser support with the payment id to request a review | Outbound payments only. Compliance screening flagged a party in the payment and the workspace's risk profile rejects it, so Tesser failed every step still created or awaiting a signature: no funds moved for them, and any balance reserved for them is available again. The payment's risk_status is automatically_rejected, announced by payment.risk_updated. Retrying or creating the same payment again won't help; contact Tesser support with the payment id to request a review. A payment whose screening couldn't be completed fails with transfers-9321 instead, and one a reviewer in your workspace rejects with transfers-9322. On an inbound step this code appears only on records written before transfers-9323 existed, where it records a Travel Rule rejection: Tesser's for incomplete data or, on records written before transfers-9218 existed, one Tesser did not make. That step's status is unchanged and the funds may still arrive. |
transfers-9204 | 500 | This transfer reached expires_at, or its provider quote lapsed, before this step was sent, usually because it wasn't funded or signed in time. The step failed and no funds moved for it. Create a new transfer to try again | The transfer expired before the step was sent: it reached expires_at before it was funded, signed or sent to the provider, or the provider's quote for it lapsed first. Tesser fails every step that hadn't started, releases any balance reserved for them, and no funds move for them. A step already in flight is not expired; its own outcome decides. Create a new transfer to try again. |
transfers-9205 | 500 | Tesser's sandbox settlement wallet doesn't have enough USDC to deliver this simulated settlement, so the step failed. Your balance isn't affected. Tesser has been alerted; create a new payment once the wallet is refilled | Sandbox only. Tesser delivers simulated OpenFX settlements from its own sandbox wallet, and that wallet didn't hold enough USDC for this one. It isn't about your balance. Tesser is alerted automatically; create a new payment once the wallet is refilled, or contact Tesser support if it keeps happening. |
transfers-9206 | 500 | The on-chain transaction for this inbound transfer was included in a block but reverted, so no funds arrived. The credit applied when it was detected has been taken back. | Inbound funds are credited when the transfer is detected, before finality. A transfer that succeeded when reported can revert when re-executed after a reorg, since it runs against different preceding state. The credit is then reversed. If the recipient already spent it, the reversal recovers only what remains and the shortfall is reported for manual recovery. |
transfers-9207 | 500 | The on-chain transaction for this inbound transfer succeeded but did not move the expected funds to the expected address. The credit applied when it was detected has been taken back. | The transaction did not revert, but the token contract emitted no Transfer event matching the reported sender, recipient and amount. Distinct from a revert: execution succeeded, it simply did not deliver what was reported. Sustained for ten minutes before acting, because a node that is behind produces the same answer as a genuine absence. |
transfers-9208 | 500 | The quote expired before the provider accepted it | The rate lock was accepted within the quote window, but the quote had expired by the time the provider processed it, so the provider refused to create the order. No funds moved. Create a new payment for a fresh quote. |
transfers-9209 | 500 | Tesser is holding this Zuba payout for manual settlement because it couldn't complete automatically; reason says why. Zuba may already have sent it, and nothing is refunded while it's held. Don't create a new payment for these funds: Tesser support will complete or release the payout and contact you. Check the payment's status for the outcome | The funds reached the Zuba ledger, but the payout couldn't complete automatically, so Tesser holds it for manual settlement. The reason param says why: ledger_shortfall (the ledger can't cover a refreshed quote), ledger_over_allocation (an earlier payout from the ledger drew more than it was allocated), quote_unavailable (Zuba wouldn't quote the payout again), payout_refused (Zuba refused the payout), payout_failed (Zuba reported it failed or returned) or payout_unconfirmed (its outcome stayed unconfirmed). Zuba may already have sent it, so the outcome can be unknown. The step stays open and nothing is refunded until Tesser support completes it or releases it; a released payout fails with transfers-9317 and its funds return to the ledger. Don't create a new payment for these funds while the hold lasts. |
transfers-9210 | 500 | Tesser couldn't confirm whether Kraken carried out this step of a Kraken to Zuba payment, so it is holding the step for Tesser support; detail says why. Kraken may already have executed it and its funds stay held, so don't create a new payment for these funds. Tesser support confirms the outcome with Kraken and then completes or fails the step; check the payment's status for the outcome | Kraken to Zuba payments only. Tesser sent the step's conversion order or USDC withdrawal to Kraken but couldn't verify the result: no Kraken order or withdrawal id was confirmed before the submission deadline, Tesser couldn't save Kraken's acceptance, the order is attached to more than one step, or Kraken's records conflict with or differ from what Tesser sent. Kraken may already have executed it, so the step neither fails nor completes: it stays submitted or confirmed, and its funds stay held, until Tesser support confirms the outcome with Kraken and completes or fails it. The error_message ends with detail, Tesser's reason. Don't create a new payment for these funds while the hold lasts; check the payment's status for the outcome, or contact Tesser support with the payment id. In the sandbox, Tesser's Kraken simulator holds steps the same way. Other Kraken transfers fail with transfers-9319 in the same case, and a withdrawal Tesser couldn't prepare, so never sent to Kraken, is held with transfers-9320. |
transfers-9211 | 500 | Tesser is holding this transfer before it's sent because the workspace's Zuba sub-account isn't active, so nothing was sent and the funds stay in the source wallet. It doesn't resume on its own, and signing it again won't help while the sub-account is inactive. Contact Tesser support with the payment id: Tesser sends it once the sub-account is active, or releases it | The step pays into the workspace's Zuba ledger, and the workspace's Zuba sub-account isn't active (not created yet, pending KYB review, or closed), so sending would leave the funds stuck at Zuba. Tesser holds the step before it is sent; the funds stay in the source wallet and the step neither fails nor completes. It doesn't resume on its own: once the sub-account is active, Tesser support sends it, or releases it on request, which fails the step with transfers-9317 and leaves the funds in the wallet. Contact Tesser support with the payment id. |
transfers-9212 | 500 | The quote expired before the rate was locked: the payment wasn't updated with its accounts before the quote window ended, so Tesser created no order at Capa and no funds moved. Create a new payment for a fresh quote | A cross-ramp quote holds its rate only for a short window, and the rate is locked when the payment is updated with its accounts. The window ended first, so Tesser created no order at Capa and no funds moved. The payment shows as quote expired rather than failed. Create a new payment for a fresh quote. |
transfers-9215 | 500 | The Travel Rule request was rejected because the beneficiary name did not match | Tesser rejected the inbound Travel Rule request because the beneficiary name the originator sent did not match the owner of the destination wallet. The step's status is unchanged: it stays created until the funds in the transaction the Travel Rule data names arrive, and moves on as usual if they do. See participants[] for the name match result, once payment.participants_updated publishes it. A later decision on the same transfer is appended after this one. |
transfers-9216 | 500 | The Travel Rule request was authorized | Tesser authorized the inbound Travel Rule request. The step's status is unchanged: it stays created until the funds in the transaction the Travel Rule data names arrive. A later decision on the same transfer is appended after this one. |
transfers-9217 | 500 | The Travel Rule data moved to the payment that received the funds | The Travel Rule data named a transaction whose funds Tesser had already recorded as another inbound payment, so the data moved onto that payment. The error_message ends with (paymentId: <id>), the ID of that payment. This record received no funds: its step stays created and nothing else happens to it. Read the decision on the payment that received the funds. |
transfers-9218 | 500 | The Travel Rule request for this inbound payment was rejected by someone other than Tesser, such as the originator's VASP or the Travel Rule provider. The step's status is unchanged and the funds may still arrive; there is nothing to retry. Contact Tesser support with the payment id if you need the reason | The inbound Travel Rule request was rejected by someone other than Tesser: the originator's VASP, a rule or a person at the Travel Rule provider, or another organization sharing the provider entity. No risk screening ran for this decision. The step's status is unchanged: it stays created until the funds in the transaction the Travel Rule data names arrive, and moves on as usual if they do. A later decision on the same transfer is appended after this one. Records written before this code existed carry transfers-9203 for the same case. |
transfers-9301 | 500 | The provider rejected this step, so it failed and no funds moved for it. Retrying the same transfer won't help; create a new one, or contact Tesser support with the payment id if you don't know why it was rejected | The provider answered the step with a final rejection, so the step failed and no funds moved for it. The error_message ends with the provider's reason when there is one. Retrying the same transfer won't help: fix what the reason names and create a new one, or contact Tesser support with the payment id. |
transfers-9302 | 500 | The provider accepted this step but later reported that it failed, so the funds didn't reach the destination. Retrying the same transfer won't help; fix what the provider's reason names and create a new one, or contact Tesser support with the payment id | The provider (Circle, Zuba or Capa) accepted the payout or transfer and later reported that it failed, was returned or was cancelled, so the step failed after it was submitted. The error_message ends with the provider's code or reason when the provider sent one, and a Capa cancellation also records Capa's cancellation fee in the step's fees. After a Circle failure the funds are available again in the source account; after a Zuba or Capa failure, contact Tesser support with the payment id to recover them. Retrying the same transfer won't help: fix what the reason names, for example the beneficiary's bank details, and create a new one. A held step that Tesser support ends without completing it carries transfers-9317 instead. |
transfers-9303 | 500 | Tesser couldn't execute this step at the provider, so it failed and no funds moved for it. Retrying the same transfer won't help; contact Tesser support with the payment id, then create a new one | Tesser couldn't execute the step at the provider: Tesser's credentials or setup for the provider failed, the order or withdrawal couldn't be prepared, OpenFX refused it in a way Tesser can't tell apart from those, or an unexpected error stopped it. The provider didn't execute the step, so its funds are available again in the source account, and the steps after it fail with transfers-9201. The error_message ends with cause_code, the code of the underlying error, when there is one. Retrying the same transfer won't help: contact Tesser support with the payment id, then create a new one. A rejection Tesser can attribute to the provider carries transfers-9301 instead, an order that didn't fill transfers-9318, an outcome Tesser couldn't confirm transfers-9319, and a hold Tesser support ended transfers-9317. A Kraken to Zuba payment's withdrawal that couldn't be prepared is held with transfers-9320 instead of failing. |
transfers-9304 | 500 | OpenFX didn't complete the currency conversion for this step, so nothing was converted and the funds are available again on the OpenFX ledger in their original currency. cause_code and detail say whether OpenFX refused it or Tesser couldn't use OpenFX. Create a new transfer to try again; contact Tesser support with the payment id if it fails again | Tesser asked OpenFX to convert the step's funds and the request failed for good: OpenFX refused the quote or trade, or Tesser couldn't use OpenFX for it (for example its credentials failed). Nothing was converted; the funds are available again on the OpenFX ledger in their original currency, and the transfer's later steps fail with it. The error_message ends with cause_code and the detail. Create a new transfer to try again; if cause_code is a Tesser-side failure or it fails again, contact Tesser support with the payment id. |
transfers-9305 | 500 | The network refused this step's signed transaction, or Tesser couldn't pay its Tempo network fee, so the step failed, nothing was sent and any balance reserved for it is available again. detail gives the reason. Create a new transfer; contact Tesser support with the payment id if it fails again | Tesser sends the transaction you signed to the network. The network or Tesser's node refused it, or Tesser couldn't pay the fee of a Tempo transaction, so nothing was sent: the step failed, its reserved balance is released and the transfer's later steps fail with it. The step keeps the hash of the transaction that was never sent. The error_message ends with the reason, and the nonce when known. Create a new transfer; contact Tesser support with the payment id if it fails again. 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. |
transfers-9306 | 500 | Circle reported that the wire for this deposit failed, so Circle credited nothing and no funds reached the destination. Contact Tesser support with the deposit id to find out why before you send another wire; a new deposit may fail the same way | Circle reported the deposit's wire as failed, so nothing was credited and the deposit's later steps fail with it. Whether and when the wire returns to the sending bank is between Circle and that bank. Contact Tesser support with the deposit id to find out why before sending another wire. |
transfers-9307 | 500 | Tesser's sandbox couldn't send the test USDC that simulates settlement of this OpenFX withdrawal, so the step failed and no test funds reached the destination wallet. This is a fault in Tesser's sandbox, not in your request, and doesn't happen in production. Create a new transfer to try again; contact Tesser support if it keeps failing | Sandbox only. OpenFX's sandbox doesn't settle withdrawals on-chain, so Tesser sends test USDC to the destination wallet in its place, and that send failed. Nothing reached the wallet, the step failed and the transfer's later steps fail with it. This is a fault in Tesser's sandbox. Create a new transfer to try again, or contact Tesser support if it keeps failing. |
transfers-9308 | 500 | The test USDC transaction that Tesser's sandbox sent to simulate settlement of this OpenFX withdrawal reverted on-chain, so the step failed and no test funds reached the destination wallet. This is a fault in Tesser's sandbox, not in your request, and doesn't happen in production. Create a new transfer to try again; contact Tesser support if it keeps failing | Sandbox only. OpenFX's sandbox doesn't settle withdrawals on-chain, so Tesser sends test USDC to the destination wallet in its place; that transaction reverted. Nothing reached the wallet, the step failed and the transfer's later steps fail with it. This is a fault in Tesser's sandbox. Create a new transfer to try again, or contact Tesser support if it keeps failing. |
transfers-9309 | 500 | The provider reported that this withdrawal failed or was cancelled, so the step failed and the funds are available again in the account they were sent from. Create a new transfer to try again; contact Tesser support with the payment id if it fails again | The provider sending the withdrawal reported it failed or was cancelled: OpenFX through its withdrawal webhook, or Kraken in its withdrawal history. In the sandbox, Tesser's Kraken simulator reports the same when its on-chain send is rejected or reverts. The step failed, its funds are available again in the account they were sent from, and the transfer's later steps fail with transfers-9201. For a Kraken to Zuba payment, that is the USDC the conversion bought, in your Kraken ledger. For OpenFX, the error_message ends with OpenFX's status. Create a new transfer to try again; contact Tesser support with the payment id if it fails again. When Tesser can't confirm whether a Kraken withdrawal went through, the step fails with transfers-9319 instead, or is held with transfers-9210 for a Kraken to Zuba payment. |
transfers-9310 | 500 | The on-chain transaction was rejected because its nonce was already used by another transaction from this wallet. This transfer is now in a failed state. You must create a new transfer in order to try again. | Another transaction from the same wallet consumed this nonce before the signed transaction reached the network. The step is terminal and its signed transaction carries the spent nonce, so the transfer cannot be retried — a new one must be created. |
transfers-9311 | 500 | This transfer waited for earlier transfers from the same wallet to be submitted, but the wait expired. This transfer is now in a failed state. You must create a new transfer 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 terminal; a new transfer is planned against a fresh nonce. |
transfers-9312 | 500 | An earlier transfer from this wallet failed before being submitted, so this transfer's position in the submission queue became invalid. This transfer is now in a failed state. You must create a new transfer in order to try again. | A transfer holding a lower allocated nonce died before broadcast (wait timeout, expiry, risk rejection, or an on-chain nonce conflict), which invalidates every allocated nonce above it. The causing transfer's id is appended when known. |
transfers-9313 | 500 | The on-chain transaction for this transfer was included in a block but reverted, so no funds moved. The reserved balance has been released. You must create a new transfer in order to try again. | The transaction was mined and finalized, but its execution reverted — commonly insufficient token balance at execution time, or a token contract rejecting the transfer. Gas was still spent and is recorded as a fee on the step. The nonce was consumed, so later transfers from the same wallet are unaffected. |
transfers-9314 | 500 | The on-chain transaction for this transfer succeeded but did not move the expected funds to the expected address. The reserved balance has been released. You must create a new transfer in order to try again. | The transaction did not revert, but the token contract emitted no Transfer event matching the expected sender, recipient and amount. Distinct from a revert: execution succeeded, it simply did not deliver. Gas was spent and is recorded as a fee. The nonce was consumed. |
transfers-9315 | 500 | Tesser couldn't send this step because the destination isn't registered with the provider yet, so it failed and no funds moved for it. Contact Tesser support with the payment id; retrying won't help until the destination is registered | The step's destination wallet or bank account has no registration at the provider that sends it (an OpenFX withdrawal address or an active Circle recipient), so Tesser didn't call the provider. The step failed and no funds moved for it. Contact Tesser support with the payment id; create a new transfer once the destination is registered. |
transfers-9316 | 500 | Tesser's sandbox can only simulate an OpenFX settlement to a wallet in USDC, so this step failed and no test funds were delivered. Use USDC for this route in the sandbox and create a new one; retrying won't help, and production isn't affected | Sandbox only. OpenFX doesn't settle on chain in the sandbox, so Tesser simulates the settlement by sending testnet USDC from its own sandbox wallet to the destination wallet. It can only send USDC, and this step's currency is another one. The step failed, and later steps of the same transfer failed with transfers-9201. Use USDC for deposits, withdrawals, rebalances and payments that settle through OpenFX to a wallet in the sandbox. Retrying won't help. Production is not affected. |
transfers-9317 | 500 | Tesser support ended this held step without completing it, so it failed and the funds it held are available again in the account that held them. Retrying the same transfer won't help; create a new one if you still want to send these funds | Tesser held this step for manual handling (transfers-9209, transfers-9211 or transfers-9320), and Tesser support then ended the hold without completing it: the provider returned the payout or never made it, your Zuba account wasn't active, or the Kraken withdrawal couldn't be prepared. The step failed, and any steps after it fail with transfers-9201. The funds the step held are available again where they were: in your Zuba ledger for a payout, in the sending wallet for a transfer into the Zuba ledger, or in your Kraken ledger for a withdrawal. The reason for the hold is appended. Retrying the same transfer won't help; create a new one if you still want to send the funds. |
transfers-9318 | 500 | The provider closed this conversion order before it filled in full, so the step failed. Any amount that wasn't converted is available again in the source currency. Retrying the same transfer won't help; create a new one | Kraken accepted the market order but closed it, cancelled or expired, before it filled the planned quantity, for example because the market moved or had too little liquidity. The step failed, and the steps after it fail with transfers-9201. If nothing filled, the source funds are available again. If part of the order filled, that part was converted and stays in the account in the destination currency, and the rest is available again in the source currency. The provider's order id is appended. Retrying the same transfer won't help; create a new one. |
transfers-9319 | 500 | Tesser couldn't confirm whether the provider executed this step, so the step failed and its funds stay reserved until Tesser support confirms the outcome. Don't create a new transfer for these funds yet; contact Tesser support with the payment id | Tesser sent the order or withdrawal to Kraken but couldn't verify what happened to it: Kraken's answer was lost, no order or withdrawal id was confirmed before the submission deadline, Tesser couldn't save Kraken's acceptance, or Kraken's records don't match this step alone (an order attached to several steps, conflicting withdrawal history, or evidence that differs from what Tesser sent). It may still have executed, so the step failed without releasing its source funds: they stay reserved, and the steps after it fail with transfers-9201. Retrying won't help. Contact Tesser support with the payment id so it can confirm the outcome with Kraken, and don't create a new transfer for the same funds until it does. The error_message ends with Kraken's order_id or withdrawal_id when Tesser has one. Steps of a Kraken to Zuba payment are held with transfers-9210 instead of failing. |
transfers-9320 | 500 | Tesser couldn't prepare the Kraken withdrawal for this Kraken to Zuba payment, so it is holding the step before sending anything to Kraken; cause_code and detail say why. Nothing was sent and the USDC stays reserved in your Kraken ledger. Don't create a new payment for these funds; contact Tesser support with the payment id: Tesser sends the withdrawal once the cause is fixed, or releases it | Kraken to Zuba payments only. After the conversion, Tesser prepares the withdrawal of the USDC it bought from your Kraken ledger to the workspace's managed wallet. Preparing it failed for a reason that doesn't clear on its own: for example the wallet's address isn't a verified withdrawal address in your Kraken account, Kraken's withdrawal method, fee or minimum no longer fits the amount, the organization's Kraken credentials failed, or Tesser's data for the step is wrong. Nothing was sent to Kraken: the step stays created and the USDC stays reserved in your Kraken ledger. The error_message ends with cause_code, the code of the underlying error when there is one, and detail. The step doesn't resume on its own. Contact Tesser support with the payment id: Tesser sends the withdrawal once the cause is fixed, for example after the address is verified again at Kraken, or releases it, which fails the step with transfers-9317 and makes the USDC available in your Kraken ledger. Don't create a new payment for these funds while the hold lasts. Other Kraken withdrawals fail with transfers-9303 in the same case. |
transfers-9321 | 500 | Tesser couldn't complete compliance screening for this payment, and the workspace's risk profile rejects payments that can't be screened, so its steps that hadn't been sent failed and no funds moved for them. Nothing was found against any party. Create a new payment to try again; contact Tesser support with the payment id if it fails the same way | Outbound payments only. Tesser couldn't finish screening the payment's parties: the screening provider kept failing, or data Tesser needs to screen them was missing. The risk profile's screening_failure_action for outbound payments is automatically_rejected, which is Tesser's default, so Tesser failed every step still created or awaiting a signature: no funds moved for them, and any balance reserved for them is available again. risk_status is automatically_rejected, and risk_status_reasons has an entry with category SCREENING_FAILED. Nothing was found against any party. Create a new payment to try again; if it fails the same way, contact Tesser support with the payment id. Set screening_failure_action to awaiting_decision to hold such payments for review instead. |
transfers-9322 | 500 | A reviewer in your workspace rejected this payment, so its steps that hadn't been sent failed and no funds moved for them. The decision is final and retrying won't help; create a new payment if it should go ahead | Outbound payments only. Screening held the payment for review (risk_status awaiting_decision), and it was rejected through the payment's review endpoint or the dashboard. Tesser failed every step still created or awaiting a signature: no funds moved for them, and any balance reserved for them is available again. risk_status is manually_rejected, announced by payment.risk_updated. A reviewed payment can't be reviewed again, so retrying won't help; create a new payment if it should go ahead after all. |
transfers-9323 | 500 | Tesser rejected the Travel Rule request for this inbound payment because the sender's Travel Rule data was incomplete and the workspace's risk profile requires all of it. The step's status is unchanged and the funds may still arrive; there is nothing to retry. The sender can send complete data, or set data_completeness to PARTIAL to accept partial data on later transfers | Inbound only. Tesser rejected the Travel Rule request because the originator's data was incomplete while the workspace's risk profile sets data_completeness to ALL (PATCH /v1/compliance/risk-profile). The step's status is unchanged: it stays created until the funds in the transaction the Travel Rule data names arrive, and moves on as usual if they do. There is nothing to retry. The sender can send complete data, and a later decision on the same transfer is appended after this one. To accept partial data on future transfers, set data_completeness to PARTIAL. Records written before this code existed carry transfers-9203 for the same case. |