sim.php was elegant... I can not for the life of me figure out the
on https://developer.authorize.net/api/reference/features/acceptjs.html to do any of this!
I just want to be able to do this dynamically in a php file,
$x_Description = $_REQUEST['x_Description'];
$x_Amount = $_REQUEST['x_Amount'];
$x_cust_id = $_REQUEST['x_cust_id'];
$x_company = $_REQUEST['x_company'];
$x_po_num = $_REQUEST['x_po_num'];
$x_event = $_REQUEST['x_event'];
and then send it off the Authorize.net..... Admins here tell everyone it is possible and they send them to links in the API documentation, but THERE REALLY IS SOMETHING MISSING there... there are some missing step.... I don't know what those dots are in front of the field, I don't know where they fit in context.... help, please.... this is all very confusing and I'm not stupid person... but 10 hours later and I can;t figure any of this out, even though sim.php works, I made that work...but this new stuff?? I'm completely lost... I can't be alone...
My needs are exceedingly simple... I just need to pass a customer id and price... how does the form pick up the price? I don't know...I can't see it being done anywhere....
Thank you.... I dont need a link to an API doc...I keep clicking on them, hoping I just missed something basic.... I need a sample of a sim.php integration --> embedded hosted form....
Flinging questions at me like this does not help, but thank you for your efforts. I understand why you asked them; I understand you are seeking clarity.... so am I.
The dots in front of the fields on this: https://developer.authorize.net/api/reference/#accept-suite-get-an-accept-payment-page I do not understand the nomenclature and it is not explained, yet when someone took the time to put dots there, they probably mean something.... I have no idea what they mean.
When Google Maps migrated to their v3 API, they had a complete step-by-step for those using their 1.0, 2.0 API... it works flawlessly... that is what I am looking for.
If you are using the SIM solution, here is how these field map to the new API, where is how you install accept.js, etc. The code samples are woefully incomplete, written by someone who does not understand that there are intermediate users who don't live their lives in code. We just want the payment stuff to work like it works already in SIM. This is not a hard concept.
I get I need to create a token, like SIM creates a hash, that contains the amount and timecode and all that stuff... yet this step is not anywhere in the documentation... I've spent HOURS looking for it and do not see it in any of the sample code... this seems like it should be a basic...
90% is the problem... if I can't complete the 10% that is missing, I am at 0% implementation.
That is my frustration. I write user manuals and instructional material for a living. I am well-trained in that skill. This is perhaps why their API is incomprehensible... it was written at a high-level, skipping critical steps, assuming everyone knows what they are. We don't.
I'll eventually get this working, but not at the expense of the stuff that brings in revenue. We're just going to tell our clients that we don't work with Authorize.net unless the SIM works... we're directing them to other payments providers and the only ones that lose out is Authorize.net.... who doesn't seem to really care if we're here or not.
Thank you for the time you took to help with my original question and reading this more detailed frustrration.
I learned the hard way that custom (merchant defined) fields are no longer functional in the Accept Hosted API.
We had to change our entire way of handling pass-through data.
Good luck, Fritz
Re: Dots in api reference guide.
The dots reference the nesting of the XML nodes. It may make more sense to look at the API Live console formatting as a guide.
** creditCard (nested inside the payment node)
***cardNumber (nested inside the creditCard node)
Here is the complete XSD reference-
I hope this helps!