-
- abort-payment-on-terminal
- capture-payment
- filter-payments
- find-payment
- initiate-payment-flow
- list-activity-logs
- list-payment-activities
- list-payments
- list-payments-by-contact
- list-payments-by-terminal
- refund-payment
- request-payment
- resume-payment-on-terminal
- retrieve-refund-performance
- retrieve-sales-performance
- reverse-payment
- start-payment-on-terminal
- void-payment
Challenge dispute
Confirms the submission of evidence and formally challenges the dispute.
A non-refundable challenge fee is charged to the merchant's balance via the daily statement upon submission. This fee is waived if the original payment was protected by 3D Secure. Failure to challenge the dispute within the deadline results in an automatic loss in favor of the customer.
dispute_id
string
Required. The unique identifier of the dispute (dsp_...)
NOT_FOUND
The specified dispute was not found.
INVALID_TRANSITION
The dispute is not in a state that can be challenged (e.g., already won or lost).
MISSING_EVIDENCE
No evidence has been uploaded for this dispute action.
UNHANDLED_ERROR
This error occurs when the server encounters an unexpected internal error that it cannot handle gracefully. This typically happens due to bugs, infrastructure issues, or edge cases that weren't anticipated during development.
INVALID_ARGUMENTS
This error occurs when the request contains invalid or missing parameters. Common cases include missing required fields, or values that don't match the expected format or type.
BAD_VERSION
This error occurs when making requests to an API version that does not exist. This commonly happens when using an outdated SDK or when the API version specified in the request URL is incorrect.
curl "https://api.reservepay.com/merchants/challenge-dispute" \
-X POST
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-H "Authorization: Bearer $(RESERVEPAY_API_KEY)" \
-d '{
"dispute_id": "dsp_01kwbby4c702mbq2htbbwnywhd"
}'
