Skip to main content

Chargeback and refund models

These models handle transaction disputes, chargebacks, and refund processing in Chargeworx.

ChargebackDetail

Tracks chargeback disputes initiated by cardholders or issuing banks.

Key properties

PropertyTypeDescription
IdGuidUnique chargeback identifier
TransactionIdGuidAssociated transaction reference
ReasonCodeStringChargeback reason code
AmountDecimalDisputed amount
StatusStringChargeback status
ReceivedDateDateTimeDate chargeback was received
DueDateDateTimeResponse due date
ResolutionDateDateTime?Date chargeback was resolved

Relationships

  • Belongs to a Transaction

Chargeback lifecycle

  1. Received - Chargeback notification received from processor
  2. Under review - Merchant reviewing dispute
  3. Responded - Evidence submitted to processor
  4. Won/Lost - Final resolution
  5. Closed - Case closed

PurchaseRefund

Represents merchant-initiated refunds for transactions.

Key properties

PropertyTypeDescription
IdGuidUnique refund identifier
TransactionIdGuidOriginal transaction reference
AmountDecimalRefund amount
ReasonStringRefund reason
StatusStringRefund status
RequestedDateDateTimeDate refund was requested
ProcessedDateDateTime?Date refund was processed
RefundTypeStringFull or partial refund

Relationships

  • Belongs to a Transaction

Refund types

  • Full refund - Complete transaction reversal
  • Partial refund - Partial amount returned to customer

Refund lifecycle

  1. Requested - Refund initiated by merchant
  2. Pending - Submitted to payment processor
  3. Approved - Processor approved refund
  4. Completed - Funds returned to customer
  5. Failed - Refund processing failed

Usage patterns

Processing refunds

Refunds can be initiated through the admin UI or API. Partial refunds allow merchants to return a portion of the transaction amount.

Managing chargebacks

Chargebacks require merchant response within the due date. Evidence and documentation can be attached to dispute cases.

Reporting

Both chargebacks and refunds impact merchant account health and are tracked for reporting and analytics purposes.

Best practices

  • Process refunds promptly to avoid chargebacks
  • Maintain detailed transaction records for chargeback defense
  • Monitor chargeback ratios to maintain processor compliance
  • Document refund reasons for business intelligence