Skip to main content
Cherp is a payment infrastructure API and SDK enabling peer-to-peer and merchant-to-consumer stablecoin payments on Solana, Base, and Tempo.

​
What we are

Cherp is a broadcaster and monitor, never a custodian or signer. Money moves directly between wallets. We provide the coordination layer.

​
Core principles

  • Non-custodial. We never handle private keys or sign transactions. You sign locally, we broadcast.
  • Fast confirmations. Payments confirm in under 5 seconds on most chains. You can treat the confirmed state as the completion signal — finalization happens in the background.
  • Stablecoins. USDC and USDT across all supported chains.
  • Reliable delivery. Signed transactions are broadcast via managed RPC providers with automatic failover.

​
Parties

Every payment involves two parties:
PartyRole
RequestorThe party requesting payment — a merchant, a friend asking to be paid
FulfillerThe party who pays — a customer, a friend settling a bill

​
How a payment works

  1. The requestor creates a Payment Intent via the API
  2. The requestor’s device broadcasts the intent via near-field audio, deep link, or QR code
  3. The fulfiller’s device decodes the audio and fetches the intent details
  4. The fulfiller reviews the payment and signs the transaction locally
  5. Cherp broadcasts the signed transaction and monitors for confirmation
  6. Both parties receive real-time status updates via webhooks or SSE

​
Architecture

Cherp runs on a globally distributed edge network. Each Payment Intent is managed by a dedicated state machine that handles transaction broadcasting, on-chain monitoring, and webhook dispatch. All RPC calls originate from Cherp’s backend, never from the client, ensuring consistent transaction submission and monitoring.