Cash, Card and Bank Transfer: How Small Businesses Can Track Different Payment Methods

Card payments can be confirmed automatically by the payment provider. Cash payments need admin to confirm the money was physically received. Bank transfers need admin to check the bank account before the invoice is marked paid. Customers should be able to indicate their payment method, but only the business can confirm the payment was received.

Card payments are the most straightforward to automate. The customer pays through a trusted provider such as Stripe. The provider confirms whether the payment succeeded, the amount paid, the currency and the payment reference. The website then updates the invoice after receiving that confirmation.

The key point is that the confirmation comes from the provider, not from the browser. As covered in the guide on Stripe server-side payment confirmation, the server should verify the result independently before updating the invoice.

When a card payment succeeds, the invoice can move straight to paid. A receipt email is sent automatically. The payment reference is stored in the log. Admin does not need to manually check anything for a successful card payment — the workflow handles it cleanly.

If a card is declined, the invoice stays unpaid and the failed attempt is logged. Staff can see this in the invoice payment log and follow up with the customer if needed.

Cash is different from card in one important way: the business cannot verify it automatically. A customer may click a button that says they paid by cash, but that does not mean the money has been received. The invoice should not become paid until staff physically confirm the cash was handed over.

A good system handles this with a cash pending state. When the customer indicates they will pay by cash, the invoice moves to cash pending. Admin receives a notification or sees the item on the payments dashboard. When the cash is received, admin confirms it and the invoice moves to paid.

This protects the business from false paid records. A customer might say they will pay cash and then not show up. Or they might pay the wrong amount. Or a technician might collect cash onsite and forget to record it. The cash pending step creates a clear checkpoint where staff confirm the reality before the record changes.

Bank transfers need the most care. A customer may send a transfer and tell the business immediately. But the transfer may take time to arrive. The amount may be wrong. The payment reference may be missing. The payment may come from a different account name than expected.

For this reason, bank transfer should usually stay in a pending state until admin confirms the funds have arrived. The customer can indicate they sent a bank transfer on the invoice page, but the status should not update automatically. Admin should check the bank account and confirm the correct amount arrived with a matching reference before the invoice becomes paid.

Some businesses send bank details separately rather than on the invoice page itself, which reduces confusion about what reference to use. Either way, the confirmation step should be a deliberate admin action, not something the customer triggers by clicking a button.

The simplest paid or unpaid status is not always enough for a service business. A more useful set of payment states might include:

• Unpaid — invoice sent, no payment action yet
• Viewed — customer has opened the invoice
• Card payment pending — checkout started but not yet confirmed
• Cash pending — customer indicated cash payment, awaiting admin confirmation
• Bank transfer pending — customer indicated a transfer, awaiting admin check
• Paid — confirmed by provider or by admin
• Overdue — payment due date has passed
• Cancelled — invoice voided or superseded

These states help staff focus on what needs attention without manually reviewing every invoice. See how the invoice status automation guide explains how each status reduces confusion for both customers and staff.