Business Analyst - Payments

Posted yesterday

diversity nexusPhoenix (AZ)

Computer Systems AnalystsComputer Systems Design Services

SENIORITY

Lead

About the role

Job TitleExperience: 8+ years in enterprise architecture, platform engineering, or solutions architecture within the banking, fintech, or payments domain.Payments Transformation: Design, plan, and execute the modernization of monolithic payment platforms into microservices and event-driven architectures.Tokenization & Security: Architect robust, PCI DSS v4.0 compliant tokenization strategies to replace sensitive Cardholder Data (CHD) and enable tokenized payment models across all channels.Integration & Orchestration: Design payment orchestration layers that support global domestic and cross-border rails (e.g., ISO 20022, SWIFT, FedNow, ACH).Architecture Governance: Establish architectural blueprints, guidelines, and reference architectures for authorization, clearing, settlement, and reconciliation flows.Core Expertise: Deep, hands-on experience in payment tokenization standards, encryption, HSM/KMS secrets management, and zero-trust security. Payments Domain Tokenization Platform Architecture & Design, REST API, SOAP Implementations, Java, Python, SQL, Springboot, Jira, Rally, Clarity, SAFe.

Before you apply

Applying takes about a minute. These four things decide how fast it moves after that.

Your profile is current

It's what we read first. Occupations, seniority and locations matter more than a long history.

Two examples you can talk through

Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.

A number in mind

What you're on now and what would make you move. We negotiate better when we know both.

Your notice period

Employers plan around it, and it's the question that stalls offers most often.

Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.