Flagship programme · 6 weeks

Payment Path Analytics

A working literacy course for people who own conversion on wallets, QR, and account-to-account rails. You leave with a marked path, a decline taxonomy, and a limitation paragraph you are willing to put in a board packet.

Person completing a mobile transfer at a desk
Week three still happens on paper before anyone opens a BI tool.

Who it is for

Product managers, growth, and ops leads who already ship a Thai or regional fintech app. You should be able to export an event dictionary or sit next to someone who can. You do not need to write production SQL, though reading a SELECT helps.

It is a poor fit if you want core banking ledger design, AML case management, or a certificate for LinkedIn. Those are outside the desk.

Informational fee

฿18,400 Open Desk

Included in Studio Year. Partner Table orgs may seat two people on the same run. No checkout on this site — write the desk to place a seat. See fees and refunds.

Modules

Six weeks, one path

  1. Capture hygiene

    What fired, what double-counted, what never left the client. We mark your event names against a ledger-friendly sheet. Most cohorts discover at least one retry that inflates “success.”

  2. Funnel geometry

    Draw the state machine for tap → authorise → capture → settle. Ecommerce four-step templates are retired in the first hour.

  3. Decline taxonomy

    Insufficient funds, issuer timeout, 3-D Secure loop, and “unknown” as a bucket you are no longer allowed to keep. Ops and product must share the same labels.

  4. Settlement lag

    When the app says paid and the rail disagrees. How to report in-flight money without pretending it is revenue.

  5. Retry economics

    Cost of a second challenge, customer drop after a soft decline, and when a retry is just cruelty dressed as conversion.

  6. Board-ready narrative

    Twelve minutes. One limitation sentence in the same paragraph as the claim. Arisa crosses out half the first draft on purpose.

Learning outcomes

Portrait of instructor Arisa Wongsawat

Instructor

Arisa Wongsawat

Former product analytics lead at a Bangkok digital bank. Arisa opened the Cache Routecore desk in 2019 and still runs Thursday readouts. She teaches in English, marks worksheets in red pencil, and will not discuss vendor bake-offs during class time.

FAQ

Do I need SQL?

Reading a SELECT is enough. We do not teach window functions from scratch. If your warehouse is a black box owned by another team, bring that person to the audit packet hour or send a redacted query.

Is this useful outside Thailand?

Yes, with a caveat. Rails and e-KYC vendors differ. The method — capture, geometry, limitation, narrative — travels. The examples are Thai-first because the desk is in Bangrak.

What will this programme not cover?

This course does not cover core banking ledger architecture or AML case management systems. It also does not implement tracking for you or certify you as a quant. If you need those, we will say so in the placement note rather than stretch Payment Path into a fiction.

Can I sit remotely?

Yes. Evening labs run 18:30–20:30 ICT. Remote seats join the same hour. Studio Year includes Bangrak evenings when you are in town.

From people who sat this syllabus

The decline taxonomy finally gave our ops lead a shared language with product. We stopped arguing about “failed payments” as if that were one thing.

Mali S. · product analytics, Bangkok digital bank

Settlement lag week was the uncomfortable one. We had been booking in-app “paid” as done. After class we split the tile. Finance was not delighted. Accuracy is rarely delightful.

Client in remittance · remote Open Desk

Ask about this programme

Placement only — not a checkout. Name, email, and a short note about the app you ship.