KYC: mobile ownership

Outcome:

we checking ownership of mobile.

Implementation description:

Endpoints:

PUT {$domain}/api/v2/barong/admin/profiles/label

File destination:

{$Dalan_Path}/app/workers/kyc/local/owner_mobile_worker.rb
{$Dalan_Path}/app/models/phone.rb
{$Dalan_Path}/app/services/kyc_service.rb
{$Dalan_Path}/app/api/v2/admin/profiles.rb
{$Dalan_Path}/app/services/jibit_service.rb

Commits:

7f06a2e3
816fb00e
2c05522f
90cbc486
91e75604
bdfc578d

What did we implement:

Ownership of mobile is done in background (worker) after last step (selfie confirmation).
The national code of verified profile with phone number , is sent to Jibit Service for matching.
The label key in the labels table is owner_phone

sequenceDiagram

    Title: mobile ownership
    note over Admin,Dalan: admin user confirm users selfie
    Admin->>PUT Dalan:user_uid, label_key, label_value
    
    note over Dalan,Jibit: Dalan send request to Jibbit service (as worker)
    Dalan->>Jibit:GET: natonal_code, phone_number
    Jibit->>Dalan:Response: matched, false or true
    Dalan->>Dalan: create ownership label with reject label or verified label

1.2 KiB Raw Blame History