What is 0Gate?

0Gate is the hosted 0Bit product surface for ramp, swap, embed, redirect, and session-based hosted payment flows. Use it when your application needs a public developer path where your server controls the order intent and the hosted 0Gate experience controls the user-facing ramp, verification, payment, and completion journey.

The core integration is server-led. Your backend creates a 0Gate session with a secret key, binds the amount, currency, return URL, optional flow, destination constraints, user reference, and metadata, then sends only the browser-safe client_secret to the client. The browser mounts the hosted widget, kit block, or redirect with a publishable key. Your backend treats signed webhooks as the durable signal for fulfillment and reconciliation.

What 0Gate is for

Product model

0Gate separates responsibility deliberately:

Endpoint groups

The product pages intentionally avoid becoming a full operation reference. Use them to understand the product shape, then use the API reference for exact request and response contracts.

Minimal server pattern

import { GateClient } from '@0bit/gate';

const gate = new GateClient({
  apiKey: process.env.GATE_KEY,
  baseUrl: 'https://gate-api-sandbox.0bit.app',
});

export async function createCheckoutSession(order: {
  id: string;
  amount: string;
  currency: string;
}) {
  const session = await gate.sessions.create(
    {
      amount: order.amount,
      currency: order.currency,
      return_url: `https://app.example/orders/${order.id}/return`,
      cancel_url: `https://app.example/orders/${order.id}/cancelled`,
      user_reference: order.id,
      metadata: { order_id: order.id },
    },
    { idempotencyKey: `order_${order.id}` },
  );

  return {
    sessionId: session.id,
    clientSecret: session.client_secret,
  };
}

Keep this pattern strict: secret-key work on the backend, browser-safe values in the client, signed webhooks for fulfillment, and support-safe logs for operations.

What not to expose

0Gate public docs should not describe:

• Internal admin routes, deploy runbooks, environment variables, provider credentials, or service-to-service secrets.
• Provider selection, liquidity routing, reserve allocation, treasury refill logic, or internal settlement automation.
• Raw identity documents, KYC vendor payloads, screening thresholds, or jurisdiction-specific legal reasoning.
• Contractual fee, spread, rebate, revenue-share, SLA, or support-tier values unless they are approved for the specific partner.
• 0Pools, 0Base, or 0Link endpoint details inside 0Gate pages unless the page is only explaining a boundary.

Related pages