Skip to main content

​
What are webhooks?

Webhooks are HTTP POST callbacks RaaS Widgets sends to your server when Partner events occur. Instead of polling, you get notified when:
  • A magic link is created or opened
  • An end user is created or gains a participation role (sender / receiver / claimer)
  • The platform needs additional user data for CIP, or CIP completes
  • An operation is created, receives a pickup PIN, completed, failed, or cancelled
  • A legacy Request Money or deferred payout API call succeeds or fails

​
Configuration

Configure your webhook URL in the Partner Portal:
  1. Open Settings → Webhooks
  2. Enter an HTTPS endpoint URL
  3. Save and copy the webhook secret for signature verification
Your endpoint must use HTTPS. HTTP endpoints are not supported.
Create-link callbackUrl is not a webhook override. It is the widget Return to app URL while the magic link is still valid. Events always go to this partner webhookUrl.

​
Request format

​
Headers

See Webhook security for verification.

​
Events

Full payloads: Webhook events. Status meanings: Operation lifecycle.

​
Delivery and retries

If your endpoint returns a non-2xx status or times out, RaaS Widgets retries with backoff (up to 5 attempts), for example:
  • Timeout: respond within 30 seconds
  • Success: HTTP 2xx
  • After the last failure, delivery is marked failed (replay from Partner Portal / support tools when available)
Return 200 immediately, then process asynchronously. Keep handlers idempotent — deliveries can repeat.

​
Best practices

Reject unsigned or invalid signatures before parsing business logic.
New event types may appear. Acknowledge with 200 and log unknowns.
Retain event bodies for audit and support — redact PII as required by your policy.

​
Sandbox testing

  1. Point the Partner Portal webhook URL at an HTTPS tunnel (e.g. ngrok)
  2. Create a sandbox link with raas_sandbox_*
  3. Confirm link.created, open the URL, then exercise data-request / operation flows as needed
  4. Pick a magic amount or cardholder directive to simulate reject, delay, fail, cancel, or a card-validation case

​
Next steps

Events

Payload reference for each event.

Payout code (PIN)

Pickup PIN via webhook or GET.

Security

HMAC verification examples.