Well, hosted payment is not a new thing at all - so you iframe or link to a page you don't host which the customer uses - thus ensuring that card details don't hit your servers and don't give you a PCI surface.
This is a fairly logical extension, I would guess that the reason it hasn't caught on more is because a JS requirement has typically been a red flag in e-commerce - 3% of users not being able to pay you once they got to that point of a funnel could be seen as disaster. Interesting, because we're looking at mandating JS in our new developments (background: company I work for does a lot of high end e-commerce - we're specialists).
In theory it's a good idea (that side of it at least) but I don't know how security perception and customer acceptance rates will go.
Oh, of course. I completely forgot that there are some crazy people out there who browse without javascript. I was just jumping at the idea of reducing PCI compliance issues - I've had to deal with them and it's a huge project.
This is a fairly logical extension, I would guess that the reason it hasn't caught on more is because a JS requirement has typically been a red flag in e-commerce - 3% of users not being able to pay you once they got to that point of a funnel could be seen as disaster. Interesting, because we're looking at mandating JS in our new developments (background: company I work for does a lot of high end e-commerce - we're specialists).
In theory it's a good idea (that side of it at least) but I don't know how security perception and customer acceptance rates will go.