CHAMPPAY

Home Who we work with

Merchants & operators

You are not short of payment apps. You are short of one that behaves.

If your terminal is charging when the queue is longest, if Friday’s takings clear on Monday, and if reconciliation is a Sunday-night job—those are the three frictions ChampPay is organised around.

Describe your operation See the product

What changes

Three problems, addressed directly.

No terminal to manage

Acceptance runs on the Android phone your staff already carry. Adding a till point at a busy hour becomes handing someone a phone, not sourcing a device.

Money that arrives today

Instant and same-day settlement is designed in, not sold as a premium tier. Your cash cycle should not be financing somebody else’s float.

Books that already match

Takings by day, by site and by staff member, reconciled against what actually landed — so the month-end is a review rather than an investigation.

Who this suits

Volume, and a reason to care about it.

The model is especially relevant where transaction counts are high enough that a few seconds at the counter and a few days in settlement genuinely matter.

Restaurants & QSR

Table turns, split bills, tips, and staff-level attribution on every transaction.

Retail & chains

Several sites reporting into one reconciliation, with per-branch visibility that does not require a phone call.

Events & hospitality

Temporary till points that stand up in minutes, on phones, and come down again the same night.

High-transaction SMEs

Businesses whose margin lives in volume and whose working capital is genuinely tight.

Straight answers

The questions merchants actually ask.

How do we explore fit?

Tell us how many sites you run, how customers pay, where settlement or reconciliation breaks down and what a better operating day would look like.

Does SoftPOS require a separate terminal?

No separate payment terminal is required; the acceptance surface is a compatible NFC Android handset.

How are commercial terms handled?

Pricing, service levels and settlement timing depend on the specific operating model and are handled in a private commercial process.

Who owns each regulated or operational role?

The relevant institutions, risk responsibilities, fund flow and support escalation should be identified in the written operating agreement for the use case.

The morning after

Yesterday, reconciled before you open.

The part of acceptance nobody demos is the bit that costs you a Sunday. Takings split by method, fees shown as a line rather than buried in a net figure, and a settlement time you can plan a stock order around.

If your current provider makes you export a spreadsheet to find out what you actually earned on Friday, the operating record is not doing enough work.

See how acceptance works

Interface and figures are explanatory illustrations, not a customer settlement record.

A useful first conversation

Bring the operating problem, not a generic wish list.

The fastest route to a useful answer is a concrete description of the counter, the cash cycle and the record your team has to reconcile.

Bring to the conversation
  • Where and how customers pay across your sites.
  • The cost, breakage or charging burden of terminal hardware.
  • How settlement timing affects stock, payroll or supplier payments.
  • The manual steps involved in reconciling sites and staff.
Keep out of public email
  • Customer names, transaction files or personal data.
  • Passwords, keys, account credentials or card information.
  • Unredacted contracts or regulated records before a secure channel is agreed.
  • Commercially sensitive information that first requires an NDA.

Tell us what happens between the tap and the ledger.

Start privately