Product Manager changes for DP338 (Y26 #1)
This guide outlines the changes Biza has introduced within Product Manager to support compliance with Decision Proposal #338, which must be implemented by 16 March 2026.
To recap the intended outputs of Decision Proposal #338, the following changes were proposed:
1. Incremented endpoint versions:
2. Summary of the changes incorporated into the updated versions following Decision Proposal #338:
- Added cardScheme and cardType fields in the existing cardArt object.
- Added
BALANCE_TRANSFERlendingRateType option. - Modified the feature isActivated field behaviour.
- Added
FUNDS_AVAILABLE_AFTERfeatureType option. - Added
OTHERconstraintType option. - Clarified the descriptions of the constraints and features fields.
- Updated and aligned the
PENSION_RECIPIENTandSTUDENTeligibility and discount eligibility 'Use of additionalValue Field' details. - Added
OTHERandUNCONSTRAINEDrepaymentType options and specified the field as mandatory. - Added
OTHERandUNCONSTRAINEDloanPurpose options and specified the field as mandatory. - Modified the existing applicabilityConditions structure in rate tier objects and added the same structure at the rate level.
- Added rate applicationType field in rate objects and modified the corresponding applicationFrequency field requirement.
- Changed the field type for the minimumValue and maximumValue fields in the rate tier structure from 'Number' to 'string'.
- Removed the
VARIABLEfeeType value, added eight new feeType values, and refined the fee and fee discount structures.
Required Actions
To ensure your product data complies with DP338, you will be required to review the following tables prior to 16 March 2026.
- Cart Art
- Features
- Constraints
- Fees
- Deposit Rates
- Lending Rates
To support you, Biza has made the following changes to Product Manager:
1. Introduction of a schema validation report
On the Space Dashboard, we have introduced a new coverage report that allows you to quickly query whether all your product data can be successfully rendered into compatible payloads for the latest product endpoint versions. This helps you verify that your product reference data structure aligns with the standards.
This report does not verify the accuracy of the product reference data and should be used in conjunction to our Verification Testing Tool (VTT) to ensure a deeper payload validation.
2. Introduction of a new Approver role in Product Manager
As part of the 1.0.13 release, we have introduced a new approver role (biza-au:pm:changeset:approve) that now allows the appropriate
segregation of responsibilities within Product Manager. Users with this role will be able to Approve drafted changesets
and immediately execute changes to product data.
The existing write role (biza-au:pm:write) will be restricted to drafting changes to changesets, which will
require approval from a user with the approver role before they are scheduled.
To minimise the impact to your services ahead of the upcoming FDO, the approver role will remain a global capability to users until the 30 April 2026.
Ahead of this timeframe, please review your permission groups in your identity provider (Entra/Okta) and ensure you have assigned the appropriate roles to prevent any disruption of services. This has been outlined in the schedule here.
3. ‘Update Required’ flag on existing data tables
To help visualise the tables which need updates to comply with the upcoming FDO, we have introduced an ‘Update Required’ flag on data sets missing inputs for mandatory or conditional fields in the new product schemas. The data sets must be reviewed and updated prior to the March 16 FDO date. To make updates, click 'Update', which will open a modal where you can provide the required field inputs.
See examples below highlighting these flags across the Card Art and Deposit Rate tables, respectively.
4. Introduction of Fee Method Type and Discount Method Type
A major change to the Fee table is the introduction of a Fee Method Type. These specify the nature of how the respective fees will be charged. The options are defined below:
- Fixed Amount - A predetermined, specific sum payable according to applicable terms.
- Rate Based - A pricing structure where the fee is based on a specific rate calculation.
- Variable - An at-cost fee that is relevant to a customer's circumstances, where the amount or rate may not be known until negotiated with the customer.
We’ve introduced a radio button that allows you to select the fee type and input the required dataset for that type.
A further addition to the fee tables is the introduction of the discount method type. This allows discounts to be either:
- Fixed, or
- Rate based.
Rate based discounts require the rate type to be defined as one of the following:
- Balance - A fee rate discount based on a balance.
- Fee - A fee rate discount based on the fee to which the discount is attached.
- Interest Accrued - A fee rate discount based on interest accrued.
- Transaction - A fee rate discount based on a transaction.
The example below highlights the segmented controller used to specify the method and rate type highlighting an example of a Rate based, fee type discount:
5. Introduction of Application type and Rate Application type to Deposit Rates
To support the changes to the Deposit and Lending Rate tables, we have introduced a new mandatory dropdown field to specify the Application Type. This approach is used to apply the rate to the account, with the following options:
-
Maturity - Applied at the end of the term.
-
Periodic - Applied repeatedly over a given timeframe.
-
Upfront - Applied at the start of the term.
We’ve also introduced the ability to apply rate applicability conditions associated with a rate and/or within rate tiers. This supports the following application types:
- Minimum Deposits - When a minimum number of deposits is made in a month, or the month prior.
- Minimum Deposit Amount - When a minimum deposit amount is made in a month, or the month prior.
- Deposit Balance Increased - When the overall balance of the account, excluding interest, has increased over the month prior.
- Existing Customer - Applicable to existing customers of the brand.
- New Accounts - Applicable to new accounts.
- New Customer - Applicable to new customers to the brand.
- New Customer to Group - Applicable to new customers to a group of brands.
- Online Only - Applicable to accounts originated online.
- Other - Applicable under other conditions. The additionalInfo field is mandatory for this type.
- Minimum Purchases - When a minimum number of purchases is made and settled in a month, or the month prior.
- Maximum Withdrawals - Applicable up to a maximum number of withdrawals in a month, or the month prior.
- Maximum Withdrawal Amount - Applicable up to a maximum amount withdrawn in a month, or the month prior.