Authorize/Decline/Error pages

[Kenny]

Hi,
We're trying to setup FaaS for a client on their CMS website. I'm wondering if there are examples anywhere of a decent typical Authorize, Decline or Error page?

The manual talks about needing to set these up on our site, but there is no more information about what would typically be on these pages as far as content. We are just wondering what would be typical for any of these.

- Should the Authorize page be what we would typically call our 'Thank You' page? We already have this created for when a purchase is made.

- Should a Decline or Error page give any instructions on how to 're-submit' or explanation of who to contact to see why it was declined/errored? Should there be a redirect back to ticket page?

Thanks. I know it's probably obvious, but I just wanted to be sure.

[CnP.Support]

Kenny,

Have you seen the examples on the site?

• http://clickandpledge.com/developers/faas/

There are 5 examples that all have the authorize/decline/error pages. The parameters are passed in the URL so you can grab them and show them if you want. Authorization code, etc.

Let me know if you are looking for something else.

[Kenny]

Yes, sorry, I had seen those. I thought those just looked like informational pages for someone wanting to know more about 'FaaS' and how to integrate it into their site. It didn't look like anything a sample end-user would expect to see or gain much from.

The only thing unique I was seeing on the page was the parameters you mentioned:

The following has occurred while processing the transaction:

Error Response

on=Invalid%20Credit%20Card%20Information%20&RefID= Example000

- Is this information automatically parsed and added to your error page? I would imagine if that was added to the URL, our site would generate a 404 error page.

Sorry, I'm just wondering how that would help a general end-user trying to make a transaction?? Would that be added to a link that they would be able to click to see what the error was or why?!?

I apologize again if I'm missing something completely obvious. It just seems that as these pages are required, we would want to make sure they're useful and decently designed.

Thanks!

[CnP.Support]

Good day!

Information is passed in the URL. So let's say your Decline Page URL is:

https://www.clickandpledge.com/developers/faas/example/001/

When a transaction posts to the FaaS service, upon authorization it will post back to the page listed for OnSuccessURL. So if the following is listed in the code:

<input type="hidden" name="OnSuccessUrl"  	id="OnSuccessUrl" 	value="https://www.clickandpledge.com/developers/faas/example/001/Authorize.asp" />

FaaS service will reply back with the following by redirecting the user to the following page and URL.

https://www.clickandpledge.com/developers/faas/example/001/Authorize.asp?on=117139149924111&vg=&RefID=Example001

As you see the Authorization parameters and various other reference information is listed in the URL. The URL may easily be parsed through reading the various parameters in the URL.

Hope that makes sense. If you are having a hard time following the logic we can set up a telephone conversation so we can explain it and discuss the vague points.