
Track overview
About this track
Decision practice for the bank's third engine: the flow of funds. Where lending earns a spread on money held and trading earns a spread on risk warehoused, payments earns a fraction of a percent on money moved — at enormous scale, and only on what survives a chain of costs the bank does not set. The discipline that runs through the course is that almost nothing an acquirer charges is an acquirer's to keep. A merchant pays a discount rate on every card it accepts; out of that rate the bank pays interchange to the cardholder's own bank — a fee the card networks set, driven entirely by which cards the merchant's customers happen to carry — plus scheme and processing fees, and it absorbs the disputes. What is left is the net take rate, and it is measured in hundredths of a percent. The opening move is therefore not what to charge but who should bear the part you cannot control: a flat rate keeps the merchant's card mix on the bank's books, interchange-plus hands it back, and the choice between them turns on one comparison — while a dispute rate above the networks' monitoring thresholds makes some volume unpriceable at any rate at all. From there the course follows a single transaction the rest of the way: over which rail to attempt it, where to set the screen so that fraud and false declines are both cheap, and when to settle it. The throughline: read what the bank actually keeps, not what flows across it — and put each risk in the hands best placed to carry it.
How each module works
Every module in this course runs the same three steps, from the first lesson to the debrief. The loop is what makes Decyde a place to practise, not just to read.
Step 1
Read
The lessons. Read the situation, the evidence and the shape of the trade-off before you commit.
Step 2
Size
The simulation. Put numbers on both sides of the trade-off, then make the call against the engine.
Step 3
Defend
The debrief and report. See what your call bought and why, so you can defend it or change it.
The same loop in every module, and a new decision each time. Judgment compounds.
Modules · In order
4 modules in this track
Each module is one decision: short readings, the decision itself, then a debrief and a replay in a shifted world.
01/04
The Interchange Call
Six merchant deals are on Keystone's acquiring desk, $4,400M of card volume, and Sales has circled the two fattest rates. But an acquirer is a toll on a road it does not own: out of every merchant discount rate it pays interchange to the cardholder's bank, set by the card networks and driven by the cards that merchant's customers carry, plus scheme and processing fees, and it eats the disputes. What is left is the net take rate. Put each merchant on a pricing rail: blended, where one flat rate leaves the interchange mix on your books; interchange-plus, where you pass the mix to the merchant and keep a 0.50% markup; or decline. The cards show volume, the headline rate, the card mix and a dispute gauge, never the interchange and never the net, because inferring the first is the decision. Every reflex in the room loses in a different direction. Then the card mix moves: customers shift to rewards cards and interchange rises. Who bleeds, and who does not? Blended was never a setting, it was a bet. This is the opener of Payments & Transaction Banking. Read the net, put the mix risk in the right hands, and decline what no price can cover.
12 lessons · 2 mini-sims · ~30 min
Begin module02/04
The Routing Call
Four million card payments a month, five authorisation rails, and a decline that isn't an ending: it falls to the next rail and is tried again. Each rail charges its fee on every attempt, win or lose, and approves its own share; and a quarter of the customers who see payment failed close the page rather than wait. So a retry costs a fee and some of your customers, and because later rails are only ever reached by what the earlier ones failed, the running order doesn't decide who goes first, it decides how much work happens at all. Set the order and the depth of the cascade while four meters run live: net contribution, approval rate, average cost per attempt, and a count of the people who walked away. None is labelled good or bad, because this is a decision the real dashboards don't flag. Your CFO asks about the four-cent rail, the cheapest line in the table. Your head of merchant operations wants the approval rate up. Neither executive is wrong: both instruments are calibrated per attempt and the decision is about order. Which table do you run, does the cheap rail belong in it, and what do the two dashboards say about your choice? Then the margin falls, and the question of which rail leads comes back. Order the attempts, not the price list.
12 lessons · 2 mini-sims · ~30 min
Begin module03/04
The Chargeback Line
The risk engine has sorted 921,913 card payments into twenty bands by how likely each is to be fraudulent, and every single band contains both real customers and fraud. There is no clean cut, which means the only question available is which error to make. Fraud operations wants the risky bands stopped; merchant operations points out that every decline is a customer who tried to buy something and was told no. They have argued for a month about where the line goes, and both of them are wrong in the same way: they have assumed there is one line. You set two gates, approve below the first, review between them, decline above the second, while four meters run live and nothing is flagged or colour-coded, because the two numbers this business actually reports both point the wrong way. The decision turns on a price nobody has written down: what a falsely declined customer really costs, the sale plus the business that never happens, most of it landing after the transaction is over, in a report nobody connects to the decline. Put that number in and every boundary becomes an exchange rate. Does the band everyone wants to block clear it? Declining everything feels responsible the whole way down; compare it with approving everything. What does a review queue add that a single line cannot? And the scheme's chargeback limit, the one externally-imposed number everyone manages to, has no term for a refused customer at all. Then the fraud ring learns where your screen is and moves: which of your gates should follow?
12 lessons · 2 mini-sims · ~30 min
Begin module04/04
The Float Call
Twelve million dollars a day crosses Keystone's acquiring book, sits on the bank's balance sheet overnight, and goes back out when the settlement policy says so. Three people want that policy changed and none of them is wrong about their own number. The CFO has the yield on settlement balances in her board pack now with her name against it. The Head of Risk has a coach operator who filed owing forty days of volume against the nine days the bank was holding. Merchant Operations has a settlement slide that reads worse than every competitor's and a phone that rings on Fridays from merchants who could not make payroll. They are arguing about one number, how long we hold the money, and the argument cannot be won, because that number is two decisions wearing one coat. How much lands the next day decides which merchants are still trading in six months; what day the rest lands decides how much of a failure you can absorb and how many merchants shop elsewhere over the figure in the contract. You set the advance and the tail on two different axes while five meters run live together, and a cohort strip shows whether each part of the book got the cash it needs by the next morning. Where does each handle belong, and what is the interest on the float worth against what it costs? None of it is visible in what the business reports: policies with the same average settlement days can be worth very different amounts, float income is a dial that does not see failure, and merchant churn counts who left while staying blind to who died. Then a platform partnership changes who the merchants are without changing a single price, and the whole shape has to be re-derived while every dial on the wall stays quiet. This is the capstone of Payments & Transaction Banking.
12 lessons · 2 mini-sims · ~30 min
Begin moduleAuthored on Decyde Practice loop curated for decision discipline
Vocabulary
What you'll engage
The decision skills you'll practice are paired with the underlying patterns you'll learn to recognize. Both vocabularies compound across the Banking Decisions domain.
Decision skills you'll practice
Credit segment readingBranch performance signalCustomer-tier trade-offsOperational risk weighingPolicy-vs-judgment balanceVolume-vs-quality calls
Patterns you'll see
Practice evidence recorded on Decyde
Every decision practiced builds your Decision Profile
Replays supported
Practice the same decision differently · iteration builds judgment
English
Additional languages on v1.3+ roadmap
What's next · One recommendation
The other Banking Decisions courses each practise a different kind of decision.
Begin practice →FAQ
Questions about this track
Common questions about Payments & Transaction Banking and how this track works.
Related · Other tracks

