We are a small company that has been using the same authorize.net online payment web page for 15 years and now we must do something quickly before Weblink is discontinued on Sunday.
Our developer was tasked to do the work several weeks ago, but he left abruptly today and we only just learned that he had done nothing about the payment web page. I am the only one in the company who knows anything about HTML and web design, but I am really just the one-eyed man in the land of the blind.
So, what would be the quickest and easiest way to keep our payment web page up and running after Sunday? Can we just modify the existing HTML code in some way? I am hoping to be able to make the transition without having to spend the weekend taking a crash course in payment gateway development.
This appears to be the relevant code we are now using (I have disguised some of our corporate information).
<form action="https://secure.authorize.net/gateway/transact.dll" method=POST>
<table width="615" border="0" cellpadding="0" cellspacing="0">
<tr><td colspan="2">
<input type=HIDDEN name="x_Version" value="3.0">
<input type=HIDDEN name="x_Login" value="xxxxxxxxxxxxxxxx">
<input type=HIDDEN name="x_Show_Form" value="PAYMENT_FORM">
<input type=HIDDEN name="x_Description" value="Product">
<input type=HIDDEN name="x_Logo_URL" value="http://www.pay.website.com/images/payment_form_logo.jpg">
<input type=HIDDEN name="x_Email_Customer" value="True">
<input type=HIDDEN name="x_Cust_ID" value="DO NOT USE">
<input type=HIDDEN name="x_Invoice_Num" value="DO NOT USE">
What do I do now?
Many thanks for any help you can offer this poor half-baked excuse for a developer.
Ciao! Bill
04-28-2017 03:23 PM
Hello @Martin616
Our best suggestion is to use an Authorize.Net Certified Developer to help you upgrade your system.
Richard
04-28-2017 03:45 PM
Hi @Martin616,
The transition is not vey difficult. Basically it amounts to modifying your application to POST your data, including your transactionKey, as XML instead of name value pairs, to Authorize.net's API at : https://api.authorize.net/xml/v1/request.api
We have upgraded many applications for the same reason.
04-28-2017 04:03 PM - edited 04-28-2017 04:05 PM
@NexusSoftware is correct, but I should point out that this can be done within an application but it should not be implemented this way using a plain HTML form as it could potentially expose your transaction key on the page.
Richard
04-28-2017 05:01 PM
@NexusSoftware
hi guys
i am getting an error on product live and test mode both "Finger Print value is not valid."
as its working on sandbox correctly and perfect the way we wanted it
we are using ..
ACCEPT HOSTED method and according to method.. we used all parameter is required and get token successfully and redirect to authorize.net payment form and when we enter cc info and other info then press Pay button then getting an error
"Finger Print value is not valid."
please guide me..
thanks in adavance.
VJ
04-29-2017 02:29 AM
Hi Bill-
We have the same problem over here. Did you ever find a solution?
Best,
mark
05-01-2017 07:38 PM