Reliable transfer records are pulling against a retry path designed to preserve delivery.
Consumers need one clear status while the service must still retry uncertain external responses.
Who you’d be doing this for
“My client asked if I’d been paid twice because the app showed two updates.”
Saeed Chamoun · Freelance photographer
She relies on a personal account to receive client payments and move money between accounts.
What is at stake
Duplicate transfer-status notifications reached 4.8% after a deployment, despite correct money movement. You must weigh a fast idempotency change against preserving retries when an external response is uncertain.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- delivery retries vs. duplicate consumer messages
- fast containment vs. transition correctness
- shared filtering vs. service ownership
Why SumUp
UK transfer flows depend on backend services that connect internal systems to external payment networks.
Written with these in mind
Not your kind of problem? 24 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.