Cowrie Research

paycrest-primary-sources-2026-04-30

3 min read

Paycrest primary sources — 2026-04-30

Project status in this pass

  • No canonical standalone whitepaper or litepaper surfaced.
  • The clearest current source of truth is the official docs corpus, llms.txt, API/OpenAPI materials, and the main site.

Primary-source snapshots

1) Main site

  • URL: https://paycrest.io/
  • Key excerpt:
    • The homepage frames Paycrest as “The open payment routing protocol” and says it lets users “Unify fiat and stablecoin payments globally, with speed, transparency, and compliance built in.”
    • It describes three operating layers: “Gateway Smart Contracts,” “Smart Routing Engine,” and “Settlement Tools.”
    • It positions the product for wallets, fintechs, treasury teams, processors, exchanges, and DeFi protocols.

2) Docs introduction

  • URL: https://docs.paycrest.io/introduction.md
  • Key excerpt:
    • Paycrest is described as a “decentralized payment routing protocol” for stablecoin-fiat payments in emerging markets.
    • The page says it routes bidirectional conversion orders through a distributed network of liquidity providers, using onchain escrow for trustless completion in under 30 seconds without custodying user funds.
    • It explicitly says Paycrest is infrastructure, not a payment app, and highlights non-custodial design, composability, provider sovereignty, and zero direct sender fees.
    • It names active corridors including NGN, KES, UGX, TZS, MWK, and BRL, and names stablecoins including USDT, USDC, and cNGN across networks such as Ethereum, Base, Arbitrum One, Polygon, BNB Smart Chain, Lisk, Celo, and Scroll.

3) Docs llms.txt

  • URL: https://docs.paycrest.io/llms.txt
  • Notes:
    • Enumerates a broad first-party docs and API surface: authentication, rates, supported currencies and institutions, supported tokens, account verification, sender/provider order APIs, protocol architecture, compliance/security, participant roles, transaction lifecycle, provider setup, sender integration, smart-contract interaction, and resources like gateway contract addresses.
    • Also links OpenAPI artifacts including openapi-v2.yaml, openapi-v1.yaml, and an OpenAPI JSON endpoint.

4) Quickstart

  • URL: https://docs.paycrest.io/quickstart.md
  • Key excerpt:
    • Recommends POST /v2/sender/orders as the primary integration path and shows both offramp (stablecoin → fiat) and onramp (fiat → stablecoin) request examples.
    • Names the public quote endpoint GET /v2/rates/{network}/{from}/{amount}/{to} for UI quote prefetching.
    • Shows status tracking through GET /v2/sender/orders/:id or dashboard-configured webhooks.
    • Lists concrete lifecycle states including initiated, deposited, pending, fulfilling, validated, settling, settled, expired, refunding, and refunded.

5) Provider setup guide

  • URL: https://docs.paycrest.io/implementation-guides/provider-setup-guide.md
  • Key excerpt:
    • Walks providers through signup, KYB, PSP onboarding, dashboard-issued aggregator credentials, and provision-node deployment.
    • Documents a self-hosted Dockerized node path using safaria/riverpod:latest, environment-variable wiring for Paycrest and PSP credentials, and an /info endpoint for node verification.
    • Also documents a Blockops-hosted path, showing Paycrest is cultivating a network of provider-run nodes rather than only an internal operator stack.

6) Federated trust model and decentralization path

  • URL: https://docs.paycrest.io/introduction.md
  • Key excerpt:
    • The docs say Paycrest currently operates as a federated protocol with one aggregator run by Paycrest, KYC-gated participation, and webhook-based payout verification.
    • The roadmap frames future decentralization in phases rather than claiming the system is already fully decentralized today.

Working conclusion

Paycrest is best cataloged as stablecoin-fiat payment-routing infrastructure with a non-custodial escrow layer, a currently federated routing/verification layer, and provider-operated last-mile settlement nodes. The docs are unusually explicit about both the present trust model and the intended decentralization path, which makes the project easier to classify than many ramp products.

Graph View