The wallet carries all three. Identity attributes verify the applicant, employment and income attestations come signed by whoever actually knows, and the same wallet produces a qualified electronic signature, which under eIDAS has the legal effect of a handwritten one across the EU.
Letting a property remotely breaks into three awkward pieces. Confirm the applicant is who they claim. Confirm they can afford it. Get a signature that holds up. Landlords collect payslip PDFs anyone could edit, chase employment letters, then either accept a weak click-to-sign or book an appointment.
Step 01
Request identity and address attributes so you know who you are dealing with before sharing property details.
Step 02
Employment status and income attestations arrive signed by the issuer, so the edited-payslip problem goes away.
Step 03
The tenant signs from the same wallet, and the signature carries the identity binding with it.
Rules in play
eIDAS 2.0 qualified electronic signature, national tenancy law
Live demo
We built Keystone, a company that does not exist, to show this running inside a finished product. The wallet flow in it is the real SDK.
Open the Keystone demoBuilt on Authbound Digital Signatures. One API key covers every flow you add later.