Refund Rejection

Order/

Refund Rejection

Request

This endpoint enables merchant to formally reject customer refund requests initiated through the Keeta platform.

Notes:

When a customer submits a refund request on the Keeta platform, the system will send a webhook notification to the third-party system.
If the third-party system has implemented refund processing capabilities, merchants can review and evaluate customer refund requests directly within their own system endpoint.
When merchants decide to reject a refund request after careful consideration, the third-party system must explicitly call this rejection API endpoint to formally communicate the decision to Keeta's platform.
This API does not support duplicate calls. If the refund has already been approved or rejected (e.g., via Keeta POS), subsequent calls will return an error.

Bodyapplication/jsonrequired

orderViewIdinteger, (int64)required

Unique identifier for orders on Keeta platform

Example:756823555555859

shopIdinteger, (int64)required

Unique identifier of the Keeta store

Example:466663

rejectCodeintegerrequired

Reason code for refund rejection:

100000: indicates other unspecified reasons

100001: indicates meal preparation already completed

100002: indicates delivery process already initiated

Enum:100000100001100002

rejectReasonstring

The rejectReason field contains the merchant's textual explanation for refusing a refund request. This provides transparency to customers about the rejection decision.

When Using Custom Rejection Code (100000), The rejectReason field becomes mandatory.

For rejectCode = 100001 (meal already prepared) or 100002 (delivery already started), The rejectReason field is optional.

Example:"Your Reason"

curl -i -X POST \
  https://open.mykeeta.com/api/open/order/reject \
  -H 'Content-Type: application/json' \
  -d '{
    "orderViewId": 756823555555859,
    "shopId": 466663,
    "rejectCode": 100000,
    "rejectReason": "Your Reason"
  }'

Responses

Request executed successfully

Bodyapplication/json

codeintegerrequired

A numeric status identifier indicating the result of the interface call, used to determine whether the operation executed successfully.

Enum Value	Description
0	The request was executed successfully.
Non-zero value	The request execution failed. Specific error details can be viewed in the message field.

Example:0

messagestringrequired

Text description corresponding to the status code, explaining the operation result or error cause to users.

Example:"Success"

Response

{
  "code": 0,
  "message": "Success"
}