It was a pain in the ass to find a surcharging API that was both compliant, and unbundled from a processing platform.
Yes, gateways will offer surcharging.
Yes, embedded payment platforms will offer surcharging.
But you have to use their entire platforms.
And naturally, none of the duopolies offer this logic because that would require that they actually do something.
Surcharging requires a BIN lookup (because you can’t charge debit or prepaid cards, so you need to know what card type it is).
Surcharging requires parsing state (or provincial) rules to make sure you don’t run afoul of the changing legislative landscape, not to mention the country-wide, arbitrary (and probably illegal) changes that come from the card duopolies themselves.
That’s what FeeRules has solved.
And it’s reached a level of confidence that a $6B processor is using it internally.
FeeRules tells us that they’re working on a Services Fee API as well, which will be helpful for industries that want to add convenience fees compliantly (and maybe some industries will learn that they’re in violation of the networks’ arbitrary rules in applying convenience fees).
We’ve seen larger merchants looking to bring this logic in-house over the years, so now there’s a digestible source to do so.
And a pretty nifty trick: you can integrate this to any software with their POS+ partnership.
Like literally any software: in theory you could use Square POS and still have integrated payments into Square that were not Square’s payments.
You asked, we delivered.
Enjoy.
Add comment