What are Applications?
An Application represents an external software system or component that will be integrated with the Basis Theory API. Basis Theory’s Applications do not imply any specific implementation type or technology. Applications could be a native app on a mobile device, a single-page application in a browser, or a regular web application that executes on a server or in a serverless environment.
How It Works
Applications within Basis Theory have the following properties and characteristics:
The name of your Application gives you clarity on what context it is being used for, for example, “Acme Billing App” or “Acme Mobile App”.
- Used with a traditional web application that runs their application logic primarily on a server or in a serverless environment (e.g. NodeJs, .NET, Java, or Ruby). This application type has the most permissions available as the API Key will be private and secured within a server environment.
- Used for Browser, Mobile, or Desktop applications running natively on a device (e.g. iOS, Android, Windows, etc) where the application is collecting the data itself and protecting with Basis Theory via an API call. Applications created with this type have limited permissions to enable using the API Key in publicly available code.
Each Application Type has different levels of permission available for the application. These permissions range from enabling the ability to Create Tokens, Use Tokens with our Proxy or Reactors, all the way to the ability to create new applications. You can find a detailed list of all of our permissions for all of our Application Types here.
Your Application’s API Key is used to authenticate your systems to the Basis Theory platform. The API Key can be used to make authenticated requests to our API directly, using Hosted Elements, or using the Basis Theory SDK. These API Keys follow a format similar to
Common Use Cases
Each system accessing Basis Theory
A common use-case for Basis Theory is to grant multiple systems access to the same data or a subset of the data that is being secured in a Tenant. This could mean that one system is allowed to only collect the data, one system is allowed to view the data, and the last system is only allowed to Proxy the data to a 3rd party but never access the raw data.
Enable partners to use data secured by Basis Theory
Often, businesses need to grant their partners access to their sensitive data — traditionally, these businesses would just export the needed data and send it over to their partner. With Basis Theory Applications, a business creates an Application with permissions restricted to ONLY the data that partner needs. In some cases, businesses will not allow the partner to see the raw data, but rather allow them to Proxy the data to another API or run serverless functions with Reactors.
Manage Basis Theory assets with Infrastructure as Code
The Management application type allows the Basis Theory platform to be configured entirely via our API. This enables engineers to write scripts to set up new Applications or Manage your Custom Reactor Formulas all without logging into our Portal UI.
Interested in using IaC (Infrastructure as Code) tooling such as Terraform to configure Basis Theory? Reach out!
How do I pick between the Elements and Client-side Application Types?
If your system is using our Elements to collect data via Inputs on your website, you will need to use our Elements application type. When you’re collecting the data yourself on a client-side application (Mobile App, Desktop App, or Browser-based app) you’ll want to use a Client-side application type.