Questions regarding payment routing and hyperswitch hosted version

[rongjc]

Hi team, we are trying to evaluate hypwerswitch as a payment middleware for our company use. Here are two questions I have

1. How does payment routing work? Say I set if currency = USD, payment processor = dummy_paypal only. I would expect this will disable all other payment methods in the checkout flow, but I still see google play and other flows(I am using the web demo app).
2. I noticed for free version and hyperswitch hosted version, the payment connectors are significant different. Wondering what are the available ones? we do have a few big ones missing from the current free version such as boku, payermax and so on
3. Also, I noticed routing rule can't be changed or deleted, you can only deactivate it and create a new one, that is quite inconvenient as we may have complex routing rules. And there can only be one active routing rule？

[tinu-hareesswar]

Hi @rongjc, clarifying on your queries below:

1. The Payment Routing handles the logic for selecting the most optimal processor based on the given payment request and customer chosen payment method. In the example that you've highlighted you are able to see Google Pay on the checkout because it has an active processor for you account that can process Google Pay payments. The rule you've set translates to say all USD payments have to go via dummy_paypal as a processor. (paypal as a payment method is different from paypal the payment processor). Payment Methods are disabled on the checkout either if there no active processors to support it or if an explicit configuration has been set to restrict it (https://app.hyperswitch.io/dashboard/configure-pmts)

2. The production environment has a subset of the processors available on the sandbox environment based on the flows tested. You can check this page (https://hyperswitch.io/pm-list) to know the availability of the processors in different environments.

3. The deletion is restricted for audit purposes to have a reference of the rules used for historical payments. There can be only one active routing configuration at a time, but you can keep adding multiple rules to the same configuration by the selecting the Add Rule option on the top right of the rule box while setting it up on Dashboard. Adding reference image below.
   

[AnandKGanesh]

Hi @rongjc - We shape our product roadmap based on the requests coming from organisations looking to adopt the solution. We would be able to add new integrations and features required for your use-case. Happy to review your feedback on the existing features as well.

Could we connect next week to discuss more about your implementation use cases and issues that you're trying to address ?

[rongjc]

Hi Anand, Happy to discuss that. What's the best way to reach you so that I can bring this offline? Thank you!

…

On Fri, Feb 21, 2025 at 7:29 PM AnandKGanesh ***@***.***> wrote: Hi @rongjc <https://github.com/rongjc> - We shape our product roadmap based on the requests coming from organisations looking to adopt the solution. We would be able to add new integrations and features required for your use-case. Happy to review your feedback on the existing features as well. Could we connect next week to discuss more about your implementation use cases and issues that you're trying to address ? — Reply to this email directly, view it on GitHub <#7329 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABMO6P3DZTRAI3HLDW3BZAL2Q4EYVAVCNFSM6AAAAABXQYWEESVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMRXGUYDQNY> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[AnandKGanesh]

Please send me an email at - anand.ganesh@juspay.in
I'll setup time for us to connect