Tag Chargeback Payment
Used to tag payment as chargeback when Merchants receive chargeback notifications via email or other communication channels. Can also be used to finalize a chargeback or revert a chargeback. Only Payments with PAID or PARTIALLY REFUNDED state can be chargeback.
Method: POST
Action: tag-chargeback
Request
Format: POST data
- action
required : string (32)
| Remark |
Sample |
| The action of this call, must be hardcoded to “tag-chargeback” |
tag-chargeback |
- timestamp
required : timestamp
| Remark |
Sample |
| The timestamp for this API call |
- |
- api_key
required : string (32)
| Remark |
Sample |
| Pipwave-assigned merchant’s API key |
123456 |
- pw_id
*required : string (32)
| Remark |
Sample |
| Pipwave’s transaction reference ID, either this or txn_id must be sent |
123456 |
- txn_id
*required : string (255)
| Remark |
Sample |
| Merchant’s transaction ID, either this or pw_id must be sent |
123456 |
- stage
required : string (32)
| Remark |
Sample |
| The stage of chargeback : either “disputed”, “chargeback”, "dispute won", "dispute resolved" or “chargeback reversed”. Payments from PAID or PARTIALLY REFUNDED state can be chargeback-finalized directly. |
initiated |
- reason
*required : string (32)
| Remark |
Sample |
| The reason that the Payment Gateway provided : either “unauthorized”, “non_receipt”, “not_as_described” or “others”. If this reference is being initialized (opening chargeback case), then this parameter is required. |
unauthorized |
Response
Format: JSON
| Remark |
Sample |
| Status of the request. Refer to appendix for list of possible values. |
0 |
| Remark |
Sample |
| Error message, if any |
- |
Signature
The data involved in generating the signature for this API are:
- timestamp
- action
- api_key
- pw_id, if provided
- txn_id, if provided
- stage
- api_secret
