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
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/