Connection to API
Koshelek Pay API
Documentation has moved
The information on this page is no longer updated and may be obsolete. The most current Koshelek documentation is now available at the new address:
Koshelek Pay API is provided by a dedicated Koshelek host.
API users are merchant's cash desk software and datacenter hosts.
API credentials, onboarding parameters and identifiers
To integrate with Koshelek Pay API, use the following parameters:
Parameter | Description |
---|---|
Login | Login for API request authentication (HTTP Basic Authentication is used) |
Password | Password for API request authentication |
API Base URL (test) | https://api-test.koshelek.app/<partner-name> |
API Base URL (production) | https://api.koshelek.app/<partner-name> |
Note that API Base URL is partner specific — that is, for partner with name name
, API Base URL will be as follows:
API Base URL (test): https://api-test.koshelek.app/name
API Base URL (production): https://api.koshelek.app/name
The following table defines merchant identifiers involved in data exchange via Koshelek Pay API. Parameters specified in color are applicable to payment via Faster Payments System ("FPS", also known as "SBP" in Russian).
Parameter | Context | Description |
---|---|---|
| General |
|
| General |
|
Stores: | General |
|
| General if cash desk has online host |
|
| General if cash desk has online host |
|
Terminals: | General |
|
| SBP |
|
| SBP |
|
| SBP |
|
| SBP |
|
| SBP |
|
| SBP |
|
| General if cash desk has online host | URL used by the cash desk for accepting transaction status updates from the Koshelek Pay server. |
API request authorization
API communication relies on HTTPS with HTTP Basic Authentication (RFC 7617) for request authorization. Request authorization credentials are passed in the Authorization
HTTP header.
Minimum requirement for TLS version: 1.2.
Message encoding
Both request and response messages use the UTF-8 encoding.
Message format and structure
API requests expect content type in header: Content-Type: application/json
and return response body in "application/json"
.
Last updated