Evaluating Klap

Know what you're buying,
before you integrate

Comparing stablecoin payment providers? Start with which parts of the flow each one actually runs. Here is that answer for Klap, including what we don’t do.

The legs we own

Klap runs the on-chain leg end to end, with no partner in between. The fiat leg is yours or a ramp partner’s.

Klap runs it

  • Creating the charge and its expiry
  • Predicting the charge address before anyone pays
  • Detecting the transfer on-chain
  • Waiting out each network’s confirmation depth
  • Paying out the split to every recipient
  • Signed webhooks and live event streams

You or a partner run it

  • Fiat on-ramp and off-ramp
  • Bank payouts and local currency
  • KYC, KYB and AML on your customers
  • Travel Rule and sanctions screening
  • Refunds outside escrow, from your own wallet

Routes live today

Live means a real payment settles on mainnet right now, not a planned integration.

NetworkUSDCUSDT
  • Ethereum
  • Base
  • Optimism
  • Arbitrum
  • Polygon
  • Avalanche
  • BNB Chain
  • Arc—
One charge can accept several of these routes at once, on the same address. No fiat rails. TRON is in progress.

Six questions, answered plainly

The criteria buyers use to compare stablecoin providers, with our real answer to each, gaps included.

Workflow fit

What does every status look like, including the stuck ones?

  • A charge is pending, partially_paid, confirmed, expired or underpaid. Each one is reached automatically, and an overpayment still confirms, with isOverpaid set.
  • Payout is tracked on its own, as settlementStatus: pending, completed or failed. “The customer paid” and “the money reached you” are two separate events.
  • A transfer that lands after expiry is still credited. It never disappears.

Klap never holds funds, so it can’t reverse a payment. Outside escrow, refunds go out from your own wallet.

Coverage

Which routes are live today, and who runs each leg?

  • USDC and USDT on eight EVM networks, listed in the table above. Arc is USDC only, since USDT isn’t issued there.
  • Klap runs every on-chain leg itself, on public 0xSplits contracts. No partner sits between the payer and you.
  • Before creating a charge, Klap reads each token issuer’s on-chain freeze status and refuses a route that couldn’t pay one of its recipients.

No fiat rails. TRON is in progress and not live yet.

Route economics

What does a payment cost, all in?

  • 1% per settled payment. No monthly fee, no setup fee, no minimums, no prefunding.
  • No spread and no FX: the payer sends the stablecoin you priced in, and you receive that same stablecoin.
  • Anyone who settles a payout earns a 0.1% incentive, and it comes out of Klap’s 1%, not out of your share.

The payer pays network gas for their own transfer. On Arc, that gas is paid in USDC.

Operational visibility

What do delayed, failed and retried payments look like?

  • Every status change goes out as an HMAC-signed webhook, delivered in up to five attempts over about a day, plus a live stream over SSE.
  • Each event carries a stable id, so a retried delivery is easy to deduplicate.
  • In test mode you can push a charge into any state, including partial payment, overpayment, expiry and a failed payout, and watch your handler react.
  • Every payment and payout links to its transaction on a public block explorer.

We don’t publish failure rates yet. We’d rather show real numbers once closed beta has enough volume to mean something.

Compliance

Which compliance work stays with you?

  • Klap is non-custodial software. It never holds funds or keys, so there is no custodial leg to license or audit.
  • Issuer freezes are respected before a charge is created, not discovered after a payout fails.

KYC, AML, Travel Rule and sanctions screening on your customers stay with you or your ramp partner.

Lock-in

What happens to your money if you leave?

  • Nothing. There is no Klap balance to withdraw. Each charge is an ownerless 0xSplits contract that can only pay out to its recipients.
  • distribute() is public. If Klap went offline tomorrow, anyone could still settle a payment that already arrived.
  • A charge is just an address, so running Klap next to another provider breaks nothing. Your full history stays on a public chain.

When Klap is not the right fit

  • You need to pay out to bank accounts in local currency.
  • You want a provider to hold balances on your behalf.
  • You need card acceptance.
  • You need TRON today.

Most production setups combine two or three providers. If you pair Klap with a ramp partner for the fiat leg, the on-chain leg stays non-custodial end to end.