Skip to main content

Update customer information

This section applies to both Verify, Reliance and Outsourced onboarding.

For any customer information that has changed, you can re-submit just the claim information that needs updating and the checks associated with that claim will be re-run. These checks will re-run when another verification is run.

Submitting Updated Claims​

You can submit the updated claim information for each legal persons using:

 POST https://api.griffin.com/v0/legal-persons/{legal-person-id}/claims

Once you have updated a claim you can fetch a list of unverified claims using the filter:

GET https://api.griffin.com/v0/legal-persons/{legal-person-id}/claims?filter[verification-status][eq]=unverified

The verification-status will change from unverified to verified when it has successfully been used as part of an accepted verification.

info

A verified claim has been used by an accepted verification. An unverified claim is when a verification hasn’t been run on a claim, or a verification resulted in a declined or errored decision.

You will need to run a new verification after you have updated claims by using: 

 POST https://api.griffin.com/v0/legal-persons/{legal-person-id}/verifications
 
 {
    "workflow-url": "{workflow-id}"
 }

If a director or PSC has changed you can remove them from the application using

DELETE https://api.griffin.com/v0/claims/{claim-id}

A successful response will give you a 204 response code.

You can then add a new director or PSC using the claims endpoint as usual.

Re-use ID&V verification (Verify onboarding only)​

When updating customer information for individuals who have completed ID&V (identity and verification) through Verify:

Within 30 days of ID&V completion​

If you update any customer information, including their name, address, or date of birth, we will automatically re-use the previously submitted selfie and ID document images. Your customer will not need to complete the ID&V process again.

After 30 days of ID&V completion​

If you update the customer's name, address, or date of birth, your customer will need to complete a new ID&V check. This means they'll need to submit a new selfie and photo of their identity document through a new ID&V link.

As you do in an initial onboarding request, get the ID&V link from idv-check-url within /verifications/<:verification-id>/resources, as shown below. You will need to share this with your customer so they can complete ID&V.

To find out the ID&V links, you can poll the verification-resources-urluntil they become available. You can also leverage webhooks and listen for the verification-resource-created|updated events, emitted once the ID&V links are available.

{
  "verification-url": "/v0/verifications/vn.IHZlcmlmaWNhdGlvbi1pZA",
  "legal-person-url": "/v0/legal-persons/lp.Kfd8_BhpSdCqFKRYXa8d45",
  "organization-url": "/v0/organizations/og.IG9yZ2FuaXphdGlvbi1pZA",
  "verification-resources": [
    {
      "verification-resource-type": "idv-check",
      "verification-resource-id": "a87ef592-c300-43f2-84f9-005120592392",
      "idv-check-status": "pending",
      "idv-check-url": "IDV.check.url",
      "idv-check-expires-at": "2024-02-16",
      "display-name": "string",
      "legal-person-url": "/v0/legal-persons/lp.Kfd8_BhpSdCqFKRYXa8d45"
    },
  ],
  "links": {
    "prev": "string",
    "next": "string"
  }
}

The idv-check-status begins in a pending state and transitions to one of three final states: complete, errored, or expired.

Embedding the ID&V flow in your web/mobile app​

For a better user experience, you can embed Veriff's ID&V flow directly within your application instead of redirecting users to an external page. Veriff provides SDKs for web, iOS, and Android that accept the session URL (the idv-check-url generated above) and render the verification flow natively in your app.

For detailed integration instructions, code examples, and platform-specific guidance, see Veriff's SDK documentation.