Skip to main content
If your webhook endpoint missed a callback, or you need the full callback history for a transaction, you can view the callback delivery details, resend the latest callback, or export all callbacks for that transaction directly from the portal — for example, for debugging your integration or reconciling your records.
1

In your portal, go to Transactions and click the transaction whose callback you want to inspect.

A side panel with the transaction details opens.
2

Switch to the Callback tab.

You’ll see the delivery details for the latest callback sent for this transaction, including its status, HTTP response, and the request body that was sent.
3

To resend this callback, click Repeat callback.

CryptoProcessing resends the latest callback for this transaction to your registered callback URL.
4

To download the full callback history, click Export All Callbacks.

A CSV file containing all callbacks sent for this transaction — not just the latest — is downloaded.

​
FAQ

​
Why am I not getting a callback for a deposit?

CryptoProcessing only sends deposit callbacks for transactions to system deposit addresses — addresses created via the /v2/addresses/take API endpoint. Deposits to customer deposit addresses or merchant top-up addresses created manually in the portal do not trigger callbacks. If you were expecting a callback for a system deposit address but did not receive one, first check that your callback URL is set up correctly and reachable, then check its delivery status in the Callback tab and click Repeat callback to resend it.
Last modified on September 18, 2026