Quiltt Logo


The Quiltt Connector is an embeddable UI component that lets you access a complete, context-rich financial picture of your end-user, without writing any integration code.

The Connector is built on top of the Profile GraphQL API, and comes pre-integrated with leading bank data networks like Plaid, MX, and Akoya.

In addition to creating connections to data providers, the Connector can be configured to authenticate, enroll and redirect end-users users to create the optimal onboarding experience for your end-users.

Link to this section#How to Integrate

The Connector can be embedded and controlled in several ways; choose the approach that best fits your use-case and technology.

  • HTML for the simplest web integration experience using plain HTML.
  • React SDK for web integrations with React.js applications, using modern React Components and Hooks and written in TypeScript.
  • React Native SDK for cross-platform integrations with React Native applications.
  • Flutter SDK for cross-platform integrations with Flutter applications.
  • iOS SDK for native iOS application integrations.
  • Android SDK for native Android application integrations.

Additionally, a powerful JavaScript API is available for programmatic access to the Connector, such as launching, passing Session tokens, and setting up event callbacks.

Link to this section#Customization

Each Connector's flow can be customized to create the perfect experience for your product. The following steps are generally available and can be configured in the Quiltt Dashboard.

Link to this section#Land

Land allows you to present a welcome screen with your logo and copy. This step is used in combination with the Authenticate step, and will be skipped for end-users pre-authenticated via Session token.

Link to this section#Authenticate

Authenticate allows users unauthenticated users to sign up or sign into your Connector using an OTP code. Currently email and SMS-based authentication methods are supported out of the box.

This supports using your Connector on public websites, and can be used to streamline local development and testing.

Link to this section#Enroll

Enroll allows you to collect additional onboarding information from the end-user, such as their legal name, address, phone number, and more.

This information gets persisted on the user's Profile to be retrieved via API or to power the Authenticate step.

Link to this section#Connect

Connect allows you to create a Connections to an end-user's financial institution, repair broken connections or request new features on existing Connections.

This is where you select which Account Aggregation providers your Connector will support, and what data features you want to get access to.

Link to this section#Features

Currently Connect supports creating Connections with the following data features:

  • Account Numbers: Verify account numbers to support money movement operations.
  • Account Owners: Verify account owner information.
  • Balances: Access account balances.
  • Investments: Access investment holdings and transactions (MX transactions coming soon).
  • Liabilities: Access additional information on credit cards, student loans and mortgages.
  • Transactions: Access deep transaction history.

Features and Institution Coverage

The Connector guarantees that successful sessions will fulfill all the requested features. This means that adding more Connector features limits the list of institutions available to the end-user to only those institutions that support all the configured features.

This means that a Connector with only the Transactions feature will provide maximum coverage, while one configured with multiple features will show fewer available institutions.

Additionally, please note that depending on the provider, some features may be automatically provisioned "for free", while others may incur usage fees. For example, the Transactions feature will automatically give you Balances, Investments and Liabilities for MX Connections and Balances for Plaid Connections. This means that you should only configure Connect with the smallest number of features your use-case requires. For more information refer to your Quiltt agreement or contact Quiltt Support.

Once a Connection is created, you can access the currently-provisioned features using the Connection.features field in GraphQL or via Connection webhooks. To request additional features, launch a Connector in Reconnect mode by supplying the connectionId to the SDK.

Link to this section#Redirect

Redirect allows you to redirect the end-user to a URL of your choice after the completion of the flow. This overrides the standard behavior of the Connector, which is to fire the exited.successful event and close.

Note that redirecting invalidates the current Session token, but you can configure Redirect to pass a new Session token to your URL, as a query parameter.

Link to this section#Kitchen Sink Demo

Click the button below to see the embedded Connector in action:

This Connector is enabled with the Land, Authenticate, Enroll, Connect and Redirect steps.