Supported assets and networks

Supported assets and networks are a runtime capability surface. A production integration should not hard-code example currencies, tokens, networks, confirmation counts, or min/max amounts; it should read capabilities and render only what the merchant account can use.

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: Read capabilities -> Filter merchant settings -> Render choices -> Create payment object -> Validate network -> Reconcile asset. 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 supported assets and networks. 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.

{
  "environment": "production",
  "payment_method": "crypto_wallet",
  "fiat_currencies": [
    "EUR",
    "GBP",
    "USD"
  ],
  "crypto_currencies": [
    "USDT",
    "USDC"
  ],
  "network": "capability_network",
  "confirmations_required": 3,
  "min_amount": "1.00",
  "max_amount": "5000.00"
}

Operational scenario

Asset/network mistakes are among the hardest payment issues to recover. Capability-driven rendering turns that risk into a predictable integration rule: if it is not active for the merchant, the customer should not be able to choose it.

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

Capability-driven assets and networks protect customers from wrong-chain and unsupported-payment mistakes. The safest payment option is the one the account can actually support at the time of checkout.

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/capabilities/payment_methods \
  -H "Authorization: Bearer $OBIT_SECRET_KEY"

Example response shape:

{
  "object": "list",
  "data": [
    {
      "object": "payment_method",
      "id": "crypto_wallet",
      "name": "Crypto wallet",
      "type": "crypto",
      "active": true,
      "currencies": [
        "EUR",
        "GBP",
        "USD"
      ],
      "crypto_currencies": [
        "USDT",
        "USDC"
      ],
      "networks": [
        "network_from_capabilities"
      ],
      "min_amount": "1.00",
      "max_amount": "5000.00"
    }
  ],
  "has_more": false,
  "url": "/v1/capabilities/payment_methods"
}

Implementation checkpoints:

• Read account and environment state before rendering or launching the product surface.
• 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

• Read capabilities at startup and before payment creation where appropriate.
• Do not hard-code example assets/networks.
• Apply min/max validation server-side.
• Separate payment and settlement capability lists.
• Store the capability snapshot used for checkout.
• Test unavailable network and inactive method paths.

Related pages