Skip to main content
Image coming soon

The Merchant Acquirer Risk Analyst Underwriting Playbook

$199.00
Adding to cart… The item has been added

A focused course, tailored for you

The Merchant Acquirer Risk Analyst Underwriting Playbook

Decision-quality underwriting and ongoing-monitoring memos for merchant services risk analysts working high-risk MCC files.

The high-risk merchant application is on your desk and the underwriting memo has to defend the reserve, the velocity caps, and the chargeback thresholds against the merchant, the sponsor bank, and the card networks all at once.

$199 one-time
Tailored to your situation. Access within 24 hours. 30-day money-back.

Includes a hand-built implementation playbook delivered alongside course access, generated for your specific situation.

Why this course

Merchant services risk analyst work is judgement work disguised as data work. The prior processor statement shows the chargeback ratio. The principal background check shows the prior MATCH listing or the thin credit. The website tells you which MCC really applies and whether the descriptor on the cardholder statement will trigger disputes. Your memo has to translate those signals into a reserve percentage, a rolling-reserve term, a velocity cap, a daily ticket ceiling, and a termination trigger that will hold up if the merchant grows, if it pivots, if it churns back, or if Visa or Mastercard puts it on a monitoring programme. The risk policy gives you ranges. The credit committee wants a recommendation. The relationship manager wants the deal closed. The compliance team wants the file clean. The work is figuring out which signals matter for this file, in what order, and writing the memo that holds.

What you walk away with

  • Write underwriting memos that name the reserve, velocity, and termination logic explicitly and survive credit-committee scrutiny.
  • Set rolling-reserve terms and release schedules that hold across MCC risk tiers without strangling merchant cashflow.
  • Build the ongoing-monitoring trigger map that catches chargeback-ratio drift, ACH return-rate climb, and MCC-creep early.
  • Run KYB enhanced due diligence on principals, beneficial owners, and the website itself with a defensible audit trail.
  • Defend the file when a sponsor bank, an ODFI, or a card-network monitoring programme asks why the merchant cleared.

The 12 modules

Module 1. The Underwriting Memo That Holds
How a merchant services risk analyst structures the underwriting memo so the reserve percentage, the rolling-reserve term, the velocity caps, the daily ticket ceiling, and the termination trigger are each named, justified, and tied to a specific signal from the file. Includes the memo template that survives credit committee review and the cross-references back to the risk policy.
Module 2. Reading the Prior Processor Statement
Working line by line through a prior processor statement to extract the chargeback ratio, the refund ratio, the average ticket, the high ticket, the swiped versus keyed mix, the international card mix, and the descriptor used on cardholder statements. Worked example uses a high-risk MCC file with a chargeback ratio sitting just under the network monitoring threshold.
Module 3. KYB Enhanced Due Diligence on Principals
The enhanced KYB workflow on principals and beneficial owners for high-risk merchant files. Background checks, beneficial-ownership tracing, sanctions and PEP screening, prior MATCH listings, prior network programme history, and the file-note pattern that ties each finding back to the underwriting decision.
Module 4. Visa VIRP, VMSS, and the Network Monitoring Programmes
Decoding the Visa Integrity Risk Programme, the Visa Merchant Screening Service, the Mastercard Excessive Chargeback Programme, and the Mastercard Excessive Fraud Merchant programme. How each programme's thresholds shape your velocity caps and ongoing monitoring triggers, what happens when a merchant trips a programme, and how the underwriting memo anticipates that path.
Module 5. MATCH List Checks and Terminated Merchant Logic
How the Mastercard Member Alert to Control High-Risk Merchants list works in practice, what the listing reason codes mean, how to interpret a hit on a principal versus on the legal entity, and the workflow for a file where the principal has a prior MATCH listing but the legal entity is new. Includes the termination decision rubric and the MATCH listing memo template.
Module 6. Rolling Reserves, Capped Reserves, and Release Schedules
The reserve calculus across MCC risk tiers. How to size a rolling reserve so it covers chargeback exposure across the network dispute window without strangling merchant cashflow. Capped reserve versus uncapped reserve. Release schedule logic. The reserve memo language that holds when the merchant pushes back through the relationship manager.
Module 7. Ongoing-Monitoring Triggers and Threshold Drift
The ongoing-monitoring trigger map for a live merchant. Chargeback ratio drift, refund ratio drift, ACH return-rate climb, average ticket creep, MCC-creep, descriptor changes, website changes, and the alert thresholds that catch each one early. How to set thresholds that fire before the network programmes do, and the escalation workflow when a trigger fires.
Module 8. ACH and Same-Day ACH Return-Rate Risk
For merchant files that include ACH or same-day ACH volume, the unauthorised return-rate ceiling, the administrative return-rate ceiling, the overall return-rate threshold, and how Nacha rules shape both the underwriting decision and the ongoing-monitoring map. Worked example walks a subscription-rebill merchant where the ACH return-rate is climbing toward the unauthorised ceiling.
Module 9. Card-Not-Present, Subscription Rebill, and Negative-Option Marketing
The specific risk pattern of card-not-present subscription rebill, free-trial-to-paid conversion, negative-option marketing, and continuity merchants. The FTC ROSCA implications, the network rules for free-trial disclosure, the chargeback-ratio reality of this model, and the underwriting memo language that captures the descriptor and disclosure controls before approval.
Module 10. AML, BSA, and the Merchant Acquirer Programme
Where merchant acquirer AML obligations sit inside the bank's BSA programme. The merchant-side suspicious activity triggers, the high-risk MCC list inside the BSA risk assessment, the CTR and SAR escalation path for merchant-funded activity, and the file-note pattern that ties merchant monitoring back into the bank's enterprise AML programme.
Module 11. Reg E, Reg Z, and the Cardholder-Side Dispute Lens
How Reg E and Reg Z shape the cardholder-side dispute path that ultimately drives merchant chargeback ratios. What an issuer is required to do on a cardholder dispute, what that means for a merchant's chargeback exposure window, and how the underwriting memo anticipates the dispute pattern that a given MCC and descriptor combination will produce.
Module 12. The Audit Trail That Survives a Regulator Question
How to write underwriting memos, ongoing-monitoring notes, reserve change memos, and termination memos so the audit trail will hold up if the OCC, the FDIC, or a network programme asks why this merchant cleared, why the reserve changed, or why the file was terminated. Includes the file-note pattern, the version-control discipline, and the language to avoid that would weaken the trail.

How this addresses your situation

Specific modules that map to what you said you are dealing with.

The high-risk MCC application is on your desk this morning. Modules 1, 2, 3, and 6 walk the underwriting memo, the prior processor statement read, the KYB on principals, and the reserve sizing for this file.
A live merchant's chargeback ratio is drifting toward the Visa VIRP threshold. Modules 4, 7, and 11 walk the network programme map, the ongoing-monitoring trigger that should have fired earlier, and the cardholder-side dispute pattern feeding the drift.
The relationship manager is pushing back on a reserve percentage in front of credit committee. Module 6 and module 1 give you the memo language and the reserve calculus to hold the line without losing the deal.
An OCC examiner is asking why a now-terminated merchant cleared underwriting eighteen months ago. Module 12 walks the audit-trail discipline that lets the file answer the question.

What you get with this course

  • Twelve written modules in the Art of Service learning environment
  • Underwriting memo template, ongoing-monitoring trigger map template, and reserve-change memo template
  • Worked underwriting example on a high-risk MCC subscription-rebill file
  • Visa VIRP, Mastercard MATCH, and Nacha return-rate reference summaries written for risk analyst use
  • Hand-built implementation playbook tailored to your merchant portfolio, delivered alongside course access

What you will have in hand by Day 1, Week 1, Month 1

Within 24 hours your account in the learning environment is provisioned and the tailored implementation playbook is delivered alongside it.

Modules 1 through 4 in week one cover the memo structure, the processor statement read, KYB on principals, and the network monitoring programmes.

Modules 5 through 8 in week two cover MATCH list logic, reserve calculus, ongoing-monitoring triggers, and ACH return-rate risk.

Modules 9 through 12 in week three cover card-not-present and subscription rebill risk, AML and BSA integration, Reg E and Reg Z, and the audit trail.

Before and after

Before

The high-risk merchant file gets a defensible reserve and velocity decision, but the memo language varies file to file and the ongoing-monitoring trigger map is partial. A network programme threshold breach surprises the team. The audit trail holds, but each memo takes too long to write.

After

Every underwriting memo follows a structure that names the reserve, velocity, and termination logic explicitly and ties each one to a specific signal from the file. The ongoing-monitoring map fires before the network programmes do. The file answers a regulator question without the analyst having to reconstruct what was thought at the time.

What happens if you do not address this

A merchant clears underwriting with a reserve and velocity decision that does not anticipate the chargeback pattern the MCC and descriptor combination will produce. Six months in, the merchant trips a network monitoring programme. The sponsor bank asks why the file cleared. The OCC asks the same question at the next exam. The memo on file does not answer it cleanly.

Who it is for

Risk analyst inside a bank-owned acquirer or independent merchant services group, working underwriting and ongoing monitoring on a mixed portfolio that includes high-risk MCC categories, subscription-rebill models, and card-not-present volume. Comfortable reading processor statements, prior chargeback data, and AML output, and accountable for the reserve, velocity, and termination logic on each file.

Who this is NOT for. Not for cardholder-side fraud analysts working issuing-bank disputes. Not for retail branch credit analysts who never touch merchant underwriting. Not for compliance generalists with no merchant portfolio exposure.

How it arrives

Text-based course in the Art of Service learning environment, plus downloadable templates and worked examples for every module, plus the hand-built implementation playbook delivered alongside course access.

Time investment. Roughly three to four hours per week across three weeks, paced so the templates can be applied to live files in the same week.

Why $199 is the right number

Network-issued training from Visa and Mastercard teaches the rules but not how to write the memo that defends the file. Internal bank training teaches the policy but rarely the underwriting craft. General compliance courses cover the BSA programme but not the merchant acquirer specifics. This course teaches the craft, with the templates and the worked example sitting alongside.

FAQ

Is this useful if my portfolio is mostly low-risk retail MCCs?
The memo structure, the ongoing-monitoring trigger map, and the audit-trail discipline apply across the portfolio. The high-risk MCC modules are the ones a low-risk portfolio analyst can use to defend the file when one creeps in.
Does this cover issuing-side fraud analyst work?
No. The course is built for the merchant acquirer side. Issuing-side fraud, dispute processing, and cardholder-side investigation are a different craft.
What does the per-buyer implementation playbook contain?
It is tailored to your portfolio mix and your role. It picks up the templates from the course and walks how to apply them to your specific MCC mix, your specific reserve policy, and your specific monitoring tools.
Will my employer see the course on a public profile?
No. Access is to your individual account in the learning environment. There is no public profile or certificate listed on a directory.

30-day money-back guarantee. If after a week of working through the materials this is not what you needed, reply to the receipt email and a full refund is processed. No questions, no forms.

Within 24 hours your account in the learning environment is provisioned and the tailored implementation playbook is delivered alongside it.