0Base checkout object boundaries
Understand the 0Base object model without assuming live production checkout behavior is enabled.
0Base is the merchant-checkout object surface for payment intents, checkout objects, links, reports, and webhook planning. Availability depends on account enablement; do not assume live money movement unless 0Bit has explicitly enabled 0Base for your account.
Do not present 0Base as a live checkout path
Keep live public checkout traffic on approved 0Gate flows unless your 0Bit account is enabled for 0Base. Do not promise live 0Base rails, settlement behavior, refunds, or provider behavior from this guide alone.
Product boundary
Object map
| Object | What it represents | Public-safe wording |
|---|---|---|
| Checkout | A merchant-facing checkout container. | "Review the checkout object shape and lifecycle." |
| Payment intent | The merchant's expected payment action. | "Bind amount, currency, reference, and status before fulfillment." |
| Payment link | A reusable or shareable entry point concept. | "Review link behavior before publishing customer-facing claims." |
| Report | Reconciliation and audit output. | "Use reports to plan finance and support workflows." |
| Webhook delivery | Outbound event delivery concept. | "Treat signed backend events as durable state once approved." |
Implementation shape
- Decide whether the customer flow is actually 0Gate, not 0Base.
- Map the 0Base object you are discussing to one business record in your system.
- Mark every unsupported or unavailable behavior as not enabled for your account.
- Avoid endpoint-level examples that are not in the product API reference you use.
- Use fake references, fake customer data, and no provider or settlement internals in review examples.
type BaseReviewRecord = {
reviewId: string;
objectKind: 'checkout' | 'payment_intent' | 'payment_link' | 'report' | 'webhook_delivery';
businessReference: string;
availabilityStatus: 'planning_only' | 'enabled_for_account' | 'not_available';
notes: string[];
};
function classifyBaseUseCase(input: { needsLiveCheckout: boolean }) {
if (input.needsLiveCheckout) {
return {
productPath: '0gate',
reason: '0Base is review-bound for this documentation set',
};
}
return {
productPath: '0base_review',
reason: 'object planning only',
};
}Developer guardrails
| Do | Avoid |
|---|---|
| Say that 0Base availability depends on account enablement. | Saying 0Base currently moves money for every public partner. |
| Describe object ownership and reconciliation concepts. | Using endpoint contracts or live checkout examples not in your product reference. |
| Route public payment flows back to 0Gate. | Promising refunds, settlement timing, or provider behavior. |
| Keep provider and settlement details out of examples. | Exposing provider names, internal configs, env keys, or data models. |