> For the complete documentation index, see [llms.txt](https://bhpaydocs.casheer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bhpaydocs.casheer.com/sample-code/3.-callback-merchant-portal.md).

# 3. Callback To Merchant Portal

### CallBack/ Response URL

```
<YourCallBackURL>?trackid=xxxx&result=xxxx&refid=&errormessage=&Hash=xxxx
```

### **Call Back Response Parameters**

| **Parameters**  | Data Type | Description                                                                             |
| --------------- | --------- | --------------------------------------------------------------------------------------- |
| `trackid`       | string    | Reference ID passed in the request.                                                     |
| `result`        | string    | <p>Payment result.<br>Example: CAPTURED, NOT CAPTURED, DECLINED, REJECTED, BLOCKED.</p> |
| `refid`         | string    | Payment Reference Number.                                                               |
| `error message` | string    | If result is other than CAPTURED, then it gives you the actual reason.                  |
| `hash`          | string    | Use this for integrity of the data explained in response integrity section              |

### How to identify parameters that are tampered?

If you want to check whether the parameters tamper or not, convert below parameters into a hash and compare with your hash which you got as a response in a query string.

Use the below method to identify parameter tempering. &#x20;

```
  String outParams = $"trackid={trackid}&result={result}&refid={refid}";
  String outhashValue = GetHashValue(outParams,_key);
  if (Hash != outhashValue)
  {
  //This means it is tampered
  // Your code
  }
  else{
  }
```


---

# 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://bhpaydocs.casheer.com/sample-code/3.-callback-merchant-portal.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.