Skip to main content

​
You can use webhooks to get notified when:

  • A payment is initiated, completed, or fails
  • Funds are credited or debited from your account
  • Other key account or transaction events occur

​
1. How It Works

When an event occurs in LINK Bridge, we send an HTTPS POST request to your specified webhook URL. Your server processes the payload and responds with a 200 OK to acknowledge receipt.

​
2. Setting Up a Webhook

Step 1: Create your endpoint URL
  • This is where LINK will send event payloads
  • Must be a publicly accessible HTTPS endpoint
Step 2: Add your webhook URL
  • Go to your LINK Bridge Dashboard → Developers → Webhooks
  • Enter your webhook URL and save changes
Step 3: Verify webhook signing (recommended)

​
3. Receiving events

Every payload has the same envelope — an event name and a payload object — but the fields inside differ by corridor. Match on event, then read the fields for the corridor the transaction belongs to.
The two corridors do not share a payload shape. Direct FX identifies a transaction by transaction_id and reference; the Pan-African Ramp sends reference and business_id with no transaction id, and carries a human-readable Notification. Code that assumes one shape will break on the other.

​
Direct FX

Sent when a Direct FX on-ramp request is accepted.

​
Pan-African Ramp

The Pan-African corridor reports each stage of the transaction. All four carry Notification, reference, business_id, payment_type (onramp or offramp), transaction_status and date_updated.
Notification wording follows the direction: an off-ramp reads “Withdrawal Request Completed.” where an on-ramp reads “Deposit Request Completed.” Branch on payment_type and transaction_status rather than parsing the sentence.
On an off-ramp, payout_amount is the fiat the customer receives; on an on-ramp it is the stablecoin delivered. The unit is part of the string.

​
⚠️ Error Handling

If your webhook endpoint is invalid or fails to respond, LINK will retry the delivery up to two additional times.
  • If the webhook still does not succeed after the retries, the event is marked as failed.
  • Failed events are not automatically retried afterward, so it’s important to ensure your endpoint is reliable.
Processing Windows Multichain Static