Widget

The Fintoc Widget is the component that your users will interact with to connect their bank accounts with Fintoc.

The Widget handles the validation of credentials, multiple factor authentication and error handling for each financial institution that we offer. You can use the widget in web applications as well as in mobile applications.

Movements Widget flow

The Widget flow starts when your user wants to connect its bank account with your application.

1. In your frontend, use your Public Key and a webhook to an endpoint on your backend to configure the Widget and show it to your user.
2. Once your user finishes the Widget flow, the Widget itself will close. The flow finishes when the Link gets created correctly or when the user stops the Link creation process by closing the Widget prematurely.
3. If a Link was correctly created, you will receive the new Link through a webhook, including its link_token. Save this link_token to be able to use the Link in the future.
4. You can use the onSuccess and onExit functions from the widget so that code gets executed on certain events. For example, you can use the onSuccess function to redirect your user to another URL once a Link gets correctly created.

Flow example

Warning: After the creation of the Link, the usage flow that is shown on the diagram is very simplified. The real usage of an application could vary radically, but the simplified example should be useful to understand the interactions between different entities.

Payments Widget flow

The Widget flow starts when your user wants to start the payment through your application.

1. In your backend, use your Secret Key to create a Payment Intent and send the widget_token attribute of said Payment Intent to your frontend.
2. In your frontend, use your Public Key and the widget_token from the previous step to configure the Widget and show it to your user.
3. Once your user finishes the Widget flow, the Widget itself will close. The flow finishes when the Payment Intent is finished correctly or when the user stops the Payment Intent process by closing the Widget prematurely.
4. You can use the onSuccess and onExit functions from the widget so that code gets executed on certain events.

Flow example

Warning: After the creation of the Payment Intent, the usage flow that is shown on the diagram is very simplified. The real usage of an application could vary radically, but the simplified example should be useful to understand the interactions between different entities.

Subscriptions Widget flow

The Widget flow starts when your user wants to create a subscription through your application.

1. In your backend, use your Secret Key to create a Subscription Intent and send the widget_token attribute of said Subscription Intent to your frontend.
2. In your frontend, use your Public Key and the widget_token from the previous step to configure the Widget and show it to your user.
3. Once your user finishes the Widget flow, the Widget itself will close. The user flow finishes when the Subscription Intent is finished correctly or when the user stops the process by closing the Widget prematurely. You can use the onSuccess and onExit functions from the widget so that code gets executed on certain events.
4. Now we have to wait until Subscription gets active. Banks can take up to 72 business hours to activate a Subscription.
5. After the Subscription is active, Charges can be added. Banks can take up to 72 business hours to confirm a Charge.

Flow example

Warning: The creation and usage flow that is shown on the diagram is very simplified. The real usage of an application could vary radically, but the simplified example should be useful to understand the interactions between different entities.