Back

Thanksgiving for 12, oven for 4…

Thanksgiving for 12 in an oven built for 4 rarely goes to plan. Most payment estates face Black Friday the same way: built for an ordinary day, then hit with peak volumes all at once. The providers who keep trading are the ones who planned for failure, with offline mode and backup routes that switch on before anyone at the register notices. 

At around 10am every Thanksgiving, home cooks have a “face-palm” moment…

…The oven that handled dinner for four all year can't fit a 20-pound turkey, two trays of stuffing and a pie at the same time.

A classic case of an ordinary kitchen expected to perform in extraordinary situations.

Believe it or not, payment estates have the same problem.

Most are sized and tested for a normal day's trading. Then Thanksgiving weekend arrives, Black Friday fills every queue, and any weak spot in the setup shows up at the moment it costs the most.

For the providers behind those terminals (PSPs & ISOs), the question is whether their estate was built for four or for twelve. To find out what gives way first, and what the calmest providers on Black Friday do differently, we spoke to Samantha Wildonger, VP of Product, Sarah Reineck, Director of Marketing & Communications, and Sierra McMillen, Head of Partnerships, US. Their answers follow the course of a typical Thanksgiving, from the night before to Black Friday morning… 

‘Twas the night before Thanksgiving…

The trouble starts long before the oven door opens. Plenty of estates go into Thanksgiving weekend unready for the peak. Part of the reason is that a peak day is very hard to practice for, much like the home cook who has made the recipe a dozen times but never for twelve people at once.

Samantha puts it down to not knowing what you don't know. 

"A lot of people think they're planning for their peak days, and that they have all their T's crossed and their I's dotted. Then in the moment, things go wrong, and they don't immediately know how to solve those problems, or even have visibility into where the problem lies."

Samantha Wildonger, VP of Product, Aevi

Sarah sees something else at play... 

"There's a kind of assumption that peak is the acquirer's problem or the gateway's problem. In practice, it lands on whoever the merchant calls, and providers usually find out the hard way, when the support lines start ringing.”

Sarah Reineck, Director of Marketing & Communications, Aevi

Testing is harder than it sounds. "How can you test a busy store day, with crowded mobile networks and nervous staff retrying the transaction every second?" Sarah asks. Her point is about people as much as technology. A test can recreate the transaction volumes, but it can't recreate how staff and shoppers behave under that kind of pressure.

Samantha notes that large retailers do have their own payments and quality assurance teams, but they test at head-office level rather than in individual stores. The stores themselves are left hoping their provider has tested enough.

Sierra points to a specific gap.

"Providers usually test expected volumes, but what they miss is testing what happens when something fails during that time, and what the recovery plan is. That kind of ‘what if’ testing is expensive, so it often gets skipped. Providers usually find out with the customers already queuing."

Sierra McMillen, Head of Partnerships US, Aevi

10am: One oven and no plan B

At 10am, with the guests four hours away, the cook finally takes a proper look at what the kitchen can and can’t handle. For payment providers, that means a handful of weak points that are easy to miss until a peak day finds them.

The first, according to Samantha, is having no offline or cellular backup. "The most common issue is connectivity. They trust their own networks more than they should." When the local network goes down, terminals with no fallback simply stop taking payments.

The second is relying on a single processor or acquirer. "If they go down, your whole system goes down as well," she says. Routing transactions to a second processor keeps the store trading. Even so, many merchants never think about it and simply stay with their one vendor on the back end.

Sierra warns that a second acquirer isn't always the safety net it looks like. "People think you can solve this by having a multi-acquiring strategy, but if they both rely on the same gateway or network, then it doesn't matter." The weak point is any dependency the whole chain shares, so providers need to know which partners sit where and how they connect to one another.

There's a slower kind of failure too. If a shopper wants to tap with Apple Pay or Google Pay and the terminal doesn't accept it, they experience the inconvenience of finding a physical card instead. Each fumble adds seconds, and on a peak day those seconds turn into a longer line. Samantha points out that offering the payment methods people are used to keeps the line moving.

Here's each weak point side by side with what it causes and how it's fixed:

Icon warning

Weak point

No offline or cellular backup

A single processor or acquirer

Shared dependencies

Missing payment methods

Icon search

What goes wrong on the day

When the local network drops, terminals stop taking payments.

If it goes down, the whole store goes down with it.

Two acquirers that rely on the same gateway or network fail together.

Shoppers fumble for another card, and the line slows down.

Icon checked/compliance

The fix

Offline mode that switches on automatically (more on this below)

A second route for transactions. An orchestration layer routes transactions to a second processor or acquirer, so one outage doesn’t stop the store.

An orchestration layer that sits across terminals, processors and payment methods, giving providers a single view of how their partners connect and where the shared risks are.

Payment methods pre-certified for supported terminals can be switched on for merchants in days, without rebuilding the estate.

2pm: The doorbell rings

At two o’clock the guests arrive, all at once, and the pressure peaks.

When a Thanksgiving dinner goes wrong, it’s usually because the oven runs out of space or the timings slip. Peak-day payments fail in a similar way. 

"It's usually not the payment itself, it's everything around it. Connectivity tends to go first. On a busy shopping day, especially in a crowded mall, hundreds of phones compete for the same network and terminals start timing out. Response times further up the chain slow down, terminals retry, and the merchant risks double charges on top of a growing queue.”

Sarah Reineck, Director of Marketing & Communications, Aevi

For Sierra, a problem anywhere in the chain shows up as a loss of speed. One slow link between the register, the gateway and the acquirer is enough to cause those timeouts. "For the shopper, the terminal is to blame, because that is what everyone can see."

The back end can cause trouble too. Sarah points to an update pushed the same week, or a certificate that expires at the wrong moment. Neither would matter much on a standard day, but on Black Friday, either one can take a store's payments down.

Samantha agrees that connectivity is the most common cause… 

"Once you start to hit that threshold of too many things happening at once, or losing connectivity, it's really important to have a backup." 

Samantha Wildonger, VP of Product, Aevi

5pm: When the guests start getting agitated…

Three hours later, dinner still hasn’t made it to the table, and the guests start to get a bit grumbly.  

When a peak-day setup fails, Sarah describes the scene in store as "a spinning terminal and a queue that stops moving."

Aevi's own research, a survey of more than 2,000 shoppers in the US, shows how little patience shoppers have for it. In the past year, 36% of US shoppers walked out of a store over a payment problem.

The research also found that shoppers often blame themselves. One US respondent described the moment her payment was declined:

"One experience that was negative is when payment was declined and made me feel embarrassed. Then all along it was the store's system issue not my card."

This shopper didn't complain, but she did leave believing her own card had let her down.

Samantha knows the feeling and described a time when she was filling up at a gas station on a major highway during an internet outage when two of her cards declined. Then she saw everyone else's cards declining too. Inside, the line stretched about 50 feet to the door. The ATMs were down, and the next fuel stop meant leaving the highway. Shoppers without cash had nowhere else to go. Needless to say, the next time Samantha passed that station, she drove on to the following rest area. For Samantha, it was a textbook example of what happens without offline mode. With it, the station could have kept accepting cards, within limits it had set in advance, and sent the payments through once the connection returned.

Samantha's experience is far from unusual. A 2026 study found that US consumers will wait just 7 minutes before abandoning a purchase when payments go down. It also found that 63% of major payment outages happen during peak trading periods.

Even when a shopper stays and the sale is eventually saved, the damage doesn't end at the register. As Sierra puts it: "It can be less about losing the sale and more about the reputation, and whether the customer returns."

For providers, the bill arrives afterwards. There are support calls on the day, then transaction investigations, queries about charges and missing settlements, and sometimes service credits. Samantha adds the damage to the merchant's own brand: "How much did they lose in that day, and how much have they lost overall? That's a hard stat to measure."

Sarah sees the biggest cost further down the line. "It's the merchant who remembers their best trading day going wrong, and brings it up at contract renewal."

Meanwhile, next door…

Next door, a neighbor cooking for the same number of guests (in a kitchen the same size), served dinner on time. And how did they do this? Well, they lined up a second oven.

For payment providers, the best backups work the same way: nobody in the store ever sees them.

The main one is offline mode, also known as store and forward. When a terminal loses its connection, it keeps accepting payments, holds them, and sends them through automatically once the connection returns. Samantha gives the example of stadiums at halftime, which switch into offline mode on purpose to keep the lines short, then process the transactions later.

“The switch has to happen on its own. You don't want your team scrambling on your peak day just to figure out how to enable your backup, it just needs to automatically fail over. The same goes for a backup processor. It's also important to see where in the chain the failure is, whether that's the processor or a handful of locations, so the right team can start fixing it straight away.”

Samantha Wildonger, VP of Product, Aevi

Sierra's test for whether a plan is real is simple. “You have to deliberately take something down in testing and prove there is a path to continue payments, whether that's an alternative route, backup connectivity or offline acceptance. Clear recovery procedures need to be in place as well.”

Why the staff can't be part of the plan

If the backup isn't automatic, the people at the register usually won't use it. Samantha has heard of staff writing customers' card details on pieces of paper to run later when the system went offline. "Just imagine a store assistant writing down your credit card information because they're offline. How much would you trust that?"

An extra step causes the same problem. "If they have to get out a dusty payment terminal that they only use for offline, they get so much anxiety. Staff end up telling customers payments are down and it's cash only. But if they can just click and it still works the same, they're more likely to trust it."

Sierra hears the same uncertainty at checkouts. "The person checking out customers in store often has no idea how the device actually works. I usually hear 'try tapping again' or 'you might have to insert your card instead."

Sierra adds that front-line staff may never fully understand offline mode, and they shouldn't need to. The merchant's operations team should, and they should set the rules for it.

The trade-off to plan for

Offline mode does carry a risk, though. A payment taken offline isn't checked with the card issuer until the connection comes back. For instance, a debit card that only has $50 on it, and is being used to make a $300 purchase, would be declined online, but could still be accepted at the terminal offline.

That's why merchants set a limit for each offline transaction, at a level they're comfortable with. If a payment is declined when it's sent through, the merchant carries that loss, which is why the limit matters.

On Aevi's platform, offline payments wait on the terminal and are sent through, oldest first, once it's back online. If the acquirer can't be reached at that point, the payment joins a queue that retries each time the acquirer's connection comes back, up to a set number of attempts. Those retries deal with connection problems. They can't turn a decline into a payment.

Sierra saw the same balance at a cruise line she worked with before joining Aevi. Out at sea, most of its transactions were offline, so it required every passenger to have a card on file before boarding.

Where the provider comes in

For providers, the lesson is to make resilience part of the setup they offer rather than something each merchant has to arrange. At Aevi, offline mode comes as standard. Samantha calls it "table stakes." Aevi also runs automated tests that recreate peak-level transaction volumes, and once a payment method is certified, a provider can switch it on for its merchants in days.

That's the role of in-person payment orchestration. It sits across terminals, processors and payment methods, so a provider can add a backup route or a new way to pay without rebuilding its estate. When it's done well, Samantha says, "it feels like nothing went wrong."

Black Friday morning: before the stores open

By Friday morning, the leftovers are in the fridge and the stores are about to open for the busiest day of the year. For any provider reading this with a few weeks still to go, Samantha suggests starting with these checks: 

Check

What happens when a location goes offline?

How fast do transactions run on an average day?

Which card types and payment methods can each location accept?

Do staff know what to do if the terminal stops working?

Have the fallbacks been tested?

Why it matters

Find out whether terminals keep taking payments, and whether staff need to do anything differently.

If they're slow on a quiet Tuesday, they'll be slower on Black Friday.

Any gap means shoppers fumbling at the front of the line.

Staff need basic training, including how to capture a transaction if they can't operate the terminal.

A backup that has only been planned on paper may not work on the day.

The cooks who enjoy Thanksgiving…

…know their oven's limits before the guests arrive, and they've lined up a second one in case the first runs out of room.

Payment estates work the same way. Busy days will always put an estate under pressure. The providers who come through Black Friday calmly have planned for that pressure, with backups that switch on by themselves and limits their merchants have chosen in advance.

When the busiest day of the year arrives, their merchants keep trading and nobody at the register notices anything has gone wrong. That's an estate built for twelve.

Get our Aevi newsletter straight to your inbox!

Stay tuned for market insights, announcements and much more.

By completing this form, I accept Aevi's privacy policy.