← SumUp
Something new at SumUp

Guide offline payments when the signal drops at a market stall

You’re the software engineer. Your team is in the room. Printed Oct 15, 2026.

Offline checkout protects a sale while placing liability on the merchant.

A stalled payment risks immediate revenue, while an offline approval can create a later loss.

Who you’d be doing this for

“The queue was there, the signal disappeared, and I had to tell three people to come back later.”

Siti Pham · Market stall owner

Runs a small food stall and relies on a portable reader during peak trading hours.

What is at stake

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.

Why it isn’t already fixed

Every obvious fix costs something else. That’s the part you’d have to decide.

  • sale continuity vs. merchant liability
  • checkout speed vs. informed choice
  • Android simplicity vs. payment-state fidelity
  • pilot learning vs. payment-risk controls

Why SumUp

Portable card readers serve owner-operators whose sales happen where reliable connectivity is not guaranteed.

Written with these in mind

payment systems buildermobile-platform engineerreliability-minded product engineer

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.