Accept on-chain payments for anything you sell

TRXN verifies cryptocurrency payments against your invoices. You create products and prices in fiat currency, generate invoices, and TRXN monitors the blockchain to confirm that the correct amount was sent to the right address within the expected timeframe. It's payment verification infrastructure for the blockchain, without actually processing the transaction.

TRXN currently supports BTC, ETH, and POL with verification across their respective blockchains. Additional chains and currencies are on the roadmap.

You define your products and prices in any fiat currency (USD, EUR, etc.). When an invoice is created, TRXN uses real-time exchange rates from industry-leading exchange providers (CoinMarketCap, CoinAPI, etc.) to calculate the equivalent crypto amount. Configurable slippage margins account for price movement between checkout and blockchain confirmation.

No. TRXN is a verification layer, not a payment processor or custodian. Payments go directly between your customer and your wallet. TRXN monitors the blockchain to verify that the payment matches your invoice.

TRXN supports phase-based subscription management. You can model free trials, promotional pricing, and graduated rates. Each phase has its own duration and price. Subscriptions automatically transition between phases and generate invoices accordingly.

A single crypto payment can be allocated across multiple invoices. This handles common scenarios like overpayments, partial payments, and customers who pay multiple invoices in one transaction. You can apply a transaction fully or partially to any open invoice.

When customers pay through exchanges like Coinbase, the exchange batches multiple transactions together, so the on-chain sender address won't match your customer's address. A payment claim lets your customer submit proof that they made a specific payment, which you can then verify and apply to the correct invoice.

x402 is an open standard for internet-native payments based on the HTTP 402 status code. When a client requests a paid resource, the server responds with 402 Payment Required along with payment details. The client pays with crypto and retries the request. No accounts, no API keys, no signup required.

TRXN handles the on-chain verification side of x402 payments. When a client pays in response to a 402, TRXN verifies the transaction on the blockchain and confirms the payment matches the requested amount. You add x402 support to your endpoints and TRXN handles the rest.

Yes. x402 is designed for both human and machine clients. AI agents can autonomously pay for APIs, data, and compute resources using the x402 protocol. No human intervention needed. This makes x402 a natural payment layer for the agentic web.

TRXN provides a secure REST API for managing products, prices, customers, invoices, subscriptions, and payment verification. Webhooks notify your application when events occur (e.g., invoice paid, subscription updated). Full API documentation is available for all endpoints.

Yes. Every account includes sandbox environments. Create as many as you need to test different configurations, integrations, or edge cases. Each sandbox is fully isolated: create invoices, simulate payments, and verify behavior without touching real funds or production data.