Welcome to the Quiltt product updates for October 2024, showcasing our recent advancements toward lowering technical barriers for individuals and teams building in financial services. Explore what’s new and how we're improving Quiltt, one update at a time.

Features

Account Owners

We now expose a normalized set of Account Owners data. This supersedes the now deprecated remote data on Connection with its own per owner data. The data is both cleaned and normalized across providers.

‍

1query {
2  accounts {
3    owners {
4      id
5      addresses {
6        city
7        country
8        countryCode
9        line1
10        line2
11        line3
12        postalCode
13        region
14        regionCode
15      }
16      emails {
17        address
18      }
19      names {
20        first
21        suffix
22        prefix
23        middle
24        last
25        full
26      }
27      phones {
28        number
29      }
30    }
31  }
32}
33

‍

Historical Priority Mode

On a per environment basis, we are able to skip the initial sync in favor of immediately doing the historical data sync. This does mean it will be slower for the first available data to be made available, but faster for all the data to be made available. This feature is in beta, contact support if you would like to try it out.

‍

Add Finicity Integration [Beta]

Introduce support for the Finicity as an aggregation provider. Docs with the test credentials can be found here.

Ntropy custom label hierarchies

Quiltt's Ntropy integration now supports uploading your own custom label hierarchies, allowing you to tailor the labels system to your unique use-case. See the Ntropy docs for more information. To enable custom labels for your integration, contact Quiltt support.

‍

ExistSuccess Metadata for Connector Redirects

You can now have Connector redirects include the metadata from the onExitSuccess Connector callback. For example, if you configure your Connector to redirect to https://myapp.com, after your end-user completes the Connector session, they will be redirected to https://myapp.com/?connectorId=CONNECTOR_ID&profileId=p_12345&connectionId=conn_12345 

You can enable this feature in a Connector's Exit Redirect settings. Redirect metadata can be used to: 

• Identify and greet the end-user who completed the redirect 
• Query or display relevant data for a newly created Connection 
• Display information based on the redirect source Connector

‍

‍

Improvements

• Added support for passing the Connector's ExitSuccess metadata to Exit Redirect URLs
• Balance Refreshes will retry with upstream for a maximum of 1 day before being dropped
• GraphQLsome text
  • Deprecatedsome text
    • Image._sourcename.
    • Search Arguments
  • Removed previously deprecated fields:some text
    • Profile.source and Profile.sources
    • Connection.source and Connection.sources
    • Transaction.logos
    • Institution.logos
    • Account.lastFourDigits
    • unused filters
• Documented Finicity's test credentials in the Finicity guide
• Track dirty field for connector name input
• Add the ability export Connection's API Keys
• Various Documentation Improvements
• Added MX as an auto-provisioned self-serve integration in Sandbox.
• Platform APIsome text
  • Improved error handling when invalid pagination inputs are supplied
•  Increase the syncing priority of Historical Data
• Fixed issue causing unnecessary delays in processing Pave Data
• Add the ability export Connection's API Keys

‍

‍

‍

Bug Fixes

• Fixed issue causing unnecessary delays in processing Pave Data
• Fixed an issue where the connector did not handle the Plaid error code PRODUCT_NOT_ENABLED
• Fixed handling of malformed MX API errors
• Fix rare issue with Pave rejecting some Plaid sandbox data
• Improve output of Connector errors in the Javascript console
• Fixed bug with Connector settings not being properly reset after changes
• Fixed edge case with parsing of Connector embed location
• Fixed issue with the institution router sometimes returning unroutable results

‍

‍