🦸‍♂️Customer States

• initiating - an initial state for a Customer. This state is assigned to an entity immediately upon creation via POST /customers endpoint. At this stage we expect a customer challenge to be signed and verified before proceeding to next states. Upon successful challenge verification an entity is transitioned to screening state

• screening - a Customer entity is undergoing blockchain screening through a third-party service. Upon completion of the screening process and if the result is satisfactory for our processes, an entity is transitioned to verifying state. If screening result is unsatisfactory, an entity is transitioned to rejected

• verifying - a Customer entity is undergoing KYC verification through a third-party service. At this stage you can retrieve customer verification details required to initiate a KYC session with our partner. Details on this process are to be added to this guide. Upon completion and successful customer verification, an entity is transitioned to active, otherwise - to rejected

• rejected - a Customer entity has failed one of the previous verification steps and is not allowed to use our services. This is a final state. The algorithms used at verification steps are able to determine false-positives and employ retry mechanisms. If a customer was not able to satisfy the requirement, we are confident they are never going to satisfy them and we won't allow them to be onboarded again

• active - a Customer entity is ready to use our services, including account and card creation. An entity can be temporarily deactivated in case of any issues or if we suspect any illicit activity. In this case an entity is transitioned to inactive state. You can also deactivate Customer yourself using PATCH /customers/{customerId}/deactivate endpoint. If we have evidence of any illicit activity received through our constant monitoring workflows, an entity is transitioned to rejected state

• inactive - a Customer entity is temporarily deactivated. It can be re-activated again on our end or using PATCH /customers/{customerId}/activate endpoint