Data Category | Event Field/Column Name | Data Type | Description | Applicability | Sample Value | Notes |
|---|---|---|---|---|---|---|
Key | TenantId | VARCHAR(32) | Unique ID associated with each Quavo client. | ALWAYS | qvo-stg |
|
Key | ClientId | VARCHAR(64) | A unique ID representing a single client. | ALWAYS | Default |
|
Key | ClaimId | VARCHAR(32) |
Unique ID associated with a claim. Format: YYMMDD<Ordinal Number>"C" Example: 2405230003C
| ALWAYS | 2306060014C |
|
Key | DisputeId | VARCHAR(32) | Unique ID associated with a disputed transaction. Format: YYMMDD#####"D" | ALWAYS | 2306050001D |
|
Decision Details | Decision | VARCHAR(64) | When related to a claim or dispute, this represents a pay/deny decision applied. When related to recovery actions, this represents a decision made by the system or user to pursue or not pursue recovery. Reflected as either "Deny," "Write Off," or "Pay" | CONDITIONAL | Deny | Only applicable when a decision has been rendered. |
Decision Details | Reason | VARCHAR | For deny decisions, this represents the deny reason applied. For pay decisions, this represents the free-form reason provided by the user. | CONDITIONAL | No Error |
|
Decision Details | Justification | VARCHAR | A list of justifications applied to the decision. | CONDITIONAL | 3D card secure. |
|
Decision Details | PerformedByUserId | VARCHAR | The username of the user that made the decision. For automated decisions, a description of the system job will be displayed. | CONDITIONAL | devan.robertson@quavo.com |
|
Metadata | EventDateTime | TIMESTAMP_NTZ(9) | The datetime that the event was recorded. | ALWAYS | 2023-09-09 21:00:00 |
|
Metadata | EventIdentifier | VARCHAR(64) | A unique ID associated with each business event. | ALWAYS | 70b1c86d-d06f-4c93-bab2-0e938a4ef768 |
|
Metadata | EventItemId | VARCHAR(64) | An ID included with each business event that identifies the tenant and Claim ID or Dispute ID associated with the event. | ALWAYS | qvo-stg|2302030002D |
|
When a pay or deny decision is applied to a dispute, an event is generated. The event includes any reasons and/or justifications applied to the decision, as well as the username of the user that made the decision. When a decision is automated, details about the system job are displayed.
General
Content
Integrations