payrail
DocsWhitepaperBlogOpen dashboard

Docs

A USDC invoice that closes itself: how to create one, how the buyer pays, how the payment is matched from the chain, and what you are trusting when you use it.

  • 01What Payrail isA USDC invoice that closes itself, and what that gets you.Read · 2 min→
  • 02Creating invoicesRegistering as a merchant, writing an invoice, and getting a payment link.Read · 2 min→
  • 03Payment flowWhat happens when a buyer opens the link. Approve, pay, and why funds never stop in between.Read · 3 min→
  • 04Verification and the indexerTwo routes to PAID, the matching rules, and why both are idempotent.Read · 3 min→
  • 05ContractsWhat PaymentProcessor does, the functions worth knowing, and how to run the whole thing locally.Read · 4 min→
  • 06APIEvery endpoint, what it accepts and what it returns, for wiring Payrail into your own system.Read · 3 min→
  • 07Risks and limitsWhat can go wrong, what you are trusting, and what has not been built yet.Read · 3 min→
Want the full design?

The whitepaper covers the mechanics end to end: the data model, the contract, the two verification routes, the trust assumptions, and what is still missing.

Read the whitepaper

Payrail is reconciliation software, not a payment service provider. USDC moves directly from buyer to merchant. Not audited; running on a test network.

DashboardDocsWhitepaperBlogTermsPrivacy