- PDF
Payment Gateway
- PDF
API Documentation
Comprehensive API documentation can be found at this link. It is used for custom implementation of e-shop connection to API. It contains sample CURL, PHP, JAVA and Python requests.
Payment Gateway Display
The standard payment gateway on an e-shop can be displayed in four different ways.
You can find more information about payment gateway display in this article.
Display of Payment Methods
You can offer your customers a wide range of payment methods and ways to display them in your e-shop. They differ from each other only in a few aspects, but all aim at the successful completion of the payment by the customer.
You can find more information about displaying payment methods in this article.
Comgate Checkout SDK
The Comgate Checkout SDK is used to integrate the payment gateway directly into the e-shop cart and enables payments without redirecting the payer to the payment gateway. Currently, payments via Apple Pay and Google Pay are supported. We are preparing card payments with card number entry directly in the e-shop cart.
The Checkout SDK is the most advanced way to integrate the payment gateway. It is an extension of the standard implementation using the API protocol.
You can find more information about the Comgate Checkout SDK in the API documentation.
Payment Gateway in a Mobile Application
Do you operate a mobile application into which you want to integrate our payment gateway?
Integration of the payment gateway into a mobile application is very similar to integration into a web interface. The only difference is that on the web it is possible to use an Iframe, while in a mobile application it is possible to use a component intended for displaying a web page, typically a WebView.
Another option besides WebView is to display the payment in the device’s native browser and subsequently use a mechanism to redirect back to the mobile application. For Android, this is an Intent, and for iPhone, URL Schemes or Universal Links.
More information about the integration can be found in the API documentation.