Request API webhooks

Overview

Configure one HTTPS webhook URL in the Partner Portal (Settings → Webhooks). Request API deliveries use the same RaaS Widgets signing and retry model as every other partner event. Delivery headers: X-RAAS-Event, X-RAAS-Timestamp, X-RAAS-Signature. See Webhook security.

Events for request money

Event	When
`request_money.created`	Successful `POST /v1/request-money`
`request_money.failed`	Error on `POST` or `GET` under `/v1/request-money`
`operation.created`	Sender creates the fulfilling transfer (`requestId` present)
`operation.completed`	Transfer settled
`operation.failed`	Transfer failed
`operation.cancelled`	Transfer cancelled (including funding expiry)

request_money.updated is not emitted. Track payer progress and settlement with operation.* events. Correlate using requestId from request_money.created.

If you previously used older event names

Previous name	Current name
`operation_created`	`request_money.created`
`operation_updated`	Use `operation.created` / `completed` / `failed` / `cancelled`
`operation_error`	`request_money.failed`

Signature headers are the platform X-RAAS-* set (not the older X-Webhook-* names). Full catalog: Webhook events.

request_money.created

{
  "event": "request_money.created",
  "timestamp": "2026-07-23T14:30:00.000Z",
  "data": {
    "legacyOperationReferenceId": "Ab3xY9mK",
    "linkId": "link_acme_fund_req_01",
    "fundRequestLink": "https://<fund-request-host>/link_acme_fund_req_01",
    "landingLink": "https://app.example.com/pay?ref=Ab3xY9mK",
    "waLink": "https://wa.me/…",
    "referenceId": "Ab3xY9mK",
    "requestId": "req_abc123",
    "userReferenceId": "user-8842",
    "amount": 150.5,
    "currency": "GTQ",
    "status": "pending",
    "statusDetails": null
  }
}

Persist requestId and deliver fundRequestLink (or your landing / WhatsApp wrapper) to the sender.

request_money.failed

{
  "event": "request_money.failed",
  "timestamp": "2026-06-29T12:00:00.000Z",
  "data": {
    "path": "/v1/request-money",
    "method": "POST",
    "referenceId": "Ab3xY9mK",
    "errorCode": "OFAC_HIT",
    "httpStatus": 403,
    "message": "Identity check rejected: global.watch.list.ofac",
    "details": {
      "restrictionKey": "global.watch.list.ofac"
    }
  }
}

Emitted in addition to the synchronous HTTP error so systems that only consume webhooks still see create failures.

Settlement — operation.*

When the sender completes the fund-request flow:

operation.created — status: created, includes requestId
Later: operation.completed | operation.failed | operation.cancelled

There is no operation.expired; funding expiry maps to cancelled. Status meanings: Operation lifecycle.

Delivery and retries

Same as the platform: up to 5 attempts with backoff, 30s timeout, acknowledge with 2xx quickly, keep handlers idempotent. Details: Webhooks overview.

Next steps

Lifecycle

End-to-end ask → operation journey.

All webhook events

Full partner event catalog and payloads.

Security

HMAC verification examples.

Getting Started

Request API

Concepts

Integration

Flows

Webhooks

Operations

Overview

Events for request money

If you previously used older event names

request_money.created

request_money.failed

Settlement — operation.*

Delivery and retries

Next steps

Lifecycle

All webhook events

Security

​Overview

​Events for request money

​If you previously used older event names

​request_money.created

​request_money.failed

​Settlement — operation.*

​Delivery and retries

​Next steps

Lifecycle

All webhook events

Security

Overview

Events for request money

If you previously used older event names

request_money.created

request_money.failed

Settlement — operation.*

Delivery and retries

Next steps