Portable Credentials

Portable, user-owned verification credentials.

LayerCred issues credentials that users control. A student verifies once and can present a time-limited, consent-based credential to any partner platform. No permanent records.

Request a pilot See the flow

What it is

A credential primitive, not a score.

🔑

User-owned

The credential belongs to the user, not your platform. They decide when and where to share it.

✋

Consent-based

Every share requires explicit user approval. Your platform requests; the user consents. No silent data flows.

⏱

Expires & revocable

Credentials auto-expire (e.g. 6 months). Users can revoke at any time. No permanent records.

How it works

Four steps. Minimal integration.

Request

Your platform requests a credential (e.g. "verified student").

Consent

The user approves sharing from their LayerCred wallet.

Verify

You receive a signed yes/no result + expiry date via API.

Expire

Credential auto-expires. User can revoke anytime. No stale data.

Example API response

{
  "credential_type": "student_enrollment",
  "status": "verified",
  "institution": "[verified institution]",
  "is_current": true,
  "verified_at": "2026-02-14T10:30:00Z",
  "expires_at": "2026-08-14T10:30:00Z",
  "badge": {
    "display": true,
    "type": "verified_student"
  }
}

For roommate & sublet platforms

Why platforms integrate LayerCred

✓
Reduce manual review workload: automated student verification replaces email/ID checks.
✓
Add a trustworthy "verified student" signal to profiles and listings.
✓
Minimize your data collection: you receive yes/no + expiry, not PII.
✓
Avoid permanent records: credentials expire and users can revoke.
✓
Ship in weeks, not months: one button, one endpoint, one webhook.

Pilot program

Lightweight integration. Clear signal.

Integration scope

One button ("Verify student"), one result endpoint or webhook, one admin view for status. That's the entire scope.

Timeline

2–4 week integration. Go live with first verified users within a month. Measure impact over 90 days.

What you receive

Signed yes/no credential with expiry, embeddable verification flow, trust badge for verified profiles, and a dashboard.

Support

Direct access to our engineering team via Slack or email throughout the pilot. Dedicated onboarding.

Pilot pricing available on request. We keep it simple.

Get pilot details

Security & Privacy

Consent required for every share. Credentials auto-expire. Minimal disclosure: your platform receives a yes/no result, not source documents or PII. Users can revoke access at any time.

Hard questions

Things people ask.

Is this a social credit score?

No. LayerCred issues specific, factual credentials (e.g. "this person is an enrolled student"). We don't rate, rank, or score people. A credential is a verified fact with an expiration date, nothing more.

Do you track users across apps?

No. The user controls every share. When a platform requests a credential, the user explicitly consents. We don't share data between platforms without user approval. There is no cross-platform tracking.

What data do you store?

Minimal. We verify a claim (e.g. student enrollment) and store the verification result, not underlying source data. We aim to minimize data retention. Verification results are time-limited and users control sharing.

Does the credential expire?

Yes. Every credential has an expiration date (e.g. 6 months). After expiry, the credential is no longer valid and must be re-verified. No stale data sits in your system.

Can users revoke access?

Yes. Users can revoke any credential at any time from their LayerCred account. Revocation invalidates the credential immediately across all platforms it was shared with.