Outsourced: Onboard an individual

Under our outsourcing model, Griffin does not perform independent third-party verification of the data you submit. We define the information required to meet account opening and regulatory reporting obligations, and when data is submitted, we validate that the required fields are present and screen the customer against our appetite criteria — including industry, jurisdiction, and risk profile.

To check the different types of entities you can onboard using Outsourced, see Entities we onboard.

Outsourced onboarding is for firms which Griffin has a pre-existing agreement with to outsource the onboarding processes to. If you don't have this agreement in place, this onboarding guide does not apply to you.

caution

Only users with the compliance role can create and submit Outsourced applications.

Process overview

There are four steps to onboarding an individual via Outsourced:

Capture the customer information
Create the legal person
Run the verification
View the verification outcome and onboarding decision

1. Capture the customer information

Individual information

Information	Claim	Required
Full name (given name)	`individual-identity`	✓
Middle name	`individual-identity`	Optional
Full name (surname)	`individual-identity`	✓
Date of birth	`individual-identity`	✓
Residential address	`individual-residence`	✓
US citizen confirmation	`us-citizen`	✓
Tax residency/ies	`tax-residencies`	✓
Tax identifier number/s	`tax-identification-numbers-by-country`	✓
Risk rating	`external-risk-rating`	✓

info

Note: this is the data we require to be sent to our system, a larger set of data requirements will be required from the customer by the outsourcing party (you) to complete CDD and risk rate the customer.

2. Create the legal person

In the API, your customer is represented as a legal person, and each of the data points above represent one claim about them. Create an individual legal person to represent the customer and then add claims about them.

curl "https://api.griffin.com/v0/organizations/${ORGANIZATION_ID}/legal-persons" \
  -H "Authorization: GriffinAPIKey $GRIFFIN_API_KEY" \
  -H 'Content-Type: application/json' \
  -d \
'{
  "display-name": "DAVIS, Henry",
  "legal-person-type": "individual",
  "claims": [
    {
      "claim-type": "individual-identity",
      "given-name": "Henry",
      "surname": "Davis",
      "date-of-birth": "1991-05-10"
    },
    {
      "claim-type": "individual-residence",
      "building-number": "19",
      "street-name": "Example Street",
      "city": "Test Town",
      "postal-code": "TE1 2ST",
      "country-code": "GB"
    },
    {
      "claim-type": "us-citizen",
      "us-citizen?": false
    },
    {
      "claim-type": "tax-residencies",
      "tax-residencies": ["GB"]
    },
    {
      "claim-type": "tax-identification-numbers-by-country",
      "tins-by-country": {
        "GB": ["AB123456C"]
      }
    },
    {
      "claim-type": "external-risk-rating",
      "external-risk-rating": "low-risk"
    }
  ]
}'

A successful response will display the URL for the newly created legal person (e.g. /v0/legal-persons/lp.Kfd8_BhpSdCqFKRYXa8d45) in the response's Location header and in the response body. Save this URL for the next step.

info

In this example, you create the legal person and their claims in one go, but you can also create a legal person first and then add claims individually. For more detail on claims, see the API reference.

3. Run the verification

Retrieve your workflows

If you're onboarding a customer for the first time, you will need to retrieve your workflows in order to submit the verification. Retrieve and cache your workflow URLs.

Submit the verification

Submit the individual legal person for verification:

curl 'https://api.griffin.com/v0/legal-persons/lp.Kfd8_BhpSdCqFKRYXa8d45/verifications' \
  -H "Authorization: GriffinAPIKey $GRIFFIN_API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{"workflow-url": "/v0/workflows/wf.G3yYmojQV32I814_5JLTEQ"}'

A successful response will look like this. Grab the verification-url for monitoring later.

{
  "created-at": "2024-02-10T10:47:51.959Z",
  "display-name": "DAVIS, Henry",
  "legal-person-type": "individual",
  "legal-person-url": "/v0/legal-persons/lp.Kfd8_BhpSdCqFKRYXa8d45",
  "updated-at": "2024-02-10T10:47:51.959Z",
  "verification-status": "pending",
  "verification-url": "/v0/verifications/vn.BhpS_dCqFKRYXa8d457fgA",
  "workflow-url": "/v0/workflows/wf.G3yYmojQV32I814_5JLTEQ"
}

4. View the verification outcome and onboarding decision

Verification status

The verification has successfully completed when verification-status reaches checks-complete. You can track this by:

Polling the verification-url
Listening for verification-updated webhook events

Example response:

{
  "created-at": "2024-02-11T10:47:51.959Z",
  "display-name": "DAVIS, Henry",
  "legal-person-type": "individual",
  "legal-person-url": "/v0/legal-persons/lp.Kfd8_BhpSdCqFKRYXa8d45",
  "external-risk-rating": "low-risk",
  "updated-at": "2022-08-15T10:48:03.215Z",
  "verification-status": "checks-complete",
  "verification-url": "/v0/verifications/vn.BhpS_dCqFKRYXa8d457fgA",
  "workflow-url": "/v0/workflows/wf.G3yYmojQV32I814_5JLTEQ"
}

Verification statuses explained

Status	Description
`pending`	Verification has been created but processing has not yet begun
`in-progress`	Verification checks are actively being performed
`failed`	An internal system error has occurred during verification
`checks-declined`	Verification was terminated early due to failing one or more workflow checks
`checks-complete`	Verification has successfully completed all required checks

Decision process

After reaching checks-complete, the system will either:

Generate an automated decision
Refer the application for manual review (followed by a manual decision)

Monitor decisions by:

Polling the legal-person-decisions-url endpoint
Listening for decision-created webhook events

View on the legal person

Both the verification status and the decisions can be seen in context on the legal person entity.

curl 'https://api.griffin.com/v0/legal-persons/lp.Kfd8_BhpSdCqFKRYXa8d45' -H "Authorization: GriffinAPIKey $GRIFFIN_API_KEY"

The response will include application-status and also the latest-decision when one exists:

{
  "latest-decision": {
    "verification-url": "/v0/verifications/vn.BhpS_dCqFKRYXa8d457fgA",
    "decision-outcome": "accepted",
    "decision-maker": "user",
    "decision-notes": "No red flags here",
    "decision-user-url": "/v0/users/ur.ICAgICAgICAgdXNlci1pZA",
    "created-at": "2024-08-11T10:47:51.959Z"
  },
  "display-name": "DAVIS, Henry",
  "application-status": "accepted",
  "status-changed-at": "2024-02-11T10:47:51.959Z",
  "created-at": "2024-02-10T10:47:51.959Z"
}

Once you have an accepted decision, you're good to go 🎉

What's next?

Open an account! See Types of bank accounts to get started.

Process overview​

1. Capture the customer information​

Individual information​

2. Create the legal person​

3. Run the verification​

Retrieve your workflows​

Submit the verification​

4. View the verification outcome and onboarding decision​

Verification status​

Verification statuses explained​

Decision process​

View on the legal person​

What's next?​