Use a repeatable review model
Apply agreed categories and evidence requirements instead of relying on an undocumented one-off website check.
Risk Service
Website Screening
Review accessible merchant-site content and supplied business context against agreed risk indicators before onboarding and during monitoring.
For PSPs, acquirers, platforms and merchants that need a repeatable website-risk review and escalation workflow.
Pre-onboarding reviewOngoing monitoringRisk indicatorsHuman escalation
Service outcomes
Turn website observations into review-ready evidence.
These are operating goals, not performance guarantees. Results depend on scope, participants, implementation and customer operations.
Surface visible risk indicators
Identify accessible content, claims, products, policies or behavior that require further merchant or compliance review.
Create a review trail
Record the reviewed scope, observed indicators, escalation and outcome for approved operational use.
Coverage & fit
Confirm what can be reviewed and what still requires other evidence.
Screening is limited to accessible content, supplied context, agreed methods and the review time. It cannot prove all merchant activity or legal compliance.
Pre-onboarding
Review accessible merchant-site information before the responsible team makes its onboarding decision.
Periodic monitoring
Repeat an agreed review on a defined schedule where ongoing monitoring is included.
Event-driven review
Open a new review after a domain, product, complaint, dispute or other approved trigger.
Manual escalation
Route material indicators or unavailable evidence to the responsible risk or compliance team.
A signal is not a final decision
Website observations are inputs to customer review. They do not establish legality, sanctions status, beneficial ownership, product delivery or overall merchant risk by themselves.
Priority use cases
Use screening where visible website content matters to merchant risk.
PSP merchant onboarding
Review the merchant’s accessible products, claims, policies and contact information before a separate approval decision.
Marketplace seller review
Apply an agreed website-review path to sellers or merchants that operate their own domains.
Ongoing merchant monitoring
Revisit approved indicators after scheduled or event-based triggers.
Dispute-led escalation
Use dispute or complaint patterns to request a focused website review where appropriate.
Core capabilities
Turn accessible website observations into a controlled review case.
The indicator taxonomy, sources, frequency, evidence and decision owners are defined by the customer and agreed scope.
Domain and access check
Confirm the agreed domain and whether relevant public pages can be accessed at review time.
Content review
Review accessible products, services, claims, policies, contact details and other agreed page categories.
Indicator classification
Map observations to the approved prohibited, restricted, misleading or operational indicator taxonomy.
Evidence capture
Record agreed page references, timestamps and review notes without treating them as conclusive proof.
Escalation routing
Send material, ambiguous or unavailable findings to the responsible reviewer.
Monitoring record
Relate repeat reviews and approved outcomes to the merchant or case record.
Integration & deployment
Connect screening to the merchant-review process, not around it.
Integration identifies the merchant record, approved domain, trigger, indicator model, evidence handling, reviewer and downstream status.
Request technical documentation →Case or onboarding API
Receive the approved merchant and domain references from the customer system where supported.
Managed review
Use an agreed operating queue and human review process where a managed model is selected.
Status and evidence return
Return supported indicators, references and review status to the responsible system or team.
Monitoring triggers
Define scheduled, merchant-change, complaint, dispute or risk-event triggers included in scope.
How it works
Move a website from review request to responsible decision handoff.
Vellfi can support the review workflow; the customer retains its onboarding, compliance and risk decision.
- 1
Receive. Accept the approved merchant, domain and review reason.
- 2
Collect. Access the agreed public pages and supplied business context.
- 3
Review. Apply the approved indicator taxonomy and evidence requirements.
- 4
Escalate. Route material, unclear or inaccessible cases to human review.
- 5
Record. Return the review status, observations and references to the responsible team.
Illustrative scenario—not a customer case study
A PSP wants a consistent website check before merchant onboarding.
Context
Reviewers currently browse merchant sites without a common indicator list or evidence record.
ChallengeSimilar merchants can receive different review depth, and later teams cannot see what was observed at onboarding time.
Possible approach
Vellfi scopes the approved page categories, indicator taxonomy, evidence notes and escalation path, then connects the review status to the merchant case.
Potential operating effectThe PSP receives a documented review trail while retaining the merchant decision and using other due-diligence sources where required.
Responsibilities & availability
Keep screening evidence and merchant decisions separate.
Customer
Owns merchant policy, due diligence, onboarding, ongoing monitoring and final risk or compliance decisions.
Vellfi
Provides only the supported website review, indicators, evidence references and workflow included in scope.
Merchant
Remains responsible for accurate information, lawful activity, disclosures and actual business conduct.
Other data sources
Corporate, sanctions, identity, transaction and other checks remain separate unless expressly included.
Public websites are incomplete evidence
Content can change, be inaccessible or differ from actual business activity. Screening must be combined with the customer’s wider due-diligence and monitoring program.
Next step
Review your website-screening workflow.
Share the merchant types, review stage, current checklist, escalation owners and monitoring triggers without sending merchant due-diligence files through the website.
FAQ
Website Screening: common questions
What does Website Screening review?
It reviews agreed accessible website content and supplied context for approved risk indicators at a point in time.
Does screening approve or reject a merchant?
No. The customer remains responsible for the onboarding and risk decision.
Can screening confirm whether a business is legal?
No. Website content alone cannot establish legality, licensing, ownership or actual conduct.
Can it support ongoing monitoring?
Potentially, through agreed scheduled or event-driven reviews and customer escalation.
What happens when a site is unavailable?
The workflow records the limitation and routes the case according to the agreed manual-review policy.
Can screening connect to eKYC?
Potentially. Website observations and eKYC review can be coordinated while remaining distinct evidence and decisions.
What is needed for scoping?
Merchant categories, prohibited or restricted policy, page checklist, evidence requirements, triggers, reviewers and downstream statuses are useful inputs.