Hyperswitch Account Structure
Last updated
Was this helpful?
Last updated
Was this helpful?
Adapting the right account structure while setting up Hyperswitch for your business is one of the most crucial steps. Hyperswitch allows you to choose different account structures based on your business needs-
Whether you are a business with multiple product lines and business units within each line, or a marketplace with multiple sub-merchants, each having multiple business units.
Whether you want to accept payments at the business level, business unit level, or allow your sub-merchants to accept payments on their own.
You can manage it all via Hyperswitch.
This is enabled by Hyperswitch’s three-level user hierarchy: Organization, Merchant Account, and Profile, enabling businesses to configure and optimize payment flows while maintaining visibility across all merchants, sub-merchants, and business units.
Once a user signs up on the Hyperswitch Control Centre, they need to create an organization. By default, one merchant account and one profile are created for the organization, and the user is assigned the role of organization Admin. They can further invite team members on the basis of the applicable roles.
Multiple Merchant Accounts: Organization admins can create and manage multiple merchant accounts under one organization for different business lines or sub-merchants, with each merchant account having its own API keys.
Multiple Profiles under each Merchant: A merchant account can set up multiple profiles for each individual business unit. Profiles are the most granular levels in Hyperswitch, and every payment via Hyperswitch is mandatorily and exclusively tagged with a profile.
Easy Checkout for Return Customers: Hyperswitch allows an organization to store customer cards while enabling sub-merchants to access them, and for payments handled by a merchant, only the cards relevant to that merchant are visible.
Additionally, payments can be tokenized (both network and PSP) at the sub-merchant level, ensuring that sub-merchants or platforms don't need to worry about PCI compliance.
Hyperswitch also enables organizations to accept payments on behalf of their sub-merchant using one of profiles of sub-merchant, without allowing the organization to access the connector credentials used with the profile.
Routing & Connectors Configuration: If a business has connector credentials for each of its business units, they can configure them to their respective profiles and set up routing rules for each profile.
If the merchant wants to accept payments at the merchant level with its own set of connector credentials, it can create another profile and configure its connectors with that profile.
Exhaustive Data Visibility: Payment lists, analytics, and teams are segregated at the profile, merchant, and organization levels. Hyperswitch allows top-down access to data; each level can access the payments data of the levels below it by switching into their levels, not vice versa.
Each level can get an aggregated view of the payment transactions of all the sub-levels beneath it. Also, Using the global search within
Hyperswitch Control Centre, you can search for any data across any merchant account or profile of which the user is a part.
