Money
How Neo connects to outside companies
How payment, delivery, identity, and messaging connections are checked and controlled.
Adapter inventory
| Concern | Runtime adapters | Safe fallback |
|---|---|---|
| Meta Cloud API | Signed deterministic provider double | |
| Planning | OpenAI Responses API | Deterministic planner |
| Payment | Paystack direct transfer, Paystack/Flutterwave hosted web checkout | Provider double; WhatsApp hosted fallback is disabled |
| Seller identity | Dojah NIN lookup | Disabled until exact certification; no BVN/chat fallback |
| Logistics | Kwik, Sendbox | Explicit manual disablement or sandbox beta |
| Uploads | MinIO-compatible storage | Private local test storage |
| Payout | Paystack recipients and transfers | Disabled production switch or sandbox double |
Exact-target certification
Certification binds a capability to the exact environment, provider, adapter version, credential-rotation label, callback URL, time window, and reviewed checks. Runs, checks, and revocations are immutable. Missing, expired, revoked, mismatched, or failed evidence blocks new external side effects while leaving callbacks, status reads, reconciliation, and cleanup available.
Deterministic tests prove the gate. They cannot certify a deployment. A provider API read or a successful sandbox flow is not certification.
Feature gates
AUTOMATED_COMMERCE_WRITES_ENABLEDcontrols consequential automated commerce writes.PAYOUT_TRANSFERS_ENABLEDindependently controls payout delivery.PAYMENT_REFUNDS_ENABLEDindependently controls provider refund delivery.- Delivery modes select direct or durable outbox behavior; production automated writes require outbox.
- Closed-beta provider writes are phone scoped and do not waive certification for public launch.
- Unresolved critical financial reconciliation blocks payout queueing and delivery.
Public and private evidence
Public health exposes capability, provider, whether certification is required, validity, and expiry only. It does not expose credential labels, evidence payloads, provider references, private callback details, or internal deployment identifiers.
The repository-only certification runbook contains controlled drill requirements. Operators must keep credentials and evidence in protected storage and avoid real customer data.
src/provider-certification.tssrc/provider-canary.tsdocs/PROVIDER_CERTIFICATION.mdtest/provider-certification.test.tstest/provider-canary.test.ts
