Description

A focused course, tailored for you

The Commerce Platform Risk Operations Playbook

Tune the merchant-risk queue so high-GMV sellers do not get auto-suspended and chargeback ratios stay inside card-network thresholds.

A top-quartile merchant is frozen at 3am, the account manager is asking questions at 9am, and the rule that fired was tuned for a pattern that no longer matches the fraud reality.

$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

Risk teams at commerce platforms sit between three forces that pull in opposite directions. Card networks (Visa VAMP, Mastercard Excessive Chargeback Program) penalise the platform when chargeback ratios cross the threshold, so the rule-set leans toward aggressive holds. Merchant Success pushes back when high-GMV sellers get caught in those holds, because every false suspension is a churn risk and a CX ticket. Compliance and Legal layer FinCEN MSB obligations, FCA payment-services rules, EBA AML guidance, and platform-specific Trust and Safety policy on top. The job is to keep all three groups defensible at once. That requires a score stack that names which signal carries what weight, a tuning cadence that reviews false positives and false negatives every week, a merchant-appeal workflow the CX team can run without escalating every case to Risk, and a policy-change memo format that survives both a network audit and an internal Trust and Safety review.

What you walk away with

Build a merchant-risk score stack with explicit weights for device, payment-method, behavioural, and KYC signals.
Run a weekly tuning cadence that closes the loop on false positives without dropping the catch rate on account-takeover or seller fraud.
Defend the chargeback ratio in a Visa VAMP review with the source data, the trend explanation, and the remediation plan ready in one document.
Stand up an appeal workflow that lets CX handle 70 percent of merchant disputes without escalating to Risk.
Write the policy-change memo template that satisfies Trust and Safety, Legal, and the card-network compliance team in a single review cycle.

The 12 modules

Module 1. The commerce-platform risk landscape and where you sit

Map the four forces pulling on a platform risk team at any given moment. Card networks and their ratio programs, payment regulators, merchant operations, and Trust and Safety. Name the standing decisions the risk owner is the only person empowered to make, and the ones that always belong to Legal or to the card-scheme compliance contact. Establish the working definition of acceptable false-positive and false-negative cost the rest of the course refers back to.

Module 2. The merchant-risk score stack, broken into named signals

Decompose the merchant-risk score into device, payment-method, behavioural, KYC, network-velocity, and merchant-category signal groups. For each, list the data sources commonly available in a platform stack, the typical weight range, and the failure mode when the signal is over-weighted or under-weighted. Include a worked example with a real-shape merchant profile so the weights map to recognisable behaviour.

Module 3. Chargeback ratio math the way the card networks read it

Walk through Visa VAMP and Mastercard ECP ratio calculation: numerator definition, denominator window, exclusion categories, and the difference between the platform-wide ratio and the merchant-acquirer ratio. Show how a single high-GMV merchant tipping into excessive chargeback territory can pull the platform ratio across a threshold, and how to model the projected exit date once remediation starts.

Module 4. Tuning cadence and the weekly false-positive review

Lay out a weekly tuning loop. Pull the prior week's holds, segment by reason code, score the false-positive cost per segment, and write the proposed rule change with the expected catch-rate impact. Includes a meeting template for the cross-functional review with Payments, Merchant Success, and Trust and Safety, and a decision log that captures why a change was approved or held back.

Module 5. Account-takeover and seller-impersonation signals

Cover the specific signal patterns that distinguish a compromised merchant account from a legitimate operational change. Login-geo shifts that coincide with payout-destination changes, sudden product-catalogue replacement, and CX inbound about a missing seller dashboard. Define the auto-action threshold and the human-review threshold for each pattern, and the rollback procedure when the merchant proves identity.

Module 6. The merchant appeal workflow CX can run without escalating

Design an appeal workflow that lets the CX team handle the majority of merchant disputes about a hold or suspension without bouncing the case to Risk. Define the evidence pack the merchant supplies, the auto-checks CX runs against that evidence, the criteria for re-enable versus continued hold, and the audit trail every appeal leaves so a quarterly review can verify the workflow stayed inside policy.

Module 7. KYC and onboarding-time risk decisions

Cover the onboarding moment where the platform decides whether to take a merchant at all. UBO checks, business-registry lookup, sanctions and PEP screening, and the device-and-network risk score at signup. Define the deny, allow, and conditional-allow paths, the data the platform retains for FinCEN MSB recordkeeping, and the timeline for re-verification when a merchant changes legal entity or beneficial owner.

Module 8. Payout-side risk, including velocity and destination changes

Map the risk surface on the payout side: bank-account-change holds, instant-payout abuse patterns, payout-to-different-jurisdiction triggers, and the interaction with sanctions screening. Include the standard SLA the team commits to merchants on payout holds, the exception process when Trust and Safety asks for an extended hold, and the data the team logs to defend any hold longer than the SLA.

Module 9. Working with Trust and Safety on policy-violation merchants

Risk and Trust and Safety overlap when a merchant violates platform policy (counterfeit goods, prohibited categories, deceptive practices). Define the handoff: which team initiates suspension, which team owns merchant comms, and how the joint decision gets logged so an appeal can be heard fairly. Includes the playbook for when external pressure (press, regulator, brand owner) lands on a single merchant case.

Module 10. The card-network review and the data pack you bring to it

Prepare the platform side of a Visa VAMP or Mastercard ECP review. The trend data, the merchant-level breakdown of the chargeback population, the remediation actions taken to date with timestamps, and the projected exit-from-program date. Includes the conversation script for the network compliance contact and the internal stakeholder list that needs to see the data pack before it leaves the building.

Module 11. Writing the policy-change memo that survives every reviewer

Build a policy-change memo template that names the change, the data that motivated it, the expected impact on false positives, false negatives, and the chargeback ratio, the rollback criteria, and the review schedule. Designed to satisfy Trust and Safety, Legal, the card-scheme compliance contact, and the internal risk committee in a single review cycle, with worked examples for a rule-loosening change and a rule-tightening change.

Module 12. Quarterly risk-program review and the metrics the executive team reads

Define the quarterly review the risk program owner brings to the executive team. Catch rate trend, false-positive trend, chargeback ratio against threshold, merchant-NPS impact from suspensions, top three policy changes shipped, top three issues outstanding. Includes a one-page format the CEO or COO can read in three minutes, and the supporting appendix Legal and Audit can verify line by line.

How this addresses your situation

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

When a high-GMV merchant is auto-suspended overnight and the AM is asking why, modules 2, 5, and 6 give the score-stack diagnosis, the auto-action threshold review, and the appeal workflow that re-enables them inside SLA.

When the platform chargeback ratio is approaching a card-network threshold, modules 3 and 10 give the ratio math and the network-review data pack.

When Trust and Safety wants a policy change that will increase merchant suspensions, modules 4 and 11 give the tuning-cadence review process and the policy-change memo that gets every reviewer aligned.

When the quarterly executive review is coming up, module 12 gives the one-page metrics format and the supporting appendix that holds up to Legal and Audit review.

What you get with this course

Twelve text-based modules with downloadable templates and worked examples.
The merchant-risk score-stack worksheet with named signals and weight ranges.
The weekly tuning-cadence meeting template and decision log.
The chargeback-ratio modelling workbook (numerator, denominator, projected exit).
The appeal-workflow design pack the CX team can pick up directly.
The policy-change memo template tuned for cross-functional review.
The hand-built implementation playbook adapted to the merchant categories the buyer's queue actually sees.
30-day money-back if the playbook does not match the queue.

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

Within 24 hours: course access provisioned in the Art of Service learning environment and the implementation playbook delivered alongside it.

Week 1: modules 1 to 4 plus the score-stack worksheet and the weekly tuning-cadence template.

Week 2: modules 5 to 8 plus the appeal workflow design pack and the KYC onboarding decision tree.

Week 3: modules 9 to 12 plus the policy-change memo template and the quarterly review one-pager.

Week 4: the hand-built implementation playbook tuned to the buyer's actual merchant categories.

Before and after

Before

The risk queue is reactive. Rules fire, merchants complain, appeals get escalated, and the team is always defending the last suspension rather than getting ahead of the next ratio review. Policy changes happen one ticket at a time and the score stack has weights nobody can defend in writing.

After

The risk queue runs on a defined score stack, a weekly tuning cadence, and an appeal workflow CX owns. The chargeback ratio is tracked against the network threshold every week, policy changes ship with a memo that satisfies every reviewer in one round, and the quarterly executive review is a one-page read with a verifiable appendix.

What happens if you do not address this

Without a tuned score stack and a defensible tuning cadence, the team takes the chargeback-ratio hit OR the merchant-churn hit, never both at once. Card-network review becomes a fire drill rather than a quarterly checkpoint, high-GMV merchants leave for a competitor after one bad suspension, and the policy-change backlog grows because nobody has a memo format every reviewer accepts.

Who it is for

A Risk team member at a global commerce or marketplace platform, sitting between merchant operations, payments, fraud, and Trust and Safety. Holds the queue. Owns the rule changes. Has to defend both the catch rate and the false-positive rate. Probably has a recent dispute about a high-GMV merchant who got auto-suspended, and a card-network ratio they have to keep clean.

Who this is NOT for. Not for someone who only writes fraud-model code without owning policy or merchant comms. Not for a pure compliance generalist with no exposure to a live merchant queue. Not for someone running risk at a single-merchant retailer rather than a platform with thousands of sellers.

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. Four to six hours per module on first pass. Templates are designed to be picked up and used the same week, so the score-stack worksheet and the tuning-cadence template typically land in the live queue inside the first two weeks.

Why $199 is the right number

The free options (card-network blog posts, ACAMS articles, payments-industry newsletters) describe the regulatory environment but do not give the working artefacts. Generalist fraud-management vendor materials sell a product, not a playbook the in-house team owns. A consultancy engagement to design the same artefacts typically runs five figures and takes eight to twelve weeks to deliver. This course delivers the artefacts in three weeks and the implementation playbook is hand-built for the buyer's specific merchant mix.

FAQ

Does this assume we already have a risk-scoring system in place?

It assumes the team has a queue and some rules. It does not assume the score stack is documented or that the weights are defensible. Module 2 is designed to work whether you are formalising an existing implicit stack or specifying a new one.

Is this specific to card payments or does it cover alternative payment methods?

The chargeback-ratio modules are card-network specific (Visa VAMP, Mastercard ECP). The score-stack, tuning cadence, appeal workflow, KYC, payout-side risk, and policy-memo modules apply across payment methods, including APMs, bank transfers, and BNPL where the platform takes risk exposure.

How is the implementation playbook tailored?

After purchase the buyer fills out a short profile (merchant categories, payment methods supported, current rule-engine vendor or in-house, current chargeback ratio range, current team size). The implementation playbook is then hand-built to those specifics and delivered alongside course access within 24 hours.

Do you cover the Trust and Safety policy side or only the risk-engine side?

Module 9 covers the working interface between Risk and Trust and Safety. The course does not try to replace a Trust and Safety policy curriculum, but it gives the risk owner the language and the joint-decision format that lets the two teams operate together without re-litigating every suspension.

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.