Wealth 2.0 - Card Refreshing Process

1. Schedule Refresh:

If your use-case requires automatic account refresh to keep track of transactional history changes, you can enable Nightly Refresh for new accounts. For this, you need to set the scheduleRefresh parameter to true in the iframe URL.

• iframe Example - https://{{instance}}-iframe.private.fin.ag/v2/?scheduleRefresh=true

2. Iframe Refresh (with the same loginid)

When a card passes to don't attend the NightlyRefresh Eligibility Criteria, the end-user has to re-engage with iframe in other to refresh the card. When it happens, the requestId iframe parameter has to be added to guarantee that refresh will impact the same loginid. Without this parameter, a new loginid will be created during reconnection process.

Observation: The requestid iframe parameter expects as its input the requestid of a previous successful connected card.

• iframe example - https://{{instance}}-api.private.fin.ag/v3/{{customerId}}/investments/reconnect?requestId={{requestId}}

• Request/Request History must exist. (This refers to the RequestId of the Regular Connect call as a first time at least, I think they can use the successful reconnect requestIds later on)
• Must not be Unauthorized / State is Successful (The requestId being used must refer to a successful request )
• Within 4 weeks old.