SYNTHETIC PROOF WALKTHROUGH
Stop vendor onboarding when a customer-required W-9 is missing
A synthetic completeness check over a customer-defined onboarding requirements list and supplied packet evidence.
THREE STEPS
Put the control before the consequential action.
The packet contains insurance and approval evidence but does not contain the required W-9 item.
- 01
Define the customer checklist
The customer decides which packet items, approval, and remittance-baseline evidence are required.
- 02
Compare supplied item names
The control performs a deterministic completeness comparison over the supplied lists.
- 03
Return one issue per gap
Each missing requirement is returned separately for the authorized onboarding workflow.
VISIBLE SYNTHETIC CONTRACT
Inspect exactly what the workflow sees.
The input and output are representative of the named product contract. Copy them into an architecture note, test fixture, or internal review—never treat this browser-only demonstration as a live control result.
{
"vendor_reference": "northstar-1007",
"required_items": [
"W9",
"insurance_certificate",
"customer_approval"
],
"supplied_items": [
"insurance_certificate",
"customer_approval"
],
"approved_by_customer": true,
"remittance_fingerprint_present": true
}{
"status": "COMPLETED",
"decision": "REVIEW_REQUIRED",
"exceptions": [
{
"code": "VENDOR_ONBOARDING_ITEM_MISSING",
"severity": "HIGH",
"message": "A customer-required vendor onboarding item is missing.",
"evidence": {
"item": "W9"
}
}
],
"evidence": {
"vendor_reference": "northstar-1007",
"required_count": 3,
"missing_items": [
"W9"
]
},
"next_action": "Collect the missing customer-required evidence before approval."
}WHAT THIS PROVES
Evidence for a stop point—not permission to act.
Vendor Onboarding Check does not collect documents, create a vendor, approve onboarding, validate a W-9, or verify remittance ownership.
- Decision
- REVIEW_REQUIRED
- Named exception
VENDOR_ONBOARDING_ITEM_MISSING- Evidence
- itemW9
- Next action
- Collect the missing customer-required evidence before approval.
KEEP BUILDING
Move from the synthetic fixture to the exact API contract.
Review the product inputs, outputs, errors, and safety boundary before using authorized data. The related implementation guide explains the design decisions behind the control.
Try the control through the supported buyer path.
RapidAPI provides the subscription, key, quota, and capped marketplace plan for this synchronous control.