---
title: Week of September 21, 2026
slug: changelog
docTags: 
createdAt: 2026-09-28T01:17:11.436Z
---

Each week we share what is new on Invoiced by Flywire, including new features, bug fixes, and improvements.

:::Changelog{title="Releases"}
::ChangelogItem{type="added" description="the ability to assign up to 10 owners per account, instead of one."}

::ChangelogItem{type="improved" description="the Merchant Transactions export on Flywire Payments so it includes all invoices applied to a payment, instead of listing only the first invoice."}

::ChangelogItem{type="fixed" description="an issue where customer top-ups were not reflected in the payout report, preventing proper reconciliation."}

::ChangelogItem{type="fixed" description="an issue where dispute reports with a pre-arbitration status could not be reconciled."}

::ChangelogItem{type="fixed" description="an issue where payout report discrepancies occurred when a capture reversal was processed without a corresponding capture deposit being recorded."}

::ChangelogItem{type="fixed" description="an issue where some payments could show a generic 500 error instead of a decline message when 3DS authentication failed."}

::ChangelogItem{type="fixed" description="an issue where card input fields on the Customer Portal could render as a blank frame when the payment gateway failed to fetch available payment methods."}

::ChangelogItem{type="fixed" description="an issue where asynchronous card declines could result in a 500 error displayed to the customer instead of the actual decline reason, and omit the failure message from the database."}

::ChangelogItem{type="fixed" description="an issue where customers in Canada using PAD payments on Flywire Payments could not complete a payment due to missing verification configuration."}

::ChangelogItem{type="fixed" description="an issue where system jobs were incorrectly voiding bank-feed payments that had already been applied to invoices, causing those invoices to revert to unpaid."}

::ChangelogItem{type="fixed" description="an issue where QuickBooks Desktop customer custom field names containing spaces or special characters were not synced correctly."}
:::