Webhook Structure
The webhook currently has the following structure:Categories
Nickel currently supports the following webhook notifications:payment.made
This notification fires when a payment is made.payment.failed
This notification fires when a payment has failed, such as when an ACH return occurs.payment.refunded
This notification fires when a payment has been refunded.payment.voided
This notification fires when a payment has been refunded, but it has not yet been sent to the ACH network or submitted for settlement to the card networks and thus was effectively canceled.disbursement.pending
This notification fires whenever a disbursement is created and is set to be sent out to your bank account on file.disbursement.succeeded
This notification fires whenever the receiving bank receives the funds. This may not necessarily be the same time as it appears in your bank account depending on your bank’s turnaround time.charge_authorization.authorized
This notification fires whenever your customer authorizes a payment method to be charged by you.charge_authorization.deleted
This notification fires whenever your customer or you delete an authorization to charge a payment method on file.Consuming Events
Individual Events don’t contain very much information on their own. This is by design, as the API structure can remain extremely stable and avoid difficult webhook migrations in the future as the Nickel API changes. If you need additional metadata, such as the amount of the Disbursement in the above example, make aGET request to the API for that information. You can use the associated_object_type or category fields to determine what resource to fetch from the API.