Open Standard for InterVASP Authorization
YONA moves pre-transfer coordination out of user prompts and closed coordination networks into direct VASP-to-VASP authorization.
Learn MoreOriginator
VASP

Using YONA
Communicate Directly
Beneficiary
VASP

Using YONA
Out-of-scope for YONA
Regulated customer data (e.g., PII, Travel Rule payloads, destination coordinates)
Works alongside existing Travel Rule, compliance, custody, and settlement systems. Open to implement under CC BY 4.0. No YONA runtime network.
View MoreMoreYONA does not replace Travel Rule, compliance, or settlement systems. It fits before those steps, enabling a clear authorization decision before later processes begin.
VASP A
Originator
YONA Authorization
- Counterparty Discovery
- Signed Authorization Request
- ACCEPT or REJECT Decision
VASP B
Beneficiary
post ACCEPT ↓
(Outside YONA Scope)
VASP A
Originator
Compliance & Travel Rule
- KYC & AML Checks
- Travel Rule Messaging
- Risk Screening
VASP B
Beneficiary
VASP A
Originator
Settlement
- Funds Transfer
- Confirmation
VASP B
Beneficiary
One Reference, No Manual Beneficiary Details for end-users
In YONA, users start from their own VASP’s app or service using one YONA-defined reference: a beneficiary_handle for push payments or an intent_locator for pull payments.
The reference gives the originator VASP enough information to continue without asking the user for blockchain addresses, tags, memos, wallet details, or separate beneficiary information. Any additional details are handled directly between VASPs, instead of being collected from the user through extra payment prompts.
Where to start
For decision-makers
Start with Pilot Overview to understand the current lower-lift pilot path, what stays unchanged, and what the pilot does and does not prove.
For engineers
Start with YONA Ruleset 1.0 for normative requirements, and Reference Messages & DID Examples.
Canonical documents for this release
- YONA Ruleset 1.0
- Defines message validity, semantics, authorization outcomes, and request/response binding
- Base Interoperability Profile (BIP)
- Defines the interoperability baseline
- YONA Conformance Test Suite
- Defines normative conformance verification