Ayra Protocol: Payloads

When we talk of handing someone an Ayra Card we talk about a small amount of standard data and a set of "payloads" that may be useful for the recipient.

What is a Payload?

A payload is not just data. A payload can be one of three things:

1. Simple Data

Unverifiable information that the credential carries along. The Ayra Card itself has no real knowledge of what the payload is or what it is for. It just carries it.

Examples:

• An email address, a phone number, a deeplink to Signal/WhatsApp/Wire

• A company's LEI for automating data movement

• A "traveler profile" (zero-party data) that allows hotels, airlines, and other travel systems to consume trusted preferences

• A certification level, a role, an authorization scope

2. A Credential in Its Own Right

A payload can be a verifiable presentation — a pre-formed request that returns a verified credential from the Ayra Card holder. This is not just data; it is trust that has been independently earned and can be independently verified.

Examples:

• A professional license issued by a licensing board

• A security clearance issued by a government

• A verified email address backed by a credential

• A competency validation from an assessment provider

• A vLEI that triggers further verification ("prove you are a signing officer for the company")

3. A Pointer

A payload can say "come check me out over here" — directing the verifier to a source they would never have known to look at on their own. This is the payload type that makes the individual the integration point.

Examples:

• A learning payload that points an employer to the learner's portfolio at Pearson — the employer would never have known to look there until the learner told them

• A government ID payload that points to the Province of British Columbia — one issuer among hundreds a verifier would never find on their own

• An AI agent endpoint (DIDComm/TSP or RESTful API) — "connect your systems to my agent instead of emailing me"

• A booking link for scheduling meetings with the credential holder

The person decides what to share and where to send the verifier. Payloads are what make the individual the integration point. Because payloads can point verifiers to sources they didn't know existed, every credential holder becomes a bridge to parts of the ecosystem that were previously invisible.

Why This Matters

Payloads move complexity out of the Ayra Card. The credential itself is simple — a standard container that is globally governed, portable, and tied to the person who earned the trust it represents. The payloads are where the value lives.

A verifier doesn't need to know in advance which government issued your ID, which institution holds your learning record, or which AI agent handles your business inquiries. The payload tells them where to look. No bilateral system integrations required. No advance knowledge of the ecosystem required.

This means organizations can interact across boundaries — not just between companies, but across any boundary that blocks integration: between departments (engineering, legal, finance), between companies, between companies and governments, between ecosystems. The Ayra Protocol standardizes the opening moves. Payloads carry the content that makes those interactions valuable across whatever boundaries exist.

Payload Maturity

Payloads are expected to mature through real-world usage:

• Unknown/unmanaged — private payloads where creator and consumer understand the content implicitly. No formal coordination required.

• Known/unmanaged — informal payload types with community descriptions. Lightweight process, similar to DID Method registration.

• Known/managed — formally specified and testable payload types for high-volume or high-value use cases.

See Payload Types for the full maturity model.

The Ayra Protocol needs to be tested in real-world pilots before committing to formal payload standardization. The three-type model (data, credential, pointer) provides the conceptual framework; the maturity model provides the governance path.