Your payment profile, readable by AI agents
payments.txt is an open standard that publishes your wallets, IBAN, payment terms, and checkout URL in a single plain-text file — so AI agents can discover how to pay you without any integration work.
Think robots.txt — but for getting paid
Just as robots.txt tells crawlers what to skip and llms.txt gives AI models context, payments.txt tells autonomous agents exactly how to pay you. It lives at a predictable URL, uses a simple key-value format, and is generated automatically from your PayRequest account data.
Wallets & bank details
Your EVM address, Solana address, and IBAN in one place. Agents read these to choose the right payment rail.
Payment terms
Default due days and late fee percentage. Agents use these when creating invoices or scheduling payments on your behalf.
X402 endpoints
Machine-payment URLs so agents can settle USDC directly, without a human checkout. Full autonomous billing support.
Human fallback
Your payrequest.me checkout URL is always included — so agents that can't pay autonomously can hand off to a human.
Auto-generated from your account
No setup required. Fill in your account details — wallets, IBAN, payment terms — and your payments.txt is live instantly. It stays current as you update your settings.
Connect your payment details
Add your EVM wallet in Provider Settings, your IBAN in Business Details, and your default payment terms. Nothing extra to configure.
payments.txt goes live
Your manifest is immediately available at payrequest.me/yourhandle/payments.txt. Changes appear in seconds — no cache to clear.
Discovery tag in your page head
Your payment page includes a link rel="payments" tag so agents parsing your HTML can find the manifest without guessing the URL.
Agents pay you autonomously
AI agents read your manifest, choose the best payment rail, and settle via X402 or bank transfer — no human click required.
Two ways agents find your manifest
Direct URL
Any agent that knows your PayRequest handle can request payrequest.me/yourhandle/payments.txt directly. No API key, no auth, publicly accessible.
HTML link tag
Your payment page includes a link rel="payments" tag in the document head. Agents that parse your page find the manifest URL without guessing.
Not PayRequest-only — any platform can implement it
payments.txt is an MIT-licensed open standard. The full spec, format reference, and implementation guides for PHP, Node.js, and other platforms are on GitHub. Any billing platform can generate a payments.txt — we built the standard and implemented it first.
Who benefits from payments.txt
AI billing agents
Claude, GPT, and custom agents can discover your payment profile and settle invoices autonomously — no manual integration.
Procurement systems
Enterprise procurement software can read your payment terms and preferred currency before generating a PO.
Developer tools
APIs and SaaS tools that need to bill usage can discover your checkout URL and open a payment without human intervention.
Future-proof billing
As agentic AI workflows become standard, having a machine-readable payment profile positions you ahead of the curve.
Frequently asked questions
Does this require any setup?
No. The moment you have a PayRequest account with any payment details filled in, your payments.txt is live. There's nothing to enable or configure separately.
Is payments.txt a PayRequest-only thing?
No. It's an open standard. We published the spec on GitHub under MIT license — any billing platform can implement it. PayRequest was the first to build it and auto-generates it for every account.
What if I haven't connected a wallet or IBAN?
Only sections with real data appear in your manifest. A fresh account with no bank or wallet details will show payment terms and the hosted checkout URL. Nothing inaccurate is published.
Is my manifest public?
Yes. payments.txt is intentionally public so any agent can read it without authentication. It contains only payment routing data — no sensitive account information, API keys, or customer data.
How does it relate to X402?
payments.txt includes your X402 discovery URL and payment endpoint. When an agent reads your manifest, it can use those endpoints to pay you autonomously in USDC on Base without a human checkout.
Will it update automatically?
Yes. The manifest is generated live from your account data. Change your IBAN, update your default due days, or add a new wallet — the manifest reflects it immediately.
Your payments.txt is waiting
Every PayRequest account gets a machine-readable payment manifest automatically. Connect your wallet, add your IBAN, and AI agents can start discovering how to pay you.