The problem
Free zones trade globally. Their payment rails don't.
Correspondent banking is closed
Resident traders can invoice a foreign buyer, but there is no compliant way to receive the money — so deals route through informal channels no authority can see.
Crypto alone isn't compliant
A raw wallet transfer settles instantly but leaves the zone with no KYC trail, no approval gate, and no way to reconcile a shipment against a payment.
The rial leg is the hard part
Even when crypto arrives, converting it to rial at an agreed rate, through a bank willing to book it, is a manual process measured in days.
Who uses it
Four parties, one ledger
Each participant gets a portal scoped to exactly what they are allowed to see and do.
Resident trader
A company registered in the zone. Issues invoices, receives stablecoin, requests rial settlement.
- Issue receive invoices
- Verify payout wallets
- Request settlement to a bank account
- Jalali-dated reports
Foreign counterparty
The overseas buyer or supplier. Onboards with a passport, pays the invoice from their own wallet.
- Passport-based onboarding
- Receive payment requests
- Pay from a self-custody wallet
- Track request status
Zone operator
The free-zone authority. Approves participants and transactions, and holds the audit record.
- Review and approve KYC
- Approve or reject invoices
- Oversee every transaction
- Set fees, limits and validity
Partner bank
The licensed institution that books the rial leg and confirms the funds moved.
- Lock the exchange rate
- Confirm rial received or paid
- Manage institutional wallets
- Settlement reporting
How a deal settles
From invoice to rial, on the record
1
Issue the invoiceTrader
The resident company raises an invoice against a shipment: amount, currency, goods, and counterparty.
2
ApproveOperator
The zone reviews the parties' KYC and the trade itself, then approves — or rejects with a reason the trader can see.
3
Pay in stablecoinCounterparty
The foreign buyer pays from their own wallet to a deterministic deposit address. Non-custodial: the funds are never pooled.
4
Confirm on-chainChain
The payment is confirmed at the required depth and matched to the invoice by amount, token and recipient — not by id alone.
5
Lock the rateBank
The partner bank quotes and locks an exchange rate, so neither side carries the volatility while the settlement is in flight.
6
Settle in rialBank
The bank credits the trader's account and records the receipt number. The zone sees the complete chain of custody, end to end.
What's included
Built for the people who have to sign off
KYC with an audit trail
Separate onboarding for residents (national ID) and foreign parties (passport), with approval, rejection reasons, and history.
Locked exchange rates
The bank commits a rate to each settlement, so the rial figure is fixed before the money moves.
Role-scoped portals
Trader, counterparty, operator and bank each see only their own surface — no shared admin console.
Persian-first, Jalali dates
Native RTL Persian throughout, with Jalali dates at render — built for the local desk, not translated onto it.
Non-custodial underneath
The crypto leg runs on the AFA.CO contracts: an atomic on-chain split, with the platform never holding customer funds.
Reconcilable reporting
Every invoice, settlement and transfer carries a trade reference and a transaction hash that anyone can verify independently.
See it before you commit to it
The prototype walks the whole journey — all four portals, every state — so a decision-maker can judge the product before a line of production code is written.
The demo is an interactive prototype: sample data, no live funds.