Institutions

What stays exactly as it is

• Your legal framework. AFC works inside existing law; it does not require legislative change to operate.
• Your compliance. KYC, AML and sanctions screening stay with you and happen before any request enters the process.
• Your systems. No one reads your internal systems. You expose only the interface the contract requires.
• Your licence and your supervisor. Licensed functions stay with licensed institutions.

What you gain is a shared, verifiable process between systems that cannot talk to each other directly today — without handing custody or control to anyone.

Public-sector use cases

We start where risk is lowest and value is easiest to verify, and widen scope only after each stage is proven.

• Audit-first control layer — a national record of public-finance movements that observes and verifies, before it ever moves money. The safest entry point.
• Treasury reconciliation — inter-agency settlement records reconciled continuously instead of in manual cycles.
• Grants and subsidies — earmarked payments traceable to final use, with protection against double spending.
• Public procurement — contract phases linked to payment milestones, with escrow-style conditions and a recorded history.
• Asset registries — state property, infrastructure or resource rights recorded as tokens of rights at official valuations.
• Cross-border corridors — institution-to-institution settlement through licensed anchors in each jurisdiction, as a later-stage pilot.
• Digital treasury sandbox — a time-boxed regulatory pilot (for example, 90 days) with agreed success criteria before any production decision.

How an engagement works

• 1 · Briefing — a technical and legal walkthrough with your team; we map where your systems meet the process.
• 2 · Scope — one use case, one jurisdiction, clear success criteria and a written responsibility map for every party.
• 3 · Sandbox — integration against the API contract in a sandbox environment, under the oversight of your supervisor where required.
• 4 · Controlled pilot — limited volumes, full audit, weekly review, and a stop point if criteria are not met.
• 5 · Decision — production only after a documented pilot review.

Is AFC a payment system or a custodian?

No. AFC is the process of executing a contract between independent parties. It does not hold funds, keep balances or open accounts. Funds in transit stay with licensed anchors under their own licences.

Which licences are involved?

Licensed functions — holding and moving money or digital assets — are performed by licensed anchors (banks, payment or e-money institutions; licensed virtual-asset service providers). AST is a separate legal entity subject to the licensing that applies to it. The exact regime depends on the jurisdiction and is confirmed with local counsel for each deployment; we do not claim that no licence is needed anywhere.

How are sanctions and currency controls handled?

The initiating institution screens every request before it enters. The contract does not override sanctions, currency-control or AML law — these apply independently, and the process is designed to comply with them, never to route around them.

Where does our data live?

Data and keys follow the jurisdiction in which they arise, under local data-protection law (for example GDPR, KVKK or CCPA). Each participant sees only the data its role requires; cross-border processing is a separate, explicit review point.

What happens if something fails mid-process?

Every process instance ends in exactly one terminal state — settled, rolled back or failed. A deviation returns the process to its last consistent state, and both the deviation and the recovery are recorded.