Business Analyst - Payments/Fiserv SME
RIT Solutions Inc/ Tech Dev IT/ Texperts Inc/ConceptsIT, Inc., Atlanta, GA, United States
Job Description
Role Summary
The Business Analyst (Payments / Client SME) is responsible for providing deep subject matter expertise in Client payment processor data, including detailed understanding of Client data fields, coded values, transaction flows, business rules, and mapping logic. This role serves as the primary functional lead for interpreting processor data and translating it into clear business rules, mappings, KPI definitions, and implementation-ready functional specifications. This individual is expected to play a critical role in bridging the gap between raw Client source data and the target canonical / semantic design, working closely with the Data Architect, Solution Lead, and client stakeholders to ensure that processor-specific logic is accurately understood, documented, and translated for downstream implementation.
Deep hands-on knowledge of Client processor data structures and field-level usage is a core requirement for this role
Serve as the primary SME for Client payment processor data, including field-level interpretation and business meaning Provide deep expertise in Client data elements, transaction attributes, coded values, status fields, event types, and processor-specific logic Analyze and document source-to-business mappings for Client data fields Interpret and explain processor-specific transaction lifecycle behavior, including statuses, approvals, declines, reversals, adjustments, settlement-related indicators, and other payment events as applicable Lead definition and documentation of business rules, code translations, and field usage guidance Partner with the Data Architect to translate detailed Client field logic into canonical structures, semantic models, and implementation-ready mappings Support identification and rationalization of overlapping, ambiguous, or inconsistently used Client source fields Define and document KPI logic based on Client data, including inclusion/exclusion rules, filters, assumptions, and edge cases Facilitate working sessions with business stakeholders and technical teams to clarify field meaning, data usage, and reporting intent Support issue triage during design, client implementation, validation, and UAT by clarifying whether issues are related to source interpretation, business logic, or implementation Maintain traceability across requirements, Client source fields, mapping rules, transformations, and KPI outputs • Contribute to documentation, design reviews, knowledge transfer, and implementation guidance for client-led execution
Job Responsibilities
Serve as the primary SME for Client payment processor data, including field-level interpretation and business meaning
Provide deep expertise in Client data elements, transaction attributes, coded values, status fields, event types, and processor-specific logic
Analyze and document source-to-business mappings for Client data fields
Interpret and explain processor-specific transaction lifecycle behavior, including statuses, approvals, declines, reversals, adjustments, settlement-related indicators, and other payment events as applicable
Lead definition and documentation of business rules, code translations, and field usage guidance
Partner with the Data Architect to translate detailed Client field logic into canonical structures, semantic models, and implementation-ready mappings
Support identification and rationalization of overlapping, ambiguous, or inconsistently used Client source fields
Define and document KPI logic based on Client data, including inclusion/exclusion rules, filters, assumptions, and edge cases
Facilitate working sessions with business stakeholders and technical teams to clarify field meaning, data usage, and reporting intent
Support issue triage during design, client implementation, validation, and UAT by clarifying whether issues are related to source interpretation, business logic, or implementation
Maintain traceability across requirements, Client source fields, mapping rules, transformations, and KPI outputs •
Contribute to documentation, design reviews, knowledge transfer, and implementation guidance for client-led execution
Role Summary
The Business Analyst (Payments / Client SME) is responsible for providing deep subject matter expertise in Client payment processor data, including detailed understanding of Client data fields, coded values, transaction flows, business rules, and mapping logic. This role serves as the primary functional lead for interpreting processor data and translating it into clear business rules, mappings, KPI definitions, and implementation-ready functional specifications. This individual is expected to play a critical role in bridging the gap between raw Client source data and the target canonical / semantic design, working closely with the Data Architect, Solution Lead, and client stakeholders to ensure that processor-specific logic is accurately understood, documented, and translated for downstream implementation.
Deep hands-on knowledge of Client processor data structures and field-level usage is a core requirement for this role
Serve as the primary SME for Client payment processor data, including field-level interpretation and business meaning Provide deep expertise in Client data elements, transaction attributes, coded values, status fields, event types, and processor-specific logic Analyze and document source-to-business mappings for Client data fields Interpret and explain processor-specific transaction lifecycle behavior, including statuses, approvals, declines, reversals, adjustments, settlement-related indicators, and other payment events as applicable Lead definition and documentation of business rules, code translations, and field usage guidance Partner with the Data Architect to translate detailed Client field logic into canonical structures, semantic models, and implementation-ready mappings Support identification and rationalization of overlapping, ambiguous, or inconsistently used Client source fields Define and document KPI logic based on Client data, including inclusion/exclusion rules, filters, assumptions, and edge cases Facilitate working sessions with business stakeholders and technical teams to clarify field meaning, data usage, and reporting intent Support issue triage during design, client implementation, validation, and UAT by clarifying whether issues are related to source interpretation, business logic, or implementation Maintain traceability across requirements, Client source fields, mapping rules, transformations, and KPI outputs • Contribute to documentation, design reviews, knowledge transfer, and implementation guidance for client-led execution
Job Responsibilities
Serve as the primary SME for Client payment processor data, including field-level interpretation and business meaning
Provide deep expertise in Client data elements, transaction attributes, coded values, status fields, event types, and processor-specific logic
Analyze and document source-to-business mappings for Client data fields
Interpret and explain processor-specific transaction lifecycle behavior, including statuses, approvals, declines, reversals, adjustments, settlement-related indicators, and other payment events as applicable
Lead definition and documentation of business rules, code translations, and field usage guidance
Partner with the Data Architect to translate detailed Client field logic into canonical structures, semantic models, and implementation-ready mappings
Support identification and rationalization of overlapping, ambiguous, or inconsistently used Client source fields
Define and document KPI logic based on Client data, including inclusion/exclusion rules, filters, assumptions, and edge cases
Facilitate working sessions with business stakeholders and technical teams to clarify field meaning, data usage, and reporting intent
Support issue triage during design, client implementation, validation, and UAT by clarifying whether issues are related to source interpretation, business logic, or implementation
Maintain traceability across requirements, Client source fields, mapping rules, transformations, and KPI outputs •
Contribute to documentation, design reviews, knowledge transfer, and implementation guidance for client-led execution