Fees object of GET Account Detail API

Question 1

Via Get Product Detail API we show that for a product Orange Everyday, there is a fee for ‘International ATM withdrawal’, and ‘International purchase’. There is also an eligibility based discount, if a customer does specific actions each month (When you deposit $1,000 or more per month and make 5+ card purchases that are settled (not pending) each month.), the above fees will be refunded. 

Is the response for the above fees and discount via Get Account Detail API supposed to be different from Get Product Details API? For example, do we need to indicate in some way that a customer has met eligibility for this month, but not for the next month on an account level? Or would the responses via both APIs be identical in this scenario?

Question 2

Below is an example of a response from Products API for a late payment fee for a credit card:

name	mandatory	Late payment fee
feeType	mandatory	EVENT
amount	conditional	20.00
balanceRate	conditional
transactionRate	conditional
accruedRate	conditional
accuralFrequency	optional
currency	optional	AUD
additionalValue	conditional
additionalInfo	optional
additionalInfoUri	optional
discounts	optional

If on an account level, a customer has negotiated a discount for this fee, does it mean that in a response from Get Account Detail API we will should populate the ‘discounts’ field that was empty in Products API response with a ‘-20.00’ amount (if the discount was 100%)?

If on an account level, a customer has negotiated a discount for this fee for one time only, but this same fee might be applied in future, how should we show this in a response from Get Account Detail API?

Should we introduce new types of discounts, which are not part of the Products API response?

Answers

To answer the questions above in more detail, they are divided into subsections with the corresponding answers below.

Question 1a: Is the response for the above fees and discount via Get Account Details API supposed to be different from Get Product Detail API?
DSB Answer: The fees shown in the Get Account Details API should be the same types of fees shown in the PRD endpoint however they may have negotiated rates specific to the account. Broadly speaking, the way you are representing the fees should be the same if they apply to the account. There may also be account specific fees that do not apply to the publicly offered products presented in PRD.

Question 1b: For example, do we need to indicate in some way that a customer has met eligibility for this month, but not for the next month on an account level?
DSB Answer: This would be a good idea. In the example you gave about discounted fees based on deposit amount or number of card purchases, you could use discountType = DEPOSITS and discountType = ELIGIBILITY_ONLY respectively to represent these discount conditions.

For discountType = DEPOSITS, additionalValue should be set to $1000. additionalInfo can be used to note whether the customer has satisfied this condition, however it is not mandatory to do so because it is assumed the ADR can infer this from the balance and transactions list.

For discountType = ELIGIBILITY_ONLY, the associated BankingProductDiscountEligibility must be populated. In the situation you describe, discountEligibilityType would be 'OTHER' and the additionalValue populated with something like '5+ card purchases that are settled (not pending) each month'. additionalInfo may be used to denote whether the customer has qualified for this, but it is not mandatory because it is assumed the ADR can infer this from the transactions list.

Question 1c: Or would the responses via both APIs be identical in this scenario?
DSB Answer: Since you have the context of the customer's transactions, you can present additional information if the customer has qualified for the discount and/or satisfied the eligibility criteria but it is not mandatory and left to the DH to decide.

Question 2a: If on an account level, a customer has negotiated a discount for this fee, does it mean that in a response from Get Account Details API we will should populate the ‘discounts’ field that was empty in Products API response with a ‘-20.00’ amount (if the discount was 100%)?
DSB Answer: Yes, you should populate the discount object with the negotiated discount. The amount would be a positive value because discount implies it is to be deducted from the base fee.

Question 2b: If on an account level, a customer has negotiated a discount for this fee for one time only, but this same fee might be applied in future, how should we show this in a response from Get Account Details API?
DSB Answer: This isn't specified in the standards how DHs should handle this. You may do as you have described and use an ELIGIBILITY_ONLY discountType with discountEligibilityType of 'OTHER', the additionalValue representing the negotiated amount and additionalInfo qualifying that this is a once-off discount. Alternatively, one time only discounts could be shown as fee waiver transactions on an account.

Question 2c: Should we introduce new types of discounts, which are not part of Products API response?
DSB Answer: If the list of discountTypes are insufficient we'd welcome change requests raised on our standards-maintenance GitHub repository. You cannot create a discount type that does not exist in the standards, so we need to go through the change process to incorporate it into the standards. This would be excellent to raise if you have identified different discount types that warrant inclusion.

Likewise, if you feel there are gaps or areas where the standards could be clearer in these respects, I am sure other DHs would benefit if you wish to raise a change request.

See:

• Creating a Change Request
• CDS Get Account Detail
• CDS Banking Product Fee