Provider guides¶
QoreID, Mono, and IdenVault share the Identity manager but expose different operation families. Check a provider's optional capability interfaces before calling provider-specific methods.
| Provider | Default? | Credential | Main capabilities |
|---|---|---|---|
| QoreID | Yes | Client ID and secret | Digital identity, biometrics, business, bank, address, assets, background, sessions, workflows |
| Mono | No | Secret key | Identity Lookup, BVN iGree, CAC, Watchlist, Prove |
| IdenVault | No | API key | NIN/BVN/demography, bank account verification, account metadata |
Choose a provider¶
use Alphabalex\IdentityMadeEasy\Facades\Identity;
$qoreid = Identity::driver('qoreid');
$mono = Identity::driver('mono');
$idenvault = Identity::driver('idenvault');
Identity::driver() with no name resolves the provider configured as IDENTITY_MADE_EASY_PROVIDER, which defaults to qoreid. See configuration for environment variables and secret handling.
Drivers implement IdentityDriverInterface as a marker, plus one or more optional capability interfaces. The shared marker does not define a generic request method. For exact operations and capability names, see the API reference.
Provider behavior¶
- QoreID API operations use a backend API token; SDK session tokens are separate, short-lived frontend/mobile handoff tokens.
- Mono operations return decoded arrays except PDF report methods, which return Laravel HTTP responses.
- IdenVault operations return Laravel HTTP responses so application code can inspect both provider data and audit/accounting headers; verification POSTs require idempotency keys.
These providers can return personal data. Your application remains responsible for consent or another lawful basis, data minimization, security, and retention.