#Meta Krypto
frank zodiac
limber quail
I get your point, but what is standard Payment Request API exactly?
quick owl
this is the standard that browsers have to follow to make web payment. I believe stripe-js just wrap calls to this (and add some stripe specific hooks within it)
Along side this standard payment request API, there are 'standard' Apple Pay and Google Pay, which I also want to use these, instead of using stripe for the frontend. The reason as said above, stripe-js use many implicit call which sometime hard to understand the full detail of what was going on
limber quail
That isn't Stripe API and TBH I am not familiar with it. But the point is you shouldn't let the card information ever reach your server or your client code, or you will be exposed to PCI Compliance
Instead stripe.js will provide a secure context which you as a merchant can't access those PII, and you are safe from PCI Compliance
stripe.js is essential
quick owl
yes, I understand that. That is why I can follow the Payment Request API, it is designed for not leaking the card information
browsers implement natively these standards
limber quail
Still you will fall into the "API Direct" classify on https://stripe.com/docs/security/guide#validating-pci-compliance, meaning you would need to 40+ pages of SAQ-D every year
I would advise against it. Using stripe.js has much more benefits