This reference is key for your comprehensive understanding of LOGPAY Token Service.
LOGPAY's APIs make use of RESTful conventions when possible and where it makes sense. All calls use the standard HTTP verbs to express access semantics, like GET, POST, PATCH, and DELETE. Other related conventions for our API can be found in the section below.
id property.snake_case.null value instead.API keys are supported to authenticate requests.
The keys are passed in via the HTTP header x-api-key.
curl --header 'X-API-Key: <SECRET>' \
--request POST 'https://test.token.logpay.de/...'The keys must be handled with care and kept secure. Never hardcode the API keys in your source code, but keep them solely on your backend systems.
Endpoints that return lists of objects support cursor-based pagination requests. By default, the API returns up to 50 objects per API call. If the number of objects in a response from a support endpoint exceeds the default, then an integration can use pagination to request a specific set of the results and/or to limit the number of returned objects.
If an endpoint supports pagination, the response body follows this structure:
{
"current_page": 1,
"page_size": 50,
"total_items": 200,
"total_pages": 4,
"data": [...]
}The single pages can be requested with query parameters:
| Parameter | Type | Description |
|---|---|---|
limit | integer | The maximum amount of objects to be returned on a page. |
page | integer | The requested number of the page to return. |
The API uses the standard errors to indicate the client errors on the service level.
The response payload for processing errors follows a standard format.
{
"status": "the HTTP status code",
"classifier": "the classifer of the error",
"message": "interesting for humans..."
}The processing errors refer to the primary functions of the LOGPAY Token Service and not necessarily to the related business logic. For example, a failed authorization due to insufficient funds will result in a 200 response, as the payment layer could successfully process the request (even though the business result is negative).
https://test.token.logpay.de/
LOGPAY Tokens are powerful instrument to manage card holder data in a PCI/DSS compliant way.
Achieve PCI / DSS compliance in almost no time using our certified managed compliance service.
Transparently use the cardholder data across all connected processors to implement a non lock-in acquiring setup.
For every card which is tokenized, network-tokens can be automatically provisioned. This allows for more secure transactions, better conversion, and ultimately lower processing cost.
All cards stored with LOGPAY can be managed via the endpoints in this section.
The CVC2 security code is only kept in an ephemeral cache for a few minutes. The API allows to manage this resource with these endpoints:
https://test.token.logpay.de/tokens/{id}
curl -i -X DELETE \
'https://test.token.logpay.de/tokens/{id}' \
-H 'X-API-Key: YOUR_API_KEY_HERE'https://test.token.logpay.de/tokens/{id}/security-code
curl -i -X GET \
'https://test.token.logpay.de/tokens/{id}/security-code' \
-H 'X-API-Key: YOUR_API_KEY_HERE'{ "security_code_available": true }
https://test.token.logpay.de/tokens/{id}/refresh-session
curl -i -X POST \
'https://test.token.logpay.de/tokens/{id}/refresh-session' \
-H 'X-API-Key: YOUR_API_KEY_HERE'{ "session_id": "1ffd059c-17ea-40a8-8aef-70fd0307db82" }
LOGPAY supports Network Tokens with major card schemes.
The lifecycle of network tokens is automatically managed. When activated a network token is automatically provisioned and maintained through its life-cycle.
The use of Network Tokens requires prior activation by your account manager.