Dunning for Payment Types

BillHive’s dunning behavior varies based on the payment method associated with the subscription. This page explains the current support and differences by payment type.

Cards and E-Wallets

Status: Supported

Standard dunning flow applies for card payments (credit cards, debit cards) and e-wallets. The system retries payment capture through the configured payment gateway.

• Soft retry (3 immediate retries with 30-minute intervals)
• Smart retry (4 scheduled retries over 7 days)
• Escalation retries (3 retries over Day 14–21)
• Full email communication sequence
• Self-serve payment update link

Mandate / Auto-Collect Payments

Status: Supported

When a subscription uses mandate-based auto-collection (e.g., via Razorpay, Cashfree), dunning triggers when the mandate capture fails after the settlement wait period.

The retry-payment handler uses the subscription’s mandateId to attempt payment capture through the payment gateway. If the mandate has been cancelled or is no longer active, the system proceeds to customer outreach.

Direct Debit (SEPA, ACH)

Status: Not Yet Implemented

Direct debit payments (SEPA via GoCardless/Adyen, ACH via Stripe/Authorize.Net) require special dunning handling because:

• Payment confirmation takes 5–7 business days from the payment service provider
• Multiple retries risk violating direct debit scheme rules
• Failed direct debits may incur bank charges

Planned behavior:

• Separate retry frequency (1–2 attempts recommended, max 5)
• Longer intervals between retries to account for settlement delays
• Email reminders not sent while a direct debit transaction is still in progress
• Compliance with SEPA and NACHA retry rules

See Pending Features for implementation timeline.

3DS / SCA Payments

Status: Not Yet Implemented

Payments requiring 3D Secure authentication (PSD2/SCA compliance) need special handling:

• Standard retries cannot succeed without customer intervention (3DS requires the cardholder to authenticate)
• Retries should only be attempted after the customer has authenticated or on the last day before dunning expires
• Requires integration with the SCA compliance checklist

Planned behavior:

• Detect 3DS failure reasons from gateway error codes
• Only retry one day before dunning period ends if no customer action
• Send “Authentication Required” emails with a link to complete 3DS verification
• Track SCA compliance status

See Pending Features for implementation timeline.

Offline Payments

Status: Not Yet Implemented

Offline payments (cash, checks, bank transfers) cannot be retried automatically. Dunning for offline payments should focus on customer communication only.

Planned behavior:

• Email reminders only (no automatic retries)
• Dunning initiated on the day the invoice is generated
• Separate configuration toggle for offline payment dunning
• Final action options: retain as unpaid, void, or write off

See Pending Features for implementation timeline.

Payment Type Summary