Vybe Checkout

Crypto checkout.
Agents can pay too.

Native Checkout into Collect: create a session, share a URL with humans, copy the same catalog for agents. One balance — no leap to full agentic commerce.

Create checkout

Free to open. 1.5% on payment requests.

See the API
Native Checkout sessions API Humans pay the link · agents pay the catalog USDC & USDT · Base, Ethereum, BNB

Payment

Pay with
Vybe walletUSDC / USDT
BaseEthereumBNB
Sessioncs_live_…9fQ2Kd
Pay $150.00

By paying, funds settle to @alex on Vybe. Humans use this page · agents use the catalog.

The gap

Most stacks jump from “checkout” to “agentic.” That’s too far.

Businesses already know hosted sessions. Give them Native Checkout first — then let the same catalog speak to agents.

Hosted checkout you already understand

Create a session, redirect to a URL, listen for webhooks. Jumping from that to full agentic commerce is a rewrite most teams won’t do.

Agents need a catalog, not a form

A checkout page works for people. Machines need prices and pay intents they can read — without a second billing stack.

Crypto shouldn’t mean a second ledger

Stablecoin rails are fine. A separate wallet, dashboard, and reconciliation job is not. Money should land next to everything else you collect.

Native Checkout API

Sessions, hosted URL, webhooks — built for Collect.

POST /api/checkout/sessions returns a hosted url for people — plus catalog_url and agent_pay_url so an agent can settle the same SKU.

  • Secret key auth: Bearer vybe_col_…
  • line_items[].price = Collect offering id
  • Retrieve with GET /api/checkout/sessions/:id
  • Fulfill on Collect payment.paid webhooks
Get an API key
Integration guide
Create sessioncurl
curl https://www.vybe.finance/api/checkout/sessions \
  -H "Authorization: Bearer vybe_col_…" \
  -H "Content-Type: application/json" \
  -d '{
    "mode": "payment",
    "line_items": [{ "price": "svc_9fQ2Kd", "quantity": 1 }],
    "success_url": "https://yoursite.com/thanks",
    "cancel_url": "https://yoursite.com/cart"
  }'
Response201
{
  "id": "pr_…",
  "object": "checkout.session",
  "status": "open",
  "payment_status": "unpaid",
  "url": "https://www.vybe.finance/r/pr_…",
  "amount_total": "50",
  "currency": "usdc",
  "catalog_url": "https://www.vybe.finance/api/agent/collect/you",
  "agent_pay_url": "https://www.vybe.finance/api/agent/collect/you/svc_9fQ2Kd"
}
One session, two buyers

Humans get a link. Agents get a catalog.

Human checkout

Redirect to session.url — hosted pay on /r/…. Wallet settles USDC or USDT. Same request object Collect already uses.

Feels like hosted Checkout

Agent catalog

Copy catalog_url into the agent. It reads prices, hits HTTP 402 / x402 on agent_pay_url, and pays the same offering — no DM, no second invoice.

No rebuild for agents

How it works

Three steps. Native Checkout.

01

Create products (offerings)

Publish prices on your Vybe service page — the same catalog humans and agents see.

02

Create a Checkout Session

POST /api/checkout/sessions with your Collect API key. Get back a hosted url for Native Checkout.

03

Share the link — or the catalog

Humans open session.url. Agents get catalog_url / agent_pay_url. Same SKU. Same balance when paid.

Native Checkout model

What maps to what.

Concept

Products / prices

Vybe Native Checkout

Collect offerings on your service page

Concept

Create checkout session

Vybe Native Checkout

POST /api/checkout/sessions

Concept

Hosted pay URL

Vybe Native Checkout

Hosted pay link /r/{id}

Concept

Buyer pays

Vybe Native Checkout

Human pays USDC/USDT · agent pays via HTTP 402

Concept

Webhooks

Vybe Native Checkout

payment.paid on your Collect webhook

Concept

Secret API key

Vybe Native Checkout

Collect API key vybe_col_…

FAQ

Straight answers

Is this a fourth Vybe product?

No. Native Checkout is Collect’s merchant-facing door — crypto get-paid with hosted sessions. Agents are a capability of the same catalog, not a separate product.

Do I need to rebuild for agents?

No. Create offerings once. Humans use the session URL. Copy catalog_url for any agent that can hit HTTP APIs.

Is settlement fiat cards?

No. Settlement is USDC and USDT on Base, Ethereum, and BNB (x402 or verified tx). Same rails as Collect.

How do I get an API key?

Sign in → web desk → Collect → create a Business Collect key (vybe_col_…). Use it as Authorization: Bearer.

What about express middleware?

Gate your own API with npm i express-vybe-402 — same offerings, HTTP 402 until paid. Checkout Sessions are for hosted / redirect flows.

Digging into Collect for freelancers? Vybe Collect · Developers · Integration guide

Ready

Ship Native Checkout. Same balance as Collect.

Create a Collect key, publish an offering, open a session — then share the URL or copy the catalog for agents.

Create checkoutSee Collect for sellers