What Happens When a Friend Never Confirms You Paid Them Back

Someone pays for the group's last dinner on the trip. A few days later, the person who owes them taps "I paid you back" in the app. And then... nothing. The receiver doesn't open Lumela for two weeks, doesn't see the request, doesn't tap approve. The payer is left wondering: did that actually register, or is it just sitting there forever?

This is a real failure mode in any app that lets one side report a repayment and waits for the other side to confirm it — and it's exactly the gap Lumela's repayment deadline closes.

How the "I paid you back" flow works#

When someone settles a debt in Lumela, they can report it themselves instead of waiting for the person they owe to log it. That report goes into a pending state. It isn't final yet — the receiver still needs to confirm it actually happened, the same way a bank transfer notification doesn't mean much until the other person checks their account.

That pending state used to be open-ended. If the receiver never opened the app, the request just sat there — not rejected, not approved, invisible to anyone trying to figure out whether the group's books were actually settled. For a payer who genuinely did pay, that's maddening: you did the right thing and the app can't tell anyone else.

The fix: a deadline that resolves it either way#

Every group now has a repayment-approval policy attached to it. By default, every group gets the same setting: auto-approval is on, with a 14-day window. A group admin can change the number of days (anywhere from 1 to 365) from the group's settings, or switch auto-approval off entirely if the group would rather every repayment stay manually confirmed, no matter how long that takes.

If the deadline passes with no response, the repayment is approved automatically — same outcome as if the receiver had tapped "confirmed" themselves, same update to the group's balances, just stamped so it's clear the approval came from the clock rather than a person.

Why the deadline is frozen, not a moving target#

The date attached to a pending repayment doesn't recalculate if the group's policy changes later. That's a deliberate choice, not an oversight: both people in the exchange are told a specific date when the repayment is reported, and a date that a group admin can quietly push later or pull earlier after the fact isn't really a date — it's a promise with an asterisk. Shortening the window later can't retroactively auto-approve something that was reported under a longer one, and lengthening it can't freeze something that was about to clear.

The one thing that does still apply live is the off switch. If an admin turns auto-approval off entirely, every repayment still waiting gets protected immediately — the deadline that already applies to it simply stops mattering. Turning it off is instant insurance; turning it on, or changing the number of days, only applies going forward.

What this isn't#

This isn't a way to force a payment through against someone's wishes. The receiver can reject a reported repayment at any point before the deadline — if the money genuinely never arrived, declining it is a real option, not just a formality waiting to be overridden by the clock. The deadline only resolves the specific case where nobody disputes anything and nobody does anything either: silence, not disagreement.

It's also narrow in scope on purpose. The job that enforces the deadline can only move a settlement from pending to approved, on its own already-stamped due date — it can't reject a repayment, reverse one, change an amount, or touch anything a person already decided. A separate reminder system exists to nudge someone toward actually confirming a repayment they owe before it ever reaches that point; the deadline is what happens if a nudge goes unanswered, not a substitute for sending one.

The practical effect#

For a payer, it means a repayment you genuinely made can't get stuck in limbo just because the other person is slow to open an app. For a receiver, it means the deadline is visible up front, not a silent trapdoor — you'll see the date the moment the repayment is reported, and you keep the ability to approve it properly, or reject it, the whole time the clock is running.

Group money apps live or die on whether "settled" actually means settled. A pending repayment that nobody ever resolves is worse than no repayment system at all, because it looks like progress while quietly going nowhere. Giving it a deadline — one that's visible, frozen, and reversible by a real decision right up until it fires — is what keeps "I paid you back" from becoming a message that disappears into the void.

Setting it for your own group#

If you're the one running a group's settings, the question worth asking isn't "should auto-approval be on" — it already is, for every group, from the moment it's created. The question is whether 14 days fits how your group actually behaves. A group of close friends who check the app constantly might shorten it, so a genuine dispute surfaces fast instead of sitting pending for two weeks. A group that only reconvenes for one trip a year, with people who go quiet between trips, might stretch it toward the 365-day ceiling instead, so nobody's real repayment gets auto-confirmed before they've even had a chance to notice it was reported. Either way, the setting lives in the same place as the rest of the group's admin controls, and it only takes effect on repayments reported after the change — nothing already pending gets caught by surprise.