Naming and Claims Guidelines

Published: April 11, 2026

YONA publishes an open specification. YONA is not a runtime network and does not operate a registry, approval program, or membership system.

Claims you should not make

Do not describe your product, company, or service in a way that implies:

  • endorsement, approval, certification, or official status from YONA;
  • membership in a YONA-controlled network or program;
  • that YONA operates your runtime messaging, routing, or settlement flow; or
  • that YONA reviewed or validated your implementation unless that is specifically true and authorized.

Examples to avoid:

  • “YONA Certified”
  • “Approved by YONA”
  • “Official YONA Partner”
  • “YONA Member”
  • “Runs on the YONA network”

Conformance claims

Only make conformance claims if they are accurate and supportable.

Examples:

  • “Conformant to yona:ruleset:v1.0, the Base Interoperability Profile (BIP), and the applicable BIP Conformance Test Suite”
  • “Self-asserted conformance claim for yona:ruleset:v1.0”
  • “Push-payment-only pilot; not a full BIP conformance claim”

Names, logos, and brand assets

This page does not grant rights to use YONA logos or brand assets.

Unless YONA gives separate written permission, do not use YONA logos, badges, or seals in product marketing or user interfaces.

Disclaimer

This page is for general guidance only and does not change the technical meaning of any YONA specification or conformance requirement.