Errors
Treasury Errors
Error codes with the treasury- prefix. See the
Errors overview for the response format and the code convention.
Treasury
| Error Code | HTTP Status | Error Message | Description |
|---|---|---|---|
treasury-1000 | 404 | Rebalance not found | The specified rebalance ID does not exist |
treasury-1001 | 404 | Transfer step not found for rebalance | The transfer step associated with the rebalance could not be found |
treasury-1002 | 404 | Account not found | The specified account ID does not exist or does not belong to this workspace |
treasury-1100 | 404 | Deposit not found | The specified deposit ID does not exist in this workspace |
treasury-1101 | 404 | The destination account wasn't found in this workspace. Check desired.to.account_id and send the request again; retrying it unchanged won't help | The deposit's destination account (desired.to.account_id) doesn't exist, or belongs to another workspace. Nothing was created. Check the id and send the request again; retrying the same request won't help. |
treasury-1102 | 404 | desired.from.account_id isn't a bank account with workspace scope in this workspace. Send a new request with a workspace bank account as the source; retrying won't help | A deposit's source, desired.from.account_id, has to be a bank account with workspace scope in your workspace. Returned when you create a deposit and the account doesn't exist in the workspace, isn't a bank account, or belongs to an entity. If the source account stops qualifying before Tesser plans the deposit, the deposit's status_reasons carry transfers-9113 with cause_code treasury-1102 instead. It is also returned when you fetch instructions after the source account was removed. Create a new deposit from a workspace bank account; retrying the same request won't help. |
treasury-1103 | 422 | Tesser hasn't set up the bank account that receives wires in this currency for your workspace. Contact Tesser support; retrying won't help until Tesser sets it up | Tesser receives deposit wires into a bank account it sets up for each workspace and currency. Returned in a deposit's status_reasons when Tesser hasn't set one up for the deposit's currency, so the deposit failed while Tesser planned it, and when you fetch instructions for or simulate a deposit whose receiving account is missing. Contact Tesser support with the currency from the message; retrying won't help until Tesser sets up the account. Then create a new deposit. |
treasury-1200 | 404 | Withdrawal not found | The specified withdrawal ID does not exist in this workspace |
treasury-1201 | 404 | Source account not found | The withdrawal source account does not exist or does not belong to this workspace |
treasury-1202 | 404 | Destination bank account not found | The withdrawal destination bank account does not exist or does not belong to this workspace |
treasury-1203 | 404 | Transfer step not found for withdrawal | The transfer step associated with the withdrawal could not be found |
treasury-2100 | 409 | This deposit is still being planned, so Tesser can't return its instructions or simulate it yet. Wait for the deposit.quote_created webhook, or until the deposit shows its steps, then try again | Tesser plans a deposit right after it is created. Returned when you fetch the deposit's instructions, or simulate it in the sandbox, before planning has finished and the deposit has no steps yet. Wait for the deposit.quote_created webhook, or until GET returns the deposit with steps, then try again; retrying after that will work. |
treasury-3000 | 400 | Tesser can't move funds from a managed wallet to this destination. A managed wallet can send only to another Tesser-managed wallet or to an OpenFX or Kraken ledger. Change desired.to.account_id and send the request again; retrying won't help | A rebalance from a Tesser-managed wallet can go to another Tesser-managed wallet, or to an OpenFX or Kraken ledger. Any other destination, such as a Circle ledger, a bank account or an external wallet, is rejected when the rebalance is created. Choose a supported destination; retrying the same request won't help. |
treasury-3001 | 400 | A network was sent for a side of this rebalance that doesn't take one. Only a wallet side takes a network, and a same-account swap takes none. Remove it and send the request again; retrying won't help | Networks apply to wallets. Returned when a rebalance sends from_network or to_network for a side that is a ledger, or any network on a same-account swap. The exception is a rebalance from an OpenFX ledger to a Circle ledger, which takes to_network as the network the funds travel on. The field param names the network to remove when Tesser can tell which one. Remove it and send the request again; retrying the same request won't help. |
treasury-3002 | 400 | desired.from.amount is missing, so Tesser can't size this rebalance. Set the amount to move from the source account and send the request again; retrying the same request won't help | A rebalance needs desired.from.amount, the amount to move from the source account; rebalances don't take a destination amount. Set it and send the request again. Retrying the same request won't help. A rebalance or withdrawal step whose amount is missing at Tesser when you sign it returns treasury-3358 instead. |
treasury-3003 | 400 | This currency pair isn't available on this rebalance's route: Tesser doesn't offer it for these accounts, or the provider hasn't enabled it for your workspace. Choose a supported pair and send a new request; retrying won't help | Each rebalance route supports specific currency pairs. A wallet-to-wallet rebalance moves one currency. A Circle ledger rebalance supports Circle's pairs, a Kraken route sends and receives only USDC on the wallet side and swaps only along Kraken's routes, and an OpenFX route supports the pairs OpenFX offers your workspace, which can change with OpenFX's market data. Returned when the rebalance is created, or in the rebalance's status_reasons if the pair stops being available before Tesser plans it. Choose a supported pair; retrying the same request won't help. Contact Tesser support if you need a pair enabled. |
treasury-3005 | 500 | Tesser can't find the Circle wallet behind the destination ledger, so it can't get the ledger's deposit address. Contact Tesser support; retrying won't help until Tesser fixes the ledger | A rebalance from an OpenFX ledger to a Circle ledger sends the funds to the Circle ledger's deposit address, which Tesser looks up through the ledger's Circle wallet. Returned when that wallet is missing or changed during the lookup, when the rebalance is created or, in its status_reasons, when Tesser plans it. Contact Tesser support with the account id from the message; retrying won't help until Tesser fixes the ledger's setup. |
treasury-3006 | 422 | An account in this rebalance doesn't hold a currency it needs, so the rebalance failed. Contact Tesser support to add the currency, then create a new rebalance; retrying won't help | Tesser plans a rebalance against the currencies each account holds. Returned in the rebalance's status_reasons when the source ledger, or a ledger the route swaps through, doesn't hold one of the currencies, so the rebalance failed while Tesser planned it. Contact Tesser support with the account and currency from the message to add the currency, then create a new rebalance; retrying won't help. |
treasury-3007 | 400 | Network is required when rebalancing between wallet accounts | On-chain wallet-to-wallet rebalances need from_network and to_network to be set |
treasury-3008 | 400 | from_network and to_network must match for wallet-to-wallet rebalance | Cross-chain wallet-to-wallet rebalance is not supported yet; source and destination network must be identical |
treasury-3009 | 422 | A Tesser-managed wallet in this request has no on-chain address yet, so Tesser can't send funds to or from it. Contact Tesser support; retrying won't help until Tesser sets up the wallet | Tesser creates an on-chain address for every wallet it manages. Returned when a wallet in a rebalance has none: when the rebalance is created on a Kraken route, or in the rebalance's status_reasons when Tesser plans it. Contact Tesser support with the account id from the message; retrying won't help until Tesser sets up the wallet. |
treasury-3010 | 400 | Wallet-to-wallet rebalances work only between Tesser-managed wallets, and at least one of these wallets isn't managed by Tesser. Choose two Tesser-managed wallets and send the request again; retrying won't help | A rebalance between two wallets needs both to be wallets Tesser manages. Choose two Tesser-managed wallets; retrying the same request won't help. |
treasury-3011 | 500 | Tesser can't process a signed transfer of this currency on this network, so it can't accept the signature for this rebalance step. Contact Tesser support; signing again won't help | Returned when you sign a rebalance step whose currency Tesser can't process on the step's network. Tesser built the step's unsigned transaction for that currency and network, so this means Tesser's configuration changed after the step was prepared. The step may already be failed; fetch the rebalance to check. Contact Tesser support with the currency and network from the message; signing again won't help. |
treasury-3012 | 500 | Tesser can't move funds on this step's network, so nothing was sent. This is a problem in Tesser's setup, not with the request or the signature. Contact Tesser support; retrying won't help | Tesser can't move funds on the step's network: a wallet-source rebalance step was signed on a network Tesser has no signing configuration for, or Tesser planned a Kraken withdrawal on a network it hasn't enabled for Kraken withdrawals. Tesser only plans steps on networks it supports, so this points to a problem at Tesser, not to the request or the signature, and nothing was sent. Contact Tesser support with the rebalance or payment id; retrying won't help. A Kraken withdrawal whose withdrawal method Kraken doesn't list returns treasury-3354 instead. |
treasury-3013 | 409 | This rebalance step isn't waiting for a signature: it isn't signed with a wallet, or it has moved past signature_requested, for example because another request signed it. Fetch the rebalance to check the step's status; signing again won't help | Only a wallet-signed (Turnkey) step in signature_requested status accepts a signature. Returned when the step is another kind, has already been signed (also by a concurrent request), or changed status while Tesser was processing the signature. Fetch the rebalance and check the step's status before doing anything else; sending the same signature again won't help. |
treasury-3014 | 500 | This rebalance step is waiting for a signature, but Tesser has no unsigned transaction stored for it, so it can't accept one. Contact Tesser support; signing again won't help | A step in signature_requested status always carries the unsigned transaction to sign. Returned when Tesser's stored step is missing it, which is a fault at Tesser. Contact Tesser support with the step id from the message; signing again won't help. A step that isn't ready for signing yet returns treasury-3013 instead. |
treasury-3016 | 400 | Signed transaction does not match the rebalance details | The destination address or amount in the signed transaction does not match the prepared rebalance step |
treasury-3017 | 400 | The destination wallet isn't an active Circle recipient yet, so Tesser can't send this rebalance to it. Circle has to approve the wallet first: send the request again once it does, or contact Tesser support if it stays pending | A rebalance from a Circle ledger to a wallet needs the wallet to be an active Circle recipient on the requested network. The wallet isn't registered with Circle 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. |
treasury-3018 | 400 | network is required when the account is a wallet | Rebalance legs referencing a stablecoin wallet must specify that leg's blockchain network; the appended field names the leg |
treasury-3019 | 400 | Tesser doesn't support this network for this rebalance route in this environment. Choose a network the route supports and create the rebalance again; retrying the same request won't help | Each rebalance route works only on some networks, and the sandbox uses test networks where production uses main networks. Returned when a wallet's network isn't one Tesser supports for rebalances in this environment, when a rebalance from an OpenFX ledger to a Circle ledger names a to_network Circle can't receive on, or when a rebalance through Kraken uses a network Kraken isn't enabled for in this environment. The network param names the network when Tesser knows it. Usually returned when the rebalance is created. If the network stops being supported before Tesser plans the rebalance, the rebalance fails with transfers-9113 and this code as cause_code; if it happens when you sign a deposit into a Kraken ledger, the sign request returns this code and the step fails with it. Choose a supported network and create a new rebalance; retrying the same request won't help. A network sent where the route takes none returns treasury-3001 instead. |
treasury-3020 | 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 |
treasury-3021 | 400 | Stamped activity type does not match the expected type | The stamped Turnkey activity must be ACTIVITY_TYPE_SIGN_TRANSACTION_V2 to sign a rebalance step |
treasury-3022 | 400 | Stamped activity unsigned transaction does not match the rebalance step | The unsignedTransaction inside the stamped Turnkey activity must equal the unsigned transaction prepared by the rebalance step |
treasury-3023 | 400 | Stamped activity signWith address does not match the rebalance source wallet | The signWith parameter inside the stamped Turnkey activity must equal the source wallet's on-chain address |
treasury-3024 | 400 | Stamped activity organizationId does not match the workspace's Turnkey organization | The stamped Turnkey activity's organizationId must equal the ID of the workspace's Turnkey organization |
treasury-3025 | 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 rebalance 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. |
treasury-3026 | 400 | Stamped activity parameters.type does not match the expected type | The Turnkey transaction type inside parameters.type must match the network of the rebalance step (e.g. TRANSACTION_TYPE_ETHEREUM for BASE) |
treasury-3028 | 409 | The source wallet's on-chain balance is below the amount of this rebalance, so it wasn't signed. Fund the wallet, then sign the step again | At sign time the source wallet's live on-chain balance was below the rebalance amount, so nothing was signed or sent. The rebalance waits for funds: rebalance.balance_updated fires with balance_status awaiting_funds, unless balance_status is already reserved or awaiting_funds. Fund the wallet, then sign the step again; the balance is checked again then. |
treasury-3029 | 502 | OpenFX refused to quote this currency pair, so the rebalance failed. Create a new rebalance; if it fails again, contact Tesser support | Tesser asks OpenFX for a quote when it plans a rebalance that swaps currencies. Returned in the rebalance's status_reasons when OpenFX rejects the quote request, so the rebalance failed. Brief OpenFX outages don't cause it: Tesser retries those. Create a new rebalance; if it fails the same way, the pair may not be available to your workspace, so contact Tesser support with the currencies from the message. |
treasury-3030 | 422 | The destination wallet is a Circle recipient only on other networks, not on to_network, so Tesser can't send this rebalance to it on that network. Use a network the wallet is registered on, or contact Tesser support; retrying won't help | A rebalance from a Circle ledger to a wallet pays out through Circle, which only pays wallets registered as recipients on that network. Tesser registers each wallet with Circle on every supported network in its family. Returned when the wallet's registrations don't cover the requested to_network, including networks Circle doesn't support. The registered param lists the Circle chains the wallet is registered on. Send the rebalance on one of those networks, or contact Tesser support; retrying the same request won't help. |
treasury-3031 | 422 | The destination wallet isn't a verified withdrawal address in your OpenFX account for this currency and network, so OpenFX can't pay it. Add and verify the address in your OpenFX dashboard, then send the request again; retrying before that won't help | OpenFX only withdraws to addresses that are added and verified in your OpenFX account for each currency and network, and Tesser picks up verified addresses automatically. Returned when a rebalance from an OpenFX ledger to a wallet targets a wallet with no verified, active withdrawal address for the currency and network in the message. Add and verify the wallet's address in your OpenFX dashboard, then send the request again; retrying before that won't help. Contact Tesser support if the address is verified and the error persists. |
treasury-3100 | 400 | This destination account can't receive deposits: a deposit goes to a ledger or a Tesser-managed wallet. Set desired.to.account_id to one of those and send the request again; retrying won't help | Deposits land in a ledger or a Tesser-managed wallet. Returned when desired.to.account_id is another kind of account, such as a bank account or an external wallet. Choose a ledger or a Tesser-managed wallet; retrying the same request won't help. |
treasury-3101 | 500 | Tesser can't tell which provider handles this deposit, so it can't return the deposit's instructions or simulate it. This is a fault at Tesser, not in your request. Contact Tesser support with the deposit id; retrying won't help | Returned when you fetch a deposit's instructions, or simulate it in the sandbox, and Tesser can't resolve the provider that handles the deposit from its steps. A deposit Tesser planned always names one, so this is a fault at Tesser. Contact Tesser support with the deposit id from the message; retrying won't help. Simulating a deposit Tesser is still planning returns treasury-2100 instead. |
treasury-3102 | 500 | The ledger this deposit settles through has no Circle setup, so the deposit failed. Contact Tesser support, then create a new deposit; retrying won't help | Returned in a deposit's status_reasons when the Circle ledger that receives the deposit lost its Circle setup between creating the deposit and Tesser planning it, so the deposit failed. Contact Tesser support with the account id from the message, then create a new deposit; retrying won't help. |
treasury-3103 | 422 | Circle hasn't approved the ledger that receives this deposit; its compliance state is in the message. If it's PENDING, send the request again after Circle approves it; otherwise contact Tesser support | Circle has to accept a ledger in its compliance review before the ledger can take deposits, and Tesser picks up Circle's decision automatically. Returned when the deposit is created, or in its status_reasons when Tesser plans it, with the ledger's state: PENDING while Circle reviews it, REJECTED if Circle declined it. If pending, send the request again after approval; retrying before that won't help. If rejected, or pending for longer than expected, contact Tesser support with the account id from the message. |
treasury-3104 | 400 | Circle only takes this ledger's deposits from the bank account in expected_id, so the deposit failed. Create a new deposit from that bank account; retrying won't help | Each Circle ledger takes wire deposits from one bank account that Tesser registered with Circle for it. Returned in the deposit's status_reasons when desired.from.account_id is a different bank account, so the deposit failed while Tesser planned it. Create a new deposit from the bank account in expected_id; retrying won't help. Contact Tesser support to change the ledger's bank account. |
treasury-3105 | 400 | The deposit's source bank account was no longer a bank account in this workspace when Tesser planned it, so the deposit failed. Create a new deposit from an existing bank account; retrying won't help | Returned in a deposit's status_reasons when its source bank account was removed or changed after the deposit was created, so the deposit failed while Tesser planned it. Create a new deposit from an existing workspace bank account; retrying won't help. Contact Tesser support if the account still exists. |
treasury-3106 | 422 | The ledger this deposit settles in doesn't hold a currency the deposit needs, so the deposit failed. Contact Tesser support to add the currency, then create a new deposit | Tesser credits a deposit to a ledger that holds its currencies: the destination ledger or, for a wallet deposit, the ledger Tesser routes it through. Returned in the deposit's status_reasons when that ledger doesn't hold the source or destination currency, so the deposit failed while Tesser planned it. Contact Tesser support with the account and currency from the message, then create a new deposit; retrying won't help until Tesser adds the currency. |
treasury-3107 | 400 | Invalid currency combination for Circle deposit | The specified from_currency and to_currency combination is not supported for Circle deposits |
treasury-3108 | 400 | This deposit has already completed or failed, so Tesser no longer gives its wire instructions or simulates it. Create a new deposit to send more funds; retrying won't help | Returned when you fetch the instructions of a deposit that has completed or failed, or simulate a deposit that has failed in the sandbox. The deposit is over and can't be funded again. Create a new deposit to send more funds; retrying won't help. |
treasury-3109 | 500 | Tesser can't find the bank transfer step of this deposit, so it can't return instructions or simulate it. Contact Tesser support; retrying won't help | Returned when you fetch a deposit's instructions or simulate it in the sandbox, and the deposit has no step for the incoming bank transfer. A deposit Tesser planned always has one, so this is a fault at Tesser. Contact Tesser support with the deposit id from the message; retrying won't help. |
treasury-3110 | 500 | Tesser's stored deposit has no source bank account, so Tesser can't plan it or return its instructions. Contact Tesser support; retrying won't help | Returned when you fetch a deposit's instructions, or in the deposit's status_reasons when Tesser plans it, and Tesser's stored deposit is missing its source bank account. This is a fault at Tesser. Contact Tesser support with the id from the message; retrying won't help. If the deposit failed, create a new one once Tesser confirms the fix. |
treasury-3111 | 500 | Tesser's stored deposit has no receiving bank account, so Tesser can't return its instructions or simulate it. Contact Tesser support; retrying won't help | Returned when you fetch a deposit's instructions, or simulate it in the sandbox, and Tesser's stored deposit is missing the bank account that receives the wire. This is a fault at Tesser. Contact Tesser support with the deposit id from the message; retrying won't help. |
treasury-3112 | 422 | The source bank account is missing details Tesser needs for the wire instructions (bank name, bank code or account number). Create the deposit from a bank account with complete details, or contact Tesser support; retrying won't help | The deposit's source bank account has no bank name, bank code type, bank identifier code or stored account number, so Tesser can't build the wire instructions. Bank accounts created through the API always have them, so this usually means an account set up another way; bank details can't be edited. Create a new deposit from a bank account with complete details, or contact Tesser support with the account id from the message. Retrying won't help. When the details are stored but Tesser can't read them right now, treasury-3355 is returned instead. |
treasury-3113 | 500 | Tesser's receiving bank account for this deposit has no account details, so Tesser can't give its wire instructions or simulate it. Contact Tesser support; retrying won't help until Tesser fixes the account | Tesser receives deposit wires into a bank account it sets up for your workspace. Returned when you fetch a deposit's instructions, or simulate it in the sandbox, and that account has no account details stored. This is a fault at Tesser. Contact Tesser support with the account id from the message; retrying won't help until Tesser fixes the account. Simulating a deposit that has already failed returns treasury-3108 instead. |
treasury-3114 | 500 | Tesser's receiving bank account for this deposit is incomplete, so Tesser can't give wire instructions. Contact Tesser support; retrying won't help until Tesser completes it | Wire instructions need the receiving bank account's bank name, account number, bank code and beneficiary name, and for Circle also the SWIFT code. Returned when you fetch a deposit's instructions, or simulate it in the sandbox, and one of them is missing; the field param names it. Contact Tesser support with the account id and field from the message; retrying won't help until Tesser completes the account. |
treasury-3115 | 400 | Simulated deposits are not available in production | Deposit simulation is only available in sandbox environments |
treasury-3116 | 400 | to_network is required when destination is a managed wallet | Deposits to a managed stablecoin wallet must specify the target blockchain network |
treasury-3117 | 400 | to_network must not be specified for ledger accounts | Deposits to ledger accounts operate without a blockchain network |
treasury-3118 | 400 | Network is not supported in this environment | Deposits to managed wallets only support BASE in production and BASE_SEPOLIA in non-production environments |
treasury-3119 | 500 | Tesser has no source amount on record for this deposit, so it can't provide the wire details. This is a fault at Tesser: contact Tesser support; retrying won't help | Returned when you fetch wire instructions for a deposit, or simulate its funding in the sandbox, after planning has finished but Tesser has no source amount or currency stored for it. A deposit that is still being planned returns treasury-2100 instead. This is a data fault at Tesser: contact Tesser support with the deposit id. Retrying won't help. |
treasury-3120 | 400 | No provider can take this deposit or rebalance with these accounts, currencies and networks. Change them and resend, or contact Tesser support if this route should work; retrying the same request won't help | No provider supports the combination of source account, destination account, currency pair and network in the request for your workspace: the pair isn't offered, the accounts can't be paired, or your workspace isn't set up with a provider that serves this route. When a provider applies but refuses (for example a compliance review or a missing registration), you get that provider's own error with a provider field instead. Change the request and resend, or contact Tesser support if you expect the route to work. Retrying the same request won't help. |
treasury-3133 | 422 | Tesser couldn't find your workspace's OpenFX ledger for this deposit's currency, so the deposit failed before any funds moved. This is a setup problem for Tesser to fix, not a problem with your request. Contact Tesser support; retrying won't help until the ledger is set up | Planning only. A deposit through OpenFX settles on your workspace's OpenFX ledger for the currency you send, which Tesser sets up when your organization connects OpenFX. The ledger was there when the deposit was created, but when Tesser planned it the destination was no longer an OpenFX ledger, or no OpenFX ledger in the workspace held the deposit's currency. The deposit failed before any funds moved. You see this code as cause_code on the deposit's transfers-9113 status reason, with this message as its detail. Contact Tesser support with the deposit id, and create a new deposit once the ledger is set up again; retrying won't help until then. If your organization has no OpenFX credentials stored, the deposit fails with openfx-1000 instead. |
treasury-3134 | 400 | OpenFX doesn't offer this currency pair for deposits to your workspace, so retrying won't help. Choose another pair, or contact Tesser support if OpenFX should offer it | OpenFX converts deposited fiat to a stablecoin only for the pairs it currently offers your workspace; same-currency deposits need no conversion. This error means OpenFX's current market list for your workspace doesn't include the pair. Choose a different pair and create the deposit again, or contact Tesser support if OpenFX should offer it. Retrying the same pair won't help. |
treasury-3136 | 502 | OpenFX didn't quote this deposit's conversion, so the deposit failed. Create a new deposit; contact Tesser support if it fails again | While planning the deposit, OpenFX refused or failed the quote for its currency conversion, so the deposit failed before any funds moved. The failed step's status_reasons carry this code as cause_code. The failed deposit can't be retried: create a new deposit. If that fails too, OpenFX may not offer the pair or amount for your workspace; contact Tesser support. |
treasury-3139 | 422 | The wallet isn't a verified OpenFX withdrawal address for this coin and network. Add it in your OpenFX dashboard, then create the transfer again | OpenFX only pays out to wallet addresses registered and verified as withdrawal addresses in your OpenFX account, per coin and network. The destination wallet isn't one for the requested coin and network. Add the address in your OpenFX dashboard (or ask Tesser support), then create the deposit or rebalance again; retrying before that won't help. At creation the request is rejected; if registration changes while a deposit or rebalance is being planned, it fails instead. In the sandbox, any verified address for the coin and network counts. |
treasury-3140 | 422 | Your OpenFX account lists this wallet more than once for this coin and network. Remove the duplicates in your OpenFX dashboard, then create the transfer again | Your OpenFX account has more than one verified withdrawal address that matches the destination wallet for the coin and network, so Tesser can't tell which one to use. Keep one and remove the others in your OpenFX dashboard (or ask Tesser support), then create the deposit or rebalance again; retrying before that won't help. In the sandbox, Tesser matches on coin and network only, so any two verified addresses for the same coin and network count as duplicates. |
treasury-3141 | 422 | The wallet is a verified OpenFX withdrawal address for this coin but not this network. Add it in your OpenFX dashboard, then create the transfer again | Your OpenFX account has the destination wallet as a verified withdrawal address for the coin, but only on other networks, or on a network Tesser doesn't support. The deposit or rebalance fails during planning. Add the address for the requested network in your OpenFX dashboard (or ask Tesser support), then create a new deposit or rebalance. Retrying won't help until then. |
treasury-3142 | 400 | to_network is required for a deposit to a wallet. Create a new deposit with to_network set | A deposit to a wallet must name the blockchain network in to_network. Such requests are normally rejected when created (treasury-3116); this error is the planning-time safeguard, and the deposit has failed. Create a new deposit with to_network set. |
treasury-3144 | 422 | The source bank account isn't registered in your OpenFX account, so OpenFX won't accept this deposit from it. Register it with OpenFX or ask Tesser support, then create the deposit again once OpenFX accepts it; retrying before that won't help | OpenFX takes deposits only from bank accounts registered in your OpenFX account, which Tesser matches to the source bank account by its account number; Tesser doesn't register bank accounts at OpenFX for you. No registration matches the source bank account. Usually returned when you create the deposit. If the registration changes before Tesser plans the deposit, the deposit fails instead, before any funds move, with this code as cause_code on its transfers-9113 status reason. Register the account with OpenFX (or ask Tesser support) and create the deposit again once OpenFX accepts it; retrying before that won't help. A registered account OpenFX hasn't activated yet returns treasury-3148, and a registration check that fails returns treasury-3357. |
treasury-3145 | 500 | Tesser has no on-chain address on record for the destination wallet. This is a fault at Tesser: contact Tesser support; retrying won't help | The destination wallet has no on-chain address stored at Tesser, so Tesser can't match it with a withdrawal address at OpenFX. This is a data fault at Tesser, not a problem with the request: contact Tesser support with the wallet's account id. Retrying won't help. |
treasury-3146 | 422 | The destination wallet isn't an active Circle recipient on this network yet. Approve its pending registration in your Circle account, or contact Tesser support if it was never registered, then resend | Circle deposits to a wallet need an active Circle recipient registration for the requested network. Tesser submits registrations when the wallet is created; each starts pending until it's approved in your Circle account. Approve the pending registration and resend the deposit, or contact Tesser support if the wallet has no registration. Retrying won't help until the registration is active. |
treasury-3147 | 400 | Destination wallet is registered with Circle on a different network than the requested one | Deposit to a Circle-bound wallet whose registered recipient chain doesn't match the requested to_network. |
treasury-3148 | 422 | OpenFX hasn't activated the source bank account yet. Create the deposit again once it's active, or contact Tesser support | The source bank account is registered in your OpenFX account, but OpenFX hasn't activated it yet; the status param shows OpenFX's status, for example under review. Create the deposit again once OpenFX activates it; retrying before that won't help. Contact Tesser support if it stays inactive or OpenFX rejected it. |
treasury-3149 | 400 | Unknown status in a treasury activity filter | funds_status takes execution statuses or in_progress, comma-separated, at most 50 items; any other value is rejected |
treasury-3150 | 400 | Invalid amount in a treasury activity 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 treasury-3155. |
treasury-3151 | 400 | A treasury activity 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 |
treasury-3152 | 400 | Invalid owner in a treasury activity filter | belongs_to takes comma-separated tenant ids (uuids) or the literal 'workspace', at most 100 items |
treasury-3153 | 400 | Invalid search in a treasury activity filter | search takes a single text value of at most 200 characters without control characters; send it once |
treasury-3154 | 400 | Invalid date in a treasury activity 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 |
treasury-3155 | 400 | Invalid currency in a treasury activity 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. |
treasury-3156 | 400 | Invalid type in a treasury activity filter | types takes deposit, withdrawal or rebalance, comma-separated, at most 50 items; any other value is rejected and the parameter must be sent once |
treasury-3157 | 400 | Invalid date range in a treasury activity 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 |
treasury-3158 | 400 | Invalid amount range in a treasury activity filter | An amount minimum must not be greater than its maximum for the same currency |
treasury-3159 | 400 | Invalid network in a treasury activity filter | network takes comma-separated network names of at most 64 characters without control characters, at most 50 items |
treasury-3200 | 400 | from_currency must be a valid currency code | User provides an invalid from_currency value |
treasury-3201 | 400 | to_currency must be a valid currency code | User provides an invalid to_currency value |
treasury-3202 | 400 | from_amount must be a valid decimal string | User provides a from_amount that is not a valid number |
treasury-3203 | 400 | to_amount must be a valid decimal string | User provides a to_amount that is not a valid number |
treasury-3204 | 400 | from_account_id must be a valid UUID | User provides a from_account_id that is not a valid UUID |
treasury-3205 | 400 | to_account_id must be a valid UUID | User provides a to_account_id that is not a valid UUID |
treasury-3206 | 400 | from_network must be a valid network identifier | User provides an invalid from_network value |
treasury-3207 | 400 | to_network must be a valid network identifier | User provides an invalid to_network value |
treasury-3300 | 400 | from_amount must be provided | Withdrawals must specify the source amount in major units |
treasury-3301 | 400 | desired.from.network must be left out when the source account is a ledger, because a ledger withdrawal doesn't move on a blockchain network. Remove it and send the request again; retrying it unchanged won't help | A withdrawal from a ledger account doesn't use a blockchain network, so desired.from.network is only accepted when the source is a wallet. Nothing was created. Remove desired.from.network and send the request again; retrying the same request won't help. |
treasury-3302 | 400 | The provider doesn't offer this currency pair for withdrawals in your workspace, so retrying won't help. Choose another pair, or contact Tesser support if it should be offered | The provider that would serve the withdrawal doesn't offer the currency pair for your workspace: OpenFX's current market list doesn't include it, or, for Circle, the pair isn't USDC to USD. At creation the response item's provider field names the provider. Choose a different pair and create the withdrawal again, or contact Tesser support if the pair should be offered. Retrying the same pair won't help. |
treasury-3303 | 400 | A withdrawal without from_network must come from a ledger account. Create a new withdrawal from a ledger, or from a wallet with from_network set | A withdrawal with no from_network pays out from a provider ledger, and the source account isn't a ledger. Requests like this are normally rejected when created; this error is the planning-time safeguard, and the withdrawal has failed. Create a new withdrawal from a ledger, or from a wallet with from_network set. |
treasury-3304 | 400 | Destination account must be a workspace bank account | Withdrawals can only target a workspace-level bank account (type=fiat_bank, no entity_id) |
treasury-3305 | 422 | Your workspace's Circle ledger isn't set up for wallet withdrawals, so this withdrawal failed. Contact Tesser support; retrying won't help until it's set up | Wallet withdrawals through Circle move the funds through your workspace's main Circle ledger, which Tesser creates when Circle is connected, and it's missing or incomplete. The withdrawal fails during planning, before any funds move. Contact Tesser support, then create a new withdrawal. Retrying won't help until then. |
treasury-3306 | 400 | Withdrawal step is not in a signable state | The step must be a turnkey step in 'signature_requested' state with a prepared unsigned transaction to accept a signature |
treasury-3307 | 500 | This withdrawal step has no transaction to sign, which is a fault at Tesser. Contact Tesser support; retrying won't help | You submitted a signature for a withdrawal step that is waiting for one, but Tesser has no prepared transaction stored for it. Tesser stores the transaction when the step starts waiting for a signature, so this is a data fault at Tesser, not a timing issue. Contact Tesser support with the withdrawal and step ids. Retrying won't help. |
treasury-3309 | 400 | Signed transaction does not match the withdrawal details | The destination address or amount in the signed transaction does not match the prepared withdrawal step |
treasury-3310 | 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 |
treasury-3311 | 400 | Stamped activity type does not match the expected type | The stamped Turnkey activity must be ACTIVITY_TYPE_SIGN_TRANSACTION_V2 to sign a withdrawal step |
treasury-3312 | 400 | Stamped activity unsigned transaction does not match the withdrawal step | The unsignedTransaction inside the stamped Turnkey activity must equal the unsigned transaction prepared by the withdrawal step |
treasury-3313 | 400 | Stamped activity signWith address does not match the withdrawal source wallet | The signWith parameter inside the stamped Turnkey activity must equal the source wallet's on-chain address |
treasury-3314 | 400 | Stamped activity organizationId does not match the workspace's Turnkey organization | The stamped Turnkey activity's organizationId must equal the ID of the workspace's Turnkey organization |
treasury-3315 | 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 withdrawal 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. |
treasury-3316 | 400 | Stamped activity parameters.type does not match the expected type | The Turnkey transaction type inside parameters.type must match the network of the withdrawal step (e.g. TRANSACTION_TYPE_ETHEREUM for BASE) |
treasury-3317 | 500 | Tesser can't sign this currency on this network, so this withdrawal can't be submitted. This is a fault at Tesser: contact Tesser support; retrying won't help | Tesser no longer supports the withdrawal's currency on its network, although it did when the withdrawal was created. This is a fault at Tesser: contact Tesser support with the withdrawal id. Retrying won't help. |
treasury-3318 | 500 | Tesser can't sign or route transactions on this network, so this withdrawal can't be submitted. This is a fault at Tesser: contact Tesser support; retrying won't help | Tesser accepted the withdrawal on a network it can no longer move it on: Tesser no longer supports signing on the withdrawal's network, or Circle, which a wallet withdrawal through Circle goes through, doesn't support it. This is a fault at Tesser: contact Tesser support with the withdrawal id. Retrying won't help. |
treasury-3319 | 409 | Source wallet has insufficient on-chain balance to sign | The wallet's live on-chain balance is below the withdrawal amount at sign time. The balance is checked again when you sign again; withdrawal.balance_updated fires with balance_status awaiting_funds, unless balance_status is already reserved or awaiting_funds. |
treasury-3320 | 400 | No provider can take this withdrawal with these accounts, currencies and network. Change them and resend, or contact Tesser support if this route should work; retrying the same request won't help | No provider supports the combination of source account, destination bank account, currency pair and network in the request for your workspace: the pair isn't offered, the source account can't be withdrawn from this way, or your workspace isn't set up with a provider that serves this route. When a provider applies but refuses (for example a compliance review or an unregistered bank account), you get that provider's own error with a provider field instead. Change the request and resend, or contact Tesser support if you expect the route to work. Retrying the same request won't help. |
treasury-3321 | 400 | Deposit has already received its funding wire. Wire instructions are no longer available | The funding wire has already been received and instructions cannot be retrieved |
treasury-3322 | 422 | Circle hasn't approved the Circle ledger this withdrawal pays out through, so Circle can't take it. Resend once Circle approves it, or contact Tesser support if it was rejected | Circle withdrawals pay out through a Circle ledger that Circle must have approved in its compliance review: the source ledger, or for a wallet source, your workspace's main Circle ledger. The state param shows Circle's review state. If it's PENDING, resend once Circle approves it; retrying before that won't help. If it's REJECTED or none, contact Tesser support. |
treasury-3323 | 400 | Same-account rebalances require different currencies | A same-account rebalance is a currency swap and cannot have matching from/to currencies |
treasury-3324 | 400 | Same-account swaps work only with currencies Tesser supports, and this currency isn't one. Choose a supported currency and resend; retrying the same request won't help | A same-account rebalance swaps currencies within one ledger, so both from_currency and to_currency must be currencies Tesser supports. The currency param names the one that isn't. Choose a supported currency and resend. Retrying the same request won't help. |
treasury-3325 | 422 | The destination bank account isn't registered in your OpenFX account for this currency. Register it there, then create the withdrawal again | OpenFX pays out only to bank accounts registered in your OpenFX account, once per currency. The destination bank account has no active registration for the payout currency. Register it for that currency in your OpenFX dashboard (or ask Tesser support), then create the withdrawal again. Retrying won't help until then. |
treasury-3326 | 502 | OpenFX didn't quote this withdrawal's conversion, so the withdrawal failed. Create a new withdrawal; contact Tesser support if it fails again | While planning the withdrawal, OpenFX refused or failed the quote for its currency conversion, so the withdrawal failed before any funds moved. The failed step's status_reasons carry this code as cause_code. The failed withdrawal can't be retried: create a new withdrawal. If that fails too, OpenFX may not offer the pair or amount for your workspace; contact Tesser support. |
treasury-3327 | 400 | Destination bank is not activated with OpenFX yet | The destination bank matched an OpenFX fiat withdrawal address, but none of its addresses are active yet (e.g. under review). Wait for OpenFX approval before retrying the withdrawal. |
treasury-3328 | 422 | Tesser hasn't set up the OpenFX deposit address this withdrawal needs for this currency and network in your workspace. Contact Tesser support; retrying won't help until Tesser adds the address | A withdrawal from a wallet through OpenFX sends the funds to the workspace's OpenFX deposit address for the wallet's currency and network, and Tesser hasn't added that address to your workspace yet. Only production checks this; sandbox uses a shared address. Contact Tesser support with the account, currency and network from the message; retrying won't help until Tesser adds the address. A Tempo wallet gets treasury-3346 instead, because OpenFX doesn't support Tempo. |
treasury-3329 | 422 | Your workspace has no OpenFX ledger for wallet withdrawals, so this withdrawal failed. Contact Tesser support; retrying won't help until it's set up | Wallet withdrawals through OpenFX move the funds through your workspace's OpenFX ledger, and the workspace has none. The withdrawal fails during planning, before any funds move. Contact Tesser support, then create a new withdrawal. Retrying won't help until then. |
treasury-3330 | 400 | Amount is below the OpenFX minimum on-chain deposit | OpenFX never credits on-chain deposits below its minimum — sub-minimum funds are not shown on the ledger and are unrecoverable, so wallet-source withdrawals below the minimum fail closed before anything is dispatched on-chain. |
treasury-3331 | 400 | Amount is below the provider's minimum tradable amount | The route includes a currency conversion, and the provider enforces a per-currency minimum on the sold amount. A sub-minimum trade would be rejected at execution — after inbound funds already landed on the provider ledger — so the request fails closed at creation instead. |
treasury-3332 | 400 | Amount is above the provider's maximum tradable amount | The route includes a currency conversion, and the provider enforces a per-currency maximum on the sold amount. An above-maximum trade would be rejected at execution — after inbound funds already landed on the provider ledger — so the request fails closed at creation instead. |
treasury-3333 | 422 | Tesser hasn't set up the OpenFX deposit address this rebalance needs for this currency and network on the destination account. Contact Tesser support; retrying won't help until Tesser adds the address | A rebalance from a wallet into an OpenFX ledger sends the funds to the ledger's OpenFX deposit address for the wallet's currency and network, and Tesser hasn't added that address to the destination account yet. Only production checks this; sandbox uses a shared address. Contact Tesser support with the account, currency and network from the message; retrying won't help until Tesser adds the address. A Tempo wallet gets treasury-3347 instead, because OpenFX doesn't support Tempo. |
treasury-3334 | 400 | Amount is below the OpenFX minimum on-chain deposit | OpenFX never credits on-chain deposits below its minimum — sub-minimum funds are not shown on the ledger and are unrecoverable, so wallet-source rebalances below the minimum fail closed before anything is dispatched on-chain. |
treasury-3335 | 400 | Destination ledger has no on-chain deposit address for the currency and network. Provision one via POST /v1/accounts/ | OpenFX→Circle rebalances ride an on-chain withdrawal to the destination ledger's deposit address. The corridor never creates addresses — provision via the onchain-addresses endpoint, then register the address as an OpenFX withdrawal address (manual provider step). |
treasury-3336 | 400 | to_network is required for rebalances from an OpenFX ledger to a Circle ledger account | OpenFX→Circle rebalances move funds on-chain, so the caller must pick the transit network via to_network. There is no default. |
treasury-3337 | 422 | The destination Circle ledger's deposit address isn't a verified OpenFX withdrawal address for this currency and network. Add it in your OpenFX dashboard, then create the rebalance again; retrying before that won't help | A rebalance from an OpenFX ledger to a Circle ledger is an on-chain withdrawal from OpenFX to the Circle ledger's deposit address, and OpenFX only pays out to addresses registered and verified as withdrawal addresses in your OpenFX account, per currency and network. The address param isn't one for the requested currency and network, or is verified only on another network. Add it in your OpenFX dashboard (or ask Tesser support), then create the rebalance again; retrying before that won't help. Usually returned when the rebalance is created; if the registration changes before Tesser plans it, the rebalance fails instead, before any funds move, with this code as cause_code on its transfers-9113 status reason. In the sandbox, any verified address for the currency and network counts. If your organization has no OpenFX credentials stored, the request is rejected with openfx-1000 instead. |
treasury-3338 | 409 | The on-chain transaction was rejected because its nonce was already used by another transaction from this wallet. This rebalance is now in a failed state. You must create a new rebalance 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 rebalance cannot be retried — create a new rebalance, which is planned against a fresh nonce. |
treasury-3339 | 500 | The network refused the signed transaction, so the step failed, nothing was sent and its reserved funds were released. Create a new withdrawal or rebalance; 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 detail param and the step's status_reasons carry the network's reason. The step failed, nothing moved and the reserved balance is released. Create a new withdrawal or rebalance; signing the failed step again won't help. If it fails again, contact Tesser support with the detail. 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. |
treasury-3340 | 409 | The on-chain transaction was rejected because its nonce was already used by another transaction from this wallet. This withdrawal is now in a failed state. You must create a new withdrawal 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 withdrawal cannot be retried — create a new withdrawal, which is planned against a fresh nonce. |
treasury-3341 | 409 | This rebalance waited for earlier transfers from the same wallet to be submitted, but the wait expired. This rebalance is now in a failed state. You must create a new rebalance 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 rebalance is planned against a fresh nonce. |
treasury-3342 | 409 | This withdrawal waited for earlier transfers from the same wallet to be submitted, but the wait expired. This withdrawal is now in a failed state. You must create a new withdrawal 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 withdrawal is planned against a fresh nonce. |
treasury-3343 | 400 | A rebalance to the same account is a currency swap inside it, which only OpenFX and Kraken ledgers support, and this account isn't one. Choose a different destination account, or swap on an OpenFX or Kraken ledger, and send the request again; retrying won't help | A rebalance whose source and destination are the same account is a currency swap inside that account, which only OpenFX and Kraken ledgers support. Returned when the rebalance is created for any other account; the id and type params name it. Choose a different destination account, or swap on an OpenFX or Kraken ledger, and send the request again. Retrying the same request won't help. A rebalance from a Kraken ledger to another account it can't serve returns treasury-3356 instead. |
treasury-3344 | 400 | from_network is required when the source account is a wallet | Withdrawals from a stablecoin wallet must specify the blockchain network the funds leave from |
treasury-3345 | 400 | Deposit cannot be simulated because it is expired or no longer awaiting funds | The deposit expired before its funding receipt was simulated, or another receipt already completed it. A Kraken deposit that simulation already credited is returned unchanged instead of this error |
treasury-3346 | 400 | OpenFX doesn't accept deposits on this network, so a wallet on it can't be the source of an OpenFX withdrawal. Send from a wallet on a network OpenFX supports; retrying won't help | A withdrawal from a wallet through OpenFX moves the funds into OpenFX first, and OpenFX doesn't support the source wallet's network (Tempo). Choose a source wallet on a network OpenFX supports. Retrying the same request won't help. |
treasury-3347 | 400 | OpenFX doesn't accept deposits on this network, so a wallet on it can't rebalance into an OpenFX ledger. Send from a wallet on a network OpenFX supports; retrying won't help | A rebalance from a wallet into an OpenFX ledger moves the funds into OpenFX first, and OpenFX doesn't support the source wallet's network (Tempo). Choose a source wallet on a network OpenFX supports. Retrying the same request won't help. |
treasury-3348 | 422 | The destination address isn't a verified withdrawal address in the organization's Kraken account for this network, so Tesser can't withdraw to it from Kraken. Add and verify the address in Kraken, then send the request again | Kraken only withdraws to addresses that are whitelisted and verified in the organization's Kraken account for the USDC withdrawal method on that network. The destination has to match exactly one verified address, with no memo or tag. Add and verify the address in Kraken, then send the request again; retrying before that won't help. Also returned when the verified address or Kraken's withdrawal method changed after the transfer was planned. |
treasury-3349 | 400 | The amount is too small to withdraw from Kraken: it's below Kraken's USDC withdrawal minimum, or Kraken's withdrawal fee would take all of it. Send a larger amount; retrying the same amount won't help | Kraken has a minimum for each USDC withdrawal and takes its fee out of the amount. The amount was below that minimum, or nothing would be left after the fee. The error_message ends with Kraken's minimum. Send a larger amount; retrying the same amount won't help. |
treasury-3350 | 422 | Kraken's withdrawal quote doesn't fit this amount: with Kraken's current fee it would fall below Kraken's minimum, cost more than the funds available, or not deliver the exact amount needed. Kraken's fees change, so try again later or send a larger amount | Kraken prices each USDC withdrawal with its current fee. With that fee, the withdrawal would fall below Kraken's minimum, cost more than the funds available, or not deliver the exact amount the transfer needs. Kraken's fees change, so the same amount can work later; otherwise send a larger amount. The error_message ends with Kraken's minimum. |
treasury-3351 | 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 rebalance; 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 rebalance can't continue: create a new one. If it fails the same way again, contact Tesser support with the request_id. |
treasury-3352 | 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 withdrawal; 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 withdrawal can't continue: create a new one. If it fails the same way again, contact Tesser support with the request_id. |
treasury-3353 | 422 | Your workspace's Circle ledger, which deposits into this wallet go through, is no longer set up, so the deposit failed and nothing was sent. Contact Tesser support; retrying won't help until Tesser sets it up again | A deposit into a wallet through Circle routes the funds through your workspace's Circle ledger, which Tesser sets up when Circle is connected. The ledger was there when the deposit was created but was gone when Tesser planned it, so the deposit failed and nothing was sent. Contact Tesser support with the wallet id from the message; once the ledger is set up again, create a new deposit. Retrying won't help until then. |
treasury-3354 | 422 | The organization's Kraken account doesn't offer exactly one USDC withdrawal method on this network, so Tesser can't withdraw from Kraken to it. Enable USDC withdrawals on this network in Kraken, or contact Tesser support if they're enabled; retrying won't help until then | Tesser withdraws USDC from the organization's Kraken account with the Kraken withdrawal method for the destination network, matched on network, on-chain asset and token contract. Kraken listed no such method for the account, or more than one, so Tesser can't pick one. The error_message ends with the network and the number of matching methods. Enable USDC withdrawals on that network in the Kraken account, or contact Tesser support if they are enabled; retrying won't help until the account offers exactly one matching method. A rebalance fails at planning; a Kraken-funded payment's quote comes back unavailable, or the payment fails at planning. |
treasury-3355 | 503 | Tesser couldn't read the source bank account's stored details to build the wire instructions. This is a temporary problem at Tesser, not with the bank account: request the instructions again in a few minutes, and contact Tesser support if it keeps failing | The source bank account's details are stored, but Tesser couldn't read them when building the wire instructions. Nothing is wrong with the bank account or the deposit. Request the instructions again in a few minutes; contact Tesser support with the account id from the message if it keeps failing. |
treasury-3356 | 400 | A rebalance from a Kraken ledger can only swap currencies within that ledger or withdraw to a Tesser-managed wallet, and desired.to.account_id is neither. Change desired.to.account_id and send the request again; retrying won't help | From a Kraken ledger, Tesser supports a currency swap within the same ledger and a withdrawal to a Tesser-managed wallet. Any other destination, such as another Kraken ledger, another provider's ledger, a bank account or an external wallet, is rejected when the rebalance is created; the id and type params name it. Change desired.to.account_id and send the request again. Retrying the same request won't help. |
treasury-3357 | 502 | Tesser couldn't check whether the source bank account is registered in your OpenFX account, so the deposit failed before any funds moved; the account may well be registered. cause_code names the underlying error. Create a new deposit; contact Tesser support with the deposit id if it fails again | Planning only. Before planning a deposit from a bank account it hasn't matched to OpenFX yet, Tesser looks up the account's registration in your OpenFX account. The lookup failed: OpenFX refused it, or Tesser couldn't use OpenFX for it, for example because the OpenFX credentials stored for your organization are missing or were rejected. The deposit failed before any funds moved, and the account may well be registered. You see this code as cause_code on the deposit's transfers-9113 status reason; this message is its detail and ends with the cause_code of the underlying error. Create a new deposit; if it fails again, contact Tesser support with the deposit id. A lookup that times out or is rate-limited is retried automatically and doesn't return this code. |
treasury-3358 | 500 | Tesser has no amount or currency recorded for this step, so it can't accept the signature and nothing was sent. This is a fault at Tesser, not in the request or the signature. Contact Tesser support with the rebalance or withdrawal id; signing again won't help | Before accepting the signature for a rebalance or withdrawal step, Tesser checks the amount and currency it recorded for the step when it prepared the transaction. One of them is missing, which is a fault at Tesser. Nothing was signed or sent, and no balance was reserved. Contact Tesser support with the rebalance or withdrawal id and the step_id from the message; signing again won't help. |
treasury-3359 | 409 | This withdrawal passed its expires_at before any of its steps started, so Tesser refused this signature. A signature sent before expires_at may still go through, so create a new withdrawal only after you receive withdrawal.expired; signing again won't help | Returned when a signature arrives after the withdrawal's expires_at and none of its steps had started, whether or not Tesser has already expired it. Once a step has started, the withdrawal runs to its own outcome and a later step can still be signed. A step that was already signed, or that failed for another reason, returns treasury-3306 instead: fetch the withdrawal to check its status before creating another. The withdrawal then expires: its unstarted steps fail with transfers-9204, any funds held for it are released, and withdrawal.expired is sent if it hasn't been already. A signature sent before expires_at that is still being processed can win instead; the withdrawal then goes ahead and no withdrawal.expired is sent. Create a new withdrawal only after withdrawal.expired arrives; sending the signature again won't help. |
treasury-3360 | 409 | This rebalance passed its expires_at before any of its steps started, so Tesser refused this signature. A signature sent before expires_at may still go through, so create a new rebalance only after you receive rebalance.expired; signing again won't help | Returned when a signature arrives after the rebalance's expires_at and none of its steps had started, whether or not Tesser has already expired it. Once a step has started, the rebalance runs to its own outcome and a later step can still be signed. A step that was already signed, or that failed for another reason, returns treasury-3013 instead: fetch the rebalance to check its status before creating another. The rebalance then expires: its unstarted steps fail with transfers-9204, any funds held for it are released, and rebalance.expired is sent if it hasn't been already. A signature sent before expires_at that is still being processed can win instead; the rebalance then goes ahead and no rebalance.expired is sent. Create a new rebalance only after rebalance.expired arrives; sending the signature again won't help. |
Last modified on