A revised Internet-Draft published on 16 November specifies a JSON Web Token that carries three identity claims — the human principal, the agent platform and the agent instance — and a companion payment token that can be presented with it. Revision -04 adds a section on the records an issuer must keep so that a token can be resolved after the fact to the verifications behind it.
What happened
A. Agarwal (Skyfire Systems) and M. B. Jones (Self-Issued Consulting) published revision -04 of draft-skyfire-oauth-kyapay-token, “KYAPay Token”. It is an individual Internet-Draft with intended status Standards Track, not a working-group document. Two companion drafts were revised the same day: “Using KYAPay Tokens” (-03, with S. Thumma of Akamai) and “KYAPay Token Exchange” (-03).
The draft defines three JWT types and registers the media types application/kya+jwt, application/pay+jwt and application/kya-pay+jwt. A KYA token carries three identity claims: hid for the human principal (an individual or an organisation), apd for the agent platform, and aid for the agent instance. In this revision apd is required in KYA and KYA-PAY tokens, not optional. A PAY token carries the amount, currency, settlement type and settlement instrument. A KYA-PAY token carries both.
The subject claim is the binding. sub identifies the combination of principal, platform and agent that the issuer verified, must be different at every other Target, must stay stable at a given Target while that combination is unchanged, and must be replaced when any of the three identities changes. The draft requires a recipient that correlates a PAY token with a KYA token to check that both carry the same iss and sub; matching one without the other is not enough. The audience claim identifies the Target’s own combination of identities, and tdm and tsi name the domain and the service the token was minted for.
Revision -04 adds an Issuer Records section. An issuer must keep verification records (which methods were used, when, by whom, and references to the evidence), authorization records (which directly identifying sub-claims were disclosed, to which Target, who authorized the disclosure and how), and issuance records (the token’s iss, jti, iat, exp, sub, aud, tsi and the three identity identifiers). Together they let an issuer resolve a token, given its iss and jti, to the verifications and authorizations behind it. The draft does not define an interface for querying them, and leaves retention periods and third-party disclosure to the law that applies to the issuer.
The payment side is concrete. A PAY token carries amt, cur, a settlement value in the network’s units, a settlement type of coin or card, and a settlement-information claim. Where the type is card, the instrument is a payment-network-issued agentic credential — the draft names Visa Intelligent Commerce and Mastercard Agent Pay, the latter using Secure Card on File — used with a single-use token cryptogram. The credential must not be a Primary Account Number, and the draft states that the underlying PAN cannot feasibly be recovered from it.
Tokens are bearer tokens unless they carry a confirmation claim. With cnf, the token is bound to a public key held by the agent, and the companion document requires the presenter to sign each request with an HTTP Message Signature (RFC 9421) over that key. The draft is explicit that cnf cannot substitute for the bearer-token protections — short lifetimes, audience restriction, transport confidentiality — because a recipient may not enforce it.
The limits are stated too. The draft says KYAPay “does not aim to define agentic identity in its entirety”, that the protocols which use the tokens are not defined by the token specification, and that early production deployments are described at kyapay.org.
Why it matters for KYA
Most agent traffic today arrives with no answer to the question a bot manager actually needs: not “is this a human?” but “did a verified human authorise this agent, for this site, for this action?” A user-agent string, an IP reputation score and a CAPTCHA can separate scripts from people. They cannot separate an agent acting for a paying customer from an agent acting for a fraud ring. The KYAPay shape — principal, platform, instance, each separately identified — is the minimum needed to make that distinction, and it lets a site throttle one misbehaving agent instance without blocking every agent on the same platform.
The Issuer Records section is the part that matters after an incident. A signed token proves only that some issuer signed some claims. It does not, by itself, show what the issuer checked or who authorised the disclosure of a real name or email address. By requiring verification, authorization and issuance records, and by making the token resolvable to them through iss and jti, the draft gives an auditor a path from a request in a log to the identity checks behind it. That is the difference between a token format and an accountability system — and it is left, correctly, to law to decide how long those records must be kept.
The pairwise subject is a design choice with an operational cost. Values differ per Target and must not be linkable without the issuer’s cooperation, which is good privacy and bad for anyone who assumes a stable agent identifier across sites. Implementers who compare sub values from two issuers, or from two different sites, will get the wrong answer; the draft tells them to compare only within the same issuer and Target.
The payment claims also show where agent commerce is heading: the card networks’ own agentic credentials, a single-use cryptogram, and an explicit prohibition on passing a PAN through the agent. That is a narrower, more defensible design than handing an agent a stored card number, and it lines up with what Visa and Mastercard have already announced.
What to watch
- Whether the OAuth working group adopts the draft at IETF 127 this week. Adoption would change the document name and put the claims through working-group review; until then this is one vendor’s proposal with a co-author from the JOSE community.
- Whether bot managers, CDNs and fraud platforms implement the recipient rules in “Using KYAPay Tokens”, or build private variants. The value of a token format is in the second implementer, not the first.
- Whether an issuer trust framework appears. A token is only as good as the recipient’s ability to decide which issuers to trust, and the draft does not define that list.
- Whether the card-settlement values track the networks’ own programmes as they change. The draft hard-codes names that are still moving.
Sources
- A. Agarwal and M. B. Jones, “KYAPay Token”, draft-skyfire-oauth-kyapay-token-04, 16 November 2026 — datatracker.ietf.org
- A. Agarwal, M. B. Jones and S. Thumma, “Using KYAPay Tokens”, draft-skyfire-oauth-using-kyapay-tokens-03, 16 November 2026 — datatracker.ietf.org
- A. Agarwal, M. Jones and A. Hingnikar, “KYAPay Token Exchange”, draft-skyfire-oauth-kyapay-token-exchange-03, 16 November 2026 — datatracker.ietf.org
- IETF, “HTTP Message Signatures”, RFC 9421 — rfc-editor.org
- KYAPay, early production deployments — kyapay.org
Know Your Agent (KYA) explains agent identity, verification and accountability. This is an explainer, not legal or compliance advice — see our Sources & methodology. New to KYA? Start with What is Know Your Agent? and the glossary.