rSign IQES
In-App One-Time QES
Full Qualified Electronic Signature inside the banking app for already authenticated customers.
Bank acts as Registration Authority. QTSP issues a short-lived one-time Qualified Digital Certificate.
Highest legal validity — no branch visit required.
eIDAS Art. 25 equivalent
No branch visit
Session-only certificate
Reuses KYC + SCA
What is rSign IQES?
IQES (In-App QES) delivers a full Qualified Electronic Signature inside the banking application for customers who are already strongly authenticated.
1. Already authenticated
Customer is logged in with Strong Customer Authentication (SCA) inside the banking app.
2. Bank as Registration Authority
Bank re-uses high-assurance KYC performed at onboarding and confirms the current session.
3. One-time QDC
QTSP issues a short-lived Qualified Digital Certificate valid only for this signing session.
4. Full QES + Timestamp
Highest legal validity under eIDAS + qualified timestamp. Ready for long-term archiving.
OnePlatform. One API. All Signature Types.
Watch the short overview of the unified digital signing platform for banks.
From “click to sign” to full QES
Most banking apps today only offer simple or advanced electronic signatures. IQES changes that.
Click-to-Sign (SES / AES)
- Simple or Advanced Electronic Signature only
- Limited or no full legal validity
- Easy for customers to dispute later
- Weak evidence in court or complaints
- Not sufficient for many high-value contracts
- Creates residual legal & operational risk
Full Qualified Signature
- True Qualified Electronic Signature (QES)
- Legal effect = handwritten signature
- Strong non-repudiation
- Excellent evidence package
- Suitable for loans, guarantees, contracts
- Customer stays inside the banking app
How IQES works
Eight clear steps from document creation to archived Qualified Electronic Signature.
1. Document created
Banking app generates the PDF that needs to be signed (loan, guarantee, contract, etc.).
2. API call to rSign
Secure submit with customer data, session proof and document to the rSign platform.
3. Bank acts as RA
Bank confirms previous high-assurance KYC performed at onboarding + current SCA session.
4. One-time QDC issued
QTSP issues a short-lived Qualified Digital Certificate valid only for this signing session.
5. Customer confirms
Customer confirms the signature (OTP, biometric or app-native method already used for SCA).
6. Full QES created
Qualified Electronic Signature is applied to the document using the one-time certificate.
7. Qualified Timestamp
Trusted timestamp is applied (can be provided by a separate Time-Stamp Authority).
8. Archived & returned
Signed PDF/A with full QES + qualified timestamp is returned to the banking app — ready for long-term archiving.
Key benefits for the bank
Convenience for the customer. Highest legal strength for the bank.
Full legal validity
QES has the equivalent legal effect of a handwritten signature under eIDAS Article 25. Strongest possible evidence.
Risk reduction
Dramatically lower chance of successful signature disputes. Excellent non-repudiation package.
Higher conversion
Customer stays inside the banking app — no branch visit, no external tools, higher completion rates.
One API
Same rSign integration covers PAES, OQES, RQES and In-App One-Time QES. Minimal additional development.
Short-lived certificate
One-time QDC is valid only for the current session (minutes to a few hours). Minimises risk exposure.
Audit-ready output
Qualified timestamp + PDF/A ready for long-term archiving, verification and regulatory review.
Click-to-Sign vs rSign IQES
Same convenient in-app experience — completely different legal strength.
SES / AES only
- Legal strength: Weak
- eIDAS equivalence: Not equivalent
- Dispute resistance: Low
- Branch dependency: Still needed for many docs
- Evidence quality: Limited
- High-value contracts: Often not suitable
Full QES
- Legal strength: Full QES
- eIDAS equivalence: Handwritten signature
- Dispute resistance: Very high
- Branch dependency: Strongly reduced
- Evidence quality: QES + Timestamp + PDF/A
- High-value contracts: Yes
Legal basis under eIDAS
Why a one-time QDC based on previous KYC still produces a full Qualified Electronic Signature.
Legal effect of handwritten signature
Previous physical presence + SCA
Confirms KYC + current session
Session-bound qualified certificate
Trusted time evidence
Long-term archive ready
Where IQES sits in the rSign platform
One API covers all three channels: On-Site (PAES / OQES) · In-App (IQES) · Remote (RQES).
On-Site — PAES / OQES
Client identification in person at the branch. Clerk verifies identity. Signature pad or one-time QDC.
In-App — IQES (NEW)
Already authenticated customer. Bank as RA → one-time QDC from QTSP → full QES inside the app.
Remote — RQES
Existing digital identity / cloud QDC from trusted identity providers or national eID schemes.
Ready to offer full QES inside your banking app?
rSign IQES gives your customers the convenience of in-app signing
and your bank the legal strength of a Qualified Electronic Signature.
One API covers classic branch OQES, remote RQES and In-App One-Time QES.