Stripe's Link now gives shopping agents a balance to spend. Follow one price-drop order through the night it lands
At 1 a.m. you mark a pair of shoes down to $89. By 1:04, someone's agent has bought them with money its owner set aside last week, and the owner is asleep. Here's what your store sees, and what it should be ready for.
Link balance, introduced October 26, 2026, lets people fund a balance and set a per-purchase limit so their agent can buy without asking each time. It settles in stablecoins on Tempo, but Finextra reports that a Stripe Issuing virtual debit card lets the agent pay through ordinary card checkout, so merchants see a card payment and need no stablecoin support. For stores, that means unattended purchases at odd hours: check fraud rules, price-change timing, confirmation emails and returns for orders nobody watched being placed.
The setup, a week earlier
On October 26, 2026, Stripe's Link introduced Link balance. According to Tempo's write-up, people add money to a balance and set a limit per purchase, and their agent can spend within it without asking each time and without seeing their card details. Balances settle in stablecoins on Tempo, at any hour. It's rolling out to users of the Instinct assistant in eligible US regions, with other agents able to connect through the open-source Link CLI.
The reason given is simple. A card payment can trigger an issuer approval, so the agent has to wait for a person, which rules out purchases that can't wait. Tempo's examples are tickets when a presale opens and shoes when the price drops.
The detail that matters most for stores comes from Finextra's November 1 analysis by Sam Boboev: Link's agent wallet enforces the per-purchase limit, and a Stripe Issuing virtual debit card backed by the balance lets the agent pay through ordinary card checkout. Merchants receive a card payment and don't need to support stablecoins.
So nothing changes in your checkout. What changes is who's clicking Buy, and when. To make that concrete, here is one illustrative night at an illustrative shoe store. The shopper told their agent, a week ago, something like Finextra's own example: buy these shoes when the price falls below $90.
Sequence of work
One price-drop order, hour by hour
- A week earlier
Shopper funds a balance and sets a limit.
- 1:00 a.m.
Scheduled markdown goes live.
- 1:04 a.m.
Agent checks out with a card payment.
- 1:05 a.m.
Confirmation email goes out.
- 7:30 a.m.
Shopper reads it, keeps or cancels.
1:00 a.m. The price drops
Your scheduled promotion starts at 1:00 a.m. The shoes go from $120 to $89.
What to check: do promotions start when you think they do? Scheduled sales often begin at midnight in one time zone and look odd in another. An agent watching for a price will see it the moment it changes, including a mistaken price that's live for ten minutes before someone notices. If a price error at night would hurt, decide now whether big markdowns need a second person to approve them before they go live.
The agent did exactly what it was told. The question for the store is whether the rest of the night was set up for a buyer who wasn't awake.
1:04 a.m. The agent buys
The agent sees the price, checks it's below the shopper's line and within the per-purchase limit, and checks out. To your store, it's a card payment like any other.
What to check: your fraud rules. A new-looking device, an unusual hour, a quick checkout right after a price change: some of the signals that fraud tools weigh could describe an agent doing its job. Look at what your rules would do with an order like this. If they'd decline it, you lose the sale. If they'd hold it for review, your team needs to get to it before the shopper wakes up and wonders why nothing happened.
We've written about the questions an authority card should answer for agents that buy. Price-watch orders are a good case to test it against: the shopper decided the price ahead of time, and the agent acted on it without asking again.
1:05 a.m. The confirmation goes out
Your store sends an order confirmation. Depending on the agent and how it was set up, that email may go to the shopper, to an address the agent manages, or both.
What to check: does your confirmation make sense to someone reading it at 7 a.m. who didn't watch it happen? Say plainly what was bought, the size and color, the price paid, and when it will ship. If your confirmation leans on "Thanks for your order!" and a photo, add the details a person would need to recognize a purchase they delegated.
7:30 a.m. The shopper wakes up
The shopper sees the email. Most likely they're pleased. Sometimes they aren't: wrong size, they already bought a pair, or they forgot they'd asked.
What to check: your returns and cancellation policy, as seen by someone whose agent made the purchase. If you allow cancellation before shipping, make that easy to find in the confirmation. A cancel link that works without logging in, for the first hour or two, is a small kindness to someone sorting out what their agent did while they slept. If an order is already packed, say so. And make sure your support team knows that "I didn't place this order" might mean "my agent did," which is a different conversation from fraud. Our note on agents that prepare a payment covers where a person should stay in the loop; this is the other end of that, where the person arrives after the fact.
By 9:00 a.m., your team is in. Someone looks at the overnight orders and sees a cluster right after the markdown went live. That's worth reading carefully rather than celebrating or panicking. Were they spread across many customers, or a few? Did any fail the fraud check, and if so, why? Did the markdown sell through faster than you planned for a sale meant to run all week? Price-watching agents can make a promotion's first hour look very different from what your past sales would predict, so look at that hour on its own before you judge how the promotion did.
The agent did exactly what it was told. The question for the store is whether the rest of the night was set up for a buyer who wasn't awake.
What to do this month
You don't need to support stablecoins or change checkout for this, based on Finextra's description. You do want to look at four things before more people hand their agents a balance:
- Price changes at night. Who approves big markdowns, and when do they go live?
- Fraud rules. What happens to a fast, off-hours, card-not-present order placed right after a price change?
- Confirmations. Could someone who didn't place the order recognize what they bought?
- Support and returns. Does your team have a script for "my agent bought this"?
None of this is unique to Link. Any agent that can pay through ordinary card checkout raises the same questions, and Link's per-purchase limit means the shopper already put a ceiling on what the agent can spend.
If you'd like help getting your store ready for orders placed by agents, from checkout and fraud settings to the emails and policies around them, our ecommerce team does that work. Get in touch and tell us what a night of orders looks like for you now.
Related work: Spin Market.
Decision guide
What the store should check
| Consideration | Moment | Check |
|---|---|---|
| Price change | Agents see it instantly. | Second approval for big markdowns |
| Checkout | Looks like any card payment. | Fraud rules for fast, off-hours orders |
| Confirmation | Read later, by someone else. | Item, size, price and ship date in plain words |
| Morning after | Shopper may change their mind. | Easy cancellation and a support script |
We build alongside the people doing the work.
Bring us the problem you’re thinking about.