Due diligence checks
Beta

Last updated: March 1, 2023

During the onboarding process on the Full account type, your sub-entities go through several statuses and undergo full due diligence checks. This includes:

Card scheme screening (CSS)
Politically exposed persons (PEP) and sanctions
Know your customer (KYC)
Know your business (KYB)

We'll notify you of any sub-entity status changes via the relevant webhook notifications. The following diagram shows the possible sub-entity statuses and webhooks you may receive during the onboarding process:

Before due diligence checks can start, sub-entities must contain all the required fields. If any of these checks do not pass the review, we'll notify you via the status_changed and full_dd_failed webhooks. You can then take action to correct this and continue the review.

Information

We strongly suggest that you subscribe to the status_changed and full_dd_failed webhooks so that you are notified when action is required.

If action is required to continue sub-entity onboarding, this will be flagged with a "status": "requirements_due" field:


1{
2  "id": "evt_htielsmgcwgejgqaunl4yb2pou",
3  "type": "status_changed",
4  "version": "1.0.0",
5  "created_on": "2020-08-20T15:24:13.8431084Z",
6  "data": {
7    "sub_entity_id": "ent_vjmdzvijizs7o26kiuiakywvyi",
8    "status": "requirements_due",
9    "reference": "tmvhWvvZfFSkJy4",
10    "legal_name": "Acme Corporation Inc."
11  },
12  "_links": {
13    "self": {
14      "href": "https://api.checkout.com/workflows/events/evt_htielsmgcwgejgqaunl4yb2pou"
15    }
16  }
17}

You can see the reason for this status:

in your Dashboard account
by retrieving sub-entity details via the Accounts API

To see the details in the Dashboard:

Sign in to your Dashboard account.
Navigate to the Sub-entities section.
Select the sub-entity in REQUIREMENTS_DUE status.

The Sub-entity Details page appears. The banner at the top of the page highlights the reasons for the REQUIREMENTS_DUE status and the actions you need to take.

To see the details via the Accounts API:

Retrieve the sub-entity details using the
get
/accounts/entities/{entityId} endpoint.
In the response, check the requirements_due array for impacted fields and corresponding reasons.


1{
2  "id": "ent_sea5kqczeqvnznx5lqsbbsnlq4",
3  "reference": "HEjzSLlfjLuvx5l",
4  "status": "requirements_due",
5  "instruments": [],
6  "requirements_due": [
7    {
8      "field": "company.document",
9      "reason": "required"
10    },
11    {
12      "field": "company.financial_details.documents.bank_statement",
13      "reason": "required"
14    },
15    {
16      "field": "company.representatives[0].identification.document",
17      "reason": "required"
18    }
19  ],
20  "contact_details": {
21    "phone": {
22      "number": "1234 567890"
23    }
24  },
25  "profile": {
26    "default_holding_currency": "GBP",
27    "urls": ["https://www.exampleurl.com"],
28    "mccs": ["5551"]
29  },
30  "company": {
31    "business_registration_number": "12345678",
32    "legal_name": "Acme Corporation LTD",
33    "trading_name": "Acme Corporation",
34    "principal_address": {
35      "address_line1": "111 Example Road",
36      "city": "London",
37      "zip": "SW1A 1AA",
38      "country": "GB"
39    },
40    "registered_address": {
41      "address_line1": "111 Example Road",
42      "city": "London",
43      "zip": "SW1A 1AA",
44      "country": "GB"
45    },
46    "representatives": [
47      {
48        "id": "rep_3ipq26zsxt3n24rh2vojjkfez4",
49        "address": {
50          "address_line1": "111 Example Road",
51          "city": "London",
52          "zip": "SW1A 1AA",
53          "country": "GB"
54        },
55        "phone": {
56          "number": "1234 567890"
57        },
58        "first_name": "Jane",
59        "last_name": "Doe",
60        "date_of_birth": {
61          "day": 5,
62          "month": 6,
63          "year": 1995
64        },
65        "place_of_birth": {
66          "country": "GB"
67        },
68        "identification": {
69          "document": {
70            "type": "passport",
71            "front": "file_a2waebevmihts7s74bie3w3nf4"
72          }
73        }
74      }
75    ]
76  },
77  "capabilities": {
78    "payments": {
79      "enabled": false,
80      "available": true
81    },
82    "payouts": {
83      "enabled": false,
84      "available": true
85    },
86    "issuing": {
87      "enabled": false,
88      "available": false
89    }
90  },
91  "_links": {
92    "self": {
93      "href": "https://api.checkout.com/accounts/entities/ent_sea5kqczeqvnznx5lqsbbsnlq4"
94    },
95    "schema": {
96      "href": "https://api.checkout.com/accounts/entities/_schema?resource_type=Entity&type=Company&schema_version=&country=GB"
97    }
98  }
99}


1{
2  "id": "ent_oewtd5r2sdf2pyl5cggmhkpqnu",
3  "reference": "VKPA5RteMGLlV5i",
4  "status": "requirements_due",
5  "instruments": [],
6  "requirements_due": [
7    {
8      "field": "individual.identification.document",
9      "reason": "document_expired"
10    }
11  ],
12  "contact_details": {
13    "phone": {
14      "number": "1234 567890"
15    }
16  },
17  "profile": {
18    "default_holding_currency": "GBP",
19    "urls": ["https://www.exampleurl.com"],
20    "mccs": ["5551"]
21  },
22  "individual": {
23    "trading_name": "Toto’s Treats",
24    "legal_name": "Toto’s Treats LTD",
25    "national_tax_id": "1234567",
26    "registered_address": {
27      "address_line1": "111 Example Road",
28      "city": "London",
29      "zip": "SW1A 1AA",
30      "country": "GB"
31    },
32    "first_name": "Jane",
33    "middle_name": "Samantha",
34    "last_name": "Doe",
35    "date_of_birth": {
36      "day": 5,
37      "month": 6,
38      "year": 1995
39    },
40    "identification": {
41      "document": {
42        "type": "passport",
43        "front": "file_a2waebevmihts7s74bie3w3nf4"
44      }
45    }
46  },
47  "capabilities": {
48    "payments": {
49      "enabled": false,
50      "available": true
51    },
52    "payouts": {
53      "enabled": false,
54      "available": true
55    },
56    "issuing": {
57      "enabled": false,
58      "available": false
59    }
60  },
61  "_links": {
62    "self": {
63      "href": "https://api.checkout.com/accounts/entities/ent_oewtd5r2sdf2pyl5cggmhkpqnu"
64    },
65    "schema": {
66      "href": "https://api.checkout.com/accounts/entities/_schema?resource_type=Entity&type=Individual&schema_version=&country=GB"
67    }
68  }
69}


1{
2  "id": "ent_sea5kqczeqvnznx5lqsbbsnlq4",
3  "reference": "HEjzSLlfjLuvx5l",
4  "status": "rejected",
5  "instruments": [],
6  "requirements_due": [],
7  "contact_details": {
8    "phone": {
9      "number": "1234 567890"
10    }
11  },
12  "profile": {
13    "default_holding_currency": "GBP",
14    "urls": ["https://www.exampleurl.com"],
15    "mccs": ["5551"]
16  },
17  "company": {
18    "business_registration_number": "12345678",
19    "legal_name": "Acme Corporation",
20    "trading_name": "Acme Corporation LTD",
21    "principal_address": {
22      "address_line1": "111 Example Road",
23      "city": "London",
24      "zip": "SW1A 1AA",
25      "country": "GB"
26    },
27    "registered_address": {
28      "address_line1": "111 Example Road",
29      "city": "London",
30      "zip": "SW1A 1AA",
31      "country": "GB"
32    },
33    "representatives": [
34      {
35        "id": "rep_3ipq26zsxt3n24rh2vojjkfez4",
36        "address": {
37          "address_line1": "111 Example Road",
38          "city": "London",
39          "zip": "SW1A 1AA",
40          "country": "GB"
41        },
42        "phone": {
43          "number": "1234 567890"
44        },
45        "first_name": "Jane",
46        "last_name": "Doe",
47        "date_of_birth": {
48          "day": 5,
49          "month": 6,
50          "year": 1995
51        },
52        "place_of_birth": {
53          "country": "GB"
54        },
55        "identification": {
56          "document": {
57            "type": "passport",
58            "front": "file_a2waebevmihts7s74bie3w3nf4"
59          }
60        }
61      }
62    ]
63  },
64  "capabilities": {
65    "payments": {
66      "enabled": false,
67      "available": true
68    },
69    "payouts": {
70      "enabled": false,
71      "available": true
72    },
73    "issuing": {
74      "enabled": false,
75      "available": false
76    }
77  },
78  "_links": {
79    "self": {
80      "href": "https://api.checkout.com/accounts/entities/ent_sea5kqczeqvnznx5lqsbbsnlq4"
81    },
82    "schema": {
83      "href": "https://api.checkout.com/accounts/entities/_schema?resource_type=Entity&type=Company&schema_version=&country=GB"
84    }
85  }
86}

The following table lists the possible reasons for the requirements_due status, and describes the action you will need to take to continue the review.

Reason	Action required
`required`	The field is required to trigger due diligence for the first time. Input the required data and resubmit.
`unidentified_details`	Individual details, such as address or date of birth, couldn't be verified against our provider databases. Upload an identification document for the individual or representative.
`document_expired`	The document provided is expired. Upload a new identification document for the individual or representative.
`document_do_not_match_user_data`	The details on the document provided do not match the data that was provided. Upload a new identification document for the individual or representative.
`invalid_document`	This can be caused by an invalid file format or document type, or a similar document issue. Upload a new identification document for the individual or representative.
`verification_failed`	Company details, such as legal name or registered address, couldn't be verified against our provider databases. Upload a new certificate of incorporation (COI).

We've made some changes to our API

Due diligence checks
Beta

Resolve `requirements_due` status

Information

Response examples

Resolve requirements_due status

Information

Response examples

Resolve `requirements_due` status