Home

Search Results ...

Home

Online Documentation

Looking for Payment Gateway integrations? You’ve come to the right place!

Choose your Integration Journey

Get started with our two most popular integration options
streetsign_icon

You want easy and modular payment integration?

 — Go with our Payment Page

You want full integration control?

Learn How to Integrate your Favorite Options - Step-by-Step
integration_icon

Follow our Payment Page Integration Guides for

Hosted Payment Page, Embedded Payment Page, and Seamless Integration

Payment Methods

Personalize the Way you Process Payments
altpayment_icon

Equip your shop with the payment methods that are best for your consumers.
integrationfeatures_icon

If you are an EU merchant and want to process card payments, head to 3D Secure 2.

Looking for installment payment? Need information about cross-referencing and referencing transactions? Take a look at our Features for REST API for all your payment-processing needs.
note_icon

  • Connections to our test and production web sites and services must not be locked on target IP address. The IP addresses of our services are dynamic, therefore usage of FQDN or URL-based filtering for outgoing connections are adequate in case of outgoing Internet connection control.

  • The digital certificates used by our applications are regularly renewed. If your applications use certificate pinning, TLS connections will generate encryption errors. We advise against certificate pinning in general as a practice and kindly ask to allow new certificates coming from our side.

  • The digital certificates behind our servers require the usage of SNI (Server Name Indication) feature for which we kindly ask you to make sure that it is activated in your applications. Without this option enabled on the client side, TLS encrypted connections may end up with errors. As our Web Application Firewall (WAF) is a cloud based service, our applications will dynamically resolve to cloud provider DNS entries. For TLS connections to succeed, the SNI TLS extension is required to be enabled.

  • Customer side applications using HTTP request headers bigger than 32Kbytes will encounter connection errors. As of industry practices, even 16Kbytes is sufficient and we kindly ask to implement this limit. Nevertheless, if your applications require more, please contact us for this matter.
callcenter_icon

Any questions? Need help? Just want to get in touch? Contact Us

Integration Options →