You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: catalog/knowyourcustomer/kyc_match_openapi.yaml
+8-8Lines changed: 8 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -60,9 +60,9 @@ tags:
60
60
paths:
61
61
/v0/match:
62
62
post:
63
-
summary: KYC Match v0.1 /match
63
+
summary: Verify match v0.1
64
64
tags:
65
-
- Match a customer identity
65
+
- Verify a customer identity
66
66
67
67
description: |
68
68
Matches a customer identity by checking a set of attributes related against the account data bound to their phone number.
@@ -168,11 +168,15 @@ paths:
168
168
$ref: '#/components/responses/Generic504'
169
169
/v0.2/match:
170
170
post:
171
-
summary: KYC Match v0.2 /match
171
+
summary: Verify match v0.2
172
172
tags:
173
-
- Match a customer identity
173
+
- Verify a customer identity
174
174
175
175
description: |
176
+
Check the [Authorization guide](/docs/authorization) on how to get an OAuth2 token, with the following purpose:
177
+
178
+
`dpv:FraudPreventionAndDetection#kyc-match:match`
179
+
176
180
Verify matching of a number of attributes related to a customer identity against the verified data bound to their phone number in the Operator systems. Regardless of whether the `phoneNumber` is explicitly stated in the request body, at least one of the other fields must be provided, otherwise a `HTTP 400 - KNOW_YOUR_CUSTOMER.INVALID_PARAM_COMBINATION` error will be returned.
177
181
178
182
In order to proceed with the match check, some Operators may have the requirement to perform an additional level of validation based on the `idDocument` property. This means that, in those cases, the `idDocument` is required and the provided value needs to match the one stored in the Operator system associated with the indicated `phoneNumber`. This validation will be done before proceeding with the match check of the rest of the properties. The following two rules apply only in the cases where the Operator have the requirement to validate the `idDocument`:
@@ -185,10 +189,6 @@ paths:
185
189
- **false**: the attribute provided does not match with the one in the Operator systems.
186
190
- **not_available**: the attribute is not available to validate.
187
191
188
-
Check the [Authorization guide](/docs/authorization) on how to get an OAuth2 token, with the following purpose:
0 commit comments