Retrieve List of Payment Plans
This endpoint is used to retrieve list of Payment Plans
Retrieve a Payment Plan
This endpoint is used to retrieve a specific Payment Plan using the paymentPlanId
Create a Payment within Payment Plan
This endpoint is used to create a payment using the paymentPlanId
Cancel Payment Plan
This endpoint is used to cancel a Payment Plan
List payments within a Payment Plan
This endpoint is used to list all the payments within a Payment Plan
Create payment within payment plan
Transaction ID created in merchant's 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: letters (A-Z, a-z), digits (0-9), and the special characters - ? , ( ) + . ' :
- Testhttps://test.computop-paygate.com/api/v2/payment-plans/{paymentPlanId}/charge
- Productionhttps://www.computop-paygate.com/api/v2/payment-plans/{paymentPlanId}/charge
curl -i -X POST \
-u '<username>:<password>' \
'https://test.computop-paygate.com/api/v2/payment-plans/{paymentPlanId}/charge' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'Content-Type: application/json' \
-H 'X-API-Key: YOUR_API_KEY_HERE' \
-d '{
"transId": "string",
"refNr": "string",
"amount": {
"value": 0
},
"statementDescriptor": "string",
"order": {
"merchantReference": "string",
"invoiceId": "string",
"description": "string"
}
}'Success
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.
{ "paymentPlanId": "string", "payId": "string", "merchantId": "string", "transId": "string", "xId": "string", "refNr": "string", "status": "string", "responseCode": "string", "responseDescription": "string", "metadata": { "property1": "string", "property2": "string" } }