Consumer Credit Data
These are the data points needed to perform BNPL reporting in the Qlarifi system.
Data Points
Here are the key data points needed by Qlarifi:
- Transaction Unique ID
- Instalment Details - For each instalment
- Instalment unique ID
- Instalment Original Due Date (used for rescheduled instalments)
- Instalment Due Date
- Instalment Amount
We have decided for simplicity’s sake to not consider the rescheduled instalment use cases (some lenders offer consumers the ability to push instalment due dates without penalty).
Tracking Changes
Lenders contribute their own data on consumer transactions—such as loan issuance, repayment, and refunds—which Qlarifi consolidates and analyzes. This enables the creation of detailed credit reports that reflect a consumer’s history and behavior, allowing lenders to make more accurate and fair underwriting decisions.
Qlarifi Credit Events
| Event Name | Description | Sample Event Link |
|---|---|---|
| TransactionIssued | Event raised when a lender has approved and created a transaction for a consumer. | Sample |
| TransactionPaidOff | Event raised when the lender recorded a payment against a transaction. | Sample |
| TransactionRefunded | Event raised when a refund was issued against a transaction. A transaction might have multiple events of this type. | Sample |
| TransactionCanceled | Event raised when a transaction has been cancelled. This can be due to a variety of reasons, such as a system error. A cancelled transaction is removed from a consumer's payment history. | Sample |
| TransactionWrittenOff | Event raised when a transaction has successfully been written off by the lender. This means that the lender has accepted that the transaction will not be repaid by the consumer. | Sample |
| InstallmentPaidOff | Event raised when the lender recorded a payment against an instalment. | Sample |
| InstallmentRebalanced | Event raised when a transaction's instalment amount has changed and been rebalanced to a different amount. This can happen on a unique transaction that changes the instalment schedule after auth/capture flows. | Sample |
| InstallmentWrittenOff | Event raised when an installment has successfully been written off by the lender. This means that the lender has accepted that the installment will not be repaid by the consumer. | Sample |
| InstallmentCanceled | Event raised when an instalment has been cancelled. This can be due to a variety of reasons, such as a system error. A cancelled instalment is removed from a consumer's payment history. | Sample |
| InstallmentPostponed | Event raised when an instalment repayment due date has been pushed to a later date. It is sometimes referred to as “rescheduling” or “snoozing” an instalment, and may incur a fee that is indicated in the event. If the fee is added to the loan amount (i.e. instead of paid separately at the time of rescheduling), the lender should also notify that change in the loan value by issuing one or several InstallmentRebalanced events. | Sample |
| FeeIssued | Event raised when a fee has been issued on an instalment or transaction. This can be due to a variety of reasons, such as a late payment or a rescheduled instalment. | Sample |
| FeePaidOff | Event raised when a fee has been paid on an instalment or transaction. | Sample |
| FeeCanceled | Event raised when a fee has been cancelled. This can be due to a variety of reasons, such as a system error. A cancelled fee is removed from a consumer's payment history. | Sample |
| FeeRebalanced | Event raised when a fee has been rebalanced to a different amount. This can happen on a unique transaction that changes the fee schedule after auth/capture flows. | Sample |
| FeeWrittenOff | Event raised when a fee has successfully been written off by the lender. This means that the lender has accepted that the fee will not be repaid by the consumer. | Sample |