Flagship course

Open Banking Assurance Studio

A six-week studio for engineers, risk partners, and product owners who must prove how open banking APIs behave under audit.

Code on a monitor in a dim workspace

What you will practise

  • Trace consent grant and revocation across API gateways
  • Build a sampling plan auditors can follow without hand-holding
  • Score third-party provider integrations for assurance gaps
  • Draft evidence packs tied to specific endpoint families
  • Run a mock findings walkthrough with peer critique
  • Document residual risk in language that survives legal review

Informational pricing

Individual seat: ₩1,890,000 · Team of four: ₩6,400,000

Figures are published for planning only. No checkout is available on this site — request a seat via contact.

Request enrolment details

Modules

  1. Week 1 — Landscape & obligations Map open banking surfaces your product exposes and which controls auditors typically sample first.
  2. Week 2 — Consent path forensics Walk grant, refresh, and revoke flows with real log excerpts and deliberate blind spots.
  3. Week 3 — Gateway & logging hygiene Align retention, correlation IDs, and redaction so evidence remains usable.
  4. Week 4 — Third-party provider posture Score TPP integrations and decide what belongs in your pack versus theirs.
  5. Week 5 — Evidence pack assembly Produce a review-ready binder for account information and payment initiation APIs.
  6. Week 6 — Auditor rehearsal Defend your pack in a timed mock review; capture follow-ups as a living backlog.

Instructor

Portrait of instructor Haeun Park

Haeun Park

Former assurance lead for a Seoul-based payments platform. Haeun designs Networksystemscloud studios around artefacts reviewers actually request — not theory decks. She still consults on open banking API audits for fintech product launches.

Learner notes

“Week 2 forced us to diagram revoke latency we had never measured. Uncomfortable, but it changed our backlog.”

Joon · Platform engineer · Busan

The mock auditor session was tougher than our last external review. I wished we had more time on certificate rotation — the course flags that as out of scope for Studio.

Anonymous client in digital banking

FAQ

Who should attend?

API engineers, security partners, and product owners who share ownership of open banking endpoints. Pure policy staff without technical peers may find labs dense.

Is this a certification?

No. You receive a completion letter and your evidence pack draft. We do not issue regulated auditor credentials.

What is a real limitation of this course?

Assurance Studio does not cover cryptographic key ceremony design or full penetration testing of your gateway. Those require separate specialists; we only teach how findings from those areas should appear in an audit narrative.

Language and schedule

Delivered in English, with optional evening slots for Korea-based teams. Exact cohort dates are shared after you contact us.