Accept payments from humans and AI agents
Create payment experiences that work for both people and AI agents without maintaining separate payment integrations for each. When you create a payment, you receive two ways to complete it. People can use a hosted checkout, while AI agents can use a programmatic payment URL.
Both entry points represent the same payment and can be reconciled against the same reference in your system. This works well when you already know what needs to be paid, such as an invoice, service fee, order balance or other one-time charge.
Your product does not need to be connected through MCP to use these payment experiences. You can create a payment and give the appropriate payment URL directly to a person or AI agent.
When to use this
Use this approach when the amount to be paid is already known and you want either a person or an AI agent to be able to complete the payment. For example, you might have an invoice for $125 that can be paid by the customer directly or by an AI agent acting on their behalf.
If an AI agent needs to interact with your product first to discover products, check availability, create an order or calculate the final amount, use Let AI agents buy from you instead.
Before you begin
You need a Mitu account, a server-side API key and a payment you want to collect. You should also have a reference from your own system that identifies what the payment belongs to, such as an order ID, invoice number or booking reference.
Create the payment
Create a payment link for the amount you want to collect.
Use reference to associate the payment with a record in your own system, such as an invoice number, order ID or booking reference. When the payment completes, the same reference can be returned with the payment event so your backend knows which record should be updated.
Use metadata for additional information you want to associate with the payment. Do not store sensitive information or secrets in metadata.
Learn more about Payment experiences.
Use the right payment URL
A payment provides separate entry points for human and agent payers.
Use the checkout URL when a person is paying. You can send it through your website, application, email, SMS, WhatsApp or another customer channel. Use the agent URL when an AI agent is paying.
You do not need to know which type of payer will complete the payment when you create it. Both entry points belong to the same underlying payment.
Let a person pay
A person opens the checkout URL and completes the payment through the hosted checkout experience. The checkout presents the payment details and the payment methods available to the payer.
You can use the checkout URL anywhere you would normally share a payment link, such as an invoice, customer portal, message or payment request. Your application does not need to build or maintain the checkout interface.
Let an AI agent pay
When an AI agent receives the agent URL, it can use the URL to complete the payment programmatically. Mitu handles the agent payment flow and the supported payment protocols required to complete the transaction, so your business does not need to implement separate x402 or MPP integrations.
Once payment succeeds, it represents the same payment that would have been completed through the human checkout.
Learn more about Agent payments.
Reconcile the payment
Whether a person or an AI agent pays, reconcile the payment using the reference from your own system.
For example, if you created the payment with:
your payment event can be associated with INV-8841 in your application. This means your backend does not need separate reconciliation logic for human and agent payments because both payer experiences resolve to the same business record.
Do not mark the payment as completed based only on a browser redirect or a response reported by an AI client. Use a verified payment event or retrieve the payment state from the API.
Receive payment events
Configure webhooks so your backend can receive payment events. When a payment completes, use the event to update the corresponding record in your system.
For example, if the payment carries the reference INV-8841, your webhook handler can use that reference to find the corresponding invoice and mark it as paid. The same handling can be used regardless of whether the payment was completed by a person or an AI agent.
Settle your funds
Funds you receive are added to your Mitu balance, where they can be settled to a supported bank account or withdrawn to an onchain address.
How the customer paid does not change how you settle the funds. Payments from humans and AI agents become part of the same balance available to your business.
Learn more about Settlement.
Other payment experiences
The same payment infrastructure can support more than one-time charges. Use invoices when you need formal billing with line items, due dates and an invoice lifecycle, or use subscriptions when customers should be charged on a recurring basis.
Use the payment experience that matches what you are collecting rather than building separate human and agent payment systems. Learn more about Invoices and Subscriptions.
One payment, two payer experiences
Your application can create a payment without needing to know whether a person or an AI agent will ultimately complete it. People receive a checkout experience designed for them, while AI agents receive a programmatic payment experience designed for agents. Both resolve to the same payment and the same reference in your system.
You continue to control what is being paid for, the amount and how it maps to your own records. Mitu handles the appropriate payment experience for the payer and makes the resulting funds available for settlement.