BlackOakAdmin

Compliance

Where the Marketplace stands against its obligations — credentials, the restrictions in force, what has been denied, and who changed what.
0ExpiredNothing lapsed
0Expiring within 365 daysRenew before they lapse
1Restrictions in forcePolicy set v3
0Denials recordedAt checkout, booking, fulfilment or return
ExpiryRestrictionsDenialsAudit history
Looking ahead:Expired only7 days30 days90 days1 yearExpired records always show, whichever you pick.
Nothing lapsed or lapsingNo credential or document expires within 365 days.
Changing configurationThis screen shows the compliance position; it does not change it. Editing restrictions, attestations and thresholds is the administrative configuration interface (WBS 10.17), which is Phase 2. Until it ships, configuration changes go through the compliance team.

How this step works

SIPOC
Who supplies this step, what it needs, what it does, what it produces, and who uses the result. Suppliers and customers are links — follow them to walk the workflow, including into the consumer and merchant apps.
SuppliersWhere the work comes from
InputsWhat this step needs to do its job
  • Credential and licence expiry across merchants
  • Restriction and attestation coverage
  • Outstanding compliance actions
ProcessWhat happens here, in order
  1. Show where the Marketplace stands against its compliance obligations
  2. Flag credentials expiring or expired
  3. Point the operator at the merchant or product to fix
OutputsWhat this step produces
  • A compliance position
  • A list of things to remedy
CustomersWho uses that output next
How this step works