State Bank of Pakistan
Secure Cheques.
Trusted Transactions.
DCVS enables digital cheque signing and verification through a national root of trust, ensuring authenticity, traceability and confidence in every transaction.
- Keys made on hardware, never exported
- Checkable from a photo of the paper
- Every action on a tamper-evident ledger
SBP
Root of Trust
Banks
Digital Certificates
Cheques
Digitally Signed
Public
Verification
Every cheque traces back to one root
Digital Cheque
Signed at issue
No. 004127
Valid · chains to the SBP root
State Bank of Pakistan · Karachi
Root of trust
Every chain ends here
About DCVS
One national root of trust for the cheque.
DCVS is the State Bank of Pakistan's framework for cheques that carry their own proof. SBP certifies each commercial bank. Each bank certifies its own account holders and issues them cheque books, and every leaf can be verified on its own.
Every action is written to a hash-chained audit ledger: registering a bank, issuing a certificate, revoking one. That ledger is anchored to a Hyperledger Fabric network, and SBP and the banks each hold a copy. To rewrite history, someone would have to rewrite every copy at once.
- The State Bank of Pakistan runs the root certificate authority
- Banks are certified one at a time, and can be revoked centrally
- Revoking an account holder cascades to every leaf they hold
- The public verifier is read-only and holds no keys
What makes a cheque trustworthy
Proof that travels with the cheque.
A DCVS cheque carries its own evidence. Whoever holds it can check it against the SBP registry in seconds, with no account and no phone call. That includes the teller, the payee and the auditor.
Tiers of trust
SBP root, bank, account holder
Signatures on every cheque
One in the QR code, one inside the PDF
Checks per verification
From the registry to the values signed
Private keys ever exported
Generated on hardware tokens and kept there
Built into every tier
Keys stay on the device
Made on the token, never copied off it
Readable from paper
The QR carries the signed values
Revocation that cascades
Revoke a holder and every leaf follows
Audit witnessed on Fabric
SBP and banks hold the ledger
Live verification
Ten checks. One verdict.
Drop in the cheque's PDF. The verifier reads its codes, walks the chain back to the SBP root and reports every check separately, so a failure tells you exactly which check failed. Only have the paper? A photo of it works too.
Pass. The check holds.
Advisory. Reported rather than decided. A joint cheque still awaiting a signature is unfinished, not forged.
Fail. If a signature is present and does not verify, the cheque fails. Always.
Verifying
Cheque No. 004127
0/10
Registry
The issuing bank is on SBP's register
Digital signature
Verifies under the bank's registered key
Chain
The bank's certificate chains to the SBP root
Current record
This is the current version of the leaf
Revocation
Leaf, account holder and bank are all live
Expiry
The bank's certificate is still in date
Signature inside the PDF
The embedded signature is intact
Account holder's signature
Made by a signatory of this account
Signatures required
As many as the mandate demands
Values signed
Amount, payee and date match what was signed
Walking the chain back to the SBP root…
How it works
From the root of trust to a verified cheque, in four steps.
- 01
SBP certifies the bank
The State Bank registers each bank and signs its certificate. The bank's key pair is generated on its own hardware token and never leaves it.
- 02
The bank certifies its signatories
Opening an account issues each signatory a certificate for a key on their own device. A joint or company account also carries a mandate: one signature, or all of them.
- 03
Cheque books are issued, signed
The bank signs every leaf at issue, twice. One signature covers its values in the QR code. The other sits inside the PDF, so any PDF reader shows it as signed.
- 04
Anyone verifies
Drop in the PDF, or a photo of the printed cheque. The verifier walks the chain to the SBP root and checks revocation, expiry and the signatures. No sign-in is needed.
Help
Questions, answered.
For a question about a specific cheque, ask the bank that issued it. Bank staff can contact the State Bank's Digital Financial Services Group.
How do I verify a cheque?
Open the verifier and drop in the cheque's PDF, or a photo of the printed cheque from any camera. You can also paste the text from its QR code. You don't need an account or a sign-in.
What does a valid result actually tell me?
That the bank on the cheque is registered with SBP, and its certificate chains to the SBP root and is still in date. That the cheque's signatures verify. And that neither the leaf, the account holder nor the bank has been revoked.
What happens if someone alters a cheque?
The signatures cover the values they attest to. Change the cheque number or the account and the bank's signature fails. Change the amount, payee or date after the account holder has signed and the values check fails. Either way, the result names the check that failed.
Can a revoked cheque still pass?
No. A signature that has been made keeps verifying forever, so the verifier also reads the live status of the leaf, the account holder and the bank. Revoking an account holder cascades to every leaf they hold.
Why does a joint cheque say a signature is outstanding?
A joint or company account's mandate can require more than one signature. A cheque with fewer is reported as unfinished rather than invalid: it hasn't been forged, it just isn't complete yet. The number required comes from the registry, never from the cheque itself.
How does a bank get access to the Bank Console?
The State Bank registers and certifies each bank through the SBP Certificate Authority. Once a bank is certified, its administrators sign in to the Bank Console with the credentials issued to them.
Before you accept a cheque
Check it. It takes seconds.
No account and no phone call. The verifier tells you whether the cheque chains to the SBP root, and exactly what it found.