VYBE opens a live account for a Bahrain resident using eKey 2.0 app-to-app authentication through the issuer, then gets a prepaid card issued. Screens follow the eKey 2.0 account-opening journey; every hop between the five systems is logged with its payload.
VYBE never talks to eKey directly. The issuer owns the eKey client credentials, PKCE verifier, token exchange and government data. VYBE owns the app screens, one forwarding call, the financial survey and the status check.
https://app.vybe.com/ekey) as the return URI. Keep vybe://ekey only as fallback.POST /api/v2/kyc-application. Store applicationId against the VYBE user.code, state, error, error_description to GET /api/v2/ekey/call-back the moment the app receives them.GET /api/v1/kyc-application/{id} with backoff (1s, 2s, 4s, cap 30s) until Verified/Failed.state, nonce, PKCE S256, bound to the applicationId with the 10-minute consent window shown on the eKey screen.VYBE_PREPAID_USD when configured. VYBE gets cardId and masked PAN only.POST /api/v2/ekey/auth-session with purpose: LOGIN. eKey is asked for openid only, so the customer sees one confirm screen and Face ID. No data-consent list, no video selfie, no survey.sub against the customer at account opening, then matches it on every log-in. It never calls the KYC data API for a log-in.sub from the id_token before pulling KYC data. If it is already linked, it returns Verified with outcome: LINKED_TO_EXISTING and the existing customerId. No second profile, no second card. VYBE signs the customer in.sub link exists yet. The issuer falls back to a CPR-hash match after the KYC data pull, then links the sub so every later log-in is the short path.| Field | Source | Shared with VYBE | Why |
|---|---|---|---|
fullNameEn / fullNameAr | eKey KYC API | Yes | Account name must match the verified identity |
dateOfBirth, nationality | eKey KYC API | Yes | Age gate and country risk for trading |
mobile, mobileVerified | eKey (General information scope) | Yes | Pre-fills VYBE contact details; no SMS OTP needed |
cpr | eKey KYC API | Masked (8•••••12) | Minimise national ID spread; the issuer keeps the full value |
photo | eKey KYC API | No | Only needed for the issuer’s biometric match |
cardId, maskedPan, status | Issuer card issuing | Yes | Display card; never the full PAN |
kyc.application.updated, HMAC-SHA256) so VYBE isn't hammering the status endpoint at onboarding peaks./api/v2, status is /api/v1. Either align or document why.failureReason code (ACCESS_DENIED, AUTH_FAILED, INVALID_STATE, CPR_EXPIRED, NAME_MISMATCH) so VYBE can route the user to retry, support or fallback.kyc-application API, selected by method.Verified is too early for a CBB investment firm: the survey, appropriateness test, FATCA/CRS and PEP declaration sit with VYBE. Add issueOn: KYC_VERIFIED | CLIENT_APPROVED.state.kyc-application. Without an auth-session (purpose LOGIN) endpoint, every returning customer would go through a full application, consent list and selfie again.