/unified-verifs/ (the downstreamPath) select which Verification API route is called; the request body and query string you send are forwarded to that route verbatim, and the Verification API's response — status code and body — is relayed back to you unchanged. Only downstream paths starting with v1/verifications or v1/banks are permitted; any other path is rejected before any upstream call is made. The Verification API's own internal secret key is injected server-side and is never exposed to callers. Every attempted call (including rejected ones) is recorded in a best-effort, PII-free audit log keyed off the caller's identity from the bearer token; audit logging failures never block the response.curl --location '/unified-verifs/v1/verifications' \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{
"exampleField": "exampleValue"
}'{
"message": null,
"status": "success",
"data": {
"exampleField": "exampleValue"
}
}