|
Premier Account integration issues
........................................................................................................................................................................................................................................................
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.
Please click here
to download any relevant documentation
|
