cancelUser
Vendo triggers the cancelUser postbackto indicate that a subscription has been canceled. The end user should retain access until the subscription reaches its expiration date. Once the subscription expires, Vendo will send the delUser postback.
Request parameters
Parameter | Data type | Description |
|---|---|---|
callback | string | Specifies the action for this request, which in this case is "cancelUser". |
username | string | End user's username. |
subscription_id | numeric | Vendo's subscription identifier. |
site_id | numeric | Vendo's site identifier. |
expiration_date | datetime | Date and time when the subscription should expire (timezone CET). Formatted as YYYY-MM-DD HH:MM:SS -Central European Time. |
is_test | boolean | Whether or not this request is related to a test transaction or subscription. |
reason_message | string | The reason why the subscription was cancelled. |
Your server must reply with one of these response formats:
OK (Response code 1)
Reply with this if the request was received successfully.
Example:
<?xml version="1.0" encoding="UTF-8"?>
<postbackResponse>
<cancelUser>
<code>1</code>
</cancelUser>
</postbackResponse>ERROR (Response code 2)
Reply with this if you encountered an unexpected problem with the request.
Include a custom error message with your message for tracing and debugging. Make sure this error message is meaningful, as it will be stored in a log file for later debugging.
Vendo will attempt a new cancelUser postback after your error response.
Example:
<?xml version="1.0" encoding="UTF-8"?>
<postbackResponse>
<cancelUser>
<code>2</code>
<errorMessage>Custom error message</errorMessage>
</cancelUser>
</postbackResponse>
Note for NATS usersNATS v3 doesn't support this postback. If you run NATS v3, you need to create a script to handle it. Contact Vendo support for more information.
Updated 9 days ago