High-Risk and Adult Merchant Account integration issues
.........................................................................................................................................................................................................................

Please note that with the High-Risk and Adult Merchant Account + Gateway you must integrate your website with one of the methods below before we can make your account live. Don't worry, we will only ask you to do this once your application has been 100% approved.

There are several different ways to integrate your site/shopping cart to the High-Risk Merchant Account + Gateway. The way in which information about purchases is passed between your shop and the payment service is called the Integration method.

Below are the different methods available:

1) CheckOut Integration

Please note that this bypasses SSL and PCI requirements and allows you to use the VPOS, but you cannot implement 3D secure or recurring payments through this integration. Also only Payment method is supported, not Authorize-Capture.

CheckOut is intended to be used by merchants who don´t want to implement their own CheckOut. It is not the only way to integrate with us. Therefore, it is important to understand the different processor operations and web services available prior to starting the integration in order to decide which features you will need.

The checkout system is designed to make the integration of the system as easy as possible. Integrating the checkout means integrating all our payments methods in one go. Through one interface it's possible to handle only credit cards at the moment, but other payment methods will be added in the future.

The checkout consists of posting some parameters, such as price and item description to our checkout page. Doing so will create a payment page with all the relevant payment options.

The user can interact with the CheckOut page to make his payment. Once the customer finishes the payment, the gateway posts to the success or error URL at the merchant side. This indicates whether the payment processed successfully or failed, and the merchant can also take advantage of the payment details posted by the gateway in the response.

Below is a functional overview of the operations that have to be done to process with CheckOut:

• Get token: This operation allows the merchant to send payment information and get a token in order to avoid tampering so that the end user never sees the information sent between the merchant and the merchant account system.
  
  
• Redirection to CheckOut: If the token is successfully generated, the merchant has to redirect the end user to CheckOut, where the payment details will be introduced by the consumer into the payment page.
  
  
• Response: Once the payment is processed, the customer will be redirected to one of the URLs provided by the merchant whether the payment was completed successfully or not.

2) Web Service Integration (Basic Operations)

This integration type supports both recurring billing, and 3D Secure. but you are unable to use the VPOS (phone payment system) using the one account and a second merchant number will need to be generated. However this must be requested at the time off application.

The Basic Operations Web Service provides all the basic functionality you need to start processing transactions. This interface is ideal for customers who don’t have special requirements and want to start sending transactions as fast as possible.

The test page we supply displays a list of the available methods that can be called and also provides a link to the WSDL description of the Web Service. In addition, this is the URL where transactions must be posted during testing and integration process.

Once you know which web services fit better for your requirements, it is necessary to decide the flow used to collect the money from card holders. This can be done in two different ways: doing a one step operation called Payment, or in two steps using Authorize and Capture operations.

The next step is to select the protocol you will use to connect the web service. We support SOAP and HTTP POST requests; you can find detailed information and the samples available in the section Protocols Supported.

Recurring Billing integrations

Once a customers credit card details are completed and submitted, the information is then validated and saved securely. An ID for the card entered is given, which will be stored with the subscription record, for future billing. The card is charged using the stored card details and will either confirm their payment or inform you that the card was declined.

Unlike our other two accounts, the repeat billing facility is more manual. Once a customers credit card details are completed and submitted, the information is then validated and saved securely. An ID for the card entered is given, which will be stored with the subscription record, for future billing. The card is charged using the stored card details and will either confirm their payment or inform you that the card was declined.

Within your website you will be able to view all new subscriptions and those which are due soon. Once a payment is due you will manually request funds from the card which was stored originally for the user. From the subscriptions page you can click the history button to see the list of payments that were made for that subscription. You will also be able to view a list of customers.

The cardId and Guid can be obtained in two ways:

• When you perform a transaction: the engine returns the CardId and CardGuid used for the transaction in the Cdc
• Explicitly calling the method RegisterCard.

When using the recurring integration the credit card details will not be stored on your servers but they are stored on our PCI compliant servers. However you will still need to have PCI Compliance as they are initially entered within your website.

NOTE: Recurring transactions can be sent through the web service BasicOperations using the parameter merchantAccountType set to 4.

The last step prior to go live is to complete the certification

The certification is a fast process that can be completed in a couple of minutes; it consists of sending some test transactions that will differ based on the features you will use in the live environment. We will monitor these transactions to check the information is received as expected.

When you are done with the integration let us know the web services and authorization flow you want to use live, with this information we will prepare and send you the test cases and will enable the traces in the server.

Protocols Supported

The Payment Processor functionality is published via Web Services that can be accessed using the next protocols:

• Soap 1.1
• Soap 1.2
• HTTP Post

All communications between customers and the bank are encrypted with SSL. We encourages the use of SOAP as the protocol to communicate with our web services. Using a SOAP toolkit dramatically reduces the development from a front-end perspective, since you don’t need to deal with XML or HTTP, but just instantiate objects and call methods on them. More information about SOAP can be found at:

• Full SOAP specification W3
• Microsoft Web Services
• Java Toolkit
• Perl Toolkit

All the web services are enabled to provide the WSDL necessary to build SOAP requests; in addition all operations provide an informational page with details about how to build the SOAP and HTTP POST requests. You can find the exact URL for each page in the description of the web methods.

Due the nature of our business integrations methods can change. Therefore the information within these documents is subject to change without notice. Up-to-date manuals and integration guides are available once your account is active and ready for testing.

Please click here to download any relevant documentation

Need someone to do the integration?

If you already have a website and need to integrate it to our high-risk or adult merchant account please contact us. We can even design one from scratch - Please either email us or ring 01482 500334

............................................................................................................................................................................................................................
Related Pages

• 3D Secure
• PCI Compliance
• Anti-Fraud Solutions