Start Verification from URL
Start a Payward-performed verification for a user with evidence provided via presigned URLs.
This endpoint accepts the same verification families as Submit Verification from URL: identity document, residence document, and liveness. Liveness checks use three-point images. Use this endpoint when Payward should verify the submitted evidence. Use Submit Verification from URL when your integration already verified the evidence and Payward should trust the verifier result you provide.
URL and file requirements
Evidence URLs must be HTTPS URLs on allowlisted domains, up to 4096 characters. Each redirect target must also use HTTPS and an allowlisted domain. The server follows up to three redirects.
The server extracts the decoded filename from the submitted URL path. The filename must be 255 bytes or less, cannot be . or .., and cannot contain path separators or control characters. It must include an extension matching the detected file content.
Downloaded files can be up to 150 MiB (157286400 bytes). The size limit is enforced from the Content-Length header and while streaming the response body. Accepted file types are JPEG/JPG, PNG, PDF, MP4/M4V, WebM, and MOV/QuickTime. Passport identity document submissions must omit back_url.
Verification result fields
Do not send verifier, verified_at, verifier_response, or verifier_response_url to this endpoint. Those fields belong to Submit Verification from URL because that endpoint trusts a verification result supplied by your integration.
Domain allowlisting
For security, the domains you use for presigned URLs must be allowlisted before you can use this endpoint. Contact your account manager to configure the allowed domains for your integration.
Authorizations
Your public API key. Identifies the partner making the request.
Monotonically increasing nonce included in the request signature.
HMAC signature over the request, computed with your private key.
Path Parameters
ID of the user the request applies to. For partners operating in the B2B2C model, this is the Sub-User the request is acting on behalf of. Canonical identifier for a user in the Payward public API.
14 - 42Body
- Option 1
- Option 2
- Option 3
Verification request body. The type discriminator selects exactly one start verification payload.
identity_document Metadata about the identity document to verify.
Presigned URL to the front side of the identity document. The filename is extracted from the URL path and must meet the URL and file requirements.
1 - 4096^https://"https://your-allowlisted-bucket.s3.amazonaws.com/front.png?X-Amz-Algorithm=AWS4-HMAC-SHA256"
Presigned URL to the back side of the identity document. The filename is extracted from the URL path and must meet the URL and file requirements. Passport submissions must omit this field.
1 - 4096^https://"https://your-allowlisted-bucket.s3.amazonaws.com/front.png?X-Amz-Algorithm=AWS4-HMAC-SHA256"
Response
Verification started.