Reply
Highlighted
Member
Posts: 1
Registered: ‎07-07-2017
Accepted Solution

Moving from SIM to Accept Hosted

I have a SIM payment system and am looking for documentation or direction on how to migrate it to Accept Hosted.  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!


Accepted Solutions
Highlighted
Solution
Accepted by Aaron (All Star)
‎07-11-2017 01:13 PM
Posts: 427
Topics: 0
Kudos: 88
Blog Posts: 0
Ideas: 0
Solutions: 34
Registered: ‎04-28-2017

Re: Moving from SIM to Accept Hosted

[ Edited ]

To use Accept Hosted, basically you would call the API method getHostedPaymentPageRequest by posting XML similiar to what is below to : 

Sandbox URL: https://apitest.authorize.net/xml/v1/request.api

or 

Production URL: https://api.authorize.net/xml/v1/request.api 

as the case maybe.

<getHostedPaymentPageRequest xmlns="AnetApi/xml/v1/schema/AnetApiSchema.xsd">
	<merchantAuthentication>
		<name>YOUR_API_LOGIN</name>
		<transactionKey>YOUR_TRANSACTION_KEY</transactionKey>
	</merchantAuthentication>
	<transactionRequest>
		<transactionType>authCaptureTransaction</transactionType>
		<amount>25.00</amount>
	</transactionRequest>
	<hostedPaymentSettings>
		<setting>
			<settingName>hostedPaymentBillingAddressOptions</settingName>
			<settingValue>{"show": true, "required":true}</settingValue>
		</setting>
		<setting>
			<settingName>hostedPaymentButtonOptions</settingName>
			<settingValue>{"text": "Pay"}</settingValue>
		</setting>
		<setting>
			<settingName>hostedPaymentReturnOptions</settingName>
			<settingValue>{"url":"https://yoursite.com/good","urlText":"Continue","cancelUrl":"https://yoursite.com/cancel","cancelUrlText":"Cancel"}</settingValue>
		</setting>
	</hostedPaymentSettings>
</getHostedPaymentPageRequest>

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 https://accept.authorize.net/payment/payment.

 

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 : https://developer.authorize.net/api/reference/features/accept_hosted.html

 

Another option is Accept.js, 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.

 

Powered by NexWebSites.com -
Certified Authorize.net developers

View solution in original post


All Replies
Highlighted
Contributor
Posts: 34
Registered: ‎09-29-2016

Re: Moving from SIM to Accept Hosted

I just went through this migration as well. I didn't find any direct 1:1 migration documentation. I used the accept js documentation: https://developer.authorize.net/api/reference/features/acceptjs.html and implemented the parts of it that I needed. Accept is pretty straight forward to implement.

Highlighted
Solution
Accepted by Aaron (All Star)
‎07-11-2017 01:13 PM
Posts: 427
Topics: 0
Kudos: 88
Blog Posts: 0
Ideas: 0
Solutions: 34
Registered: ‎04-28-2017

Re: Moving from SIM to Accept Hosted

[ Edited ]

To use Accept Hosted, basically you would call the API method getHostedPaymentPageRequest by posting XML similiar to what is below to : 

Sandbox URL: https://apitest.authorize.net/xml/v1/request.api

or 

Production URL: https://api.authorize.net/xml/v1/request.api 

as the case maybe.

<getHostedPaymentPageRequest xmlns="AnetApi/xml/v1/schema/AnetApiSchema.xsd">
	<merchantAuthentication>
		<name>YOUR_API_LOGIN</name>
		<transactionKey>YOUR_TRANSACTION_KEY</transactionKey>
	</merchantAuthentication>
	<transactionRequest>
		<transactionType>authCaptureTransaction</transactionType>
		<amount>25.00</amount>
	</transactionRequest>
	<hostedPaymentSettings>
		<setting>
			<settingName>hostedPaymentBillingAddressOptions</settingName>
			<settingValue>{"show": true, "required":true}</settingValue>
		</setting>
		<setting>
			<settingName>hostedPaymentButtonOptions</settingName>
			<settingValue>{"text": "Pay"}</settingValue>
		</setting>
		<setting>
			<settingName>hostedPaymentReturnOptions</settingName>
			<settingValue>{"url":"https://yoursite.com/good","urlText":"Continue","cancelUrl":"https://yoursite.com/cancel","cancelUrlText":"Cancel"}</settingValue>
		</setting>
	</hostedPaymentSettings>
</getHostedPaymentPageRequest>

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 https://accept.authorize.net/payment/payment.

 

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 : https://developer.authorize.net/api/reference/features/accept_hosted.html

 

Another option is Accept.js, 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.

 

Powered by NexWebSites.com -
Certified Authorize.net developers