Paycrest company primary sources — 2026-08-09

Classification takeaway

Paycrest now clears the bar for a separate companies/ note because the useful control question is not only how do the Gateway contract, provision nodes, and routing flow work? It is which named operator currently runs the sole aggregator, gates API access through KYB/KYB, issues provider credentials, collects the aggregator fee, and becomes the source of webhook and order-state truth? The strongest answer in current primary materials is Paycrest Inc., which also wraps Paycrest Protocol and Noblocks inside one legal services shell.

Primary sources reviewed

1. Official homepage — https://paycrest.io/

   • Best high-level operator framing for the current product family.
   • Presents Paycrest as an open payment routing stack spanning protocol, engine, bridge, network, and rail, and markets Noblocks as a reference app built on top.

2. Introduction docs — https://docs.paycrest.io/introduction.md

   • Best concise statement of the current trust model.
   • Says Paycrest is a decentralized payment routing protocol today operating as a federated protocol, identifies the Aggregator as currently operated by Paycrest, and says the current 0.5% aggregator fee flows entirely to Paycrest.

3. Architecture docs — https://docs.paycrest.io/concepts/architecture.md

   • Strongest source for the operator boundary around routing.
   • Says Paycrest currently operates the sole aggregator, all order matching and coordination fees flow to Paycrest, and the aggregator manages order monitoring, provider matching, settlement coordination, and webhook delivery.

4. Compliance & Security docs — https://docs.paycrest.io/concepts/compliance-security.md

   • Best source for access mediation and federated compliance.
   • Says all senders and providers currently undergo identity verification before API access is granted, and that provider participation includes PSP-licensing documentation plus ongoing compliance monitoring.

5. Provider setup guide — https://docs.paycrest.io/implementation-guides/provider-setup-guide.md

   • Strongest source for dashboard and credential control.
   • Says provider API keys and secrets come from the Paycrest dashboard, providers must register their provision-node host identifier in the app, and self-hosted providers still depend on the Paycrest-operated aggregator endpoint.

6. Docs index (llms.txt) — https://docs.paycrest.io/llms.txt

   • Best evidence for the breadth of the company-run operational shell.
   • Shows Paycrest controls the documentation and live workflow for sender orders, provider orders, market data, supported institutions and tokens, webhook delivery logs, architecture, compliance, and troubleshooting.

7. Terms of Use — https://www.paycrest.io/terms-of-use

   • Strongest source for the legal entity boundary.
   • Identifies Paycrest Inc. as the Delaware company providing the services, says Paycrest Protocol, noblocks, and future offerings are all company services, and explicitly says those services do not operate as independent legal entities.

Selected excerpts

Introduction / decentralization path

Paycrest currently operates as a federated protocol: one aggregator (run by Paycrest), KYC-gated participation, webhook-based payout verification.

How it works today: Paycrest operates the sole aggregator. All order routing, provider matching, and payout verification run through Paycrest-controlled infrastructure.

Architecture

Paycrest currently operates the sole aggregator in the network (federated model). All order matching and coordination fees flow to Paycrest.

Compliance

All senders and providers currently undergo identity verification before being granted API access. This is the federated phase; permissionless participation is a future phase.

Provider setup

API Key → set as AGGREGATOR_CLIENT_ID

API Secret → set as AGGREGATOR_SECRET_KEY

In the app: Settings → Payout tab → Configure Provision Node → Host identifier — paste the URL and click Update

Terms

Welcome to Paycrest Inc. (“the Company,” “We,” “Our”). These Terms of Use (“Terms”) govern your access to and use of all products and services offered by Paycrest Inc., including but not limited to Paycrest Protocol, noblocks, and any future offerings developed by the Company (“the Services”).

Paycrest Inc. which is registered in Delaware, is the official legal entity accountable for delivering and managing the Services.

Why it belongs in the active corpus

• Useful comparison point for payment stacks that advertise protocol or decentralization language while still depending on one company-run routing, admission, and webhook-publication shell.
• Helpful for separating non-custodial escrow from the still-centralized coordination surface: funds may be escrowed onchain, but access, routing, payout verification, and fee capture still sit with one named operator today.
• Good companion for other company-note cases where open protocol framing coexists with company-run onboarding, credential issuance, and managed default paths.