Review vendor categories, data roles, integration boundaries, and notification expectations before legal approval.
The final named vendor list should be confirmed in the customer packet after the rollout scope and integrations are known.
Named register
This public register separates core services from customer-specific or conditionally configured vendors.
Email delivery for website leads, demo requests, customer proof invitations, and internal notifications.
Fallback email delivery when configured for website lead or proof workflows.
Business signup routing, account discovery, customer proof administration, and customer workflow handoff.
Payment workflow orchestration, merchant handoff, and payment-readiness review.
Merchant underwriting, payment processing, settlement, funding, statements, and chargeback workflows.
Human verification and abuse prevention for public signup flows when enabled.
DNS, edge routing, TLS, and traffic protection where configured for public web properties.
Infrastructure provisioning and hosting operations where configured for deployment environments.
Review process
Simple enough for operators, specific enough for procurement.
Identify each vendor category used by the customer's rollout.
Document data role, data type, region, retention, and integration boundary.
Confirm procurement, legal, and customer notification requirements.
Re-check vendors annually or when a material vendor changes.
