This section provides integration scenarios and best practices for implementing Lean Disposable in your application.
Choose the enrollment flow based on your use case:
- Enroll with OTP by SMS — standard flow, OTP sent via SMS
- Enroll with OTP by email — OTP sent via email (LRA authorization required)
- Enroll without OTP — no OTP required (LRA authorization required)
- Enroll with external OTP — OTP managed externally, e.g. PSD2 banking flow (LRA authorization required)
- Enroll with eID assertion — enrollment via SPID, CIE, EUDIW, or other authorized eID
- Enroll with AML identification — enrollment via AML identification process (LRA authorization required)
- Workflow overview — full enrollment workflow with steps and required methods
- eID identification — supported eID types and field mapping
- How to handle errors — common errors and solutions
- Certificate serial number — how the serial number is composed
- Allowed characters — characters not allowed in holder fields
- Non-unique phone number (Error 10068) — how the uniqueness check works
The pages below describe a feature whose development has not started yet. They are published for review only: the contract may change and the functionality is not available in any environment.
- Understanding webhook — how the document preservation notification works, payload and retry behaviour
- Webhook configuration — URL requirements, host allowlist and JWS signature verification
For the full API reference, see the API References section.