topic Re: Need to switch from SIM to AIM, Accept or ??? in Integration and Testing

Need to switch from SIM to AIM, Accept or ???

mferguson — Mon, 16 Jan 2017 18:09:03 GMT

We have been using SIM for years, but the hosted payment form is not mobile-friendly and there seems to be no immediate plans to make it so, according to tech support.

So, we're forced to host our own form. We've got an SSL cert installed and I've downloaded the SDK, but I can't find any kind of form samples to see what can work for us. And should I be using AIM or is that now something else... or should I use Accept?

We just need a simple form that submits 3 fields - the cardholder's Name, Card Number and Exp. Date and returns the fact that the transaction is good (or error code if bad).

A little help, please? :)

Re: Need to switch from SIM to AIM, Accept or ???

Lilith — Tue, 17 Jan 2017 21:55:21 GMT

@mferguson You have a few options these days. I'd strongly recommend using one of the Accept Suite's options. Accept Hosted or Accept.js might be your best option. (Accept Hosted is the direct replacement for SIM's Hosted Payment Form, and Accept.js is a replacement for DPM which doesn't include its own payment form, but greatly improves security since you don't have to handle PAI directly.)

Re: Need to switch from SIM to AIM, Accept or ???

mferguson — Wed, 18 Jan 2017 02:26:24 GMT

Hi Lilith,

Thanks for responding. It appears that Accept Hosted is what I need to implement to replace the SIM hosted payment form.

I have looked at the GetHostedPaymentForm() - JSON request, but I don't see how to implement this. I'm assuming somehow this function and data in it gets POSTed to the URL:

https://test.authorize.net/payment/payment

but I don't see anything that show how to do this. Can you point me to a sample page or something that explains how everything works together?

Thanks,

Mark

Re: Need to switch from SIM to AIM, Accept or ???

Lilith — Wed, 18 Jan 2017 16:55:29 GMT

@mferguson -- thanks for the feedback. I agree that we could probably spell out the process a bit more clearly, but I think the intention was to let the sample code at https://github.com/AuthorizeNet/accept-sample-app serve as an explanation of how to implement Accept Hosted into your existing workflow. We figured that it'd be better to show how to add the Accept Hosted form into a lightbox, for example.

You seem to be asking about how to summon the Accept Hosted form directly, using the token from getHostedPaymentPageRequest, so I'll focus on that.

First, getHostedPaymentPageResponse will look like this:

<getHostedPaymentPageResponse xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="AnetApi/xml/v1/schema/AnetApiSchema.xsd">
<messages>
  <resultCode>Ok</resultCode>
  <message>
   <code>I00001</code>
   <text>Successful.</text>
  </message>
</messages>
<token>fpXAkWfQzJUD6zzuU+yz9olx2YkoHd2bPzjm6u/teYYsKi3KmR9xmszKsEvw8bafqxwpshKqAUuXUp0uPMvWjelVNZDv+TYDcsq2+X+B7kuoQpnQeBnhMZg</token>
</getHostedPaymentPageResponse>

That token is what you pass to https://test.authorize.net/payment/payment in Sandbox, and https://accept.authorize.net/payment/payment in Production.

The HTTP body of the request would just be:

token=fpXAkWfQzJUD6zzuU+yz9olx2YkoHd2bPzjm6u/teYYsKi3KmR9xmszKsEvw8bafqxwpshKqAUuXUp0uPMvWjelVNZDv+TYDcsq2+X+B7kuoQpnQeBnhMZg

We'll respond to that token, if it is valid, by displaying the Accept Hosted form, as configured in your original getHostedPaymentPageRequest call.

Does that help?

Re: Need to switch from SIM to AIM, Accept or ???

mferguson — Wed, 18 Jan 2017 22:47:10 GMT

Do you mean if I just do this I should get a form displayed?

https://test.authorize.net/payment/payment?token=6B54DCFD276E00...

I tried this, it doesn't work, but I'm posting a token to the URL. I tried in a POST format, also and got the same error, "Missing or invalid token" with a Close button displayed. Is there something more I need to do that I'm not getting?

Also, I tried a few things with the JSON Request object on this page:

https://developer.authorize.net/api/reference/features/accept_hosted.html

But nothing works. Am I supposed to post this object? How?

Still in the dark.

Mark

Re: Need to switch from SIM to AIM, Accept or ???

Lilith — Thu, 19 Jan 2017 15:55:56 GMT

@mferguson The token goes into the HTTP body, not into the URL. We will ignore query strings, and strongly discourage their usage. HTTP POST generally works with the HTTP body. This StackOverflow discussion explains the difference.

Which scripting language or framework are you using? While I am not a developer myself, I can possibly suggest the method in that language or framework for executing a proper HTTP POST.

Re: Need to switch from SIM to AIM, Accept or ???

mferguson — Thu, 19 Jan 2017 20:03:49 GMT

I'm using LAMP (Linux, Apache, Mysql & PHP) with jQuery and Bootstrap.

I know the difference between GET and POST and why I tried it both ways, but I see now that I need to grab the token from the JSON (or XML) Response and POST that to:

Sandbox: https://test.authorize.net/payment/payment

Production: https://accept.authorize.net/payment/payment

Is that correct?

At first, I thought I was supposed to create the token in the admin Settings, but it's Authorize.net that creates the token and sends it in the Response code. Then I return it in a POST, which then gives me the FORM for user input, right?

If all the above is correct, what I'm really missing is the first step in how to create and make the REQUEST in order to get the RESPONSE. It appears that I use the JSON or XML REQUEST function. I just don't know how to use it so that it creates the REQUEST.

Re: Need to switch from SIM to AIM, Accept or ???

Aaron — Thu, 19 Jan 2017 21:00:31 GMT

Hi @mferguson,

The first step is to get a token. Your server sends a request for a token with details of the payment, and we respond with a token. Then next step is for you to send the token back to us from the browser so that we know which form to load into the browser with which details.

That first step, the token request, is going the be done directly from your server to ours. Once you know everything you need to know to start collecting payment (amount at least), you send a request to the getHostedPaymentPageRequest method in our API. That call returns a response with a token good for 15 minutes.

The actual request comes from your server, but how you get your server to send it is up to you. Our PHP SDK has methods for doing this token request, so you could just call the appropriate method from a PHP script on your server.

To send the token back to us, you get the browser to do an HTTP POST to us with the token in it. In it's simplest form, you could create an HTML page like this:

<html>
<head>
<title>Form test page</title>
</head>

<body>
<form method="post" action="https://test.authorize.net/payment/payment">

Token: <input type="text" name="token" />

<input type="submit" />

</form>
</body>

</html>

Load that form up in a browser, copy the token you've received from the initial token request into the text field, paste it into the field, and click submit. The browser will then take you to the payment form corresponding to your initial request.

That's not suitable for real-world use, of course, so you need to find some way to get the customer's browser to request that form. You could serve the customer a page with a hidden form that automatically submits, causing the browser to be redirected to a page on our server with the form in it. Or, you could embed into your page an iframe containing the results of the form post.

Our sample app does it this way. It creates an iframe, with HTML form code inside. To get the value of the token to put into the form, it's calling a PHP script inline to do the token request to our system. Then, it submit's the form so that the result of that POST is what's visible to the user.

Hopefully I'm shedding a little light on this conceptually and not confusing you further. Please let us know if any of this does not make sense or if we can help you further.

Re: Need to switch from SIM to AIM, Accept or ???

mferguson — Fri, 20 Jan 2017 19:11:17 GMT

Hi Aaron,

Thanks for the detailed response.

I get the whole flow of how everything should be now. The main problem I'm having is how to send a request to the getHostedPaymentPageRequest method in your API.

I've now got the php-sdk working on my site and can log in to the /accept/index.php page with a Customer ID I created, but when I click on the "Hosted Pay" button, I get a modal that says, "Missing or invalid token." Any idea why I might be getting this?

Also, I click the "Pay" button, which displays a modal with form fields to fill out. I fill them out and click SUBMIT and get "Accept.js Example" and "error".

I think if I can get this all working I'll have a better idea of how I should set it up on our site.

thanks,

Mark

Re: Need to switch from SIM to AIM, Accept or ???

Aaron — Fri, 20 Jan 2017 22:51:32 GMT

Hi Mark,

You have the PHP SDK? or the sample app? or both? The problems you're talking about involve the sample app, and we can look into those. However, to get your code up and running, you'll want to install the PHP SDK and the PHP sample code. The PHP sample code has a "get-hosted-payment-page.php" sample that will show you exactly how to call the PHP SDK to get a token.

Re: Need to switch from SIM to AIM, Accept or ???

mferguson — Mon, 23 Jan 2017 20:49:52 GMT

Hi Aaron,

I have both, but am working with the sample app. I assume you mean this page, right?

/accept/getHostedPaymentForm.php

Here's the errors I get when trying to bring this page up directly (which comes up blank):

PHP Warning: SimpleXMLElement::__construct(): namespace warning : xmlns: URI AnetApi/xml/v1/schema/AnetApiSchema.xsd is not absolute in /accept/getHostedPaymentForm.php on line 105

PHP Warning: SimpleXMLElement::__construct(): <getHostedPaymentPageRequest xmlns="AnetApi/xml/v1/schema/AnetApiSchema.xsd"> in /accept/getHostedPaymentForm.php on line 105

PHP Warning: SimpleXMLElement::__construct(): ^ in /accept/getHostedPaymentForm.php on line 105

PHP Notice: Use of undefined constant JSON_UNESCAPED_SLASHES - assumed 'JSON_UNESCAPED_SLASHES' in /accept/getHostedPaymentForm.php on line 109

PHP Warning: json_encode() expects parameter 2 to be long, string given in /accept/getHostedPaymentForm.php on line 109

PHP Fatal error: Call to undefined function curPageURL() in /accept/getHostedPaymentForm.php on line 112

I can log in and get to the /accept/index.php page as I detailed in my prior reply. There's a little Iframe that opens up to the left of the buttons. It appears to be the XML file for what is needed to send to your server, but there is no token there. And when I click on the Hosted Pay button, I get a modal that says, "Make Payment" and "Missing or invalid token", so it appears this sample is not sending a token back.

Thanks,

Mark

Re: Need to switch from SIM to AIM, Accept or ???

Aaron — Mon, 23 Jan 2017 20:43:41 GMT

The sample code is something different from the sample app. Go to this GitHub page. That's a collection of sample code that you can use to see how the different method's are implemented. It would be best to clone that whole repository to the machine where you've installed the PHP SDK.

Each of the sample code files in that sample code repository provides an example for how to use the Authorize.Net PHP SDK to do a particular type of transaction.

Re: Need to switch from SIM to AIM, Accept or ???

markusfergus — Fri, 26 May 2017 22:48:08 GMT

I'm back with more questions. We had some other tasks taking precedence over this one of moving from SIM to Accept Hosted, so took a while to get back to this.

I've got Accept Hosted working for the most part, now. I get a token, get the form for entering CC info, submit that and get a completed transaction with email receipt.

What I'm not getting is a return of name=value pairs from the "Default Relay Response URL" set up in the Admin > Settings > Response/Receipt URLs page. SIM sends us back vars like: x_first_name, firstName, or any other custom var I create. Accept Hosted is not doing this. I was told at the beginning that Accept Hosted is the replacement for SIM, so I expect all aspects of SIM to be happening... except we can now have a mobile-friendly form.

Is there some trick here to get this working or some other way to do this with Accept Hosted?

Thanks,

Mark

Re: Need to switch from SIM to AIM, Accept or ???

NexusSoftware — Sun, 28 May 2017 11:49:02 GMT

When using Accept Hosted, the following parameter settings are used with the getHostedPaymentPageRequest API method. All configuration options for how the form operates and is displayed are set by sending these parameters within hostedPaymentSettings in the token request. The form's appearance and behavior are not affected by SIM payment form settings or any other settings in the merchant interface.

Information specific to your customer can be passed back to your server by embedding it in the continue/return URL or the cancel URL. By embedding information into the URL that is provided in the token request, your server can identify the specific customer and transaction that has been processed when the customer returns. Any name-value pairs embedded in the URL should be URL-encoded to ensure correct processing in the form request.

Whether the API request is sent using JSON or XML formatting, the values for all parameters sent within hostedPaymentSettings are sent as JSON objects.

hostedPaymentReturnOptions {"showReceipt" : true, "url":"https://yoursite.com/receipt", "urlText": "Continue", "cancelUrl": "https://yoursite.com/cancel", "cancelUrlText": "Cancel"}

If the API request is sent using JSON formatting, the values need to be sent using backslashes to escape the quote characters.

{
"settingName": "hostedPaymentReturnOptions",
"settingValue": "{\"url\":\"https://www.yoursite.com/continue\",\"urlText\":\"Continue\",\"cancelUrl\":\"https://yoursite.com/cancel\",\"cancelUrlText\":\"Cancel\"}"
}

Note: If you are using an IFrame, you must send the hostedPaymentIFrameCommunicatorUrl parameter in the getHostedPaymentPageRequest method.

Re: Need to switch from SIM to AIM, Accept or ???

markusfergus — Tue, 30 May 2017 13:53:39 GMT

The one problem I see with using this method would be where the user leaves the page and doesn't click the button. Then my update script doesn't get run and their order isn't recorded, like what I get using SIM.

Is there a way to get my custom name/value pairs returned after the transaction is successful, whether or not the "continue" button is clicked or not?

Re: Need to switch from SIM to AIM, Accept or ???

NexusSoftware — Tue, 30 May 2017 14:20:17 GMT

One way is to use webhooks, which would enable you to still be notified if a transaction was processed but the customer closed the browser before following the return URL.

Re: Need to switch from SIM to AIM, Accept or ???

markusfergus — Wed, 31 May 2017 22:18:23 GMT

Well, I'm just not able to make sense out of the webhooks docs and it doesn't seem that it would do what I need anyway.

I'm using the Silent Post method and it's working very well. Only drawback is that it seems to have a limit of 20 name/value pairs you can send... but I can work with that.

Now, after a transaction is successful, it displays, "Thank-you for your business!" How do I edit that wording?

Re: Need to switch from SIM to AIM, Accept or ???

Aaron — Wed, 31 May 2017 22:23:12 GMT

Hi @markusfergus,

There's no way to edit that wording, unfortunately, but I can definitely see the usefulness of such an option.

I'd encourage you to post this onto our Ideas Forum where others can take a look, contribute feedback, and vote for new features.

Re: Need to switch from SIM to AIM, Accept or ???

markusfergus — Wed, 31 May 2017 23:03:00 GMT

Yes, it assumes a particular type of transaction is taking place, when it could be many different things. This is not something that should be static, but editable.

Thanks, I'll make the suggestion.

Re: Need to switch from SIM to AIM, Accept or ???

Lilith — Fri, 09 Jun 2017 15:51:17 GMT

@markusfergus -- Out of curiosity, did you have a specific issue with the Webhooks documentation? I'm eager to hear any feedback you have so we can improve its quality.