Four AI payment standards, zero agent identity solutions

Dev.to / 5/16/2026

💬 OpinionSignals & Early TrendsIdeas & Deep AnalysisIndustry & Market Moves

Key Points

  • Four new AI payment standards have been introduced recently by major players, including Stripe infrastructure shipping and Google’s AP2 announcement, showing rapid ecosystem momentum.
  • The article argues that these payment standards still fail to provide “agent identity,” which is essential for secure payments by autonomous agents rather than humans.
  • It highlights three missing capabilities for agent payments: persistent identity across deployments and vendors, trust history tracking (overspending, compromise, policy adherence), and cross-system revocation if an agent turns rogue.
  • The author proposes “agent FICO” as a trust layer above payment protocols that assigns persistent identity, maintains a continuously updated trust score, and enforces policy boundaries like spend limits and vendor allowlists.
  • It concludes that payment protocol upgrades alone are insufficient and recommends implementing the trust layer first to reduce the risk of major agent fraud incidents in 2026.

four new AI payment standards emerged in the last 90 days. stripe shipped infrastructure. google announced AP2. the ecosystem is moving fast.

but here's the problem: none of these standards solve agent identity.

when a human makes a payment, we have:

  • government-issued ID
  • credit history
  • fraud detection tied to behavioral patterns

when an agent makes a payment, we have... an API key?

that's not enough. you need:

persistent identity. the same agent across deployments, versions, and vendors. not just "this API call came from this server."

trust history. has this agent overspent before? has it been compromised? does it follow policy?

revocation. if an agent goes rogue, you need to kill its payment authority everywhere — not just in your own system.

this is the gap i'm solving with agent FICO. it's a trust layer that sits above the payment protocol. every agent gets:

  • a persistent identity (tied to deployment metadata, not just API keys)
  • a trust score (updated after every transaction)
  • a policy boundary (spend limits, vendor whitelists, compliance rules)

the payment standards are necessary infrastructure. but they're not sufficient.

we're building the highway before we've invented the driver's license. that works until the first major agent fraud incident — then everyone's going to scramble for identity and trust solutions.

if you're implementing any of these new payment standards in 2026, add the trust layer first. the protocol won't save you when an agent misbehaves.