Using the Accept Customer Hosted Form

[bob_h]

We've been using SIM (I guess now renamed as Payment Form) for several years.  The BIG advantage of this method is that it falls under PCI SAQ A, which is easy to meet the requirements.  I would keep using SIM forever if the payment page was made responsive.  Not sure why that was so difficult and never got done.  

So, it looks like the "Accept Customer Hosted Form" (previously CIM Hosted?) is the place for me now, even though it is much more complex than SIM.  Still falls under SAQ A if I use a redirect or iframe.  

I copied the sample code from here: https://github.com/AuthorizeNet/accept-sample-app and it mostly works.  The part I'm having trouble with is the button labeled "Hosted Pay".  That button posts  to https://accept.authorize.net/payment/payment, and uses a method "getHostedPaymentPageRequest".  

Where is the documentation for  https://accept.authorize.net/payment/payment and getHostedPaymentPageRequest?  I can't seem to find any mention of these.  

When I run the sample code, I receive this error message:

"Error E00001 An error occurred during processing. Please try again."

Any ideas what to try to make this work?

All the other features work fine.  I'm using our live account, not sandbox.  

Thanks.

Bob

[RichardH · Accepted solution]

Hello @bob_h

A replacement for SIM is nearly ready for general release.  If you would like to begin developing with Accept Hosted, you can find documentation at http://developer.authorize.net/api/reference/features/accept_hosted.html

RIchard

[bob_h]

Thank you!  

Bob

[bob_h]

With the SIM method, we would collect name and billing address on the form on our web server.  We could post that info to the payment form hosted at authorized.net and it would pre-populate those fields, so the customer would not have to retype that information.  

Will it be possible to pre-populate these fields when using the Accept Customer Hosted Form?

Bob

[Aaron]

Hi Bob,

It is indeed possible to prepopulate the form. When you request the token, include anything you want prepopulated in the "transactionRequest" element of the request. You can use all of the same information that you see for "transactionRequest" for the regular payment transactions (https://developer.authorize.net/api/reference/#payment-transactions), with the following known issues:

• If you're sending in an address, you must send the country element with it.
• Don't send in a "payment" element. You probably wouldn't anyway, since it doesn't make sense to prepopulate a hosted payment form with a card number. But, if for some strange reason you wanted to try it, it won't work.