feat: adding external account validation schema

openapi/components/schemas/external_accounts/BeneficiaryVerificationStatus.yaml

@@ -0,0 +1,19 @@
+type: string
+enum:
+  - MATCHED
+  - PARTIAL_MATCH
+  - NOT_MATCHED
+  - UNSUPPORTED
+  - CHECKED_BY_RECEIVING_FI
+  - PENDING
+description: |
+  The result of verifying the beneficiary name against the account holder name.
+
+  | Status | Description |
+  |--------|-------------|
+  | `MATCHED` | The beneficiary name is an exact match |
+  | `PARTIAL_MATCH` | The beneficiary name is a fuzzy match |
+  | `NOT_MATCHED` | The beneficiary name does not match |
+  | `UNSUPPORTED` | The payment rail does not support name verification |
+  | `CHECKED_BY_RECEIVING_FI` | Verification is deferred to the receiving financial institution (e.g. ACH) |
+  | `PENDING` | Verification is still in progress |

openapi/components/schemas/external_accounts/BeneficiaryVerifiedData.yaml

@@ -0,0 +1,6 @@
+type: object
+properties:
+  fullName:
+    type: string
+    description: The verified full name of the account holder as returned by the payment rail
+    example: John Doe

openapi/components/schemas/external_accounts/ExternalAccount.yaml

@@ -34,5 +34,11 @@ allOf:
           False if not provided. Note that at most, one external account can be set as the default UMA deposit account for a customer.
           If there is no default UMA deposit account, incoming UMA payments will be deposited into the primary internal account for the customer.
         example: false
+      beneficiaryVerificationStatus:
+        $ref: ./BeneficiaryVerificationStatus.yaml
+        description: The result of verifying the beneficiary name against the account holder name
+      beneficiaryVerifiedData:
+        $ref: ./BeneficiaryVerifiedData.yaml
+        description: Verified beneficiary data returned by the payment rail, if available
       accountInfo:
         $ref: ./ExternalAccountInfoOneOf.yaml