Settlement tracking
Track 0Gate session, transaction, webhook, and settlement-aware records without exposing provider or treasury internals.
Settlement tracking is the operational view of a 0Gate flow after the user has completed hosted steps. It joins your order or ledger record to 0Gate session ids, transaction refs, webhook event ids, request ids, timestamps, and, where your account is enabled, rail or settlement-aware records.
Tracking model
Records to store
| Record | Source | Why |
|---|---|---|
| Partner order id | Your backend | Primary id for your support and ledger. |
user_reference | Session create request and webhook data | Correlates 0Gate events to your record. |
| Session id | 0Gate session response | Anchors the hosted attempt. |
| Transaction ref | Completion event or transaction API where available | Helps investigate payment/ramp outcomes. |
local_rail_transaction_id | Transaction or receipt API where available | Rail-side reference for local payment or payout records. Prefer this over deprecated rail-specific aliases. |
| Event id | Webhook header or payload | Dedupe key and audit trace. |
| Request id | API response headers or error envelope | Useful for support escalation. |
| Environment | Key mode and API host | Prevents mixing sandbox and live records. |
What to show users
| User-facing state | Backend evidence |
|---|---|
| Pending | Session open, processing event, return URL reached without terminal backend event, or delayed delivery. |
| Completed | Verified completion event and your idempotent ledger update. |
| Failed | Verified failed event, unrecoverable API state, or manual support resolution. |
| Cancelled | Verified cancel event or your own cancellation action. |
| Expired | Session expires_at passed or expired event processed. |
Do not publish
- Provider identities, bank or rail internals, treasury operations, reserve movements, or reconciliation runbooks.
- Raw customer identity data, card/bank details, or provider payloads.
- Settlement SLAs, payout timing, or live availability that is not approved for the partner and market.
- Internal ledger table names, admin routes, or operator-only dashboards.
Support escalation package
When contacting support@0bit.io, include support-safe values:
- Partner account or environment.
- Your order id or
user_reference. - 0Gate session id.
- Transaction ref if present.
- Local-rail transaction id if present.
- Webhook event id and delivery id if relevant.
- Timestamp and symptom.
- Redacted request id or error code.