Four competing agent payment protocols just fragmented compliance

Dev.to / 5/10/2026

💬 OpinionSignals & Early TrendsIdeas & Deep AnalysisIndustry & Market Moves

Key Points

  • Four different agent-to-agent payment protocols have been launched by major companies (Coinbase’s X402, OpenAI and Stripe’s ACP, Google’s AP2, and Visa’s Trusty), creating fragmentation with no interoperability standards.
  • The lack of shared standards makes compliance and auditability harder, raising questions about responsibility for audit trails, decision-context logging, and transaction-chain reconstruction.
  • Article 12’s compliance requirements focus on providing meaningful information about the underlying logic regardless of which payment protocol clears the transaction.
  • A proposed approach is to place an audit layer (e.g., BizSuite) above the payment protocol to capture agent spending decisions before they reach the payment rail, keeping documentation protocol-agnostic.

Coinbase ships X402. OpenAI and Stripe ship ACP. Google ships AP2. Visa ships Trusty.

Four competing protocols for agent-to-agent payments. Zero interoperability standards.

This is great for innovation. It's a disaster for compliance.

If your agent uses ACP to pay a vendor's agent running on X402, who's responsible for the audit trail? Which protocol logs the decision context? How do you reconstruct the transaction chain when the auditor asks?

Article 12 doesn't care which protocol you picked. It requires "meaningful information about the logic involved" — regardless of whether the payment cleared via Visa, Stripe, or Coinbase.

BizSuite's audit layer sits above the protocol layer. It captures agent spending decisions before they hit the payment rail, so your compliance documentation works whether you're on ACP, X402, or something that ships next month.

Protocol fragmentation is inevitable. Audit fragmentation is optional.

If you're building on agent payments, pick your protocol for speed — but build your audit layer protocol-agnostic from day one.