PBRC — Payment Business Rules Configuration · Omkar Kulsange

All work

PBRC — Payment Business Rules Configuration

Turned rule changes from an engineering ticket into a governed self-service tool. Ops teams build, approve and activate payment rules in real time.

Year

2025–2026

Role

Lead UX Designer & Tech Analyst

Client

Big-four Australian bank

Timeline

2025–Present

What changed

1

1

Zero deployment cycles: approved rules go live immediately

Zero deployment cycles: approved rules go live immediately

2

2

Maker/checker enforced in the workflow, with change-diff review

Maker/checker enforced in the workflow, with change-diff review

3

3

One unified rule model replaced three separate entities

One unified rule model replaced three separate entities

4

4

Three rounds of usability testing, each one changing the design

Three rounds of usability testing, each one changing the design

Have a problem like this?

Open to roles from November. Get in touch to discuss senior UX and product design opportunities.

Email me

Next case study

PSDS — Payment Static Data Setup

A platform for all payment static data, designed for reuse from day one. Starts with time-critical RTGS cutoff exceptions.