Branding and checkout settings

Branding and checkout settings are operational configuration, not decoration. They control what customers see at the moment of payment, which methods are offered, how support is reached, and how the merchant presents trust while 0Base preserves the payment object lifecycle.

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 settings -> Capability constraints -> Checkout page -> Customer state copy -> Support route -> Change log. 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 branding and checkout settings. 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_id": "mrc_2048",
  "brand_display_name": "Merchant Ltd",
  "support_email": "payments@example.com",
  "return_url": "https://merchant.example/checkout/return",
  "enabled_methods": [
    "crypto_wallet"
  ],
  "settings_state": "approved"
}

Operational scenario

A clean branded checkout should reduce customer doubt while making payment rules clearer. It should not introduce hidden promises, unsupported assets, or confusing return URLs.

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

Checkout settings determine customer trust and payment availability. Good settings keep the checkout professional while preventing unsupported methods, wrong return URLs, or confusing support paths.

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/checkouts \
  -H "Authorization: Bearer $OBIT_SECRET_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: ord_100045:base:v1" \
  -d '
{
    "amount": "129.00",
    "currency": "EUR",
    "cryptoCurrency": "USDT",
    "clientReference": "ord_100045"
}'

Example response shape:

{
  "checkout_id": "chk_test_123",
  "status": "open",
  "amount": "129.00",
  "currency": "EUR",
  "crypto_currency": "USDT",
  "payment_intent_id": "pi_test_456",
  "checkout_url": "https://checkout.0bit.app/c/chk_test_123",
  "expires_at": "2026-06-28T21:00:00Z"
}

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

• Review settings per environment.
• Treat return URLs as UX only.
• Gate methods by capabilities.
• Store change history.
• QA every visible state.
• Keep rollback settings ready.

Related pages