Paycrest

• Name: Paycrest
• URL: https://paycrest.io/
• Category: stablecoin-fiat routing stack / corridor aggregator
• Summary: Paycrest is a corridor router with escrow contracts, not a trustless payments baseline. The contracts matter, but the practical leverage still sits with the aggregator, provider admission, PSP wiring, and quote selection.
• What it does:
  • Lets sender applications create offramp and onramp orders through a Sender API or directly through Gateway smart contracts
  • Routes orders to liquidity providers that run their own provision nodes, set their own rates, and connect their own local PSP accounts
  • Uses onchain escrow so stablecoins are locked until local-fiat delivery is confirmed or automatically refunded if fulfillment fails
  • Supports both stablecoin → fiat and fiat → stablecoin flows through the same order-creation surface, with public quote endpoints, account verification, and status tracking
  • Exposes provider-facing operational docs for self-hosted Docker deployments, PSP credential wiring, dashboard-managed API keys, and alternative hosted node setup through Blockops
  • Publishes first-party docs covering architecture, participants, transaction lifecycle, supported currencies and tokens, contract addresses, and OpenAPI specs
  • Targets wallets, fintechs, exchanges, DeFi protocols, payroll flows, treasury operations, and cross-border payment products rather than end-user consumer-only flows
• Key claims:
  • The docs introduction calls Paycrest a “decentralized payment routing protocol” for stablecoin-fiat payments in emerging markets and says orders complete with “onchain escrow ensuring trustless, automatic completion in under 30 seconds, without custodying user funds”
  • The docs explicitly say Paycrest is not a payment app but infrastructure that applications can integrate for on- and offramps, and that senders and providers are KYC/KYB-gated
  • The site and docs both describe the core architecture as Gateway smart contracts, a routing engine / aggregator, and settlement tools or provision nodes tied to local PSP rails
  • The quickstart shows both offramp and onramp creation through POST /v2/sender/orders, which is strong evidence that Paycrest is exposing a real bidirectional integration surface rather than only marketing copy
  • The llms.txt indexes a substantial first-party docs surface spanning authentication, rates, supported currencies and tokens, sender and provider order endpoints, architecture, compliance, participant roles, provider setup, smart-contract interaction, and OpenAPI artifacts
  • The provider setup guide shows providers can self-host Dockerized provision nodes, use Paycrest-issued aggregator credentials plus PSP-issued credentials, and optionally use Blockops for low-touch hosting
  • The decentralization-path section says the protocol is currently federated around a single Paycrest-run aggregator and frames future decentralization as a staged roadmap rather than something already achieved
• Whitepaper: No canonical standalone Paycrest whitepaper or litepaper surfaced in this pass. The clearest current source of truth is the official docs corpus, llms.txt, API/OpenAPI materials, and the main site; see ../whitepapers/paycrest-primary-sources-2026-04-30.md.
• Sources:
  • https://paycrest.io/
  • https://docs.paycrest.io/
  • https://docs.paycrest.io/llms.txt
  • https://docs.paycrest.io/introduction.md
  • https://docs.paycrest.io/quickstart.md
  • https://docs.paycrest.io/implementation-guides/provider-setup-guide.md
  • https://docs.paycrest.io/concepts/architecture.md
  • https://docs.paycrest.io/openapi-v2.yaml

Internal linkages

• Keep the linkage budget short.
• Best upward reads: bridge-xyz and coinflow.

Control surface

• Authority sits in provider onboarding, PSP connectivity, quote and routing policy, KYC/KYB gating, and the still-federated aggregator.

• The escrow contracts narrow one risk. They do not remove the operator chokepoint around who can fulfill local fiat legs and on what terms.

• Read Paycrest as a thinner routing layer pointing upward to stronger payment-control anchors, not as a settled decentralization endpoint.

• Last reviewed: 2026-06-01 UTC