Kushki Charges API
Direct charge against a previously created card token
Kushki Charges API is one of 12 APIs that Kushki publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
This API exposes 2 JSON Schema definitions.
Tagged areas include Charges. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a JSON-LD context, and 2 JSON Schemas.
This API exposes 2 operations across 2 paths, and defines 6 schemas. It is described by OpenAPI 3.1.0, at version 1.0.0.
Requests are made against 3 base URLs: https://api.kushkipagos.com, https://api-uat.kushkipagos.com, https://api-stg.kushkipagos.com.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 2
Kushki Charges API declares
2 security schemes
for authenticating requests.
An API key is passed in the header as Public-Merchant-Id (PublicMerchantId).
An API key is passed in the header as Private-Merchant-Id (PrivateMerchantId).
By default, every request must be authenticated.
PublicMerchantId— Client-side merchant key. Used by Kushki.js and mobile SDKs to tokenize cards. Never use server-side for charging.PrivateMerchantId— Server-side merchant key. Required for charge, capture, void, refund, subscription, and payout calls.
Paths & Operations 2
Across 2 paths, the API surfaces 2 operations — 2 POST. Each is listed below with its method, path, parameters, and response codes.
Direct charge against a previously created card token
Schemas 6
The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are ChargeResponse (10 properties), ChargeRequest (8 properties), Amount (6 properties), ContactDetails (6 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Kushki 11
Other APIs Kushki publishes across the network.