<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: How come Mobile SDK payment process is not subject to SAQ A-EP? in Integration and Testing</title>
    <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/How-come-Mobile-SDK-payment-process-is-not-subject-to-SAQ-A-EP/m-p/62438#M36760</link>
    <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.developer.cybersource.com/t5/user/viewprofilepage/user-id/23829"&gt;@cccedi&lt;/a&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Please refer to the &lt;A href="https://www.authorize.net/content/dam/authorize/documents/coalfire_authorize.net_accept_saq_eligibility_white_paper.pdf" target="_self"&gt;Authorize.Net Accept SAQ Elibitility White Paper&lt;/A&gt;&amp;nbsp;that covers this topic in detail.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Richard&lt;/P&gt;</description>
    <pubDate>Mon, 02 Apr 2018 14:50:24 GMT</pubDate>
    <dc:creator>RichardH</dc:creator>
    <dc:date>2018-04-02T14:50:24Z</dc:date>
    <item>
      <title>How come Mobile SDK payment process is not subject to SAQ A-EP?</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/How-come-Mobile-SDK-payment-process-is-not-subject-to-SAQ-A-EP/m-p/62436#M36758</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I observed that although both the payment processes of Mobile SDK and the Custom payment page (with Accept.js) allow the developers to create their own page to enter the card data, the Mobile SDK process is subject to SAQ A whereas the&amp;nbsp;&lt;SPAN&gt;&amp;nbsp;Custom payment page (with Accept.js)&amp;nbsp;is subject to SAQ A-EP&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Please let me know if i am missing something.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Apologies if I am missing something very obvious.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I understand that the mobile SDK is for native apps and&amp;nbsp;&amp;nbsp;&lt;SPAN&gt;Custom payment page (with Accept.js)&amp;nbsp;is for web site.&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;How does that affect it.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks in advance.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Ed&lt;/P&gt;</description>
      <pubDate>Mon, 02 Apr 2018 14:05:47 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/How-come-Mobile-SDK-payment-process-is-not-subject-to-SAQ-A-EP/m-p/62436#M36758</guid>
      <dc:creator>cccedi</dc:creator>
      <dc:date>2018-04-02T14:05:47Z</dc:date>
    </item>
    <item>
      <title>Re: How come Mobile SDK payment process is not subject to SAQ A-EP?</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/How-come-Mobile-SDK-payment-process-is-not-subject-to-SAQ-A-EP/m-p/62438#M36760</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.developer.cybersource.com/t5/user/viewprofilepage/user-id/23829"&gt;@cccedi&lt;/a&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Please refer to the &lt;A href="https://www.authorize.net/content/dam/authorize/documents/coalfire_authorize.net_accept_saq_eligibility_white_paper.pdf" target="_self"&gt;Authorize.Net Accept SAQ Elibitility White Paper&lt;/A&gt;&amp;nbsp;that covers this topic in detail.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Richard&lt;/P&gt;</description>
      <pubDate>Mon, 02 Apr 2018 14:50:24 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/How-come-Mobile-SDK-payment-process-is-not-subject-to-SAQ-A-EP/m-p/62438#M36760</guid>
      <dc:creator>RichardH</dc:creator>
      <dc:date>2018-04-02T14:50:24Z</dc:date>
    </item>
  </channel>
</rss>

