Payment Processing & CRM Integration Platform Experience: 15 years Role: Senior Technical Architect / Solution Architect Domain: FinTech / Payment Processing / ACH / Banking Integrations Engagement: Full time Position Summary We are looking for a highly experienced Senior Technical Architect to architect and lead the development of a Payment Processing Platform for a US-based Debt Settlemen Senior Technical Architect – Payment Processing & CRM Integration Platform

Experience: 15 years

Role: Senior Technical Architect / Solution Architect

Domain: FinTech / Payment Processing / ACH / Banking Integrations

Engagement: Full-Time

Position Summary

We are looking for a highly experienced Senior Technical Architect to architect and lead the development of a Payment Processing Platform for a US-based Debt Settlement business, starting from the ground up.

The Payment Platform will integrate with an existing/parallel Debt Settlement CRM. The scope is not to build the CRM. The primary responsibility is to design and implement the complete integration layer and payment-processing ecosystem, ensuring reliable, secure and real-time handshakes between the CRM, Payment Platform, banks, ACH processors and other financial service providers.

The candidate will own the technical architecture from inception through production and will work closely with the CRM team to define and implement APIs, webhooks, event flows, data synchronization, payment instructions, transaction status updates and reconciliation mechanisms.

This is a hands-on architect role requiring strong experience in payment systems and enterprise integrations.

Key Responsibilities

- Overall Architecture

Design the complete architecture of the Payment Processing Platform from scratch.

Define the boundary between the Debt Settlement CRM and Payment Platform.

Establish the API, event, webhook and integration architecture between the two systems.

Define module/service boundaries, data ownership and system responsibilities.

Design for scalability, security, reliability and financial transaction integrity.

- CRM ↔ Payment Platform Integration

Design and implement all required handshakes between the CRM and Payment Platform, including:

Customer creation/update

Payment account/sub-account creation

Bank account linking

Payment authorization

Payment scheduling

Payment modification/cancellation

ACH debit initiation

ACH credit/disbursement

Payment status updates

Failed payment notifications

Returns and reversals

Refunds

Settlement updates

Account balance updates

Transaction history

Ledger updates

Reconciliation status

Webhook/event notifications

Error and exception handling The architect will establish clear request/response contracts, event contracts, authentication mechanisms, retry mechanisms and idempotency rules for every integration.

- Payment Processing Architecture

Architect the complete payment lifecycle, including:

CRM → Payment Platform → Bank/Processor → ACH Network → Bank/Processor → Payment Platform → CRM

Define how the system handles:

Payment initiation

Authorization

Processing

Pending status

Successful transactions

Failed transactions

ACH returns

Reversals

Refunds

Settlement

Reconciliation

Exceptions

- ACH / NACHA

Design ACH processing architecture and workflows.

Understand NACHA file formats, transaction codes and ACH lifecycle.

Design ACH submission, processing, returns and settlement flows.

Handle ACH return codes and appropriate downstream updates.

Design integration with ACH processors/banks.

Ensure appropriate validation and auditability of ACH transactions.

- Ledger & Financial Architecture

Design the financial data model and transaction architecture for:

Customer accounts

Sub-accounts

Transaction ledger

Credits/debits

Available balance

Pending balance

Settled balance

Fees

Payment allocations

Settlement payments

Refunds

Reversals

Adjustments

Reconciliation

Strong preference for candidates with experience designing double-entry or transaction-based financial ledgers.

- Sub-Account Architecture

Design the architecture for managing individual customer/sub-accounts, including:

Account creation

Account status

Account balances

Funding

Payments

Allocations

Transaction history

Restrictions/holds

Reconciliation

Account closure

- Banking & Payment Processor Integrations

Architect a versatile integration framework allowing the platform to connect with:

Banks

ACH processors

Payment processors

Account verification providers

KYC/identity providers where applicable

Other financial service providers The architecture should allow additional processors/providers to be added without major changes to the core platform.

- API & Integration Architecture

Define

REST APIs

Webhooks

Event-driven communication

Authentication/authorization

API versioning

Request/response standards

Error standards

Retry mechanisms

Timeout handling

Idempotency

Correlation IDs

Transaction tracking

Audit logging

- Reliability & Transaction Integrity

Financial transactions must be processed reliably and without duplication.

The architect will design mechanisms for:

Idempotent payment requests

Duplicate prevention

Exactly-once business processing where required

Retry and recovery

Dead-letter handling

Transaction state management

Partial failure handling

Timeout management

Reconciliation

Disaster recovery

- Security

Design security controls for sensitive financial and customer information, including:

API security

OAuth/JWT or equivalent authentication

RBAC

Encryption in transit and at rest

Secrets management

PII protection

Tokenization where appropriate

Audit trails

Secure webhook validation





Access controls

Secure logging

Experience with PCI DSS, SOC 2, GLBA and US financial-services security requirements is highly desirable.

- Technical Leadership

Lead the technical architecture and development of the platform.

Work closely with Business Analysts to convert requirements into technical specifications.

Work with the CRM development team to define integration contracts.

Guide developers on implementation.

Conduct architecture and code reviews.

Identify technical risks and dependencies.

Establish coding and integration standards.

Resolve complex technical and architectural issues.

Ensure development remains aligned with the approved architecture.

- Cloud & DevOps

Design and guide

Cloud infrastructure

Development/QA/UAT/Production environments

CI/CD pipelines

Containerization

Monitoring

Logging

Alerting

Backup

Disaster recovery

High availability

Security controls

Required Technical Skills

10–15 years of software engineering experience.

5 years in architecture/technical leadership roles.

Strong experience building FinTech/payment-processing platforms.

Strong hands-on experience with Node.js / Python/TypeScript.

Experience with Next.js/Nest.js is desirable.

Strong experience with MySQL/PostgreSQL or equivalent relational databases.

Strong REST API and integration experience.

Experience with event-driven architecture and webhooks.

Strong understanding of ACH and NACHA.

Experience with banking/payment processor integrations.

Experience designing financial transaction and ledger systems.

Experience with sub-account/wallet/account architectures.

Strong understanding of reconciliation.

Experience with message queues such as Kafka, RabbitMQ, SQS or equivalent.

Experience with Redis or equivalent caching technologies.

Strong AWS/Azure/GCP experience.

Strong understanding of API security and encryption.

Experience with Docker and CI/CD.

Strong understanding of distributed systems and fault-tolerant architectures.

Must-Have Domain Experience The ideal candidate should have hands-on experience with several of the following:

Payment processing

ACH

NACHA

Banking APIs

Payment gateways

Payment orchestration

Financial ledgers

Reconciliation

Sub-accounts

Wallets

Transaction processing

Payment failures/returns

Refunds/reversals

Webhooks

Financial APIs

Candidates with actual payment-platform architecture experience should be preferred over candidates who have only generic enterprise architecture experience.

Key Deliverables The architect will be responsible for producing and maintaining:

1.Overall Solution Architecture

2.CRM ↔ Payment Platform Architecture

3.System Context Diagram

4.Integration Architecture

5.API Architecture

6.API Specifications

7.Webhook Specifications

8.Payment Sequence Diagrams

9.ACH/NACHA Architecture

10.Banking Integration Architecture

11.Ledger Architecture

12.Sub-Account Architecture

13.Database ERD

14.Transaction State Models

15.Error/Retry Architecture

16.Reconciliation Architecture

17.Security Architecture

18.Cloud/Infrastructure Architecture

19.CI/CD Architecture

20.Technical Development Roadmapt business, starting from the ground up.

The Payment

Platform will integrate with an existing/parallel Debt Settlement CRM. The scope is not to build the CRM. The primary responsibility is to design and implement the complete integration layer and payment-processing ecosystem, ensuring reliable, secure and real-time handshakes between the CRM, Payment Platform, banks, ACH processors and other financial service providers. The candidate will own the technical architecture from inception through production and will work closely with the CRM team to define and implement APIs, webhooks, event flows, data synchronization, payment instructions, transaction status updates and reconciliation mechanisms. This is a hands-on architect role requiring strong experience in payment systems and enterprise integrations.

Key Responsibilities 1.

Overall

Architecture ·Design the complete architecture of the Payment Processing Platform from scratch. ·Define the boundary between the Debt Settlement CRM and Payment Platform. ·Establish the API, event, webhook and integration architecture between the two systems. ·Define module/service boundaries, data ownership and system responsibilities. ·Design for scalability, security, reliability and financial transaction integrity.

2. CRM ↔ Payment Platform Integration Design and implement all required handshakes between the CRM and Payment Platform, including: ·Customer creation/update ·Payment account/sub-account creation ·Bank account linking ·Payment authorization ·Payment scheduling ·Payment modification/cancellation ·ACH debit initiation ·ACH credit/disbursement ·Payment status updates ·Failed payment notifications ·Returns and reversals ·Refunds ·Settlement updates ·Account balance updates ·Transaction history ·Ledger updates ·Reconciliation status ·Webhook/event notifications ·Error and exception handling The architect will establish clear request/response contracts, event contracts, authentication mechanisms, retry mechanisms and idempotency rules for every integration. 3.

Payment Processing Architecture

Architect the complete payment lifecycle, including: CRM → Payment Platform → Bank/Processor → ACH Network → Bank/Processor → Payment Platform → CRM Define how the system handles:



·Payment initiation ·Authorization ·Processing ·Pending status ·Successful transactions ·Failed transactions ·ACH returns ·Reversals ·Refunds ·Settlement ·Reconciliation ·Exceptions 4. ACH / NACHA ·Design ACH processing architecture and workflows. ·Understand NACHA file formats, transaction codes and ACH lifecycle. ·Design ACH submission, processing, returns and settlement flows. ·Handle ACH return codes and appropriate downstream updates. ·Design integration with ACH processors/banks. ·Ensure appropriate validation and auditability of ACH transactions.

5. Ledger &

• Financial Architecture Design the financial data model and transaction architecture for: ·Customer accounts ·Sub-accounts ·Transaction ledger ·Credits/debits ·Available balance ·Pending balance ·Settled balance ·Fees ·Payment allocations ·Settlement payments ·Refunds ·Reversals ·Adjustments ·Reconciliation Strong preference for candidates with experience designing double-entry or transaction-based financial ledgers.

6. Sub-Account Architecture Design the architecture for managing individual customer/sub-accounts, including: ·Account creation ·Account status ·Account balances ·Funding ·Payments ·Allocations ·Transaction history ·Restrictions/holds ·Reconciliation ·Account closure 7. Banking &

• Payment Processor Integrations Architect a adaptable integration framework allowing the platform to connect with: ·Banks ·ACH processors ·Payment processors ·Account verification providers ·KYC/identity providers where applicable ·Other financial service providers The architecture should allow additional processors/providers to be added without major changes to the core platform.

8. API &

• Integration Architecture Define: ·REST APIs ·Webhooks ·Event-driven communication ·Authentication/authorization ·API versioning ·Request/response standards ·Error standards ·Retry mechanisms ·Timeout handling ·Idempotency ·Correlation IDs ·Transaction tracking ·Audit logging 9. Reliability &

• Transaction Integrity Financial transactions must be processed reliably and without duplication.

The architect will design mechanisms for: ·Idempotent payment requests ·Duplicate prevention ·Exactly-once business processing where required ·Retry and recovery ·Dead-letter handling ·Transaction state management ·Partial failure handling ·Timeout management ·Reconciliation ·Disaster recovery 10.

Security

Design security controls for sensitive financial and customer information, including: ·API security ·OAuth/JWT or equivalent authentication ·RBAC ·Encryption in transit and at rest ·Secrets management ·PII protection ·Tokenization where appropriate ·Audit trails ·Secure webhook validation ·Access controls ·Secure logging Experience with PCI DSS, SOC 2, GLBA and US financial-services security requirements is highly desirable. 11.

Technical

Leadership ·Lead the technical architecture and development of the platform. ·Work closely with Business Analysts to convert requirements into technical specifications. ·Work with the CRM development team to define integration contracts. ·Guide developers on implementation. ·Conduct architecture and code reviews. ·Identify technical risks and dependencies. ·Establish coding and integration standards. ·Resolve complex technical and architectural issues. ·Ensure development remains aligned with the approved architecture.

12. Cloud &

• DevOps Design and guide: ·Cloud infrastructure ·Development/QA/UAT/Production environments ·CI/CD pipelines ·Containerization ·Monitoring ·Logging ·Alerting ·Backup ·Disaster recovery ·High availability ·Security controls Required Technical Skills ·10–15 years of software engineering experience. ·5 years in architecture/technical leadership roles. ·Strong experience building FinTech/payment-processing platforms. ·Strong hands-on experience with Node.js / Python/TypeScript. ·Experience with Next.js/Nest.js is desirable. ·Strong experience with MySQL/PostgreSQL or equivalent relational databases. ·Strong REST API and integration experience. ·Experience with event-driven architecture and webhooks. ·Strong understanding of ACH and NACHA. ·Experience with banking/payment processor integrations. ·Experience designing financial transaction and ledger systems. ·Experience with sub-account/wallet/account architectures. ·Strong understanding of reconciliation. ·Experience with message queues such as Kafka, RabbitMQ, SQS or equivalent. ·Experience with Redis or equivalent caching technologies. ·Strong AWS/Azure/GCP experience. ·Strong understanding of API security and encryption. ·Experience with Docker and CI/CD. ·Strong understanding of distributed systems and fault-tolerant architectures. Must-Have Domain Experience The ideal candidate should have hands-on experience with several of the following: ·Payment processing ·ACH ·NACHA ·Banking APIs ·Payment gateways ·Payment orchestration ·Financial ledgers ·Reconciliation ·Sub-accounts ·Wallets ·Transaction processing ·Payment failures/returns ·Refunds/reversals ·Webhooks ·Financial APIs Candidates with actual payment-platform architecture experience should be preferred over candidates who have only generic enterprise architecture experience.

Key Deliverables

The architect will be responsible for producing and maintaining:

1.Overall Solution Architecture

2.CRM ↔ Payment Platform Architecture

3.System Context Diagram

4.Integration Architecture

5.API Architecture

6.API Specifications

7.Webhook Specifications

8.Payment Sequence Diagrams

9.ACH/NACHA Architecture

10.Banking Integration Architecture

11.Ledger Architecture

12.Sub-Account Architecture

13.Database ERD

14.Transaction State Models

15.Error/Retry Architecture 16.Reconciliation Architecture

17.Security Architecture

18.Cloud/Infrastructure Architecture

19.CI/CD Architecture

20.Technical Development Roadmap

Pay: ₹175,000.00 - ₹225,000.00 per month

Benefits

- Paid time off
- Provident Fund

Work Location: Remote

📌 Senior Technical Architect (India)
🏢 Driptas Sparkle Yields
📍 India