Authentication

Overview

Our Gateway is an application programming interface (API), intended to accept requests from the merchant's web services to the payment platform. The Gate API conforms to the Representational State Transfer (REST).

Gateway and merchant's web service interact by exchanging request and reply messages in the HTTP format: the web service issues requests and the payment platform responds to those requests.

If the payment platform is able to respond to requests without resorting to any third parties such as customers or external payment systems, it uses the synchronous model; otherwise the payment platform uses the asynchronous model.

Synchronous model

Gate uses the synchronous model when it can generate the response by using only its own data and resources, for instance to return the current status of payment. Synchronous interaction is performed in a single HTTP session and allows you to send only one response.

Asynchronous model

The asynchronous model is used when to generate response, the payment platform needs to communicate with third parties, for instance when it processes payment which requires input from the customer and/or payment system. In this model, Gate sends the following to the merchant web service: acknowledgement that initial request is accepted and successfully validated and the callback with final result (in case initial request is successfully validated). The model may also include exchange of messages with intermediate results between those two responses, for instance the payment platform may issue redirects to a form exposed by the payment system.

API Authentication

All authentication for our API is handled using OAuth Bearer tokens. To generate your token, login into your Dashboard account and navigate to the E-commerce & API section. A step by step guide for API authentication can be found in the API reference.


Jump to
  • Overview
  • API Authentication