POST request to your registered webhook endpoint whenever a significant event occurs on your account. Each request contains a JSON payload describing the event type, when it occurred, and the relevant data object. You can register and manage webhook endpoints from Dashboard → Settings → Webhooks.
Before processing any webhook, you should verify the request signature to confirm it genuinely originated from RemitFlex.
Payload Structure
Every webhook request body follows the same top-level envelope:Unique identifier for this webhook event, prefixed with
evt_. Use this to deduplicate deliveries — RemitFlex may retry delivery if your endpoint does not respond with a 2xx status.The event type string, in the format
resource.action (e.g., payment.delivered). Use this to route the event to the appropriate handler in your code.ISO 8601 timestamp of when the event was generated. Use this to verify the event is recent and guard against replay attacks.
The event-specific payload. The shape of this object varies by event type and is documented in the sections below.
Event Categories
Payment Events
Payment Events
Payment events track the full lifecycle of a RemitFlex payment from creation through final fiat delivery.
| Event type | Trigger |
|---|---|
payment.created | A new payment has been created. |
payment.processing | The payment is actively being settled on-chain. |
payment.settled | The stablecoin has settled on-chain. |
payment.delivered | Fiat has been confirmed received by the recipient. |
payment.failed | The payment could not be completed. |
payment.cancelled | The payment was cancelled before processing. |
payment.created examplepayment.delivered examplepayment.processing examplepayment.settled examplepayment.failed exampleWhen a payment fails, the data object includes a failure_reason field with a machine-readable error code.payment.cancelled exampleConversion Events
Conversion Events
Conversion events are emitted when RemitFlex executes a stablecoin-to-fiat (or stablecoin-to-stablecoin) conversion as part of a payment or off-ramp.
| Event type | Trigger |
|---|---|
conversion.completed | The conversion finished successfully. |
conversion.failed | The conversion could not be completed. |
conversion.completed exampleThe data object includes conversion_id and converted_amount so you can reconcile conversion outcomes against your records.conversion.failed exampleOff-Ramp Events
Off-Ramp Events
Off-ramp events track stablecoin-to-fiat conversions and the subsequent bank transfer, from processing through confirmed bank receipt.
| Event type | Trigger |
|---|---|
offramp.processing | The off-ramp is being actively processed. |
offramp.settled | Conversion is complete and the bank transfer has been initiated. |
offramp.delivered | The destination bank has confirmed receipt of the funds. |
offramp.failed | The off-ramp failed at some stage. |
offramp.processing exampleofframp.settled exampleofframp.delivered exampleofframp.failed exampleCompliance Events
Compliance Events
Compliance events are emitted when RemitFlex’s automated screening flags a transaction for review, or when a manual review reaches a conclusion. Subscribe to these events to pause downstream processing whenever a transaction is under review.
| Event type | Trigger |
|---|---|
compliance.review_required | A transaction has been flagged and requires manual compliance review. |
compliance.approved | A previously flagged transaction has been approved after review. |
compliance.rejected | A previously flagged transaction has been rejected after review. |
compliance.review_required exampleThe data.review_id identifies the compliance case. Hold any related payouts until you receive a compliance.approved or compliance.rejected event.compliance.approved examplecompliance.rejected example