Dinesh R

Project - AMH (Payment Gateway) CBPR+ and RTGS MX migration

Client - Standard Chartered bank

Worked projects - SADC ZM,SIRF ZM, BW RTGS,ZM RTGS

• Alliance Messaging Hub is a modular, financial messaging solution for our network. Highly configurable and resilient, it uses the latest technology to manage messages and files for various formats in parallel, providing extensive throughput and sophisticated data management.
• Fully integrated into Swift’s product portfolio, AMH meets the needs of a wide range of financial institutions, from those with more traditional operations to those with very specific messaging requirements.
• Migration of MT to MX for all the RTGS Countries
• Worked on PACS, CAMT and XSYS ISO MX messages
• Processed outward and inward flow of MX messages
• Tested validation of payload,crossfield,Duplicate check,initial check,ACK format and NACK format
• All the validation & message creation is done through WB(Manual input)
• Tsaas check and UAM check for Swift messages
• Inward & Outward RTGS rules and report testing
• End to end payment processing
• Preparing Daily status report
• Creation of Business scenario document and providing walkthrough to stakeholders
• Test cases preparation, logging defects all the test execution is done through Azure devops
• Domestic and cross border payments

Project - Collections Application

Client - YOMA bank

• Working in product company as QA and role is to test all features newly introduced in collection application of major banks in Australia
• Worked in agile environment
• Tested features( Client maintenance, strategy studio, batch integration, reports, actions, grid filter, bulk communication)
• Raised more than 250 bugs/defects in last 6 months
• Experience in UI and API testing
• Experience in preparing Test planning, test case preparation, test strategies and coverage, Test Execution
• Having experience includes working on projects like On-call production support team and involving in User acceptance testing and Regression Testing
• Experience in performing Regression, UAT and Negative Testing
• Experience in preparing Daily Status reports

Project - Global Cards & Payments

Client - President choice financial

• Experience in understanding the SWIFT MT (MT103, MT202, MT202 COV) payment messages and ISO 20022 Standards
• Experience in handling FPS, PAIN, PACS, SEPA payments
• Experience in handling Nostro and Vostro accounts
• Analyzing the business and functional requirements through BRDs, FRDs and Walkthrough
• Involved in the preparation of Test Scenarios, Test Conditions and Test Cases
• Ensured that the test cases were complete to test the business functionalities
• Identification and setup of Test Data
• Involved in Web testing as well as Mobile Testing on Android, iOS platform.
• Responsible for reporting daily tasks activities on timely basis to internal teams
• Reporting the defects through Defect Tracking/Test Management tool – JIRA
• Reporting to business teams & Onsite Coordinator about status of test activities on a daily basis
• Interacting with development and business teams to resolve issues

Project - Payments Sanction screening

Client -Citibank

• Experience in understanding the SWIFT MT payment messages, SWIFT ISO 20022 MX messages
• Experience in handling FPS, PAIN, PACS, SEPA payments
• Experience in clearing and settlements
• Experience in handling Nostro and Vostro accounts
• Sanction Screening ops - Check the payments on behalf of a number of branches
• The payments processed on these branches fall into to the Sanctions queue for verification of the payments from the Sanctions perspective based on the Global and local Sanctions regulations
• Sanction screening ops reviews the potential matches
• Positive matches and matches that cannot be resolved must be escalated in accordance with the escalation procedures defined by the business unit
• The initial review of potential matches generally involves the review of non-complex potential matches and is performed by staff processing transaction
• The review involves at least two individuals prior to a decision to process or stop a payment
• If both the maker and the checker agree that the match is positive or disagree as to whether a match is positive or false, the match must be escalated to the next level of review, to the compliance team (i.e., L2)