Refunds
Learn how to get refund transactions to your server via webhooks
This webhook service keeps you informed about any successful refund transaction triggered by the user or merhant including both one-time and subscription based payments.
Setup the Endpoint URL
Webhook events are sent to your server via HTTP POST
. You configure the endpoint URL through Developer Tools / Webhooks menu under your project.
Events Format
Webhook events are serialized in JSON. The body of a POST
request to your server will contain the serialized event.
Fields
queue | Webhook type and history. |
parameters | Details about the webhook. |
is_refund | This value is always sent as 1. |
refund_price | Refunded amount. |
refund_reason | Refund reason. |
credit_card | Credit card used in the transaction. |
status | Contains the transaction type associated with refund, possible values:
|
transaction_id | Unique ID of transaction. |
provider_transaction_id | Transaction ID in the relevant payment provider. |
currency | Currency used in the transaction. |
provider_name | Payment provider name. |
create_date | Transaction start date. |
subscriber_id | Subscriber ID associated with the transaction. |
custom_parameters | If the subscriber has custom parameters, they are sent in this field. |
original_purchase_date | Subscriptions original start date. |
package_id | ID of the package purchased. |
expire_date | Expiration date if it is a subscription purchase. |
purchase_date | The transaction completion date. |
payment_type | Contains the type of payment, possible values :
|
quantity | The number of items purchased. |
package_price | Standard package price. |
price | Transaction amount. |
Last updated