...

• CaseType - This will always be DisputeTransaction

• Action - This should be set to Create for the intake widget and Status for the status widget

• Component1Name - This should represent what the first component is, which is typically an identifier for a customer or member.  Reasonable values for this might be "CustomerId", "MemberId", "SSN", etc.

• Component1 - This typically is an identifier for the accountholder themselves.  This may be a customer id, member id, etc.. it should uniquely identify a human if possible

• Component2Name - This should represent what the second component is, which is typically an identifier for an account, share or card.  Reasonable values for this might be "AccountNumber", "ShareId", "LoanId", "AccountId", "CardId", "CardNumber", etc.. for the status widget, depending on where it is embedded, this parameter may be omitted.

• Component2 - This should represent the account identifier used for the widget.  This may be an account number or share id or card number, etc.. for the status widget, depending on where it is embedded, this parameter may be omitted.

• Component3Name - tbd if needed.  This should represent what the third component is, ex: a unique identifier for a transaction.  This parameter is only used for the intake widget.  Reasonable values for this might be "TransactionSequenceNumber", "TransactionARN", "TransactionPostDateTime", etc.

• Component3 - tbd if needed.  Ex:  this could be an identifier for a particular transaction.  This identifier needs to be unique to a transaction and tie back to one provided to QFD by the core banking integration.  Sequence numbers, timestamps, etc.. are typically used here.. This parameter is only used for the intake widget.

• Component4Name - tbd if needed

• Component4 - tbd if needed

If using Get Case URL both internally and externally, a component will have to be used to differentiate the two.

Sample URL call request (Intake)

...