Reliance onboarding
Reliance is for use by regulated firms only, onboarding via Reliance is only available by API.
You complete customer due diligence (CDD) using your own tools and processes, and then send us the information we need. You must also attest that you have verified your customer's identity in line with the standards set by the Joint Money Laundering Steering Group (JMLSG).
Once you’ve provided us with the information we need, we will run Politically Exposed Person (PEP) and Sanctions checks on your customer and, where applicable, an Immigration Act check.
Only users with the compliance role can create and submit Reliance applications.
There are four steps to onboarding a company using Reliance.
- Choose your workflow
- Capture the customer information
- Submit the application
- Receive a decision
1. Choose your workflow
Find the relevant workflow by querying organization-workflows-url, as shown below. Grab the workflow-url to use in the next step.
curl "https://api.griffin.com/v0/organizations/${ORGANIZATION_ID}/workflows" -H "Authorization: GriffinAPIKey$GRIFFIN_API_KEY"
{
"workflows": [
{
"workflow-url": "/v0/workflows/wf.Ul-1r4gRWfOFxHJsHWghcA",
"display-name": "Reliance LTD Company",
"legal-person-type": "corporation"
}
]
}
2. Capture the customers information
You will need the following information about the customer
| LTD | Sole trader | Individual |
|---|---|---|
| Company name | Full name | Full name |
| Company registration number | Business name | Address |
| Business type | Business type (sole trader) | Date of birth |
| Industry code (SIC) | Industry code (SIC) | US citizen confirmation |
| Business size | Business size | Tax residency/ies |
| Number of employees* | Number of employees* | Tax identifier number/s |
| Balance sheet size* | Balance sheet size* | Risk rating |
| Estimated annual turnover* | Estimated annual turnover* | |
| Company trading address | Residential address | |
| Company registered address | Date of birth | |
| Tax residency/ies | US citizen confirmation | |
| Tax identifier number/s | Tax residency/ies | |
| Risk rating | Tax identifier number/s | |
| ↓ Director & PSC info ↓ | Risk rating | |
| Full name | ||
| Address | ||
| Date of birth | ||
| US citizen confirmation | ||
| Tax residency/ies | ||
| Tax identifier number/s |
*Requested but not required
Note this is the data we will hold on our system, a larger set of data will be required for you to complete your own risk assessment and adhere to CDD standards.
2.1 Attesting to verification
In addition to submitting the above information about the company, you must also attest that you have verified both the company information and the identities of the directors and PSCs. To do this, use the reliance-verification claim, and enter one or more of the following reliance-verification-methods:
| Verification method | Description |
|---|---|
electronic | the customer was verified using electronic sources (credit reference agency) |
physical | the customer provided documentation in person |
manual-biometric | government documentation cross-referenced with a selfie and verified by a third party |
manual-document | the customer supplied documentation e.g. a passport copy and address document |
reliance-verification-standard | attest that the verification method used was in line with JMLSG standards |
3. Submit an application
To submit an application, make a request to:
POST https://api.griffin.com/v0/organizations/{organization-id}/onboarding/applications
You will need to provide the claims relevant to the customer type, as shown in the table above (following claims) for the subject profile, i.e. the profile of the customer you are onboarding, below is an example from a corporation request.
Here is an example application:
{
"workflow-url": "/v0/workflows/wf.Ul-1r4gRWfOFxHJsHWghcA",
"subject-profile": {
"display-name": "Money Technology Ltd",
"claims": [
{
"claim-type": "uk-company-register",
"entity-name": "Money Technology Ltd",
"corporation-type": "private-limited-company",
"entity-registration-number": "91824539",
"date-of-incorporation": "2017-06-01",
"building-number": "184",
"city": "London",
"street-name": "Argyle Street",
"postal-code": "EC2V 9AN",
"country-code": "GB"
},
{
"claim-type": "trading-address",
"trading-address": {
"building-name": "Tower A",
"building-number": "12",
"street-name": "High Street",
"city": "London",
"postal-code": "TE1 2ST",
"country-code": "GB"
},
},
{
"claim-type": "sic-codes",
"sic-codes": ["01110"]
},
{
"claim-type": "business-size",
"business-size": "small"
},
{
"claim-type": "tax-residencies",
"tax-residencies": [
"GB",
"US"
]
},
{
"claim-type": "tax-identification-numbers-by-country",
"tins-by-country": {
"GB": [
"12345-6789"
],
"US": [
"123-45-6789"
]
}
{
"claim-type": "external-risk-rating",
"external-risk-rating": "low-risk"
},
},
]
},
"related-profiles": [
]
},
{
"display-name": "KLEIN, Monica",
"subject-association": {
"psc": {}
},
"claims": [
{
"claim-type": "individual-identity",
"date-of-birth": "1963-02-02",
"given-name": "Monica",
"surname": "Klein"
},
{
"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": [
"Italy"
]
},
{
"claim-type": "tax-identification-numbers-by-country",
"tins-by-country": {
"Italy": [
"12345-6789"
],
}
},
{
"claim-type": "reliance-verification",
"reliance-verification-methods": ["manual-biometric", "manual-document"],
"reliance-verification-standard": "jmlsg"
}
]
}
If a director is also a PSC, you should add both roles on the subject-association parameter, as shown below:
{
"workflow-url": "/v0/workflows/wf.Ul-1r4gRWfOFxHJsHWghcA",
"subject-profile": {...},
"related-profiles": [
{
"display-name": "JOHNSON, Talia",
"subject-association": {
"director": {},
"psc": {}
},
},
]
}
A successful response body looks like this:
{
"onboarding-application-url": "/v0/onboarding/applications/oa.b25ib2FyZGluZy1hcHBsaQ",
"onboarding-application-status": "submitted"
}
3.1. Monitoring the application
To monitor the application status, either poll the onboarding-application-url or create a webhook and listen for the onboarding-application-created and onboarding-application-updated events.
Once an application has been submitted, it will register the subject and related profiles and the status will update to processing. A legal-person-url and verification-url will be added to the application, as shown below:
{
"onboarding-application-url": "/v0/onboarding/applications/oa.b25ib2FyZGluZy1hcHBsaQ",
"created-at": "2019-08-24T14:15:22Z",
"workflow-url": "/v0/workflows/wf.Ul-1r4gRWfOFxHJsHWghcA",
"onboarding-application-status": "processing",
"legal-person-url": "/v0/legal-persons/lp.IGxlZ2FsLXBlcnNvbi1pZA",
"verification-url": "/v0/verifications/vn.IHZlcmlmaWNhdGlvbi1pZA"
}
4. Receive a decision
When the onboarding-application-status moves to complete, a decision of accepted or declined will be added to the application.
A successful response body for a complete application that has been accepted looks like this:
{
"onboarding-application-url": "/v0/onboarding/applications/oa.b25ib2FyZGluZy1hcHBsaQ",
"created-at": "2019-08-24T14:15:22Z",
"workflow-url": "/v0/workflows/wf.Ul-1r4gRWfOFxHJsHWghcA",
"onboarding-application-status": "complete",
"legal-person-url": "/v0/legal-persons/lp.IGxlZ2FsLXBlcnNvbi1pZA",
"verification-url": "/v0/verifications/vn.IHZlcmlmaWNhdGlvbi1pZA",
"decision": "accepted"
}
If the verification process fails, the application status will update to errored. You can query the verification-url for more detail:
GET https://api.griffin.com/v0/verifications/{verification-id}
A body response for an errored application looks like this:
{
"onboarding-application-url": "/v0/onboarding/applications/oa.b25ib2FyZGluZy1hcHBsaQ",
"created-at": "2019-08-24T14:15:22Z",
"workflow-url": "/v0/workflows/wf.Ul-1r4gRWfOFxHJsHWghcA",
"onboarding-application-status": "errored",
"legal-person-url": "/v0/legal-persons/lp.IGxlZ2FsLXBlcnNvbi1pZA",
"verification-url": "/v0/verifications/vn.IHZlcmlmaWNhdGlvbi1pZA"
}
Onboarding international directors/pscs
When onboarding directors/pscs outside the UK, the claim requirements for addresses are different.
See this example for an imaginary French address:
{
"claim-type": "individual-residence",
"address-line-1": "4 Rue Paul Cabet",
"address-line-2": "Appartement 5",
"city": "Dijon",
"state": "Côte-d'Or",
"postal-code": "21000",
"country-code": "FR"
}
Required:
claim-typeaddress-line-1citypostal-codecountry-code
Optional:
address-line-2state