Specify the type credential requested

Describes the type of client assertion provided in the message request

MPS User Id associated with this amend mandate request

Request UUID that identifies the mandate amendment operation to be performed. This must be a Universally Unique IDentifier (UUID). This UUID must be unique amongst all request_ids passed to this end-point by the same MPS User. If a request is encountered with a request ID that has previously been used then a duplicate check will be performed by comparing the digest of the current request with the digest of the previous request. If the digests match then the details of the previous mandate amendment will be returned. If the digests do not match then an HTTP 409 will be returned.

Boolean flag indicating if the amendment action is bilateral or unilateral.

MPS User Id associated with this create mandate request

Request UUID that identifies the mandate creation operation to be performed. This must be a Universally Unique IDentifier (UUID). This UUID must be unique amongst all request_ids passed to this end-point by the same MPS User. If a request is encountered with a request ID that has previously been used then a duplicate check will be performed by comparing the digest of the current request with the digest of the previous request. If the digests match then the details of the previous mandate creation will be returned. If the digests do not match then an HTTP 409 will be returned.

Optional time used to indicate by when resolution of a bilateral action is requested from the other party to the mandate. It will be provided in any notification sent to the counterparty. This time is for informational purposes only and does not affect the expiry time imposed by the MMS.

An ISODateTime whereby all timezoned dateTime values are UTC.

For an ATTENDED request resolution_requested_by should be within 5 minutes, ANZ will default to 5 minutes where not provided or override to 5 minutes where exceeds 5 minutes.

For an UNATTENDED request resolution_requested_by should be within 5 calendar days, ANZ will default to 5 calendar days where not provided or override to 5 calendar days where exceeds 5 calendar days.

Identification for the mandate request, as originally assigned by the initiating party. Specifies a character string with a maximum length of 35 ASCII printable characters.

Identifies the type of mandate.

Identifies the arrangement (unilateral or bilateral) and party that established the mandate.

Specifies the high level purpose of the mandate based on a set of pre-defined categories. Specifies an alphanumeric string with a length of 4 characters.

Reason for the mandate setup as narrative text. Specifies a character string with a maximum length of 140 ASCII printable characters.

Start date of the validity of the mandate. The mandate is valid as of 00:00:00.000 Australia Sydney time on this date. A particular point in the progression of time in a calendar year expressed in the YYYY-MM-DD format. This representation is defined in "XML Schema Part 2: Datatypes Second Edition - W3C Recommendation 28 October 2004" which is aligned with ISO 8601.

End date of the validity of the mandate. If specified, the mandate is valid until 23:59:59.999 Australia Sydney time on this date. A particular point in the progression of time in a calendar year expressed in the YYYY-MM-DD format. This representation is defined in "XML Schema Part 2: Datatypes Second Edition - W3C Recommendation 28 October 2004" which is aligned with ISO 8601.

Indication of future transfer date, conditions of sale and requirement to hold funds. Specifies a character string with a maximum length of 140 characters.

Automatic renewal of a mandate arrangement at the end of the defined period (period start through period end).

Information concerning the debtor party identified in the mandate.

The following rules apply to this structure:

• AccountIdentificationRule1: If account_identification_type_code is equal to value 'ALIA' then account_alias_type_code and account_alias_identification must be present, and account_identification must be absent.

• AccountIdentificationRule2: If account_identification_type_code is equal to value 'BBAN' then account_identification must be present and start with BSB (bank-state-branch), and account_alias_type_code and account_alias_identification must be absent.

• AccountIdentificationRule3: If establishment_scheme is equal to value 'MGCR' then account_identification_type_code must be equal to value 'BBAN'.

Information concerning the creditor party identified in the mandate.

The following rules apply to this structure:

• CreditorPartyTypeRule1: If establishment_scheme is equal to 'MGCR' then party_type must be present.

Set of characteristics detailing mandate payment information.

Property descriptions:

• payment_frequency - Regularity with which instructions are to be created and processed.
• payment_amount_type - Identifies the mandate payment arrangement.
• first_payment_amount - Amount different from the payment amount, as it includes the costs associated with the first debited amount.
• last_payment_amount - Last payment amount different to the payment amount.
• amount - Fixed amount to be debited from the debtor's account.
• maximum_amount - Maximum amount that may be paid from the debtor's account, per instruction.

The following rules apply to this structure:

• PaymentAmountTypeRule1: If payment_amount_type code is equal to value 'FIXE' then amount must be present.

• PaymentAmountTypeRule2: If payment_amount_type code is equal to value 'BALN' then amount must be present AND (first_payment amount OR last_payment amount) must be present.

• PaymentAmountTypeRule3: If payment_amount_type code is equal to value 'USGB' then maximum_amount must be present.

• PaymentAmountTypeRule4: If payment_amount_type code is equal to value 'VARI' then maximum_amount must be present.

• FirstPaymentDateRule1: first_payment_date cannot be before validity_start_date.

• FirstPaymentDateRule2: first_payment_date cannot be after validity_end_date.

• FirstPaymentDateRule3: If establishment_scheme is equal to 'MGCR' then first_payment_date cannot be present.

• LastPaymentDateRule1: last_payment_date cannot be before validity_start_date.

• LastPaymentDateRule2: last_payment_date cannot be after validity_end_date.

• FrequencyInTermsRule1: Both count_per_period AND point_in_time cannot be present.

• PaymentAmountRule1: amount cannot exceed maximum_amount.

• PaymentAmountRule2: first_payment_amount cannot exceed maximum_amount.

• PaymentAmountRule3: last_payment_amount cannot exceed maximum_amount.

• PaymentAmountRule4: If establishment_scheme is equal to 'MGCR' then first_payment_amount cannot be present.

MPS User Id associated with this change mandate status request

Request UUID that identifies the mandate status change operation to be performed. This must be a Universally Unique IDentifier (UUID). This UUID must be unique amongst all request_ids passed to this end-point by the same MPS User.

Enumeration of possible status changes.

Code defining the reason for the status change to the mandate. Specifies an alphanumeric string with a length of 4 characters.

Date and time when MPIR was created. UTC expressed without offset, i.e. YYYY-MM-DDThh:mm:ss.sssZ An ISODateTime whereby all timezoned dateTime values are UTC.

Date instruction to be processed. Can be future dated, up to 60 calendar days.

MPS User Id associated with this MPIR

MPS User Id associated with this query resolution request

Request UUID that identifies the query resolution operation to be performed. This must be a Universally Unique IDentifier (UUID). This UUID must be unique amongst all request_ids passed to this end-point by the same MPS User.

Case Identifier. A unique case reference as assigned by ANZ. To be referenced when providing a Query Resolution.

Case Decision.

Unique ID, as assigned by the MMS, to unambiguously identify the mandate. This ID must be used to identify the mandate for all further operations on the mandate. Universally Unique IDentifier (UUID) version 1, as described in IETC RFC 4122 "Universally Unique IDentifier (UUID) URN Namespace" without the 4 hyphen separators. For example: '00000000000010008000000000000000' instead of '00000000-0000-1000-8000-000000000000' (without quotes)

Rejection Reason Code.

Unique reference, as assigned by the Biller, to unambiguously identify the return transaction.

To be provided when reject_reason_code = ARDT.