Skip to main content
NewChargeback Protection + Fee Intelligence for high-volume merchants. Get a savings analysis and a review of your dispute handling.See how it works
Details

Chargeback Protection + Fee Optimization

See how it works: high-volume merchants get automated dispute evidence, interchange optimization, and real-time savings visibility.

See how it works
Fee Check

Payment case studies: worked scenarios by business type

Every case study here is a worked scenario rather than a customer reference. Read one the way you would read a worked example: the value is in the order of operations.

Browse by topic

How to read a case study here

  • Illustrative, and labelled that way

    Each study carries an illustrative-scenario notice on the article itself. The business, the staff and the figures are constructed to show how a deployment of that kind behaves — nothing here is attributed to a real business, and the figures exist to make the arithmetic legible rather than to report a result anyone achieved. What is not constructed is the workflow: the sequence of steps is the one a business of that shape actually goes through, in the order it goes through it. For figures from your own operation, a statement review produces an estimate against your actual card mix.

  • Written for the person running the shift

    The detail sits where an operator feels it — the tip prompt appearing before the guest authorizes, a return matched to the original transaction, a deposit taken before parts are ordered. Buying criteria appear only where they change what happens on the floor, which is why none of these pages opens with a feature list.

  • One shape of business per study

    Each study takes a business of a recognisable shape — a three-site restaurant group, a retailer selling in a store and online, a contractor whose crews collect in the field — and follows where the card is presented, who is standing there when it happens, and what somebody has to reconcile the next morning. So the three shelves are less industries than three different places a card gets presented: at a table, at a counter that also has a website behind it, and in somebody else’s building. Plenty of operations sit in two of them at once, and reading two studies together is usually more useful than reading one twice.

  • The common thread is reconciliation

    All three end in the same place: the report that has to agree with the deposit. Deposit-level reporting, per-location breakdowns and interchange-plus pricing are what make that comparison possible, which is why the same section recurs in every study rather than being written once and linked.

Where to start

  • Illustrative scenario: Summit HVAC field deposits

    Start here if jobs get invoiced and then chased. It covers the deposit taken at booking, collection on site, pay-by-link for the balance, and how a day in the field reaches the office system.

  • Illustrative scenario: Riverbend Supply omnichannel payments

    Start here if the store and the website are still two sets of numbers. It covers one catalogue, returns taken in either channel, and a month-end close that has to combine both.

  • Illustrative scenario: Trattoria North tableside payments

    Start here if service itself is the constraint. It follows a three-site group from the walk to the till through tip handling, split cheques, and a shift close that has to agree across rooms.

Questions about these scenarios

I run more than one format. Which of these applies?

Read the shelf that matches where most of your transactions happen, then the one that matches the awkward channel. A group running a dining room and a retail counter has one payment problem rather than two, and per-location reporting and permissions under a single merchant account are what keep it that way at month end.

Do the workflows described require RapidCents POS software?

Some do, some do not. Tableside ordering, split bills and item-level returns come from Restaurant POS and Retail POS. Collecting in the field needs none of that: Tap to Pay on a compatible phone, a mobile terminal or a payment link is enough, with no point-of-sale software involved at all.

Can the products used in one scenario run on a single account?

Yes. Terminals, hosted checkout, payment links, the virtual terminal and invoicing sit on the same merchant account, which is why one dashboard covers transactions, deposits, refunds and disputes across every channel instead of one dashboard per channel.

How do I get figures for my own business instead of these?

Upload a recent statement for a review. It reads your actual card mix, volume and existing markup and returns an estimate — an estimate, not a quote, because the rate on a live account depends on underwriting and on the card mix that turns up next month.

None of these three shapes matches my business. Where else should I look?

The industry pages describe acceptance trade by trade rather than by scenario, and the solutions pages start from a job to be done — lowering processing costs, replacing terminals, selling online, automating billing — instead of from a business type.

Restaurants & hospitality

Hospitality is where the payment happens away from the till: at the table, on a patio, at a counter with a queue behind it. This shelf follows a full-service group through tableside acceptance, the tip prompt, split and transferred bills, and what a shift close looks like when three rooms report into one merchant account.

Retail & e-commerce

Retail breaks when the store and the website become two businesses that happen to share a name. This shelf follows a retailer running both, through the parts that only hurt once you sell in two places: one catalogue, returns taken in store against an online order, and a close that has to reconcile deposits from both channels.

Professional & field services

Field services get paid in the least convenient place available: a driveway, a mechanical room, a customer’s kitchen at the end of a long job. This shelf follows a contractor collecting a deposit before ordering parts, sending a payment link for the balance, and getting the day’s collection into the office system without a shoebox of paper slips.