Errors
Account Errors
Error codes with the accounts- prefix. See the
Errors overview for the response format and the code convention.
Accounts
| Error Code | HTTP Status | Error Message | Description |
|---|---|---|---|
accounts-1000 | 404 | Account not found | The specified account ID does not exist in this workspace |
accounts-1001 | 404 | Entity not found | The tenant or counterparty specified does not exist |
accounts-2000 | 403 | The entity does not belong to your workspace | User tries to link an account to an entity that belongs to a different workspace |
accounts-3000 | 400 | Cannot provide both tenant_id and counterparty_id | User provides both tenant_id and counterparty_id when only one is allowed |
accounts-3001 | 400 | A workspace-level bank account already exists. Only one is allowed per workspace. | User tries to create a second workspace-level bank account |
accounts-3002 | 400 | wallet_address is required for unmanaged wallets (is_managed=false) | User creates an unmanaged wallet without providing a wallet_address |
accounts-3003 | 500 | Tesser can't tell which network this wallet type is on, so it didn't create the wallet. This is a fault at Tesser, not in the request: contact Tesser support; retrying won't help | Tesser maps every wallet type it accepts to a network. Returned when an unmanaged wallet's type has no network in that map, which means Tesser's configuration is incomplete: type is checked first, and a type Tesser doesn't accept returns accounts-3107 instead. Nothing was created. Contact Tesser support with the type from the message; retrying won't help. |
accounts-3004 | 400 | signature is required for managed wallets (is_managed=true) | User creates a managed wallet without providing the required signature |
accounts-3005 | 400 | Invalid signature format. Expected base64-encoded JSON with body and stamp fields. | The signature parameter could not be decoded or is missing required fields |
accounts-3006 | 400 | Circle Mint ledgers require a tenant_id or counterparty_id. Workspace-level sub-ledgers are not supported. | User tries to create a Circle Mint ledger without linking it to a tenant or counterparty |
accounts-3007 | 409 | This tenant or counterparty already has a Circle Mint ledger, and each can have only one, so no ledger was created. Use the existing ledger; retrying won't help | Each tenant and each counterparty can have one Circle Mint ledger. The tenant_id or counterparty_id in the request already has one, so nothing was created and nothing was sent to Circle. Use the existing ledger, whose id is at the end of the error_message. Retrying won't help. A second OpenFX ledger in a workspace gets accounts-3127 instead. |
accounts-3008 | 400 | A workspace-level Circle Mint master wallet ledger already exists. | User tries to create a second master wallet ledger for the workspace |
accounts-3009 | 400 | CIRCLE_MINT provider requires a tenant_id or counterparty_id | Circle Mint metadata preparation requires an entity to be linked |
accounts-3010 | 400 | CIRCLE_MINT provider requires a business entity (not individual) | Circle Mint only supports business-classified entities, not individuals |
accounts-3011 | 422 | The ledger's owner is missing business details that Circle needs, listed in missing_fields, so Tesser didn't create the Circle ledger. Tenants and counterparties can't be updated through the API: contact Tesser support to add them, or use an owner that has them; retrying won't help | A Circle ledger's owner must be a business with a legal name, country, legal entity identifier, state and city. Returned when you create a Circle ledger and the tenant or counterparty lacks some of them; missing_fields lists them by their API field names. Nothing is created at Circle. Tenants and counterparties can't be updated through the API, so contact Tesser support to add the details, or create the ledger for an owner that has them. Retrying won't help. When Tesser has the details but can't read them, accounts-5003 is returned instead. |
accounts-3012 | 422 | Circle hasn't approved this ledger, so Tesser can't set up its wire deposit instructions yet; its compliance state is in the message. If it's PENDING, try again after Circle approves it; otherwise contact Tesser support | Circle has to accept a ledger in its compliance review before Tesser can set up the ledger's wire deposit instructions, which Tesser does the first time it plans a deposit into the ledger or records a Circle deposit into it. Returned when the ledger's compliance_state isn't ACCEPTED at that moment: PENDING while Circle reviews it, REJECTED if Circle declined it. A deposit into a ledger Circle hasn't approved is normally refused with treasury-3103, which carries the same guidance. If the state is PENDING, try again after Circle approves the ledger; if it's REJECTED, or stays PENDING longer than expected, contact Tesser support with the account id. |
accounts-3013 | 500 | Tesser can't find the Circle wallet behind this ledger, so it can't set up the ledger's wire deposit instructions. Contact Tesser support; retrying won't help until Tesser fixes the ledger | Tesser records a Circle ledger's Circle wallet when Circle approves the ledger, and needs it to set up the ledger's wire deposit instructions for a deposit. Returned when the ledger is approved but Tesser has no Circle wallet for it, a fault in Tesser's setup of the ledger. Contact Tesser support with the account id from the message; retrying won't help until Tesser fixes the ledger. |
accounts-3014 | 422 | Your workspace has no workspace-level bank account, which Circle wires need. Create a bank account without tenant_id or counterparty_id, then send a new request; retrying won't help until then | Circle wires, for deposits through Circle and for withdrawals Circle pays out to a bank, go through your workspace-level bank account: the bank account created without tenant_id or counterparty_id. Returned when the workspace has none. A withdrawal that runs into this fails at its payout step, before Tesser asks Circle to pay out, so no funds move; the step's status_reasons carry transfers-9301 with this message as the detail. Create the workspace-level bank account, then create a new withdrawal; retrying won't help until it exists. |
accounts-3015 | 422 | Your Circle account has no wire bank account registered, so Tesser can't use Circle wires for this workspace. Register one in Circle or contact Tesser support; retrying won't help until then | Circle sends and receives wires only through a wire bank account registered in your Circle account, and Tesser uses it for deposits through Circle and for withdrawals Circle pays out to a bank. Returned when Circle lists none. A withdrawal that runs into this fails at its payout step, before Tesser asks Circle to pay out, so no funds move; the step's status_reasons carry transfers-9301 with this message as the detail. Register a wire bank account in Circle, or contact Tesser support, then create a new withdrawal; retrying won't help until one is registered. |
accounts-3016 | 422 | Your Circle account has more than one wire bank account, and Tesser needs exactly one for Circle wires. Remove the extras or contact Tesser support; retrying won't help until then | In production Tesser uses the one wire bank account registered in your Circle account for deposits through Circle and for withdrawals Circle pays out to a bank. Returned when Circle lists more than one and Tesser hasn't recorded which to use; count gives how many. The sandbox uses the first one instead. A withdrawal that runs into this fails at its payout step, before Tesser asks Circle to pay out, so no funds move; the step's status_reasons carry transfers-9301 with this message as the detail. Remove the extra wire bank accounts in Circle, or contact Tesser support, then create a new withdrawal; retrying won't help until then. |
accounts-3017 | 502 | Circle listed a wire bank account without an id, so Tesser can't use it for Circle wires. This is a problem at Circle: contact Tesser support; retrying won't help until Circle's record is fixed | Tesser uses the wire bank account registered in your Circle account for deposits through Circle and for withdrawals Circle pays out to a bank. Returned when Circle's record of that account has no id, a fault at Circle. A withdrawal that runs into this fails at its payout step, before Tesser asks Circle to pay out, so no funds move; the step's status_reasons carry transfers-9301 with this message as the detail. Contact Tesser support, and create a new withdrawal once Circle's record is fixed; retrying before that won't help. |
accounts-3020 | 400 | Entity type must be 'counterparty' or 'tenant' | The referenced entity is not a valid type for account linking |
accounts-3022 | 400 | Signature body has unexpected activity type | The stamped Turnkey activity inside the signature is not the expected CREATE_WALLET or CREATE_WALLET_ACCOUNTS activity |
accounts-3023 | 400 | The signed request's organizationId isn't this workspace's Turnkey organization, so no wallet was created. Sign the request again for this workspace's Turnkey organization and send it; resending the same signature won't help | A managed wallet request is stamped for a Turnkey organization, and it must be the organization of the workspace that the API key or dashboard session belongs to. The organizationId in the signed body is another one, for example when the request was stamped in another workspace's Turnkey session or with another workspace's key, or after switching workspaces in the dashboard. Nothing was sent to Turnkey and no wallet was created. Stamp the request again for this workspace's Turnkey organization (with the SDK, request a new unsigned payload) and send it. Resending the same signature won't help. When Tesser has no Turnkey organization on record for the workspace, accounts-3128 is returned instead. |
accounts-3024 | 400 | Signed wallet account addressFormat does not match the wallet type | The stamped CREATE_WALLET parameters describe an address format that does not match the dto.type |
accounts-3025 | 400 | Managed wallets are only supported for type 'stablecoin_ethereum' | User attempted to create a managed (is_managed=true) wallet for a non-Ethereum wallet type |
accounts-3026 | 409 | Capa returned a deposit account for this payment that Tesser has on record for a different owner, so Tesser didn't set the payment's accounts. Capa may already have created the order: don't send funds for it. Contact Tesser support with the payment id; retrying won't help | When you update a cross-ramp payment with its accounts, Tesser creates the order at Capa and records the MXN deposit account Capa returns for the originator. Returned when Tesser already has that deposit account on record for a different tenant or counterparty in your workspace. Tesser stops rather than point the payment's deposit at another owner's account, so the payment's accounts aren't set, although Capa may already have created the order. Don't send funds for the payment. Contact Tesser support with the payment id; only Tesser can resolve this with Capa, and retrying won't help. |
accounts-3027 | 400 | Generic accounts require a tenant_id or counterparty_id | User creates a generic account without linking it to a tenant or counterparty. A generic account identifies an account held by exactly one owner. |
accounts-3028 | 409 | A generic account with this generic_account_number already exists for this owner | The owner already has a generic account with the same generic_account_number, created by the customer or by Tesser from a travel-rule inbound. The message names the existing account's id; use that account instead. |
accounts-3029 | 400 | Account is a generic account and cannot send or receive funds | User passes a generic account as the source or destination of a payment, deposit, withdrawal or rebalance, or requests an on-chain address for it. A generic account has no network, currency or balance, so it can only be a payment's funding_account_id. |
accounts-3030 | 400 | The signed request adds the account to a wallet other than this workspace's master wallet, so no wallet was created. Request a new unsigned payload, sign its body and send it; resending the same signature won't help | A managed wallet account created on the master wallet (ACTIVITY_TYPE_CREATE_WALLET_ACCOUNTS) must be added to the workspace's master wallet, whose id the unsigned payload returns as master_wallet_id. The signed walletId is another wallet, or the body was signed without fetching an unsigned payload while the workspace had no master wallet on record yet (expected then reads <unset>); fetching the unsigned payload records it. The error_message ends with the expected and the signed walletId. Nothing was sent to Turnkey. Request a new unsigned payload, sign its body unchanged and send it. Resending the same signature won't help. |
accounts-3031 | 409 | A wallet with this name is already linked to a different account | The Turnkey wallet with this name already exists and is linked to an account with a different tenant, counterparty or wallet type. Use a different wallet name. |
accounts-3033 | 409 | This wallet name is reserved by another account in this workspace, so Tesser didn't create the wallet. Use a different name; retrying with this one won't help | With SDK 0.1.0 and later, a managed wallet's address is derived from its name, so a name stays reserved for the account first created with it, even after that account is renamed. Returned when another account in this workspace holds the address for this name under a different name; account_id names that account. Use a different name; retrying with this one won't help. |
accounts-3035 | 409 | The workspace has reached the wallet provider's limit on wallets. Contact Tesser support | The wallet provider refused to create another wallet because the workspace holds the maximum number of wallets. Retrying the request does not help; contact Tesser support. |
accounts-3100 | 400 | account_name is required and must be between 1-255 characters | User provides an account name that doesn't meet length requirements |
accounts-3101 | 400 | tenant_id must be a valid UUID | User provides a tenant_id that is not a valid UUID |
accounts-3102 | 400 | counterparty_id must be a valid UUID | User provides a counterparty_id that is not a valid UUID |
accounts-3103 | 400 | bank_name is required and must be between 1-255 characters | User provides a bank name that doesn't meet length requirements |
accounts-3104 | 400 | bank_code_type must be one of: SWIFT, BIC, IBAN, ROUTING | User provides a bank_code_type that is not in the allowed enum |
accounts-3105 | 400 | bank_identifier_code is required | User creates a bank account without providing the bank identifier code |
accounts-3106 | 400 | bank_account_number is required | User creates a bank account without providing the account number |
accounts-3107 | 400 | type is missing or isn't a supported account type. A wallet takes stablecoin_ethereum, stablecoin_solana or stablecoin_stellar, and listing accounts also takes fiat_bank, ledger or generic. Correct type and send the request again; retrying won't help | Returned when type isn't one Tesser accepts for the request. Creating a wallet requires type, one of stablecoin_ethereum, stablecoin_solana or stablecoin_stellar. Listing accounts takes type as an optional filter that also accepts fiat_bank, ledger and generic. Correct type and send the request again; retrying the same request won't help. |
accounts-3108 | 400 | wallet_address must be a valid blockchain address for the specified network | User provides a wallet address that doesn't match the expected format for the network |
accounts-3109 | 400 | Wallet signature is malformed or invalid | User provides a signature that is not properly formatted or cannot be verified |
accounts-3110 | 400 | provider is missing or isn't a supported ledger provider. A new ledger takes CIRCLE_MINT or OPENFX; Tesser creates Kraken ledgers itself when Kraken is connected. Correct provider and send the request again; retrying won't help | Creating a ledger requires provider, either CIRCLE_MINT or OPENFX. Returned when it's missing or has any other value. Kraken ledgers can't be created with this request: Tesser creates your organization's Kraken ledger when Kraken is connected, so contact Tesser support for one. Correct provider and send the request again; retrying the same request won't help. |
accounts-3111 | 400 | This account can't have an on-chain deposit address: only Circle ledgers and Kraken ledgers support one. Use one of those accounts; retrying won't help | On-chain deposit addresses exist only for Circle ledgers and Kraken ledgers. Returned when you request one for any other account, such as a bank account, a wallet or an OpenFX ledger; a generic account returns accounts-3029 instead. Request the address for a Circle or Kraken ledger; retrying won't help. |
accounts-3112 | 422 | Circle hasn't approved this ledger in its compliance review, so it can't get an on-chain deposit address yet; its compliance state is in the message. If it's PENDING, send the request again after Circle approves the ledger; otherwise contact Tesser support | A Circle Mint ledger gets on-chain deposit addresses only after Circle accepts it in its compliance review, and Tesser picks up Circle's decision automatically. The error_message ends with the ledger id and its state: PENDING while Circle reviews it, REJECTED if Circle declined it, or none if Tesser has no review state for it. Nothing was created. If pending, send the request again after Circle approves the ledger; retrying before that won't help. If rejected, none, or pending for longer than expected, contact Tesser support with the ledger id. When the ledger is approved but Tesser has no Circle wallet on record for it, accounts-3129 is returned instead. |
accounts-3113 | 400 | network is not supported for on-chain deposit addresses | User requests an on-chain deposit address on a network the ledger provider does not support in this environment |
accounts-3114 | 400 | account has too many transfers to sort by amount | Dashboard user sorts an account's activity by amount when the account has more transfers than the amount sort reads |
accounts-3115 | 400 | Signed wallet account path must be m/44'/60'/<account>'/0/<address> with both indexes below 2^31 | The stamped CREATE_WALLET_ACCOUNTS activity carries a derivation path that is not in the master wallet format |
accounts-3116 | 400 | The signature was made for a different wallet name than this request's name, so Tesser didn't create the wallet. Sign again with signCreateWallet using exactly this request's name and type, then send the request; resending this signature won't help | With SDK 0.1.0 and later, signCreateWallet signs a derivation path that Tesser derives from the wallet name. Returned when the signed path doesn't match the name in the request, for example because the name changed after signing; expected and actual are the two paths. Sign again with signCreateWallet using exactly the request's name and type, then send the request; resending the same signature won't help. |
accounts-3117 | 400 | The signed wallet request doesn't have the parameters Tesser expects, and reason says which, so Tesser didn't create the wallet. Sign again with signCreateWallet using exactly this request's name and type, then send the request; resending this signature won't help | signCreateWallet signs the request Tesser prepares: one Ethereum account, with the request's name, on your workspace's wallet. Returned when the signed parameters differ, for example extra parameters, more than one account, another key type or path format, or an account name that isn't the request's; reason names the difference. Sign again with signCreateWallet using exactly the request's name and type, then send the request; resending the same signature won't help. If a signature from signCreateWallet still fails, contact Tesser support. |
accounts-3118 | 400 | search isn't a valid filter for listing accounts: send it once, with at most 200 characters and no control characters. Fix it and send the request again; retrying won't help | search takes one text value of at most 200 characters, without control characters such as line breaks. Returned when it's longer, contains control characters, or is sent more than once; the message ends with the problem or the values sent. Fix search and send the request again; retrying the same request won't help. |
accounts-3119 | 400 | start_date or end_date isn't a valid date for listing accounts: send each once, as YYYY-MM-DD or a UTC date-time such as 2026-01-31T09:30:00Z. Fix it and send the request again; retrying won't help | start_date and end_date each take one value: a calendar date in YYYY-MM-DD format, covering the whole UTC day, or a UTC date-time in YYYY-MM-DDTHH:mm |
accounts-3120 | 400 | start_date is later than end_date in this accounts list filter. Send a start_date at or before end_date; retrying won't help | Returned when start_date falls after end_date. Tesser compares instants: a date-only start_date means 00:00:00.000Z on that day and a date-only end_date means 23:59:59.999Z, so equal dates are valid. Send a start_date at or before end_date; retrying the same request won't help. |
accounts-3121 | 400 | belongs_to isn't a valid owner filter for listing accounts: it takes up to 100 comma-separated tenant ids or the value workspace. Fix it and send the request again; retrying won't help | belongs_to takes up to 100 comma-separated owners, each a tenant id (a UUID) or the literal workspace for the workspace's own accounts. Returned when a value is neither, or when there are more than 100; the message ends with the invalid values or the problem. Fix belongs_to and send the request again; retrying the same request won't help. |
accounts-3122 | 400 | currency isn't a valid filter for listing accounts: send it once, as a currency code of at most 64 characters with no control characters, and one Tesser knows when you also filter by amount. Fix it and send the request again; retrying won't help | currency takes one currency code, such as USDC, of at most 64 characters and without control characters. Returned when it's longer, contains control characters, or is sent more than once, and when it's a code Tesser doesn't know while amount_min or amount_max is set; on its own, an unknown code matches no accounts. Fix currency and send the request again; retrying the same request won't help. |
accounts-3123 | 400 | amount_min or amount_max isn't a valid amount for listing accounts. Send each amount once, as a non-negative decimal in major units of currency. Fix it and send the request again; retrying won't help | amount_min and amount_max each take one non-negative decimal number with at most 30 integer and 18 fraction digits, in major units of currency. Returned when an amount isn't such a number or is sent more than once; the message ends with the value that failed. Fix it and send the request again; retrying the same request won't help. A currency Tesser doesn't know returns accounts-3122. |
accounts-3124 | 400 | amount_min and amount_max need currency, because amounts are in that currency's major units. Add currency and send the request again; retrying without it won't help | Returned when listing accounts with amount_min or amount_max but no currency. Amounts are compared in major units of currency, so it's required with either. Add currency and send the request again; retrying without it won't help. |
accounts-3125 | 400 | amount_min is greater than amount_max in this accounts list filter. Send an amount_min at or below amount_max; retrying won't help | Returned when amount_min is greater than amount_max. Equal amounts are valid. Send an amount_min at or below amount_max; retrying the same request won't help. |
accounts-3126 | 400 | network isn't a valid filter for listing accounts: send it once, as up to 50 comma-separated network keys Tesser supports. Fix it and send the request again; retrying won't help | network takes up to 50 comma-separated network keys, such as BASE or POLYGON, each one Tesser supports. Returned when a key is unknown, there are more than 50, or network is sent more than once; the message ends with the unknown keys or the problem. Fix network and send the request again; retrying the same request won't help. |
accounts-3127 | 409 | This workspace already has an OpenFX ledger, and a workspace can have only one, so no ledger was created. Use the existing ledger; retrying won't help | A workspace has one OpenFX ledger, which Tesser creates when the organization's OpenFX credentials are stored with POST /v1/organizations/secrets. Creating another with POST /v1/accounts/ledgers and provider OPENFX is refused: nothing was created and nothing was sent to OpenFX. Use the existing ledger, whose id is at the end of the error_message. Retrying won't help. Storing OpenFX credentials returns this code too when the workspace still has its OpenFX ledger; the credentials aren't saved, so contact Tesser support. |
accounts-3128 | 422 | Tesser hasn't finished setting up managed wallets for this workspace in Turnkey, so it can't create managed wallets for it yet. This isn't a problem with your request or signature. Contact Tesser support; retrying won't help until Tesser sets it up | Managed wallets live in the workspace's Turnkey organization, which Tesser sets up with a first wallet when the workspace is created; new managed wallet accounts are added to that wallet. For this workspace Tesser has no Turnkey organization on record, or the organization holds no wallet. Returned when you create a managed wallet with POST /v1/accounts/wallets, or when the SDK requests the unsigned payload for one. Nothing was created. Contact Tesser support; retrying won't help until Tesser finishes the setup. |
accounts-3129 | 422 | Circle approved this ledger, but Tesser has no Circle wallet on record for it, so it can't create an on-chain deposit address. This isn't a problem with your request. Contact Tesser support; retrying won't help until Tesser fixes the ledger | An on-chain deposit address for a Circle Mint ledger is created in the ledger's Circle wallet, which Circle assigns and Tesser records when Circle accepts the ledger. The ledger is accepted, but Tesser has no Circle wallet on record for it. Nothing was created. Contact Tesser support with the ledger id from the message; retrying won't help until Tesser fixes the ledger's setup. |
accounts-3130 | 400 | Turnkey refused the signed wallet request, so no wallet was created. Sign a new request and send it; resending the same signature won't help. Contact Tesser support if a new signature is refused too | Tesser forwards the signed create_wallet or create_wallet_accounts request to Turnkey unchanged. Turnkey refused it, or accepted it and then failed it: usually the stamp doesn't cover the exact body, the signing key isn't an active API key of the workspace's Turnkey organization, the body is incomplete (for example it has no wallet name), or a Turnkey policy denied it. The error_message ends with Turnkey's status and reason. No wallet was created. Sign a new request (with the SDK, request a new unsigned payload first) and send it. Resending the same signature won't help. Contact Tesser support with the request_id if a new signature is refused too. |
accounts-4290 | 429 | Too many wallet creation requests. Retry shortly | The wallet provider rate limited the wallet creation or the lookup of an existing wallet. Retry the same request after a short delay. |
accounts-5000 | 502 | Turnkey didn't confirm the wallet creation, so Tesser can't tell whether the wallet was created. Send the same request again with the same name: Tesser links the wallet if Turnkey created it. Contact Tesser support if it keeps failing | Tesser forwards the signed request to Turnkey, which creates the wallet or wallet account. Turnkey failed or timed out, its answer couldn't be read, it held the activity for approval, or it reported the wallet name as taken but Tesser couldn't find that wallet. The wallet may have been created. Send the same request again with the same name: if Turnkey created the wallet, Tesser links it to the account instead of creating a second one. Contact Tesser support with the request_id if it keeps failing. When Turnkey refuses the signed request, accounts-3130 is returned instead. |
accounts-5001 | 502 | Circle refused or failed to register this ledger's owner, so Tesser didn't create the Circle ledger; reason gives Circle's answer. Retry after a short delay; if it fails again, contact Tesser support | Creating a Circle ledger registers its owner with Circle as a business. Returned when Circle refuses that registration, for example because it rejects the owner's details, or fails to answer. Tesser creates no ledger. Circle may have registered the owner anyway, and Tesser reuses that registration on a retry, so retrying is safe. The reason param carries Circle's answer. Retry after a short delay; if it fails again, contact Tesser support with the tenant or counterparty id. When Circle Mint isn't connected for the organization, circle-1000 or circle-1001 is returned instead, and circle-4290 when Circle rate limits the request. |
accounts-5002 | 502 | Tesser couldn't set up the wire deposit instructions for this Circle ledger: Circle didn't return them, the ledger changed meanwhile, or Tesser couldn't save them. Retry after a short delay; contact Tesser support if it keeps failing | Tesser sets up a Circle ledger's wire deposit instructions the first time it plans a deposit into the ledger, or records a Circle deposit into it. Returned when that fails: Circle didn't return the instructions, the ledger's Circle wallet changed while Tesser was fetching them, or Tesser couldn't save them. Setting them up again is safe, because Tesser reuses instructions it already saved. Retry after a short delay; if it keeps failing, contact Tesser support with the account id. |
accounts-5003 | 502 | Tesser couldn't read the stored business details of the ledger's owner, so it didn't create the Circle ledger. This is a fault at Tesser: retry after a short delay, and contact Tesser support if it keeps failing | Creating a Circle ledger reads the owner's stored business details, such as the address and legal entity identifier, to register the owner with Circle. Returned when Tesser couldn't read them. This happens before anything is sent to Circle, so nothing was created and retrying is safe. Retry after a short delay; if it keeps failing, contact Tesser support. |
accounts-5004 | 502 | Tesser couldn't get an on-chain deposit address for this account from its provider. Retry after a short delay: if the provider created the address meanwhile, Tesser returns it. Contact Tesser support if it keeps failing | Tesser gets a Circle or Kraken ledger's on-chain deposit address from the provider, creating it there if it doesn't exist yet. Returned when the provider call fails or times out, or Tesser can't save the result. The provider may have created the address anyway; requesting it again is safe, because Tesser returns an existing address instead of creating another. Retry after a short delay; if it keeps failing, contact Tesser support with the account id. |
accounts-5030 | 503 | The wallet is still being created. Retry the same request with the same wallet name | The wallet provider accepted the wallet creation but had not finished it when Tesser stopped waiting. Retry with the same wallet name to receive the account once the wallet exists. |
Last modified on