> For the complete documentation index, see [llms.txt](https://docs.tutelar.io/tutelar-api-document/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tutelar.io/tutelar-api-document/tutelar-api-document-v2/fraud-detection-monitoring/refund-transaction.md).

# Refund Transaction

&#x20;            A refund transaction is the process where money is returned to a customer for a purchase they previously made. In the context of fraud detection, refund transactions can be flagged for investigation if they exhibit suspicious or unusual patterns, such as an unusually high frequency of refunds, refunds of large amounts, or discrepancies between the refund request and the original purchase details. These flags help identify potential fraudulent activity, ensuring the integrity and security of the transaction process.

### Header

| Name          | Value                     |
| ------------- | ------------------------- |
| Content-Type  | `application/json`        |
| Authorization | `Bearer eyJhbGciOiJ.....` |

## POST /api/v2/fraud-detector/transaction/refund

> Refund Transaction

```json
{"openapi":"3.0.0","info":{"title":"Refund Transaction API","version":"1.0.0"},"servers":[{"url":"https://secctrl.tutelar.io"}],"paths":{"/api/v2/fraud-detector/transaction/refund":{"post":{"summary":"Refund Transaction","requestBody":{"required":true,"content":{"application/json":{"schema":{"type":"object","required":["status","orderId","reason"],"properties":{"status":{"type":"string","description":"It is used to request the status of a refund for a transaction. The value should be one of the following: 'requested': Indicates that the refund has been requested but not yet processed. 'processed': Indicates that the refund has been processed.\n","enum":["requested","processed"]},"orderId":{"type":"string","description":"This key represents the Transaction Order ID. It is a unique identifier for the transaction associated with the order for which the refund is being requested."},"reason":{"type":"string","description":"This key is used to provide the reason for the refund. It explains why the refund is being requested, such as due to a product issue, service dissatisfaction, or any other relevant reason."}}}}}},"responses":{"200":{"description":"Refund status updated successfully","content":{"application/json":{"schema":{"type":"object","properties":{"success":{"type":"boolean"},"message":{"type":"string"},"data":{"type":"object","properties":{"orderId":{"type":"string"},"requestedDateTime":{"type":"string","format":"date-time"},"responseDateTime":{"type":"string","format":"date-time"},"processedTime":{"type":"integer"}}}}}}}},"422":{"description":"Invalid status","content":{"application/json":{"schema":{"type":"object","properties":{"success":{"type":"boolean"},"code":{"type":"integer"},"message":{"type":"string"}}}}}}}}}}}
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.tutelar.io/tutelar-api-document/tutelar-api-document-v2/fraud-detection-monitoring/refund-transaction.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
