Link to this section#Environments
An Environment serves as an isolated container for your Profiles and associated data. Each Environment has its own Integrations and you can have as many Environments as your use-case requires. There are three Environment modes:
|No||Unlimited mock operations, suitable for local development and automated testing.|
|No||Limited live operations, suitable for staging and QA use-cases.|
|Yes||Unlimited live operations, suitable for production use.|
Link to this section#Profiles
A Profile represents an individual end-user associated with an Environment. In addition to financial data each 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 with the Quiltt Connector, or for compliance requirements mandated by one of your integrations, such as KYC.
You can request ephemeral Session tokens to access the Profile GraphQL API and the Quiltt Connector for a given Profile.
While all customer data is encrypted at rest, Quiltt automatically 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, Pave and others.
Link to this section#Connections
A Connection represents the data source for a Profile's accounts, transactions and other data. Connections are created when a user authenticates into their financial institution and are associated to an upstream record like a Plaid "Item" or MX "member".
Connections support a variety of features, #(Connections):
- Account Verification
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.