Core concepts

The core 0Base concepts are deliberately small: merchant order, checkout or link surface, payment intent, optional deposit-address record, webhook delivery, settlement ledger, and report. A strong integration keeps those objects distinct instead of collapsing them into one status column.

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.

End-to-end picture

This flow is intentionally shown as product infrastructure: Merchant order -> Checkout/link/invoice -> Payment intent -> Deposit address or customer payment -> Webhook delivery -> Settlement ledger. 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

Status and state handling

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 core object model. 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.

{
  "merchant_order_id": "ord_concepts_001",
  "checkout_id": "chk_...",
  "payment_intent_id": "pi_...",
  "deposit_address_id": "da_...",
  "event_id": "evt_...",
  "settlement_id": "set_...",
  "report_period": "2026-06"
}

Operational scenario

A developer should be able to answer one question from each layer: what did the customer buy, what 0Base object collected payment, what raw status does it have, which event delivered that status, and which ledger row or report confirms the finance side.

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

Evidence to keep

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

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

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

Clear concepts reduce operational risk. When developers separate merchant orders, payment objects, webhook deliveries, and ledger rows, customers get clearer payment states and merchants avoid support processes built from screenshots and guesswork.

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 GET https://base-api-sandbox.0bit.app/v1/payment_intents/pi_test_456 \
  -H "Authorization: Bearer $OBIT_SECRET_KEY"

Example response shape:

{
  "intentId": "pi_test_456",
  "status": "processing",
  "amount": "89.00",
  "currency": "EUR",
  "cryptoCurrency": "USDT",
  "clientReference": "ord_100045",
  "conversionTxId": "conv_test_123",
  "quotedRate": "1.08450000",
  "cryptoAmount": "96.52000000"
}

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

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

• Name the owner of each state field.
• Store raw 0Base status values.
• Keep client references unique enough for support.
• Join events to payment objects before applying business effects.
• Treat reports as reconciliation, not the only status source.
• Document which objects your product uses before launch.

Related pages