How it works
The core model — predicted addresses, detection vs. settlement, why there's no refund API. Read this first.
Keep Liquidity Always Permissionless. A merchant creates a charge, the payer sends funds directly to a predicted on-chain address, Klap detects and distributes it — without ever holding the money itself. This site covers the REST API, the Node.js SDK, and the TypeScript types together, by resource.

One doc, organized by resource — not three separate sites for the API, the Node.js SDK, and @klappay/types. Every resource page below covers all three together: the concept, the REST endpoints, the SDK methods, and the types, so you don't have to cross-reference three tabs to build one integration.
For the interactive request builder (try-it, auth, generated curl), use the API Playground — that stays a separate tool on purpose, this site is for reading, not for firing live requests.
Not sure where to start? How it works covers the non-custodial model in 5 minutes, Getting started covers installing the SDK and creating your first charge, and Build a checkout flow walks the whole thing end to end — charge, hosted checkout, webhook, confirmation.