Timeline for Handling coupon refunds and partial refunds when coupon budgets are enforced via Redis counters
Current License: CC BY-SA 4.0
Post Revisions
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 21, 2025 at 19:11 | history | edited | tusharRawat | CC BY-SA 4.0 |
added 74 characters in body
|
| Dec 21, 2025 at 18:43 | history | edited | tusharRawat | CC BY-SA 4.0 |
updated the rps term meaning explicity
|
| Dec 21, 2025 at 17:47 | answer | added | Ewan | timeline score: 1 | |
| Dec 21, 2025 at 16:00 | history | edited | Greg Burghardt | CC BY-SA 4.0 |
markdown numbered list
|
| Dec 21, 2025 at 15:09 | comment | added | tusharRawat | We can't do transaction update by doing increment on budget(and user offer) + log for refunds. Because background worker is also running which is rolling back the logs to counter so budget might get inc twice here. | |
| Dec 21, 2025 at 15:06 | review | Close votes | |||
| Dec 29, 2025 at 3:09 | |||||
| Dec 21, 2025 at 14:41 | comment | added | tusharRawat | @Basilevs What approach should we take for refunds to inc counter back. Same as we are doing in redeem flow? | |
| Dec 21, 2025 at 13:12 | comment | added | Basilevs | Correctness and latency seem to be irrelevant for refunds. One user can not predict or rely on refunds done by another, so there is no way for them to notice an invalid rejection of coupon, if some fedunds are "in progress". | |
| Dec 21, 2025 at 11:38 | history | asked | tusharRawat | CC BY-SA 4.0 |