The white-label handover process will only begin once you have submitted all of the required information and taken all of the required actions listed below.
This article relates to preparing the App for white-label go-live, all of which can be done via the Dashboard. We recommend that you start the white-labeling with your Test Project to keep the momentum. Once your Production Project is approved, we can simply switch out your Test App ID with your Production App ID.
Please note: The requirements for going to production are separate - see the production review article for more information.
Once you have prepared all the information below, you can complete this form to submit your white-label request.
App name (max 50 characters - will be displayed publicly to end-users)
App description (max 255 characters - will be displayed publicly to end-users)
Logo: Format: PNG, Width: At least 800px, Height: Less than half the width, Size: Less than 200kB
Icon: Format: PNG, Width: At least 500px, Height: Exactly equal to the width, Size: Less than 200kB
Rehive App IDs for production and test projects
Wallet URL (e.g. wallet.yourdomain.com, needs to be a domain you own and control)
Company legal name and address.
Link to website.
Terms and conditions URL (either on your website or you can use a third-party provider like Iubenda)
Sign up for SendGrid and Twilio accounts to use in your Production Project. You will not be able to use Rehive's credentials in production.
Complete the registration and get started steps on the Dashboard.
Configure a Rehive test project and have the App ID ready.
Configure a Rehive production project and have the App ID ready.
Web app (required for white-label web application)
Set up your DNS records and related configurations in the Rehive dashboard as described in the following article: Configuring your custom domain.
Mobile apps (required for white-label iOS and Android applications)
See all information below related to self-hosting and how you can complete your mobile applications set up via the Dashboard.
Apple Developer account registered under your business name (not an individual account)
Google Play developer account registered under your business name (not an individual account)
If your organization does not have an Apple Appstore account, you will be needing a D-U-N-S number.
Vector version of logo (width: at least 1024px, height: less than half the width, format SVG, max 5MB)
Vector version of icon (width: at least 1024px, height: exactly equal to the width, format SVG, max 5MB)
(Optional) Unique apple bundle identifier (e.g. com.yourdomain.wallet)
(Optional) Unique android package name (e.g. com.yourdomainwallet)
(Optional) Splash screen image to display on startup for iOS/Android apps
(Optional) Mobile app name (if different from web app name)
Demo user for the app stores to test the product.
Source code handover:
Please see the Rehive Mobile App source code which can be downloaded from the App Extension section in the Rehive Dashboard. For codebase access a Rehive Premium or Enterprise subscription is required.
Additional requirements for Merchant Documentation:
Log into the DNS provider for your domain and set up DNS records with the following details:
Documentation: DNS Name: docs.yourdomain.com, Type: CNAME, TTL: 5 minutes (or longer if your provider does not support 5min TTL), Data: fintechdns.com
API: DNS Name: api.yourdomain.com, Type: CNAME, TTL: 5 minutes (or longer if your provider does not support 5min TTL), Data: fintechdns.com
Your npmjs.com account name and access token for publishing your Merchant Documentation SDK.
The above additional requirements fall under the category of backlog issues. The concept behind this initiative is to enable merchants to independently manage their documentation for online payments, offering a white-label solution for clients. You can find further details here.