Start with one payment.
Create the order on your server, present checkout in your product, and fulfill only after a verified event.
- 1
Create a sessionServer only
- 2
Open checkoutCustomer browser
- 3
Verify the eventYour webhook
Start from the business obligation.
Checkout is an attempt. Links, requests, and balances exist for longer-lived collection models. Choose the owner first, then the customer interface.
Checkout Session
Create one short-lived customer attempt with hosted, embedded, or custom presentation.
→ReusablePayment Link
Publish fixed or customer-entered collection without creating every order first.
→ReceivablePayment Request
Track one known amount across reminders, retries, partial payments, and reconciliation.
→Persistent fundsCustomer balance
Provision deposits and exact-asset balances for later payments and withdrawals.
→The shortest path to a verified payment.
These boundaries stay the same for hosted, embedded, and custom checkout. Start here before choosing how much UI you want to own.
- 01
Install the server SDK
Keep the secret key in your server runtime.
pnpm add @paybytoken/node - 02
Create a Checkout Session
Send an authoritative amount or line items.
checkoutSessions.create() - 03
Present checkout
Redirect, mount the managed UI, or render your own.
hosted · embedded · custom - 04
Verify the payment event
Fulfill once after signature verification.
payment_intent.succeeded
Go directly to the work in front of you.
Each guide starts with the required boundary, gives you the implementation path, and links to the relevant API contracts.
Complete a first payment
Create a server-owned order and finish one end-to-end test payment.
→Managed UIMount embedded checkout
Keep the customer on your page with the browser or React SDK.
→RedirectLaunch hosted checkout
Send the customer to a Paybytoken-hosted, responsive payment page.
→Your UIBuild custom checkout
Own token selection and transfer presentation using session primitives.
→FulfillmentVerify signed webhooks
Authenticate terminal events and make order fulfillment idempotent.
→OperationsTest and troubleshoot
Understand origin rules, credential boundaries, failures, and recovery.
→When you already know what you need.
Jump directly to resource contracts, packages, event payloads, and error behavior.
Checkout Sessions
Create, retrieve, and confirm the resource behind every UI.
Choose your runtime
Use isolated server, browser, and React packages.
Inspect payment events
Retrieve event payloads and build reliable fulfillment.
Handle API errors
Read the error envelope, codes, and retry guidance.
Browse every endpoint
Inspect the generated merchant, public, consumer, and operator API inventory.
Customer deposits and withdrawals
Understand persistent addresses, exact-asset balances, fees, and asynchronous state.
See each checkout mode with a real test order.
Compare hosted, embedded, and custom integrations before choosing the surface for your product.