Paybytoken SDKs
Choose the package that belongs in each part of your payment integration.
Paybytoken SDKs preserve the server/browser boundary while reducing the amount of payment infrastructure your application needs to own.
Choose a package
Merchant server
@paybytoken/node
Create sessions, retrieve payment state, confirm custom checkout and verify signed webhooks.
Browser
@paybytoken/checkout
Mount embedded checkout in any browser application and subscribe to lifecycle events.
React application
@paybytoken/react
Render embedded checkout with managed initialization, updates and cleanup.
Install the server package for every integration. Add one browser package only when you use embedded checkout.
Server
pnpm add @paybytoken/nodeEmbedded browser
pnpm add @paybytoken/checkoutFor React applications, install the React wrapper instead:
pnpm add @paybytoken/reactKeep credentials separated
@paybytoken/node receives a Core merchant secret and, when Router is enabled, a separate Payments
merchant credential. Both must run only on your server and are not interchangeable.
@paybytoken/checkout and @paybytoken/react receive only a session-scoped embedded checkout
credential created by your server.
Never import a merchant secret key into browser code, a public environment variable or a frontend bundle.
Continue with the Node SDK, Browser SDK, or React integration.
Did this page answer your question?
Your feedback helps us improve the integration path.