---
# System prepended metadata

title: Marketplace VC Use cases

---

# Marketplace VC Use cases

## Traditional KYC/AML Provider with "traditional" contracts
### Personas: 
- **Traditional KYC/AML Provider** that provides Online Verification Services for Service Providers that have to adhere to regulartory requirements.
- **Holder/Subject** of the Credential AND **User** (of the Service Provider)
- **Service Provider** offering an Online Service to its users.

### Use Case:
- As an online KYC provider I want to be able to offer my verification service transparently online to Service Providers who require KYCed customers, as well as user directly in order to increase the service usage.
- Technically KYC Credentials can be REUSED until revoked.
- As a KYC Provider I want to be reimbursed for reoccuring usage AND/OR a one-time issuing fee. The one-time issuing fee can be set against the serivce provider redirecting the user to the KYC service OR the user directly.
- As a KYC Provider I want to be able to set a transparent cost basis for the recurring AND/OR one time issuing fee.
- SPECIAL REQUIREMENT: As a service provider I want to be able to have special offers / contracts with service providers that consume my issued credentials.
    - Ideally these "special" conditions are not visible to the general public.
    - E.g. special offers could be models as a "Payback" mechansim outside of the VC Marketplace.
- As a KYC Provider I want to be able to charge for User or Service Provider initated credential revocation (Is that a good motivation?)


### Feedback:
- Privacy element: Generally utilization of a VC should NOT be transparent to the original issuer.



Other UC Repositories in the SSI Space:
- https://github.com/w3c-ccg/vc-ed-use-cases/issues
- https://docs.google.com/document/d/1dbWvs1m8uziTsbhUQv_nPofTXAyDSkxI5CZtoo1SlRY/edit?ts=5e85430a#