> For the complete documentation index, see [llms.txt](https://developer.paywall.one/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.paywall.one/payment-orchestration-integration-document/callback-examples/general-communication.md).

# General Communication

**Example:** You have an address like <https://domain.com/paywall/generalcallback> and registered it in the Paywall panel. During the setup, you specified that only Refunds, Cancellations, and Partial Refunds should be sent to this address. In this case, Paywall sends notifications to the specified address only for payments in those specific statuses.

<table><thead><tr><th>Key</th><th>Description</th></tr></thead><tbody><tr><td><pre><code>Type
</code></pre></td><td><p>Notification Type</p><p><br>See: <a href="/pages/zEIvla8ZN22dNrlNQODr">Review </a></p></td></tr><tr><td><pre><code>PaymentId
</code></pre></td><td>Payment identifier</td></tr><tr><td><pre><code>Amount
</code></pre></td><td>Payment amount</td></tr><tr><td><pre><code>OperationAmount
</code></pre></td><td><p>The amount of the action taken on the payment.</p><p><br><strong>Example:</strong> If it is a partial refund, this represents the partial refund amount.</p></td></tr><tr><td><pre><code>IP
</code></pre></td><td>The IP address that sent the request to Paywall</td></tr><tr><td><pre><code>UniqueCode
</code></pre></td><td>Tracking number provided at the time of payment creation</td></tr><tr><td><pre><code>CurrencyId
</code></pre></td><td><p>Currency</p><p><br>See: <a href="/pages/bahfUMz1dqpN1ZCnpVtM">Review</a></p></td></tr><tr><td><pre><code>PaymentMethodId
</code></pre></td><td><p><strong>Payment method</strong></p><p><br>See: <a href="/pages/Ry0msBeuGT7JjG6Ij5BH">Review</a></p></td></tr><tr><td><pre><code>Installment
</code></pre></td><td>Payment installment value</td></tr><tr><td><pre><code>ChannelId
</code></pre></td><td><p>Payment channel ID</p><p><br>See: <a href="/pages/NNCAeMZE1felse8L3CY9">Review</a></p></td></tr><tr><td><pre><code>TagId
</code></pre></td><td>Payment tag ID.<br>This parameter is included if you provide it at the time of payment creation.</td></tr><tr><td><pre><code>DateTime
</code></pre></td><td>The date the payment was processed</td></tr><tr><td><pre><code>Hash
</code></pre></td><td><p>It is the Hash value used to verify that the request originated from Paywall. It is generated using the <strong>System Webhook Hash Key</strong> created in the Paywall panel.</p><p></p><p>The key mentioned above may vary depending on the value of the <code>HashKeyType</code> parameter. A dynamic structure should be implemented.</p></td></tr><tr><td><pre><code>HashFormat
</code></pre></td><td>The format type used to generate the hash value<br><br>See: <a href="/pages/CwGK9IsyjWbnxDaBvQOq">Hash Formats</a></td></tr><tr><td><pre><code>HashKeyType
</code></pre></td><td>The type of key used in generating the hash value<br><br>See: <a href="/pages/rGeM863mExwJKspEaXUG">Key Types</a></td></tr></tbody></table>

```csharp
public class GeneralCallbackModel
{
    /// <summary>
    /// This property indicates the type of payment as
    /// SuccessPayment - UnsuccessfulPayment - RefundPayment - CancelPayment - PartialRefundPayment
    /// </summary>
    public int Type { get; set; }
    public int PaymentId { get; set; }
    public decimal Amount { get; set; }
    public decimal OperationAmount { get; set; }
    public string IP { get; set; }
    public Guid PaywallUniqueCode { get; set; }
    public string MerchantUniqueCode { get; set; }
    public string TrackingCode { get; set; }
    public string UniqueCode { get; set; }
    public short CurrencyId { get; set; }
    public int PaymentMethodId { get; set; }
    public byte Installment { get; set; }
    public int ChannelId { get; set; }
    public int TagId { get; set; }
    public DateTime DateTime { get; set; }
    public string Hash { get; set; }
    public string HashFormat { get; set; }
    public short? HashKeyType { get; set; }
}
```


---

# 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://developer.paywall.one/payment-orchestration-integration-document/callback-examples/general-communication.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.