Compliance Model: Compliance at the Edges
Paycrest verifies who takes part, and each participant owns the compliance closest to them:Providers own local compliance
Each liquidity provider is responsible for complying with the rules that apply to them locally: AML/CFT requirements and any reporting obligations in their jurisdiction.
Senders own their compliance
Senders (apps integrating Paycrest) are responsible for their own user KYC/KYB, sanctions screening, and applicable regulations in the markets they serve.
Screening and review
Paycrest screens orders for sanctions risk and can hold an order for review. Treat
status as the source of truth.KYB-gated participation
Every sender and provider business is verified before going live.
KYB Requirements
For Senders
Senders are companies or developers who integrate Paycrest to provide on- or off-ramp services to their users:- Business verification (KYB) required before going live
- Register at app.paycrest.io and complete the KYB process
For Providers
Providers are businesses that supply fiat and stablecoin liquidity in both directions:- Business verification (KYB) required before going live
- Live fiat rails in each corridor they serve, for paying out and receiving funds
- Ongoing compliance monitoring as a condition of continued participation
Security
Smart Contract Security
The Gateway contract is the only place funds are held, and only temporarily, in escrow:- Open-source contracts: The Gateway contracts are public at github.com/paycrest/contracts.
- Non-custodial escrow: Funds are locked on-chain until either (a) payout is verified and stablecoins are released to the provider, or (b) the order cannot be fulfilled and is refunded to the sender automatically.
- Multi-signature governance: Protocol parameter changes require multi-signature approval
- Emergency pause: The Gateway contract can be paused in a security incident
API Security
- API Key authentication: Every API request requires a valid
API-Keyheader - API Secret: Used for webhook signature verification. Never expose it in client-side code
- Webhook HMAC verification: All webhooks include an
X-Paycrest-Signatureheader using HMAC-SHA256, allowing receivers to verify payload authenticity - TLS required: All API communication over HTTPS; never disable SSL verification in your HTTP client
Data Protection
- Encrypted recipient data: Bank account and mobile wallet details are encrypted in transit and at rest
- Minimal data retention: The protocol stores only what is needed for routing, settlement and compliance
Governance
Protocol changes are ratified by the Paycrest Core Multisig. As the protocol matures, governance is intended to move toward broader, community-led decision-making. See the Decentralization Path.Pricing & Sender Fees
What a sender pays on each order:- Rate: Quoted live by the Paycrest Sender API before the order is created.
- Transaction fee: Covers the gas the aggregator pays to create and settle the order. By default it comes out of the sender fee; the integrating app can pass it to its customers instead.
- Sender fee (optional): Set by the integrating app and settled on-chain in the same transaction as the order.
Paycrest is not a licensed financial institution. This documentation does not constitute legal or regulatory advice. Participants are responsible for their own compliance obligations in their respective jurisdictions.