Ok, I see, so it's a bit different from Stripe's approach which to actually Ajax the cc# to stripe's server and return a token which the merchant then uses as a proxy for thee cc in normal API calls. I think they claim to obviate the self-exam for merchants despite it being materially similar to e transparent post.