The DPay Web EID identity verification platform (Identity Verification HUB) enables companies to verify user identities and retrieve bank account data through a REST API. All capabilities are available through one integrated API.
Available verification methods
| Method | Provider key | Description |
|---|
| Verification transfer | bank_transfer | PLN 1 micro-transfer and verification of the sender's details |
| mObywatel | mobywatel | QR code scanning in the mObywatel app |
| AIS/PSD2 | ais_psd2 | Access to bank account data through PSD2 |
| Demo | demo | Test provider with manual approval |
API architecture
| Environment | Base URL |
|---|
| Production | https://WSKAZANY_PRZEZ_SUPPORT.dpay.pl/api/v1 |
| Sandbox | https://WSKAZANY_PRZEZ_SUPPORT.dpay.pl/api/v1 |
- Format: JSON (Content-Type:
application/json)
- Authentication: Bearer token (API key in the
deid_live_xxx or deid_test_xxx format)
- Standard: OpenAPI 3.1
Where should I start?
- Generate an API key in the administration panel
- Create your first verification session - a four-step quickstart
- Learn about verification modes - single, sequential, pool and dynamic
- Configure webhooks to receive real-time notifications
Key concepts
- Verification session - a container for the verification process with its own lifecycle (
created → completed/failed/expired)
- Mode (
mode) - determines how verification proceeds: as a single step, multiple steps, a user choice or a dynamic flow
- Purpose (
purpose) - identity_verification (personal data) or account_data (AIS account data)
- Result - PII (personal data) returned after successful verification and encrypted with AES-256-GCM
Support