Core Concepts
Link to this section#Environments
An Environment serves as an isolated container for your Profiles and associated data. Each Environment has its own Profiles, Connectors, Integrations and more. There are several types of Environments available, and you can set up as many Environments as your use-case requires:
| Mode | Description | Profile Limit |
|---|---|---|
PRODUCTION | Unlimited live operations for production use. | Unlimited |
DEVELOPMENT | Limited live operations for local development and preview use. | 50 |
SANDBOX | Limited mock operations for local development and preview use. | 50 |
TEST | Unlimited mock operations for automated testing/CI use. | Unlimited |
Link to this section#Profiles
A Profile represents an individual end-user associated with an Environment. In addition to financial data, a Profile can contain additional information such as email, phone, name, birthday, address and more. These fields can be used to allow end-users to authenticate themselves into the Quiltt Connector, or for compliance requirements mandated by one of your integrations, such as KYC.
The best way to interact with a profile is to create an ephemeral Session token to authenticate with the Profile GraphQL API and the Quiltt Connector.
While all customer data is encrypted at rest, Quiltt applies additional column-level encryption to sensitive Profile fields that may contain PII.
Link to this section#Integrations
An Integration represents a 3rd party provider configuration in a given Environment. This include services like Plaid, MX, FinGoal and others.
Integrations can be managed in the Dashboard and be configured to use your own API credentials or credentials provided and managed by Quiltt on your behalf. Check out our Integrations guide to learn more.
Link to this section#Connections
A Connection represents a data source for a Profile's accounts, transactions and other data. Connections are created when a user authenticates into their financial institution and are usually associated with an upstream record like a Plaid "Item" or an MX "Member".
Connections support a variety of features:
- Transactions
- Account Numbers
- Account Owners
The easiest way to create Connections is through the Quiltt Connector, which orchestrates the necessary feature-specific configurations for Plaid Link, MX Connect and more.
Link to this section#API Keys
An API Key allows you to programmatically interact with an Environment's data from a server or backend system. Each Environment can have multiple API Keys.