-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Brazilian standard require idNumber, back document and email fo… #85
Changes from 4 commits
421ad53
e834177
0ff71de
48d216c
e2c9d58
b29d830
795dc78
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
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` | ||
`PersonalDataAndDocuments`, | ||
`PersonalDataAndDocumentsWithBack` | ||
] | ||
``` | ||
|
||
|
@@ -2233,6 +2234,37 @@ 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 brasilian standard KYC schema containing personal data about a user, as well as documents such as an ID photo and selfie. | ||
|
||
``` | ||
{ | ||
fullName: `string`, | ||
dateOfBirth: { | ||
day: `string`, | ||
month: `string`, | ||
year: `string` | ||
}, | ||
address: { | ||
address1: `string`, | ||
address2?: `string`, | ||
isoCountryCode: `string`, | ||
isoRegionCode: `string`, | ||
city: `string`, | ||
postalCode?: `string` | ||
}, | ||
phoneNumber: `string`, | ||
idNumber: `string`, | ||
email: `string`, | ||
selfieDocument: `string`, | ||
identificationDocumentFront: `string`, | ||
identificationDocumentBack: `string`, | ||
Comment on lines
+2261
to
+2262
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 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. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @cajubelt the docs are those accepted as an official identification document in Brazil: |
||
} | ||
``` | ||
|
||
The `selfieDocument`, `identificationDocument` and `identificationDocumentBack` fields should be base64 encoded binary blobs representing images. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Can you provide some more detailed information on the fields required in this schema? (For example, how There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 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.