Thats wild to me. Payment data is like, the most relational. You need to learn 20 different data models and all their many interconnected relationships just to implement a custom API integration. Maybe thats why it sometimes feels like pulling teeth to get the data you want out of a particular Stripe flow.
I used a document db for our side of the billing integration and I really, really wish I hadn't.
I am trying to be constructive here: "Relational" in RDBMS does not refer to what you are implying that it refers to. It's a common misconception honestly.
Anyway many interconnected relationships become much simpler to model when you have the richness and flexibility of the document data model.
