Build swap experiences
Use 0Pools to power swaps such as 0EUR to USDT or USDT to 0BRL inside your product.
Use 0Pools to power swaps such as 0EUR to USDT or USDT to 0BRL inside your product.
Documentation boundary
Use-case pages help readers choose the right 0bit product surface. They should route to product docs for implementation detail and avoid promising general availability, specific regional support, reserve guarantees, provider behavior, or legal outcomes.
What this page covers
- Build swap experiences
- Product ownership, record joins, and launch boundaries
- Product events, status ownership, and reconciliation joins
How it fits
Use-case pages help readers choose the right 0bit product surface. They should route to product docs for implementation detail and avoid promising general availability, specific regional support, reserve guarantees, provider behavior, or legal outcomes.
Workflow
- Pick the primary user action and owning product.
- Add adjacent product records only when the workflow needs them.
- Capture request ids, object ids, event ids, timestamps, assets, and environment from the beginning.
- Add webhook, idempotency, and reconciliation before launch.
- Confirm access, region, entitlement, and review status with the right owners.
Status and data signals
| Signal | Use it for | Do not use it for |
|---|---|---|
| Product mix | Which 0bit surfaces are involved. | Feature promise. |
| User action | Payment, swap, link, dashboard, or asset workflow. | Internal operator task. |
| Operations link | Where reconciliation happens. | Private runbook. |
| Review status | What needs human approval. | Legal guarantee. |
Implementation notes
- Start in sandbox or test mode with fake data.
- Keep server-only credentials, webhook secrets, PII, provider payloads, and internal runbooks out of public docs and browser code.
- Use documented ids, request ids, event ids, timestamps, status fields, asset symbols, and environment names for support and reconciliation.
- Treat browser callbacks as user-experience signals; use signed webhooks, API reads, scan records, or settlement reports for durable backend state.
- Confirm product access, entitlement, regional availability, and review status before presenting the workflow as live.
Related pages
Products
Choose the product area that owns the workflow.
Architecture
Open Architecture for the related implementation details.
Guides
Follow task-based guides for the implementation sequence.
Test and go live
Use the launch checklist before switching to production credentials.
Example trace
A use case becomes implementation work only after the owning product is clear. Payment apps start with 0Gate, swap experiences start with 0Pools, protocol dashboards start with 0Base and 0Pools Scan, and connected finance flows use 0Link to join surfaces. Once the owner is selected, stay inside that product's sidebar for quickstart, concepts, architecture, authentication, and build pages before adding cross-product links.