Application header options for an InterAct application header

For an InterAct application header, a request, response, or notification can specify the following options:

From

• rep. 0…1
• A folder that identifies the sending application. It can contain following elements:
  • Type (field)
  • Id (field)

To

• rep. 0…1
• A folder that identifies the application that must receive the message. It can contain following elements:
  • Type (field)
  • Id (field)

Type

• string, 0…4 characters, rep. 0…1
• The type of business entity that the Id element identifies, for example:

  DN

  Distinguished name

  BIC

  Bank Identifier Code

  NAME

  Name of a business entity

Id

• string, 0…30 characters, rep. 0…1
• A name that identifies the business entity.

SvcName

• string, 0…30 characters, rep. 0…1
• Identifies the SWIFTNet service to which the business message belongs.

MsgName

• string, 1…30 characters, rep. 0…1
• A name that uniquely identifies the business message.

MsgRef

• string, 0…30 characters, rep. 1
• An ID specified by an application and used to uniquely identify a business message. Sending and receiving applications can use this value to correlate messages.

CrDate

• dateTime, rep. 0…1
• Date and time (UTC) when the message was created. If this element is not specified, the MSIF transfer service uses the date and time when the message is sent to the SAG.

Dup

• rep. 0…1
• A folder that specifies elements used to process duplicate emissions. It can contain the following elements:
  • Ref (field)
  • Info (field)

Ref

• string, 0…30 characters, rep. 0…1
• The original MsgRef of a message that is being resent. The receiving application can compare this value with the MsgRefs of earlier messages to determine whether the resent message is a duplicate, that is, whether it has already been successfully received.

Info

• string, 0…140 characters, rep. 0…1
• Additional information relating to a duplicate message. This element can be specified only if the Ref element is also specified.