slide 1 fin copy seminar, albanian interbank payment system. tirana, albania: 05 september 2003...

Fin Copy Seminar, Albanian Interbank Payment System.

Tirana, Albania: 05 September 2003 FinCopy_CUG_v1.ppt

FIN Copy and Closed User Group

Ali Bakhtaoui

Customer Services

AGENDA

FIN & FIN Copy concept

Closed User Group

Service Profile & Message Matrix

Message Flow

Implementation Schedule

Fallback Connectivity

Supporting FIN Copy

AGENDA

FIN & FIN Copy concept Closed User Group


Message Flow



Supporting FIN Copy


FIN

User BUser A

FIN Copy

CentralInstitution

User A User B

What is FIN Copy?

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)

TY

Use of FIN Copy for RTGS Payment Order

SWIFT FINNetwork

Y- CopyBank A Bank B

CentralInstitution

Payment order(MT103, 102, 202, 205)

Use of FIN Copy for RTGS Settlement Request

Payment order

Bank A Bank B

CentralInstitution

SettlementRequest(MT096)

Y- Copy

SWIFT FINNetwork

FIN Copy for RTGS Authorisation

Payment order


CentralInstitution

SettlementRequest(MT 096)

Approved / SettledPayment order

Authorisation (MT 097)

SWIFT FIN Network

FIN Copy Rejection

Payment order

Bank A Bank B

CentralInstitution

SettlementRequest(MT 096)

Rejection(MT 097)

AbortNotification(MT 019)

Y- Copy

SWIFT FINNetwork

MT 096 FIN Copy to Central Institution Message

Basic HeaderApplication HeaderUser Header

Trailer Block

Envelope

Text Block“Basic HeaderApplication HeaderUser HeaderText (some or all fields)Trailer block”

Copy of original Message

MT 097 FIN Copy Message Authorisation/Refusal Notification

Basic HeaderApplication HeaderUser Header

Trailer Block

Envelope

Text Block“FIN Copy Service Identifier Code : AIPMRF Trailer from MT 096Acceptance/Rejection Code

Abort Reason

Information for senderInformation for receiver”

O

M

M (if codeword ‘Reject’, otherwise not present)

FIN Copy Authentication


CentralInstitution

PAC1: A to Central Institution Destination

MAC: A to B

SWIFT FINNetwork

Live :STANALTAA

T&T : ZYAAALT0

PAC2: Central Institution Destination to B

AGENDA


Closed User Group


Message Flow



Supporting FIN Copy

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 paymentclearing only

FIN Copy Closed User Group

SettlementApplication

SWIFTInterface

SWIFT FINNetwork

Paymentorder

Y- Copy

CentralInstitution

Bank B

1

2

4

53

Bank A

5

FIN Copy - Summary

SettlementApplication

SWIFTInterface

SWIFT FINNetwork

Paymentorder

Y- Copy

CentralInstitution

Bank B

1

2

4

5

1 Payment Instruction

3 Settlement response

4Final Payment Instruction received

5Sender / receiver notification and reporting

2Settlement request 3

Bank A

5

AGENDA


Closed User Group


Message Flow



Supporting FIN Copy

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

Message matrix

Fin CopyParticipants

& PSPA

Fin CopyParticipants

& PSPA

ServerDestinations

ServerDestinations

MTs 900, 910,941, 942, 950, 999

MTs 900, 910,941, 942, 950, 999

MTs 102, 103,202, 205

From

To

AGENDA


Closed User Group


Message Flow Implementation Schedule


Supporting FIN Copy

MESSAGE FLOW: MT103 - as sent

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

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:/123456BENEFICIARY CUSTOMERADDRESS:71A:SHA-}{5:{MAC:12AB34CD}{PAC:34CD56EF}{CHK:123456789ABC}}

Bank A

FIN COPY Service Identifier

Code

Message User Reference

copied to the CI within the MT

096

PAC Trailerbased on BKE between

Sender bank and CI

MESSAGE FLOW: MT096{1:F01STANALTAXXX0246000987}{2:O0961200000920DYLPXXXXEXXX00191399900009201200S}{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:030319120000000920SENDALTAXXX01234123456} } }

{5:{CHK:987654321ABC}{SYS:1200000920RECVALTAXXX01234123456}}

Envelope

copied from the MT 103

header of MT 103


Text fields of MT 103


User message reference trailer : inserted by FIN

Copy containing information from MT 103

MESSAGE FLOW: MT 097 - Authorised Msg

{1:F01STANALTAXXX0246123456}{2:I097SWFTXXXXXXXXS}{4:{103:AIP}{109:030319120000000920BANKLLKLAXXX01234123456} } }}{451:0}{114:AUTH REF 123456}{115:SETTLEMENT REF 123456}}{5:{PAC:A1B2C3F4}{CHK:246135789FED}}


User messagereference

copied fromthe MT 096

Accept/Reject Field 0=Accepted

Info from CI to Sender bank

Info from CI to Receiver bank

New PAC trailer : calculated between CI and Receiver bank

MESSAGE FLOW: MT103 - as received{1:F01RECVALTAXXX124123456}{2:O1031200990809SENDALTAXXX012300

04569908021205U}{3:{103:AIP}{108:MUR}}{115:Settlement ref 123456}}{4:20: SREF:32A: 030905ALL100000,00:50K: ORDERING CUSTOMER:59:/123456BENEFICIARY CUSTOMERADDRESS:71A:SHA-}{5:{MAC:12AB34CD}{PAC: A1B2C3F4}{CHK:123456789ABC}}

Bank B

FIN Copy Service

Identifier Code

MUR - copied from the MT 096

Info from CI - copied

from MT 097

PAC Trailer - copied from

MT 097

MESSAGE FLOW: MT 097 - Rejected Msg

{1:F01RECVALTAXXX0246123456}{2:O1031200990809SENDALTAXXX01230004569908021205U}{4:{103:AIP}{109:030319120000000920SENDALTAXXX1234123456} {451:1}{432:66}}{5:{PAC:A1B2C3F4}{CHK:246135789FED}}

Accept/Reject Field 1=Rejected

Abort reason codecopied from MT

097

PAC : NEW PAC trailercalculated by the CI, based on BKE between CI and Receiver bank

MESSAGE FLOW: MT 019 - Abort Notification

{1:F01SENDALTAXXX0247000888}{2:O019SWFTXXXXXXXXS}{4:

{175:1200}{106:SENDALTAXXX1234123456} {102:RECVALTA}{432:66}}{5:{CHK:123456789ABC}{SYS:1205990802STANALTAXXX0246123456}

Identification of original payment

message

Abort reason codecopied from MT

097

AGENDA


Closed User Group


Message Flow



Supporting FIN Copy

Implementation schedule

Receive the information

package

Read the FIN Copy

documentation

Upgrade your CBT for FIN

Copy

Return the completed forms to the Central

Institution for approval : FIN Copy Undertakings (2)

& Service Form (1)

Exchange of T&T keys with CID :

ZYAAALT0(as of now)

Start FIN Copy testing

Exchange of Live keys with CID :

STANALTA(as of

15/12/2003)Perform testing with live

destinations to ensure proper

set-up

Full RTGS in

Live Mode(TBC)

FIN Copy Forms for participants

Standard procedures and forms for participants :

– FIN Copy Undertaking (2*) Form

– Service Form

FIN Copy Undertaking

Service Form Page 1

Service FormPage 2

Service FormPage 3

Service FormPage 4

Service FormPages 5 & 6

Keeping the members informed

From the Central Bank

Service Profile Project plan Emergency

scenarios

From SWIFT

FIN Copy Service Description Book

UHB Interface

Documentation

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.

FIN Copy patch download procedure

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

AGENDA


Closed User Group



Message Flow

Registration Forms


Supporting FIN Copy


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.


1. Market Infrastructures Customers

2. Top 100 (based on msg volume)

3. Top 101 to 500

4. All others

Every 3 months (1 & 2)

Every year (3 & 4)

Who ?

When ?


How ? How ?

Minimum a successful Login to SWIFT network for each live BIC8 via a backup SWIFT access point


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).


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

AGENDA


Closed User Group



Message Flow

Registration Forms


Supporting FIN Copy

Online support

Supporting FIN Copy

Customer Services Centre

Tel : +31 71 582 2822

Fax : +31 71 581 2637

SWIFT BIC : SWHQNLNL

e-mail : [email protected]

SWIFT Contacts

Customer Services Centre NL

Bank of Albania

- Service Administrator

Regional Account Manager -Alke De Boer

slide 1 fin copy seminar, albanian interbank payment system. tirana, albania: 05 september 2003...

Documents

fin copy slide

use of fin copy

fin copy seminar

swift fin network slide

present slide

central institution

b swift fin network

closed user group subgroup