Bit2Me APIMoney flow
How value moves between Wallet, Pro, Earn, and funding rails.
How money moves in the different transaction types. Use this page as a map; the live numbers always come from pockets, Pro balances, and teller orders.
| Rail | Guide |
|---|---|
| Fiat deposit | Fiat funding, Apple Pay / Google Pay |
| Wallet ↔ Pro | First order — POST /v1/trading/wallet/deposit and POST /v1/trading/wallet/withdraw |
| Spot orders | Same page, POST /v1/trading/order |
| Buy / sell in Wallet | Buy, sell, and swap |
| On-chain out | Address book withdrawals (verify destination first time; no separate Travel Rule call). Travel Rule only on Wallet legacy when the operation asks |
| Bit2Me user | Transfers (Social Pay: email, phone, alias). Last mile: Argentina only |
Fees and pocket debits of each operation come from the REST responses.
Loans
Crypto-backed loans: simulate LTV, create an order, increase guarantee, pay back.
Sign in with API key POST
Authenticates a user using an API key and returns a JWT access token. The API key must be sent via the `ApiKeyAuth` security scheme. The request body carries the `userId` that the key belongs to. On success the response contains an `accessToken` with its expiration timestamp.