Get paid in XLM the moment your credential is verified
Stellaroid Earn binds credential verification to an instant payout in one on-chain flow. Once an approved issuer verifies your credential, link_payment sends XLM straight to your verified wallet — typically in under five seconds, for a fraction of a cent. This is a live pilot on Stellar testnet.
Why proof and payment belong in one flow
Most tools stop at the credential. A graduate earns a badge, then waits days or weeks while an employer confirms it by email, runs a background check, and finally cuts a payment through net-30 terms and a platform that skims a cut. The proof and the payout live in two different systems, and the gap between them is where time and money leak.
Stellaroid Earn closes that gap. The same on-chain record that proves a credential is real is the record that unlocks payment. There is no second system to reconcile: when the contract marks a credential Verified, the employer can pay the exact wallet that owns it, and the money moves in the same flow.
- Verification and payment share one on-chain source of truth
- No invoice, no net-terms, no 30-day wait after work is verified
- Payment lands on the wallet the credential is bound to — not a routing account
The verify-then-pay flow, on-chain
Three contract calls carry a credential from issued to paid. An issuer calls register_certificate to bind a certificate's SHA-256 hash to a student's Stellar wallet; duplicate hashes are rejected on-chain. An approved issuer or the admin then calls verify_certificate, which sets the credential status to Verified and emits a cert_ver event anyone can audit on stellar.expert.
Only after that does payment open. link_payment transfers XLM via the native Stellar Asset Contract directly to the verified wallet and emits a payment event. On Stellar testnet, settlement is typically under five seconds and costs a fraction of a cent in network fees.
- register_certificate — anchor the hash to the graduate's wallet
- verify_certificate — trusted verification, status becomes Verified, emits cert_ver
- link_payment — XLM moves wallet-to-wallet via the native SAC, emits payment
Payment is gated on verification, by the contract
Binding proof to payment only matters if the payment cannot jump the queue. In Stellaroid Earn, it cannot. An employer cannot pay a credential that has not been verified — the contract blocks the write until a credential reaches the Verified state, and a revoked credential is rejected with a typed CredentialRevoked error.
The gate stays closed on bad credentials too. A revoked credential can no longer unlock payment (the contract returns CredentialRevoked), and suspended or expired credentials are not eligible for verification-based actions. The status that graduates and employers see on a proof page is the same status the contract enforces before it releases a single stroop.
- No payment to an unverified credential — enforced on-chain
- Revoked, suspended, and expired credentials cannot trigger a payout
- The proof page status and the contract's gate are the same record
The wedge: nobody else binds verify-then-pay
Credential platforms like Credly, Accredible, Dock, Blockcerts, and BCdiploma issue and display credentials. Background-check firms verify people. Neither side pays anyone. Stellaroid Earn sits at the intersection they leave empty: it verifies a credential and pays its owner in a single on-chain flow.
Because it runs on Stellar, the payout is near-instant and near-free, it moves wallet-to-wallet with no platform take rate, and every step — the verification and the payment — is a public event on stellar.expert. Anyone can open a proof page and confirm a credential with no wallet and no login; a wallet is only needed to issue, verify, or pay.
How it works
- 1
An issuer anchors the credential
A school, bootcamp, or employer calls register_certificate, binding the certificate's SHA-256 hash to the graduate's Stellar wallet. Duplicate hashes are rejected on-chain, so a credential cannot be silently overwritten.
- 2
An approved issuer verifies it
An approved issuer or the admin wallet calls verify_certificate with the hash. The contract sets the credential status to Verified and emits a cert_ver event that anyone can audit on stellar.expert — no email thread required.
- 3
The employer pays the verified wallet
With the credential verified, the employer calls link_payment to send XLM via the native Stellar Asset Contract straight to the graduate's wallet. It emits a payment event and typically settles in under five seconds for a fraction of a cent.
Why it holds up
Direct to the verified wallet
link_payment sends XLM through the native Stellar Asset Contract straight to the wallet the credential is bound to — wallet-to-wallet, with no platform take rate between the employer and the graduate.
Sub-5-second settlement
On Stellar testnet, a payment typically clears in under five seconds. There is no invoice to raise, no net-30 to wait out, and no batch run — the payout follows verification immediately.
A fraction of a cent in fees
Stellar network fees are tiny, so paying a graduate costs a fraction of a cent. The economics work for a single credential payout, not just large batches.
Payment gated on verification
The contract will not release funds to an unverified credential, and a revoked credential returns CredentialRevoked. Employers pay confirmed work, and only confirmed work.
Public, auditable payout
Verification emits cert_ver and payment emits a payment event, both visible on stellar.expert. The proof page shows the status; the chain shows the money moved.
No login to check the proof
Anyone can open a public proof page and confirm a credential without a wallet or account. A wallet is only needed to issue, verify, or pay on-chain.
Frequently asked questions
- How do I get paid in XLM when my credential is verified?
- Once an approved issuer or the admin verifies your credential with verify_certificate, an employer can call link_payment, which transfers XLM through the native Stellar Asset Contract directly to your verified Stellar wallet. On testnet it typically settles in under five seconds for a fraction of a cent, with no invoice and no platform fee.
- Can an employer pay before a credential is verified?
- No. The contract blocks payment to any credential that has not reached the Verified status — this is enforced on-chain by the contract itself. A revoked credential also cannot unlock payment; the contract returns a CredentialRevoked error.
- How fast does the payout settle and what does it cost?
- Payments run on Stellar testnet through the native Stellar Asset Contract, so settlement is typically under five seconds and network fees are a fraction of a cent. This is a live pilot on testnet, not a mainnet or production financial product.
- Does the payment go through a platform or middleman?
- No. link_payment moves XLM wallet-to-wallet, straight to the wallet the credential is bound to, with no platform take rate between the employer and the graduate. The transfer emits a payment event that is publicly auditable on stellar.expert.
- Do I need a wallet to view a proof of payment or verification?
- No. Verification is public and read-only — anyone can open a proof page and confirm a credential's status, its issuer's trust standing, and its on-chain events without connecting a wallet or logging in. A wallet is only needed to issue, verify, or pay on-chain.
- Is this real money on mainnet?
- No. Stellaroid Earn is a live pilot running on Stellar testnet. It is a free public demo with no purchase, subscription, or mainnet funds required, and it should not be treated as a mainnet or production financial product.
Try the live testnet pilot
Free public early access on Stellar testnet — no purchase, subscription, or mainnet funds required.