0Gate transactions
List and retrieve partner transaction records for hosted 0Gate sessions, support lookup, settlement review, and webhook reconciliation.
0Gate transaction endpoints are read paths for partner transaction records. They help your backend and support tooling connect session state, user-visible status, signed webhook events, asset movement, fees, and settlement records.
Endpoints
| Method | Path | Operation id | Purpose |
|---|---|---|---|
GET | /transactions | listTransactions | List partner transactions. |
GET | /transactions/{refid} | retrieveTransaction | Retrieve a transaction by reference id. |
Retrieve by reference
curl -X GET https://gate-api-sandbox.0bit.app/v1/transactions/tx_test_123 \
-H "Authorization: Bearer sk_test_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"Use transaction reads when a webhook was delayed, a user refreshed after redirect, support needs a single record, or operations need to join a payment flow to settlement reporting.
Transaction fields
| Field | Use it for |
|---|---|
refid | Stable transaction lookup key. |
session_id | Join to hosted session. |
action | Buy, sell, swap, pay-in, pay-out, or equivalent product action. |
status | Current transaction state. |
token / network | Asset and network context. |
currency | Fiat currency context. |
payment_method | User-visible method category where approved. |
fiat_amount / token_amount | Reconciliation amounts. |
exchange_rate | Partner-visible rate context where approved. |
total_fees | Fee context where approved. |
local_rail_transaction_id | Rail-side transaction id for local payment or payout records. |
Older local-rail records may also include facilita_transaction_id. Treat it as a deprecated compatibility alias for local_rail_transaction_id; store the generic field in new integrations.
Reconciliation flow
Support checklist
When investigating a transaction, capture:
- partner order id
- 0Gate session id
- transaction
refid - webhook event id
- request id from the API call
- asset symbol and network
- fiat currency and amount
- current status and timestamps
Do not ask users to provide secret keys, webhook secrets, full signature headers, raw PII-heavy payloads, or screenshots containing credentials.