A standard Gr4vy deployment runs as a single tenant instance, each with its own 2 environments, sandbox and production. Within that environment, it’s possible to add additional sub-accounts called merchant accounts.
Each merchant account can be used to configure individual connections and flow rules, and process transactions with unique buyers, payment methods, and vaulted cards; routing transactions to distinct connections and using individual Flow rules and anti-fraud services to decline, route, or trigger 3DS.
By default, each environment in your instance is a single-tenant environment. That means that in your sandbox or production environment your company is the only merchant account using the resources of that instance, including the database, cloud servers, and more This creates a uniquely redundant system unique to Gr4vy.
Additional merchant accounts can be generated within an environment to support a few different scenarios.
Support for multiple merchant accounts in one instance is a premium feature. Please contact your account manager for pricing.
Once multiple merchant accounts have been enabled for your instance, log into your environment as an administrator and click the Settings icon in the top bar. You will be presented with the merchant account list. Click Add merchant to create a new account.
To create a new merchant account, provide a display name and a short ID. The display name is used to display a human-friendly name to the merchant account users in the dashboard. The ID is used as the unique identifier for the merchant account and can not be changed.
Deleting a merchant account is currently not possible as it may affect a lot of existing data. The ability to deactivate merchant accounts is rolling out at a later point.
To edit a merchant account, log into your environment as an administrator and click the Settings icon in the top bar. You will be presented with the merchant account list. Click on the three dots next to any merchant and select Edit merchant.
The display name can be changed at any time but the ID can not be changed as it’s the unique identifier used for API calls, internal reporting, and more.
In some cases, data from different merchants may be associated with the default merchant account because of a setup before multi-merchant was enabled. Please reach out to support for support migrating existing data to different merchant accounts.