FIN Copy and Closed User Group

advertisement
FIN Copy and
Closed User Group
Ali Bakhtaoui
Customer Services
Fin Copy Seminar, Albanian Interbank Payment System.
FinCopy_CUG_v1.ppt
Tirana, Albania: 05 September 2003
Slide 1
AGENDA
FIN & FIN Copy concept
Closed User Group
Service Profile & Message Matrix
Message Flow
Implementation Schedule
Fallback Connectivity
Supporting FIN Copy
Slide 2
AGENDA
FIN & FIN Copy concept
Closed User Group
Service Profile & Message Matrix
Message Flow
Implementation Schedule
Fallback Connectivity
Supporting FIN Copy
Slide 3
FIN & FIN Copy concept
FIN Copy
FIN
User A
User B
User A
User B
Central
Institution
Slide 4
What is FIN Copy?
 Value
added message copying
to 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)
Slide 5
Use of FIN Copy for RTGS Payment Order
SWIFT FIN
Network
Payment order
(MT103, 102, 202,
205)
Bank A
Y
- Copy
Bank B
Central
Institution
Slide 6
Use of FIN Copy for RTGS Settlement
Request
SWIFT FIN
Network
Payment order
Y
Bank A
- Copy
Bank B
Settlement
Request
(MT096)
Central
Institution
Slide 7
FIN Copy for RTGS Authorisation
SWIFT FIN
Network
Payment order
Bank A
Y
Approved / Settled
Payment order
- Copy
Settlement
Request
(MT 096)
Bank B
Authorisation (MT 097)
Central
Institution
Slide 8
FIN Copy Rejection
SWIFT FIN
Network
Payment order
Bank A
Y
Abort
Notification
(MT 019)
Settlement
Request
(MT 096)
- Copy
Bank B
Rejection
(MT 097)
Central
Institution
Slide 9
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
Trailer Block
Copy of
original Message
Slide 10
MT 097 FIN Copy Message
Authorisation/Refusal Notification
Basic Header
Application Header
User Header
Envelope
Text Block
“FIN Copy Service Identifier Code : AIP
MRF Trailer from MT 096
Acceptance/Rejection Code
Abort Reason
M (if codeword ‘Reject’,
otherwise not present)
Information for sender
Information for receiver”
Trailer Block
M
O
Slide 11
FIN Copy Authentication
MAC: A to B
Bank A
PAC1:
A to Central Institution Destination
SWIFT FIN
Network
Y
- Copy
Bank B
PAC2:
Central Institution Destination to B
Central
Institution
Live :STANALTAA
T&T : ZYAAALT0
Slide 12
AGENDA
FIN & FIN Copy concept
Closed User Group
Service Profile & Message Matrix
Message Flow
Implementation Schedule
Fallback Connectivity
Supporting FIN Copy
Slide 13
Closed User Group
 Sub-group
within SWIFT
 Access
only for authorised institutions and
recognised message types
 Controlled
by Central Institution
 Reduced
cost membership
for access to the payment
clearing only
Slide 14
FIN Copy Closed User Group
SWIFT FIN
Network
Payment
order
Y
1
Bank A
4
- Copy
Bank B
2
5
3
5
SWIFT
Interface
Central
Institution
Settlement
Application
Slide 15
FIN Copy - Summary
SWIFT FIN
Network
Payment
order
Y
1
1
Payment
Instruction
2
Settlement
request
3
Settlement response
4
Final Payment
Instruction received
5
Sender / receiver
notification and
reporting
Bank A
4
- Copy
Bank B
2
5
3
5
SWIFT
Interface
Central
Institution
Settlement
Application
Slide 16
AGENDA
FIN & FIN Copy concept
Closed User Group
Service Profile & Message Matrix
Message Flow
Implementation Schedule
Fallback Connectivity
Supporting FIN Copy
Slide 17
Service Profile

Service Identifier Code :
AIP

FIN Copy Mode :
Y

Copy :
Partial

Authentication Mode :
Double

CID – Live :
STANALTA

CID – T&T :
ZYAAALT0

Currency check :
ALL

Sender Notification :
Individual use

Message Types to copy :
MT103, MT 102, MT 202,MT 205

Field & Tags to copy :
20, 32A (or B),72
Slide 18
Message matrix
To
From
Fin Copy
Participants
& PSPA
Server
Destinations
Fin Copy
Participants
& PSPA
MTs 102, 103,
202, 205
Server
Destinations
MTs 900, 910,
941, 942, 950, 999
MTs 900, 910,
941, 942, 950, 999
Slide 19
AGENDA
FIN & FIN Copy concept
Closed User Group
Service Profile & Message Matrix
Message Flow
Implementation Schedule
Fallback Connectivity
Supporting FIN Copy
Slide 20
MESSAGE FLOW: MT103 - as sent
Bank A
{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}}
Slide 21
MESSAGE FLOW: MT103 - as sent
Bank A
FIN COPY
Service
Identifier
Code
{1:F01SENDALTAXXX1234123456}
{2:I103RECVALTAXXXXU}
{3:{103:AIP}{108:MUR}}
{4:
Message User
:20: SREF
Reference
:32A: 030905ALL100000,00
:50K: ORDERING CUSTOMER copied to the CI
within the MT
:59:/123456
096
BENEFICIARY CUSTOMER
ADDRESS
:71A:SHA
-}
{5:{MAC:12AB34CD}
{PAC:34CD56EF}
PAC Trailer
{CHK:123456789ABC}}
based on BKE between
Sender bank and CI
Slide 22
MESSAGE FLOW: MT096
copied from {1:F01STANALTAXXX0246000987}
the MT 103 {2:O0961200000920DYLPXXXXEXXX0019
1399900009201200S}
{3:{103:AIP}{108:RECVALTA1200456}}
{4:
header of
{1:F01SENDALTAXXXX01234123456}
MT 103
{2:I100NATHLKAXXXXU}
{3:{103:AIP}{108:MUR}}
copied from
{4:
the MT 103
Text fields :20: SREF
of MT 103 :32A: 030905ALL100000,00
-}
{5:
{MAC:12AB34CD}
copied from
{PAC:34CD56EF}
the MT 103
{CHK:123456789ABC}}
{MRF:030319120000000920SENDALTAXXX
01234123456} } }
{5:{CHK:987654321ABC}{SYS:1200000920
RECVALTAXXX01234123456}}
Envelope
User message reference
trailer : inserted by FIN
Copy containing information
from MT 103
Slide 23
MESSAGE FLOW: MT 097 - Authorised Msg
copied
from the
MT 103
User message
reference
copied from
the MT 096
Accept/Reject
Field
0=Accepted
{1:F01STANALTAXXX0246123456}
{2:I097SWFTXXXXXXXXS}
{4:
{103:AIP}
{109:030319120000000920BANKLLKLAXXX
01234123456} } }
}
Info from CI to
{451:0}
Sender bank
{114:AUTH REF 123456}
{115:SETTLEMENT REF 123456}
Info from CI to
Receiver bank
}
{5:
{PAC:A1B2C3F4}
{CHK:246135789FED}} New PAC trailer : calculated
between CI and Receiver bank
Slide 24
MESSAGE FLOW: MT103 - as received
FIN Copy
Service
Identifier
Code
Info from
CI - copied
from MT
097
{1:F01RECVALTAXXX124123456}
{2:O1031200990809SENDALTAXXX012
30004569908021205U}
{3:{103:AIP}{108:MUR}}
MUR {115:Settlement ref 123456}}
copied from
{4:
the MT 096
20: SREF
:32A: 030905ALL100000,00
:50K: ORDERING CUSTOMER
:59:/123456
BENEFICIARY CUSTOMER
ADDRESS
:71A:SHA
-}
{5:{MAC:12AB34CD}
PAC Trailer copied from
{PAC: A1B2C3F4}
MT 097
{CHK:123456789ABC}}
Bank B
Slide 25
MESSAGE FLOW: MT 097 - Rejected Msg
Accept/Reject
Field
1=Rejected
Abort reason code
copied from MT
097
{1:F01RECVALTAXXX0246123456}
{2:O1031200990809SENDALTAXXX012300045699080
21205U}
{4:
{103:AIP}
{109:030319120000000920SENDALTAXXX1234123456
}
{451:1}
{432:66}
}
{5:
{PAC:A1B2C3F4}
PAC : NEW PAC trailer
{CHK:246135789FED}} calculated by the CI, based on BKE
between CI and Receiver bank
Slide 26
MESSAGE FLOW: MT 019 - Abort Notification
Identification of
original payment
message
Abort reason code
copied from MT
097
{1:F01SENDALTAXXX0247000888}
{2:O019SWFTXXXXXXXXS}
{4:
{175:1200}
{106:SENDALTAXXX1234123456}
{102:RECVALTA}
{432:66}
}
{5:
{CHK:123456789ABC}{SYS:1205990802STANALTAXX
X0246123456}
Slide 27
AGENDA
FIN & FIN Copy concept
Closed User Group
Service Profile & Message Matrix
Message Flow
Implementation Schedule
Fallback Connectivity
Supporting FIN Copy
Slide 28
Implementation schedule
Exchange of Live
keys with CID :
Upgrade your
STANALTA
CBT for FIN
(as of
Copy
15/12/2003)
Perform testing
Start FIN
with live
Copy testing
destinations to
Read the
ensure proper
Exchange of T&T
FIN Copy
set-up
keys with CID :
documentation
ZYAAALT0
(as of now)
Receive the
Full
information
Return the completed
RTGS in
package
forms to the Central
Live
Institution for approval :
Mode
FIN Copy Undertakings (2)
(TBC)
& Service Form (1)
Slide 29
FIN Copy Forms for participants
Standard procedures and forms for participants :
– FIN Copy Undertaking (2*) Form
– Service Form
Slide 30
FIN Copy
Undertaking
Slide 31
Service Form
Page 1
Slide 32
Service Form
Page 2
Slide 33
Service Form
Page 3
Slide 34
Service Form
Page 4
Slide 35
Service Form
Pages 5 & 6
Slide 36
Keeping the members informed
From the Central Bank
From SWIFT
 Service
Profile
 FIN
 Project
plan
 Emergency
scenarios
Copy Service
Description Book
 UHB
 Interface
Documentation
Slide 37
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.
Slide 38
FIN Copy patch download procedure
Slide 39
FIN Copy patch download procedure
Slide 40
FIN Copy patch download procedure
Slide 41
FIN Copy patch download procedure
Slide 42
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 

Perform testing with live BIC (as per Central Institution requirements)
15/12/2003

Full RTGS in Live Mode TBC
- 13/12/2003
-
Slide 43
AGENDA
FIN & FIN Copy concept
Closed User Group
Service Profile & Message Matrix
Implementation Schedule
Message Flow
Registration Forms
Fallback Connectivity
Supporting FIN Copy
Slide 44
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.
Slide 45
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)
Slide 46
Fallback Connectivity

How ?
 Minimum
a successful Login to SWIFT
network for each live BIC8 via a backup
SWIFT access point
Slide 47
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).
Slide 48
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
Slide 49
AGENDA
FIN & FIN Copy concept
Closed User Group
Service Profile & Message Matrix
Implementation Schedule
Message Flow
Registration Forms
Fallback Connectivity
Supporting FIN Copy
Slide 50
Online support
Slide 51
Supporting FIN Copy
Customer Services Centre
Tel : +31 71 582 2822
Fax : +31 71 581 2637
SWIFT BIC : SWHQNLNL
e-mail : support.europe@swift.com
Slide 52
SWIFT Contacts

Customer Services Centre NL

Bank of Albania
- Service Administrator

Regional Account Manager
-Alke De Boer
Slide 53
Download