<?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: Moving from SIM to Accept Hosted in Integration and Testing</title>
    <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/Moving-from-SIM-to-Accept-Hosted/m-p/58723#M33338</link>
    <description>&lt;P&gt;To use &lt;SPAN&gt;Accept Hosted, b&lt;/SPAN&gt;asically you would call the API method getHostedPaymentPageRequest by posting XML similiar to what is below to :&amp;nbsp;&lt;/P&gt;&lt;P&gt;Sandbox URL: &lt;A href="https://apitest.authorize.net/xml/v1/request.api" target="_blank"&gt;https://apitest.authorize.net/xml/v1/request.api&lt;/A&gt;&lt;/P&gt;&lt;P&gt;or&amp;nbsp;&lt;/P&gt;&lt;P&gt;Production URL: &lt;A href="https://api.authorize.net/xml/v1/request.api&amp;nbsp;" target="_blank"&gt;https://api.authorize.net/xml/v1/request.api&amp;nbsp;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;as the case maybe.&lt;/P&gt;&lt;PRE&gt;&amp;lt;getHostedPaymentPageRequest xmlns="AnetApi/xml/v1/schema/AnetApiSchema.xsd"&amp;gt;
	&amp;lt;merchantAuthentication&amp;gt;
		&amp;lt;name&amp;gt;YOUR_API_LOGIN&amp;lt;/name&amp;gt;
		&amp;lt;transactionKey&amp;gt;YOUR_TRANSACTION_KEY&amp;lt;/transactionKey&amp;gt;
	&amp;lt;/merchantAuthentication&amp;gt;
	&amp;lt;transactionRequest&amp;gt;
		&amp;lt;transactionType&amp;gt;authCaptureTransaction&amp;lt;/transactionType&amp;gt;
		&amp;lt;amount&amp;gt;25.00&amp;lt;/amount&amp;gt;
	&amp;lt;/transactionRequest&amp;gt;
	&amp;lt;hostedPaymentSettings&amp;gt;
		&amp;lt;setting&amp;gt;
			&amp;lt;settingName&amp;gt;hostedPaymentBillingAddressOptions&amp;lt;/settingName&amp;gt;
			&amp;lt;settingValue&amp;gt;{"show": true, "required":true}&amp;lt;/settingValue&amp;gt;
		&amp;lt;/setting&amp;gt;
		&amp;lt;setting&amp;gt;
			&amp;lt;settingName&amp;gt;hostedPaymentButtonOptions&amp;lt;/settingName&amp;gt;
			&amp;lt;settingValue&amp;gt;{"text": "Pay"}&amp;lt;/settingValue&amp;gt;
		&amp;lt;/setting&amp;gt;
		&amp;lt;setting&amp;gt;
			&amp;lt;settingName&amp;gt;hostedPaymentReturnOptions&amp;lt;/settingName&amp;gt;
			&amp;lt;settingValue&amp;gt;{"url":"https://yoursite.com/good","urlText":"Continue","cancelUrl":"https://yoursite.com/cancel","cancelUrlText":"Cancel"}&amp;lt;/settingValue&amp;gt;
		&amp;lt;/setting&amp;gt;
	&amp;lt;/hostedPaymentSettings&amp;gt;
&amp;lt;/getHostedPaymentPageRequest&amp;gt;&lt;/PRE&gt;&lt;P&gt;The response from the API contains a form-validation token. Using this token returned from the API you can embed the payment form or redirect the customer to the payment form by sending an HTML form post to &lt;A href="https://accept.authorize.net/payment/payment" target="_blank"&gt;https://accept.authorize.net/payment/payment&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Once your customer fills in the payment form, the transaction is processed when the user submits the form, your customer then returns to your site, where you can display a result page based on the url followed or the response information sent. More details at&amp;nbsp;:&amp;nbsp;&lt;A href="https://developer.authorize.net/api/reference/features/accept_hosted.html" target="_self"&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;Another option is &lt;A href="https://developer.authorize.net/api/reference/features/acceptjs.html" target="_self"&gt;Accept.js,&amp;nbsp;&lt;/A&gt;which provides the flexibility of your own design and forms and also helps minimize your PCI compliance because it sends payment data directly to Authorize.Net via a nonce (number used once or number once). Your server application then uses the nonce to replace the payment details in standard Authorize.Net API calls.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 07 Jul 2017 18:06:55 GMT</pubDate>
    <dc:creator>NexusSoftware</dc:creator>
    <dc:date>2017-07-07T18:06:55Z</dc:date>
    <item>
      <title>Moving from SIM to Accept Hosted</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/Moving-from-SIM-to-Accept-Hosted/m-p/58721#M33336</link>
      <description>&lt;P&gt;I have a SIM payment system and am looking for documentation or direction on how to migrate it to Accept Hosted. &amp;nbsp;Since this is a direct replacement, it seems like there should be some form of migration guide out there, and I was hoping one of you might have come across it. Thanks in advance!&lt;/P&gt;</description>
      <pubDate>Fri, 07 Jul 2017 15:31:56 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/Moving-from-SIM-to-Accept-Hosted/m-p/58721#M33336</guid>
      <dc:creator>matdave</dc:creator>
      <dc:date>2017-07-07T15:31:56Z</dc:date>
    </item>
    <item>
      <title>Re: Moving from SIM to Accept Hosted</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/Moving-from-SIM-to-Accept-Hosted/m-p/58722#M33337</link>
      <description>&lt;P&gt;I just went through this migration as well. I didn't find any direct 1:1 migration documentation. I used the accept js documentation:&amp;nbsp;&lt;A href="https://developer.authorize.net/api/reference/features/acceptjs.html" target="_blank"&gt;https://developer.authorize.net/api/reference/features/acceptjs.html&lt;/A&gt; and implemented the parts of it that I needed. Accept is pretty straight forward to implement.&lt;/P&gt;</description>
      <pubDate>Fri, 07 Jul 2017 17:52:42 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/Moving-from-SIM-to-Accept-Hosted/m-p/58722#M33337</guid>
      <dc:creator>Devin</dc:creator>
      <dc:date>2017-07-07T17:52:42Z</dc:date>
    </item>
    <item>
      <title>Re: Moving from SIM to Accept Hosted</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/Moving-from-SIM-to-Accept-Hosted/m-p/58723#M33338</link>
      <description>&lt;P&gt;To use &lt;SPAN&gt;Accept Hosted, b&lt;/SPAN&gt;asically you would call the API method getHostedPaymentPageRequest by posting XML similiar to what is below to :&amp;nbsp;&lt;/P&gt;&lt;P&gt;Sandbox URL: &lt;A href="https://apitest.authorize.net/xml/v1/request.api" target="_blank"&gt;https://apitest.authorize.net/xml/v1/request.api&lt;/A&gt;&lt;/P&gt;&lt;P&gt;or&amp;nbsp;&lt;/P&gt;&lt;P&gt;Production URL: &lt;A href="https://api.authorize.net/xml/v1/request.api&amp;nbsp;" target="_blank"&gt;https://api.authorize.net/xml/v1/request.api&amp;nbsp;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;as the case maybe.&lt;/P&gt;&lt;PRE&gt;&amp;lt;getHostedPaymentPageRequest xmlns="AnetApi/xml/v1/schema/AnetApiSchema.xsd"&amp;gt;
	&amp;lt;merchantAuthentication&amp;gt;
		&amp;lt;name&amp;gt;YOUR_API_LOGIN&amp;lt;/name&amp;gt;
		&amp;lt;transactionKey&amp;gt;YOUR_TRANSACTION_KEY&amp;lt;/transactionKey&amp;gt;
	&amp;lt;/merchantAuthentication&amp;gt;
	&amp;lt;transactionRequest&amp;gt;
		&amp;lt;transactionType&amp;gt;authCaptureTransaction&amp;lt;/transactionType&amp;gt;
		&amp;lt;amount&amp;gt;25.00&amp;lt;/amount&amp;gt;
	&amp;lt;/transactionRequest&amp;gt;
	&amp;lt;hostedPaymentSettings&amp;gt;
		&amp;lt;setting&amp;gt;
			&amp;lt;settingName&amp;gt;hostedPaymentBillingAddressOptions&amp;lt;/settingName&amp;gt;
			&amp;lt;settingValue&amp;gt;{"show": true, "required":true}&amp;lt;/settingValue&amp;gt;
		&amp;lt;/setting&amp;gt;
		&amp;lt;setting&amp;gt;
			&amp;lt;settingName&amp;gt;hostedPaymentButtonOptions&amp;lt;/settingName&amp;gt;
			&amp;lt;settingValue&amp;gt;{"text": "Pay"}&amp;lt;/settingValue&amp;gt;
		&amp;lt;/setting&amp;gt;
		&amp;lt;setting&amp;gt;
			&amp;lt;settingName&amp;gt;hostedPaymentReturnOptions&amp;lt;/settingName&amp;gt;
			&amp;lt;settingValue&amp;gt;{"url":"https://yoursite.com/good","urlText":"Continue","cancelUrl":"https://yoursite.com/cancel","cancelUrlText":"Cancel"}&amp;lt;/settingValue&amp;gt;
		&amp;lt;/setting&amp;gt;
	&amp;lt;/hostedPaymentSettings&amp;gt;
&amp;lt;/getHostedPaymentPageRequest&amp;gt;&lt;/PRE&gt;&lt;P&gt;The response from the API contains a form-validation token. Using this token returned from the API you can embed the payment form or redirect the customer to the payment form by sending an HTML form post to &lt;A href="https://accept.authorize.net/payment/payment" target="_blank"&gt;https://accept.authorize.net/payment/payment&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Once your customer fills in the payment form, the transaction is processed when the user submits the form, your customer then returns to your site, where you can display a result page based on the url followed or the response information sent. More details at&amp;nbsp;:&amp;nbsp;&lt;A href="https://developer.authorize.net/api/reference/features/accept_hosted.html" target="_self"&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;Another option is &lt;A href="https://developer.authorize.net/api/reference/features/acceptjs.html" target="_self"&gt;Accept.js,&amp;nbsp;&lt;/A&gt;which provides the flexibility of your own design and forms and also helps minimize your PCI compliance because it sends payment data directly to Authorize.Net via a nonce (number used once or number once). Your server application then uses the nonce to replace the payment details in standard Authorize.Net API calls.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 07 Jul 2017 18:06:55 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/Moving-from-SIM-to-Accept-Hosted/m-p/58723#M33338</guid>
      <dc:creator>NexusSoftware</dc:creator>
      <dc:date>2017-07-07T18:06:55Z</dc:date>
    </item>
  </channel>
</rss>

