<?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 How to pick best payment solution for me in Integration and Testing</title>
    <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/How-to-pick-best-payment-solution-for-me/m-p/69231#M42297</link>
    <description>&lt;P&gt;Authorize.net documentation is quite good but I still would like some clarification on which solution I should implement.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am looking at this link:&lt;BR /&gt;&lt;A href="https://developer.authorize.net/api/reference/features/accept.html" target="_blank"&gt;https://developer.authorize.net/api/reference/features/accept.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;and believe I have narrowed my choice to "Accept Hosted" and "Accept Customer".&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I like the idea of having customer profiles so I thought I would use the "Accept Customer", but then I read this page:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://developer.authorize.net/api/reference/features/accept_hosted.html" target="_blank"&gt;https://developer.authorize.net/api/reference/features/accept_hosted.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;and it seems to also support customer profiles.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Anyway, my question is:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What are the key differences between "accept hosted" and "accept customer" that I should be aware of when choosing between them?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there one that Authorize.net is pusing more such that they are no likely to deprecate it?&lt;/P&gt;</description>
    <pubDate>Sat, 28 Sep 2019 19:18:42 GMT</pubDate>
    <dc:creator>pottmi</dc:creator>
    <dc:date>2019-09-28T19:18:42Z</dc:date>
    <item>
      <title>How to pick best payment solution for me</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/How-to-pick-best-payment-solution-for-me/m-p/69231#M42297</link>
      <description>&lt;P&gt;Authorize.net documentation is quite good but I still would like some clarification on which solution I should implement.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am looking at this link:&lt;BR /&gt;&lt;A href="https://developer.authorize.net/api/reference/features/accept.html" target="_blank"&gt;https://developer.authorize.net/api/reference/features/accept.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;and believe I have narrowed my choice to "Accept Hosted" and "Accept Customer".&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I like the idea of having customer profiles so I thought I would use the "Accept Customer", but then I read this page:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://developer.authorize.net/api/reference/features/accept_hosted.html" target="_blank"&gt;https://developer.authorize.net/api/reference/features/accept_hosted.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;and it seems to also support customer profiles.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Anyway, my question is:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What are the key differences between "accept hosted" and "accept customer" that I should be aware of when choosing between them?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there one that Authorize.net is pusing more such that they are no likely to deprecate it?&lt;/P&gt;</description>
      <pubDate>Sat, 28 Sep 2019 19:18:42 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/How-to-pick-best-payment-solution-for-me/m-p/69231#M42297</guid>
      <dc:creator>pottmi</dc:creator>
      <dc:date>2019-09-28T19:18:42Z</dc:date>
    </item>
  </channel>
</rss>

