|
Premier Account integration issues
.........................................................................................................................................................................................................................................
Before applying for your chosen account we
recommend downloading the integration guide.
Click here to download
There are several different ways to integrate your
site/shopping cart to the Premier Account. The way in
which information about purchases is passed between
your shop and the Premier Account payment service is
called the Integration method.
Below are the different methods available:
1) CheckOut API
The Premier Account 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) Basic Operation Web Service.
With the Premier Account we have a Basic Operations
Web Service, which provides all the basic functionality
you need to start processing transactions. A side Basic
Operations you have extended web services to provide
additional and specific features.
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.
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. To help you with your planning you should
Basic Operations Web Service
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.
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:
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
|
