Webhooks

Webhooks send payment and checkout events from Yera Connect to merchant systems.

They are important because checkout does not always finish while the customer is still on the screen. A payment provider may confirm a payment later, or a customer may close the browser before returning to the store. Webhooks allow Yera Connect to update the merchant system when the final payment status is known.

Common events

1. payment.created
2. payment.redirected
3. payment.pending
4. payment.processing
5. payment.completed
6. payment.failed
7. payment.cancelled
8. payment.refunded

Why merchants need webhooks

Webhooks help merchants:

1. Update WooCommerce orders after payment.
2. Mark internal orders as paid or failed.
3. Reconcile transactions.
4. Trigger fulfillment.
5. Notify customer support when payment fails.
6. Debug payment problems from event history.

WooCommerce webhook URL

The WooCommerce plugin creates this endpoint inside WordPress:

https://merchant-store.com/wp-json/yera-connect/v1/webhook

Yera Connect sends normalized payment events to that URL so WooCommerce can update orders.

Custom webhook URL

For custom integrations, merchants can add their own backend webhook URL.

The URL should:

1. Use HTTPS.
2. Accept POST requests.
3. Read the event payload.
4. Verify the webhook signature if configured.
5. Return a successful HTTP status when processed.
6. Be reachable from the public internet.

Delivery headers

Every merchant webhook request includes:

Verify the signature against the raw request body before updating an order:

hex(hmac_sha256(webhook_secret, `${yera-timestamp}.${rawRequestBody}`))

Store yera-event-id after processing. If the same event arrives again, return success without applying the order update twice.

Payment completed confirmation

Treat payment.completed as the fulfillment signal only after the webhook signature is valid.

For WooCommerce stores, Yera Connect also sends the WooCommerce callback so the plugin can update the order note and status. Admins can confirm the same event in:

Admin -> PayGate Callbacks
Admin -> Sessions -> Session detail
Admin -> Webhook Logs

How to test webhooks

Run a sandbox checkout, then open the Webhooks page and confirm:

1. An event was created.
2. Delivery was attempted.
3. The destination URL is correct.
4. The response status is successful.
5. The linked payment session or transaction is visible.

What to check when delivery fails

1. URL uses HTTPS.
2. WordPress REST API is reachable.
3. Security plugin is not blocking requests.
4. Secret/signature configuration matches.
5. The event appears in dashboard webhook logs.

Merchant support tip

When contacting support about a webhook issue, include the webhook event ID, destination URL, payment session ID, transaction ID, and the response error shown in the dashboard.