Readiness
Every operation an endpoint can perform has an effective readiness: what it is cleared to do right now, and what is still outstanding. The gates beneath — KYB on the business, KYC on the people, screening on both — are verified in onboarding; the console reads their effect per operation.
Readiness is resolved per operation, before value can move.
- Surface
- readiness · per operation
- Gates
- KYB · KYC · screening
- Cleared in
- onboarding
- Held by
- VantaCrest
The book as it stands.
as of 09:48:17acc_8xK2 · ep_7Q4 · gates cleared in onboarding · readiness resolved per operation
- Business (KYB)Northwind Ltd · registry verifiedverified
- Directors (KYC)2 of 2 verifiedverified
- Beneficial owners1 of 1 outstanding
- Sanctions screeningscreened · no matchcleared
Effective readiness · per operation
- Open accountKYB cleared.
- ready
- Receive (internal)Endpoint cleared.
- ready
- Send (external rail)Awaiting beneficial-owner verification.
- blocked
- Go liveOne gate outstanding.
- blocked
Verify the outstanding gate and watch each operation's readiness re-resolve.
The gate comes first
KYC and KYB readiness is verified before an account or a transfer can move. The gates are cleared in onboarding; their state decides what each operation may do, so you know exactly what stands between an application and its first live movement.
Effective readiness, per operation
Readiness resolves per operation: what this endpoint, in this environment, is cleared to do right now. Opening an account may be ready while sending on an external rail is still blocked on one outstanding gate.
Held by VantaCrest
Readiness is enforced on the institution's governed infrastructure, answerable to one mandate. You operate the surface; the gate itself is held beneath it, the same for every application on the core.