X402 Secure
X402 Secure is the XRPL-first embedded risk layer for x402, Verifiable Intent, and AP2-compatible agent payments.
X402 Secure is the XRPL-first embedded risk layer for agent payments over x402 and AP2-compatible flows. On XRPL, it runs behind the hosted XRPL x402 Facilitator as an internal risk feature before settlement. The product connects payment requirements, reasoning traces, Verifiable Intent evidence, AP2 mandate references, external signals, and settlement receipts into a risk decision that downstream services can enforce.
X402 Secure is intentionally focused: it is the risk and evidence layer around machine payments, not a wallet, custody product, or replacement for payment rails. Trustline provides the canonical risk assessment and evidence records. X402 Secure owns the x402 integration, XRPL Facilitator extension semantics, payment binding, gateway behavior, and facilitator-facing enforcement.
Learn more about the product at t54.ai/x402-secure.
Public Processing Footprint
X402 Secure has a public processing footprint across the x402 ecosystem. Public ecosystem records for the payTo addresses associated with X402 Secure show more than 32 million all-time transactions.
This footprint is a high-level traction signal. It shows that X402 Secure is connected to visible x402 payment activity at meaningful scale and gives developers and partners a concrete reference point for the Trustline-backed risk layer behind the product.
What X402 Secure Adds
X402 Secure adds an embedded risk envelope around XRPL x402 and companion x402 rails.
| Layer | Responsibility |
|---|---|
| Agent or buyer client | Requests a protected resource, receives 402 Payment Required, collects trace or intent evidence, and retries with payment headers. |
| Resource server | Publishes payment requirements and enforces access only after payment verification. |
| XRPL x402 Facilitator | Serves as the public XRPL payment edge and calls X402 Secure internally when X402 Secure extension fields are present. |
| X402 Secure | Parses risk headers, binds evidence to the payment context, calls Trustline, and returns an enforcement-ready decision. |
| Trustline | Evaluates risk, verifies evidence and generic constraints, stores evidence records, and records receipts. |
| Companion facilitators or proxy paths | Verify and settle Base, Solana, or self-hosted x402 payment payloads with the same Trustline-backed risk layer. |
This separation keeps XRPL as the first-class public payment edge while keeping the risk logic reusable across additional rails. It also gives institutions and service providers a clearer operating model: x402 handles the payment interaction, the XRPL x402 Facilitator handles rail-specific verification and settlement, and Trustline-backed X402 Secure handles the underwriting decision before access or settlement proceeds.
Verifiable Intent And AP2
X402 Secure's latest integration work focuses on Verifiable Intent and AP2 inside the XRPL x402 payment path. Verifiable Intent gives agents a cryptographic way to present delegated intent and selective evidence. AP2 provides a protocol model for agent payments through intent, cart, and payment mandates. X402 Secure is designed to operate as a core risk service by binding those proofs and mandates to actual payment requirements and settlement events.
This binding step matters because intent evidence is not the same thing as payment approval. A credential or mandate becomes financially meaningful only when it is connected to the amount, merchant, resource, settlement rail, receipt, and policy being enforced. X402 Secure is built to make that connection operational.
Primary Use Cases
X402 Secure supports several common use cases.
| Use case | Value |
|---|---|
| XRPL x402 settlement gating | The XRPL x402 Facilitator can call embedded X402 Secure before settlement. |
| Agent API purchases | Agents can pay for protected resources while providing trace and intent evidence. |
| Service provider protection | Merchants and API providers can require risk evaluation before granting access. |
| Facilitator enforcement | Facilitators can block settlement when Trustline returns deny or review under enforce-mode policy. |
| Dispute and audit records | Evidence, assessments, and receipts can be preserved for later review. |
| AP2-compatible payment flows | Mandate references can be validated and bound to the payment context. |
XRPL-First Rails And Direction
X402 Secure is first-class on XRPL through T54's hosted XRPL x402 Facilitator. Buyers and merchants use the Facilitator as the public payment edge, and X402 Secure runs internally when X402 Secure extension fields, Verifiable Intent evidence, AP2 mandate references, or policy requirements are present.
Base and Solana remain supported companion paths through the hosted paid API and open-source proxy. They use the same Trustline-backed risk layer, but the product story starts with XRPL because X402 Secure is embedded into the XRPL x402 Facilitator rather than exposed as a separate public XRPL risk endpoint.
The strategic direction is simple: wherever agents can pay, the ecosystem needs a risk layer that can understand authorization, evidence, counterparty risk, settlement binding, and liability-sensitive decision records. X402 Secure is t54's product for that layer.