Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No SAQ A solution (IFrame or full redirect), only SAQ A-EP solutions #749

Open
joshcodes opened this issue Mar 10, 2015 · 0 comments
Open

Comments

@joshcodes
Copy link

As of October of 2014 the SSC has clarified SAQ-A vs SAQ-A-EP, it now seems that SAQ-A is ok for iFrame and full Redirect integrations but SAQ-A-EP is required for Direct Post or Transparent Redirect style implementations. All of Balanced Payment's systems known to me use Direct Post (requiring SAQ A-EP). There is currently not anyway to do full redirect or IFrames with Balanced Payments per:

[13:29] As of October of 2014 the SSC has clarified SAQ-A vs SAQ-A-EP, it now seems that SAQ-A is ok for iFrame and full Redirect integrations but SAQ-A-EP is required for Direct Post or Transparent Redirect style implementations. All of Balanced Payment's systems known to me use Direct Post (requiring SAQ A-EP). Is there anyway to do full redirect or IFrames?
[13:33] @ras__ joshcodes: not at the moment, but you can start a github issue: https://github.com/balanced/balanced-api/issues

https://www.pcicomplianceguide.org/saq-a-vs-a-ep-what-e-commerce-merchants-service-providers-need-to-know-now/
http://www.ippayments.com/direct-post-transparent-redirect-versus-iframe-for-pci-dss-scope-reduction/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant