Hacker News new | ask | show | jobs
by taurath 1767 days ago
Definitely a market need for this, having built one of those layers myself.

Are you planning to support saved payment methods across multiple providers? Thats always seemed like the touchiest area for me, especially since it would seemingly invalidate a lot of the fraud protection that payment providers use to keep lock-in.

1 comments

That's awesome that you built that layer yourself. If you're up for it, would love to connect and hear why you did so.

We're PCI compliant so can use saved payment methods across multiple providers, however in our case it does not invalidate the built-in fraud protection that providers use. Additionally, you could also use third party fraud providers at any point within your processing flow.

It was for a big subscription service and we needed to enable a lot of promotional capabilities and also keep payment provider costs low + be able to operationally switch over in high traffic times.

> however in our case it does not invalidate the built-in fraud protection that providers use

Thats pretty neat! Even Stripe Radar? My understanding was that used their client side fingerprinting when the card is inputted, but its been a little bit.