Receiving RMA authorisations

If the RM transfer service receives an RMA authorisation, it checks whether the received authorisation is a new authorisation, that is, whether the RMDS does not yet contain an authorisation of type toSnd with an own BIC, correspondent BIC, and SWIFT business service that are the same as those of the received authorisation.

• If the received authorisation is a new authorisation, the RM transfer service:
  1. Maps the received authorisation to a business OU
  2. Checks whether the DateTimeIssued and the digest of the received authorisation are valid. If one or both are invalid, the RM transfer service sends an RMA rejection to the correspondent as described in Sending RMA messages and terminates processing of the received authorisation.
  3. Stores the received authorisation in the RMDS
  4. Creates a history entry in the RMDS
• If the received authorisation is not a new authorisation and the DateTimeIssued of the received authorisation is larger than the DateTimeIssued of the existing authorisation in the RMDS, the RM transfer service:
  1. Checks whether the DateTimeIssued and the digest of the received authorisation are valid. If one or both are invalid, the RM transfer service:
     1. Sends an RMA rejection to the correspondent as described in Sending RMA messages
     2. Issues an event that informs about sending of this rejection
     3. Checks the status of the authorisation and, if the status is Enabled, sets the status to Deleted
     4. Terminates processing of the received authorisation
  2. Updates the RMDS with information from the received authorisation
  3. Creates a history entry in the RMDS
• Otherwise, the RM transfer service issues an event that indicates that an out-dated authorisation was received.