Skip to main content
This step retrieves profile information using the UID and consent token returned after a completed journey. These values are required to call the SDK profile methods to fetch user data, registrant details, KYC certificates, and SDK capability information.

​
1. Get User

// KioskFace.tsx — called after KioskMode journey finds a match
const piiOnly  = localStorage.getItem('piiOnly') === 'true';
const response = await Quepass.getUser(uid, token, piiOnly);

if (response?.code === 200) {
  // response.data is UserKycProfile | UserKycProfileGov
  setCustomerData(response.data);
} else {
  const msg = response?.errors?.[0]?.message ?? 'Profile not found.';
  setProfileError(msg);
}

​
2. Get Registrant

const res = await Quepass.getRegistrant(uid, eventId, token, false);
if (res.code === 200) { /* res.data — registrant profile */ }

​
3. GetKycCertificate

const res = await Quepass.getKycCertificate(uid, token);
if (res.code === 200) { /* res.data — certificate payload */ }

​
4. Customer Status

 const response = await Quepass.customerStatus({
                uid: credentials.documentNumber,
                status: credentials.status,
            })
if (response.code === 200) {
                // Success - Customer status updated successfully
            } else {
                // Failed - update customer status");
            }

​
5. Customer Life Cycle

 const response = await Quepass.customerLifecycle({
                uid: credentials.documentNumber,
                status: credentials.status,
                from: credentials.from,
                to: credentials.to,
            });
if (response.code === 200) {
                // Success - Customer life cycle updated successfully
            } else {
                // Failed - update customer life cycle");
            }
Ensure you securely store the UID and consent token returned after a journey, as both are required to retrieve user profiles and related KYC data.