CDE mFund Application and Redemption

The below workflow will apply where the Auto-responder acts on behalf of a Product Issuer Settlement Participant (PISP) in response to the where:

  • the CSP generated an mFund Application Order Request (mfnd_401) message with the Order State of "Pending" to a PISP; or

  • the CSP generated an mFund Redemption Order Request (mfnd_407) message with the Order State of "Pending" to a PISP.

For a detailed breakdown of available functionality, refer to the mFund Application Process and mFund Redemption Process Functional Specifications.

mFund Application

Where a Participant initiates a mFund Application Order Request (mfnd_401) the Auto-responder will act as the PISP. The rules governing the Auto-responder behaviour are detailed in the diagram below: 

On an acceptance, as per mFund Application - Acceptance and Settlement, the PISP is required to send an mFund Order Confirmation (mfnd_406) to the CSP as per mFund Application - Unit Allotment. The mFund Application - Unit Allotment will require the participant to use the rest end point acting as the related PISP, by sending an mfnd_406 using the command /xmlIngest/submitXML.

mFund Redemption

Where a Participant initiates a mFund Redemption Order Request (mfnd_407) the Auto-responder will act as the PISP. The rules governing the Auto-responder behaviour are detailed in the diagram below: