Multiple Authorize.net accounts via Payment Method Restrictions

In a store I have I am trying to process payments to 2 different Authorize.net accounts. One account is for orders where sales tax is charged.

The store sells normal merchandise, but also "sells" donations and sponsorships. The physical products are to be taxed and this money all goes to Account A. The donations and sponsorships are not taxed and go to Account B.

I can't find it now, but I had initially achieved this following instructions in an old forum post.

In HikaShop, in System->Payment methods, I added two instances of the Authorize.net payment plugin. They each have their own Login ID & API stuff. Let's call these Payment A and Payment B. Payment A has "Restrictions" set up with a minimum weight of 0.00001 and minimum volume of 0.00001. Payment B has a maximum weight of 0.00001 and maximum volume of 0.00001.

I swear I tested this and it was working when the store opened. But now (and for more than a month) it shows both payment methods at checkout. The physical products have weights & dimensions. The others do not. This doesn't even seem relevant, as both payment methods show regardless of what's in the cart. It seems like the restrictions are being ignored. I have tried adding minimums and maximums (instead of leaving them blank) but saw no change.

Am I missing something? Is there a better way to do this?

Hi Jerome, I am using HikaShop Business 3.1.1 [1706082210] in Joomla 3.7.5.

I have adjusted the restrictions in each payment method to only use a minimum weight of 0.00001 on one, and a maximum weight of 0.00001 on the other. Both options still appear at checkout, for an order with only physical products or only virtual products.

It seems like the restrictions aren't being factored in for some reason. They do show on the methods screen, as you see in my previous screenshot, but when I open a method to edit, the restrictions box is unchecked and hidden. I don't know if this is just a toggle for advanced setup, or if it's relevant..

Nicolas, I have adjusted the values in the restrictions to 0.001 and confirm this fixed my problem.

I must have tested it with fewer decimal places and then changed it later to the very small values.