A Customer on the Rize Platform is the end user of your application. Customers are unique to each Program and the management of all accounts and identifying information is handled on a Program-by-Program basis.

After your initial submission supplying external uid and email, the Customers endpoint will accept the remaining personally identifiable information (PII) and Profile Responses for each Customer. The PII for a Customer must be submitted in full. Rize will not accept your request if any field is incomplete or missing. PII can be edited for a Customer up until a valid request to onboard a Customer to a Product is sent to the Customer Product endpoint.

Profile Responses are submitted in response to Profile Requirements. The Profile Requirements a Customer must satisfy before onboarding onto a Product are available on the Products endpoint. Profile Responses may be risk tolerance, income level, or other profile related data required from a Customer before they can onboard onto the Product.

To join a Program, a Customer must pass the Know Your Customer/Anti-Money Laundering (KYC/AML) identity verification requirements set by the Custodian(s) participating in your Program. The KYC_status on the Customer record indicates the Customer’s current state within the KYC/AML verification workflow. Rize will initiate KYC/AML verification using the Customer PII on record after a valid request for onboarding is sent to the Customer Product endpoint. Examples of verification statuses include Approved, Manual Review, Documents Required, and Denied. Rize will work with you to define these states based on inputs from the Custodian.

A new Customer record must be created for each Program even when an identical Customer already exists on a different Program.

At no point will a Customer record be accessible outside of its Program.

This endpoint is also used for Customer management functions such as freezing or unfreezing a Customer or archiving a Customer.