FIN Copy and Closed User Group - PowerPoint PPT Presentation

fin copy and closed user group n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
FIN Copy and Closed User Group PowerPoint Presentation
Download Presentation
FIN Copy and Closed User Group

play fullscreen
1 / 53
FIN Copy and Closed User Group
711 Views
Download Presentation
Patman
Download Presentation

FIN Copy and Closed User Group

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. FIN Copy and Closed User Group Ali Bakhtaoui Customer Services Fin Copy Seminar, Albanian Interbank Payment System. Tirana, Albania: 05 September 2003 FinCopy_CUG_v1.ppt

  2. AGENDA FIN & FIN Copy concept Closed User Group Service Profile & Message Matrix Message Flow Implementation Schedule Fallback Connectivity Supporting FIN Copy

  3. AGENDA FIN & FIN Copy concept Closed User Group Service Profile & Message Matrix Message Flow Implementation Schedule Fallback Connectivity Supporting FIN Copy

  4. FIN Copy FIN User A User B User A User B Central Institution FIN & FIN Copy concept

  5. T What is FIN Copy? Y • Value added message copyingto central institution • Operates in Y-copy mode : • ‘store-copy-authorise-forward’ • Operates between 3 parties: • Sending institution (ordering) • Central institution(clearing, netting or settlement) • Receiving institution (beneficiary)

  6. Bank A Bank B Central Institution Use of FIN Copy for RTGS Payment Order SWIFT FIN Network Payment order (MT103, 102, 202, 205) Y- Copy

  7. Bank A Bank B Central Institution Use of FIN Copy for RTGS Settlement Request SWIFT FIN Network Payment order Y- Copy Settlement Request (MT096)

  8. Bank A Bank B Central Institution FIN Copy for RTGS Authorisation Approved / Settled Payment order SWIFT FIN Network Payment order Y- Copy Settlement Request (MT 096) Authorisation (MT 097)

  9. Bank A Bank B Central Institution FIN Copy Rejection SWIFT FIN Network Payment order Y- Copy Abort Notification (MT 019) Settlement Request (MT 096) Rejection (MT 097)

  10. MT 096 FIN Copy to Central Institution Message Basic Header Application Header User Header Text Block “Basic Header Application Header User Header Text (some or all fields) Trailer block” Envelope Copy of original Message Trailer Block

  11. MT 097 FIN Copy Message Authorisation/Refusal Notification Basic Header Application Header User Header Text Block “FIN Copy Service Identifier Code : AIP MRF Trailer from MT 096 Acceptance/Rejection Code M Envelope M (if codeword ‘Reject’, otherwise not present) Abort Reason Information for sender Information for receiver” O Trailer Block

  12. Bank A Bank B Central Institution FIN Copy Authentication SWIFT FIN Network MAC: A to B Y- Copy PAC1: A to Central Institution Destination PAC2: Central Institution Destination to B Live :STANALTAA T&T : ZYAAALT0

  13. AGENDA FIN & FIN Copy concept Closed User Group Service Profile & Message Matrix Message Flow Implementation Schedule Fallback Connectivity Supporting FIN Copy

  14. Closed User Group • Sub-group within SWIFT • Access only for authorised institutions and recognised message types • Controlled by Central Institution • Reduced cost membershipfor access to the paymentclearing only

  15. Bank B Bank A Central Institution FIN Copy Closed User Group SWIFT FIN Network Payment order Y- Copy 1 4 2 5 5 3 SWIFT Interface Settlement Application

  16. Bank A Bank B Settlement request 2 Central Institution 3 Settlement response Final Payment Instruction received 4 Sender / receiver notification and reporting 5 FIN Copy - Summary SWIFT FIN Network Payment order Y- Copy 1 4 1 Payment Instruction 2 5 5 3 SWIFT Interface Settlement Application

  17. AGENDA FIN & FIN Copy concept Closed User Group Service Profile & Message Matrix Message Flow Implementation Schedule Fallback Connectivity Supporting FIN Copy

  18. Service Profile • Service Identifier Code : • FIN Copy Mode : • Copy : • Authentication Mode : • CID – Live : • CID – T&T : • Currency check : • Sender Notification : • Message Types to copy : • Field & Tags to copy : AIP Y Partial Double STANALTA ZYAAALT0 ALL Individual use MT103, MT 102, MT 202,MT 205 20, 32A (or B),72

  19. Message matrix To Fin Copy Participants & PSPA Server Destinations From Fin Copy Participants & PSPA MTs 102, 103, 202, 205 MTs 900, 910, 941, 942, 950, 999 Server Destinations MTs 900, 910, 941, 942, 950, 999

  20. AGENDA FIN & FIN Copy concept Closed User Group Service Profile & Message Matrix Message Flow Implementation Schedule Fallback Connectivity Supporting FIN Copy

  21. Bank A MESSAGE FLOW: MT103 - as sent {1:F01SENDALTAXXX01234123456} {2:I103RECVALTAXXXXU} {3:{103:AIP}{108:MUR}} {4: :20: SREF :32A: 030905ALL100000,00 :50K: ORDERING CUSTOMER :59:/123456 BENEFICIARY CUSTOMER ADDRESS :71A:SHA -} {5:{MAC:12AB34CD} {PAC:34CD56EF} {CHK:123456789ABC}}

  22. Bank A MESSAGE FLOW: MT103 - as sent {1:F01SENDALTAXXX1234123456} {2:I103RECVALTAXXXXU} {3:{103:AIP}{108:MUR}} {4: :20: SREF :32A: 030905ALL100000,00 :50K: ORDERING CUSTOMER :59:/123456 BENEFICIARY CUSTOMER ADDRESS :71A:SHA -} {5:{MAC:12AB34CD} {PAC:34CD56EF} {CHK:123456789ABC}} Message User Reference copied to the CI within the MT 096 FIN COPY Service Identifier Code PAC Trailer based on BKE between Sender bank and CI

  23. copied from the MT 103 header of MT 103 copied from the MT 103 Text fields of MT 103 copied from the MT 103 User message reference trailer : inserted by FIN Copy containing information from MT 103 MESSAGE FLOW: MT096 {1:F01STANALTAXXX0246000987} {2:O0961200000920DYLPXXXXEXXX0019 1399900009201200S} {3:{103:AIP}{108:RECVALTA1200456}} {4: {1:F01SENDALTAXXXX01234123456} {2:I100NATHLKAXXXXU} {3:{103:AIP}{108:MUR}} {4: :20: SREF :32A: 030905ALL100000,00 -} {5: {MAC:12AB34CD} {PAC:34CD56EF} {CHK:123456789ABC}} {MRF:030319120000000920SENDALTAXXX 01234123456} } } {5:{CHK:987654321ABC}{SYS:1200000920 RECVALTAXXX01234123456}} Envelope

  24. copied from the MT 103 User message reference copied from the MT 096 Info from CI to Sender bank Accept/Reject Field 0=Accepted Info from CI to Receiver bank New PAC trailer : calculated between CI and Receiver bank MESSAGE FLOW: MT 097 - Authorised Msg {1:F01STANALTAXXX0246123456} {2:I097SWFTXXXXXXXXS} {4: {103:AIP} {109:030319120000000920BANKLLKLAXXX 01234123456} } } } {451:0} {114:AUTH REF 123456} {115:SETTLEMENT REF 123456} } {5: {PAC:A1B2C3F4} {CHK:246135789FED}}

  25. FIN Copy Service Identifier Code MUR - copied from the MT 096 Bank B PAC Trailer - copied from MT 097 MESSAGE FLOW: MT103 - as received {1:F01RECVALTAXXX124123456} {2:O1031200990809SENDALTAXXX01230004569908021205U} {3:{103:AIP}{108:MUR}} {115:Settlement ref 123456}} {4: 20: SREF :32A: 030905ALL100000,00 :50K: ORDERING CUSTOMER :59:/123456 BENEFICIARY CUSTOMER ADDRESS :71A:SHA -} {5:{MAC:12AB34CD} {PAC: A1B2C3F4} {CHK:123456789ABC}} Info from CI - copied from MT 097

  26. Accept/Reject Field 1=Rejected Abort reason code copied from MT 097 PAC : NEW PAC trailer calculated by the CI, based on BKE between CI and Receiver bank MESSAGE FLOW: MT 097 - Rejected Msg {1:F01RECVALTAXXX0246123456} {2:O1031200990809SENDALTAXXX01230004569908021205U} {4: {103:AIP} {109:030319120000000920SENDALTAXXX1234123456} {451:1} {432:66} } {5: {PAC:A1B2C3F4} {CHK:246135789FED}}

  27. Identification of original payment message Abort reason code copied from MT 097 MESSAGE FLOW: MT 019 - Abort Notification {1:F01SENDALTAXXX0247000888} {2:O019SWFTXXXXXXXXS} {4: {175:1200} {106:SENDALTAXXX1234123456} {102:RECVALTA} {432:66} } {5: {CHK:123456789ABC}{SYS:1205990802STANALTAXXX0246123456}

  28. AGENDA FIN & FIN Copy concept Closed User Group Service Profile & Message Matrix Message Flow Implementation Schedule Fallback Connectivity Supporting FIN Copy

  29. Implementation schedule Exchange of Live keys with CID : STANALTA (as of 15/12/2003) Upgrade your CBT for FIN Copy Perform testing with live destinations to ensure proper set-up Start FIN Copy testing Read the FIN Copy documentation Exchange of T&T keys with CID : ZYAAALT0 (as of now) Receive the information package Full RTGS in Live Mode (TBC) Return the completed forms to the Central Institution for approval : FIN Copy Undertakings (2) & Service Form (1)

  30. FIN Copy Forms for participants Standard procedures and forms for participants : • FIN Copy Undertaking (2*) Form • Service Form

  31. FIN Copy Undertaking

  32. Service Form Page 1

  33. Service FormPage 2

  34. Service FormPage 3

  35. Service FormPage 4

  36. Service FormPages 5 & 6

  37. Keeping the members informed From the Central Bank • Service Profile • Project plan • Emergency scenarios From SWIFT • FIN Copy Service Description Book • UHB • Interface Documentation

  38. Upgrade your CBT • SWIFT interface customers: swift.com download procedure • Non SWIFT interface customers: please contact your interface vendor. All interface vendors have received the service profile for this FIN Copy service.

  39. FIN Copy patch download procedure

  40. FIN Copy patch download procedure

  41. FIN Copy patch download procedure

  42. FIN Copy patch download procedure

  43. RTGS Implementation Plan - Summary • Read FINCopy Service description  • Return the Completed Forms (service & Undertaking forms) - 05/09/2003 • Upgrade your Interface (CBT)  • Exchange of T&T keys with CID: ZYAAALT0 - 20/09/2003 • Start FIN Copy testing  - 22/9/2003 • Exchange of Live keys with the CID: STANALTA  - 13/12/2003 • Perform testing with live BIC (as per Central Institution requirements) -15/12/2003 • Full RTGS in Live Mode TBC

  44. AGENDA FIN & FIN Copy concept Closed User Group Service Profile & Message Matrix Implementation Schedule Message Flow Registration Forms Fallback Connectivity Supporting FIN Copy

  45. Fallback Connectivity • Mandatory tests to improve the readiness of customers and protect the financial community • SWIFT customers must be able to send and receive messages every day without fail.

  46. Fallback Connectivity • Who ? 1. Market Infrastructures Customers 2. Top 100 (based on msg volume) 3. Top 101 to 500 4. All others • When ? Every 3 months (1 & 2) Every year (3 & 4)

  47. Fallback Connectivity • How ? • How ? • Minimum a successful Login to SWIFT network for each live BIC8 via a backup SWIFT access point

  48. Fallback Connectivity • What ? • Once the Service is in Live mode, SWIFT will contact the Central Institution • MT 999 to each individual BIC8 which is member of the Service, informing them of their obligation to do this test every 3 months starting at (date).

  49. Fallback Connectivity • What ? • Tracking customers who do not use multiple SAPs for accessing SWIFT as normal practice • Notifying customers who do not demonstrate fallback connectivity capability • Escalation to Operations Committee

  50. AGENDA FIN & FIN Copy concept Closed User Group Service Profile & Message Matrix Implementation Schedule Message Flow Registration Forms Fallback Connectivity Supporting FIN Copy