Australia's payments backbone just plugged its engineers into AI, and the result isn't fewer people—it's faster decisions when milliseconds cost millions.

The Summary

The Signal

AP+ isn't a startup playing with payment APIs. They operate PayTo, Osko, and BPAY—the plumbing that moves money for 25 million Australians. When they ship code, it touches real-time settlements, regulatory compliance across multiple frameworks, and integrations with every major Australian bank. This is critical infrastructure experimenting with AI tooling, which makes their implementation choices worth studying.

The deployment split AI assistance into two clear lanes. ChatGPT Enterprise handles the knowledge work: regulatory interpretation, documentation generation, onboarding new engineers to complex codebases. Codex assists with code completion and review. The division matters because it maps to where engineers actually lose time in financial infrastructure—not writing code, but understanding context.

"Engineers save hours on documentation, code review, and navigating regulatory complexity—time that now goes to judgment calls that actually need human brains."

Payments infrastructure has a unique constraint set that makes it a proving ground for AI tooling:

  • Zero tolerance for errors in production—a bug doesn't just break a feature, it breaks trust across the financial system
  • Regulatory frameworks that change frequently and require precise interpretation
  • Code that has to interface with legacy systems, modern APIs, and everything in between
  • Real-time operations where diagnosis speed during incidents directly impacts customer money access

AP+ reports quality improvements alongside time savings, which is the harder metric to move in this domain. In payments, "move fast and break things" gets you investigated by regulators. The fact that they're seeing both velocity and quality gains suggests the AI tooling is helping with the tedious-but-critical work—the kind that burns out senior engineers because it's necessary but not interesting.

The human-in-the-loop emphasis isn't just PR cover. In financial infrastructure, judgment calls around risk, compliance interpretation, and architectural decisions carry legal weight. AP+ is using AI to collapse the time between "I need to understand this regulation" and "I understand this regulation well enough to make a call," but the call itself still requires a human with their name on it.

The Implication

Watch how other financial infrastructure operators respond. If AP+ proves you can move faster without increasing risk, every payment processor, clearing house, and settlement system will need to deploy similar tooling or accept being structurally slower than competitors. The leverage gap between AI-assisted and non-assisted engineering teams in regulated domains is about to become visible in cycle time metrics.

For engineers in financial services: this pattern of AI-as-leverage rather than AI-as-replacement is the template. The roles that survive aren't the ones writing boilerplate or searching documentation—those tasks are getting compressed to seconds. The roles that matter are the ones making judgment calls when the answer isn't in the training data. If you're in payments, clearing, or settlement infrastructure and you're not experimenting with AI tooling for the grunt work, you're choosing to be slower than necessary.

Sources

OpenAI Blog