Skip to main content
This guide covers practical tips for integrating Flinks Upload into your application, including submission modes, data consumption patterns, and handling edge cases.

Integration modes for submitting documents

There are three ways users can submit documents to Flinks Upload:
ModeDescriptionBest for
Connect Widget (Primary)Upload option displayed alongside bank linking after institution selectionMaximum coverage — users choose between linking or uploading
Connect Widget (Fallback)Upload option appears only after a failed bank login attemptKeeping bank linking as the primary flow
DashboardManual upload through the Flinks DashboardBack-office or support-initiated uploads
For details on configuring the primary and fallback modes, see Flinks Upload.

Integration modes for consuming data

ModeDescription
APICall /GetAccountsDetail to retrieve extracted transaction and account data programmatically
DashboardView extracted data and fraud signals visually in the Flinks Dashboard
Use the API for automated workflows. Use the Dashboard for manual review of fraud signals and document quality.

Fallback triggers

When Upload is configured as a fallback in Flinks Connect, the upload option appears automatically when the user encounters one of these connection errors:
Error codeDescription
INVALID_USERNAMEThe username entered was not recognized
INVALID_PASSWORDThe password entered was incorrect
INVALID_LOGINGeneric login failure
DISABLED_LOGINThe user’s online banking access is disabled
RETRY_LATERThe financial institution is temporarily unavailable
SESSION_EXPIREDThe session timed out during authentication
INVALID_SECURITY_RESPONSE_NO_RETRYSecurity question answered incorrectly with no retry allowed
AGGREGATION_ERRORA general error occurred during data aggregation
The fallback behavior is also built into the Primary configuration — so if you enable Primary mode, fallback logic is included automatically.

Force-upload shortcut

You can send users directly to the upload flow for a specific financial institution by appending /upload/[Institution Name] to your Flinks Connect URL:
https://[instance]-iframe.private.fin.ag/v2/upload/[Institution Name]
This bypasses the institution selector and login screens, taking the user straight to the document upload screen for the specified institution.

Async handling with webhooks

Flinks Upload processes documents asynchronously. Rather than polling the API for results, configure webhooks to receive a notification when processing completes.
Use webhooks over polling. Webhook-based async handling is the recommended pattern for Upload. It reduces unnecessary API calls and delivers results as soon as they’re ready.

Credit union member numbers

For credit union accounts, member numbers may be displayed with suffixes that indicate the account type:
SuffixAccount type
-0Chequing / share draft
-1Savings
-2, -3, etc.Additional accounts
For example, a member number like xxxx2354-0 indicates a chequing account, while xxxx2354-1 indicates a savings account under the same membership.

Multiple files in one upload

When a user uploads multiple PDF files in a single submission, they count as one upload against your quota. You don’t need to have users submit files one at a time — up to 24 files (180 MB total) can be included in a single upload.