Compare approaches to agent trust
Where SILS fits.
SILS is a trust layer. It sits between agents and the payment protocols and rails they already use. It adds owner-bound identity, private payment proofs and spending policy. It does not replace card networks, stablecoins or banks.
Layer map
One trust layer between agents and rails.
Agents reach SILS through assistant protocols. SILS proves who stands behind the agent and that it paid. The payment itself moves over existing protocols and rails.
Positions show where SILS fits, not integrations that exist today. SILS Proof is in development as a scheme inside x402. Reading AP2 mandates is in development. SILS support for ACP and MPP is not specified.29
Criteria first
Six questions for any agent trust approach.
Compare capabilities, not companies. These are the criteria used on this page.
- Owner binding
- Who stands behind the agent. A wallet, a unique human, an account at a platform, or a KYC or KYB verified person or business.
- Merchant visibility
- What the merchant learns at payment. The payer's wallet, balance and history, or only that the payment is valid.
- Policy enforcement point
- Where spending limits are enforced. In the wallet, at the network, at the issuer, on chain, or at settlement.
- Settlement options
- Which rails and networks the approach can settle on.
- Standards
- Which open protocols it uses or extends, such as x402, AP2, ERC-8004, MCP and W3C Verifiable Credentials.
- Auditability
- How an authorized party, such as an auditor or regulator, can review a specific payment without exposing everything else.
Approaches compared
Grouped by approach, not by vendor.
Each approach solves a real part of the problem. Vendors often combine more than one. Descriptions summarize public materials and may not fit every product in a group.
| Approach | Owner binding | Merchant visibility | Policy enforcement point | Settlement options | Standards | Auditability |
|---|---|---|---|---|---|---|
| Card network agent tokens9, 12, 13 | Cardholder or registered agent tied to an issuer account | Tokenized credential and order data. Raw card number withheld | Network and issuer, through token scope | Card rails. Some programs extend to stablecoins | HTTP Message Signatures, Verifiable Intent, AP2 | Network dispute and chargeback processes |
| KYA attestations20, 22 | Verified owner asserted in a signed token or credential from an identity provider | Attested owner claims. Payment privacy outside scope | Provider or wallet | Rail agnostic | JWT, OAuth and OIDC, W3C Verifiable Credentials | Provider records |
| Wallet guardrails18, 3 | Wallet control. Human binding often not documented | Public chain data. Payer address visible in standard x402 settlement | Wallet service or secure enclave | Many public chains | x402, account abstraction | Public chain history |
| Proof of personhood25 | A unique human, without legal identity | Proof that a unique human stands behind the agent. Payment privacy not documented | Not documented | Layers on x402 | x402 | Limited by design |
| Protocol identity chains24 | Account-level identity anchored to identity providers | Zero-knowledge proofs of attributes such as age or residency | Protocol features such as payment locks | The protocol's own chain, with registries on other chains | x402, MCP | Through regulated identity providers |
| Confidential payment schemes26, 30 | Not part of the scheme | Hides amounts, balances or linkage. Scope varies. Some keep addresses visible | Not part of the scheme | Specific chains, often testnet or beta | x402 | Varies by scheme |
| SILS29 | KYC or KYB verified owner. Soulbound agents under that owner In development | Proof valid, owner verified, within policy. Not the wallet, balance or history In development | Policy service, on-chain session key hook, and a settlement gate In development | Revolution primary. Base, Ethereum and Solana In development Planned | x402 scheme, ERC-8004 mirror, AP2 mandates, MCP, A2A In development | Viewing proof for one specified payment. Mandate anchor In development |
For SILS, Revolution settlement is in development. Base, Ethereum and Solana support is Planned.
Standards
What each standard covers today.
SILS extends open standards. It does not compete with them. This table shows what each one defines, as documented in its own materials.
| Standard | Identity bound to a human owner | Payer privacy | Policy and limits | Settlement | Status, Oct 2026 |
|---|---|---|---|---|---|
| x4021, 2, 3 | Out of scope by design. Sign-In-With-X proves wallet control | Not provided. Payer address and amount are public on chain | Partial. upto ceiling and timeouts. No owner policy | EVM chains, Solana and other ecosystems | v2. x402 Foundation at the Linux Foundation |
| ERC-80044 | Token owner wallet. No KYC defined | Not provided. Public registries | Not defined | Any EVM chain. Payments out of scope | Draft ERC. Mainnet deployments since Jan 2026 |
| AP25 | Through signed mandates. Depends on the credential issuer | Not defined for the on-chain leg | Intent mandate rules such as price and timing | Cards. Stablecoins through the A2A x402 extension | v0.2. Donated to the FIDO Alliance Apr 2026 |
| ACP and Shared Payment Tokens6, 7 | Through the platform account and payment provider | Card tokenization. No on-chain privacy | Token maximum amount, expiry and seller scope | Card and wallet rails | Spec snapshot 2026-04-17 |
| Visa TAP and Intelligent Commerce9, 10 | Consumer recognition, ID token, Visa-verified directory | Card tokenization | Issuer controls | VisaNet. Also bridges x402 and MPP | Live programs and pilots |
| Mastercard Agent Pay and Verifiable Intent12, 13, 14 | Registered agents. Signed intent chain | Selective disclosure of claims | Spending limits and machine-enforceable constraints | Cards, accounts and stablecoins | Agent Pay live. Verifiable Intent Draft v0.1 |
| Cross-network KYA framework15 | Operator traceability, as a principle | Not addressed | Monitoring, as a principle | Card networks. Crypto rails not addressed | Principles. No timetable announced |
| MPP8 | No identity layer found | Not documented | Payment sessions | Tempo and Stripe | Launched Mar 2026 |
| MCP and A2A16 | Signed Agent Cards prove keys, not owners | Not applicable | Not applicable | Not applicable. Distribution | MCP 2026-07-28. A2A v1.0 |
| W3C VC 2.0 and DID17 | Format. Depends on the issuer | Selective disclosure | Not applicable | Not applicable | VC 2.0 Recommendation. DID 1.1 Candidate Recommendation |
Visa's July 2026 report states: "No universal agent identity standard bridges the emerging crypto-native rails with traditional rails."11
Vendor matrix
As of October 3, 2026.
Each row summarizes the vendor's public materials and cites them. "Not documented" means the sources reviewed did not describe the capability. It does not mean the vendor lacks it.
| Vendor and offering | Approach | Owner binding | What the merchant sees | Policy controls | Settlement | Standards | Status | Sources |
|---|---|---|---|---|---|---|---|---|
| Visa Trusted Agent Protocol, Intelligent Commerce |
Card network agent tokens | Documented. Consumer recognition object with an ID token. Tokenized credentials authorized by the consumer | Partial. Card tokenization. Payer privacy from the merchant not documented | Partial. Issuer controls | VisaNet. Intelligent Commerce also bridges x402 and MPP | HTTP Message Signatures. Supports TAP, x402, MPP, ACP and UCP | TAP announced Oct 14, 2025. Programs and pilots | 9 10 11 |
| Mastercard Agent Pay, Verifiable Intent, Agent Pay for Machines |
Card network agent tokens | Documented. Registered agents with network tokens. Verifiable Intent links consumer identity to instructions | Partial. Selective disclosure of intent claims. Agent Pay for Machines records permissions on public chains by design | Documented. Spending limits and token scope | Cards, accounts and stablecoins. Agent Pay for Machines on several public chains | AP2. Verifiable Intent Draft v0.1, donated to FIDO | Agent Pay live. Agent Pay for Machines launched Jun 10, 2026 | 12 13 14 |
| Stripe ACP, Shared Payment Tokens, Tempo |
Platform checkout and tokens | Partial. Through the platform account and payment provider | Partial. Tokenized credentials. On-chain payer privacy not documented | Documented. Token maximum amount, expiry and seller scope | Cards and wallets. Tempo network with MPP | ACP, co-developed with OpenAI. MPP, co-authored with Tempo. MCP server | ACP spec 2026-04-17. Tempo mainnet Mar 18, 2026 | 6 7 8 28 |
| Coinbase Developer Platform x402 facilitator, Agentic Wallets |
Wallet guardrails | Not documented. Guardrails without human binding | Not documented. Standard x402 settlement is public on chain | Documented. Session caps, per-transaction limits, allowlists | Base, Ethereum, Solana and other chains | x402 originator. Facilitator runs KYT and OFAC checks | Agentic Wallets launched Feb 11, 2026 | 18 19 3 |
| Skyfire KYAPay |
KYA attestations | Documented. Signed JWT carrying verified owner information | Not documented. | Documented. Per-agent spending limits | USDC on chain, tokenized cards, ACH. Chains not documented | OAuth2 and OIDC. References MCP, UCP and A2A. Mastercard KYA integration announced Sep 30, 2026 | KYAPay launched Jun 26, 2025 | 20 21 |
| Crossmint Agentic Credentials, agent wallets |
KYA attestations and wallet guardrails | Partial. W3C verifiable credentials that an agent acts for a user | Not documented. | Documented. Spending limits, merchant allowlists, approval thresholds, audit logs | Stablecoin wallets across 40+ chains. Virtual cards | x402, AP2, Visa Intelligent Commerce. MiCA CASP authorization, SOC 2 | In market | 22 |
| Catena Labs Agent Commerce Kit |
KYA attestations and wallet guardrails | Partial. Verifiable identity per agent | Not documented. | Documented. Deterministic policies, spending limits, approved recipients | Cards, ACH, wires, stablecoins. Chains not documented | Agent Commerce Kit on W3C standards | Filed for an OCC national trust bank charter | 23 |
| Concordium Protocol identity, x402 integration |
Protocol identity chain | Documented. Accounts linked to a verified real-world identity | Partial. Zero-knowledge attribute proofs. Hiding the payer wallet from the merchant not documented | Partial. Protocol-level payment locks | Concordium L1. Agent registry spans other chains | x402, MCP | Live L1. x402 integration live Jun 2026 | 24 |
| World AgentKit |
Proof of personhood | Partial. Unique human, not legal identity | Partial. Proves a unique human without revealing who. Payment privacy not documented | Not documented. | Layers on x402. USDC on Base mentioned | x402 | Launched Mar 17, 2026. Expanded Jun 24, 2026 | 25 |
| TACEO Confidential x402 payments |
Confidential payment scheme | Not documented. | Partial. Hides amounts and balances. Sender and receiver addresses visible. Full privacy on roadmap | Not documented. | Base Sepolia testnet | x402 | Testnet since May 14, 2026 | 26 |
| Kite AI Kite Chain, Agent Passport |
Protocol identity chain | Partial. Agent Passport with verifiable identity. Public KYC binding not documented | Not documented. | Documented. Budgets, permission scopes, revocation, audit trails | Kite Chain, EVM compatible, stablecoin settlement | x402, AP2, MPP, MCP | Launched Apr 30, 2026 | 27 |
| SILS SILS ID, Policy, Proof |
Trust layer across rails | KYC for people, KYB for businesses, KYA for agents. Soulbound agent names In development |
Proof valid, owner verified, within policy. Wallet, balance and history not revealed In development |
Caps, categories, approval threshold, expiry, kill switch In development |
Revolution primary. Base, Ethereum and Solana In development Planned |
x402 scheme, ERC-8004 mirror, AP2 mandates. MCP server In development |
In development Not generally available |
29 |
Vendor names are used for identification only. No affiliation, partnership or endorsement is implied. Some sources are secondary and are labeled in the list below.
What the merchant sees
Same purchase. Two receipts.
In a standard x402 payment, settlement uses a transfer authorization that publishes the payer address on chain.3 Anyone with that address can read its balance and history. With SILS Proof, the merchant checks a proof instead.
Illustrative. Static example with sample values. SILS Proof is in development. The merchant learns that a settlement exists, that it matches the stated terms, that it was not presented before, and that it is bound to this request.29
Where others are stronger today
An honest list.
- Distribution. Card networks and payment platforms already reach consumers and merchants at scale. SILS does not yet.
- Shipped product and volume. Several vendors in the matrix operate in production today. SILS does not.
- Licenses. Some vendors hold or have applied for regulatory authorizations, such as an EU MiCA CASP authorization or a U.S. national trust bank charter.22, 23
- Capital. Many vendors in this market are better funded than SILS.
- Standards authorship. Others wrote x402, AP2, ACP, MPP and ERC-8004. SILS builds on their work.
- Audits and certifications. Some vendors publish SOC 2 reports and named audits. SILS has completed neither.
- Zero-knowledge identity with x402 is already live on at least one protocol identity chain.24
When SILS is not the right fit
Choose something else if:
- You need a production system today. SILS capabilities are in development or planned.
- You accept cards only and need chargeback protection now. Card network agent programs serve that case.
- You want payments with no owner behind them. SILS binds every agent to a verified owner. It is not an anonymity tool.
- You need the recipient hidden as well as the payer. SILS Proof is designed to hide the payer side.
- You need a consumer credit score. SILS Score is commercial reputation for agents and merchant entities, never the human.
- You need fiat on and off ramps from SILS directly. Ramps are planned through licensed providers.
Corrections
Spot an error? Tell SILS.
This page compares named vendors. If a cell is wrong or out of date, email the corrections inbox with a source. SILS responds within 5 business days and dates every change.
Corrections inbox
corrections@silsacommerce.com
Page history. Oct 3, 2026: comparison compiled from public sources. Next review scheduled before publication.
Sources
- x402 Foundation, "x402 Specification v2," Dec 9, 2025. github.com/x402-foundation/x402. Linux Foundation, x402 Foundation launch, Apr 2, 2026. linuxfoundation.org
- x402 docs, "Sign-In-With-X (SIWX)," accessed Oct 3, 2026. docs.x402.org/extensions/sign-in-with-x
- Ethereum EIPs, "ERC-3009: Transfer With Authorization." eips.ethereum.org/EIPS/eip-3009
- Ethereum EIPs, "ERC-8004: Trustless Agents" (Draft). eips.ethereum.org/EIPS/eip-8004
- Google Cloud, "Announcing Agent Payments Protocol (AP2)," Sep 16, 2025. cloud.google.com. Google, AP2 donated to the FIDO Alliance, Apr 28, 2026. blog.google
- Agentic Commerce Protocol repository (spec 2026-04-17), accessed Oct 3, 2026. github.com/agentic-commerce-protocol
- Stripe Docs, "Shared payment tokens," accessed Oct 3, 2026. docs.stripe.com
- The Block, "Tempo Mainnet goes live with Machine Payments Protocol for agents," Mar 18, 2026. theblock.co
- Visa, "Visa Introduces Trusted Agent Protocol," Oct 14, 2025. usa.visa.com. Visa Developer, "Trusted Agent Protocol Specifications," accessed Oct 3, 2026. developer.visa.com
- Visa, announcements at Visa Payments Forum, Jun 10, 2026. usa.visa.com
- Visa, agentic payments report, Jul 2026. visa.com
- Mastercard, "Mastercard Agent Pay," accessed Oct 3, 2026. mastercard.com
- Mastercard, "How Verifiable Intent builds trust in agentic AI commerce," Mar 5, 2026. mastercard.com. Verifiable Intent Draft v0.1. github.com/agent-intent/verifiable-intent
- Mastercard, "Mastercard Launches Agent Pay for Machines," Jun 10, 2026. investor.mastercard.com. Fortune, Jun 10, 2026. fortune.com
- Forkast, Visa, Mastercard and Ant International Know Your Agent framework, Sep 2026 (secondary). forkast.news
- Model Context Protocol, Specification (revision 2026-07-28). modelcontextprotocol.io. Linux Foundation, A2A Protocol, Apr 9, 2026. linuxfoundation.org
- W3C, "Verifiable Credentials Data Model v2.0," Recommendation, May 15, 2025. w3.org/TR/vc-data-model-2.0. W3C, "DIDs v1.1," Candidate Recommendation Snapshot, Mar 5, 2026. w3.org/TR/did-1.1
- Coinbase Developer Platform, accessed Oct 3, 2026. coinbase.com/developer-platform. Eco, "Coinbase Agentic Wallets explained" (secondary). eco.com
- x402 docs, "Facilitators," accessed Oct 3, 2026. docs.x402.org/dev-tools/facilitators
- Business Wire via StreetInsider, "Skyfire Launches Open KYAPay Protocol," Jun 26, 2025. streetinsider.com. Skyfire, accessed Oct 3, 2026. skyfire.xyz. skyfire.xyz/product
- Business Wire via FinancialContent, "Mastercard Advances Agentic Commerce With New Trust and Intelligence Services," Sep 30, 2026. financialcontent.com
- Crossmint, AI agents solution page, accessed Oct 3, 2026. crossmint.com. BlockEden, Mar 16, 2026 (secondary). blockeden.xyz
- Catena Labs, accessed Oct 3, 2026. catena.com. The Block, Catena Labs Series A and trust charter filing, May 20, 2026. theblock.co
- Concordium, accessed Oct 3, 2026. concordium.com. Concordium, "x402 Explained," Jul 28, 2026. concordium.com/article. KuCoin Insight, Sep 24, 2026 (secondary). kucoin.com
- BlockEden, "World AgentKit and x402," Mar 17, 2026 (secondary). blockeden.xyz. HackerNoon, Jun 24, 2026 (secondary). hackernoon.com
- IT Brief, "TACEO launches confidential payments for x402 on Base," May 14, 2026. itbrief.news
- Kite AI, accessed Oct 3, 2026. gokite.ai. The Block (press release), Kite Chain and Agent Passport, Apr 30, 2026. theblock.co
- Stripe Docs, "Agents and AI on Stripe," accessed Oct 3, 2026. docs.stripe.com/agents. Decrypt, Tempo mainnet and MPP, Mar 18, 2026. decrypt.co
- Revolution Network Whitepaper v2.0, October 2026, draft for review: §5.1, §6.2, §8.6, §8.8, §14. SILS component status as of Oct 3, 2026.
- zBase, "Private payments for AI agents," accessed Oct 3, 2026. zbase.app