SumUp
Each of these is a real decision SumUp is working through, written so you can make the call yourself — incomplete information, someone who pushes back, no answer key.
SumUp is a fintech company, founded in 2012, that provides payment acceptance hardware and software, card readers, point-of-sale systems, inventory management, business analytics, and adjacent financial tools for micro and small businesses in retail, hospitality, and services, monetizing through transaction fees and software subscriptions. SumUp handles millions of card transactions every day. Its core business includes lending, payments, and merchant banking products, and it offers a free digital account. Its Point of Sale app includes ordering experiences such as the shopping bag, checkout, catalog browsing, open orders, table management and printer integrations. SumUp is building its own payment acquiring capability in Europe and is launching a financing product in Brazil for the roughly 50 million registered and informal sole traders who currently can't access affordable credit. SumUp Limited is a Central Bank of Ireland regulated electronic money institution. Backend engineering teams build on Golang, AWS, Kafka, PostgreSQL, Redis, and Kubernetes, with Prometheus, Grafana, and Honeycomb for observability.
Your first one is free. No card.
25 live right now.
The rest
Win bookkeeper referrals before merchants split cash across more tools
Merchants are managing payment settlements and supplier payments in separate places, while bookkeepers remain outside the account conversation. You must weigh fast partner recruitment against a referral motion advisers can confidently use with clients.
Close the association deal without promising access to unsettled funds
A 180-member association has paused its referral agreement over conflicting answers about when card takings can be used. You must weigh member conversion against commitments that card and transfer operations can stand behind.
Place the account next to Edenred while owners decide on settlements
Qualified payment and POS prospects are declining the account because they cannot place it beside Edenred in their daily routine. You have to weigh a faster close against a recommendation the owner will still use after setup.
Trace Bluetooth failures while café queues keep moving
Bluetooth payment failures are interrupting checkout even when the phone still appears connected. You must weigh faster diagnosis against the evidence threshold engineers need before changing a payment flow.
Guide offline payments when the signal drops at a market stall
Merchants abandon sales or take offline payments without understanding the later risk. You must weigh a faster checkout against a choice that remains clear and auditable.
Trace duplicate tickets while dinner service keeps moving
Duplicate kitchen tickets appear after orders move between devices, even when payment appears once. You must decide which evidence AI can assemble and where engineers must verify the cause.
Resume open orders when a tablet drops out
Interrupted open orders can be recreated, charged twice, or sent twice to the kitchen. You must weigh a fast recovery flow against certainty about shared order state.
Cut triage of SEPA delays to 20 minutes while engineers verify evidence
Delayed SEPA cases take a median 42 minutes to reach a verified hypothesis. You must weigh faster incident context against the risk of trusting an incomplete payment timeline.
Show merchants when card takings settle without promising funds early
Merchants delay supplier payments because accepted card takings are not yet visible as a usable outlook. You must weigh planning clarity against the risk of showing money before settlement is dependable.
Recover UK transfers without creating a second ledger record
Some merchants see a UK transfer affect their balance twice even though the supplier received one payment. You must weigh fast balance recovery against the risk of making the ledger harder to reconcile.
Restore transfer updates before suppliers question completed payments
Accepted SEPA transfers are reaching recipients while some merchants still see them as pending. You must weigh a fast status repair against the risk of replaying money-movement events.
Introduce a balance buffer without confusing everyday transfers
Spending signals show recurring low balances before expected outgoings among people already using Spaces. You must weigh a useful reserve against rules that make consumers unsure what money they can spend.
Hold or release the UK transfer backlog without duplicating any payment
A network disruption left UK transfer instructions in uncertain states, and some may already have moved. You must weigh faster access to money against an irreversible risk of duplicate execution.
Contain duplicate alerts while UK transfers keep retrying
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.
Decide when readers can go live before delivery
Turning readers on before delivery is confirmed reduces failures on day one, but a diverted terminal could take payments before ownership is confirmed. You set the evidence bar and escalation rules before this is hard to unwind.
Decide how to move payments before the exit date
The contract for hosting ends in 10 weeks, and no test recreates real device connectivity at peak trading. You have to weigh continuity against schedule certainty, then evidence a cutover you cannot undo.
Decide what happens to 46,000 legacy readers
Those terminals cannot display transaction information in the accessible form the regulator requires by a fixed date. You have to choose between replacement, restriction, or market exit, and defend the choice.
Decide where the last batteries should go
The supplier stops making a legacy battery part after the next run, and stock will not cover both new merchants and warranty swaps. You get 10 business days to order, and two sites show a 9% stock gap.
Settle the wholesaler deal before the window closes
The wholesaler wants a three-year commitment and one launch date across 180 branches, and its exclusivity window closes in 14 days. You have to weigh volume against terms you cannot cheaply unwind.
Check who is really ready before the cutover
Three weeks out, 39% of the cohort is flagged not ready, and automated summaries conflict with source records on 14% of accounts. You have to decide who moves and who waits, with peak trading close and the date fixed.
Cut off terminal access when staff leave
Tokens stay valid long after an employee is dropped from the roster, and a review tied several delayed removals to live sessions. You weigh strict expiry against blocking a legitimate checkout.
Move merchants to certified receipts before the deadline
Nearly a third of affected merchants are still outside the certified flows, and the account mappings behind the migration are machine-generated. You have to decide who moves and when, knowing it cannot be cheaply undone.
Choose how to fix payments on older readers
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.
Decide where to draw the decline line
The card network now makes terminals reject a new class of compromised credentials, and the proposed rules disagree on how many good sales get declined. You pick the boundary and prove it, because the change cannot be undone.