• Most proper payment gateways incorporates a way to give realtime feedback to you as a merchant about transactions as they occur.
• This can then help you as a merchant to react on this feedback.
  • If the transaction went through with success; you can react positively e.g. provide the buyer with a product.
  • If the transaction did not go through you might also want to record this for statistical purposes e.g. to determine how many bad transactions on a certain product occurred.
• Authorize.Net also gives us this means. In fact it offers us two ways to utilize this.

• If you log into the Authorize.Net merchant dashboard there is an Account entry (top right)
• Under the Account entry are various Settings which you can adjust.
• Select the Silent Post URL under Transaction Format Settings .
• Specify it as: http://[your RADIUSdesk server]/cake2/rd_cake/fin_authorize_net_transactions/silent_post.json
• Click Submit to make it permanent.

We use this as a double check mechanism since some people reported that the next method did not always work as intended.

• When you specify a URL for the Relay Response item, Authorize.Net will source this page behind the scenes and display the results on the server of Authorize.Net after a transaction has been completed.
• This may be a bit different when compared with other payment providers which will simply redirect back to a specified URL.
• We can also not dynamically provide this URL for instance in a Buy Me type of button like we do in PayPal.
• When this URL is called from Authorize.Net's server it is called with a http POST.
• This POST then contains all the transaction's details which we in turn can use for instance to generate a receipt for our buyer.

• In RADIUSdesk we would like to make the user experience as pleasant as possible.
• We would like to simply log them in with their voucher which was generated during a successful purchase.
• For this purpose we will modify the page which will be displayed by the Authorize.Net 'proxy' that it automatically redirects to another page (our login page).
• This login page in turn will check for a value in the query string of the page and if this value is present (which is the Authorize.Net transaction id) it will query the back-end in an Ajax call to source the voucher details associated with this transaction.
• If the login page got the voucher details, it will use it to connect to the CaptivePortal.
• To the user this will all be seamless and they will simply connect to the Internet through the captive portal after a successful transaction.

• If you log into the Authorize.Net merchant dashboard there is an Account entry (top right)
• Under the Account entry are various Settings which you can adjust.
• Select the Relay Response under Transaction Format Settings .
• Specify it as: http://[your RADIUSdesk server]/cake2/rd_cake/fin_authorize_net_transactions/receipt
• Click Submit to make it permanent.

Now that we get transaction details from Authorize.Net we can create some buttons.