CDE Payment Provider Authorisation

Payment Provider Environment Only: Paying Payment Providers must not submit a rejection Funds Obligation Status Advice (sett_135) message in response to a Funds Obligation (sett_133) message with an Authorisation Reason of Funds Authorisation (PFAU) that is received during Batch Settlement. Providing a rejection response in this scenario will cause Batch Settlement to not complete and the only remediation will be an environment reset.

The below workflows apply to a Paying Payment Provider where the CSP sends a Funds Obligation (sett_133) as a part of Batch Settlement or Bilateral Demand Settlement. For a detailed breakdown of available functionality, refer to the Batch Settlement Aggregate Funds Obligation, Batch Settlement Funds Movement and Bilateral Demand Settlement Functional Specifications.

Non-Payment Provider Environments

For CDE, Participants are encouraged to submit any BDSI Settlement Instruction Request (sett_105) messages prior to 6:15pm in order to ensure completion of a scenario within the same business day.

Payment Provider Environment

For CDE, Payment Providers are encouraged to submit any Payment Provider Funds Obligation Status Advice (sett_135) messages prior to 6:15pm in order to ensure completion of a scenario within the same business day.

Refer to CDE Reserve Bank Information & Transfer System (RITS) for further details.

Non-Payment Provider Environments

In non-Payment Provider environments, the Auto-responder will act in the role of a Paying Payment Provider.

The rules governing the Auto-responder behaviour are detailed in the diagrams below:

Non-Payment Provider Environments: Batch Settlement

Non-Payment Provider Environments: Bilateral Demand Settlement

Non-Payment Provider Environments: Batch Settlement Bank Funds Transfer

Payment Provider Environments

In Payment Provider environments, the Auto-responder will act in the role of a Paying Payment Provider, however Payment Providers may still perform testing of the relevant workflow. The Auto-responder in Payment Provider environments will not immediately generate an Acceptance response for Funds Obligation (sett_133) messages that have an Authorisation Reason of Funds Authorisation (PFAU). Instead, it will generate a delayed acceptance response after 30 minutes from the receipt of a Funds Obligation (sett_133) with an Authorisation Reason of Funds Authorisation (PFAU). This will allow Batch Settlement to complete in the scenario where the Payment Provider has not accepted the Funds Obligation as part of their required business workflow.

Where the Paying Payment Provider wants to accept a Funds Obligation (sett_133) with an Authorisation Reason of Funds Authorisation (PFAU), then they must accept within 30 minutes from the receipt of the Funds Obligation (sett_133) message.

No responses will be automatically generated for other Funds Obligation (sett_133) Authorisation Reason values.

Where a Payment Provider submits a Funds Obligation Status Advice (sett_135) to the CSP prior to the Auto-responder Acceptance response in a Payment Provider environment, the Auto-responder Acceptance response will be rejected by the CSP and the Payment Provider will receive a Rejected Transaction (comm_808) message. The Payment Provider should ignore this message if it doesn’t relate to a Funds Obligation Status Advice (sett_135) they submitted.

The rules governing the Auto-responder behaviour are detailed in the diagrams below:

Payment Provider Environments: Batch Settlement and Bilateral Demand Settlement



Payment Provider Environments: Batch Settlement Bank Funds Transfer