Webhook Setup Primer

Webhooks notify your server when payments succeed, fail, or are refunded. Configure them early in technical onboarding so you can validate the full flow on Fin staging.

Why webhooks matter

Approach	Limitation
Redirect to `successUrl` only	Customer can close browser before redirect — not proof of payment
Polling status API	Works, but slower and misses async updates
Webhooks	Real-time, server-to-server confirmation

❗️
Always confirm payment via status API or webhook — never trust successUrl alone.

Minimum requirements

Requirement	Detail
HTTPS URL	Publicly reachable TLS endpoint
POST handler	Accept `application/json` body
Idempotency	Same event may arrive twice — dedupe by `transactionId`
Fast response	Return `200` within 5 seconds, process async if needed

Setup steps

Choose URL — e.g. https://yourstore.com/webhooks/digetpay
Implement handler — see Handle Webhooks and PHP examples in Hosted Checkout
Register in dashboard — Settings → Webhooks (staging: fin-admin.digetpay.com)
Test on Fin — complete a payment and verify delivery

Full guides:

Configure webhooks

Dashboard and Portal API registration.

Verify signatures

Validate webhook authenticity.

Event payloads

Fields and status mapping.

Staging vs production

Register separate webhook URLs (or separate paths) per environment. Use Fin staging keys only against staging endpoints.