Building secure, compliant payment systems that stay reliable in production.

I design and maintain payment platforms in regulated environments — from PCI-driven portals and vendor integrations to IVR infrastructure and kiosk applications. My focus is stability, correctness, and controlled evolution.

Correctness-first systems

PCI & compliance constraints

Vendor integrations

IVR / Asterisk

Kiosk apps

Operational clarity

Open to a conversation View Resume (PDF) LinkedIn See highlights

Status: Not actively job hunting — open to the right conversation.

ABOUT

I’m a Principal Software Engineer focused on payments engineering and platform design. I like the hard parts: multi-system integrations, retries and idempotency, compliance constraints, and production realities. My goal is simple: build systems that behave correctly under stress and remain understandable to the teams that run them.

Systems architecture Design for constraints: PCI, vendor contracts, operational ownership, and realistic failure modes.

Production reliability Observability, incident reduction, safe rollouts, and behavior under retries/timeouts.

Payments domain depth Portals, gateways, kiosk flows, IVR systems, and real-world edge cases.

Controlled evolution Modernize without drama: incremental changes that reduce risk and keep shipping.

PRINCIPLES

Correctness First Payment systems must handle retries, integrations, and failures without losing integrity. Edge cases are part of the product.

Compliance as Input PCI constraints shape architecture decisions. Security and delivery have to coexist — not compete.

Operational Clarity Systems should be maintainable, observable, and understandable by the team that supports them.

Reduce risk, then scale Stability buys you speed. Make behavior predictable before you add complexity.

“Payments engineering is where correctness meets reality: vendors, timeouts, partial failures, compliance rules, and humans.”

FOCUS AREAS

PCI compliance & secure design Architecture choices shaped by regulated environments and real audit requirements.

Vendor integrations Stable integrations with clear contracts, timeouts, retry semantics, and failure handling.

IVR / Asterisk infrastructure Operationally dependable voice/payment workflows built to survive noisy real-world conditions.

Kiosk applications Reliable card-present and kiosk payment experiences with strong observability and rollback options.

CAREER HIGHLIGHTS

Long-term platform ownership Owned and evolved payment services platforms over multiple years, balancing uptime, compliance, and delivery.

Stability & incident reduction Introduced operational clarity (logs/metrics/traces, runbooks, safer releases) to reduce surprise failures.

Integration hardening Improved reliability across vendor integrations by making retries and idempotency explicit and testable.

Modernization without downtime Incremental refactors and migration paths designed for real production constraints.

Want the detailed version? My full experience is on LinkedIn: linkedin.com/in/paymentsengineer

CONTACT

Email juan@elitewebdeveloper.com
Best for: introductions, quick questions, thoughtful problem statements.

Resume Resume.pdf
Note: PDF opens in a new tab.

LinkedIn /in/paymentsengineer
Status: Not actively looking — open to the right conversation.

Status Not actively job hunting — open to the right conversation.

If you reach out, include: context, constraints, and what “success” looks like.