Sharing data

For you to retrieve subscriptions from Minna, you need to share account and transaction data. You can share data either on-demand or by letting Minna do data polling.

Pros and cons for sharing data on-demand or with data pollingPros and cons for sharing data on-demand or with data polling

Pros and cons for sharing data on-demand or with data polling

On-demand

When you share data on-demand, you explicitly need to start a sync. Minna will detect subscriptions as part of the sync. Once the sync is completed you can get the subscription data either directly or at a later time. The main downside of this approach is that the overall latency can be high, since transactions need to be shared and processed right before retrieving subscription data.

Sharing data on-demandSharing data on-demand

Sharing data on-demand

Implementing on-demand sharing

  1. Create a backend endpoint that calls Minna's API (with Authentication), that your frontend can call.
  2. Start a sync.
  3. Fetch the subscription data.
  4. Store responses in a database/cache.
  5. Your frontend calls your backend endpoint to get data.

Data polling

When you share data with data polling. You allow Minna to fetch accounts and transactions on a scheduled basis. This requires you to create endpoints for account and transaction data that Minna are allowed to call.

Sharing data with data pollingSharing data with data polling

Sharing data with data polling

Implementing data polling sharing

  1. Provide an accounts endpoint that Minna can fetch data from.
  2. Provide a transactions endpoint that Minna can fetch data from.
  3. Provide an access or refresh token with long enough TTL to allow Minna to set up scheduled batch jobs.

Requirements

As you can see in the following matrix, on-demand requires very little on your infrastructure, while data polling requires you to open up endpoints for Minna to call.

Requirements

On-demand

Data polling

Requires dedicated PULL endpoints

Pros and cons

The main reason for allowing Minna to do data polling is to reduce latency. By letting Minna process data on a scheduled basis, the data can be ready and up to date when you want to retrieve it.

Pros

On-demand

Data polling

Scheduled

Reduced network latency

Reduced overall latency

Shorter loading times

Share and retrieve

The following matrix summarizes all the different combinations of sharing and retrieving data:

Minna ← Bank

Minna ← Bank

Minna → Bank

on-demand

batch-job

webhook

Minna ← Bank

on-demand

(✅)

Minna → Bank

data polling

Two notable combinations are sharing on-demand + retrieving with batch job and sharing on-demand + retrieving with webhook. The first case requires you to both share transaction data in your batch job and retrieve subscription data. The second case doesn't make much sense since the webhook solution is reactive. When using webhooks, Minna should pull data from you using data polling.


Did this page help you?