Callback allows you to integrate your Nochex payments with your website's back-end operations, so you get immediate confirmation and authentication of the Nochex payments you receive. It's very similar to our Nochex APC system. It allows you to:
• Process your customers payments in real-time
• Give immediate feedback to your customer
• Store your Nochex payments in your own database
Callback can be integrated into the Nochex checkout system to allow you to create a payment system that alleviates the need for you to log into the Nochex system to confirm that payments have been made. The customer will also benefit from the Callback as they will receive an immediate response to the order they have placed, similar to that of making payments through a credit card system.
How does the Nochex Callback work?
The Nochex Callback system works by sending a confirmation POST to a page on your server. Once your server has received a response from our servers, you can process the information to allow you to construct an email or update an order on your website / shopping cart in relation to a payment that has been made, and whether it has been a AUTHORISED or DECLINED transaction.
How do I apply for Callback?
To use the Callback functionality - you will need to contact support who can enable this feature for you.
How do I change the Callback URL that Nochex send the confirmations to?
If you are a Merchant account holder and wish to amend the URL Nochex POST their confirmations to follow these steps:-
• Login to your NOCHEX account
• Click on the 'Payments Page Setup' link
• Edit the URL in the 'CallBack' textbox
• Press "Save Changes" button
you can send the Callback details with your checkout parameters, for example:
callback_url=http://your.url.here/responder.asp [Callback responder address]
How do I integrate the Nochex Callback into my site?
For detailed instructions on integrating the Callback system into your website please download a copy of the attached Callback guide.
What information can be retrieved from the Nochex Callback System?
The following information can be retrieved from the CALLBACK system
| Variable || Value || Description |
| transaction_date || Transaction specific || Date/time stamp of transaction. |
| transaction_id || Transaction specific || Unique code generated to distinguish transactions. |
| security_key || Transaction specific || System generated key (for Nochex use). |
| amount || Transaction specific || Amount received into Nochex account after charges. (same as net amount) |
| gross_amount || Transaction specific || Full amount of the customers payment |
| order_id || Transaction specific || Transaction specific code, order id as passed by you, the merchant. Your customer is not able to view or edit this. It must be unique per transaction. |
| merchant_id || Transaction specific || Merchant Alias of the payment recipient. |
| email_address || Transaction specific || Email address of the payment sender. |
| postage || Transaction specific || Postage amount for transaction |
| insurance || Transaction specific || Insurance amount for transaction |
| optional_1 || Transaction specific || Optional field submitted by merchant |
| optional_2 || Transaction specific || Optional field submitted by merchant |
| optional_3 || Transaction specific || Optional field submitted by merchant |
| optional_4 || Transaction specific || Optional field submitted by merchant |
| optional_5 || Transaction specific || Optional field submitted by merchant |
| transaction_status || 0=Live , 100=test || Used to distinguish a test transaction where no money has been sent, from a live transaction where money has been sent. |
| billing_fullname || Transaction specific || Billing name of customer |
| billing_address || Transaction specific || Billing address of customer |
| billing_postcode || Transaction specific || Billing postcode of customer |
| delivery_fullname || Transaction specific || Customer Delivery name |
| delivery_address || Transaction specific || Customer Delivery address |
| delivery_postcode || Transaction specific || customer delivery postcode |
| customer_phone_number || Transaction specific || customer phone number |
| consumer_message || Transaction specific || customer message entered on payment page |
| ip_address || Transaction specific || Ipaddress of customer |
| ip_country || Transaction specific || Country IP address based in |
| card_country || Transaction specific || Country debit / credit card issued |
| card_address_check || Not Checked, Failed, Not Available, Passed || Address verification result. NotChecked = AVS Check Bypassed, Failed = Address not match, Passed = Address match, Not Available = AVS not available for card |
| card_postcode_check || Not Checked, Failed, Not Available, Passed || Address verification result. NotChecked = AVS Check Bypassed, Failed = postcode not match, Passed = postecode match, Not Available = AVS not available for card |
| card_security_code || Not Checked, Failed, Not Available, Passed || CVV2 result. NotChecked = AVS Check Bypassed, Failed = CVV2 not match, Passed = CVV2 match, Not Available = CVV2 check unavailable for card |
| 3d_secure_validation_check || Fully Authenticated, Authentication Attempted, No Authentication Attempted || 3D Secure result. Fully Authenticated = 3DS Full Pass , Authentication Attempted = Attempted 3DS Check ,No Authentication Attempted = 3DS check bypassed |
| net_amount || Transaction specific || Amount received into Nochex account after charges. (same as amount) |
| charge || Transaction specific || Nochex charge for transaction |
Examples of Callback
We have various examples available to show how the Callback system works, and you will receive an email informing oyu of the parameters, and whether the transaction has been Authorised or Declined. Our Examples come in various programming languages
Last Updated 5 months ago