/events/consumer/user
endpoint allows you to operate on the Consumer User Events entity.
User events are created after the initial POST /consumer/users
call (which creates a user) and are used to:
userStateDetails
or kycStatusDetails
fieldupdatedConsumerUserAttributes
field.If you have neither of the above two use cases, you do not need to use user events.
Each user event needs three mandatory fields:
timestamp
- the timestamp of when the event was created or occured in your systemuserId
- The ID of the transaction for which this event is generated.In order to make individual events retrievable, you also need to pass in a unique eventId
to the request body.
Boolean string whether Flagright should allow a Consumer user event to be applied to a Business user with the same user ID. This will converts a Business user to a Consumer user.
Boolean string whether Flagright should lock the CRA risk level for the user.
Timestamp of the event
Transaction ID the event pertains to
Unique event ID
Reason for the event or a state change
Event description
Model for User details
Unique user ID
Timestamp when userId is created
Timestamp when user was activated
Model for consumer user personal details
User’s legal identity documents - See Document Model for details
Model for business user contact information details
Details of User’s employment
Model for transaction limits for a given user
Model for expected income details
Model for User acquisition channel
Timestamp of the last successful transaction of the user