Account linking vs verifiable credentials for AI commerce

Account linking connects an agent-enabled experience to a customer’s account at a business. Verifiable credentials let an issuer make claims that a receiving party can check. The approaches can work together: a merchant account can manage orders while a credential supplies accepted evidence of a membership held elsewhere.

The choice depends on where the relevant customer information lives, which organisation is responsible for it and what the merchant needs to decide. Neither approach automatically grants spending authority or guarantees a discount.

When account linking is a good fit

If a merchant already maintains the customer’s membership, saved addresses and order history, a connection to that account may be the most direct route. The customer approves access, and the integration uses the authorised functions of that merchant’s system.

The Universal Commerce Protocol identity-linking specification, version 2026-04-08, uses OAuth 2.0 and identifies loyalty benefits, personalised offers and other account features as use cases. UCP therefore does address identity linking and loyalty access; these are not absent from its commerce design.

The merchant remains responsible for interpreting its account data and applying its offer rules. A linked account is particularly useful when the transaction requires ongoing merchant services, such as delivery preferences or post-purchase support.

When a verifiable credential is a good fit

A credential can be useful when the relevant fact originates outside the merchant’s account system. Examples include membership in an accepted partner programme or entitlement issued by an organisation with which the merchant has an agreement.

W3C Verifiable Credentials Data Model 2.0 defines issuer, holder and verifier roles. Checking a credential’s integrity does not establish that its issuer is suitable for the merchant’s decision. Selective disclosure also depends on the chosen credential and proof mechanisms, rather than following automatically from the data model.

A merchant accepting a credential needs a trust policy: permitted issuers, required claims, freshness, status checks and any binding needed between the evidence and the represented customer. Portability of a claim does not create portability of a commercial benefit.

Compare the decision each approach supports

• Source of information: account linking accesses a business’s customer relationship; a credential conveys claims from an issuer the receiver elects to trust.
• Scope: an account connection grants defined access to services; a claim can establish a fact relevant to a decision. Purchase authority needs explicit treatment in either design.
• Updates: the merchant can consult its account state; a credential flow needs a policy for expiry, freshness and status.
• Privacy: both designs need minimum necessary access and retention. The outcome depends on what is requested, disclosed and logged.
• Acceptance: an account relationship is governed by that business; external claims require an agreed trust and benefit policy.

A worked example using both

In this hypothetical flow, a customer links an account with Merchant D to manage delivery and returns. The customer also belongs to a partner programme that Merchant D recognises for a delivery benefit.

The account connection provides the authorised delivery information. A separate credential supplies the accepted membership claim. Merchant D evaluates its partner offer and calculates a basket with the delivery benefit applied. The agent then checks that the resulting purchase fits the customer’s authority.

If the membership evidence is unavailable, the merchant can explain that the benefit cannot be applied. It should then obtain any approval needed for the changed price. The linked account can still exist; losing one eligibility claim need not require deleting the entire customer relationship.

How to choose without overbuilding

Begin with the information needed for one checkout decision. If all relevant facts already sit in the merchant’s system, start by evaluating account access. If the decision depends on another organisation’s claim, evaluate how that claim can be presented and trusted. Use both when they answer separate necessary questions.

Then test the failure paths. Can a customer disconnect an account? Can a stale claim be rejected? Can the merchant explain which evidence produced the price? Can support still resolve an order after the agent’s permission ends? These tests are more informative than selecting a mechanism because it sounds more portable.

Where AIR fits in that architecture

AIR Agent focuses on the user’s relevant credentials and permissions in agent interactions. A proposed integration can evaluate this alongside existing merchant accounts and commerce interfaces. Supported protocols, accepted issuers and deployment availability should be confirmed for the specific flow.

For a commercial example, read our guide to membership at agent checkout. For the controls around the purchase itself, read agent permissions and spending limits.

Frequently asked questions

What is account linking in AI commerce?

Account linking connects an agent-enabled shopping experience to a customer’s account at a business, within the access that the customer and business permit.

What does a verifiable credential add?

It can carry an issuer’s claim for a receiving party to check and evaluate. The receiving merchant still chooses which issuers and claims it accepts.

Can account linking and credentials work together?

Yes. A merchant account might provide delivery and order services while an accepted credential supplies evidence of membership in a partner programme.

Are credentials automatically private?

No. Privacy depends on the disclosure mechanism, identifiers, requested claims, status checking and retention. Teams need to evaluate the complete flow.

Does either approach automatically authorise a purchase?

No. The integration must establish purchase authority and enforce the customer’s limits, regardless of how account access or eligibility evidence is provided.

About AIR

We build identity, money and loyalty infrastructure for businesses. Explore AIR Agent or discuss your commerce flow with AIR.

Moca Network, the identity network of Animoca Brands.