Aros Financial Core

What AFC is

AFC is not a platform, a bank or a payment system. It is the process of executing one contract — the Aros API Contract — between independent parties that each keep their own licence, systems and responsibilities.

An institution that has already completed its own checks sends an authorised request. AFC coordinates the steps that follow between AST (the execution and record engine) and licensed anchors (regulated institutions that move money and digital assets under their own licences). When the process ends, the AFC instance ends with it.

Nothing about your legal framework, your core banking system or your regulator changes. AFC connects systems that today cannot reach each other directly, quickly and safely — without asking either side to become the other.

The contract is permanent. Each AFC process instance exists only while one transaction is being executed, and closes in exactly one terminal state: settled, rolled back, or failed.

Why it matters

Money and value now live in two kinds of infrastructure — regulated fiat systems and cryptographic networks. Existing bridges between them usually solve the problem by taking custody, hiding the process, or blurring who is responsible.

• Interoperability without merging — fiat and digital-asset systems work together without losing their nature or their regulatory perimeter.
• Coordination without custody — AFC orchestrates the process but never holds participants' funds or balances.
• Transparency without exposure — every step is recorded and auditable, while each participant's internal systems stay private.

How a process runs

• 1 · Initiation — the institution completes KYC, AML, sanctions screening and internal authorisation, then submits the request to the API gateway.
• 2 · Admission — the gateway checks identity, certificate, contract version and message structure. Unauthorised or malformed requests never enter.
• 3 · Validation — AI supervision and the structural validation layer check the route, the roles and the process state before anything executes.
• 4 · Execution — AST executes and records each step on NodeChain; the relevant licensed anchor performs the regulated money or asset movement under its own licence.
• 5 · Settlement — the recipient receives value in the form it is meant to receive it; each party sees only what its role requires.
• 6 · Finalisation — the process closes in one terminal state. If anything deviates, it is returned to its last consistent state and the reason is recorded.

Trust and security

• Non-custodial by design — AFC never owns or holds participants' funds. Funds in transit sit with the licensed anchor, never with Aros Studio.
• Role isolation — every participant performs exactly one role in a process; no party can act as another.
• Zero-exposure interoperability — participants expose interface logic only; no one reads another party's internal systems.
• Zero-trust transport — mutual TLS between services, certificate-based institution identity, no public write endpoints.
• Deterministic recovery — a deviating process is rolled back to a safe checkpoint, and the rollback is itself recorded.

Compliance and accountability

AFC does not replace the regulatory work of institutions. Each participant remains accountable within its own jurisdiction.

• Initiating institutions perform KYC, AML, sanctions screening and authorisation before a request enters AFC. Unverified flows cannot enter — that is the condition of activation.
• Licensed anchors carry the licensed functions (holding and moving money or digital assets) under their own licences and supervisors.
• AST executes and records the process; it holds only its own funds.
• AFC validates the structure and architectural conformity of each request and keeps the audit trail.

Sanctions, currency-control and AML rules apply independently of any contract. AFC is built to respect them, not to route around them. Licensing requirements differ by jurisdiction and are confirmed with local counsel for every deployment.

For developers and integration teams

The API contract, message schemas, process states, security model and performance targets are described in the AFC documentation. The formal model — axioms, boundaries and formulas — is in the white paper.