[photochemsyn]

> "We hope to publish guides about more complex use cases (lending, insurance, etc.) in the future."

That would be appreciated. It'd be nice to see the minimal complexity needed for something like a local credit union that managed customer savings and checking accounts, as well as home and car loans.

More ambitious would be a central banking app, in particular how does double-entry accounting work when a central bank (i.e. the Fed) is doing 'quantitative easing' and using their helicopter money to buy up Treasury bonds and mortgage-backed securities in order to keep major banks and government solvent? What's the private bank's balance sheet look like when they use the central bank money for stock buy-backs instead of for increasing commercial lending?

For example, the Fed says it's unloading the mortgage-backed securities it bought up in 2008-2009. That's got to be some convoluted accounting:

https://www.marketplace.org/2022/06/02/why-the-federal-reser...

[kojim]

That's a cool idea. Any other deep-dive guides on fintech/payments that would be helpful for readers here? We're always looking for new topics to write about.

[gtolle]

The book Central Banking 101, by Joseph Wang, is a good deep-dive on how the accounting works on the central-banking side when money is created, etc.

[m33k44]

> Any other deep-dive guides on fintech/payments that would be helpful for readers here?

How online payments actually work behind the scenes, complete flow from sender to receiver. That deep-dive would be really useful.

[kojim]

Do you mean for card payments, like the card network and authorization flow? I found this article really good from the systems design side although you might have to be a subscriber: https://newsletter.pragmaticengineer.com/p/payments-system

[m33k44]

> Do you mean for card payments, like the card network and authorization flow?

Yes.