Skip to main content
For the Neuro sandbox, follow the account and identity quickstart, which uses public account enablement and automatic test-identity approval. The guide below covers the general provider-managed process. After creating the application, upload its required attachments and call ReadyForApproval to start review. The sandbox may approve the identity earlier: if its current state is already Approved, skip ReadyForApproval and continue with that identity.

​
Choose the deployed review method

Use GetApplicationAttributes and the supported service-provider operations to discover what the Neuron actually offers. A deployment might use operator review, an identity review service, peer review, or another configured policy. If the chosen reviewer requires explicit access, grant only the documented identity access for that review and record how it is revoked afterward.

​
Application state model

Use the status returned by GetIdentity rather than mapping it to a guessed enum. Store the raw status plus the application state your user interface needs.

​
Observe completion

  1. Persist the Legal Identity/application identifier returned earlier.
  2. Use the event, message, callback, or polling mechanism confirmed for the target Neuron.
  3. Make repeated observations idempotent so the same result is not applied twice.
  4. Retrieve the current identity before enabling a trust-dependent application action.
  5. Surface rejection or correction information without leaking identity evidence.

​
Completion

The workflow is complete when the relying application has retrieved the identity’s current status and evaluated it against its own provider and assurance policy. “Request accepted” and “review pending” are not successful identity verification.

​
Next