Skip to main content

Get transaction details


GET /api/distributor/details

This GET method enables integrators to fetch detailed information about a previously created transaction.

Authentication

This endpoint requires an OAuth 2.0 Bearer Token. Pass the access_token obtained from the authentication flow in the Authorization header:

Authorization: Bearer <access_token>

Request details

Query parameters

ParameterTypeRequiredDescription
transaction_idnumberUnique identifier of the transaction in Keepz system.

Response details

✅ Success Response

If the request is valid, the API returns next payload:

{
"value": {
"transactionId": 26,
"status": "SUCCESS",
"statusDescription": "success",
"amount": 1,
"toIban": "GE34TB0000000000000000",
"currency": "GEL",
"paymentDescription": "string",
"uniqueId": "3fa85f64-1011-4562-b3fc-2c963f66afa6",
"createdAt": "2024-07-29T17:54:12.853213",
"commissionAmount": 0.01
}
}

Inside value object, the following parameters are available:

ParameterTypeDescription
transactionIdnumberUnique identifier of the transaction in the Keepz system.
statusstringCurrent status of the transaction. See Transaction Status Codes.
statusDescriptionstringHuman-readable description of the current transaction status.
amountnumberTransaction amount.
toIbanstringBeneficiary's IBAN.
currencystringTransaction currency. Possible values: GEL, USD, EUR.
paymentDescriptionstringNarrative/payment purpose text provided during creation.
uniqueIdstring (UUID v4)Unique transaction identifier provided by the client. Ensures idempotency.
createdAtstring (ISO 8601 datetime)Timestamp when the transaction was created.
commissionAmountnumberCommission fee applied to the transaction (if any).
❌ Error Response

If an error occurs, the API returns next payload:

{
"message": "Incorrect credentials",
"statusCode": 5021
}
ParameterTypeDescription
messagestringError message. Details are provided in the dedicated section below.
statusCodenumberError status code. Details are provided in the dedicated section below.

⚠️ Important: Make sure to include the Bearer token in the Authorization header for all requests. The transaction ID must be a valid number in the Keepz system.

Details can be found at Error Code Description.