Ever wondered how Venmo, Coinbase, and other fintech apps work behind the scenes? Rehive is designed to be flexible and easy to build on top of and/or integrate any existing payment system, service provider, and store of value.

In most cases when you’re creating a fintech app it is not always possible to build everything directly on the payment network or core banking system. These systems weren’t designed to easily build on top off. It is often necessary to create a middleware layer to abstract existing payment networks, banking products, and/or niche service providers e.g. KYC/AML.

Businesses can either build a many-to-one middleware layer on top of an existing system or map accounts one-to-one. Many-to-one architecture means that the sum of all the user balances in the system is mapped back to a treasury or custodian account, e.g. like a bank. Whereas a one-to-one architecture will directly map all balances and transactions on both systems. It is not always necessary to create a middle layer for a one-to-one architecture, but it limits customizability and speed to innovate while keeping management processes clean. Read more about cash-in and cash-out here.

Venmo, Coinbase, Paypal, Robinhood, Acorns, etc. had to build their own ledger and user management system to support their niche features like sending to an email address, tracking investments, recording savings, etc. The diagram below highlights how Rehive slots in on top of the underlying fintech stack, whether banking, crypto, or financial service providers.

Did this answer your question?