Consent Management
Overview
Every member enrollment requires explicit consent to the partner data policy. Your integration must present the consent request to the member and pass the accepted policy version to Otonum at enrollment.
Enrollment and Consent
When a member enrolls, include consent details in the enrollment payload. For exact request formats, use the API Reference.
The consentPolicyVersion must match the current active data policy version configured in the Rewards App. Outdated versions are rejected.
Displaying Consent
Your UI must display the policy terms and record explicit acceptance before enrollment is sent. Otonum stores the policy snapshot at consent time, but presenting and collecting consent remains your responsibility.
Do not call enrollment before explicit informed consent is collected. Passing a policy version without presenting the corresponding policy creates a compliance risk.
Consent Withdrawal
To withdraw consent and unenroll a member, use the withdrawal operation in the API Reference.
After withdrawal, the member cannot earn or redeem rewards until re-enrollment with fresh consent.
Policy Updates
When policy content changes, publish a new policy version in the Rewards App. Existing enrolled members keep consent under their accepted version. New enrollments must reference the latest version.
If regulations require re-consent after policy updates, detect enrolled members on older versions and prompt them to re-consent.
Key Points
jurisdictionCodeis set at tenant level and is not passed per enrollment request.- Consent records are immutable. A new consent record is created on each enrollment.
- Consent withdrawal does not delete member transaction history. Data retention follows applicable regulations.
See Also
- Consumer Consent: Conceptual consent and versioning model
- Quick Start: Enrollment overview