Maintenance operations

Capture payments

If you have initially processed your transactions as authorisations (which have status.Output.statusCode=5), you need to capture them eventually to receive the funds. To do so, send a request to our dedicated CapturePayment endpoint:

{
  "amount": 1000,
  "isFinal": false
}

Property	Description
{merchantId}	Your account on our platform through which the initial transaction was processed. Add it as a path parameter to the CapturePayment endpoint Url.
{paymentId}	The payment.Id of the initial transaction which our platform returned in the CreatePayment/GetHostedCheckout request. Add it as a path parameter to the CapturePayment endpoint Url.
amount	The gross amount you want to capture for the original authorisation. If left empty, our platform will capture the full original amount.
isFinal	Define whether to close the transaction for subsequent captures if you only partially capture the amount. "true": The transaction will be closed for any further capture requests. "false": The transaction will remain open for subsequent (partial) capture requests for uncaptured amounts. If left empty, the default value is "false".

Cancel payments

If you have initially processed your transactions as authorisations (which have status.Output.statusCode=5), you can cancel them to unblock the funds. To do so, send a request to our dedicated CancelPayment endpoint:

{
  "amountOfMoney": {
    "amount": 1000,
    "currencyCode": "EUR"
  },
  "isFinal": false
}

Property	Description
{merchantId}	Your account on our platform through which the initial transaction was processed. Add it as a path parameter to the CancelPayment endpoint Url.
{paymentId}	The payment.Id of the initial transaction which our platform returned in the CreatePayment/GetHostedCheckout request. Add it as a path parameter to the CancelPayment endpoint Url.
order.amountOfMoney      amount      currencyCode	amount: The gross amount you want to cancel for the original authorisation. currencyCode: The ISO 4217 currency code for this amount. If left empty, our platform will cancel the full original amount.
isFinal	Define whether to close the transaction for subsequent cancellations if you only partially cancel the amount. "true": The transaction will be closed for any further cancellation requests. "false": The transaction will remain open for subsequent (partial) cancellation requests for uncaptured amounts. If left empty, the default value is "false".

Refund payments

You can reimburse successfully processed payments (which have status.Output.statusCode=9). To do so, send a request to our dedicated RefundPayment endpoint:

{
  "amountOfMoney": {
    "amount": 1000,
    "currencyCode": "EUR"
  }
}

Property	Description
{merchantId}	Your account on our platform through which the initial transaction was processed. Add it as a path parameter to the RefundPayment endpoint Url.
{paymentId}	The payment.Id of the initial transaction which our platform returned in the CreatePayment/GetHostedCheckout request. Add it as a path parameter to the RefundPayment endpoint Url.
order.amountOfMoney      amount      currencyCode	amount: The gross amount you want to refund for the original authorisation. currencyCode: The ISO 4217 currency code for this amount. If left empty, our platform will refund the full original amount.

Operation limits

Our platform implements limitations for maintenance operations that you can perform per individual transaction. This is a security measure that can help you identify issues in your server architecture, such as infinite loops or other flaws in your integration logic.

We distinguish between two types of limits:

• Soft limit: You can still process maintenance operations, but limited to one every 30 minutes. If you make more requests within these 30 minutes, our platform will reject it, resulting in errors.errorCode=50000429. This error indicates an unusual amount of maintenance operations for standard business use cases, possibly due to unintended infinite loops such as repeated refund retries.
• Hard limit: Your request is rejected as the transaction has reached the maximum number of allowed operations, resulting in errors.errorCode=50000430.

To avoid either limit, we recommend following these guidelines:

• Check your integration with our platform: For errors.errorCode=50000429, review your mechanism for requesting maintenance operations. Verify that retry requests have proper exit conditions and no infinite loops.
• Monitor operation counts: Send GetPaymentDetails requests to keep an eye on the number of performed maintenance operations per transactions. An unusually high number might indicate unintended workflows within your integration.
• Report exceptional business cases: Contact us if you require to exceed the soft/hard limit for specific scenarios.