Haute Lumière

Commerce · III.09 · MMXXVI · daylight

La Bourse  /  Volume III  /  Nº III.09  /  Workbook — the Gainshare employee

WORKBOOK — THE LUMINOUS GAINSHARE EMPLOYEE

Chapter III.09 · Digital Settlement Without Extraction

How the mechanism reads from inside. What to measure, what to claim, how the ledger works, what to ask for.

---

WHY THIS CHAPTER IS YOUR BEST GAINSHARE CLAIM

Most gainshare claims are hard because the saving is contested. Someone argues the market moved, or the mix changed, or the improvement would have happened anyway. You spend three months proving causation and the pool arrives shrunken and late.

Payment acceptance is different, and the difference is structural. The saving is a rate change on a measured volume. Both halves are on documents that already exist — your merchant statement and your revenue ledger — and neither is a forecast. There is no counterfactual to argue about, because the old rate and the new rate are both printed, and the volume is the volume.

   saving  =  ( old rate  −  new rate )  ×  migrated volume

Three inputs, all documented, none estimated. That is the cleanest claim structure in this entire volume, and it is why this chapter is worth taking first if you have a choice of where to point your effort.

Here is what it is worth at a realistic scale. A firm with $240.0 million of revenue, 70 per cent of it card-borne, pays $2,637,600 a year in acceptance. Migrate 30 per cent of that volume from 1.57 per cent to 0.22 per cent and the verified saving is $680,400 in year one. At a 20 per cent employee share that is a pool of $136,080, or $3,024.00 each across a claiming unit of 45 people. At full migration: $2,268,000 saved, a pool of $453,600, and $10,080.00 each.

---

PART ONE — DISCOVERY

Days 1–30: find where the gain actually is

1.1 — Get the statement, not the summary. Ask for twelve months of merchant statements. Not the finance summary — the statements. You are looking for three components, and most organisations have never separated them:

• Interchange, paid to the cardholder's bank, set by the network.
• Scheme fees, paid to the network.
• Acquirer margin, the only piece anyone has ever negotiated.

If nobody can produce the decomposition, that is your first claim. Producing it is a measurable piece of work with a documented result, and it is the input every subsequent claim depends on. Claim it as an enabling contribution and say so plainly in the ledger.

1.2 — Find the volume that could move tomorrow. Not all volume is migratable. Sort it:

• Trade and wholesale customers — invoice-based, relationship-based, finance-literate. These move first and they move easily.
• Repeat consumer customers with an account — second.
• One-off consumer transactions at the point of sale — hardest, and the place where acceptance, not price, is the binding constraint.

Write the three volumes down. Your claim will live almost entirely in the first bucket in year one, and a claim that promises the third bucket in year one will be marked down when it under-delivers.

1.3 — Find who is already doing it unrewarded. Somebody in your organisation already asks large trade customers to pay by bank transfer. They do it because it is easier for them, not because anyone measured it. Find them. Their existing behaviour is the baseline, and they should be named in your claim as a contributor. A gainshare claim that harvests somebody else's unrewarded work and does not name them is the fastest way to make the next one impossible.

1.4 — Establish the baseline before you touch anything. The migration rate and the blended acceptance rate, both dated and both agreed in writing with finance, before the first customer moves. An unagreed baseline is not a baseline; it is a future dispute, and in a gainshare it is a future dispute about your money.

---

PART TWO — THE ARITHMETIC

Days 31–45: compute what you are owed

2.1 — The claim, in the form the ledger takes it.

  verified saving  =  ( rate_old − rate_new ) × migrated volume
  employee pool    =  verified saving × scheme share
  per person       =  employee pool / claiming unit

Worked, at the scale above: ( 0.0157 − 0.0022 ) × $168.0 million × 0.30 = $680,400. Pool at 20 per cent: $136,080. Across 45 people: $3,024.00.

Do the same arithmetic at your own numbers before you talk to anybody. Walk in with the figure, not with the request to compute the figure.

2.2 — Decide what counts as migrated, and write it down first. This is where gainshare claims are actually lost. Define, in advance and in writing:

• Migration is measured on value, not transaction count. A rate saving is a value saving, and counting transactions will understate you on exactly the large baskets where the saving concentrates — on a representative 1.8 per cent rate, a €4,000 basket carries €72.00 against €0.72 on a €40 basket.
• The rate used is the blended all-in rate including scheme fees, not the headline interchange.
• Volume that migrates and then returns is netted in the month it returns.

2.3 — Net off what the migration costs, honestly. A claim that ignores the offsetting costs gets discounted by someone else, at a number they choose. Do it yourself, at a number you choose:

• The acceptance levy, if your organisation joins a merchant mutual: 0.10 per cent of migrated volume. On the decision inequality this still leaves 2.2 % − 0.22 % − 0.10 % = 1.88 % of migrated volume retained, and a coverage ratio of 19.8 times between fees avoided and levy paid.
• The dispute process. Instant payments are irrevocable and there is no chargeback. Something has to fund the equivalent. Name it.
• Any discount you offered the customer to move them. If you shared half the saving, claim on the half you kept.

2.4 — Then state the ratio that makes the claim large. Not the saving. The saving as a share of net profit. At the scale above, the acceptance fee is 1.10 per cent of revenue and 18.32 per cent of net profit — same fee, and only the second number gets an agenda slot. Your year-one saving is 4.72 per cent of net profit, rising to 15.75 per cent at full migration.

2.5 — And know the small-business version. If your claiming unit is a single shop rather than a division, the arithmetic is the same and the proportions are larger. On R$1,000,000 of card-borne revenue at a 4.0 per cent margin, moving from 2.2 per cent to 0.22 per cent saves R$19,800 — 49.5 per cent of net profit — and a 20 per cent share of that is R$3,960.00 to the people who did it. At a 3 per cent margin the saving is 66.0 per cent of net profit, and below a 1.98 per cent margin the payment fee exceeds the whole profit of the business.

---

PART THREE — DESIGN

Days 46–70: make the uncounted countable

3.1 — Build the migration dashboard before you need it. Weekly, four lines, on one screen:

1. Migrated value this week, and cumulative.
2. Blended acceptance rate, this week and at baseline.
3. Saving to date, computed from the two above.
4. Pool to date at the scheme share.

The fourth line is the one that changes behaviour, and it is the one most schemes leave out. People do not work harder for a saving. They work harder for a number with their name near it.

3.2 — Write the claim as a standing mechanism, not an event. A one-off claim pays once. A mechanism pays every period and does not have to be re-argued. Propose that acceptance saving becomes a standing gainshare line with a defined rate, a defined share and a defined review, rather than a special claim this year. The organisation will usually prefer this too, because a standing line is budgetable and a surprise claim is not.

3.3 — Ask for the three things that make it durable. When you negotiate, ask for these in this order:

1. The agreed baseline, signed. Without it nothing else matters.
2. The share, stated as a percentage rather than a discretionary pool. A discretionary pool is not a gainshare; it is a bonus with a story.
3. The claiming unit, named. Who is in it, and why. Include the people from Exercise 1.3 who were doing it before anyone measured.

3.4 — What to do when somebody says the saving is not real. They will say one of three things, and each has an answer already on paper:

• "The rate would have fallen anyway." Brazilian credit card merchant discount fell from 2.8 to 2.2 per cent and debit from 1.6 to 1.1 per cent between 2014 and 2021, and much of that predates Pix. Concede it. Then point out that your claim is on migration between rails, not on the movement of either rate, and that the migrated volume is documented.
• "Customers will not move." Brazil went from launch to 54.7 per cent of retail transactions in five years; India to 83.4 per cent of ecosystem volume in nine. They will move if somebody is paid to move them. That somebody is you, which is the whole argument for the claim.
• "The saving belongs to finance, not to you." The saving belongs to whoever produced the migration. That is why you instrumented it weekly from day one.

---

PART FOUR — DESTINY AND DELIGHT

Days 71–90: make it hold

4.1 — Get the migration rate into the standing pack. One line, monthly, beside the acceptance cost as a share of net profit. A number in the standing pack survives a change of sponsor; a number in a slide deck does not.

4.2 — Recruit the second owner, and give them the first result. One person running a migration is a hobby. Two is a practice. Recruit them by handing them the credit for the first verified quarter, which costs you nothing this year and secures the claim for every year after.

4.3 — Watch the sunset. If your organisation joins an acceptance mutual, the levy has a five-year sunset written into the constituting document — five years of levy at R$5.0 million against R$99.0 million of fees avoided on a pooled R$1.00 billion. Diary the sunset date. When a levy outlives its purpose it becomes exactly the thing it was built to replace, and the people defending it will be the people it employs. Being the person who remembers the date is itself a contribution and should be claimed as one.

4.4 — Know what happened in India, because it will happen to you. Zero merchant discount rate ran from January 2020. The state paid 1,389 crore rupees, then 2,210, then 3,631, then an outlay of 1,500 — 8,730 crore, about $992 million — against an industry-estimated running cost of 20,000 crore a year, so even the largest year covered 18.2 per cent of it. On 15 October 2026 a 0.4 per cent fee returned on merchant payments above ₹2,000, capped at ₹300. Free was a phase, not a property. Build your claim on the migration, which is permanent, and not on the rate being zero, which was always temporary.

4.5 — The delight, from inside. The good moment is not the pool landing. It is the meeting where somebody who does not report to you quotes your migration number back at you, in an argument about something else entirely, and does not attribute it. That is the moment a measurement becomes infrastructure. It has stopped being yours, which is exactly what you wanted, and it is also the moment the claim becomes a standing line instead of an annual negotiation.

---

KNOW YOUR SCHEME — A CHECKLIST

Before you claim anything, be able to answer all nine.

---

THE CONVERSATION, SCRIPTED

You: I have the twelve-month decomposition. Acceptance is costing us $2,637,600 a year, which is 1.10 per cent of revenue and 18.32 per cent of net profit.

Them: That is just the cost of doing business.

You: It is a rate on a volume, and the rate is a choice. Thirty per cent of our card-borne volume is trade customers who would move to the instant rail this quarter if we asked them. That is $680,400 a year — 4.72 per cent of net profit. At full migration it is $2,268,000, or 15.75 per cent.

Them: And what do you want?

You: The baseline signed before we move anybody, the standard scheme share on verified saving, and the claiming unit to include the two people in trade sales who have been doing this for three years without anyone counting it. I have netted off the levy and the dispute cost already — the numbers I have given you are after those.

Them: Send me the page.

You: It is one page. The baseline is on the back so you can sign it today.

---

APPRECIATIVE QUESTIONS FOR YOUR TEAM

1. Who here has already moved a customer onto a cheaper payment method, and what did they actually say to make it work?
2. What is the largest single transaction we take by card, and what would moving just that one customer be worth?
3. If the pool arrived at $3,024.00 each this year, what would we want to change about how the next one is measured?
4. What would make the migration dashboard the first thing this team looks at on a Monday rather than the last?
5. Who outside this team would notice first if our migration stalled — and how do we make sure they tell us?