3 ms·
We model a timestamp which functionally is "when does this activity go on the books"? We compute clearing both based on this "effective_at" and a "system time"
by ilganeli 3y ago
We model a timestamp which functionally is "when does this activity go on the books"? We compute clearing both based on this "effective_at" and a "system time" (there are some business functions with known periodicity and it makes for a useful debugging tool).
Long-clearing activity makes for some interesting business cases and long-standing float obviously can lead to some detection noise. For example, Brazil has uniquely long settlement times.
- dwightboyyy 3y agoI work with payments in a bank in Brazil and as I was reading the question I thought "interesting question, here we have a great 'delay' in clearances and very old and very complex government-embedded systems to deal with it, funny to see that you know about it too. btw, are you familiar with Pix? https://www.bcb.gov.br/en/financialstability/pix_en https://www.bcb.gov.br/en/financialstability/pix_en
- lmz 3y agoWell at least some people there should be familiar with it - https://docs.stripe.com/payments/pix https://docs.stripe.com/payments/pix