Page Comparison

Learn how to enable your customers to go through Groov's Connect consent management journey (white labelled with your brand) and connect their external accounts

Integration section

Once you are complete with editing the Connect setup, you’ll find access to the user secret_key In the Integration section.

The user secret_key is used to authenticate your application against the Groov API and should be treated confidentially, every institution user (role permitting) will have his/her secret_key. In test mode, it will be prefixed with pk_test whilst a live secret_key will have pk_live as prefix.  We dont expire the user secret_keys at the moment but if you loose them, you can regenerate them on demand by reaching out to us. The institution client_id is not secret but is used to identify your application instance with us as an institution, this can be found in the Developers section (which is under design).

The Integration section also allows you to configure redirect URIs. Groov's Connect consent flow (and SDK's) will redirect to one of these URIs when your customer authorises the account consent with Groov, we will not be able to redirect to any other locations. These redirect URIs could be as simple as your application page details from where you initiated the Groov Connect consent flow (or could be as simple as to your institution web page if the consent initiation at your end has been via a manual campaign). Currently our default setup allows you to provide one redirect URI. 

Test your consent flow

You are all set to test your first consent flow with Groov. This will be your first API test call to our CONNECT hosted page via the Portal. We have enabled this ability from the Portal dashboard to test the white labeled CONNECT consent flow as soon as you get your Portal account without having to wait for your development team to set up the back end toolkit to connect to Groov. 

1. Click on Test oAuth button as shown below

2. The following screen will be presented. It will ask you to enter an 'Account Id'. As this is a front end based test consent flow, we would need a unique customer account identifier (a test identifier you want to associate with your test connection customer record) in this field. In a Live mode, when you call our CONNECT hosted page from a journey page (or a campaign page) from your end/application, your back end logic (or campaign mailer logic) will pass us this account identifier for every customer you bring on to our CONNECT consent journey. We use this account identifier known to you to identify an initial ledger record on our platform.

Once you provide the account identifier, the Copy button will get enabled for you to click and copy the CONNECT hosted dynamic link. once you click on the button, the dynamic URL gets copied to your clipboard which you can use to test a sample customer connect flow right away. 

3. Open a new web browser window, and paste the CONNECT link/URL from the previous step in the browser address bar. You will be presented with the landing hosted page all white-labeled with your appearance/brand and showing your consent narratives that you setup in the previous steps. The page will look as follows (the one below is a design copy only). In your test version ensure your consent narratives are appearing correctly else note down copy changes you would want to go back later and save.

4. As this is test mode, you will see 'sandbox' partner available to connect. You are now going through the flow as one of your SME customer. Select the available partner and proceed to next step. 

FYI, a progress bar allows your customer to sense check the progress of the consent/authorisation flow. 

5. Your SME customer will be shown the following Groov consent confirmation page which explains that Groov will show as the 3rd party having access to their external accounts provider data and details how we manage/process the data on behalf of your customer.

6. Progressing ahead, your customer will be presented with the partner connection logic page. As this is a test mode, you will be shown the sandbox logic page that we have curated to enable you test our product and access test data. The user credentials are preset, you will just need to select one of the many test customer types and follow the steps till you see a connection successful page. You will be then redirected to any redirect URI you setup as part of the previous step configs or you will be taken to our default URI. 

7. Post a successful consent flow, you can browse through the Portal dashboards as explained in the next step to access the Sales data from our Portal front end OR if you have your engineering team at hand, you can connect to our Unified Groov API's via Swagger links and use the test ledger ids created for the test connection as above and go through our test dataset.