Payment Provider Authorisation for RTGS Payments Process

Table of Contents

Payment Provider Authorisation for RTGS Payments Process Flow

Payment Provider Authorisation for RTGS Payments Process

StepDescriptionPartyRecipientMessage Reference
1

The Payment Provider Authorisation for RTGS Payment Process is invoked from the Bilateral Demand Settlement Instruction Process.

2The CSP matches the transaction. Then, refer to Step 3 and 5; "Payments Provider Funds Obligation".CSP--
Payment Provider Funds Obligation
3

The CSP generates and sends a Funds Obligation to the Receiving Payment Provider, indicating that a Funds Obligation is to be received for a specified bank account.

CSPReceiving Payment ProviderFunds Obligation (sett_133)
4The Receiving Payment Provider optionally sends a Funds Obligation Status Advice with an acceptance to the CSP however no further action will occur in the Payment Provider Authorisation for RTGS Payments Process Flow.Receiving Payment ProviderCSPFunds Obligation Status Advice (sett_135)
5The CSP generates and sends a Funds Obligation to the Paying Payment Provider, indicating that a Funds Obligation is to be paid for a specified bank account.CSPPaying Payment ProviderFunds Obligation (sett_133)
6

The Paying Payment Provider determines whether to accept or reject the Funds Obligation.

If the Paying Payment Provider accepts or rejects the Funds Obligation; refer to Step 7; "Acceptance/Rejection".

If the Paying Payment Provider takes no action by the end of the Payment Date, refer to Step 22; "No Response".

Paying Payment Provider--
Acceptance/Rejection
7

The Paying Payment Provider populates the Funds Obligation Status Advice with the following:

  1. Mandatory ISO 20022 elements defined in the Message Usage Guidelines;
  2. Optional ISO 20022 elements defined in the Message Usage Guidelines where applicable to the request; and
  3. Related ASX business values and rules applicable to the request.

The Paying Payment Provider sends a Funds Obligation Status Advice to the CSP, advising that a payment request has been accepted or rejected.

Paying Payment ProviderCSPFunds Obligation Status Advice (sett_135)
8

The CSP validates the Funds Obligation Status Advice against the schema and business validation rules.

If the Funds Obligation Status Advice is schema and business valid, then refer to Step 9; "Acceptance/Rejection".

If the Funds Obligation Status Advice is not schema or business valid, then refer to Step 24; "On Fail".

CSP--
9

The CSP determines whether the Paying Payment Provider accepted or rejected the Funds Obligation.

If the Paying Payment Provider accepted the Funds Obligation, refer to Step 10; "Accepted Payment Provider Funds Obligation".

If the Paying Payment Provider rejected the Funds Obligation, refer to Step 21; "Rejected Payment Provider Funds Obligation".

CSP--
Accepted Payment Provider Funds Obligation
10The CSP generates and sends a RITS payment request to the Reserve Bank Information and Transfer System (RITS).CSPRITS (Payment Service)-
11

RITS processes the RITS payment request onto the RITS System Queue.

RITS (Payment Service)--
12The Paying Payment Provider updates the Credit Status of the RITS Payment Request in RITS.Paying Payment ProviderRITS (Payment Service)-
13RITS informs the CSP of the status of the RITS payment request.RITS (Payment Service)CSP
14

The CSP processes the RITS response.

If RITS successfully processed the RITS payment request, refer to Step 15; "Successful RITS Processing".

If RITS unsuccessfully processed the RITS payment request, refer to Step 18; "Unsuccessful RITS Processing".

CSP--
Successful RITS Processing
15The CSP processes the completed RITS payment request.CSP--
16The CSP sends a Funds Movement notification to the Receiving Payment Provider, advising them that the RITS payment request has been successfully processed.CSPReceiving Payment ProviderFunds Movement (sett_137)
17The CSP sends a Funds Movement notification to the Paying Payment Provider, advising them that the RITS payment request has been successfully processed. Then, refer to Step 23; "Refer to Initiating Process".CSPPaying Payment ProviderFunds Movement (sett_137)
Unsuccessful RITS Processing
18The CSP processes the rejected RITS payment request.CSP--
19The CSP sends a Transaction Acknowledgement Advice to the Receiving Payment Provider, advising that the RITS payment request has not been processed.CSPReceiving Payment ProviderTransaction Acknowledgement Advice (comm_809)
20The CSP sends a Transaction Acknowledgement Advice to the Paying Payment Provider, advising that the RITS payment request has not been processed. Then, refer to Step 23; "Refer to Initiating Process".CSPPaying Payment ProviderTransaction Acknowledgement Advice (comm_809)
Rejected Payment Provider Funds Obligation
21

The CSP processes the Funds Obligation Status Advice (Rejected). Then, refer to Step 23; "Refer to Initiating Process".

CSP--
No Response
22The End of Day process is triggered to perform ASX Housekeeping of unprocessed Funds Obligations for a Paying Payment Provider. Then, refer to Steps 19 and 20; "Unsuccessful RITS Processing".CSP--
Refer to Initiating Process
23

Refer to the Bilateral Demand Settlement Instruction Process.

On Fail
24

If the Funds Obligation Status Advice fails schema or business validation, the CSP will send the Paying Payment Provider:

  • An invalid Transaction Notification with the relevant error code for schema failure; or
  • A rejected Transaction for business validation failure.
CSPPaying Payment Provider

Invalid Transaction Notification (comm_807)

Rejected Transaction (comm_808)


Business Values and Rules Table
Funds Obligation

The CSP sends a Funds Obligation to the receiving and paying Payment Providers, advising that a Funds Obligation is to be received/paid for a specified bank account.

ASX Element Name
ISO 20022 Element
Guidelines
Report Header
Settlement DateSettlement Date / DateThe current date when the Funds Obligation was requested
Settlement Account Net Position
Transaction IdNet Position Identification

The unique identifier of a transaction within the CSP. Further details of Transaction Identifications are detailed here.

Obligation IdMarket Infrastructure Transaction Identification

Indicates the Obligation Id for the "matched" Bilateral Demand Settlement Instruction.

Cash AccountCash Account / Identification / Other / Identification

Indicates the Bank Account Number recorded on the Payment Facility with an associated sub-type of Bilateral Demand Payer (BDSP) or Bilateral Demand Payee (BDSR).

AmountAmount / Amount

Indicates the Settlement Amount for the Bilateral Demand Settlement Instruction.

The element has a Currency attribute associated with it. Example: <Amt Ccy="AUD">225.25</Amt>

Credit Debit IndicatorAmount / Credit Debit Indicator

Indicates whether the Payment Provider is the Payer or Payee of the Funds Obligation, either:

  • Credit (CRDT), where the Payment Provider is the Payee; or
  • Debit (DBIT), where the Payment Provider is the Payer.
Identifier of Payment ManagerCash Account Owner / Identification / Organisation Identification / Other / Identification

Indicates the identifier of the Manager of the Payment Facility.

Name of Payment ManagerCash Account Owner / NameIndicates the name of the Manager of the Payment Facility.
Authorisation ReasonAuthorisation Reason

Indicates the type of authorisation being notified, either:

  • Real Time Payment Notification (RPNO); or
  • Real Time Payment Authorisation (RPAU).

Funds Obligation Status Advice

The Paying Payment Provider sends a Funds Obligation Status Advice to either Accept or Reject their Funds Obligation. The Receiving Payment Provider may optionally send a Funds Obligation Status Advice to Accept their Funds Obligation.

ASX Element Name
ISO 20022 Element
Guidelines
Origin Message IdStatus Header / Original Business Request / Message IdentificationIdentifies the Message Id of the Funds Obligation.
Cash AccountNet Position Status / Cash Account / Identification / Other / IdentificationIdentifies the Bank Account provided on the Funds Obligation that is being accepted or rejected.
Target Transaction IdNet Position Status / Net Position IdentificationIdentifies the Transaction Id of the Funds Obligation that is being accepted or rejected.
StatusNet Position Status / Status

Identifies whether the Payment Provider accepts or rejects the Fund Obligation; either: 

  • Acknowledge Accepted (PACK), when accepting the Fund Obligation; or
  • Rejected (REJT), when rejecting the Fund Obligation.
Bank ReferenceNet Position Status / Account Servicer ReferenceAllows the Payment Provider to include a reference on their acceptance or rejection. No business validations performed on this field

Funds Movement

The CSP sends a Funds Movement notification to the paying and receiving Payment Providers, advising them that the RITS payment request has been successfully processed.

ASX Element Name
ISO 20022 Element
Guidelines
Transaction IdNotification / Identification

Indicates the Transaction Id provided on the Funds Obligation.

AccountNotification / Account / Identification / Other / IdentificationIndicates the Cash Account provided on the Funds Obligation.
AmountNotification / Entry / AmountIndicates the Amount transacted by RITS.
Credit / Debit IndicatorNotification / Entry / Credit Debit Indicator

Indicates whether the funds were received or paid, either:

  • Credit (CRDT), where the funds were received; or
  • Debit (DBIT), where the funds were paid.
Value DateNotification / Entry / Value DateIndicates the date that funds were transferred in RITS.
Payment ReferenceNotification / Entry / Account Servicer ReferenceIndicates the Payment Reference provided by the requester of the payment. 
Bank Transaction CodeNotification / Entry / Bank Transaction Code / Proprietary / Code

Indicates a settlement of funds, in this case Real Time Funds Movement (RTFM) will be present.

Counterparty IdentifierNotification / Additional Notification InformationThe UIC of the participant which is the counterparty to the transaction.

Transaction Acknowledgement Advice

The CSP sends a Transaction Acknowledgement Advice to the Paying and Receiving Payment Providers, advising that the Funds Obligation was not authorised and housekept or the RITS payment request has not been processed.

ASX Element Name
ISO 20022 Element
Guidelines
Transaction IdRelated Reference / ReferenceIndicates the Transaction Id provided on the Funds ObligationFurther details of Transaction Identifications are detailed here.
Status CodeStatus Code

Indicates either:

  • Cancelled by System (CANS), where the unauthorised Funds Obligation was housekept; or
  • Rejected (REJT), where RITS unsuccessfully processed the RITS payment request.




Related Pages:

There are no related labels.

Browse Popular Pages:

No labels match these criteria.



This document provides general information only. ASX Limited (ABN 98 008 624 691) and its related bodies corporate (“ASX”) makes no representation or warranty with respect to the accuracy, reliability or completeness of the information. To the extent permitted by law, ASX and its employees, officers and contractors shall not be liable for any loss or damage arising in any way (including by way of negligence) from or in connection with any information provided or omitted or from anyone acting or refraining to act in reliance on this information.

© 2022 ASX Limited ABN 98 008 624 691


The following macros are not currently supported in the footer:
  • style