Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.quepass.com/llms.txt

Use this file to discover all available pages before exploring further.

This step updates and manages the customer’s status and lifecycle information using the UID obtained after a completed journey. The UID is required to call the SDK methods that update customer status and track lifecycle transitions (such as stage changes or status updates). These methods ensure that the customer’s verification state and lifecycle progression are properly recorded within the system.

​
1. Customer Status

​
Required Parameters

  • uid (string) – User identity
  • status (string) – Current status of the user or operation

​
Return Parameters

  • status (string) – Current status of the user or operation

​
Code Example

 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");
            }

​
2. Customer Life Cycle

​
Required Parameters

  • uid (string) – User identity
  • status (string) – Current status of the user or operation
  • from (string) – Start timestamp or date for the query/filter
  • to (string) – End timestamp or date for the query/filter

​
Return Parameters

  • status (string) – Current status of the user or operation

​
Code Example

 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.