Issuing your first digital credential: what to expect

Getting started with digital credentials sounds like a big project. In practice, issuing your first one is a short, well-defined path. Here’s what it looks like.

1. Book a pilot call

We start with a short call to understand what you issue today and what "verified" needs to mean for your verifiers. You leave with sandbox access and API keys.

2. Design the credential

Define the fields your credential carries and how it’s branded. This is where you decide what each credential asserts — a qualification, a licence, a membership — and what a verifier will see.

3. Issue from the API

A single REST call issues a credential to a holder. There’s no proprietary wallet to force on anyone: it’s a link by default, and works with any OpenID-conformant wallet if your holders prefer one.

4. Verify and go live

Anyone can verify the credential cryptographically — pass or fail, no manual follow-up. When you’re ready, the same API moves to production with no rebuild.

Most teams get to their first issued credential in under a day. We’re early-stage and founder-led, so you’ll be working directly with the people building Skippy.