Compliance is not a branch. It is the control plane.
Cross-border payment diagrams usually draw compliance as one service beside messaging, settlement, custody, liquidity, and reporting. That model is wrong for institutional adoption. Compliance is the layer that proves every other layer was authorized, reconciled, mapped, and bounded.
The stack is built. The proof layer is not.
Banks, fintechs, and enterprise treasury teams can already reach payment rails, custody platforms, stablecoin networks, exchange venues, and reporting tools. What they cannot easily prove is that the control state existed before value moved.
The control plane sits above the stack.
A control plane does not replace the underlying rail. It makes policy, authority, thresholds, approvals, exceptions, and evidence visible across the stack. In institutional payments, that distinction matters because a regulator or audit committee does not only ask whether value moved. They ask whether the organization can prove the move was authorized under the correct policy at the correct time.
The relationship has four modes.
Vestry's public model separates the control plane from the stack underneath it. It consumes some layers as inputs, attests over some processes, sits above payment rails without depending on a single rail, and draws hard boundaries around functions it should not perform.
Four relationships make the model legible.
The point is precision. Compliance should not be an everything bucket. It should be explicit about what it reads, what it proves, where it is independent, and what remains outside its boundary.
| Relationship | What it means |
|---|---|
| Consumes as input | Regulatory rules, sanctions results, KYC and KYB outputs, Travel Rule payloads, ISO 20022 messages, VASP exchange, and digital identity signals become evidence sources. |
| Attests over | Authorization, reconciliation, process confirmation, operator hierarchy, and regulatory reporting become provable control states. |
| Sits above rails | Correspondent banking, payment hubs, RTP/FedNow style rails, stablecoin settlement, and other value movement paths remain underlying infrastructure. |
| Out of scope | FX execution, fraud and cyber detection, transaction monitoring, and value movement stay outside the attestation layer unless they produce findings the control plane must prove were honored. |