Sign PDFs with your wallet, and invite others to sign

Open the signing page, sign in, upload the PDF and click "Release for signing". Scan the QR code with the QR scanner in CodeB Wallet (on the phone itself, tap "Open in CodeB Wallet"). The wallet shows the document, you confirm, and the signed PDF appears on the page.

Yes. Invite them by e-mail when you create the request or later. They sign one after another on the same PDF; each person gets an e-mail when it is their turn and needs no account. At the end everyone gets a link to the signed PDF.

An advanced electronic signature with any signature source in the wallet, or a qualified electronic signature with a signature card whose certificate states a qualified signature. The signatures are PDF signatures (PAdES).

Only when the signer uses a signature card with a qualified certificate. The page shows "qualified" when the certificate states it (qcStatements); it does not check the certificate against the EU trusted lists. Self-signed certificates are never shown as qualified.

Every signed PDF must contain the earlier version byte for byte, followed by the new signature. The server verifies the signature and refuses updates that replace page content, add visible annotations or add content after the signature.

A request is open for 24 hours for your own signature and 72 hours for each invited person. Documents and signed PDFs are kept for 30 days after the request closes, or until you delete them.

It is designed to follow the EU Architecture and Reference Framework (ARF) 3.0, topic 16, and the OpenID4VP-based signing request of ETSI TS 119 432. ARF 3.0 does not yet define the trust set-up for signing requests, so CodeB Wallet recognises the website through a CodeB certificate until an access certificate from a national registrar is available. It is not certified.

Yes. The viewer on the signing page shows the PDF with its signatures on the right, like a desktop PDF reader: for each signature whether the signed part is unchanged, whether anything was changed afterwards, who signed, the certificate and its validity at the signing time, and the time stamp. A PDF you only look at before uploading is checked on request and not stored. Certificates are not checked against the EU trusted lists; "qualified" is shown only as stated in the certificate.

Yes, when a time-stamp server answers. CodeB Wallet asks the CodeB time-stamp service, with a second time-stamp server as fallback; the signature then carries a trusted time (PAdES-B-T). If neither answers, the PDF is still signed, with the signer's own time only (PAdES-B-B). The viewer shows which one a signature has.

The request list shows for the invited person whose turn it is whether the e-mail was handed to the mail server or failed, with a "Send e-mail again" button (at most 3 times, once a minute).

A guest account can sign 5 documents per day (UTC) with the CodeB signing service, can start up to 5 signing requests and invite up to 2 people per request. Signatures given as an invited signer in someone else's request do not count toward the daily limit. Signatures with your own signature card are not limited.

Open the signing page and sign in (a guest account is enough). To sign you need the CodeB Wallet app for Android, available at myeuid.app. CodeB Wallet is in closed beta; to become a tester, write to info@aloaha.com.