Class ReturnRefundsAPIResponse
Successful Response
If successful, the response body contains a newly created instance of
| Name | TYPE | REQUIRED | Description |
|---|---|---|---|
| Id | string | Yes | Unique EndToEndId reference for the transaction. RequestForRefund.Id |
| Status | string | Yes | Status of the Transaction. Enum values: Pending Pending - Successfully submit the RTP transaction to RTP Network. It's an Ack. Rule: Intimation of successful posting the transaction to Recipient via EES events. RequestForRefund.Status |
| Other fields in the Response | string | The remaining fields are replica of request (RequestForRefund) which is received. Where OriginalPaymentId contains the Id field's value in the Request. Refer the field's description in "Request body" section above. |
Failure Response
If failure, the response body contains a newly created instance of
| Name | TYPE | REQUIRED | Description |
|---|---|---|---|
| Message | string | Yes | Free text. Error Message. RequestForRefund.Message |
| Code | string | Yes | Error code RequestForRefund.Code |
| Description | string | Yes | Error description RequestForRefund.Description |
Successful Response - JSON representation
{
"RequestForRefund": {
"Id": string,
"Status": string,
"ReasonCode": "enum(reasoncode)",
"UserName": string,
"OriginalPaymentId": "string",
"Notes": "string"
}
}
Failure Response - JSON representation
{
"RequestForRefund": {
"Message": string,
"Error": {
"Code": string,
"Description": string
}
}
}
Sample Response: Success Scenario
{
"RequestForRefund": {
"Id": "123456789-RTP-JSHIR58756",
"Status": "Pending",
"ReasonCode": "CUST",
"UserName": "RTPUATUser",
"OriginalPaymentId": "123456789-RTP-IISQB45490",
"Notes": "This is test transaction"
}
}
Sample Response: Error Scenario
{
"RequestForRefund": {
"Message": "Validation failed",
"Error": {
"Code": "70040",
"Description": "Matching credit transfer record not found to initiate a refund"
}
}
}