Payments Domain Lead

Job Description

We are looking for a Payments Industry Lead with at least 20 years of banking and banking technology experience including a minimum of 10 years' experience in the Payments domain covering platform implementation, program oversight with a keen eye on business development and client relationship management. The candidate should have been in leadership roles with industry presence, client relationships that can be accessed and leveraged to acquire new business.

͏

Following is a summary of the experience profile expected:

Business Development and Executive Experience:

• Should have been in Client facing roles with mandate to build relationships
• Demonstrable success with pursuits and achieving hard/soft revenue targets
• Experience with Presales function is preferred
• Experience with managing large accounts is preferred

͏

Domain Experience:

• Functional and technical understanding of payment architectures, core payment processing solutions and underlying payment business processes. Experience on any industry led platforms would be a bonus.
• Understanding of the basic payment hub architecture, the surround systems for payment hubs in a typical payment hub architecture
• Hands on experience in business rule configuration, profiles set up and other static data set up based on bank’s business requirement
• Understanding of underlying payment flows and business processes
• Understanding of surround system integration and the diverse protocols – RESTful, SOAP, APIs, File based, JMS, MQ
• Hands-on experience with platform implementation lifecycle – gap analysis, interface study, data migration, support of SIT, UAT, penetration testing.
• Exposure to any of the payment messaging formats would be a plus
• Understanding of Payments domain with demonstrable knowledge on - Real time, batch payments, high value payments
• Should understand the workflow for bulk payments (mass pay) and single payments (high value and real time)
• Should have a know-how of defect triaging for identifying the root cause of issue
• Must have exposure to typical payment platform components such as process engine, rules engine, format designer, alerts / notification engine, exceptions management, network wait queues
• Must have exposure to batch, real time interface with surround applications in a bank’s environment using industry standard protocols
• Should carry an appreciation of micro-services-based payment transaction flows