Paybytoken Pay private beta
Understand the controlled consumer-authorized balance payment method.
Paybytoken Pay lets an authenticated Paybytoken consumer approve a payment from finalized funds in their Paybytoken balance. It is a private beta, not a generally available payment method. Access is granted for specific merchants, consumer accounts, chains and assets. Live mode remains disabled until Paybytoken completes the applicable custody, identity, compliance, legal and security gates.
Paybytoken Pay uses the same PaymentIntent, PaymentAttempt, Refund and signed webhook lifecycle as stablecoin transfer payments. It does not create a second merchant accounting model.
Ownership boundary
| Participant | Owns | Must not do |
|---|---|---|
| Merchant server | Order, Customer, PaymentIntent, handoff creation, fulfillment and refund | Confirm a consumer debit or expose a secret key in the browser |
| Paybytoken consumer | Authentication, merchant-link consent and payment approval | Share a bearer token or hosted capability with the merchant |
| Paybytoken | Consumer UI, finalized-balance authorization, atomic settlement and signed events | Expose global consumer balances or unrelated merchant activity |
The Merchant Portal may show a reduced handoff state and a stable failure category. It never shows the consumer's global balance, authentication identity, other merchant links, access token or hosted fragment capability.
Availability
Your server can create this payment method only when Paybytoken has enabled the exact merchant, chain and currency. The consumer must also be eligible for the same asset. Test and live data are isolated. A test-mode approval never enables live mode.
Use the Portal's Settings → Money movement → Payment methods page to inspect merchant readiness. Controls and live enablement are managed by Paybytoken during the private beta; they are not self-service.
Payment lifecycle
- Create an active merchant Customer linked to the consumer's Paybytoken Account.
- Create a PaymentIntent with
payment_method_types: ["paybytoken_pay"]from your server. - Create a short-lived ConsumerPaymentSession and redirect the customer to its one-time hosted URL.
- Treat the browser return as navigation only.
- Fulfill only after a verified
payment_intent.succeededwebhook or authenticated server lookup. - Use the existing Refund API for full or partial refunds to the original consumer balance.
Continue with Create the consumer handoff.
Did this page answer your question?
Your feedback helps us improve the integration path.