September 2026 Updates

All Updates

September 2026

September 2026 Product Updates

Improvements

Connector
- Upgrade the MX Connect widget to MX's new Web Connect Widget SDK
- Reduce Connector and SDK bundle sizes to improve load times for end users
- Improve visual hierarchy across Connector forms and search screens (sizing, spacing, and emphasis)
- Add vertical padding to the MX widget
- Improve provider routing for institutions with limited connection history
- Improve the connection fallback screen so a failed connection no longer reads as a dead end, and offer a clear next step whenever another connection path is available
- Replace bank-specific wording with institution-neutral wording throughout the Connect and Repair flows
- Smooth loading state transitions so screens and loading indicators crossfade instead of flashing between steps
- Ensure that initial load for Dark mode connector does not flash a light background
- Reduce the visual prominence of scrollbars and improve their theme-awareness
- Ignore transient MX outages while polling connection status, so a brief provider blip no longer aborts a poll during the Connect flow
GraphQL
- Return 405 Method Not Allowed when a mutation is sent via GET instead of 400 Bad Request
- Return 422 Unprocessable Content for invalid query strings or malformed variables instead of 400 Bad Request
- Expose new Plaid remote data fields including account APY, holding cost basis and tax lots, and account verification previous returns
REST API
- Expose a Processor Token's account connection status to the Processor Token introspection endpoint
- Expose new Plaid remote data fields including account APY and holding tax lots
- Return 502 Bad Gateway for all MX provider 5xx errors, including gateway timeouts and unmapped status codes that previously surfaced as 500
Platform
- Add sync event metadata reporting for Investments transactions; previously event sync metadata only captured date ranges for non-investment transactions and account statements
- Sync available data immediately when importing Plaid connections without transactions, instead of waiting on webhooks that may not fire
- Improve fill rate for Holding.costBasis for certain Finicity-sourced accounts
- Prevent infinite loop when Finicity can't access webhooks
Dashboard
- Add a /billing link that opens billing for your organization
- Show a retryable "MX is temporarily unavailable" message when MX cannot be reached while validating integration credentials
Hub
- Make Connector flows launched from the Hub follow the Hub's light or dark theme instead of always defaulting to light
- Improve spacing and alignment on the experience picker and footer
- Add tooltips to icon-only buttons for keyboard and screen-reader users
- Standardize icon sizing and spacing inside buttons
- Align the Add Account button height with the balance indicator
- Improve accounts list empty-state messaging
Documentation
- Group Account Numbers and Balance Refresh endpoints under a single Accounts section in the REST API reference
- Clarify that ACH numbers may be fetched asynchronously and become available after the end-user verifies their account
- Call out the Connection.at field as the "as of" timestamp for judging how current a SYNCED status is
- Add a how-to guide for verifying a bank account and retrieving ACH account and routing numbers for payments
- Document the themeMode option for Quiltt.connect and Quiltt.reconnect in the Connector JavaScript API reference
- Add a tutorial on working with enriched transaction data, showing how to enable an enrichment provider and query categories, merchant names, and logos via the GraphQL API
- Explain how Profiles are billed, including how empty and deleted Profiles count toward each billing period
- Add a top-level Guides section that organizes how-to content by developer job-to-be-done
- Move the Connector reconnect walkthrough into Guides as "Reconnect a broken bank connection", with a redirect preserving the old link
- Document the 502 Bad Gateway response returned when an upstream provider is temporarily unavailable, and recommend retrying with backoff
- Reclassify task-oriented tutorials as Guides, moving GraphQL tooling, account statements, transaction enrichment, transaction sync, and account verification into the Guides section
- Redirect the old tutorial URLs to their new Guides locations so existing links keep working
- Explain in the connection troubleshooting reference that a connection can re-enter ERROR_REPAIRABLE repeatedly for some institutions and providers, and link it to the reconnection guidance
- Align the Connector landing page title and meta description with search keywords
- Rewrite the meta descriptions on the Finicity, Akoya, Plaid, and MX connectivity integration pages so each is unique and search-optimized
- Align the Get Started page title and description with the open banking API keyword strategy so the docs entry point ranks for the terms developers search

Bug Fixes

Connector
- Fix OAuth popups (e.g. bank credential pages) closing prematurely in WebKit-based browsers (Safari and all browsers on iOS) by requesting third-party storage access in the embedded Connector iframe
- Fix MX connections stalling on "Connecting..." when MX doesn't signal completion
- Fix the MX widget ignoring the themeMode passed at launch and using the Connector's Dashboard theme instead
- Fix the MX widget resolving an auto theme on its own, so it could render light while the rest of the Connector rendered dark
- Improve handling of user-actionable MX errors
- Improve handling of Finicity Connect 201 "Retry Later" error code to show a user-friendly error message instead of attempting to close the Connector prematurely
- Fix MX connections failing when institutions reject optional account identification products
GraphQL
- Fix highlighted code suggestions being unreadable in the GraphQL Explorer
Platform
- Notify administrators and stop syncing when Plaid integration credits are exhausted
- Fix Finicity error 913 (no active accounts found) incorrectly classified as error_provider, so connections whose accounts were closed now resolve to synced instead of surfacing a provider error
- Fix unstable Finicity transactions ids created when re-syncing accounts with multiple same-day, same-amount charges
- Fix duplicate transactions created when two syncs run on the same account at once
- Fix Plaid connections getting stuck failing transaction syncs after a reconnect
- Fix available balance extraction for Finicity investment accounts
- Fix transaction history loss when duplicate accounts merge after reconnect
- Fix new Finicity connections sometimes syncing with no transactions after Connect
- Fix Finicity balance refreshes reporting declined/revoked consent and internal system errors as unrecoverable instead of prompting reconnection
Dashboard
- Fix Enrichment integrations (FinGoal, Ntropy, Pave, etc.) incorrectly showing "Upgrade to Unlock" for Builder plan organizations
- Fix an expired or revoked session trapping the browser in a reload loop between the app and the login page instead of letting you log back in
Documentation
- Correct the Connector provider name to Mock Data to match the Dashboard
- Reorder the Statements tutorial Connector setup so the provider is enabled before the product
- Correct the connectionSimulateError mutation response shape in the reconnect guide
- Fix the onExitSuccess event value in the Connector JavaScript API reference
- Add the missing QuilttConnector import to the React Native example in the migration guide
- Fix invalid JSON in the GraphQL queries curl example
- Fix API Reference link buttons
- Correct the DISCONNECTED reconnect guidance: reconnecting establishes a new Connection to the same institution, and reconnecting an errored Connection can in some cases replace the Connection record
- Fix the subscription onData payload access in the GraphQL tooling tutorial so the example reads the result at data.data
- Correct the API version upgrade steps to match the Dashboard: click the Upgrade API Version button, then select Upgrade to vX from the menu

Connector
- Upgrade the MX Connect widget to MX's new Web Connect Widget SDK
- Reduce Connector and SDK bundle sizes to improve load times for end users
- Improve visual hierarchy across Connector forms and search screens (sizing, spacing, and emphasis)
- Add vertical padding to the MX widget
- Improve provider routing for institutions with limited connection history
- Improve the connection fallback screen so a failed connection no longer reads as a dead end, and offer a clear next step whenever another connection path is available
- Replace bank-specific wording with institution-neutral wording throughout the Connect and Repair flows
- Smooth loading state transitions so screens and loading indicators crossfade instead of flashing between steps
- Ensure that initial load for Dark mode connector does not flash a light background
- Reduce the visual prominence of scrollbars and improve their theme-awareness
- Ignore transient MX outages while polling connection status, so a brief provider blip no longer aborts a poll during the Connect flow
GraphQL
- Return 405 Method Not Allowed when a mutation is sent via GET instead of 400 Bad Request
- Return 422 Unprocessable Content for invalid query strings or malformed variables instead of 400 Bad Request
- Expose new Plaid remote data fields including account APY, holding cost basis and tax lots, and account verification previous returns
REST API
- Expose a Processor Token's account connection status to the Processor Token introspection endpoint
- Expose new Plaid remote data fields including account APY and holding tax lots
- Return 502 Bad Gateway for all MX provider 5xx errors, including gateway timeouts and unmapped status codes that previously surfaced as 500
Platform
- Add sync event metadata reporting for Investments transactions; previously event sync metadata only captured date ranges for non-investment transactions and account statements
- Sync available data immediately when importing Plaid connections without transactions, instead of waiting on webhooks that may not fire
- Improve fill rate for Holding.costBasis for certain Finicity-sourced accounts
- Prevent infinite loop when Finicity can't access webhooks
Dashboard
- Add a /billing link that opens billing for your organization
- Show a retryable "MX is temporarily unavailable" message when MX cannot be reached while validating integration credentials
Hub
- Make Connector flows launched from the Hub follow the Hub's light or dark theme instead of always defaulting to light
- Improve spacing and alignment on the experience picker and footer
- Add tooltips to icon-only buttons for keyboard and screen-reader users
- Standardize icon sizing and spacing inside buttons
- Align the Add Account button height with the balance indicator
- Improve accounts list empty-state messaging
Documentation
- Group Account Numbers and Balance Refresh endpoints under a single Accounts section in the REST API reference
- Clarify that ACH numbers may be fetched asynchronously and become available after the end-user verifies their account
- Call out the Connection.at field as the "as of" timestamp for judging how current a SYNCED status is
- Add a how-to guide for verifying a bank account and retrieving ACH account and routing numbers for payments
- Document the themeMode option for Quiltt.connect and Quiltt.reconnect in the Connector JavaScript API reference
- Add a tutorial on working with enriched transaction data, showing how to enable an enrichment provider and query categories, merchant names, and logos via the GraphQL API
- Explain how Profiles are billed, including how empty and deleted Profiles count toward each billing period
- Add a top-level Guides section that organizes how-to content by developer job-to-be-done
- Move the Connector reconnect walkthrough into Guides as "Reconnect a broken bank connection", with a redirect preserving the old link
- Document the 502 Bad Gateway response returned when an upstream provider is temporarily unavailable, and recommend retrying with backoff
- Reclassify task-oriented tutorials as Guides, moving GraphQL tooling, account statements, transaction enrichment, transaction sync, and account verification into the Guides section
- Redirect the old tutorial URLs to their new Guides locations so existing links keep working
- Explain in the connection troubleshooting reference that a connection can re-enter ERROR_REPAIRABLE repeatedly for some institutions and providers, and link it to the reconnection guidance
- Align the Connector landing page title and meta description with search keywords
- Rewrite the meta descriptions on the Finicity, Akoya, Plaid, and MX connectivity integration pages so each is unique and search-optimized
- Align the Get Started page title and description with the open banking API keyword strategy so the docs entry point ranks for the terms developers search