Submit External Ownership Verification
This endpoint submits an ownership verification from an external provider (e.g. Jumio, Onfido) by directly uploading identity documents and raw verification data, bypassing the default Veriff verification flow.
The uploaded files and raw data are stored in the same format as Veriff, so the existing downstream processing (Braid UBO saga) consumes them normally.
Prerequisites
- The ownership data must be submitted first using the Submit Business Ownership endpoint.
- The owner must not already be
approvedorin_review.
Technical Details
- Status Change: The owner status changes directly to
approved. - No verification link is generated — documents are uploaded directly.
- The
mediaNamemetadata values (face,document-front,document-back) are set automatically to ensure compatibility with downstream processing.
Authorization:
bearer
HTTP: bearer
HTTP Authorization Scheme: bearer
Headers:
Authorization: APIKey {YOUR_API_KEY}
Endpoint
/api/v2/kyb/banking-verification/business/ownership/{ownerId}/submit-external-verification
Content Type
multipart/form-data
Path Parameters
| Parameter | Type | Description |
|---|---|---|
ownerId | string (uuid) | Required. The owner ID to submit verification for. |
Request Body Schema
| Field | Type | Description |
|---|---|---|
face | binary | Required. Selfie image of the owner. |
documentFront | binary | Required. Front of the ID document. |
documentBack | binary | Back of the ID document (optional). |
raw | string (JSON) | Required. Raw verification JSON from the external provider. Must be valid JSON. |
provider | string | Required. Source provider name (e.g. jumio, onfido). |
Response Sample
{
"ownerId": "00000000-0000-0000-0000-000000000001",
"status": "approved",
"firstName": "John",
"lastName": "Wick",
"email": "jwick@blockwyre.com",
"phone": "+1234567890",
"dateOfBirth": "1990-05-15",
"documentId": {
"idNumber": "123456789",
"idDocumentType": "passport",
"idIssueDate": "2020-01-01",
"idExpiryDate": "2030-01-01",
"idCountryOfIssue": "US",
"nationality": "US"
},
"address": {
"address1": "123 Main St",
"address2": "Apt 4B",
"city": "New York",
"state": "NY",
"postalCode": "10001",
"country": "US"
},
"ownershipPercentage": 100,
"role": "owner"
}
Error Responses
Owner Already Approved or In Review
If the owner is already in approved or in_review status, you will receive a 409 Conflict error.
Invalid Raw JSON
If the raw field is not valid JSON, you will receive a 400 Bad Request error.
Support and Resources
If you need assistance or have any questions, our support team is here to help. You can contact our support team at support@blockwyre.com.
Stay Updated
Stay up-to-date with the latest news, updates, and features from BlockWyre by following us on social media:
- Instagram: BlockWyre Instagram
- Twitter: BlockWyre Twitter
- Facebook: BlockWyre Facebook
- LinkedIn: BlockWyre LinkedIn
We are excited to have you on board and look forward to seeing how you leverage BlockWyre's powerful tools to enhance your financial operations. Happy integrating!