Configure your application

Pay close attention to this step by step, because some panel scenarios have conditions and it will be necessary to go through a step to release the next functionality.

Configure your white label journey and access the Journey Demo menu

The application panel is the main scenario in which it will be possible to configure, test and monitor the APIs and white label journeys contracted by Open Keys, both for the Payments product and for the Data Sharing product.

Your first step, when your application has a white label product, is to access the Configure Journeys menu in your application panel.

 

In this first scenario above, you see a Data sharing Purpose selection screen. This item is mandatory so that your client has information on the purpose of using the data that will be consented to your company. When you click on Save edits, this information will be visible in the journey and your journey Demo menu will have the available Data Sharing flows.

In the scenario below, which represents the configuration of your white label journey for Payment Initiation, you must enter your company details and register the bank account that will receive the payment made by your customer. In the Receipt Data field , it is possible to optimize filling by only informing the Pix Key and the system performs a query via DICT to complete the rest of the information.

 

By clicking the Save edits button , whether on the Payments screen or the Data Sharing screen, you will enable demonstration journeys in your Journeys Demo menu . However, before you can even access them, you need to configure your test user!

 

Configure your test user

Now that you have configured and granted access to the journeys Demo menu, you need to register your test user to take advantage of the flows, end to end, in a Sandbox environment. First, access the Settings menu and on the first screen you will identify your product credentials and also the Test user management field. In it, you will need to enter a name, CPF (CNPJ is optional) and register a password. When you click Save , the system will generate the username that you can use in the mock stage, along with the password you chose.

 

Now that you have registered your user, how about registering the endpoint on which you will receive webhook returns about your customers' Payment or Data Sharing lifecycle!?

Configure your Webhook

To configure the endpoint through which you will receive webhook information, still in the Settings menu, simply change the page view to the Payment and Data scopes, so that you can access the Endpoint Management field . In this field, you also have a test button to evaluate whether the link was successful.

On this same screen, you can configure the consent expiration period. This option concerns the time that the consent status will change from “pending approval” to “Cancelled”, in terms of the moment it is generated and the completion of the journey. This is the time the user has to confirm the operation and this option to customize this time is specific to the test scenario, given that deadlines in a productive environment are defined by the Open Fianance ecosystem, being 5 minutes for Payments and up to 60 minutes for data sharing.

 

 

Now that you've made the mandatory settings for your panel, it's time to take advantage of all the opportunities it offers you. To learn more about all the other options available, visit the link below: