The ledger was right
A team sale splits one commission between two people. The split was recorded correctly everywhere a person could look, and the code that sent the money would have paid the wrong one.
3 min readGlitz · Team stage
On the marketplace, creators can work in teams. A member makes a sale and the commission splits: part to the member, part to the leader who brought them in. That split is the leader's whole reason to run a team, so the platform guards it. A member who shares their own solo link to dodge the leader's cut has the sale routed through the team anyway, earliest membership winning, with the split read from the team's records rather than anything the app sends.
Two functions, one row
A sale writes a ledger row. It records who sold, which team, the split rate, the member's amount and the leader's amount, each computed once and stored. Thirty days later a scheduled job releases the row and sends two transfers. The function that writes the row and the function that sends the money are different code, and they were written at different times. The split arrived on 18 February 2026. The sender arrived on 29 March, and it was correct that day. The rerouting of solo links arrived on 21 April, and it created a kind of row the sender had never been asked to read.
What the sender read
The sender found the leader's payee from the row's seller field. On a team link the leader created, the seller is the leader, so the money went to the right place. On a solo link the team check had rerouted, the seller is the member, because it was the member's own link. The row also carried a leader field, filled in correctly at sale time. The sender never read it. Both transfers would have gone to the member: their own share, and the leader's.
Everything a person could look at was right. The ledger showed the split. The member's running total showed their share and only their share. The leader got a notification for money that was never going to arrive. The only place the mistake lived was the transfer itself, the one record nobody reads until someone asks where their money went.
Found by reading
Nobody reported it. I found it on 2 October 2026, reading the source to write about the team check, and the essay stopped there. The honest version would have described a live bug, and the flattering version would have claimed a defence that did not reach the money. Production held no team sales at all, so nothing had been paid wrongly and nothing needed correcting. The fix merged on 21 October. The leader's share is paid to the leader field. The release notification goes to the same person. The same rerouting now runs for orders that come in through connected stores. A missing split falls back to the team's own default before the platform's. The scheduled jobs that send the money were redeployed on 31 October.
Fixed is not impossible
The fix is a corrected line, not a structure that rules the mistake out. The writer and the sender are still two code paths reading one row, and the notification repeats the payee expression rather than sharing it. If a rerouted row were ever written with an empty leader field, the fallback would pay the member again. What guards it today is a battle test that seeds team sales, releases them, and checks which account received how much. Its six team cases all passed on the last recorded run, in late October, and three of them had failed before the fix. It runs by hand against throwaway records, not on every change.
The version that makes it impossible is small. One function decides who is owed what from a row, and both the transfer and the notification call it. Before any transfer leaves, an assertion checks that the two amounts add up to the commission and that the leader's transfer is going to the leader. That is a morning's work. It is the difference between a bug that was fixed and a kind of bug that cannot come back.
Why it belongs on this page
The writer, the sender and the rerouting were written by the same person, weeks apart. That is the only reason the disagreement could be found from a chair. Whoever was reading the team check also knew, without asking anyone, which field the sender read. When those functions belong to two people, the ledger is right, the dashboard is right, and the first sign is a leader asking where their money went.