Terms

To help keep us all on the same page we've included a list of terms that are useful to know when going through the documentation.

Application

An application is used to create a boundary of permissions, role and context for authentication. Its encouraged to use applications in order to enact the principle of least privilege between the different systems that engage with Authvia.

Common application use cases would be.

• Payment experience embedded into another system where a merchant/account is creating payment conversations.
• An integration between an invoicing system, and Authvia's API's, to subscribe to webhooks and make API calls in order to add Authvia products to the invoicing system.
• An ISV system creating merchant accounts in Authvia to make Authvia products available to the merchants.

Even if the same platform engaged in all of the above at the same time, we would encourage a different application for each use case as the scopes required for each would be different.

Tenant (Partner)

A service provider or platform, that will be offering services or products to merchants. Authvia has Tenancy API's that can be used to model these relationships within the tenancy, with appropriate data and authentication boundaries to ensure isolation across sub partners, and merchants.

Merchant (Account)

Best thought of as an 'account' that will be directly using the products offered by Authvia in order to engage directly with customers/consumers. Volume can vary widely from different merchants, however the Authvia products they use will be to engage with a customer.