Issue once. Verify anywhere.
Digital credentials anyone can verify in seconds.
Issue certificates, licenses, KYC results or payment histories that can't be faked and that anyone can check without calling you. No blockchain knowledge needed.
Built on![]()
In production. Used by real organizations.


135
credentials issued in production, led by BAF, a Latin American Web3 foundation
3
active pilots with external organizations
1st
digital identity standard on Stellar registered with the W3C, created by ACTA
01The problem
Information moves in seconds. Trust still starts from zero.
Certificates, licenses and credit histories live in PDFs and private databases: easy to fake, slow to check and impossible to reuse. A client can repay on time for years and still walk into the next lender with nothing it can check.
36payments on time
0a bank can verify
02How it works
Issue once. Verify anywhere.
One transaction per batch rather than one per credential. That keeps on-chain credentials affordable when you issue thousands at once.
- On-chain per batch
- 1 tx
- Personal data
- 0 bytes
- 01
Issue
An organization signs a W3C credential with its did:stellar. ACTA checks the signature before anything else happens.
eddsa-jcs-2022 · Ed25519
- 02
Anchor
Credentials are grouped into a batch. When it closes, only a Merkle root is written to your anchor contract on Stellar, in one transaction.
32-byte root · no personal data
- 03
Hold
The person keeps the credential with its proof, and shares it as a link or a QR code with any lender, employer or app.
Credential + Merkle proof
- 04
Verify
Anyone checks it on-chain in seconds, without calling the issuer: the signature, the proof against the anchored root and the revocation bit.
Three checks · seconds
03Platform
A credential is only as strong as its anchor.
Every credential is signed with your organization's own digital identity and anchored on a public network. If someone alters it, the check fails; if you revoke it, every verifier sees it. And it does not depend on ACTA to stay true.
- 01
Your own digital identity
Every credential is signed under your organization's own did:stellar. Your key, your signature, no intermediary issuing on your behalf.
- 02
Keys rotate
Replace or revoke a signing key and keep the same identity. Past credentials stay valid.
- 03
Issuers revoke
Withdraw a credential at any time. The revocation is public and permanent, and every verifier sees it at once.
- 04
No personal data on-chain
The ledger only holds 32-byte fingerprints and a revocation bitmap, on open W3C standards.
Same identity, new keys
Key 1revoked
Key 2rotated
Key 3active
did:stellar:mainnet:q4fz…7nka
the DID never changes
Unlocks →Credit historyReusable KYCDiplomas & skills
04Why ACTA
What institutions use today, and what changes
PDF certificates and e-signatures
Easy to forge, slow to check and impossible to withdraw once sent.
Cryptographically signed credentials with live status that anyone can check and you can revoke.
A central registry or database
Verification depends on your servers staying up, and a breach exposes personal data.
Proof lives on a public network. Personal data never touches the chain.
Building it in-house
Months of work on identity, signatures, anchoring, revocation and a verification page.
The full stack is ready: digital ID, issuing, anchoring, verification and revocation.
Credentials without an anchor
No public proof of when a credential was issued or whether it is still valid.
Every batch is anchored on Stellar and every revocation is a permanent public record.
05Use cases
Built for organizations that certify things.
If your organization vouches for something today on paper, by email or in a database, it can be a credential anyone can check.
06How it looks
Simple for your team. Ready for your systems.
Your team issues credentials from the ACTA app, with no technical knowledge and no crypto wallets. When you want to automate, your developers connect your current systems to ACTA in an afternoon.
- Try everything for free on a test network, then go live with the same setup
- Only your institution can sign its credentials. ACTA never holds your key
- Anyone can check a credential in seconds, without contacting you
ACTA app
07FAQ
Frequently asked questions
Anything else? Our team answers at hola@acta.build.
The technology stays. The complexity goes.
ACTA for your organization.
- 01No wallets: sign in with Google.
- 02Credential all your clients, students or members in one batch.
- 03A dApp built for institutional teams.
- 04Verification with zero dependency on ACTA.