July 2026

August 1, 2026

​

Flinks Pay

Faster payments for returning customers: Customers who’ve already linked their bank can pay again without re-linking. Flinks can securely save and reuse their bank account information, so repeat payments skip straight to the amount step, offering a smoother checkout experience and helping reduce drop-offs. Payee visibility: Sessions with an optional payee now show those details in the API response, including institutionCode, transitNumber, accountNumber, and accountLabel, so you can clearly see who’s being paid. G-EFT reports by email: G-EFT reports can now be delivered by email on top of the existing SFTP option, and each report includes a summary header row with the aggregate totals. A weekly email schedule is also available alongside the existing daily delivery. To have this enabled, G-EFT customers need to contact their Flinks account manager.

​

Flinks Upload

Improved error responses: Error responses from the Flinks Upload complete endpoint now include the LoginId, making it easier to trace and investigate failed requests. Response messages have also been made clearer about the upload state. Duplicate file detection within the same request: Duplicate files submitted within the same upload request, whether matching by name or content, are now caught and rejected upfront. 20 MB per-file limit now enforced on the API: The 20 MB per-file size limit already in place for uploads through the Customer Dashboard and Flinks Connect now applies to the Uploads API as well. Files exceeding this limit will be rejected at upload time.

​

Flinks Enrich

Next Pay Date attributes fix: We’ve fixed an issue where Next Pay Date attributes returned no result for some requests, even when pay dates were available.

​

Customer Dashboard

Added Refresh warning: A warning now appears every time before a refresh starts, noting that the refresh may fail if the institution requires reauthentication or is temporarily unavailable. This helps set expectations around the limitations of refresh and its potential impact on the end-user flow. This applies to Flinks Connect requests only. Flinks Upload refreshes are unaffected.