Relationship Management Application (RMA)

The Relationship Management Application (RMA) is a Swift service that is designed to enable clients to control the messages that they would like to exchange with each other. The RMA enables clients to record and enforce pre-agreed relationships between participating clients using a FIN, FINplus or other SwiftNet services. Clients can create, store, view, manage, and enforce pre-agreed relationships with their correspondents. Service administrators can choose to use RMA to allow their service participants to have control of the messaging traffic received or sent within their services. Swift, or as the case may be, the service administrator, decides whether the RMA is used or supported.

The RMA has two main functions:

• Authorisation: Clients exchange or create authorisations, indicating "who can send traffic to whom".
• Filtering: The clients' messaging interfaces apply these rules to control which traffic they can exchange with which correspondent.

Clearstream BICs

SwiftNet services

Authorisation

An authorisation is an entity that authorises one BIC to send messages to or receive messages from a correspondent BIC for a particular service. Each authorisation is unidirectional and can be specified to apply only to certain message types or categories.

There are two types of authorisation:

Authorisation to send (toSnd)

This is an authorisation sent by a correspondent to the client that authorises the client’s BIC to send messages to the correspondent’s BIC for a particular service. An authorisation to send only becomes active if the client accepts it, at which point its status is set to “Enabled”. If the client rejects an authorisation to send, the RMA sets its status to “Rejected” and notifies the correspondent. If the client deletes an authorisation to send that they had accepted previously, the RMA sets its status to “Deleted” and notifies the correspondent.

A correspondent can revoke an authorisation to send. When the RMA Transfer Service receives an RMA message indicating that an authorisation to send has been revoked, the RMA sets the status of the authorisation to ”Revoked”.

Authorisation to receive (toRcv)

This is an authorisation, created by the client, that authorises the client’s BIC to receive messages from the correspondent BIC for a particular service. When the client creates an authorisation to receive, the RMA sends a corresponding authorisation to send to the correspondent. That authorisation to send authorises the correspondent to send messages to the client’s BIC. The authorisation to receive remains in the “Enabled” status as long as the correspondent either does not react to, or accepts, the corresponding authorisation to send. If the correspondent does not wish to send messages to the client’s BIC for the specified service, the correspondent rejects or deletes the authorisation to send, and the RMA automatically changes the status of the corresponding authorisation to receive to “Rejected”.

When the client revokes an authorisation to receive, the RMA sets its status to “Revoked” and notifies the correspondent.