Skip to content
Start with Identity
Protocol

Transaction Tokens (Txn-Tokens)

Transaction Tokens (Txn-Tokens) are short-lived, signed JWTs, defined in the IETF draft draft-ietf-oauth-transaction-tokens, that carry the user identity, workload identity, and authorization context of one external request through every internal service that processes it inside a single trust domain. As of October 2026 the draft is an IETF OAuth Working Group document in the "WG Consensus: Waiting for Write-Up" state, which means the working group has agreed on it but it has not gone to the IESG and is not an RFC.

The problem is the internal call chain. A request hits an API gateway with a user's access token, then fans out across ten microservices, and by the third hop most architectures either forward the original broad token (a replay risk) or drop it and rely on network trust (no user context at all). A Transaction Token Service mints a Txn-Token at the edge, typically lasting minutes and bound to that one transaction, and downstream services verify it instead of the external token. A stolen Txn-Token is worth far less than a stolen access token, and every service can see who started the request and why. Expect it to show up alongside WIMSE and SPIFFE in service mesh and agent runtime designs.

See also: token exchange, WIMSE, workload identity, access token, token theft, workload identity 101, agent identity standards map 2026

Last reviewed By SWI Community TeamSuggest a correctionHow we research