Deposit address flow

Use deposit-address style flows only where 0Base provider enablement is approved.

The deposit-address flow gives a customer payment instructions for a specific payment intent. It is useful for stablecoin-style payments, but it needs strict handling of network, address, expiry, confirmations, and received amount.

0Base availability is account-gated. Build against capabilities, merchant status, environment mode, and settlement settings instead of assuming that every payment method, asset, network, cadence, or refund path is enabled for every merchant.

0Base product docs and API details

These pages are public product guidance for merchant and platform developers. 0Base endpoint-level API pages are not published for partners yet; use this product documentation to understand the workflow, records, and launch boundaries.

End-to-end picture

This flow is intentionally shown as product infrastructure: Payment intent -> Create deposit address -> Show address and amount -> Detect payment -> Confirmations -> Terminal status. The merchant application can make the customer experience simple, but the backend should keep each step visible enough for retries, support, and finance closeout.

Production contract

Boundary	What to build	Why it matters
Intent binding	Create the deposit address from an existing payment intent.	The address belongs to a payable business object.
Network binding	Use only networks returned as available for the merchant/account.	Prevents wrong-chain payments.
Expiry binding	Display and store expiry.	Avoids late payments against stale instructions.
Confirmation binding	Track confirmations required and received.	Keeps pending state honest.
Amount binding	Store min, max, received amount, and payment hash where available.	Supports underpaid/overpaid recovery.

Status and state handling

State	What it means	Developer action
Active	Address can be shown to the customer.	Customer may pay.
Payment detected	Incoming payment signal exists.	Keep pending.
Confirming	Waiting for confirmations.	Do not assume finality.
Underpaid/overpaid/expired/failed	Recovery state.	Route to support or retry flow.

Status handling should be strict even when the customer UI is friendly. Store raw 0Base statuses, map them to customer-safe labels at the edge, and keep the merchant order state separate from the payment object state. That separation lets you change customer copy without corrupting reconciliation.

Example implementation record

This is an application-side record shape for deposit address flow. Keep exact request and response fields aligned with your enabled account contract when 0Base API access is released for your partner account; the point of this record is to keep product, support, and finance joined in your system.

{
  "payment_intent_id": "pi_live_456",
  "deposit_address_id": "da_live_789",
  "network": "capability_network",
  "address": "address_from_response",
  "status": "active",
  "expires_at": "2026-06-28T21:00:00Z",
  "confirmations_required": 3,
  "confirmations_received": 0
}

Operational scenario

A deposit page should show exactly one current set of instructions. If the address expires or the cart changes, the merchant should stop displaying old instructions and create a fresh payment path from the backend.

In practice, production 0Base integrations make the happy path fast while keeping exceptions predictable: retries return the same object, delayed notifications can be repaired, expired sessions do not become mystery payments, and finance exports can be traced back to the original merchant order.

Before and after

Before 0Base	With 0Base
Customers copied static addresses from documentation.	Addresses are created per payment intent where enabled.
Network mismatch was discovered after payment.	Network is chosen from capabilities before issuing instructions.
Confirmations were invisible.	The page can show pending/confirming using backend state.
Late payments had no evidence.	Expired address state and payment hash evidence are stored.

Evidence to keep

Evidence	What to store
Deposit record	Deposit address id, intent id, network, address, expiry, min/max.
Payment evidence	Amount received, payment hash, detection timestamp.
Confirmation evidence	Required confirmations, received confirmations, last update.
Instruction snapshot	What the customer saw and when.
Recovery note	Underpaid, overpaid, expired, failed, or manual support decision.

This evidence is what makes the integration supportable at institutional scale. A developer should not need private operational knowledge to answer basic questions such as what the customer saw, which object owns the state, which event announced the change, and which ledger or report row closed the money movement.

Failure modes and recovery

Failure mode	Recovery
Customer uses wrong network	Mark unresolved and route to support; do not mark order paid.
Payment arrives after expiry	Read current object state and follow late-payment policy.
Address page is refreshed	Re-read current address state instead of creating duplicates.
Confirmations stall	Show pending and keep support packet with payment hash.

Recovery should be idempotent and explainable. When the system is uncertain, preserve the current raw status, read the latest object state, attach a support reference, and avoid changing fulfillment or finance state until a trusted terminal condition is present.

API adjacency

API area	Use it for
`POST /payment_intents/{intentId}/deposit_address`	Create deposit address record.
`GET /payment_intents/{intentId}`	Read current status.
`GET /capabilities/networks`	Choose supported network.
`GET /webhooks/deliveries`	Trace status events.

For endpoint-level implementation, use the API reference as the source of truth for fields, enums, authentication, idempotency behavior, pagination, and response examples.

Why this matters for merchants and customers

Deposit-address flows are useful only when network and amount instructions are exact. 0Base gives developers a way to issue payment instructions tied to an intent instead of relying on static addresses and manual investigation.

At scale, the value of 0Base is not only that a payment can be created. The value is that the payment can be explained later: what the customer saw, which account capabilities allowed it, which backend state changed, which notification delivered it, and which ledger or report row closed it.

Worked API path

The example below shows the implementation shape for this page. Use merchant-specific capabilities, account settings, and API responses in production; the ids and values here are illustrative.

curl -X POST https://base-api-sandbox.0bit.app/v1/payment_intents/pi_test_456/deposit_address \
  -H "Authorization: Bearer $OBIT_SECRET_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: ord_100045:base:v1" \
  -d '
{}'

Example response shape:

{
  "deposit_address_id": "da_test_789",
  "intent_id": "pi_test_456",
  "status": "active",
  "address": "address_from_response",
  "network": "network_from_capabilities",
  "expires_at": "2026-06-28T21:00:00Z",
  "confirmations_required": 3,
  "confirmations_received": 0
}

Implementation checkpoints:

Store your merchant reference before calling 0Base.
Attach the returned object id to the same business record.
Record the request id, idempotency key, raw status, and environment.
Use webhook and report reads to repair delayed or missed state changes.

Data join map

This join map is the reason 0Base is infrastructure rather than a payment button. A merchant can change checkout UX, support tooling, or finance exports without losing the chain from customer action to backend state and settlement evidence.

Operator runbook

Signal	Check first	Action
Customer reports payment not updating	Look up merchant order id, 0Base object id, raw status, and latest webhook delivery.	Read current object state before changing fulfillment.
Webhook delivery failed	Check delivery id, event id, attempts, last error, and handler logs.	Fix the handler, replay once, and dedupe by event id.
Finance cannot match a row	Compare client reference, intent id, settlement id, report period, and export row.	Move the item to reconciliation queue instead of closing by amount/date.
Customer paid but order is still pending	Check raw intent status, deposit-address status, confirmations, and latest report row.	Keep fulfillment pending until terminal success or documented manual review.

The runbook should be available to support and finance teams before launch. A developer integration is not complete if only engineering can explain the state of a customer payment.

Developer checklist

Create deposit addresses only from a server-created intent.
Never hard-code example addresses.
Show expiry and network clearly.
Store confirmation counts.
Handle underpaid and overpaid states explicitly.
Hide expired instructions immediately.