Visa · Accounting Platform · India and Australia

Payment accounting with traceable events and dedicated ownership

Evolution of the Visa accounting platform using Pismo capabilities, event-driven architecture, AI-assisted reconciliation, and a new operating model.

1–20 → 0–1reconciliation defects/week

800 → 250 mscross-region latency

≈ 95%reduction at the previous upper bound

3 teamspermanent ownership

The challenge

The platform supported payment operations in India and Australia, but fragmented integrations, limited traceability, and latency across the United States, India, and Australia caused between one and twenty reconciliation defects per week. Banking and regulatory changes were frequent.

Initial state

Events and integrations with limited traceability
Recurring reconciliation failures
Cross-region latency of approximately 800 ms
Temporary support and fragmented ownership

→

Target platform

Event contracts and end-to-end correlation
Idempotency, deduplication, and replay
Optimized private connectivity
Permanent teams with clear missions

What I personally led

Target architecture

Technical design and operating model for the accounting platform, including the adoption of Pismo capabilities.

Platform and reliability

Scalability, CI/CD, security governance, and cross-region integration.

International alignment

Engineering, Finance, Compliance, regional teams, and Visa specialists in Austin.

Precise scope: I led the technical adoption of the Pismo accounting platform within Visa, not the Pismo acquisition.

The key decision

Combine the Pismo accounting flow with event-driven architecture and Amazon Bedrock-assisted reconciliation. Every regulatory change became a versioned, tested, and approved engineering change.

Payment

Context-rich event

Pismo / acquiring

Accounting ledger

Reconciliation

Approved adjustment

Event identity

Transaction ID, correlation ID, timestamp, status, and business context.

Resilience

Idempotency, deduplication, controlled retries, DLQ, and replay.

Governance

Automated tests, approval gates, security checks, and controlled releases.

Dedicated operating model

TEAM 01

Accounting Engineering

Accounting rules
Event contracts
Pismo integration

TEAM 02

SRE

Observability
Capacity and performance
Incident response

TEAM 03

DevSecOps

Infrastructure as code
Security controls
Delivery pipeline

AI supporting financial judgment

Bedrock agents using RAG grounded in accounting rules, regulatory requirements, and validated procedures correlated events across Visa, Pismo, acquiring systems, and accounting records.

Detect

Missing events, duplicates, idempotency issues, and broken accounting sequences.

→

Recommend

Investigate the cause and suggest evidence-based corrective action.

→

Validate

Sensitive or low-confidence cases reviewed by the accounting manager; no autonomous financial adjustments.

Measurable outcomes

Reconciliation defectsup to 20/week → 0–1/week

Cross-region latency800 ms → 250 ms

Monitored accounting complaintseliminated

Lesson: an accounting platform is more than an integration project. It requires financial correctness, resilient architecture, strong network design, regulatory governance, and clear ownership. AI improved speed and consistency, while final accountability remained with qualified professionals.