POSTCancel Subscription API
Use Case
This API is used to cancel the existing subscription using merchant’s credentials - This can be used by any subscription merchant. Token Type required here is AES.
Request Attributes
Head
Attribute | Description |
---|---|
clientId string(3) optional | Paytm use the merchant key on the basis of clientId parameter value. It requires only if the merchant has more than one key. Example: C11 |
version string(4) optional | Version of the API. Example: v1 |
requestTimestamp string(15) optional | EPOCH timestamp of the time at which request is being sent. |
channelId string(3) optional | The parameter value identifies the Channel for which API call is initiated. Possible values:
WEB
,
For websites, the value to be passed should be "WEB"
WAP
For Mobile websites/App, the value to be passed should be "WAP"
|
tokenType string mandatory | AES – signature is mandatory for checksum validation. |
signature string(108) mandatory | Paytm validates the request and ensures that parameters are not tempered by verifying the signature in the request. For creating the checksum (signature) refer to the steps given in Checksum Logic. |
Body
Attribute | Description |
---|---|
mid string(20) mandatory | Paytm provides MID as a unique identifier to each merchant. For your staging MID, click here. You get the production MID post the account activation. Example: INTEGR7769XXXXXX9383 |
subsId string mandatory | Subscription ID - Only Subscription flow |
Response Attributes
Head
Attribute | Description |
---|---|
version string(2) | Version of the API passed in the request. |
responseTimestamp string(15) | EPOCH timestamp of the time at which response is being sent. |
signature string(108) | You should validate the parameter values by verifying the signature comes in the response. It ensures that parameter values not tempered. Signature string can be verified by using Paytm checksum library. |
Body
Attribute | Description | ||||||||
---|---|---|---|---|---|---|---|---|---|
resultInfo object | This parameter gives the information about the result of the API response | ||||||||
ResultInfo +
| |||||||||
mid string(20) | Paytm provides MID as a unique identifier to each merchant. For your staging MID, click here. You get the production MID post the account activation. Example: INTEGR7769XXXXXX9383 | ||||||||
subsId string | Subscription ID - Only Subscription flow | ||||||||
custId string(64) | Customer ID whose subscription is being cancelled | ||||||||
createdDate string(15) | Creation date of subscription | ||||||||
expiryDate string(15) | Expiry date of subscription set at the time of creation |
Response Codes & Messages
code | status | message |
---|---|---|
200 | SUCCESS | Subscription is unsubscribed successfully. NO CONTENT FOUND (In case where subscription is already cancelled). |
400 | FAILURE | Subscription Id field can not be empty. Failed in cancelling subscription. Token not associated with subsId passed in request. MID not associated with subsId passed in request. |
401 | FAILURE | Authentication Failure. |
4001 | FAILURE | Invalid Subscription start date. Invalid Frequency Unit. |
curl -X POST 'https://securestage.paytmpayments.com/subscription/cancel' \
--header 'Content-Type: application/json' \
--data '{"body":{"mid":"{mid}","subsId":"67491"},"head":{"tokenType":"AES","signature":"{signature}"}}'