Your user funds their own balance
Agent pays with your user’s card
$600Flights & hotelsUntil Friday
Merchant seesyour user
Your user funds balances in your app
Agent buys on the user’s behalf
User’s balance chargedon your company’s card
Merchantsees your company
Your user approves the agent once
Agent gets a stand-in card number
Agent makes purchasebased on user’s rules
Merchantsees an agent with permission
Your user funds their own balance and gets a card with the agent’s rules on it. The agent pays with that card. The merchant sees your user, and your user keeps the protections of a card purchase.
Example: a travel agent books a flight on its user’s card, with a $600 limit for flights and hotels only, until Friday.
Your users fund balances in your app. When an agent buys something, your company’s card pays the merchant and the user’s balance is charged. You deal with the merchant on the user’s behalf, the way a travel agency does.
Visa and Mastercard now let a person hand an agent a limited version of a card. The person approves the agent once, and the network gives it a stand-in card number that works only for that agent and that task, which merchants can recognize as an agent acting with permission. Your program is enabled for Visa Intelligent Commerce and Mastercard Agent Pay, so a card from your program carries the networks’ credential as well as your rules.
Example: your user’s agent card carries a Visa agent token for this week’s groceries. A merchant that checks for the networks’ credential sees it, and anything outside the task declines.
“Flights and hotels, up to $600, until Friday.”
“$5 a query, and never more than $1,000 a day.”
“One supplier, one invoice, then the card dies.”
“Ask me above $500. Do not bother me below it.”
“Software subscriptions only, $300 a month, cancel any time.”
“Only these three contractors, never more than their invoice.”
“Twenty agents, twenty cards, $10,000 across all of them.”
“Flowers today. Nothing tomorrow.”
No. They add money, see a balance, and watch what the agent does with it. Stablecoins are how Rain settles underneath.
It cannot spend past the limits on its card. For a purchase on a user’s own card, the user keeps the dispute rights that come with any card payment. When your platform is the buyer, you handle the merchant on the user’s behalf.
Rain runs programs for partners with users in the US, Europe and the UK, Latin America, and Asia, and cards work at 175 million merchant locations in 220 countries and territories. We will confirm the markets you need on the first call.
In some cases, depending on how your checkout and your sellers are set up. Talk to us.
Mostly they do not have to. The agent pulls what it needs from a bank account or a card the user connected once, in seconds. Users who prefer to keep a balance can, and stablecoins they already hold work too.
Yes. They share the same balance, rules, and ledger, so adding a second is a configuration, not a new integration.
No. Rain carries the program: card issuing, the compliance framework, and settlement with the networks. You keep the brand, the users, and the rules.
It depends on the shape you pick and the market. On the first call we give you the steps, who owns each one, and the typical timeline, in writing.
