Implementing Callbacks (Deprecated in v0.9)

Deprecated API Version: The v0.9 API has been deprecated and the callback functionality is no longer operational. Please upgrade to the v1.0 API for current functionality.

This guide explains how callbacks worked in the v0.9 API. For current implementation instructions, please refer to the v1.0 documentation.

How Callbacks Worked in v0.9

In the v0.9 API, Cryptofuse could notify your application about payment status changes in real-time through webhooks (callbacks). When you created a payment request with a callback_url, Cryptofuse would send HTTP POST requests to that URL whenever the payment status changed.

Callback Flow (Historical Reference)

1. You created a payment with a callback_url parameter
2. Customer initiated a payment to the provided cryptocurrency address
3. Cryptofuse detected the transaction on the blockchain
4. Cryptofuse sent a callback notification to your callback_url
5. Your server processed the notification and updated your system

Webhook Format (Historical Reference)

Cryptofuse sent JSON payloads with payment information:

{
  "event_type": "payment.status_updated",
  "payment_id": "550e8400-e29b-41d4-a716-446655440000",
  "status": "confirming",
  "crypto_amount": 0.05,
  "token": "USDT",
  "blockchain": "ETH",
  "transaction_hash": "0x4a9a3a8c9e67f4f4b5c6d7e8f9a0b1c2d3e4f5a6b7c8d9e0f1a2b3c4d5e6f7a8",
  "confirmations": 2,
  "custom_id": "ORDER-12345",
  "created_at": "2025-04-17T12:30:25.123Z",
  "updated_at": "2025-04-17T12:35:42.567Z"
}

Upgrading to v1.0

To upgrade to the v1.0 API callback system:

1. Update your API endpoint URLs from /v0/... to /v1/...
2. Obtain new API credentials through the Cryptofuse dashboard
3. Update your callback handler to process the v1.0 format (which includes additional security features)
4. Test your integration with the v1.0 webhook system

For detailed migration instructions contact our support team at [email protected].

v1.0 Improvements

The v1.0 API includes these improvements to the callback system:

• Webhook signing for security verification
• Configurable retry policies
• Webhook logs API
• Multiple webhook endpoints per account
• Test webhook feature

Please refer to the v1.0 documentation for current implementation details.