FAQ: Technical Integration
List of questions
- What is your integration model like?
- In what way transactions are authorized using PayLane’s system?
- Can I get a test account?
- Do you use your own Payment Gateway?
- How secure is your system?
- What anti-fraud screening tools do you use?
- Are your fraud prevention/detection tools free of charge, or do I have to pay additional fees for using them?
- Do you offer free technical support?
- Do you offer integration packages for your API?
- Is it possible to use PayLane Secure Order Form?
- Are there any additional requirements to integrate my webshop with your payment gateway?
- In what way should the payment form to collect cardholders’ details be designed?
- What is authorization and capture model?
- Do I have to postpone completion of all website elements before integration with PayLane is performed?
Q1: What is your integration model like?
PayLane’s integration process is fairly easy and transparent, both for our merchants, and for their customers coming through a checkout process on a website.
Our gateway offers an API (Application Programming Interface) for interacting with our services. You will get a direct interface based on webservices that you can use to process all the sales under the hood.
Our model allows for a programmer to communicate with the gateway from server-to-server instead of redirecting the customer to any secure payment page stored on PayLane’s servers and back again.
As a result, the transaction seems to only occur on the merchant's website. This alleviates the problem of the customer leaving your website and not feeling comfortable with their purchase.
With all the pages of the order process that have the same look and feel as the rest of the website, you will create a professional image, expected from your clients.
Q2: In what way transactions are authorized using PayLane’s system?
When the order process in completed by the customer, he submits his credit card and other mandatory details.
The payment authorization is being initiated by your IT System and sent to PayLane Payment Processing System
via webservices that PayLane provides for merchants.
As a result of this process, an immediate response is sent back to your system about whether the transaction
is accepted or declined.
Q3: Can I get a test account?
Yes – just
apply for the merchant account.
Q4: Do you use your own Payment Gateway?
Yes, we have developed our own Payment Processing System.
Q5: How secure is your system?
With years of experience in the online payment processing industry, we know that there
is nothing more frustrating for the merchants than to suddenly discover that their
payment processing service is down, payment pages do not work or the control
panel "times out" due to a database error.
At PayLane, we have invested significant resources to build an infrastructure that
boasts excellent reliability, offers high performance, and protects us and our merchants
against any security threats.
The entire network is monitored 24/7. In case any server anomaly is detected, an
immediate action takes place to ensure that no neither PayLane merchants, nor their
customers have to deal with the service downtime or outage.
Q6: What anti-fraud screening tools do you use?
PayLane’s service includes a highly-sophisticated, built-in Anti-Fraud System that
prevents fraudulent transactions and significantly reduces the fraud risk. Therefore, it
helps to avoid delayed merchant payouts and penalties. Our anti-fraud tools are provided
to all merchants, free of charge, as a part and parcel of our offer.
The Anti-Fraud System screens all the data provided upon a transaction, estimates the
risk and automatically blocks any suspicious transactions before they are performed!
The risk estimation is based on various criteria, such as: comparison of the service
recipient's address with the country where a bank that has issued a credit card is
located, customer’s GeoIP localization, anonymous web proxy identification and many more.
The fraud score, being the result of the Anti-Fraud System check, can be used to block
suspicious transactions. The score range is: 0-10 points. The higher the score, the
bigger the risk of a fraudulent transaction.
Normally, only evident frauds, reaching the score of 10 points, are blocked.
However, PayLane allows you to set your own fraud score limit thus reduce the risk
even more effectively.
You can monitor the fraud scores for all the transactions via your PayLane Merchant Panel.
You will be able to review the all the scores for transactions that were blocked as
well as for those that were successfully processed (their score was below a set limit).
Moreover, each transaction includes a comprehensive, human readable description
explaining the fraud score.
Q7: Are your fraud prevention/detection tools free of charge, or do I have to pay additional fees for using them?
PayLane fraud prevention service is provided free of charge, as an inherent part
of our payment processing system, to all of our merchants.
Q8: Do you offer free technical support?
For all our Merchants PayLane offers free technical support in
the integration phase and afterwards.
Our help does not include custom software development. We won't DO the integration with
your IT System but we will help you in case you have any problems.
Q9: Do you offer integration packages for your API?
We've prepared easy to use integration packages for the
following programming languages:
The integration packages allow integrating with PayLane Payment Processing System in 2-3 hours.
Q10: Is it possible to use PayLane Secure Order Form?
PayLane doesn't offer a Secure Order Form for Merchants.
We feel that it's always better for customers not to leave
the website of the Merchant while they're shopping online.
Note that Merchants DON'T HAVE to save any cardholder
information, even though the secure order form is on
their servers. The information is only passed through
the secure order form and goes directly to PayLane.
In case of recurring transactions PayLane offers a unique
resale feature allowing Merchants to execute recurring
transactions based on the unique Sale ID number of the
first transaction in the recurring cycle - only one Sale
ID number needs to be stored by the Merchant - cardholder
information will be saved in the PayLane Payment Processing System.
Q11: Are there any additional requirements to integrate my webshop with your payment gateway?
The basic requirement is to buy an SSL (Secure Sockets Layer) Certificate to ensure satisfactory level of security regarding data transfer of cardholders’ details via your payment page.
Q12: In what way should the payment form to collect cardholders’ details be designed?
The design and layout of the information that you request from your customer during the order process is up
to you, on condition that the payment (order) process is compliant with
Credit Card Organizations’ website
compliance rules.
Our merchants create payment pages themselves. If there is something incomplete, inaccurate or needs
amendment, PayLane swiftly provides the merchant with applicable indications.
Q13: What is authorization and capture model?
Our system allows to split two stages of a single transaction – authorization and capture of a certain
amount may be performed separately.
Normally, a sale involves authorization and capture as simultaneous actions.
However, some merchants may find it useful to initially only block the funds on a card. In the meantime, they
get e.g. an opportunity to check whether ordered items are on stock or contact a customer to confirm a payment
amount (the amount to charge can be modified at this stage).
Then a certain amount is captured. If you decide not to capture the amount for some reasons – you can either
release the funds, or they will be unblocked automatically after some period of time (usually 7 days, depending on a bank).
Q14: Do I have to postpone completion of all website elements before integration with PayLane is performed?
No – you can get integrated with PayLane’s system after you have completed all website amendments.
Moreover, the website should be ready enough to perform website compliance check before we move to the integration part.
