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.
In your portal, go to Transactions and click the transaction whose callback you want to inspect.
A side panel with the transaction details opens.
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.
To resend this callback, click Repeat callback.
CryptoProcessing resends the latest callback for this transaction to your registered callback URL.
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 or withdrawal?
Deposits to customer deposit addresses created in the portal, withdrawals initiated in the portal, and individual withdrawals created through a mass payout don’t trigger callbacks unless you enable business wallet transactions callbacks, see Configure callbacks.
If you were expecting a callback 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.
Why am I not getting a callback for a payment request created in the portal?
Payment requests created in the portal don’t trigger callbacks — only payment requests created via the API do. Last modified on September 30, 2026
