# 7.17 PATCH /transfers/{ID}

# Context

(HUB -> DFSP)

This message use by the HUB to inform a payee DFSP participant of the successful conclusion of a transfer. This message is only generated if the payee DFSP response with a Reserved status when providing the fulfillment in the PUT \transfers message.

Here is an example of the message:

{
"GrpHdr": {
    "MsgId":"01JBVM1CGC5A18XQVYYRF68FD1",
    "CreDtTm":"2024-11-04T12:57:45.228Z"},
"TxInfAndSts":{
    "PrcgDt":{"DtTm":"2024-11-04T12:57:45.213Z"},
    "TxSts":"COMM"}
}        

# Message Details

The details on how to compose and make this API are covered in the following sections:

1. Core Data Elements
   This section specifies which fields are required, which fields are optional, and which fields are unsupported in order to meet the message validating requirements.
2. Header Details
   This general section specifies the header requirements for the API are specified.
3. Supported HTTP Responses
   This general section specifies the http responses that must be supported.
4. Common Error Payload
   This general section specifies the common error payload that is provided in synchronous http error response.

# Core Data Elements

Here are the core data elements that are needed to meet this market practice requirement.

The background colours indicate the classification of the data element.

Here is the defined core data element table.