deprecated
This part of the guide is for a deprecated feature. Please do not use it for new implementations! The feature has been permanently or temporarily discontinued.
Feel welcome to ask our friendly help desk to understand the best options for your use case!
You may be looking for recurring payments, which can be used to implement flexible subscriptions in a web shop or other e-commerce application. Unlike subscription payments, flexible plans and processes can be implemented. The application then controls orders proactively instead of reactively depending on payment transactions.
The integration guide for such recurring payments is here: Recurring Payments
An active or suspended subscription can be cancelled. Cancelled subscriptions cannot be reactivated. There is another pair of endpoints to suspend and reactivate subscriptions.
In order to cancel the subscription you must call the endpoint POST /api/v2/Payment/Subscriptions/{id}/cancel:
POST /api/v2/Payment/Subscriptions/SUB_WNFRN9X2ZV8W3411BVM4D8UO6WJUOP/cancel HTTP/1.1Host: connect-testing.secuconnect.comAuthorization: Bearer qb56tjj1bcvo9n2nj4u38k84loContent-Type: application/jsonAccept: application/json{ "reason": "Not satisfied with the service"}The field reason is optional.
If everthing is fine, the API responds with 200 OK, and the representation of the Subcription object:
HTTP/1.1 200 OKContent-Type: application/json...{ "object": "payment.subscriptions", "id": "SUB_WNFRN9X2ZV8W3411BVM4D8UO6WJUOP", "status": "cancelled", "reason": "Not satisfied with the service"}The status canceled tells about the permanent deactivation.