Darshan Ravishankar

Business Analyst @BMO

Toronto, ON, CA

Project - Lynx Release 2 - Payment ModernizationParticipants/Banks must at a minimum be able to o receive and process ISO 20022 payment messages (pacs.008, pacs.009 core, pacs.009cov, pacs.004 with the Business Application Header (BAH)) o process SWIFT Net system messages for the partial Y-copy service (xsys.002, and xsys.003). o send pacs.008, pacs.009 core, pacs.009 cov, and pacs.004 payments will be optional. o Attended MX Working Group meetings conducted by Payments Canada to review ISO MX Requirements and gain consensus on any critical topics discussed in the forum from the internal business and technical teamo Reviewed MX Remittance Policy details by attending LPG Sessions and discussed possible options with business and technical team to ensure enhanced structured remittance information is available to the customerso Attend Payments Canada\'s Lynx MX Rules sessions to review all the Lynx Rules for ISO MX Messages including but not limited to Lynx MX Contingency Procedures, Payment Transmission, Management of settlement mechanisms, Payment finality and return, Lynx Emergency procedures, Lynx MX payment message types and formats.MX messages in scope are as follows: o Payment clearing and settlement: Pacs.008, pacs.004, pacs.002, pacs.009core, pacs.009cov, payment Initiation: pain.001o o Cash Management: camt.052, camt.053, camt.054o Lynx Acceptance and Rejection: Xsys.002 and xsys.003o Business Application Header: Head.001

Ramaiah Institute Of Technology

Bachelor’s Degree