When a payment fails, the transaction should remain unsuccessful, the balance should stay open, and the workflow should determine whether to retry, notify the customer, restrict service, or escalate the issue.
A failed payment does not always mean the same thing. The payment provider may return a decline, processing error, expired method, or another failure status, and the next step depends on the configured payment rules.
What Should Be Recorded After a Failure?
- The customer and related invoice or booking.
- The amount and time of the payment attempt.
- The failure status or reason returned by the payment provider.
- Whether another attempt is allowed or scheduled.
- Whether the customer has been notified.
- The remaining balance after the failed attempt.
What Rules Should Be Defined?
Define whether failed payments are retried, how many attempts are allowed, when the customer is notified, when reminders or escalation begin, and whether an unpaid balance affects the related service or booking.
What Happens If the Next Attempt Succeeds?
The successful payment should update the related balance and payment status. Earlier failed attempts should remain in the transaction history instead of being erased.
Where Can You Review Payment Features?
See Payment Processing for declined transaction handling and Payment Reminder for follow-up and overdue workflows.
What Should You Review Next?
Related reading: Refund vs. Credit · What Is a Chargeback?.
Sources and Further Reading
- Booking Ninjas: Payment Processing — covers payment status, declined transactions, invoice updates, refunds, and payment records.
- Booking Ninjas: Payment Reminder — covers overdue follow-up, reminder timing, and escalation rules.
- Stripe Billing APIs
- Stripe: How Subscriptions Work
- Stripe: Refund and Cancel Payments
- Stripe: How Disputes Work
External references explain the underlying concepts; they do not imply Booking Ninjas requires or uses the referenced product.