Adult Account integration methods
There are several different
ways to integrate your site/shopping cart to the Adult Merchant Account
and Payment Gateway. Be it a simple checkout redirect to our secure payment
pages, using a cart plug-in, using a fully customisable API to allow for
credit card storage to provide customers a quicker payment method (great
for returning customers or recurring payments), or our mobile integration
which allows for fully mobile payments - including apps.
highly recommend that you understand the relevant integration
methods, or ask whoever is doing the integration (such
as a developer). Not only will this help you work out how you want
payments to be taken on your website (for example will you use 3D
Secure, store card details, repeat billing facility etc.) it will
also enable you to complete the relevant online application.
note that 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.
Below are the different methods available:
Please note that this bypasses SSL and PCI requirements and allows
you to use mobile payments and the VPOS, but
you cannot implement 3D secure or recurring payments through this
CheckOut is intended to be used by merchants who
don´t want to implement their own secure checkout and wish
to redirect to our secure payment pages. 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.
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.
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
Web Service Integration (Basic Operations)
This integration type supports recurring billing, credit card storage
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 of 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.
Please see below for an overview of these
two different ways:
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.
Below is a functional overview of the operations
that have to be done to process with CheckOut:
This is the easiest way to bill an amount over a card. The
Payment operation collects immediately the amount desired
authorize operation allows the merchant to book the desired money
from the card. This is the preferred method since it provides the
bank authorization to collect the money from the customer, but without
collecting it immediately. This operation has two-steps and must always
be completed by voiding the transaction or capturing, the completion
must be done within a maximum time of 14 days
Capture: The Capture operation
consists of collecting the money from authorizations previously done.
Normally a Capture is performed for the total amount of the transaction
but it might be possible to capture only part of the money reserved.
Please note that only one Capture operation can be performed per Authorization
Billing (repeat) Transactions
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 can either manually
request funds from the card which was stored originally for the user (useful
if you need to do checks each time you bill) or use an automated system
via an API. 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 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 Basic
To enable us to provide shopping cart plug-ins for our Adult account,
we have teamed up with Sellxed Payment
Extensions to provide the plug-ins. You must also integrate with our
Acapture integration method - subject
to application as this method is not available to all merchants and is
dependent on business industry and volume.
Acapture integrates with all alternative payment methods and manages
your multi-currency, multi-language, multi-country and multi-platform
eCommerce transactions through a single payment platform. As with all
our accounts you get full guides, manuals and free support.
Please note that there is a one off payment of £140 (€172)
plus 17p per transaction. All support for the specific plugin is provided
as well as an a surety that the plugin connection with the payment platform
is online 24/7. You also get the following included:
- Instant Download
- Free access to unique
- Free access to all updates
and upgrades of your modules
- All sellXed plugins
are PCI DSS compliant
We trust in what we do - We give you a guarantee that the module
functions - otherwise you will get your money back!
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
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.
The Payment Processor functionality is published via Web Services that
can be accessed using the next protocols:
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:
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 requests.