# Rejected S2S Webhook Postback

## What is the Rejected Report Postback?

A Rejected Postback is a notification sent to external partners when they detect suspicious or fraudulent activities during the user interaction with campaigns or apps. Unlike standard postbacks, which are used to track conversions or user events, rejected postbacks signal that an event has been flagged due to abdonrmal behavior or policy violantions.

Each rejected postback contains a parameter called `{rejected_reason_id}`, which provides the specific reason for flagging the event.

You can configure your rejected postback by using the parameter we provide for the S2S Webhook postback, along with {rejected\_reason\_id}.

An example of a Rejected Postback URL looks like this:

```
https://yourdomain.org/postback?user_id={user_id}&...&payout=0&user_payout=0&rejected_reason_id={rejected_reason_id}
```

**Note:** `payout` and `user_payout` will be always set to 0 for rejected events.

### When a Rejected Report Postback is Triggered

A rejected postback is triggered in cases where an external system identifies behavior that doesn't align with expected norms. Each of these issues is represented by a specific `rejected_reason_id` in the postback.

### How to Set Up a Rejected Report Postback

To set up a Rejected Report Postback URL in our platform, go to the Settings page and navigate to the *Additional Postback (optional)* section located at the bottom left.

Select the option "*Rejected"* , enter the full Rejected Report Postback URL in the input field, and then click the button "*Add+".*

<figure><img src="/files/wj2yLX165rL0aqLkmDj9" alt=""><figcaption></figcaption></figure>

## Rejected Reasons Details

Each postback includes a `rejected_reason_id` parameter, which indicates why the event was flagged. The following table outlines the available rejected reasons and their severity.&#x20;

**Note**: We cannot prescribe specific actions, as enforcement is at your discretion. However, as a reference, here is the policy we apply on our own platforms:

* **High severity (first occurrence):** Immediate user ban
* **Multiple medium severity events within a 7-day period:** User ban
* **Low severity:** Used primarily to inform risk scoring and assess content quality

| ID | Severity |
| -- | -------- |
| 0  | Low      |
| 1  | High     |
| 2  | Medium   |
| 3  | Medium   |
| 4  | Low      |
| 5  | Medium   |
| 6  | Low      |
| 7  | Low      |
| 8  | Medium   |
| 9  | Low      |
| 10 | High     |
| 11 | Medium   |
| 12 | High     |
| 13 | Medium   |
| 14 | High     |


---

# Agent Instructions: 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:

```
GET https://docs.mychips.io/reward-handling/rejected-s2s-webhook-postback.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.