This endpoint allows you to increase the authorized amount for an existing card transaction when the initial authorization is insufficient. The additional amount is appended to the original authorization, and the total authorized amount reflects both.
Transaction ID created in your system. It should be unique for each payment.
Your unique reference number for the specific operation. You can pass this value to reconcile different operations in a payment (authorization, capture, refund, etc) individually. It is recommended to limit the length to 18 characters so that it works for all payment methods. Allowed characters: (A-Z, a-z) and digits (0-9)
- Testhttps://test.computop-paygate.com/api/v2/payments/{id}/incrementals
- Productionhttps://www.computop-paygate.com/api/v2/payments/{id}/incrementals
curl -i -X POST \
-u '<username>:<password>' \
'https://test.computop-paygate.com/api/v2/payments/{id}/incrementals' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'Content-Type: application/json' \
-H 'Idempotency-Key: string' \
-H 'X-API-Key: YOUR_API_KEY_HERE' \
-d '{
"transId": "6B29FC40-1067-B31D-00DD010662DA",
"amount": {
"value": 10000,
"currency": "EUR"
},
"duration": 10
}'Successful operation
A unique identifier assigned by Computop Paygate to the payment. This ID remains constant throughout the lifecycle of the payment and is used to track and reference the payment across all subsequent operations, such as authorization, capture, refund, or cancellation.
A unique identifier assigned by Computop Paygate for each operation in the payment. For example: xId will be different for the authorization and capture operations of a payment whereas payId will be same.
{ "merchantId": "test-merchant", "payId": "some-pay-id", "xId": "some-x-id", "transId": "some-trans-id", "status": "OK", "responseCode": "00000000", "responseDescription": "success", "refNr": "some-ref-nr" }