The Exception Logging module changed how we write reopen criteria. We still struggle when engineering tickets close without evidence attached—class named that friction instead of pretending templates fix culture.
Yuri N. · Tokyo · Controls testing
Flagship course
Payment Controls Assurance Lab
A six-module program for practitioners who design and execute controls testing audits for fintech platforms—wallets, remittance, and acquiring stacks.
What you leave with
- A redacted-ready control inventory worksheet mapped to payment product surfaces
- Sample plans that stratify by corridor volume and exception rate
- Walkthrough scripts for override and privilege paths
- Exception logging conventions with owner and due-date fields
- A short management report template that states residual risk without soft language
Modules
Curriculum map
-
01
Control inventory for payment surfaces
Catalog preventive and detective controls across onboarding, funding, transfer, settlement, and access. Identify orphan controls that exist only in policy.
-
02
Sampling for corridor volume
Move past fixed sample counts. Practice stratification for remittance and settlement populations, and document when judgmental samples are the honest choice.
-
03
Maker-checker and override walkthroughs
Build facilitator notes that keep engineering and risk aligned when demonstrating dual control and break-glass paths.
-
04
Access recertification evidence
Design attestation trails for privileged roles, contractor lag, and system exports that auditors can re-perform.
-
05
Exception logging without theater
Log defects with root cause candidates, owners, and reopen rules. Avoid burying issues under vague improvement tickets.
-
06
Reporting and limitation statements
Draft a management summary that states coverage, findings, and what the test could not prove. Capstone critique closes the lab.
Instructor
Eun-ji Park
Former internal audit lead for a licensed Korean payments firm; now designs Datalinkbox labs with a focus on evidence that survives re-performance.
Informational pricing
Individual Assurance Cohort seats are listed at ₩2,450,000 on the pricing page. Team retainers are quoted after a fit call. This site does not process payment.
Refunds and cancellations follow the rules on our Refund page.
FAQ
Who is this lab for?
Internal audit, operational risk, and compliance testing staff who own controls on payment, wallet, or remittance platforms. Product managers sometimes join as observers, not as primary testers.
Is the material specific to Korea?
Examples reference Korean licensing language and Incheon office hours, but the testing methods apply to APAC and cross-border stacks. We do not teach local law as a substitute for counsel.
What is a real limitation of this course?
We do not provide a certified opinion on your control environment, and we do not supply production data extracts. If your team lacks access to system logs, parts of Modules 2 and 4 will stay theoretical until you can practice on your own systems.
How are sessions delivered?
Live remote workshops with optional hybrid kickoff for Controlroom Retainer teams when travel schedules allow. Recordings are available for a limited window inside the cohort.
From past cohorts
Walkthrough scripts from Module 3 are now our default for privilege demos. Capstone critique was tougher than expected—useful, if a bit compressed in the final week.
Platform-style review · rating submitted after Assurance Cohort