CONTENT 3 Initiating the project 4

Implementation chal-lenges 5 FPS, SWIFT, CHAPS, SEPA 6 Old Data Flow 7 New Data Flow 8 Pre-Live Pound Test

The project was initiated with the goal to create new and better services and code compared to the exist-ing application. Initial project scope covered: · Analyse current design · Code review · Reverse engineer current application scope to re-trieve requirements · Reduce code duplicates · Design new solution and present UML diagrams · Click To find more about project details · Finance and Payments Architect DevOps Method-ology · Architect DevOps Communication Methodology · Certified Beta Release Methodology · How-To Certified Beta Release Methodology · Our Moneycorp success story · If the links do not work use Our website http://www.adtsoft.co.uk and read our “Greenfield Innovations”

Initiating the project

Solution implementation was started with replacing the services. The application is Windows Service based and all the logic was implemented in on the service level. After the requirements were retrieved from the old services the new implementation scope was defined. We did two FPS implementations and this was major challenge. After the first FPS solution was completed and tested the major change in on Moneycorp partner bank site happen. We have to move from ISO20022 payment message formatting to SWIFT formatting. The follow up was to extend the so-lution with components reusability message proces-sors handling message processor switching. Solution Design Common Components Þ Custom DBBContext and POCO classes and reposi-tories Þ Workflow activities Þ Multi-threading Þ Data, Queues and Timers managers SWIFT payment message processor ISO20022 payment message processor

Implementation challenges

After the first lesson when we refactored the solution to add interchangeable payment message proces-sor we improved implementation speed by creating instances in the common module from the compo-nents and embed the implementation into Service-Host. Another challenge was reuse of the existing da-tabase stored procedures, functions and tables and later integrate both solutions — the new greenfield and remaining part of the existing application. The business logic should manage · ISO20022—SEPA, Europe, APAC, US, International ISO20022 payment format type · SWIFT—CHAPS, FPS, SWIFT format type · Pre-Live pound live account payment test—Send payment with live transfer of £1 and process bank reply messages · Multi-bank integration

FPS, SWIFT, CHAPS, SEPA

Old Dataflow was already obsolete and Moneycorp had already created vision how to integrate the dif-ferent incoming payment flows. Taking in account Moneycorp envisioning we created Solution and Technical design. The implementation take place to improve the data flow to be provided by single source

Old data flow

Text fileInput data flow

Queues

Interop SQL DataLoad SQL Data

Process File

Process Queues and Reload SQL DataGenerate SWIFT Format

ISO20022 Format

We designed the new data flow to represent real live payment input and output solution. We do process the single incoming data source flow and store it into the database. The stored data is processed further to create specific payment details as below FPS, SWIFT, CHAPS, SEPA (APAC, EU, US, International) and send the payment messages to the Moneycorp partnering bank.

New Dataflow

Single format consistent input Process incoming data

SEPA CHAPS SWIFT FPS

SWIFTFileAct

Pre-Live Test FPS LIVE ACCOUNTSWIFTMoneycorp office

Payment

FILEAct

ISO20022BANK

CHAPS/SWIFT BANK

Send Live FPS payment

Receive MT Payment confirmation

WE BELIEVE YOU ARE OUR NEXT SUCCESSFUL CLIENT

THANK YOU!!