feat: Brazilian standard require idNumber, back document and email fo… #85
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -2148,7 +2148,8 @@ An enum listing the KYC schema types recognized by the FiatConnect specification | |
|
|
||
| ``` | ||
| [ | ||
| `PersonalDataAndDocuments`, | ||
| `PersonalDataAndDocumentsWithBack` | ||
| ] | ||
| ``` | ||
|
|
||
|
|
@@ -2233,6 +2234,39 @@ A KYC schema containing personal data about a user, as well as documents such as | |
|
|
||
| The `selfieDocument` and `identificationDocument` fields should be base64 encoded binary blobs representing images. | ||
|
|
||
| #### 9.3.1.2. `PersonalDataAndDocumentsWithBack` | ||
|
|
||
| A KYC schema containing personal data about a user, as well as documents such as an ID, photo and selfie. | ||
| The accepted documents are [RG](https://en.wikipedia.org/wiki/Brazilian_identity_card), [CNH](https://en.wikipedia.org/wiki/Driving_licence_in_Brazil) and [RNM](https://en.wikipedia.org/wiki/Registro_Nacional_de_Estrangeiros) | ||
|
There was a problem hiding this comment. all 3 of these documents have CPF on them, which the image would presumably include. Does idNumber still need to be its own field? Seems like it could be redundant, though I don't know the details of how you're doing KYC checks.. There was a problem hiding this comment. if you can drop the idNumber field, or clarify that it needs to be CPF specifically for the case where some new field like There was a problem hiding this comment. which could be helpful for other providers and consumers of the FC API |
||
|
|
||
| ``` | ||
| { | ||
| fullName: `string`, | ||
| dateOfBirth: { | ||
| day: `string`, | ||
| month: `string`, | ||
| year: `string` | ||
| }, | ||
| address: { | ||
| address1: `string`, | ||
| address2?: `string`, | ||
| isoCountryCode: `string`, | ||
| isoRegionCode: `string`, | ||
| city: `string`, | ||
| postalCode?: `string` | ||
| }, | ||
| phoneNumber: `string`, | ||
| email: `string`, | ||
| selfieDocument: `string`, | ||
| identificationDocumentFront: `string`, | ||
| identificationDocumentBack: `string`, | ||
|
Comment on lines
+2261
to
+2262
There was a problem hiding this comment. what kind of identity document is accepted? Any? Or just CPF cards? The description of the schema should probably go into this-- we're currently running into trouble with another KYC schema due to the ambiguity there on what document types are acceptable. If it's CPF only, the schema should probably also be renamed. There was a problem hiding this comment. @cajubelt the docs are those accepted as an official identification document in Brazil: |
||
| } | ||
| ``` | ||
|
|
||
| `email` MUST be a [valid email](https://en.wikipedia.org/wiki/Email_address#Syntax). | ||
| `phoneNumber` MUST be an 11-digit [Brazilian mobile phone number](https://en.wikipedia.org/wiki/Telephone_numbers_in_Brazil) including area code. The string MUST match the regex `/[0-9]{11}/`. | ||
| The `selfieDocument`, `identificationDocument` and `identificationDocumentBack` fields should be base64 encoded binary blobs representing images. | ||
|
There was a problem hiding this comment. Can you provide some more detailed information on the fields required in this schema? (For example, how There was a problem hiding this comment. ok @jophish , I will do that. |
||
|
|
||
| ### 9.3.2. Fiat Account Schemas | ||
|
|
||
| All Fiat Account Schemas supported by FiatConnect MUST contain the `accountName`, `institutionName`, and `fiatAccountType` fields. `accountName` is a friendly, user-definable name for the account. | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this schema name is misleading because it sounds more general than it actually is. Currently the constraints on document type, phone number and ID make this specific to Brazilian KYC checks.