Event Type Examples

This section provides complete request and feedback payload examples for each event type supported by the Mubeen risk validation API. Use these as reference when integrating specific event flows.

Monetary Event Types

Monetary events involve financial transactions and include the transaction_amount field with a non-zero value.

Event Type	Description	Page
payment	Payment transaction	View examples
checkout	Checkout / cart completion	View examples
transfer	Money transfer between accounts	View examples
refund	Refund processing	View examples
credit	Credit or top-up operation	View examples

Non-Monetary Event Types

Non-monetary events do not involve direct financial transactions. The transaction_amount field can be omitted or set to 0.

Event Type	Description	Page
signin	User sign-in attempt	View examples
registration	New account registration	View examples
email_change	Account email address change	View examples
phone_change	Account phone number change	View examples
password_change	Authenticated password change	View examples
security_settings_change	2FA / trusted devices / recovery options	View examples
listing	Content or product listing creation	View examples

Common Structure

All event type requests share the same endpoint and authentication:

POST https://api.sa.mubeen.ai/api/v1/generic/validate
X-API-Key: <your_key>
Content-Type: application/json

Every request should include the event_type. If omitted it defaults to checkout, and the value is not validated, so a typo is accepted silently and creates a new event type on your account. device_id is optional but strongly recommended — it's the primary device signal for fraud detection. timestamp is optional too — if omitted, the server's current time is used. Additional fields vary by event type — monetary events typically include payment and card fields, while non-monetary events focus on customer and device context.

For full field reference, see Server-Side Integration.