Skip to main content
Order requirement webhooks notify your system when compliance opens an information requirement on one of your orders, and track it until it is resolved. A requirement is a request for supporting information or documentation about a specific order (for example, as part of enhanced due diligence). It carries a message describing what is needed and, while it is waiting on you, a deadline. These events allow you to:
  • Get notified as soon as an order needs supporting information
  • Surface the compliance message and deadline to the right team
  • Track the review progress after you respond
  • React to the final outcome (approved, rejected or expired)

​
Order Requirement Lifecycle

An order requirement follows this state flow:

​
State Definitions

​
Available Events

Each state transition fires the matching event:

​
Payload Fields

All six events share the same data structure:
  • requirementId — Unique identifier of the requirement
  • subjectType — What the requirement is attached to: ORDER or KYC_SESSION
  • subjectId — Identifier of that subject (the order id, or the KYC session id)
  • orderId — The order the requirement is attached to. Sent only when subjectType is ORDER, where it repeats subjectId.
  • merchantId — Your merchant identifier
  • previousState — The state the requirement was in before this transition. Omitted on requirement_created.
  • newState — The state the requirement transitioned to (matches the event)
  • message — Compliance message describing what is needed or the resolution. Included when provided.
  • expiresAt — ISO 8601 deadline to respond. Present only while the requirement is not in a final state.
Requirements are responded to from the RalioPay Portal. Branch on subjectType before correlating: an ORDER requirement blocks the operation identified by orderId, while a KYC_SESSION one concerns the verification of a user and carries no orderId.