Good checkout design makes the next action clear. This four-part flow is a way to frame Tillora's early product exploration, from preparing an order to keeping a useful record. It describes a design direction, not a released payment service or a finalized technical flow.
01 — Build the basket
The merchant prepares the order using a familiar point-of-sale interaction. The customer should be able to see what is included before the total is confirmed, and the merchant should have a clear chance to review the items. The interface can reduce small errors by keeping names and quantities easy to scan.
A concept also needs to consider ordinary edits. Removing an item or correcting a quantity should not leave either person unsure about which total is current.
02 — Review the total
Both sides need a shared understanding of the amount due before a payment action begins. A review moment can bring the items, total, and any relevant context together in one place. It gives the customer a chance to check the purchase and the merchant a chance to catch a mistake.
The amount should stay visually clear, and supporting details should be available without competing with it. That is a usability principle, independent of what payment options a future product might offer.
03 — Explain the payment step
A future flow would need to make the selected payment route and the meaning of any confirmation clear. The person paying should know what they are authorizing, while the merchant should be able to tell whether the checkout needs attention or has reached an expected state.
The exact payment options and technical mechanics remain open product decisions. A useful design can still explore how to communicate a pause, a retry, or a request for another action without suggesting that an outcome has been confirmed when it has not.
04 — Keep a record
The final moment is a useful receipt: an understandable account of the purchase that connects back to the checkout. It should help a customer remember what happened and help a merchant find the corresponding order during routine follow-up.
What a record contains and how it is accessed depend on decisions that Tillora has not announced. The design goal is narrower and more grounded: a person should be able to recognize the transaction without interpreting raw technical data.