Easily Integrate Unzer Webhooks with your application.

https://docs.unzer.com/reference/supported-webhook-events/

Steps to receive Unzer Webhooks

Sign up for your free Hooky account.
Create a new Webhook Source, and select Unzer. This will be the endpoint that receives webhooks on behalf of your application, and forwards them using the unified SDK.
Step 1
Step 2
Once a webhook is received from Unzer, you'll see it under the Live Logs section of your webhook source.
Next, follow the examples below to integrate the Hooky SDK in ruby or javascript, and start receiving webhooks.

Save countless hours integrating Unzer webhooks into your application.

Integrating Unzer Webhooks Using Javascript

Integrating Unzer webhooks with Hooky in your Javascript based application is straight forward. Just grab the SDK, and call a function when that webhook is received.

Integrating Unzer Webhooks Using Ruby

Integrating Unzer webhooks with Hooky in your Ruby or Ruby on Rails application is straight forward. Just grab the SDK, and call a method when that webhook is received.

Configuring Unzer Webhook Authentication

Here's how it works

Supported Unzer Webhook Events

authorize

Triggers a notification for all authorization related events.

authorize.succeeded

Triggers a notification for successful authorization creation events only.

authorize.failed

Triggers a notification for failed authorization events only.

authorize.pending

Triggers a notification for pending authorization events only. For example, an authorization, that needs the customers’ payment confirmation.

authorize.canceled

Triggers a notification for canceled authorization events only. For example, an authorization that is fully reversed.

charge

Triggers a notification for all charge related events. Including direct charge & charge after authorization.

charge.succeeded

Triggers a notification for successful charge events only.

charge.failed

Triggers a notification for failed charge events only.

charge.pending

Triggers a notification for pending charge events only. For example, a charge, that needs the customer’s payment confirmation.

charge.canceled

Triggers a notification for canceled charge events only. For example, a charge that is fully refunded.

chargeback

Triggers a notification for chargeback events only.

types

Triggers a notification for all payment resource creation events.

customer

Triggers a notification for all customer resource related events.

customer.created

Triggers a notification for successful customer creation events only.

customer.deleted

Triggers a notification for successful customer deletion events only.

customer.updated

Triggers a notification for successful customer update events only.

payment

Triggers a notification for all payment related events.

payment.pending

Triggers a notification when a payment is in pending state. This event is usually triggered when an authorization or charge which requires a customer confirmation is called.

Triggers a notification when a payment is in completed state. This event is usually triggered in the following scenarios: * When calling a direct charge, which does not require the customer’s payment confirmation. * When an authorization has been fully charged: calling a charge for authorization with the full amount of the authorization.

payment.canceled

Triggers a notification when a payment is in canceled state. This event is usually triggered when a the full amount of a payment is cancelled.

payment.partly

Triggers a notification when a payment is in partly charged state. This event is usually triggered in the following scenario: * When an authorization has been partly charged: calling a charge for an authorization with one part of the full authorization amount.

payment.payment_review

Triggers a notification when a payment is in payment review state. This event is usually triggered in the following scenarios: * When an authorization has been over charged: calling a charge for an authorization with an amount that is greater than the amount of the authorization. * When an authorization has been over charged: calling multiple charges for an authorization where the total amount is greater than the amount of the authorization.