Tillora.
Follow the idea
About Tillora

Payments are technical.
Paying should feel human.

Tillora is an early point-of-sale concept asking how a checkout might become easier to understand for the people on both sides of the counter.

Follow the thinking An idea in development
THE STARTING POINTA better checkout starts with the people using it.

Can a point of sale feel more open and stay familiar?

A merchant needs a sale that is easy to run, a clear payment status, and records that make sense after the rush. A customer needs to check the order, understand the choice, and know when the payment is complete.

Tillora is exploring whether Web3 could support a digital point of sale around those everyday needs. The concept is at an early stage: this site does not document a product architecture or payment model, and it starts with defining the experience each side needs.

Read the product concept
What guides the work

Principles before promises

These are standards for evaluating the concept as it takes shape.

01 / MAKE IT LEGIBLE

Explain the next step.

Show the amount, the choice, and the result in everyday language before asking someone to act.

02 / DESIGN FOR BOTH SIDES

Respect the work at the counter.

Consider merchant operations and customer understanding together, including when the smooth path breaks.

03 / EARN EVERY CHOICE

Let the need guide the technology.

Choose infrastructure only when it addresses a real need and its tradeoffs can be explained plainly.

What comes before a product decision

Questions worth answering next

A responsible path from concept to product would first need evidence about the checkout, then clear criteria for judging the technology behind it.

01 OPEN QUESTION

Map the merchant’s day

Understand the sale from basket to end-of-day records, including interruptions, mistakes, returns, and the work around a payment.

02 OPEN QUESTION

Check customer understanding

Find out whether the amount, choice, confirmation, and receipt are clear without asking customers to learn new technical language.

03 OPEN QUESTION

Compare the system choices

Assess candidate approaches against privacy, reliability, cost, payment recovery, and the actual needs of the checkout.

04 OPEN QUESTION

Explain each decision

Share what was chosen, what tradeoff it brings, and what remains unresolved before presenting an idea as a capability.

Keep exploring

Follow the idea as it develops

Our concept notes explain the questions and tradeoffs behind the work.

Explore all updates