Skip to main content
Transactions in Byzantine are always two-step: you request a payload or an action, then submit the signed payload to execute it on-chain. The exact endpoints depend on whether the user authenticates with Passkey (WebAuthn).

​
What you can do

  • Deposit — Deposit can be made in stablecoins or fiat. Fiat deposits also involve on-ramping via a dedicated bank account. See Deposit and Deposit (technical).
  • Withdraw — Move funds out of a vault to stablecoins or to a bank account (off-ramp). No vault approval is needed; withdrawals use the same two-step pattern and are available at any time. See Withdrawal and Withdrawal (technical).
  • Account balances and idle — Balances in the vault earn yield; stablecoins left in the user’s secure wallet are idle balance and do not. Idle balance can be deposited manually into the vault later. See Account balances & idle.

​
Two-step pattern

  1. Prepare — Call the appropriate “get payload” or “init” endpoint (e.g. get deposit payload, initiate withdrawal). For passkey, they sign the payload in your app.
  2. Submit — Call the submit endpoint with the signed payload. Byzantine then broadcasts and executes the transaction (or, for fiat deposits, waits for funds and then executes).
Transactions go through the following statuses:
  • created: The transaction has been created and is waiting to be signed.
  • waiting_for_funds: The transaction has been signed. The system is waiting for the bank transfer to trigger the broadcasting of the transaction.
  • funds_in_transfer: The funds have been scheduled to arrive with Bridge soon.
  • processing: The funds have arrived with Bridge and are currently being on-ramped.
  • completed: The transaction has been broadcasted and executed.
The transaction status can be checked by calling the Get transaction status endpoint.
For full request/response details, use the Transactions with passkey section in the API endpoints, together with Authentication methods.