Capability status2 min read
Know what is built. Know what is gated.
Find the foundations relevant to your use case, inspect their evidence and identify the next decision for your team.
Implementation asks whether code exists. Verification asks what evidence has been recorded: fixtures, provider sandbox or actual journeys. Deployment asks which source and schema are running. Approval asks whether the specific program and operations are authorized. These pages do not certify live deployment or partner approval.
The map below describes reviewed source and recorded evidence categories. Actual deployment and account-specific rights must be confirmed for every evaluation. Provider names identify candidate or implemented technical paths, not established partnerships.
- Implementation
- Persistent records and ledger services.
- Verification
- Recorded synthetic service tests; not rerun for this edition.
- Deployment
- Not verified for this edition.
- Approval
- No live financial approval established by this guide.
- Next acceptance gate
- Target schema and authenticated journeys.
- Implementation
- Demo-only financial services; planning foundations.
- Verification
- Recorded simulation tests; deployed/device acceptance remains separate.
- Deployment
- Not verified for this edition.
- Approval
- No live financial approval established by this guide.
- Next acceptance gate
- Client/API compatibility and device acceptance; real program separately.
- Implementation
- Sandbox protocol transports.
- Verification
- Recorded mocked protocol tests; no real provider acceptance established here.
- Deployment
- Not verified for this edition.
- Approval
- No live financial approval established by this guide.
- Next acceptance gate
- Authorized accounts, outcome/settlement evidence and registration.
- Implementation
- Candidate contract boundary; no certified direct adapter.
- Verification
- No direct provider acceptance recorded in this review.
- Deployment
- Not verified for this edition.
- Approval
- No live financial approval established by this guide.
- Next acceptance gate
- Official technical pack and authorized access.
- Implementation
- Connect and sandbox-gated collection code.
- Verification
- Fixture/service evidence recorded in prior work; actual account acceptance not established here.
- Deployment
- Not verified for this edition.
- Approval
- No live financial approval established by this guide.
- Next acceptance gate
- Exact account acceptance, scope and target deployment.
- Implementation
- Separate test-billing services.
- Verification
- Recorded test protocol/service evidence; actual provider acceptance remains open.
- Deployment
- Not verified for this edition.
- Approval
- No live financial approval established by this guide.
- Next acceptance gate
- Approved test catalog/account and lifecycle acceptance.
- Implementation
- Approval-gated hosted foundation; direct execution blocked.
- Verification
- Host/configuration fixture evidence; approved hosted acceptance not established here.
- Deployment
- Not verified for this edition.
- Approval
- No live financial approval established by this guide.
- Next acceptance gate
- Agreement, identity binding, corridor/origin/platform acceptance.
- Implementation
- Provider boundary, protocol foundations and card simulation.
- Verification
- Recorded protocol/simulation tests; actual issuer sandbox acceptance not established here.
- Deployment
- Not verified for this edition.
- Approval
- No live financial approval established by this guide.
- Next acceptance gate
- Authorized program, provider sandbox and financial approval.
- Implementation
- Read-import transports and gated draft posting.
- Verification
- Recorded adapter/service fixtures; actual OAuth/posting acceptance remains open.
- Deployment
- Not verified for this edition.
- Approval
- No live financial approval established by this guide.
- Next acceptance gate
- Consented test organization, OAuth and recovery acceptance.
- Implementation
- Scoped reads and review-only extraction drafts.
- Verification
- Recorded scoped service tests; intended-deployment provider walkthrough remains separate.
- Deployment
- Not verified for this edition.
- Approval
- No live financial approval established by this guide.
- Next acceptance gate
- Configured provider, data review and intended-user acceptance.
Approval must identify the operation, merchant or customer, asset, country/corridor, environment and platform. One sandbox test does not authorize all merchants, all countries, production payments or a different financial product.