Data Category | Event Field/Column Name | Data Type | Description | Applicability | Sample Value | Notes |
|---|---|---|---|---|---|---|
Key | TenantId | VARCHAR | Unique ID associated with each Quavo client. | ALWAYS | qvo-stg | |
Key | Tenant | VARCHAR | A tenant is a Quavo customer that uses QFD. Each tenant is assigned a unique Tenant ID. | ALWAYS | Default | |
Key | ClientId | VARCHAR | A unique ID representing a single client. | ALWAYS | Default | |
Key | Client | VARCHAR | A client is a Quavo customer that uses QFD through a relationship with a Quavo tenant. Each client is assigned a unique Client ID. | ALWAYS | Default | |
Claim Details | ClaimType | VARCHAR | See Transaction Type. | CONDITIONAL | Card-Pinless | |
Claim Details | ClaimCategory | VARCHAR | General categorization of the claim. For a more precise description, see Claim Reason. | CONDITIONAL | Fraud | |
Claim Details | ClaimReason | VARCHAR | Identifies the specific reason associated with the claim. | CONDITIONAL | Stolen | |
Compliance Details | RegulatoryCoverage | VARCHAR | Identifies the specific reason associated with the claim. | CONDITIONAL | Reg E | |
Card Details | BIN | VARCHAR | Bank Identification Number (BIN) is the first 4-8 digits of a payment card that identifies the issuing institution. | CONDITIONAL | 412356, 41235678 | |
Transaction Details | TransactionType | VARCHAR | The type of transaction, such as ACH, BillPay, Card, Check, RTP, Wire, Zelle, etc. | ALWAYS | ATM | |
Transaction Details | Network | VARCHAR | A network is a company that provides the communication system between a merchant and a card issuer in order to process transactions. For more details, see Acquirer Networks. | CONDITIONAL | Mastercard, Visa | |
Key | ClaimId | VARCHAR(32) | Unique ID associated with a claim. Format: YYMMDD<Ordinal Number>"C" Example: 2405230003C | ALWAYS | 2306060014C | |
Key | DisputeId | VARCHAR(32) | ALWAYS | 2306060014D | ||
Claim Details | ClaimStatus | VARCHAR(64) | Represents the current stage or step of a particular process or lifecycle, such as a claim or dispute. | ALWAYS | RESOLVED-PAID | |
Dispute Details | DisputeStatus | VARCHAR(64) | Represents the current stage or step of a particular process or lifecycle, such as a claim or dispute. | ALWAYS | RESOLVED-PAID | |
Dispute Details | Decision | VARCHAR(64) | "Paid" or "Denied". If one, or more, disputes on a claim are paid, the claim decision is "Paid". | CONDITIONAL | Paid, Denied | |
Dispute Details | DenyReason | VARCHAR | The reason associated with a denial action. See Denied for a list of supported reasons. | CONDITIONAL | No Error | |
Dispute Details | ReassertionIndicator | BOOLEAN | Indicates if the dispute has been reopened. | CONDITIONAL | TRUE | |
Account Details | NextPaymentDate | DATE | The next scheduled automatic payment date, as of the date the claim was filed, as provided by the system of record. | CONDITIONAL | 2023-09-09 | Only applicable when provided by the System of Record. |
Account Details | AutopayEnrollmentIndicator | BOOLEAN | Represents whether the account is enrolled for automatic bill payment, when this information is available from the system of record. | CONDITIONAL | TRUE | Only applicable when provided by the System of Record. |
Account Details | StatementCycleDate | DATE | The date, or day of month, that an account cycles and a statement is generated. | CONDITIONAL | 2023-09-09 | Only applicable when provided by the System of Record. |
Dispute Details | CreateDate | DATE | The datetime that a record was created. | CONDITIONAL | 2023-09-09 | |
Claim Details | ContactDate | DATE | Represents the date that the claim was received from the accountholder. | CONDITIONAL | 2023-09-09 | |
Compliance Details | InvestigationDate | TIMESTAMP_NTZ(9) | Date and/or datetime that a Pay or Deny decision is rendered for all disputes on a claim. | CONDITIONAL | 2023-09-09 21:00:00 | |
Correspondence Details | AcknowledgementLetterDate | TIMESTAMP_NTZ(9) | Datetime that the acknowledgement (confirmation) letter was mailed. | CONDITIONAL | 2023-09-09 21:00:00 | |
Compliance Details | AcknowledgementDeadline | TIMESTAMP_NTZ(9) | Date that the claim must be acknowledged, where required. | CONDITIONAL | 2023-09-09 | Only applicable to claims covered by Regulation Z. |
Compliance Details | PC1020 | Number | Indicates whether a 10 business day or 20 business day PC requirement is applied based on the proximity of disputed transaction dates to account open date. | CONDITIONAL | 10, 20 | Only applicable to claims covered by Regulation E. |
Compliance Details | PCDeadline | DATE | Calculated date that indicates the date that a dispute must be resolved or granted provisional credit. | CONDITIONAL | 2023-09-09 | Only applicable to Regulation E. |
Compliance Details | WitholdingDeadline | DATE | Calculated date that a provisional credit or dispute status must be applied to a dispute in order to prevent a billing attempt by debiting a disputed amount via automatic payment. | CONDITIONAL | 2023-09-09 | Only applicable to Regulation Z. |
Accounting Details | PCDate | TIMESTAMP_NTZ(9) | Datetime that a provisional credit accounting entry was executed. | CONDITIONAL | 2023-09-09 21:00:00 | Only applicable when provisional credit accounting has been executed. |
Accounting Details | PCAmount | NUMBER | Amount of provisional credit accounting entry was executed. | CONDITIONAL | 123.45 | Only applicable when provisional credit accounting has been executed. |
Correspondence Details | PCLetterDate | TIMESTAMP_NTZ(9) | Datetime that notification of provisional credit was mailed. | CONDITIONAL | 2023-09-09 21:00:00 | Only applicable when provisional credit letter has been mailed. |
Dispute Details | DisputeStatusDate | TIMESTAMP_NTZ(9) | Datetime that a dispute was placed in dispute status via Account Maintenance. | CONDITIONAL | 2023-09-09 21:00:00 | Only applicable to Regulation Z. |
Compliance Details | ResolutionDeadline | DATE | Datetime assigned by the system by which a claim must be resolved in order to be compliant with applicable regulations. | ALWAYS | 2023-09-09 | |
Dispute Details | ResolutionDate | TIMESTAMP_NTZ(9) | Datetime that a claim or dispute is set to a "Resolved" status.. Also referred to as RESOLVEDDATETIME. | CONDITIONAL | 2023-09-09 21:00:00 | Only applicable when the dispute has been resolved. |
Accounting Details | FinalCreditDate | TIMESTAMP_NTZ(9) | Datetime that a final credit was executed via one of the following accounting entries: ‘Final Credit’, ‘Undue Enrichment Recovery (AccountHolder)’, ‘Write Off’. | CONDITIONAL | 2023-09-09 21:00:00 | Only applicable when a final credit has been executed. |
Accounting Details | FinalCreditAmount | NUMBER | Amount of final credit via one of the following accounting entries: ‘Final Credit’, ‘Undue Enrichment Recovery (AccountHolder)’, ‘Write Off’. | CONDITIONAL | 123.45 | Only applicable when a final credit has been executed. |
Correspondence Details | ResolutionLetterDate | TIMESTAMP_NTZ(9) | Datetime that a Paid or Denied letter was mailed. | CONDITIONAL | 2023-09-09 21:00:00 | Only applicable when a resolution letter has been mailed. |
Accounting Details | DenyDebitDate | TIMESTAMP_NTZ(9) | Datetime that a credit reversal was executed via one of the following accounting entries: ‘Deny Dispute', ‘Final Credit Reversal’. | CONDITIONAL | 2023-09-09 21:00:00 | Only applicable when deny debit accounting has been executed. |
Accounting Details | DenyDebitAmount | NUMBER | Amount of credit reversal via one of the following accounting entries: ‘Deny Dispute', ‘Final Credit Reversal’. | CONDITIONAL | 123.45 | Only applicable when deny debit accounting has been executed. |
General
Content
Integrations