Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Learn how to set your brands look & feel which your customers will see when you invite them to provide consent/authorisation for their external accounts.

Connect setup

In order to allow your customers to provide authorisation for us to access their payment/external Partner account information, your customers have to go through our CONNECT module. We have allowed you ability to set your brands look and feel as well as given you the ability to set custom/bespoke  narratives to guide through your customers in the consent journey having that digital conversation with them citing the benefits of connecting their accounts and sharing the data with your institution via Groov.

A brief description of the module is as follows:


a. Consent & Authorise: The service handles the authorisation technicalities/setup and manages the OAuth connections and consent management flows. It requires authorisation from the customer sharing their data to establish a connection to the their external account data source, before data can be pulled. Institutions have the following options for the user experience their customers will follow to authorise the sharing of their account data.
In order for you to setup the details, you can use the 'Edit' option in product connections page or navigate via Settings and Edit option. The former option will look something similar to the following:

  

What needs to be setup

Please use this section to provide bespoke/custom narratives that will appear in your white-labeled consent CONNECT flow to explain to your customer what data you plan to collect and what value you will provide via your offerings. There are information fields to provide narratives for both an unhappy retry and a deny flow if the customer ever happens to land on one. 
As a default we will provide you with some placeholder narrative that you can use as examples to amend and provide your version of the narratives. Or if you are happy with the placeholders, you can leave them as is.


    

Image Added

Contextually,

: the value that you will provide in field "Redirect URL" which is mandatory will be used by CONNECT journey to redirect the customer/merchant flow back to you once they complete their account linking process via Groov using our CONNECT consent journey. This redirect URL could be your 'Thank You/Next Steps' page on your website OR it could be a handshake step in your customer engagement journey from where you initially triggered Groov's CONNECT journey. 

: the copy text in the field "Hosted Page" in the section above will appear in the landing page of the CONNECT journey that your customer/merchant will see when they click the CONNECT consent URL. 

: the copy text in the field "Data access consent copy" in the section above will appear in the second step of the CONNECT journey when your customer/merchant selects a data source provider/payment/commerce partner and clicks on the CTA button labelled "Next"


: the copy text in the field "Deny consent confirmation copy" in the section above will appear in the CONNECT journey when your customer/merchant decides to abandon the account linking process.

: the copy text in the field "Retry connect consent flow copy" in the section above will appear in the CONNECT journey when your customer/merchant fails to successfully connect to their data provider account, this could be for various reasons like incorrect credentials or the data provider server downtime, etc. 


  • Appearance/Brand

You can use this section to set your brand logo, colour themes to give the connect HOSTED consent flow pages your institution applications look and feel. There is a Preview iframe that lets you interactively test your brand settings as you configure.


                  


Once the changes are made, remember to Save the changes. 

You can always revisit these sections on your Portal account and make as many changes as you want till you get the narratives drafted to your satisfaction. You can view your changes in the actual test consent flow when you setup a test connection as explained in the next section



Panel

On this page:

Table of Contents



Related pages

Filter by label (Content by label)
showLabelsfalse
spacesGroovDocs
showSpacefalse
sorttitle
typepage
cqllabel = "test-consent-connect-flow" and type = "page" and space = "GroovDocs"
labelsdocumentation-space-sample