Troubleshooting & FAQPayment Issues

Payment Issues

Last reviewed: 16 November 2026

A payment failed

Symptoms. The invoice stays unpaid, the subscription shows In Dunning, the customer got a Payment Failed email.

Causes. Soft declines (insufficient funds, limit exceeded, network error) or hard declines (expired card, closed account, mandate revoked).

Check. The transaction on Customers > Transactions and the dunning case for the failure reason.

Fix. Soft declines are retried automatically. For hard declines, ask the customer to update the payment method through the link in the dunning email.

Prevent. Watch Card Expiry Approaching and Payment Method Invalid notifications; use mandates for recurring debits.

The customer paid, but the invoice is still unpaid

Causes. The payment was made outside BillHive (bank transfer, cheque), or the gateway confirmation hasn’t arrived yet.

Fix. Record the offline payment against the invoice. See Recording Offline Payments. If the payment is sitting unapplied on the account, apply it. See Unapplied Payments.

Gateway settlement doesn’t match BillHive

Fix. Compare the gateway’s settlement report with Customers > Transactions by gateway reference. BillHive doesn’t import settlement reports. Look for refunds and gateway fees, which change the settled amount but not the invoice.

A refund didn’t reach the customer

Causes. The customer paid offline, so there was no gateway payment to refund; BillHive created a Refund transaction in Needs Attention for finance instead.

Fix. Pay out from your bank and record it. See Offline Refunds.

Gateway onboarding is stuck

See Gateway Onboarding Troubleshooting and Onboarding Status.

Dunning cancelled a subscription the customer wanted to keep

Fix. Reactivate it once the customer is ready to pay; the reactivation starts a new term at the plan’s current list price.

Prevent. Watch high-value accounts flagged for manual review during escalation. Pausing dunning is planned, not available yet.

Webhook for a payment arrived with an empty body

By design today: only subscription events carry data. Call GET /invoices/{invoiceId} or the account’s transactions to read payment details. See Webhook limits.