A mandatory technical change can turn a reliable device into a merchant continuity problem.
Teams often weigh broad protection, limited replacement capacity, and commitments that cannot be easily reversed.
Who you’d be doing this for
“I can’t turn up on Saturday and find out the thing I use for every sale won’t work.”
Gamze Zayed · Owner of a market-stall bakery
She uses an older reader as her primary way to take card payments at weekend markets.
What is at stake
Some older readers are failing validation ahead of the certificate deadline, and more merchants are hit each week. You weigh retiring the models, paying for replacements, or extending compatibility, and none of it can be undone.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- network deadline vs. merchant continuity
- standardized retirement vs. targeted protection
- subsidy exposure vs. payment-volume preservation
- automated impact lists vs. verified outreach
Why SumUp
At SumUp, payment continuity can matter most for merchants least able to absorb a sudden device change.
Written with these in mind
Not your kind of problem? 9 more at SumUp, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.