Low Risk and Standard Accounts
High-Risk Accounts
Adult Merchant Accounts
High Volume Corporate Accounts
 Face to Face Payments (Chip n Pin)
Home Page
Account ID:
Password:
Login Now
Web Merchant Services - Online Payment Solutions
Merchant Support
Technical Support
Company Profile
Search Website
Payment Demos

Using the Callback Feature
......................................................................................................................................................................................................................

When a shopper makes an order at your website and starts to pay, our 'callback' feature enables you to automatically return information to your webserver. The Payment Response feature posts the payment information from our server to a URL on your server via HTTP(s). This enables you to validate the information, update the order and if required display your own shopper result pages

Many shopping carts make extensive use of this feature, to manage your shopper's orders more effectively.

Benefits

If you use Payment Response, you can:

  • get more information about the payment than you would receive in the merchant confirmation email.
  • send the shopper additional information about their order in your own result pages or an order confirmation email.
  • use the information received to trigger actions in your own system.
  • pass your own order variables through our Payment Service and then back to your server.
  • check and validate all the payment data that has been received and processed.
  • examine any available fraud check results, such as those arising from verification of Address, Security Code and Authentication information.
  • maintain any recurring payment agreements.

The Process

The following diagram explains the life cycle of a standard transaction and how the Payment Response feature is used within this process.

 

  1. Order: The shopper places an online order with the merchant.
  2. Purchase Token: The merchant produces a purchase token containing details about the order, which is then sent along with the shopper's browser to a payment page located on our Payment Service secure serve. The shopper then enters their card details into the payment page and we check these details with the card issuer.
  3. Result Pages: If the card issuer authories the transaction, or the shopper cancels the payment we will display a result page to the shopper.
  4. Confirmation Email: For successful transactions, we send an email to the merchant and shopper, confirming the details of the transaction.
  5. HTTP(s) Payment message: By enabling Payment Response for your installation, we will also send you a payment message via HTTP(s) to your server. This message contains information about the transaction and can include your own variables.
  6. Shopper response: Upon receiving the HTTP(s) payment message you can usa a server side script to send a response to the shopper's browser.
    Note: If the shopper response fails to display your own result pages to the shopper's browser, then the default pages will be displayed.

Can I use callback with Repeat Billing (FuturePay)?

Yes - see: FuturePay for more details.

What happens if my callback fails?

If your callback fails, we will alert you to the failure (via an email), and try to assist you in finding out the reason for failure.

Please note we have a comprehensive range of technical guides and application 'plug-ins' that are made available to you on application. Including a FREE integration manual and 24/7 tech support

 

 
     

Contact Us | Privacy Policy | Legal Information | Terms & Conditions
     
Web-Merchant Services Limited. Registration No. 03919014 © 1997-2012. All Rights Reserved
SimplyPayments™ and Web-Merchant Services (including all other trading arms) are fully compliant with the Payment Card Industry Data Security Standard (PCI DSS)