Bit2Me APICrypto withdrawals (Wallet legacy)
Proforma, confirm that id, then Travel Rule with the operation id. Still live.
This page describes the published API. It is not legal advice. Bit2Me Legal and Compliance must review KYC, KYB, Travel Rule, and 2FA copy before this portal is announced to partners.
POST /v1/wallet/transaction/proforma and POST /v1/wallet/transaction are not marked deprecated. Prefer address book for new subaccount work. Sunset dates are not published.
This path is not the address-book draft. Do not decide Travel Rule from an address-book accept status. Address book does not call travel-rule-order.
| Branch | What it is | Required when | Skip when |
|---|---|---|---|
| Travel Rule | POST /v2/blockchain-manager/travel-rule-order/{orderId} with the operation id from execute. Not Embed report. | Operation status is pending_user_information | Any other status |
| Destination verification | Confirm the on-chain destination for this movement (deprecated pair) | isVerified: false | Already verified, or GET stays 404 |
POST /v1/wallet/transaction/proformatype: SEA = send exact amount (pocket debited amount + network fee). If omitted, REA (receive exact amount). The address-book draft does not take type. Network list REST paths are not in this snapshot — use the network field the address-book or currency catalog already returns. No 2FA on the quote.
POST /v1/wallet/transactionBody field proforma is the quote id from step 1. Headers x-totp and x-totp-type: gauth. The 200 returns the operation id. That id is not the proforma id. Use it for Travel Rule and for GET /v1/wallet/transaction/{id}.
GET /v1/wallet/transaction/{id}{id} is the operation id from execute. Read status. pending_user_information means you must submit Travel Rule. Do not use a blockchain-manager order id from the address-book path on this GET.
POST /v2/blockchain-manager/travel-rule-order/{orderId}{orderId} is the operation id from execute, not the proforma id. Call it only when GET /v1/wallet/transaction/{id} returned pending_user_information. Do not use Travel Rule v1. This step is not part of address book.
OpenAPI marks this pair deprecated in favour of address-book confirm.
GET /v1/compliance/blockchain-address-confirmation/wallet-movement/{walletMovementId}. Confirm with 2FA only if isVerified: false. Persistent 404 means confirmation is not required for that movement.
HTTP map on this path: 401 email not verified; 412 pocket funds; 417 amount; 420 invalid 2FA; 423 blocked (case-specific); 428 2FA required (stablecoins); Travel Rule 409 wrong status.