Skip to main content
When you initiate a payout, the payment enters PENDING status while Circle processes the fiat leg. Your application cannot poll the /pay response for a final result—Circle posts the outcome asynchronously as a webhook event. Meterlane exposes a webhook receiver that Circle calls directly; when a matching event arrives, Meterlane updates the payment status in your account and you can react to it from your own systems.

​
Webhook endpoint

Register the following URL as your webhook destination inside the Circle developer dashboard under Notifications → Webhooks.
You do not need to build or host a receiver yourself—Meterlane handles ingestion. What you do need is to ensure Circle is configured to send payout events to the address above so the status transitions happen in real time.

​
Signature verification

Every request Circle sends to the webhook endpoint includes a Circle-Signature header. Meterlane verifies this signature using HMAC SHA-256 computed over the raw request body and your configured webhook secret. Requests that arrive without a valid signature are rejected with a 401 response and never processed.
Meterlane performs the signature check on your behalf. You do not write verification code—just make sure the webhook secret configured in your Meterlane account settings matches the one in your Circle dashboard.
The verification algorithm, for reference:
Circle uses a hex-encoded digest. Meterlane compares the values using a constant-time comparison to prevent timing attacks.

​
Payment status events

Circle emits three event types that affect corridor payment status. Meterlane maps each event to a final payment status.
A payment in COMPLIANCE_HOLD status is not failed—it is paused pending review. Do not re-submit the payout or cancel the quote until you have contacted support and the hold is resolved.

​
Example webhook payload

When Circle fires a payments.payment_completed event, the payload looks like this:
The data.id field contains the Circle CPN payment ID. Meterlane matches this value against the cpnPaymentId returned in the original /pay response and updates the corresponding payment record.
Store the cpnPaymentId from the /pay response alongside your internal order record. If you need to reconcile a webhook event manually, compare data.id in the webhook payload against the cpnPaymentId you stored.

​
Confirming payout settlement

Because final status arrives via webhook, build your integration around event-driven status updates rather than polling. Here is the recommended pattern:
  1. Call POST /corridors/:id/pay and store the returned paymentId and cpnPaymentId in your database.
  2. When Meterlane receives the Circle webhook, it updates the payment record to SETTLED, FAILED, or COMPLIANCE_HOLD.
  3. Reflect the updated status in your application by checking the payment status via your dashboard or by building a thin status-check endpoint that queries your stored paymentId.
Meterlane acknowledges every webhook from Circle with a { "received": true } response immediately after processing, regardless of whether a matching payment record was found. This prevents Circle from retrying deliverable events unnecessarily.

​
Troubleshooting