Skip to main content

API Testing Payloads

This guide provides copy-paste request bodies for testing common integration scenarios against the Verifow sandbox. All payloads assume the base URL /api/v1/ and bearer token authentication.

1. Authentication

1.1 Login

POST /api/v1/auth/login

2. KYC Verification

2.1 Submit Individual KYC Application

POST /api/v1/kyc/applications

3. Transaction Screening

3.1 Screen Transaction — Individual (APPROVE)

POST /api/v1/transactions/screen

3.2 Screen Transaction — Individual (KYC BLOCK)

POST /api/v1/transactions/screen

3.3 Screen Transaction — Sanctions Hit

POST /api/v1/transactions/screen

3.4 Screen Transaction — Business / KYB

For corporate senders, your payload must flag the transaction as a business transaction and supply the company’s CAC registration number. When your bank has already performed KYB verification outside of Verifow, assert senderKybStatus: "VERIFIED" to bypass the Verifow KYB lookup. You should still send the sender’s KYC fields, because authorized signatories and directors may still be evaluated under individual KYC rules. POST /api/v1/transactions/screen
Business screening payload fields
Note: If senderKybStatus is omitted for a business transaction, Verifow will attempt a local KYB lookup using metadata.senderRcNumber. If no KYB record exists, the transaction will be scored as high risk.

4. KYB Verification

4.1 Submit KYB Application

POST /api/v1/kyc/kyb/applications