Link to this section#Environments
An Environment serves as an isolated container for your deployments, users and integrations. 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#Deployments
A Deployment is the primary interface to interact with a Quiltt environment. Each environment will typically be provisioned with one or more deployments, depending on your use-case.
Each API deployment has an API Secret which can be used to call the Auth API and the Admin API within the context of the deployment's environment.
A User represents an individual end-user associated with an environment, and can be issued ephemeral Session Tokens to access the GraphQL API and the Quiltt widget.
Each user has a profile which contains important information about the user, such as their phone, email, names, birthday, address and more. Profile fields can be used to support compliance requirements mandated by one of your integrations, such as KYC.
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 provisioned for a given environment.
Currently, Quiltt supports integrations with Plaid, Spade, Stripe and several other 3rd parties.
Integrations can be managed in the Dashboard and be configured to use your own API keys or API keys provided by Quiltt.