1. Introduction and Service Overview
Charge Assist (CA) white label app is a service provided by GreenFlux (GFX), under which GFX makes the development and maintenance of a white label app, on behalf of the customer. The app is supported both in Android and iOS.
This app is based on Charge Assist app (available in Play Store and App Store). The functionalities that will be available are based on those. Any additional functionality may be proposed, subject to be adopted by GreenFlux. Once we get a commitment from the customer that the app development is to start, we will take care of development, and we start charging this service to the customer, once this is made available towards the customer.
It is important to mention that the app is owned by the customer, meaning that the app will be hosted in the customer app stores' account.
As follows, a high level process for delivery of the white label app.
As follows, an overview on the main delivery steps and the roles of each entity. It is crucial that once a project is initiated, both GreenFlux and the customer commits resources, in order to ensure a smooth and quick delivery. More details in section 2.2.
Delivery Step | Description | Customer Role | GreenFlux Role |
KoM | Kick off meeting | Joint meeting | |
0.1 | Basic Setup of GreenFlux platform (ACC and PROD) | Consulted for some inputs
Setup of Stripe Account (ACC and PROD) | Make all configurations in ACC and PROD environments |
0.2 | Creation of business accounts in app stores | Main responsible | Fills in only information directly related with the app architecture/ safety features, in the app stores |
0.3 | Basic app configurations, settings and receipt info form | Responsible | None |
1 | Develop acceptance apps (ACC) | None | Responsible |
2 | Send invitations to customer, for testing ACC app | None | Responsible |
2.1 | Testing in ACC app build | Responsible | None |
3 | Configuration of google and apple pay | Google Pay: customer always responsible for this
Apple Pay: GreenFlux handles, unless informed otherwise | |
4 | Develop production apps (PROD) | None | Responsible |
4.1 | Send invitations to customer, for testing PROD app | None | Responsible |
4.2 | Testing several use cases with the PROD app | Responsible | None |
5 | App release | The responsibility will be according to what customer defines in the settings form. |
2. White Label App Delivery
2.1 Responsibilities
Customer:
- Responsible for registration in the app stores and fill in all required fields to being validated for app launching (e.g. terms and conditions, company website, etc..)
- Providing the required information for app development (e.g. design pieces such as images, logos, marketing texts, etc)
- Registration in Google/Apple Pay (guidelines available in FAQ section later on)
- Marketing activities related with app promotion and advertisement
- Any costs associated with registration in the app stores or Stripe.
GreenFlux:
- Responsible for the app development and maintenance (Charge Assist Team)
- Fill in the app stores required info related with architecture and data management from the app. (Charge Assist Team)
- Customer Success Manager: coordinates activities and alignment on both sides
2.2 Delivery Steps
Step 0.1: Basic Setup of GreenFlux platform – Setup ACCeptance and PRODuction platform environments, including:
Action Description | Responsible |
Setup Stripe Account and share linking URL with customer | CSM |
Setup CPOs and link them to Stripe account and to Charge Assist related OCPI subscription | CSM |
Create and share with customer an EMSP in ACC (only), where they will be able to issue tokens, that can be used for test purposes | CSM |
Share ACC and PROD environments with customer, as well as relevant CPOs/EMSPs. | CSM |
Align with customer what is the pricing model for their direct payment methods (applicable to CPO only). This is defined in the back-office and not visible to customer. | CSM |
Link the Stripe Account, both PRODuction and ACCeptance, after receiving instructions from CSM | Customer |
Step 0.2:
Customer creates a business account in both iOS and Google Play app stores.
- App Store Connect (iOS): https://appstoreconnect.apple.com/register
Note: Make sure to have access to App Store Connect
- Google Play Console (Android): https://play.google.com/console/register
For both accounts:
- Add users of your (customer) organization
- Add a user of GreenFlux as admin in order to support you with the setup and manage the releases:josien.jansen@greenflux.com
The customer needs to fill in all required fields in the App stores for initial setup and releases (only exception are those that are app specific (e.g. security of data, app architecture)
Step 0.3:
Customer provides the following data and sends it back to the CSM:
- Basic configurations, settings and receipt info form, as per attachment ‘Settings Form.docx’
- App assets/logo, as per attachment
‘App Assets.pdf’
CHECK-POINT:
The app build can only start once steps 0.1, 0.2 and 0.3 are concluded. These need to be concluded in full, including all mandatory fields in the app stores (e.g. terms and conditions, company website, etc…)
Step 1: GreenFlux
develops the acceptance (ACC) apps (android + iOS)
- @CA Team: guarantee QR codes point to correct app (ACC tenant)
Step 2: GreenFlux sends invitations to customer, for allowing it to test the ACC app - (invitation sent by e-mail from CA team, to the e-mail addresses indicated in the settings form)
Step 2.1
(Optional): Customer carries out testing in Acceptance after receiving invites. See some guidelines in the FAQ section below.
Step 3 :
Customer configures Google Pay (this is optional, depending on whether the customer wants to allow these payment types)
See instructions in FAQ at the end of the article.
Step 4:
GreenFlux develops the production (PROD) apps (android + iOS) in parallel
- @CA: guarantee QR codes point to correct app (PROD tenant)
Step 4.1: App pre-release (android + iOS). At this stage, no app is available in the app stores. GreenFlux will send invitations to customer, for allowing it to test the PROD app
(invitation sent by e-mail from CA team, to the e-mail addresses indicated in the settings form).
INFO:
Once we reach this stage, GreenFlux will trigger invoicing of white label app product.
Step 4.2:
(Optional): Customer carries out testing in Production app
Step 5: App release (android + iOS) – GreenFlux or the customer will request the app stores to launch the app, according to the approach defined by the customer in the ‘Settings Form’.
3. Miscellaneous
3.1 Additional Remarks
- Direct Payment Methods (e.g. credit card, Apple/Google Pay) are only available for our CPO customers (more details about this in this article: Ways to start a session using Charge Assist App (greenflux.com)).
- For EMSP customers, the only available option is using a charge card, which yields (typically) end of the month payment from drivers towards his/her EMSP (more details about this in this article: Ways to start a session using Charge Assist App (greenflux.com)).
- Setting up Apple/Google Pay for Acceptance builds is not possible. In order to simulate an ad-hoc payment, the user can use a credit card, from one of those provided by Stripe
- GreenFlux cannot provide test charge cards to test sessions in PRODuction environment. Customer will need either to issue some (if acting as EMSP), or using an external card. For issuing charge cards (virtual) in ACCeptance, so that you can use to test sessions in the ACCeptance build, check FAQ section, question about tests.
3.2 FAQ - Frequently Asked Questions
Can we have the receipts in several languages?
Multi language receipts are available. List of languages:
- English (standard)
- Dutch
- French
- German
- Spanish
- Greek
Customer wants to grant access to test app to additional users, how to do it?
This is only possible to do ad-hoc for Android. The test users for iOS based apps can only be invited when they have been added upfront when setting up the app build. This should as such have been provided with the settings form (see step 0.2)
For Android (only, share in any moment the following with your CSM:
Name | E-mail | Access to ACC app? (Y/N) | Access to PROD app? (Y/N) |
How do I setup the Google and/or Apple Pay?
This is applicable only to CPO customers that want to activate ad-hoc charging (charging sessions that are paid immediately after the session through Stripe, powered by GreenFlux.
Apple Pay:
GreenFlux will take care of this, unless you have defined that this should not be done (in the ‘Settings Form’ Attachment), or should not be done by GreenFlux. When GreenFlux does it, we will of course link the apple pay to the customer stripe account, so that all payments end up in the customer stripe account.
When customer wants to do it themselves, then you can activate it using this documentation (no support from GreenFlux though): you should follow the instructions as provided in this Stripe documentation – LINK. In particular, you should follow the steps regarding "Set up Apple Pay for your iOS app".
Google Pay:
Before proceeding with this setup, request the necessary screenshots to GFX, which are mandatory by google.
This is a little more complex, as you will have to submit the app for approval to Google (separately from the Store release!). Most of these steps will have to be done by the customer or those in control of the merchant account.
The steps are as follows:
- Create an account in Google Pay Business Console (Google account credentials can be used).
- Go to the “Integrate with your Android app” part (“Integrate with the Google Pay API” you already have).
- You will see the apps that are available and are developed by the business entity you are logged in into.
- Click on Manage.
- Choose “Integration type” as Gateway (As we're performing this integration through Stripe and not directly).
- Take screenshots of the app and the concrete way the payment flow through Google Pay looks like. These screenshots can only be taken based on a test version on App Tester as the integration itself is not yet available.
- Upload and save the screenshots (< 1 MB has to be uploaded).
- Submit the integration for approval.
- Google will reply to your integration through e-mail.
Which kind of tests can I make to get used to the app
Customer may perform tests of the app to go through the user journeys and understand a bit more in-depth how the app works. It is advisable to perform tests in a first stage in ACCeptance environment. For this, customer will need to connect a charger to GreenFlux ACCeptance environment (no test chargers available by GreenFlux).
GreenFlux suggests two user journeys are tested, in order to get and end2end view:
- Perform a charge session using an direct payment method (using credit card)
- Perform a charge session using a charge card, added to the app
Useful resources:
- Relevant for 1: Stripe provides some testing credit cards, that you can use to perform the ad-hoc user journey in Acceptance environment – check this LINK
- Relevant for 2: You should create a charge card in ACCeptance EvPortal environment, that you can then add in the app as a charge card