Pay API assessment for data structures to mock

[Arash-IND]

btr-web/btr-common-components/interfaces/fees-i.ts

export interface TaxI { gst: number, pst: number }

export interface FeeInfoI { filingFees: number, filingType: string, filingTypeCode: string, futureEffectiveFees: number, priorityFees: number, processingFees: number, serviceFees: number, tax: TaxI, total: number }

export interface PayFeesWidgetItemI extends FeeInfoI { uiUuid: string, quantity?: number }

[Arash-IND]

{ uiUuid: '123', quantity: 2, filingFees: 0, filingType: 'Register Significant Individual2', filingTypeCode: 'TEST', futureEffectiveFees: 0, priorityFees: 0, processingFees: 0, serviceFees: 0, tax: { gst: 0, pst: 0 }, total: 27.23 }

[mbertucci]

Please update the ticket with your findings.

[Arash-IND]

Below is the JSON structure for the mock pay API which is also aligned with BTR repo, as mentioned in the comment above. Travis set up data on the pay API as a placeholder and in future sprints the plan was to use that. { uiUuid: '123', quantity: 2, filingFees: 0, filingType: 'Register Significant Individual2', filingTypeCode: 'TEST', futureEffectiveFees: 0, priorityFees: 0, processingFees: 0, serviceFees: 0, tax: { gst: 0, pst: 0 }, total: 27.23 }