cancel
Showing results for 
Search instead for 
Did you mean: 

Trying to write simple PHP form to handle payments.

Hi! I'm trying to create a checkout script in HTML and PHP which can easily allow custom fields and make simgle purchase payments. This is proving to be quite the challenge, and I'd like to ask your advice as to how to approach this.

 

I've created a form using some scripts I found online and created a Sandbox account. I keep getting a (99) error and I don't know why. Even the diagnostic tool didn't help.

 

Before I post what I ahve and ask specific questions, I'd like to ask if there are any example scripts which work well that allow me to store custom data into my transaction?

 

Thanks,

Brendan

 

bdparker
Contributor
3 REPLIES 3

It is very easy, in any language, to post the appropriate XML or JSON https://developer.authorize.net/api/reference/index.html to the appropriate endpoint ...

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

and process the results.

 

Error 99 is applicable only to the SIM API. The server-generated fingerprint does not match the merchant-specified fingerprint in the x_fp_hash field.

 

As SIM is deprecated, are you sure you wouldn't rather use Accept Hosted or Accept.js in order to reduce your PCI requirements?

Powered by NexWebSites.com -
Certified Authorize.net developers
NexusSoftware
Trusted Contributor

Thanks for the response!

 

If SIM is deprecated, I'm open to other methods. I just got SIM to work (after working on it for a really long time) but I will switch if it's better.

 

We want to avoid using SSL so it looks like Accept.js is out of the question. It's too bad, too! It looked like good, clean code. The Accept Hosted details didn't specify whether we needed an SSL, so I'm assuming no. It looks like we don't, but I can't be sure. If not, is there any example scripts which I can use to get started? It looks like there's a bit of code on the page you provided but no explanation of where it goes or how it gets set up.

 

Thanks!

In order to process payments, you need to be using TLS 1.2, for the protection of your customers as well as yourself. For a free and easy alternative to standard SSL certificates check out https://letsencrypt.org/

Powered by NexWebSites.com -
Certified Authorize.net developers