3 ms·
This is kind of awkwardly phrased, especially because state machines or things that look like them are unavoidable in payments. You have a UI flow with state tr
by pjc50 2y ago
This is kind of awkwardly phrased, especially because state machines or things that look like them are unavoidable in payments. You have a UI flow with state transitions.
But it also has a very valid point about events. Or rather accounting records.
Because ultimately it's a payment system, and what you're doing is updating the accounting records across at least three parties: the user, the payment service, and your own records. You do so by sending messages, and it's a good idea to keep track of the content of those messages. At which point it starts to look a lot more like an event system.
In some cases recording may be a legal requirement. French NF525, for example, mandates securely recording every receipt.
https://www2.ikosoft.com/en-gb/all-knowledge-about-the-nf525-standard-for-cash-register-software/ https://www2.ikosoft.com/en-gb/all-knowledge-about-the-nf525...