Managed Service Provider Configuration Guidelines - Kill Bill | HS #5601
shaun-forgie
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have been reviewing the documentation provided about connecting subscription management systems with Hyperswitch which is found here https://docs.hyperswitch.io/features/payment-flows-and-management/subscriptions
There are a number of Hyperswitch configuration guidelines that need to be clarified in order to understand how best to map Billing Tenants in the subscription system to the correct Organisation/Merchant/Business Profile entity in the HS hierarchy.
If a managed service provider (MSP) is hosting both subscription and payment orchestration systems they are performing the role of "Platform Operator" and have the responsibility to administer and maintain the underlying infrastructure and payment network connectivity which in some cases may require commercial pairing agreements that are maintained independently of the tenants (billing && payment) being hosted on a given instance of the platform.
In the case of a MSP hosted platform we will need to establish suggested guidelines for the best way to handle the mappings | synchronisation of Billing tenancies with the appropriate HS administrative entity. This will require the Platform Operator role to be formally defined and mapped into the HS heirarchy.
Beta Was this translation helpful? Give feedback.
All reactions