4 ms·
i agree it's actually kind of bad that payment providers don't provide this page. todays technology could even render it on the webpage of the customer shop wit
by vectorEQ 9y ago
i agree it's actually kind of bad that payment providers don't provide this page. todays technology could even render it on the webpage of the customer shop without redirecting fully to another page (scrpt scr=paymentproviderscript.bla? or so?). If people have to maintain and host their own script it makes them horrible prone to attack. In which case i'd rather have a payment provider who needs to secure it than every customer of the payment provider (reduces attack surface). i think paypal does good by providing this passive system and other providers should follow it, and perhaps if it's not to their liking innovate in this line instead of dumping their issues to the customer shop.
- thinkloop 9y ago> scrpt scr=paymentproviderscript.bla? They can't do this because then the untrusted merchant has access to everything again. It needs to be sandboxed in a separate page so that the customer is talking directly with the processor, with SOP, cors, https, and simply not being able to intercept PII and payment information.
- celman 9y agoThis is already possible via iframes, check out braintree payments for example.