About the role
Stavtar builds StavPay, the expense, invoice, allocation and payments platform used by hedge funds, private-equity firms and family offices to run their entire payables cycle — from invoice capture and multi-entity allocation through to money actually leaving the bank.
This role sits in the Dev.Payment.Banks pod, which owns everything between a StavPay invoice and a bank. That means the payment rails themselves (ACH, wire, cheque, positive pay, ISO 20022), the bank-specific file templates, the FTP/API transmission jobs, the return and acknowledgement processing, and the reconciliation back into the GL feed.
This is a configuration, integration and onboarding role. The bulk of the week is spent standing up payment rails for new clients and banks, keeping live rails running, and diagnosing what went wrong when a payment file does not land. The depth required is in SQL, in payment file formats, and in the discipline of tracing a failure to its actual cause.
What the work actually looks like
Client L3 support & production troubleshooting - ~20%
Root-cause analysis on live payment failures across 30+ client instances — failed ACH/ISO files, stuck batches, mis-set invoice states, FTP delivery gaps, reconciliation breaks.
Client & bank onboarding - ~29%
Standing up new clients and new banking relationships: debit/credit account loads, payment rules, vendor payment detail grids, template configuration, FTP credentials and key vault setup.
Enablement & internal projects - ~22%
Domain deep-dives, documentation, QA and UAT environment setup, process improvement, training.
Meetings & coordination - ~17%
Working directly with BAs, QA, BPO, DBA/deployment, and occasionally client-side and bank-side contacts.
Infrastructure & scheduled jobs -~12%
Job schedulers, FTP/SFTP configuration, setting sync between QA/UAT/Prod, deployment support.
Key responsibilities
Payment rails & bank integration
• Configure and maintain bank payment templates end to end — invoice gr
📌 Payments Engineer (India)
🏢 Stavtar
📍 India