# Provider Errors

{/* AUTO-GENERATED - DO NOT EDIT. Run: bun run apps/gateway/docs/scripts/generate-error-docs.ts */}

Error codes with the `circle-`, `capa-`, `kraken-`, `openfx-`, and `zuba-` prefixes. See the
[Errors overview](/overviews/errors) for the response format and the code convention.

## Circle

<table className="wrap-first-col error-table">
  <thead>
    <tr>
      <th>Error Code</th>
      <th>HTTP Status</th>
      <th>Error Message</th>
      <th>Description</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>`circle-1000`</td>
      <td>422</td>
      <td>Circle Mint isn't connected for this workspace's organization: Tesser has no Circle Mint API key for it, so Tesser can't use Circle Mint for this request. Contact Tesser support to connect it; retrying won't help until then</td>
      <td>Tesser uses your organization's own Circle Mint account, through an API key that Tesser stores for it. Returned when you create a Circle ledger, or a deposit, withdrawal, rebalance or payment that has to go through Circle Mint, and no key is stored, so no other provider can take the request. When other providers also refuse the request, their reasons come first. Contact Tesser support to connect Circle Mint; retrying won't help until then. A key that's stored but can't be loaded returns circle-1001 instead.</td>
    </tr>
    <tr>
      <td>`circle-1001`</td>
      <td>503</td>
      <td>Tesser couldn't load the Circle Mint API key it stores for your organization, so it couldn't call Circle Mint. This isn't a problem with your request. Contact Tesser support; retrying won't help until Tesser restores the key</td>
      <td>Tesser calls Circle Mint with the API key it stores for your organization. Returned when the key is on file but Tesser can't load it, on any request that calls Circle Mint for your workspace. Tesser doesn't fail a transfer step for it. Contact Tesser support with the request_id or the payment id; retrying won't help until Tesser restores the key. A workspace with no Circle Mint key at all gets circle-1000 instead.</td>
    </tr>
    <tr>
      <td>`circle-4290`</td>
      <td>429</td>
      <td>Circle Mint is rate limiting calls made with your organization's Circle Mint API key, so it refused this request. Wait a short while and send it again</td>
      <td>Circle Mint limits how many requests each API key can make, and Tesser calls it with your organization's key. Returned when Circle Mint refuses a request with its rate-limit response. Wait a short while and send the request again. When a transfer step hits it, Tesser retries the step on its own.</td>
    </tr>
  </tbody>
</table>

## Capa

<table className="wrap-first-col error-table">
  <thead>
    <tr>
      <th>Error Code</th>
      <th>HTTP Status</th>
      <th>Error Message</th>
      <th>Description</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>`capa-1000`</td>
      <td>422</td>
      <td>Capa has no record of the user or quote Tesser sent for this payment, so Capa created no order. This isn't a problem with your request. Contact Tesser support with the payment id; retrying won't help</td>
      <td>Returned when you accept a cross-ramp payment's quote (the PATCH that attaches its accounts) and Capa answers that it doesn't know the originator's Capa user or the quote Tesser sent. Capa created no order, so no funds are due, and the payment's first step fails with transfers-9301 carrying this code. This points to a mismatch between Tesser's records and Capa's, not to a problem with the request. Contact Tesser support with the payment id; retrying or creating the same payment again won't help until Tesser fixes it. When Capa can't quote the currency pair at all, the payment fails with capa-3004 instead.</td>
    </tr>
    <tr>
      <td>`capa-2000`</td>
      <td>503</td>
      <td>Capa rejected the credentials Tesser uses for this operation, so Tesser can't reach Capa. This isn't a problem with your API key. Contact Tesser support; retrying won't help until Tesser fixes the credentials</td>
      <td>Capa refused Tesser's partner credentials: the key is invalid, or Tesser's partner account isn't enabled for this operation. Tesser has to fix it: contact Tesser support and quote the request_id. The same request fails until then. When it happens while a quote is accepted, the payment step fails and Capa creates no order.</td>
    </tr>
    <tr>
      <td>`capa-3000`</td>
      <td>400</td>
      <td>Capa rejected the request Tesser sent for this payment as invalid, so Capa created nothing and the payment failed. Check the payment's amount and the beneficiary's bank account details, then create a new payment; contact Tesser support if they're correct. Retrying this payment won't help</td>
      <td>Capa refused a request Tesser built from the payment as invalid. Returned in the failed step's status_reasons when Capa refuses the quote after you create a cross-ramp payment, and as the response when Capa refuses the order while you accept the quote; the payment's first step then fails with transfers-9301 and Capa creates no order. The detail param carries Capa's reason when it gives one. Check the payment's amount and the beneficiary's bank account (account and routing numbers, holder name and address), then create a new payment; retrying the same payment won't help. If the details are correct, contact Tesser support with the payment id. An amount Capa can't quote returns capa-3001 instead, and a beneficiary bank account Capa can't register returns capa-3003.</td>
    </tr>
    <tr>
      <td>`capa-3001`</td>
      <td>422</td>
      <td>Capa couldn't quote this amount, which usually means it's above the most Capa converts in one payment. The payment failed: create a new payment for a smaller amount; retrying this one won't help</td>
      <td>Tesser asks Capa for a quote after you create a cross-ramp payment. Returned in the failed step's status_reasons when Capa refuses to quote the amount in the way it does for amounts outside its range; this has been seen near USD 1,000,000, and Capa doesn't publish the exact limit. The payment fails and payment.updated is sent. Create a new payment for a smaller amount; retrying the same payment won't help. Capa's other quote refusals return capa-3000.</td>
    </tr>
    <tr>
      <td>`capa-3002`</td>
      <td>400</td>
      <td>Capa refused the cross-ramp because its quote expired</td>
      <td>Capa rejected the cross-ramp create with its documented QUOTE_EXPIRED code: the ~10s quote lapsed before Capa processed the order, so no order was created.</td>
    </tr>
    <tr>
      <td>`capa-3003`</td>
      <td>400</td>
      <td>The provider rejected the beneficiary bank account</td>
      <td>The cross-ramp provider could not register the beneficiary's bank account (account and routing numbers, account holder, or address) under the originator, so no order was created.</td>
    </tr>
    <tr>
      <td>`capa-3004`</td>
      <td>422</td>
      <td>Capa can't quote this currency pair for Tesser, so the payment couldn't be quoted and no funds are due. This isn't a problem with your request. Contact Tesser support with the payment id; creating the same payment again won't help until Tesser fixes it</td>
      <td>When you create a cross-ramp payment (MXN to USD), Tesser asks Capa for a quote. Capa answered that it doesn't offer the currency pair or payout route for Tesser's Capa account, so the payment failed before it was quoted. The payment's first step carries this code in its status_reasons. This is a setup problem between Tesser and Capa, not a problem with the request. Contact Tesser support with the payment id; creating the same payment again won't help until Tesser fixes it.</td>
    </tr>
    <tr>
      <td>`capa-4290`</td>
      <td>429</td>
      <td>Capa rate limited the request</td>
      <td>Capa returned a 429 rate-limit response.</td>
    </tr>
    <tr>
      <td>`capa-5000`</td>
      <td>502</td>
      <td>Capa answered, but Tesser couldn't read the answer, so Tesser doesn't know whether Capa acted on it. Don't accept the quote again or create a new payment yet: check the payment's status first, and contact Tesser support with the payment id if it isn't resolved</td>
      <td>Capa answered with a response that doesn't match what Capa documents, for example a success with no data or a quote for a different amount, so Tesser didn't use it. When it happens while Tesser requests a quote, Tesser retries on its own and you don't see it. When it's returned while you accept a quote, Capa may have created the order: the payment isn't failed, so check its status before you accept again or create a new payment. Contact Tesser support with the payment id if it isn't resolved.</td>
    </tr>
    <tr>
      <td>`capa-5030`</td>
      <td>502</td>
      <td>Tesser couldn't get an answer from Capa: Capa didn't respond in time, returned a server error, or was still processing the request. Capa may have acted on it, so the outcome is unknown. Don't accept the quote again or create a new payment yet: check the payment's status first, and contact Tesser support with the payment id if it isn't resolved</td>
      <td>Capa didn't respond within Tesser's time limit, the connection failed, or Capa answered with a server error or said it was still processing the request. When it happens while Tesser requests a quote, Tesser retries on its own and you don't see it. When it's returned while you accept a quote, Capa may have created the order: the payment isn't failed, so check its status before you accept again or create a new payment, and contact Tesser support with the payment id if it isn't resolved.</td>
    </tr>
  </tbody>
</table>

## Kraken

<table className="wrap-first-col error-table">
  <thead>
    <tr>
      <th>Error Code</th>
      <th>HTTP Status</th>
      <th>Error Message</th>
      <th>Description</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>`kraken-0000`</td>
      <td>500</td>
      <td>Tesser's records for this workspace's Kraken connection don't agree with each other, so Tesser stopped this request. This isn't a problem with your request or your Kraken account. Contact Tesser support to repair them; retrying won't help until then</td>
      <td>Tesser keeps one Kraken ledger per connected Kraken account and checks its records before it uses them. Returned when those records conflict: you connect Kraken (POST /v1/organizations/secrets) while the workspace already has a Kraken ledger without stored credentials, or while another request is connecting it; Tesser finds the same Kraken account behind two ledgers, or a ledger without its Kraken settings, while it creates a deposit address for a Kraken ledger; or, in the sandbox, the simulated Kraken ledger's records don't match. Contact Tesser support with the workspace or account id; retrying won't help until Tesser repairs the records.</td>
    </tr>
    <tr>
      <td>`kraken-0001`</td>
      <td>500</td>
      <td>Tesser's records for this step, which moves USDC from a wallet into Kraken, don't match the step's plan, so Tesser stopped. This is a fault at Tesser, not in your request. Contact Tesser support with the step id; retrying won't help until Tesser fixes the records</td>
      <td>A rebalance from a wallet into a Kraken ledger moves USDC in a step that Tesser plans in advance. Before it signs, sends or settles the step, Tesser checks the step against that plan: its amounts, currency and network, the wallet and Kraken ledger it moves between, and the deposit address. Returned when they no longer match, for example because the step's accounts changed or belong to another workspace. A request that submits the step's signature returns it, and the step isn't sent. This is a fault at Tesser. Contact Tesser support with the step_id; retrying won't help until Tesser fixes the records.</td>
    </tr>
    <tr>
      <td>`kraken-1001`</td>
      <td>422</td>
      <td>Tesser has no Kraken API key on file for this workspace's organization, so it can't use the workspace's Kraken ledger. Contact Tesser support; retrying won't help until Tesser restores the key</td>
      <td>Tesser calls Kraken with the API key your organization registered when it connected Kraken. Returned when no key is on file while a request needs the workspace's Kraken ledger: when you create a deposit or rebalance through it, or a deposit address for it. Connecting Kraken again doesn't work while the ledger exists. Contact Tesser support; retrying won't help until Tesser restores the key. A key that's on file but can't be loaded returns kraken-5037 instead.</td>
    </tr>
    <tr>
      <td>`kraken-2000`</td>
      <td>503</td>
      <td>Kraken rejected the API key or secret your organization registered for Kraken, so Tesser can't call Kraken with it. Check that the key is still active in your Kraken account, or contact Tesser support to replace it; retrying won't help until then</td>
      <td>Tesser calls Kraken with the API key and secret your organization registered when it connected Kraken (POST /v1/organizations/secrets). Returned when Kraken refuses them, for example because the key was deleted or disabled in Kraken or the secret doesn't match. When it happens while you connect Kraken, Tesser keeps the credentials but creates no Kraken ledger, and connecting again returns organizations-0023. The key can't be replaced through the API: contact Tesser support. Retrying won't help until the key works. Calls Kraken refuses because Tesser sent them out of order return kraken-5035, and other refusals Tesser doesn't recognize return kraken-5036.</td>
    </tr>
    <tr>
      <td>`kraken-2001`</td>
      <td>422</td>
      <td>The Kraken API key your organization registered lacks a permission this operation needs. Add it to the key in your Kraken account, then send the request again, or create a new transfer if this one failed; retrying without it won't help</td>
      <td>Deposits from a wallet into Kraken need the query-funds and add-funds permissions on your organization's Kraken API key, and withdrawals from Kraken need query-funds, withdraw-funds and query-ledger. Returned when the key lacks one of them, or Kraken refuses a call for lack of permission; the missing_permissions param names them when Tesser checked the key itself. If Tesser finds it while planning, the transfer fails and its status_reasons carry transfers-9113 with cause_code kraken-2001; if a permission is removed after that, a deposit step fails with kraken-2001 when it's signed or sent. Add the permissions to the key in Kraken, then send the request again or create a new transfer. If it happened while you connected Kraken, contact Tesser support instead: Tesser keeps the credentials, and connecting again returns organizations-0023. Swaps return kraken-2002, and a missing query-ledger permission on deposits returns kraken-2003.</td>
    </tr>
    <tr>
      <td>`kraken-2002`</td>
      <td>422</td>
      <td>The Kraken API key your organization registered lacks a permission Kraken swaps need. Add query-funds, query-open-trades, query-closed-trades, modify-trades and query-ledger to the key in your Kraken account, then create a new transfer; retrying without them won't help</td>
      <td>Tesser converts currencies on Kraken with your organization's Kraken API key, which needs the query-funds, query-open-trades, query-closed-trades, modify-trades and query-ledger permissions. The missing_permissions param names the ones the key lacks. Tesser checks them when it plans a transfer that swaps on Kraken, so the transfer fails and its status_reasons carry transfers-9113 with cause_code kraken-2002. Add the permissions to the key in Kraken, then create a new transfer; retrying the same one won't help.</td>
    </tr>
    <tr>
      <td>`kraken-2003`</td>
      <td>422</td>
      <td>The Kraken API key your organization registered lacks the query-ledger permission, which Tesser needs to confirm USDC deposits into Kraken. Add it to the key in your Kraken account, then send the request again, or create a new rebalance if this one failed; retrying without it won't help</td>
      <td>Tesser confirms what Kraken credited for a USDC deposit from a wallet by reading the Kraken ledger, so your organization's Kraken API key needs the query-ledger permission besides query-funds and add-funds. Returned when you create a deposit address for a Kraken ledger, or a rebalance from a wallet into one, and the key lacks it. If Tesser finds it while planning the rebalance, the rebalance fails and its status_reasons carry transfers-9113 with cause_code kraken-2003; if the permission is removed after that, the step fails with kraken-2003 when it's signed or sent. Add the permission in Kraken, then send the request again or create a new rebalance.</td>
    </tr>
    <tr>
      <td>`kraken-3000`</td>
      <td>422</td>
      <td>Kraken doesn't offer a bank deposit method for this currency that matches the methodId in depositInstructions, so Tesser couldn't set up Kraken. Check the methodId against the deposit methods in your Kraken account; retrying unchanged won't help</td>
      <td>Returned while Tesser sets up Kraken for an organization, when Kraken lists no bank deposit method for the currency, or its method doesn't match the methodId sent in depositInstructions. The request is valid, but the instructions or the Kraken account have to change first. Outside sandbox the credentials stay stored, so a corrected request returns organizations-0023: contact Tesser support to finish the setup with the corrected instructions.</td>
    </tr>
    <tr>
      <td>`kraken-3001`</td>
      <td>400</td>
      <td>The amount is too small to convert on Kraken: it's below Kraken's minimum order for this currency pair, or nothing would be left after Kraken's fee. Create a new transfer with a larger amount; retrying the same amount won't help</td>
      <td>For each currency pair, Kraken sets a minimum order size and value and the decimal places an order can use, and it takes a fee. Returned when the amount Tesser would convert doesn't meet them or leaves nothing after the fee. When Tesser checked Kraken's current minimums, minimum_volume gives the minimum in USDC (BRL on the BRL route) and minimum_cost the minimum in CAD or USD. Kraken's minimums change. Tesser finds it while planning, so the transfer fails and its status_reasons carry transfers-9113 with cause_code kraken-3001. Create a new transfer with a larger amount; retrying the same amount won't help.</td>
    </tr>
    <tr>
      <td>`kraken-3002`</td>
      <td>400</td>
      <td>A fixed Kraken source amount must use the trading pair's base currency</td>
      <td>Deposits and rebalances that require a conversion must start in the first Kraken trading pair's base currency. Quote-currency source amounts cannot be guaranteed.</td>
    </tr>
    <tr>
      <td>`kraken-3003`</td>
      <td>422</td>
      <td>Your organization's Kraken account doesn't offer exactly one USDC deposit method on this network, so Tesser can't deposit into Kraken from it. Enable USDC deposits on this network in Kraken, or contact Tesser support if they're enabled; retrying won't help until then</td>
      <td>Tesser deposits USDC into your organization's Kraken account through the Kraken deposit method for the wallet's network, matched on network, token contract and on-chain symbol. 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. Returned when you create a deposit address for a Kraken ledger or a rebalance from a wallet into one; if Tesser finds it while planning the rebalance, the rebalance fails and its status_reasons carry transfers-9113 with cause_code kraken-3003. Enable USDC deposits on that network in Kraken, or contact Tesser support if they're enabled; retrying won't help until the account offers exactly one matching method.</td>
    </tr>
    <tr>
      <td>`kraken-3004`</td>
      <td>422</td>
      <td>The organization's Kraken account has no usable USDC deposit address on this network, and Tesser can't create one safely: Kraken doesn't allow a new one for this deposit method, the account's address limit is reached, or a new address has a fee. Create a USDC deposit address on this network in Kraken, or contact Tesser support; retrying won't help until then</td>
      <td>Tesser receives USDC into the Kraken ledger at a deposit address of the organization's Kraken account on the requested network. Kraken listed no usable address for the deposit method (none, or only expired ones or ones that need a memo or tag), and Tesser doesn't create one when Kraken doesn't allow it, the account has reached its address limit, or a new address costs a fee. Returned by POST /v1/accounts/:id/onchain-addresses for a Kraken ledger. A rebalance into the Kraken ledger fails while Tesser plans it, with transfers-9113 whose cause_code is kraken-3004. Create a USDC deposit address on that network in the Kraken account, or contact Tesser support, then request the address or create the rebalance again. Retrying won't help until then. In the sandbox it means Tesser hasn't finished connecting Kraken for the workspace; contact Tesser support. An address that stops being valid after the rebalance was planned returns kraken-3007 instead.</td>
    </tr>
    <tr>
      <td>`kraken-3005`</td>
      <td>400</td>
      <td>The amount can't be deposited into Kraken: it's outside the minimum and maximum of Kraken's USDC deposit method on this network, more than your Kraken account's remaining deposit limit, uses more decimal places than USDC has on the wallet's network, or Kraken's deposit fee would take all of it. Create a new rebalance with a different amount; retrying the same amount won't help</td>
      <td>A rebalance from a wallet into a Kraken ledger deposits USDC through Kraken's deposit method for the wallet's network. The amount has to be positive, use no more decimal places than USDC has on that network, fall within the method's minimum and maximum, fit your Kraken account's remaining deposit limit, and be larger than Kraken's deposit fee; the decimals, minimum, maximum, remaining_limit or fee param gives the bound the amount missed. If Tesser finds it while planning, the rebalance fails and its status_reasons carry transfers-9113 with cause_code kraken-3005; if Kraken's limits change after that, the step fails with kraken-3005 when it's signed or sent. Create a new rebalance with an amount that fits; retrying the same amount won't help.</td>
    </tr>
    <tr>
      <td>`kraken-3006`</td>
      <td>422</td>
      <td>Sandbox simulates Kraken, and the simulation doesn't support this operation yet, so Tesser can't run it in sandbox. This isn't a problem with your request. Contact Tesser support if you need it in sandbox; retrying won't help</td>
      <td>In sandbox, Tesser runs Kraken transfers against a simulated Kraken account. Returned when a transfer needs a Kraken operation the simulation doesn't support; the operation param names it. If Tesser finds it while planning, the transfer fails and its status_reasons carry transfers-9113 with cause_code kraken-3006. Production isn't affected. Contact Tesser support if you need the operation in sandbox; retrying won't help.</td>
    </tr>
    <tr>
      <td>`kraken-3007`</td>
      <td>409</td>
      <td>The Kraken deposit address this rebalance step sends to is no longer valid at Kraken, so Tesser failed the step and sent nothing. Create a new rebalance, which uses a current address; retrying this one won't help</td>
      <td>Before Tesser signs or sends the step that moves USDC from a wallet to the Kraken ledger, it checks with Kraken that the deposit address chosen when the rebalance was planned is still valid: Kraken still lists it as a usable address for the same deposit method and network, and the credentials still belong to the same Kraken account. One of these changed, for example the address expired or was removed in Kraken, or the Kraken credentials now point to another account. The step failed before it was sent, any USDC reserved for it is available again in the wallet, and the step's status_reasons carries this code; a request that submits the step's signature returns it too. Create a new rebalance. Retrying won't help.</td>
    </tr>
    <tr>
      <td>`kraken-3008`</td>
      <td>409</td>
      <td>Kraken is already connected for another workspace of this organization, and the sandbox connects Kraken to one workspace per organization, so Tesser didn't connect it to this one. Use the workspace that has the Kraken ledger, or contact Tesser support; resending won't help</td>
      <td>Sandbox only. In the sandbox, Tesser connects a simulated Kraken account to one workspace per organization and creates its Kraken ledger there. Returned when you connect Kraken (POST /v1/organizations/secrets) from another workspace of the same organization. Nothing was created in this workspace. Use the workspace that already has the Kraken ledger, or contact Tesser support to move it; resending won't help. In production an organization holds one set of Kraken credentials, and connecting from a second workspace returns organizations-0023.</td>
    </tr>
    <tr>
      <td>`kraken-4290`</td>
      <td>429</td>
      <td>Kraken is rate limiting calls made with your organization's Kraken API key, so it refused this one. Wait a short while and send the request again. If this happened while you connected Kraken, contact Tesser support instead: connecting again won't work</td>
      <td>Kraken limits how often each API key can call it, and Tesser calls Kraken with your organization's key. Returned when Kraken refuses a call for exceeding that limit. Wait a short while and send the request again; while Tesser plans or executes a transfer, it retries on its own. When it happens while you connect Kraken (POST /v1/organizations/secrets), Tesser keeps the credentials but creates no Kraken ledger, and connecting again returns organizations-0023: contact Tesser support to finish connecting.</td>
    </tr>
    <tr>
      <td>`kraken-5030`</td>
      <td>502</td>
      <td>Kraken is temporarily unavailable to Tesser: it didn't respond, returned a server error, or its market for this currency pair wasn't open. Wait a short while and send the request again. If this happened while you connected Kraken, contact Tesser support instead: connecting again won't work</td>
      <td>Returned when Tesser can't complete a call to Kraken for a reason that usually passes: Kraken, or Tesser's connection to it, didn't respond in time; Kraken answered with a server error or an error it didn't explain; the currency pair's market wasn't open for trading; or Kraken's withdrawal fee changed each time Tesser priced it. Wait a short while and send the request again; while Tesser plans or executes a transfer, it retries on its own. If an order or withdrawal was being submitted, Tesser doesn't resend it, because Kraken may have received it: the step is held until Tesser confirms the outcome. When it happens while you connect Kraken (POST /v1/organizations/secrets), Tesser keeps the credentials but creates no Kraken ledger, and connecting again returns organizations-0023: contact Tesser support to finish connecting.</td>
    </tr>
    <tr>
      <td>`kraken-5031`</td>
      <td>502</td>
      <td>Kraken returned a response Tesser couldn't verify, so Tesser stopped instead of acting on it. Wait a short while and send the request again; contact Tesser support with the request_id if it keeps failing</td>
      <td>Tesser checks every Kraken response against what Kraken documents, such as required fields, matching amounts and a quote for the amount Tesser asked about, and stops when one doesn't match rather than act on it. Returned when that check fails while you create a deposit address for a Kraken ledger, sign a step that deposits into Kraken, or connect Kraken. It's also returned when Tesser's connection to Kraken refuses a request Tesser built before the request reaches Kraken. While Tesser plans a transfer it retries on its own, and a submitted order or withdrawal is held until Tesser confirms its outcome. Send the request again after a short wait, and contact Tesser support with the request_id if it keeps failing. When it happens while you connect Kraken, connecting again returns organizations-0023: contact Tesser support instead.</td>
    </tr>
    <tr>
      <td>`kraken-5034`</td>
      <td>503</td>
      <td>Tesser has asked Kraken for a USDC deposit address on this network and is waiting for Kraken to list it. Send the request again in a few minutes; Tesser only checks for the address and won't ask again. If it keeps failing, contact Tesser support</td>
      <td>Tesser asks Kraken for a deposit address at most once per Kraken account and deposit method, then waits for Kraken to list it. Returned when you create a deposit address for a Kraken ledger, or Tesser plans a rebalance into one, before Kraken lists the address it was asked for. Later requests only check for that address, so sending the request again in a few minutes is safe; while Tesser plans a rebalance, it retries on its own. Contact Tesser support with the account id if it doesn't resolve, because Tesser won't ask Kraken again on its own.</td>
    </tr>
    <tr>
      <td>`kraken-5035`</td>
      <td>503</td>
      <td>Kraken refused this call because the calls Tesser signed with your organization's Kraken API key reached it out of order. This is a fault at Tesser, not a problem with your key. Wait a short while and send the request again. If this happened while you connected Kraken, contact Tesser support instead: connecting again won't work</td>
      <td>Kraken requires every call signed with an API key to carry a number higher than the last one it saw for that key. Returned when Kraken refuses a call because the number Tesser sent wasn't higher, which can happen when Tesser makes several calls with the same key at once. Wait a short while and send the request again; contact Tesser support with the request_id if it keeps happening. When it happens while you connect Kraken (POST /v1/organizations/secrets), Tesser keeps the credentials but creates no Kraken ledger, and connecting again returns organizations-0023: contact Tesser support to finish connecting.</td>
    </tr>
    <tr>
      <td>`kraken-5036`</td>
      <td>502</td>
      <td>Kraken answered this call with an error Tesser doesn't recognize, so Tesser stopped without using the answer. Send the request again after a short wait, and contact Tesser support with the request_id if it fails the same way. If this happened while you connected Kraken, contact Tesser support instead: connecting again won't work</td>
      <td>Returned when Kraken answers a call with an HTTP client error that Tesser doesn't map to another code, such as 400, 404 or 409, or a timeout status when Tesser submitted an order. Tesser can't tell from the answer whether Kraken acted on the call, so a submitted order that gets it isn't sent again: the step is held until Tesser confirms the order's outcome. Send the request again after a short wait, and contact Tesser support with the request_id if it fails the same way. When it happens while you connect Kraken (POST /v1/organizations/secrets), Tesser keeps the credentials but creates no Kraken ledger, and connecting again returns organizations-0023: contact Tesser support to finish connecting.</td>
    </tr>
    <tr>
      <td>`kraken-5037`</td>
      <td>503</td>
      <td>Tesser couldn't load the Kraken API key it stores for your organization, so it couldn't call Kraken. This isn't a problem with your request or your Kraken account. Contact Tesser support; retrying won't help until Tesser restores the key</td>
      <td>Tesser keeps the Kraken API key and secret your organization registered in a vault and loads them for every call to Kraken. Returned when the key is on file but Tesser can't load it, or what it loads isn't a complete key and secret, so Kraken received nothing. When it happens while you connect Kraken (POST /v1/organizations/secrets), Tesser keeps the credentials but creates no Kraken ledger, and connecting again returns organizations-0023. Contact Tesser support with the request_id or the payment id; retrying won't help until Tesser restores the key. An organization with no Kraken key on file gets kraken-1001 instead.</td>
    </tr>
  </tbody>
</table>

## OpenFX

<table className="wrap-first-col error-table">
  <thead>
    <tr>
      <th>Error Code</th>
      <th>HTTP Status</th>
      <th>Error Message</th>
      <th>Description</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>`openfx-0002`</td>
      <td>400</td>
      <td>OpenFX account has a negative balance (per-currency or net USD); fund the account before onboarding</td>
      <td>The workspace's OpenFX account reported a negative balance during ledger onboarding — either a single currency with amount &lt; 0 or a net USD-equivalent &lt; 0. Creation aborted to prevent unfunded ledgers.</td>
    </tr>
    <tr>
      <td>`openfx-1000`</td>
      <td>422</td>
      <td>Tesser has no OpenFX credentials for this workspace's organization, so it can't use OpenFX for this request. Store them with POST /v1/organizations/secrets or contact Tesser support; retrying won't help until they're stored</td>
      <td>The organization has no OpenFX credentials stored with Tesser, so Tesser can't call OpenFX for it. Returned when a request needs OpenFX, for example a deposit or rebalance through OpenFX. When Tesser plans a deposit or rebalance and the credentials are gone, it fails with transfers-9113 and this code as cause_code. Store the credentials with POST /v1/organizations/secrets, or contact Tesser support; retrying won't help until they're stored. Credentials that are stored but can't be loaded return openfx-5033 instead.</td>
    </tr>
    <tr>
      <td>`openfx-2000`</td>
      <td>503</td>
      <td>OpenFX rejected the credentials Tesser uses for your workspace, so Tesser can't reach OpenFX. This isn't a problem with your API key. Contact Tesser support; retrying won't help until Tesser fixes the credentials</td>
      <td>OpenFX refused the credentials Tesser stores to call it for your workspace. Tesser has to fix them: contact Tesser support and quote the request_id. The same request fails until then.</td>
    </tr>
    <tr>
      <td>`openfx-4001`</td>
      <td>400</td>
      <td>OpenFX trade amount below minimum</td>
      <td>OpenFX rejected the trade with INVALID_TRADE_AMOUNT — the amount is below the account's minimum trading limit. User-fixable by sending a larger amount.</td>
    </tr>
    <tr>
      <td>`openfx-4290`</td>
      <td>429</td>
      <td>Cannot complete request because rate limited by provider OpenFX</td>
      <td>The OpenFX API returned a 429 rate limit response</td>
    </tr>
    <tr>
      <td>`openfx-5000`</td>
      <td>502</td>
      <td>OpenFX refused the request Tesser sent for this operation. Retrying the same request won't help; contact Tesser support with the request_id or the payment id</td>
      <td>OpenFX answered a request Tesser sent for your workspace with a final refusal: an HTTP 4xx other than a credentials failure, a rate limit, a 422 or a below-minimum trade, for example because a quote expired or a withdrawal account isn't active at OpenFX. The status param is OpenFX's HTTP status and path is the OpenFX endpoint. It is returned as an HTTP error when you connect OpenFX (POST /v1/organizations/secrets) or create an OpenFX ledger (POST /v1/accounts/ledgers). On a transfer it appears as cause_code in the failed step's status_reasons: transfers-9304 for a currency conversion, transfers-9303 for an OpenFX withdrawal. Retrying the same request won't help. Contact Tesser support with the request_id or the payment id so it can check OpenFX's reason, then create a new transfer. openfx-4001 is returned instead for an amount below OpenFX's minimum, openfx-2000 when OpenFX rejects Tesser's credentials, idempotency-0002 for an OpenFX 422, openfx-5031 when Tesser couldn't send the request and openfx-5032 when Tesser couldn't read OpenFX's answer.</td>
    </tr>
    <tr>
      <td>`openfx-5030`</td>
      <td>502</td>
      <td>OpenFX is temporarily unavailable</td>
      <td>OpenFX returned a 5xx or the request failed in transit (network error/timeout). The request may or may not have been processed by OpenFX — retry with the same idempotency key.</td>
    </tr>
    <tr>
      <td>`openfx-5031`</td>
      <td>503</td>
      <td>Tesser couldn't send this request to OpenFX because of a problem in Tesser's setup, so OpenFX received nothing. This isn't a problem with your request. Contact Tesser support; retrying won't help until Tesser fixes it</td>
      <td>Tesser calls OpenFX for your workspace through a connection that Tesser configures. That connection isn't set up in this Tesser environment, or a safety check at Tesser stopped the request before it was sent, so OpenFX received nothing and nothing was created, converted or sent there. It is returned as an HTTP error when you connect OpenFX (POST /v1/organizations/secrets) or create an OpenFX ledger (POST /v1/accounts/ledgers). On a transfer it appears as cause_code in the failed step's status_reasons (transfers-9304 or transfers-9303). This is a fault at Tesser. Contact Tesser support with the request_id or the payment id; retrying won't help until Tesser fixes it.</td>
    </tr>
    <tr>
      <td>`openfx-5032`</td>
      <td>502</td>
      <td>OpenFX answered without the data Tesser needs, so Tesser couldn't complete the request. This isn't a problem with your request. Try again in a few minutes, and contact Tesser support if it keeps failing</td>
      <td>When you connect OpenFX (POST /v1/organizations/secrets) or create an OpenFX ledger (POST /v1/accounts/ledgers), Tesser reads your OpenFX balances to set up the ledger. OpenFX answered without the list of balances, so Tesser didn't create the ledger. Send the request again in a few minutes; if it keeps failing, contact Tesser support with the request_id.</td>
    </tr>
    <tr>
      <td>`openfx-5033`</td>
      <td>503</td>
      <td>Tesser couldn't load the OpenFX credentials it stores for your organization, so it couldn't call OpenFX. This isn't a problem with your request. Contact Tesser support; retrying won't help until Tesser restores them</td>
      <td>Tesser calls OpenFX with the credentials it stores for your organization. Returned when they're on file but Tesser can't load them, on any request that calls OpenFX for your workspace, so OpenFX received nothing. When Tesser plans a deposit or rebalance, it fails with transfers-9113 and this code as cause_code. Contact Tesser support with the request_id or the payment id; retrying won't help until Tesser restores the credentials. An organization with no OpenFX credentials gets openfx-1000 instead.</td>
    </tr>
  </tbody>
</table>

## Zuba

<table className="wrap-first-col error-table">
  <thead>
    <tr>
      <th>Error Code</th>
      <th>HTTP Status</th>
      <th>Error Message</th>
      <th>Description</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>`zuba-0001`</td>
      <td>503</td>
      <td>Tesser's connection to Zuba isn't configured in this environment, so Tesser sent nothing to Zuba. This is a problem at Tesser, not with the request. Contact Tesser support; retrying won't help until Tesser configures it</td>
      <td>Tesser's own Zuba configuration, the Zuba hosts and credentials Tesser uses or the Basis Theory reactor that checks and submits payouts, is missing in this environment. Tesser checks it before contacting Zuba, so nothing was sent to Zuba for this request. It can come back from a request that reaches Zuba, in a payout step's status_reasons when the step failed before anything was sent, or as the reason Tesser holds a payout. Contact Tesser support; retrying won't help until Tesser fixes its configuration. A workspace with no Zuba account returns zuba-3025 instead.</td>
    </tr>
    <tr>
      <td>`zuba-0004`</td>
      <td>409</td>
      <td>Tesser refused this Zuba onboarding step because it conflicts with the Zuba sub-account or KYB application already on record for this organization; reason says which. Retrying won't help: contact Tesser support with the reason, or, for organization_has_different_sub_account, send the KYB with the legal name and country of incorporation the sub-account was created with</td>
      <td>The organization's Zuba onboarding conflicts with what Tesser or Zuba already holds for it, so Tesser stopped this step. The reason param says which: organization_has_zuba_credentials (the organization still has Zuba credentials stored from before Tesser managed its Zuba sub-account, and Tesser has to remove them), organization_has_different_sub_account (the organization already has a Zuba sub-account under a different legal name or country than this KYB's businessInfo), application_account_mismatch or application_mismatch (the KYB application Zuba returned belongs to another sub-account or isn't the one on record), or application_not_recoverable (Zuba says an application already exists, but Tesser can't find exactly one for the sub-account). Steps that finished earlier in the same request, such as creating the sub-account or filing the application at Zuba, stay done. Retrying won't help: for organization_has_different_sub_account, send the KYB with the original legal name and country of incorporation; otherwise contact Tesser support with the reason. A step sent before the application step returns zuba-3028, and persons that don't match the application return zuba-3029.</td>
    </tr>
    <tr>
      <td>`zuba-2000`</td>
      <td>503</td>
      <td>Zuba rejected the credentials Tesser uses for your workspace, so Tesser can't reach Zuba. This isn't a problem with your API key. Contact Tesser support; retrying won't help until Tesser fixes the credentials</td>
      <td>Zuba refused the credentials Tesser stores for your workspace, so Zuba didn't act on this call. Tesser has to fix them: contact Tesser support and quote the request_id. The same request fails until then.</td>
    </tr>
    <tr>
      <td>`zuba-2001`</td>
      <td>500</td>
      <td>Zuba says the Zuba sub-account Tesser has on record for this workspace doesn't belong to Tesser's Zuba account, so Zuba refused this call. This is a fault in Tesser's setup, not in your request. Contact Tesser support; retrying won't help until Tesser fixes it</td>
      <td>Zuba answered not_account_owner: the Zuba sub-account Tesser stores for the workspace's organization isn't one Tesser's Zuba platform account can act for, so Zuba didn't act on the call. It is a fault in Tesser's setup, and the same call fails until Tesser fixes it. Accepting a quote or an onboarding step that hits it changed nothing; contact Tesser support with the request_id. A payout step that hits it isn't failed: it stays unconfirmed until Tesser support settles it, because an earlier attempt may have been paid, so don't create a new payment for those funds. A sandbox deposit step that hits it fails with transfers-9301.</td>
    </tr>
    <tr>
      <td>`zuba-3000`</td>
      <td>400</td>
      <td>Zuba rejected this request as invalid. Check the details you sent, such as the KYB application or document, fix them and send the request again; retrying unchanged won't help. Contact Tesser support if they look correct, and include the request_id</td>
      <td>Zuba answered the call with a validation error. Through the onboarding API it is the sub-account, KYB application, document upload or identity verification step that Zuba refused: nothing was saved for that step, and the same request fails until its details change. Fix the KYB data or document and send it again, or contact Tesser support with the request_id if they look correct. When Zuba refuses a payout this way it may still have recorded the payout, so Tesser doesn't fail the step: it looks the payout up and the step's status gives the outcome. Don't create a new payment for those funds while it is unresolved. A request Tesser itself couldn't build returns zuba-3030, and an onboarding request Tesser refuses before sending it returns zuba-3031.</td>
    </tr>
    <tr>
      <td>`zuba-3001`</td>
      <td>422</td>
      <td>Zuba refused this payout because the USDC balance of the workspace's Zuba sub-account didn't cover it. Zuba may have recorded the payout as failed, so Tesser checks with Zuba before settling the payment's outcome. Don't create a new payment for these funds yet: check the payment's status, and contact Tesser support with the payment id if it stays unresolved</td>
      <td>Zuba refused the payout because the USDC balance of the workspace's Zuba sub-account, its Zuba ledger, was below the payout's debit. Tesser funds that balance as part of the payment and checks it before sending, so this is a shortfall for Tesser to resolve, not a problem with your request. Zuba usually records a failed payout for the refusal, so Tesser looks the payout up instead of failing the step at once: a sandbox payout then fails with transfers-9302, and a payout from the Zuba ledger is held for Tesser support with transfers-9209. Don't create a new payment for these funds until the payment's status settles; contact Tesser support with the payment id if it doesn't.</td>
    </tr>
    <tr>
      <td>`zuba-3002`</td>
      <td>422</td>
      <td>Zuba does not quote this corridor</td>
      <td>Zuba answered UNSUPPORTED_CORRIDOR to a payout-intent quote. No quote exists and nothing was submitted.</td>
    </tr>
    <tr>
      <td>`zuba-3003`</td>
      <td>422</td>
      <td>Zuba refused the payout because its quote expired</td>
      <td>Zuba refused this quote-bound payout request with QUOTE_EXPIRED. The refusal covers only this request: an earlier attempt under the same clientRef may still have been accepted, so reconcile the clientRef by lookup before concluding no payout exists. The quote cannot be reused; a new quote needs its own acceptance.</td>
    </tr>
    <tr>
      <td>`zuba-3004`</td>
      <td>400</td>
      <td>This USDC payout to an NGN or GHS bank account can't be created with the field named in field, so nothing was created. Remove it and send the request again, and set the accounts when you accept the quote; in the sandbox you can instead send funding_account_id, desired.from.account_id and desired.to.account_id together</td>
      <td>A payment that pays out USDC to an NGN or GHS bank account through Zuba is priced by its payout amount (desired.to.amount), and the payout currency has no network, so desired.to.network is refused. Its accounts are set when you accept the quote. In the sandbox you can also send funding_account_id, desired.from.account_id and desired.to.account_id together on create, and the quote is accepted at once; sending only some of them is refused, and outside the sandbox sending them on create is refused. The field param names what to remove. Nothing was created; fix the request and send it again.</td>
    </tr>
    <tr>
      <td>`zuba-3005`</td>
      <td>409</td>
      <td>This payment's quote has no price that can be accepted, so Tesser didn't accept it and nothing was changed. Create a new payment to get a new quote; retrying won't help</td>
      <td>The payment is priced by a Zuba quote stored on it. Accepting it, with PATCH /v1/payments/:id or, in the sandbox, when the payment is created with its accounts, needs that quote to be ready. Zuba, or Kraken for a Kraken-funded payout, didn't return a price Tesser can accept, so the quote isn't ready. Nothing was changed: no accounts were attached. Create a new payment to get a new quote. Retrying won't help. A quote Tesser had to refresh when you accepted it returns zuba-3026, a payment whose quote isn't accepted with PATCH returns zuba-3027, and a review of a Zuba-priced payment that isn't awaiting one returns payments-3105.</td>
    </tr>
    <tr>
      <td>`zuba-3006`</td>
      <td>422</td>
      <td>No wallet account in this workspace holds the sandbox wallet address</td>
      <td>Sandbox instant acceptance funds Zuba through the Tesser sandbox wallet, which must be registered in the workspace as an unmanaged wallet account. Nothing was created; register the sandbox wallet, then retry with a new Idempotency-Key.</td>
    </tr>
    <tr>
      <td>`zuba-3007`</td>
      <td>502</td>
      <td>Zuba's sandbox refused or failed the test deposit that funds this payout, so the deposit step failed and the payout wasn't sent. The test USDC already sent to Tesser's sandbox wallet isn't returned. Create a new payment to try again; contact Tesser support if it keeps failing</td>
      <td>Sandbox only. A sandbox payout is funded by sending test USDC to Tesser's sandbox wallet, after which Tesser asks Zuba's sandbox to credit the same amount to the workspace's Zuba sub-account. Zuba refused that deposit, or created it and then reported it failed, so the deposit step failed with transfers-9301 (this code is its code param) and the payout after it wasn't sent. The test USDC already in Tesser's sandbox wallet isn't returned. Retrying the same payment won't help; create a new one, and contact Tesser support if deposits keep failing.</td>
    </tr>
    <tr>
      <td>`zuba-3008`</td>
      <td>422</td>
      <td>This destination bank account can't be paid in the sandbox: its account number must be one of Zuba's sandbox test numbers, so Tesser didn't accept the payment with it. Use a bank account numbered 0000000000 (pays out) or 0000000001 or 0000000002 (fail on purpose) and try again; retrying with this account won't help</td>
      <td>Sandbox only. Zuba's sandbox pays only to its test account numbers: 0000000000 pays out, and 0000000001 and 0000000002 fail on purpose. The destination bank account's number isn't one of them. Nothing changed: on create, no payment was created; on accepting the quote, it wasn't accepted and no steps were created. Use a bank account with one of those numbers and send the request again. A bank account without an owner, a listed bank code or a valid account number gets zuba-3010 instead.</td>
    </tr>
    <tr>
      <td>`zuba-3009`</td>
      <td>422</td>
      <td>Zuba hasn't allowed Tesser to open a Tempo deposit wallet for this organization's Zuba sub-account, so Tesser couldn't set up the workspace's Zuba ledger and created nothing. Tesser has to get Zuba to enable it; contact Tesser support. Retrying won't help until Zuba does</td>
      <td>Each workspace with an active Zuba sub-account gets a Zuba ledger whose deposit address is a Zuba wallet on Tempo. Zuba refused to open that wallet: the sub-account isn't enabled for Tempo deposits, or Tesser's Zuba credentials lack the permission to open wallets. Nothing was created, so the workspace has no Zuba ledger yet. Tesser has to get Zuba to enable it and then sets the ledger up again; retrying before then won't help. Contact Tesser support.</td>
    </tr>
    <tr>
      <td>`zuba-3010`</td>
      <td>422</td>
      <td>The destination bank account can't receive this Zuba payout: it needs an owner (a tenant or counterparty) with a name, a bank code Zuba lists for the payout currency, and an account number of the right length. Tesser didn't accept the payment with it. Fix the bank account or use another one, then try again; retrying with this account unchanged won't help</td>
      <td>Zuba pays out only to a bank account in the payout currency that belongs to a tenant or counterparty with a name (no leading or trailing spaces or control characters), has a bank code Zuba lists (for NGN, a Nigerian bank code; for GHS, the SWIFT/BIC of a Ghanaian bank, or that bank's Zuba id in the sandbox), and has an account number of the right length (10 digits for NGN, 8 to 20 for GHS). This bank account fails one of those rules. Nothing changed: the quote wasn't accepted and no accounts were attached, or on a sandbox create no payment was created. Fix the bank account or choose another one and send the request again; retrying with the same account won't help. A bank account whose details changed after the payment was accepted holds the payout with zuba-3034 instead.</td>
    </tr>
    <tr>
      <td>`zuba-3011`</td>
      <td>422</td>
      <td>Zuba refused this payout because the sender's details were incomplete, invalid or not on record with Zuba, so it didn't create the payout; provider_code says which. Correct the name, address and registration details of the payment's originator and contact Tesser support with the payment id; sending the same details again won't help</td>
      <td>Zuba checks the payout's sender, the payment's originator (the tenant or counterparty that owns the funding account), before it queues the payout, and refused it: SENDER_INFO_INCOMPLETE or SENDER_INFO_INVALID (the originator's name, address, date of birth or registration number is missing or invalid) or ORIGINATOR_NOT_ON_RECORD (Zuba has no sender on record for it). No payout was created. A payout from the workspace's Zuba ledger is held for Tesser support with transfers-9209 (reason payout_refused, this code and provider_code), and its funds stay on the ledger until Tesser support sends or releases it. A sandbox payout fails with this code. Correct the originator's details and contact Tesser support with the payment id; retrying with the same details won't help.</td>
    </tr>
    <tr>
      <td>`zuba-3020`</td>
      <td>422</td>
      <td>This workspace's Zuba sub-account isn't active (Zuba onboarding isn't finished, Zuba is still reviewing it, or it was closed), so Tesser or Zuba refused this Zuba action. Finish Zuba onboarding or contact Tesser support; retrying won't help until the sub-account is active</td>
      <td>The workspace's organization has no Zuba sub-account yet, Zuba hasn't approved its KYB application, or the sub-account was closed. Tesser only treats it as active after its next check with Zuba, within about five minutes of approval. Until then Tesser refuses every Zuba action except the KYB application itself, and Zuba refuses payouts for it. Accepting a quote changes nothing. Signing a step of a Kraken to Zuba payment holds that step with transfers-9211, and signing it again keeps failing until Tesser support sends or releases it. A Kraken to Zuba payment that reaches its Kraken legs fails with transfers-9113, with this code as cause_code. A payout step fails on its first attempt, or for a payout from the Zuba ledger is held with transfers-9209 and this code; on a later attempt it stays unconfirmed, since an earlier attempt may have been paid. A sandbox deposit step fails with transfers-9301. Finish the organization's Zuba onboarding and wait for approval, or contact Tesser support; retrying won't help until the sub-account is active.</td>
    </tr>
    <tr>
      <td>`zuba-3021`</td>
      <td>422</td>
      <td>The Zuba KYB application is missing steps or documents</td>
      <td>Zuba refused to submit the application; the missing steps, company documents and persons without documents are listed as Zuba returned them.</td>
    </tr>
    <tr>
      <td>`zuba-3022`</td>
      <td>500</td>
      <td>Zuba has no record of the Zuba sub-account Tesser stores for this organization, so Zuba didn't act on this call. This is a fault in Tesser's setup, not in your request. Contact Tesser support; retrying won't help until Tesser fixes it</td>
      <td>Zuba doesn't know the Zuba sub-account id Tesser stored when it created the organization's sub-account, for example because it was created under other Zuba credentials. Tesser has to correct it. Zuba didn't act on the call: a read or a sandbox approval changed nothing, though a KYB application submitted earlier in the same request stays submitted. Retrying won't help; contact Tesser support with the request_id.</td>
    </tr>
    <tr>
      <td>`zuba-3023`</td>
      <td>409</td>
      <td>Zuba's sandbox refused to approve this organization's Zuba sub-account because its KYB application isn't in a state it can approve, such as waiting on more information. The submission stays recorded, but the sub-account isn't active. Check the onboarding status, update the application and submit again, or contact Tesser support; submitting again unchanged won't help</td>
      <td>Sandbox only. In the sandbox Tesser approves the sub-account right after the KYB application is submitted. Zuba's sandbox approves only a pending sub-account whose application is submitted and not waiting on more information, and this one isn't: the application needs more information, or the sub-account was rejected or closed. The sub-account wasn't approved and stays as it was; a submission made in the same request stays recorded. Read the onboarding status with GET /v1/organizations/zuba/onboarding: if the application needs more information, send the updated KYB through the application step and submit again; otherwise contact Tesser support. Submitting again unchanged won't help.</td>
    </tr>
    <tr>
      <td>`zuba-3024`</td>
      <td>409</td>
      <td>Zuba's sandbox refused to start the applicant's identity verification, so Tesser didn't submit the KYB application; reason gives Zuba's reason. Check the onboarding status and contact Tesser support with the reason; submitting again won't help until it changes</td>
      <td>Sandbox only. Before submitting a KYB application in the sandbox, Tesser starts the applicant's identity verification at Zuba; an applicant who is already verified is fine. Zuba refused to start it, and the reason param gives Zuba's code: step_locked, identity_verification_in_review, identity_verification_changed, identity_verification_not_linked, application_closed, or unrecognized when Zuba sent another value. The application wasn't submitted and nothing else changed. Submitting again won't help until the reason changes; contact Tesser support with the reason. Production doesn't start identity verification this way: there the submit fails with zuba-3021 listing verify_identity instead.</td>
    </tr>
    <tr>
      <td>`zuba-3025`</td>
      <td>422</td>
      <td>This workspace has no Zuba account at Tesser, so Tesser sent nothing to Zuba. Complete Zuba onboarding for the workspace, or contact Tesser support if it's complete; retrying won't help until the account exists</td>
      <td>Tesser sends Zuba requests for a workspace through its organization's Zuba account, which Zuba onboarding creates. The workspace has none on record, so Tesser sent nothing to Zuba. Most requests check this first and return zuba-3020; this code comes back where Tesser reaches Zuba directly, for example in a payout step's status_reasons when the step failed before anything was sent, or as the reason Tesser holds a payout. Complete Zuba onboarding with the /v1/organizations/zuba/onboarding endpoints, or contact Tesser support if onboarding is complete. Retrying won't help until the account exists.</td>
    </tr>
    <tr>
      <td>`zuba-3026`</td>
      <td>409</td>
      <td>Zuba's refreshed quote for this payout doesn't match the one shown: Zuba didn't quote it again, changed the payout amount, or priced it more than 1% higher, so Tesser didn't accept it and nothing was changed. Create a new payment to get a current quote; sending the same request again may fail the same way</td>
      <td>A payout that Zuba completes from a managed wallet takes time to fund. When the quote shown on the payment would expire before the USDC reaches Zuba, Tesser asks Zuba for a new quote for the same payout amount when you accept it with PATCH /v1/payments/:id, and accepts the new quote only if it pays out the same amount and debits at most 1% more than the quote shown. Zuba didn't quote the payout again, or its new quote failed one of these checks; the reason param says which (quote_unavailable, payout_amount_changed or price_moved). Nothing was attached and the payment still waits for acceptance. Create a new payment to see the current price. Sending the same PATCH again asks Zuba for another quote, which may fail the same way.</td>
    </tr>
    <tr>
      <td>`zuba-3027`</td>
      <td>409</td>
      <td>This payment's quote can't be accepted with PATCH: in the sandbox, a Zuba payout's quote is accepted only when the payment is created with its accounts. Create a new payment with funding_account_id, desired.from.account_id and desired.to.account_id; retrying won't help</td>
      <td>A payout that Zuba completes from a managed wallet is accepted in one of two ways. In production, the payment is created without accounts, and PATCH /v1/payments/:id attaches them and accepts the quote. In the sandbox, the payment is created with funding_account_id, desired.from.account_id and desired.to.account_id, and its quote is accepted then; PATCH can't accept it later. This payment's quote can't be accepted with PATCH, so nothing was changed. In the sandbox, create a new payment with its accounts. In production, contact Tesser support: Tesser's Zuba payout setup is incomplete. Retrying won't help.</td>
    </tr>
    <tr>
      <td>`zuba-3028`</td>
      <td>409</td>
      <td>This organization has no Zuba sub-account or KYB application yet, so Tesser can't take this onboarding step; reason says which. File the KYB application first with POST /v1/organizations/zuba/onboarding/application, then send this request again</td>
      <td>Uploading or confirming a KYB document and submitting the application need the organization's Zuba sub-account and KYB application, which the application step creates. The reason param says which is missing: workspace_has_no_sub_account or workspace_has_no_application. Nothing was sent to Zuba. File the KYB application first with POST /v1/organizations/zuba/onboarding/application, then repeat this request; repeating it before then won't help.</td>
    </tr>
    <tr>
      <td>`zuba-3029`</td>
      <td>409</td>
      <td>The persons in this request don't match the persons on the organization's Zuba KYB application one to one, so Tesser sent no documents; reason says how and count how many. Send the KYB with the same persons as the application, or use a person_id the application step returned, or contact Tesser support if the application's persons are wrong</td>
      <td>Tesser maps each person in the KYB to exactly one person on the organization's Zuba KYB application, by name, before any document is sent. The reason param says what failed: kyb_person_not_on_application (a KYB person has no match), application_person_not_in_kyb (the application has a person the KYB doesn't), application_person_ambiguous (two application persons share a name), application_person_unnamed (an application person has no name), or person_not_on_application (the person_id on a document isn't on the application); count says how many persons. Steps that finished earlier in the same request, such as creating the sub-account or filing the application, stay done, and no document was sent. Send the KYB with the application's persons, or a person_id from the application step's persons, and repeat the request; contact Tesser support if the application's persons themselves are wrong. Repeating it unchanged won't help.</td>
    </tr>
    <tr>
      <td>`zuba-3030`</td>
      <td>500</td>
      <td>Tesser couldn't build a valid request to Zuba for this, so it sent nothing to Zuba. This is a fault at Tesser, not in your request. Contact Tesser support with the payment id or request_id; retrying won't help</td>
      <td>Tesser checks every request it builds for Zuba before sending it, and this one failed the check, so nothing reached Zuba. It is a fault at Tesser. A payout step that hits it fails with this code in the sandbox, or for a payout from the Zuba ledger is held for Tesser support with transfers-9209; a sandbox deposit step fails with transfers-9301. Retrying won't help; contact Tesser support with the payment id or request_id.</td>
    </tr>
    <tr>
      <td>`zuba-3031`</td>
      <td>400</td>
      <td>Tesser can't send this onboarding request to Zuba because it's invalid; reason says what is wrong and detail which KYB fields. Fix the KYB or document and send the request again; retrying unchanged won't help</td>
      <td>Tesser validates the KYB body and each document before sending them to Zuba. The reason param says what failed: kyb_invalid (detail lists the KYB field paths that are missing or invalid, never their values), kyb_persons_invalid (the persons array can't be read), sub_account_identity_invalid (the legal name or country of incorporation in businessInfo can't open a Zuba sub-account), document_type_invalid, document_too_large (over 10 MB) or document_mime_type_unsupported (only PDF, PNG and JPEG). Nothing was sent to Zuba. Fix the request and send it again.</td>
    </tr>
    <tr>
      <td>`zuba-3032`</td>
      <td>400</td>
      <td>The payment's statement description or the originator's details can't be sent to Zuba as written: a value is blank, longer than 500 characters, or contains control characters or double braces; field says which. Nothing was accepted. Fix the value and accept the quote again</td>
      <td>Before a Zuba payout is funded, Tesser checks the text it will send to Zuba: payment_info.payment_description_wire and the originator's name, country, registration number, street address, city and postal code (date of birth for an individual). A value that is blank, longer than 500 characters, or contains control characters or double braces can't be sent. The field param is payment_info.payment_description_wire or originator. Nothing was accepted or created. Fix the payment's description or the originator's details and accept the quote again; retrying unchanged won't help.</td>
    </tr>
    <tr>
      <td>`zuba-3033`</td>
      <td>502</td>
      <td>Zuba says the deposit wallet for this workspace's Zuba ledger isn't active, so Tesser didn't set up the Zuba ledger. Contact Tesser support; retrying won't help until Zuba reactivates the wallet</td>
      <td>Internal: returned while Tesser sets up a workspace's Zuba ledger, never to an API request, when Zuba answers that the ledger's Tempo deposit wallet exists but isn't active. Tesser doesn't use the wallet, so the workspace has no Zuba ledger until Zuba reactivates it and Tesser sets the ledger up again.</td>
    </tr>
    <tr>
      <td>`zuba-3034`</td>
      <td>409</td>
      <td>Tesser won't send this Zuba payout to the destination bank account because the account's details changed after the payment was accepted. Contact Tesser support with the payment id; don't create a new payment for these funds while the payout is held</td>
      <td>Tesser records the destination bank account's details when the payment is accepted and checks them again before sending the payout. They changed in between, for example the account number, bank or owner's name, so Tesser didn't send the payout to the changed account. A payout from the Zuba ledger that Tesser hadn't tried to send yet is held with transfers-9209 and this code, and its funds stay on the Zuba ledger. If Tesser had already tried to send it before the change, the step stays unconfirmed while Tesser support checks that earlier attempt, which may have been paid. Contact Tesser support with the payment id; don't create a new payment for these funds while it is held.</td>
    </tr>
    <tr>
      <td>`zuba-3035`</td>
      <td>502</td>
      <td>Tesser couldn't confirm whether Zuba recorded this onboarding step: Zuba didn't answer in time, or answered in a way Tesser couldn't use. Send the same request again, which is safe; contact Tesser support with the request_id if it keeps failing</td>
      <td>Tesser sent the sub-account, KYB application, document or submission to Zuba and couldn't confirm whether Zuba recorded it. Every onboarding step is safe to repeat: the sub-account is created under the same key each time, an existing application is reused, a submit reads Zuba's state first, and a repeated document upload at worst leaves an extra copy at Zuba. Send the same request again after a short wait; contact Tesser support with the request_id if it keeps failing.</td>
    </tr>
    <tr>
      <td>`zuba-4000`</td>
      <td>502</td>
      <td>Zuba has a payout under this payment's reference that Tesser can't confirm as this payout: it already existed when Tesser sent it, there's more than one, or it doesn't match this payment. Its outcome is unknown and it may be paid. Don't create a new payment for these funds: check the payment's status, and contact Tesser support with the payment id if it doesn't resolve</td>
      <td>Tesser sends each Zuba payout under a reference tied to its step, so it is never paid twice. Zuba reported a payout already under that reference when Tesser sent it, or Tesser found two payouts under it, or one whose amount, currency or beneficiary differs from this payout. Tesser doesn't send it again and doesn't adopt a payout it can't match: the step stays unconfirmed while Tesser checks with Zuba, and Tesser support settles a payout that doesn't match. The payout may already have been paid. Don't create a new payment for these funds; check the payment's status and contact Tesser support with the payment id if it doesn't resolve.</td>
    </tr>
    <tr>
      <td>`zuba-5030`</td>
      <td>502</td>
      <td>Tesser couldn't complete this call to Zuba: Zuba didn't answer in time, answered with an error, or returned something Tesser couldn't use. Retry after a short wait; if a payout is involved, check the payment's status first, and contact Tesser support with the request_id if it keeps failing</td>
      <td>Zuba, or the service Tesser uses to send bank details to Zuba, didn't answer, answered with a server error or an unexpected status, or returned an answer Tesser couldn't use or that didn't match the request. It comes only from calls that move no money (reading payouts, deposits, wallets or onboarding data, requesting a quote, opening a deposit wallet, starting identity verification, approving a sandbox sub-account, uploading a KYB document) or from a payout or deposit that failed before it was sent. Retrying after a short wait is safe and usually works; contact Tesser support with the request_id if it keeps failing. When it comes from Tesser checking a payout it already sent, that payout's outcome is still unknown: Tesser keeps the step unconfirmed and checks again, so check the payment's status and don't create a new payment for those funds. A Kraken to Zuba payment that can't be priced waits with transfers-9114 and is priced again on the next balance change. A sandbox deposit step that fails this way before sending fails with transfers-9301; create a new payment.</td>
    </tr>
    <tr>
      <td>`zuba-5031`</td>
      <td>502</td>
      <td>Tesser couldn't confirm whether Zuba accepted this payout or the sandbox deposit that funds it: the request timed out or failed, or Zuba's answer couldn't be matched to it. It may still be paid, so Tesser keeps checking with Zuba. Don't create a new payment for these funds: check the payment's status, and contact Tesser support with the payment id if it doesn't resolve</td>
      <td>Tesser sent a payout, or a sandbox deposit that funds one, and can't tell whether Zuba accepted it: the call timed out, failed in transit or got a server error, Zuba's answer was unusable or didn't match what Tesser sent, Zuba refused a repeat of the request as different from the first, or the payout Tesser found can't be fully matched to this one. Zuba may have accepted it. Tesser never sends it again under a new reference: the step stays submitted while Tesser looks the payout up, and a payout from the Zuba ledger that stays unconfirmed is held for Tesser support with transfers-9209. A sandbox deposit whose outcome is unknown isn't sent again, because a second deposit would credit twice; Tesser support settles it. Don't create a new payment for these funds; check the payment's status and contact Tesser support with the payment id if it doesn't resolve. An onboarding step whose outcome is unknown returns zuba-3035 instead.</td>
    </tr>
    <tr>
      <td>`zuba-5032`</td>
      <td>409</td>
      <td>Zuba answered with a Zuba sub-account whose legal name, country or type differs from this KYB, usually because the organization's sub-account was already created at Zuba with other details. Tesser saved nothing. Send the KYB with the legal name and country of incorporation used the first time, or contact Tesser support; retrying with these details won't help</td>
      <td>Tesser creates each organization's Zuba sub-account under a key that is the same on every attempt, so Zuba returns the first sub-account it created for the organization even if the request changed. The sub-account Zuba returned has a different legal name or country than this KYB's businessInfo, or isn't a sub-account, so Tesser didn't record it and nothing was saved. Send the KYB with the legal name and country of incorporation used the first time and Tesser records the existing sub-account; if those details are unknown or wrong, contact Tesser support. Retrying with the same details won't help.</td>
    </tr>
    <tr>
      <td>`zuba-5033`</td>
      <td>502</td>
      <td>Zuba answered with a payout, deposit or wallet that belongs to another Zuba account, so Tesser didn't use it and is holding this payment until Tesser support confirms what happened at Zuba. This payout's outcome is unknown. Don't create a new payment for these funds: check the payment's status, and contact Tesser support with the payment id</td>
      <td>Zuba returned a payout, deposit or deposit wallet whose owner isn't the workspace's Zuba sub-account, or a lookup of this payout found only other accounts' payouts. Tesser doesn't adopt it and never sends the payout or deposit again: the step stays submitted until Tesser support confirms with Zuba which account owns it and whether this workspace's payout exists, then settles it; a payout from the Zuba ledger still unconfirmed at its deadline is held with transfers-9209. A deposit wallet answered this way isn't used, so the workspace's Zuba ledger isn't set up. Don't create a new payment for these funds; contact Tesser support with the payment id.</td>
    </tr>
  </tbody>
</table>
