Defensible Onboarding and Monitoring Standards for Payment Facilitators

A fast onboarding experience can be an important competitive advantage for Payment Facilitators (PayFacs).  Many would say the ability to rapidly onboard a merchant is an absolute requirement today.  But speed means little if the organization cannot explain why a submerchant was approved, what risks were identified, or how those risks are being managed after processing begins.

Sponsor banks and card networks are focused on more than whether a PayFac has an underwriting policy.  They want evidence that the policy works.  A defensible program is one in which decisions are consistent, exceptions are controlled, monitoring is meaningful, and actions can be reconstructed long after an event.

Define the Risk You Are Willing to Accept

Defensible onboarding begins with a documented risk appetite, agreed upon with the sponsor bank.  The policy should identify acceptable and prohibited business categories, geographic restrictions, exposure limits, and the circumstances requiring enhanced review or bank approval.

Risk classifications should guide the process.  A low-risk, established service business with modest, anticipated volume may warrant a streamlined review.  A merchant with deferred delivery, unusually high tickets, cross-border activity, or a complex ownership structure may require additional information, financial analysis, or a different settlement arrangement.

The objective is not to treat every applicant identically.  It is to apply consistent standards to merchants presenting comparable risks and document the rationale for different treatment.

Verify the Business, Not Just the Application

Collecting information is not the same as verifying it.  Sound onboarding must establish that the applicant is a legitimate business, identify relevant owners and controllers, validate business activities, and confirm that the merchant fits the PayFac’s approved acceptance criteria.

That may include evaluating business registrations, bank account ownership, operating websites, advertised products, expected volumes, fulfillment practices, sanctions exposure, and relevant terminated-merchant screening results.  The exact requirements depend on the PayFac’s activities, applicable law, network rules, and sponsor-bank agreements. 

Discrepancies between a merchant’s description and its online presence should prompt questions before activation.

Make Automated Decisions Explainable

Automation allows PayFac’s to onboard thousands of merchants efficiently, but an approval produced by a rules engine must still be explainable.  Each decision should preserve the information evaluated and approving authority.  Where staff override a system recommendation, the file should record who authorized the exception, why, and whether compensating controls were imposed.

Periodic quality reviews should test whether rules perform as intended.  This includes examining merchants approved incorrectly, excessive false positives, gaps in third-party data, and changes to scoring models.  A program that cannot reproduce its decisions will struggle to defend them.

Monitor Behavior Against Expectations

Underwriting establishes an initial risk profile; monitoring tests whether that profile remains accurate.  Thresholds should reflect merchant risk requirements rather than relying exclusively on a single portfolio-wide number.  A rapid increase in volume may be normal for one merchant and a warning sign for another.

PayFacs should establish appropriate merchant-level and portfolio-level alerts for sudden volume increases, unusual transaction sizes, excessive authorization declines, refund spikes, elevated disputes or fraud, and changes in sales geography.  Monitoring should also consider website changes, product shifts, customer complaints, and indicators of transaction laundering.

Equally important, alerts must lead to investigations.  A dashboard showing deteriorating activity is not an effective control if no one is responsible for responding.

Connect Alerts to Documented Action

A defensible monitoring program identifies who owns each case, what evidence must be reviewed, when escalation is required, and which remedial actions are available.

Responses might include requesting additional documentation, adjusting processing limits, changing settlement terms, imposing reserves where contractually permitted, notifying the sponsor bank, or terminating the relationship.

Investigators should document their findings, the decision made, and the basis for closing the case.  Repeat alerts and unresolved exceptions should be visible to risk leadership, not lost in separate operational queues.

Demonstrate Oversight to the Sponsor Bank

Sponsor banks retain significant oversight responsibilities, even when underwriting and monitoring activities are delegated to a PayFac.  Strong reporting should therefore go beyond merchant counts and processing growth.

Useful measures include portfolio risk distribution, approval exceptions, alert volumes and resolution times, fraud and dispute trends, concentrations, potential settlement exposure, and the results of quality-control testing.

Management should periodically compare actual performance against approved risk appetite, revisit thresholds, and verify that policies reflect current products and merchant behavior.  Independent reviews can help identify whether procedures are genuinely operating as described.

Defensibility Is a Discipline, Not a Document

The strongest PayFac programs combine efficient onboarding with disciplined risk decisions and continuous monitoring.  They can answer three fundamental questions: Why did we approve this merchant?  What changed after approval?  What did we do about it?

At RPY Innovations, we believe those answers should be readily available—not assembled only after a sponsor-bank inquiry, examination, or loss event.  PayFacs that make defensibility part of daily operations will be better positioned to earn sponsor-bank confidence, protect their portfolios, and grow sustainably.

Next
Next

Sponsor Bank Program Governance