Description

A focused course, tailored for you

The Payments Platform Compliance Analyst Operating Playbook

The state MTL exam, the SAR queue, the PCI attestation, and the sanctions hit-list, run on one weekly cadence by one analyst.

Four regulators ask different questions in the same week. The exam letter, the BSA officer review, the PCI QSA walk-through, the OFAC false-positive backlog. One analyst sits at the intersection. There is no template that maps all four onto a single weekly cadence, so the work compounds and the binder gets built the night before the deadline.

$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

A compliance analyst inside a payments and commerce platform owns a surface no playbook on the open market covers cleanly. Money transmitter licenses across forty-plus US states, EU and UK payment institution permissions, PCI DSS scope across acquirers, BSA and AML obligations for stored value and instant payouts, OFAC sanctions screening at onboarding and at the transaction level, consumer protection rules touching pay-over-time and merchant cash advance products, state safeguarding and segregation of customer funds, complaints handling for the CFPB consumer complaint database, and merchant-facing terms that have to track every product change. Each of those has its own examiner, its own evidence room, its own audit cycle. The work is not hard one task at a time. The work is hard because all of them land on the same calendar and there is no single source of truth that ties the merchant risk score to the monitoring alert to the SAR narrative to the exam answer. This playbook builds that single source of truth and the weekly cadence that keeps it current.

What you walk away with

A single weekly cadence that runs the MTL exam prep, the PCI attestation cycle, the AML sample review, and the sanctions backlog from one calendar.
An exam binder template that maps the standard state Division of Banking request list to evidence already stored in the platform, so the binder assembles in days not weeks.
A transaction monitoring sample design that survives the BSA officer Q&A and the next exam, with documented thresholds and clear false-positive disposition.
A PCI DSS scope diagram for a multi-acquirer commerce platform, with the segmentation evidence the QSA actually asks for.
A merchant risk register that ties onboarding tier to monitoring alert thresholds to enhanced due diligence triggers, defensible to an examiner.

The 12 modules

Module 1. The compliance analyst calendar at a payments platform

Walks through the twelve recurring obligations that hit the analyst seat across a year. State MTL renewals and call reports, PCI DSS quarterly scans and annual attestation, BSA annual training and SAR cycle, OFAC list refresh cadence, EU and UK payment institution annual return, CFPB complaint response SLAs. Builds the master calendar that ties each obligation to evidence already produced elsewhere in the platform so deadlines stop being surprises.

Module 2. The state MTL exam binder before the examiner asks

Reverse-engineers the standard pre-exam request list that state Divisions of Banking send four to six weeks before a money transmitter renewal exam. Twenty-two recurring line items mapped to the evidence the platform already has, the evidence that needs a one-time build, and the evidence that has to be produced fresh each cycle. Produces a binder template that survives a multi-state exam with one common foundation and per-state annexes.

Module 3. Transaction monitoring sample design for stored value and instant payouts

Designs the monthly transaction monitoring sample for a platform book covering card processing, merchant balances, instant payouts, and pay-over-time. Threshold rationales, segmentation by merchant tier, false-positive disposition logs, escalation criteria, the documented analyst rationale that survives BSA officer review and a regulator Q&A. Includes a template SAR narrative that ties the alert back to the underlying merchant pattern.

Module 4. Sanctions screening across onboarding, payouts, and the OFAC backlog

Builds the sanctions screening cadence across three control points. Merchant onboarding screening against OFAC SDN and consolidated lists plus EU and UK sanctions, transaction-level screening for cross-border payouts, and the false-positive backlog clearance process. Includes the matching threshold rationale, the four-eyes disposition log, and the periodic list refresh evidence that examiners request first.

Module 5. PCI DSS scope diagram for a multi-acquirer commerce platform

Produces the PCI DSS scope diagram and segmentation evidence package for a commerce platform that runs multiple acquirers, a tokenisation vault, and merchant-facing checkout surfaces. Maps the cardholder data environment boundary, the connected systems, the segmentation controls and their evidence, and the SAQ versus ROC decision for each merchant cohort. Closes with the QSA pre-meeting question set.

Module 6. Merchant risk register and the underwriting-to-monitoring tie-back

Builds a merchant risk register that ties the onboarding tier and underwriting decision to the monitoring alert thresholds the merchant lives under for the rest of their tenure. Documents the enhanced due diligence triggers, the periodic re-review cadence, the offboarding criteria, and the evidence trail an examiner asks for when a merchant featured in a SAR also had a missed monitoring threshold.

Module 7. State safeguarding, customer funds segregation, and the call report

Covers the state safeguarding and customer funds segregation rules for stored value and merchant balances. Walks through the daily reconciliation evidence, the trust account or eligible investment structure, the state-specific permitted investments lists, and the quarterly state call report fields that map directly to the segregation evidence. Closes with the working paper bundle for the safeguarding section of the MTL exam.

Module 8. EU PI and UK PI permissions, safeguarding, and the annual return

Maps the EU payment institution and UK payment institution permission scope to the platform's product surface. Walks through safeguarding accounts, the segregation method election, the annual safeguarding audit evidence, the regulatory return fields, and the operational resilience self-assessment. Closes with the change-of-control and material change notification process when product ships a new payment surface.

Module 9. Pay-over-time, BNPL, and the CFPB consumer protection surface

Walks through the consumer protection surface for pay-over-time and BNPL products. Truth in Lending Act disclosures where applicable, Reg E error resolution timelines, dispute handling, the CFPB consumer complaint database response SLA, and the marketing review process that prevents UDAAP findings. Closes with the complaints register design that ties consumer complaints back to product and underwriting changes.

Module 10. Product change review, the compliance approval gate, and the change log

Builds the compliance change review process for a product organisation shipping payment changes on a weekly cadence. The intake form product fills out, the four review lenses (licensing, BSA, consumer protection, data), the documented compliance approval or hold decision, and the change log that ties product releases to compliance sign-offs. Survives an examiner asking how a specific product change was reviewed.

Module 11. BSA officer review, four-eyes, and the analyst evidence pack

Designs the monthly BSA officer review meeting and the evidence pack the analyst brings. The transaction monitoring summary, the SAR cycle metrics, the sanctions backlog status, the training completion rate, the model tuning log, and the exception register. Includes the four-eyes documentation pattern that makes every analyst decision review-ready and reduces re-work when an examiner sample lands on an old disposition.

Module 12. The hand-built implementation playbook for your state mix and product surface

The implementation playbook is hand-built after purchase against the actual state mix, payment permission stack, acquirer count, and product surface the analyst seat covers. Names the specific recurring deadlines for the next four quarters, the specific binder gaps to close before the next examiner letter, and the specific monitoring sample design changes worth running through the BSA officer review. Delivered alongside course access.

How this addresses your situation

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

The state MTL renewal examiner letter just landed. Modules 2, 7, and 11 build the binder and the safeguarding evidence pack the examiner opens first.

The BSA officer wants the monthly transaction monitoring sample restructured. Modules 3, 4, and 11 produce the sample design, the disposition log, and the evidence pack for the review meeting.

Product is shipping an instant payout change next quarter that touches state safeguarding. Modules 7, 8, and 10 cover the safeguarding rule change, the regulatory notification, and the compliance change review evidence.

A pay-over-time product expansion is on the roadmap and Legal asked who owns the CFPB exposure. Modules 9 and 10 cover the consumer protection surface, the complaints register, and the change review gate.

What you get with this course

Twelve text-based modules in the Art of Service learning environment.
Downloadable templates for the MTL exam binder, the transaction monitoring sample, the merchant risk register, the PCI DSS scope diagram, and the state call report mapping.
Worked examples for SAR narrative, false-positive disposition, safeguarding reconciliation, and a compliance change review log.
The hand-built implementation playbook tailored to the analyst seat's actual state mix, payment permission stack, and product surface.
30-day money-back guarantee.

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 to 4 cover the analyst calendar, the state exam binder, the transaction monitoring sample, and sanctions screening. Most analysts work through these in the first week.

Modules 5 to 8 cover PCI DSS scope, the merchant risk register, state safeguarding, and EU and UK PI permissions. Most analysts work through these in week two.

Modules 9 to 12 cover consumer protection, the compliance change review gate, the BSA officer review evidence pack, and the implementation playbook walk-through. Most analysts work through these in week three.

Before and after

Before

Four regulator surfaces and four internal stakeholders pull on the analyst calendar with no shared cadence. Each exam binder gets assembled the night before, the monitoring sample design lives in one analyst's head, and product ships changes faster than the compliance review log can keep up.

After

One weekly cadence runs all four surfaces. The MTL exam binder assembles from evidence already stored in the platform. The monitoring sample design is documented, reviewed, and survives the BSA officer Q&A. Every product change has a documented compliance approval gate and a logged decision.

What happens if you do not address this

Examiner findings on the next MTL renewal that reference missing evidence the platform already had but could not produce on time. A BSA officer escalation when a SAR backlog ties to an old monitoring threshold nobody documented. A product change shipped without a compliance approval log that becomes the lead question in the next regulatory exam.

Who it is for

Compliance analyst sitting inside a commerce or payments platform with a meaningful US state footprint, an EU or UK payments permission stack, a merchant book that runs into the hundreds of thousands, and a product line that includes card processing, stored value, instant payouts, and pay-over-time. The analyst is the operating layer between the BSA officer, the General Counsel, the product managers shipping payment changes, and the external examiners and QSAs who arrive on a fixed cadence. The seat is usually one or two people wide for the volume.

Who this is NOT for. Not for bank holding company compliance, not for a single-product fintech with one acquirer and one state, not for general corporate compliance roles that do not touch payments licensing. The course assumes the seat covers MTL, PCI DSS, and BSA AML at minimum.

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. Around three to four hours per week for three weeks. Modules are designed to be worked through alongside the live calendar, so the templates get populated with the analyst's actual current cycle as the modules progress.

Why $199 is the right number

Generic AML or PCI DSS courses on the open web cover one regulator at a time and assume a single-product fintech. The MTL examiner manuals and BSA officer handbook cover the rules but not the operating cadence. Internal training tends to cover only the most recent finding. This playbook is the operating layer that ties all four surfaces to one analyst calendar.

FAQ

Is this tied to a specific platform?

No. The course is for a compliance analyst seat at any commerce or payments platform with a comparable state MTL footprint, EU and UK PI permission stack, multi-acquirer card processing, stored value, instant payouts, and pay-over-time. The implementation playbook is hand-built against the specific state mix and product surface the analyst seat covers.

I'm an analyst, not the BSA officer. Is this still the right course?

Yes. The analyst seat is the explicit audience. The course covers what an analyst produces for the BSA officer's monthly review, what an analyst hands to the QSA, and what an analyst loads into the MTL exam binder. The BSA officer is a stakeholder, not the buyer.

Does this cover state-by-state MTL specifics?

The modules cover the common 80 percent of the multi-state MTL request list. The hand-built implementation playbook covers the specific state-by-state annexes for the states the analyst seat actually holds licenses in, drawn from the platform's NMLS record.

What happens within 24 hours?

Your account in the learning environment is provisioned and the tailored implementation playbook is delivered alongside it.

Refund?

30-day money-back guarantee, no questions asked.

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.