Can verifiable credentials verify a foreign degree?

Yes. A diploma issued as a W3C Verifiable Credential verifies anywhere that reads the standard, so a degree issued in one country can be verified by an institution in another in seconds, without contacting the issuer.

You pick a VCALM provider and can swap it. You aren't locked to one wallet vendor or one stack, unlike the OID4VCI / OID4VP approach where interoperability is mainly at the wallet layer.

Issue and verify Diplomas, Certificates and other credentials with VCALM

Q: How do you issue a digital diploma?

Issue the diploma as a W3C Verifiable Credential over VCALM (the VC API). The university signs the credential and delivers it to the graduate's wallet over a short HTTP exchange. Any conformant wallet can hold it, and any institution can verify it cryptographically — no central identity provider required.

Q: Can you verify academic credentials online?

Yes. When a credential is issued as a W3C Verifiable Credential, an admissions office or employer verifies it instantly by checking its cryptographic proof and the issuer's identity — no phone calls to the registrar and no PDF forwarding, including across borders.

Issue diplomas, transcripts, and enrollment proofs that any wallet can hold and any institution can verify — without a central identity provider.

To issue a digital diploma, a university signs it as a W3C Verifiable Credential and delivers it to the graduate's wallet over VCALM (the VC API). Any conformant wallet holds it; any institution verifies it cryptographically — instantly, across borders, with no central identity provider.

University issues a diploma

Graduate clicks Add to wallet -- lands in seconds
Graduate holds it

In their wallet, on their phone, under their control
Admissions office verifies

Cryptographic proof -- no calls to the registrar

What it feels like to use

The technology is invisible by design. Here's what each person actually does — and what they no longer have to.

The university issues a diploma

A graduate clicks "Add to wallet" on the university portal — or scans a QR code at the ceremony. They pick the wallet app they already use. The diploma lands in it in seconds.

No new account. No vendor the university chose for them.
The graduate holds it

The diploma now lives in the graduate's wallet, on their phone, under their control — like a boarding pass or a payment card. It works even if the university's website is down years later.

They can move it to a different wallet whenever they like.
An admissions office verifies it

The graduate applies to a master's program abroad. The application page asks for proof of their degree. They tap "Share diploma", approve once, and the admissions office confirms it instantly — cryptographically, no phone calls to the registrar.

Verified in seconds, across borders, in any language.

What the graduate experiences

Three taps, not three weeks. Receive, hold, share.
Their choice of wallet. Not dictated by the school or a government list.
They stay in control. Nothing is shared without an explicit, one-time approval.
It keeps working. The credential doesn't depend on the issuer staying online.

What the institution experiences

No identity silo to run. You issue a credential; you don't host the user's login.
Instant, tamper-evident verification. No manual transcript checks.
No vendor lock-in. Pick a provider, swap it later, keep working with every wallet.
Cross-border by default. A diploma issued here verifies anywhere that reads the standard.

How it works

One diagram, three actors, one loop.

   ISSUER                 WALLET                 VERIFIER
 (university)         (student's choice)     (admissions office)
     |                      |                       |
     | -- delivers -->      |                       |
     |   diploma VC         |                       |
     |                      | <-- asks for --        |
     |                      |   proof of diploma     |
     |                      | -- presents -->        |
     |                      |   diploma VC           |
     |                      |                  verifies (ok)

A credential is just signed JSON the holder carries.
Delivery (issuer → wallet) and presentation (wallet → verifier) are the same simple exchange loop: POST, read what the server wants, POST back.
That loop is the entire "VCALM delivery" surface — the part that competes with OID4VCI/OID4VP, and it's short.

A good fit if…

You issue credentials people carry across institutions or borders.
You want recipients to control their credentials (no vendor lock).
You need verification that works across wallets.

Start building

Common questions

How do you issue a digital diploma?

The university signs the diploma as a W3C Verifiable Credential and delivers it to the graduate's wallet over VCALM (the VC API). See the issuer quick start.

Can you verify academic credentials online?

Yes — an admissions office or employer checks the credential's cryptographic proof and the issuer's identity instantly, with no calls to the registrar, including across borders.

Is there an API to issue student credentials?

Yes. VCALM (the VC API) is an open W3C HTTP API for issuing, presenting, and verifying credentials. What is VCALM?

Why VCALM vs. OID4?

You pick a VCALM provider and can swap it. You aren't locked to one wallet vendor or one stack. See the full comparison.