Rehive is designed to make it easy to get started with an end-to-end solution, while we also offer the flexibility for you to go in your own direction.

Refer to the developer documentation to get started with a custom extension.

At the core is the Rehive Platform, which consists of the minimum set of features for building a financial/banking application: Authentication, Users, and Ledger. We also offer a couple of off-the-shelve Rehive Extensions: Notifications, Conversions, Mass Send, Invoicing, Business, Stellar, Wyre, etc. Rehive Platform and Rehive Extensions are backend API services.

The idea is that you can easily build custom extensions, whether integrations or value-added features, on top of the Rehive Platform and Extensions APIs.

Common integrations

  • Cash-in/out integration - Depending on the region and use case, this can cover a range of payment methods: cards, ACH, cash, vouchers, etc.

  • KYC integrations - While Rehive captures user information and manages various business logic such as tiers, limits, fees, etc, you still need to verify information through a vendor that can provide automation and specialized capabilities.

  • Forex - Rehive Conversions provides brokerage-like services to manage rates, quotes, and conversions, but we do not provide liquidity management and actual trading. You have to integrate with your forex/exchange partner to take care of the underlying money movement.

  • Support/CRM - It is likely that you are using a specialized CRM service to send out important messages, help with support, etc. Typically, you might want to add new registrations to your CRM automatically.

Value-added features

Rehive offers a couple of featured value-added extensions such as Notifications, Rewards, Mass Send, Conversions, etc. It is very likely that you are looking to introduce a feature to differentiate your service in one way or another.

For example, perhaps you are looking to provide shared accounts, automated donations, budget management, portfolio tracking, real-time payouts to gig workers, locked accounts, etc.

Typically these features can be seamlessly developed on the Rehive Platform and Extension APIs.

Important notes

  • Building an Extension typically requires admin-level permissions. Make sure you are calling the Rehive Admin API and not the Rehive User API. The difference is that the Rehive Admin API can perform actions on any user in the system.

  • Make sure to use idempotency requests to avoid accidental duplicate requests.

  • We do support webhooks on any event in the Rehive system. In many cases, custom extensions need to await an update or a user or transaction status which can be obtained through this capability.

  • Use Rehive transaction collections to bundle related transactions. This is useful when you need to fail or complete a set of transactions as a whole.

  • Stay up to date with Rehive Changelogs and deprecation timeline.

Find more developer recommendations here.

Did this answer your question?