.Klappay

Non-custodial

They pay
You receive
We never hold

Any wallet, any chain, anywhere. Each charge gets its own on-chain address, your customer pays into it, and the funds never pass through us

Start building
Ethereum
Base
Optimism
Arbitrum
Polygon
Avalanche
BNB Chain

Payments that move
Control that stays yours

We handle the payment plumbing
You own the experience, from the first API call to the final settlement

01 / CREATEON-CHAIN
USDCUSDT

Your checkout, all the way

No hosted checkout. You build the payment UI inside your own product

02 / PAYSPLIT
PAYMENT
95%5%

Split at the source

Add multiple recipients to a charge. Revenue splits on-chain, no payout queue

03 / SETTLENON-CUSTODIAL

Straight to your recipients

We detect and route. Funds go from payer to recipient, never through us

checkout.ts
const charge = await klap.charges.create({
  amount: 49.9,
  expiresIn: 900,
  acceptedPayments: [
    { token: 'USDC', network: 'base' },
  ],
})


console.log(charge.address)
INTERACTIVE EXAMPLE
READYSIMULATED RESPONSE

Run the example to follow a payment.

One API call
A whole new payment flow

Create a charge, get a payment address, and let your customer pay — keep building what makes your product different

  • ✓A typed Node.js SDK
  • ✓API and SDK types from one shared schema
  • ✓Sandbox events without a real transaction
See the full integration guide →

One API, a growing suite of products

The Core API is the foundation — everything above it ships as a standalone product

LIVE

Klappay Core

The non-custodial payments API — charges, distributions, and webhooks for any crypto checkout.

BUILDING

Klappay Link

Shareable payment links and product pages — create one from a dashboard, get paid non-custodially, no API integration required.

COMING SOON

Klappay Fund

Pooled fundraising with on-chain, non-custodial escrow.

COMING SOON

Klappay Give

Tipping and donations, split and settled non-custodially.

COMING SOON

Klappay Recurring

Subscription and recurring billing on crypto rails.

COMING SOON

Klappay One

One button, one wallet for every payment address you own — approve from a push notification, wherever you are.

And much more

A few examples of what's next:

  • Klappay Commerce — Embeddable checkout widget for your site or app.
  • Klappay Payroll — Pay your team globally in USDC, on a schedule.
  • Klappay Streams — Pay by the second — continuous money flow.

The payment layer
Without the gatekeeper

Your funds don't need a middleman
Your developers don't need more workarounds

Custody
Others —Funds pass through the provider’s account before reaching you.
Klappay —Never. Funds go straight to the on-chain split address.
Integration
Others —Hosted widget/iframe — you adapt your product to it.
Klappay —Pure API. Your checkout, your design, your UX.
Split payments
Others —Bolted-on feature, usually gated or priced separately.
Klappay —Native: a multi-recipient address ships with every charge.
Real-time status
Others —Manual polling or a single webhook, no native stream.
Klappay —SSE + webhooks + charge.waitForConfirmation() in the SDK.
Sandbox
Others —Testnet-only when it exists — slow, brittle setup.
Klappay —Simulate any charge event without touching a real chain.
Types
Others —Types maintained by hand, tend to drift from the real API.
Klappay —API and SDK share the same Zod schema. Never drifts.
Refunds
Others —A chargeback exists, but only because your funds sat in the processor’s custody first.
Klappay —No automatic reversal — it settles on-chain and the payer is never a split recipient. You decide the remedy: partial delivery, manual refund, or credit.
Comparison of payment models — individual providers vary.