Deal amount changed

Emitted when an operator changes the amount of a live deal before PAYMENT_VERIFIED (the Amend operation). amount carries the NEW amount, old_amount the previous one, amount_version the monotonic edit counter (a new deal starts at 1, every edit increments it). Escrow holds are recreated for the new amount and the USDT equivalent is recalculated at the deal's own rate; the deal status does not change. V2 merchants only — the V1 adapter has no callbackType for this event and never delivers it.

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

The canonical webhook body for the merchant, sent on lifecycle events. Signed with the same HMAC-SHA256 scheme as incoming requests (the X-Signature header).

event*string

The event identifier (for example deal.completed).

deal_id*string

Formatuuid

merchant_id*string

Formatuuid

tenant_id*string

Formatuuid

amount*integer

The deal amount in minor currency units.

Formatint64

old_amount?integer

The deal amount BEFORE the change — present in deal.amount_changed only.

Formatint64

amount_version?integer

Monotonic amount-edit counter — present in deal.amount_changed only (a new deal starts at 1, every edit increments it).

Formatint64

currency*string

ISO 4217 currency code.

status*OrderStatus

The canonical V2 order lifecycle state (FSA). Exactly matches domain.OrderStatus and the OrderStatus proto enum.

Value in

"INITIALIZED"
"ESCROW_LOCKED"
"PAYMENT_NOTIFIED"
"PAYMENT_VERIFIED"
"COMPLETED"
"EXPIRED"
"CANCELLED"
"APPEALED"
"REFUND_PENDING"
"SPAM_REJECTED"
"SOFT_DISPUTED"

timestamp*string

The RFC 3339 event timestamp.

Formatdate-time

received_amount?integer

The actually received amount (differs from amount on partial/overpaid).

Formatint64

amount_match_status?AmountMatchStatus

How well the expected and the actually received payment amounts match. Values are lowercase strings.

Value in

"full"
"partial"
"overpaid"

provider_metadata?

Provider-specific passthrough data (deeplinks, payment page URLs).

fee_breakdown?

Merchant-side economics of the deal — deal.completed (PayIn) only, V2 only. All amounts are int64 in USDT cents (JSON strings, the proto3 JSON rule). The platform's internal costs are not disclosed: only the gross, the merchant's commission and the merchant's net go out; the promo fields are present only when a promo is applied.

Response Body

`application/json`

Example Requests

POST/deal.amount_changed

Request Body

Response Body

200application/json

Request Bodyapplication/json

`application/json`