You're missing the point.
While the user is entering the credit card number, there's a chance that someone can intercept and steal the CC.
You can easily solve this problem by putting the credit card form inside your own iframe. :)
While the user is entering the credit card number, there's a chance that someone can intercept and steal the CC.
You can easily solve this problem by putting the credit card form inside your own iframe. :)
The rule should be: if your app has a credit card form under its own banner, the whole thing is implicated for PCI assessments. But that's not the rule.
As part of Compliance, the merchant attests that he never handles the cardholder information, and that closes off huge portions of it.