Payments made through the Clan Pay (Group Pay) system are applied as account credits. These credits automatically cover any invoices generated in the billing system. Credits function account-wide rather than attaching to individual services and are consumed on a first-come, first-served basis according to the order in which invoices are generated.

This model simplifies shared payment management for groups or organizations running multiple services under a single account. The billing engine draws from the central credit balance whenever an invoice appears, eliminating manual assignment while maintaining a clear, chronological application order.

#Mechanics of Credit Application

When a Clan Pay transaction completes, the full amount is added to the account credit balance immediately. The billing system references this balance each time it creates an invoice for any resource. Available credit is deducted before the invoice becomes payable. No manual steps or per-service routing is required or possible.

Because credits remain unattached to any particular service, a contribution intended for one item can satisfy costs from another if that second invoice reaches the system first. The account-centric design prioritizes overall balance management and prevents credits from sitting idle while other services incur charges.

#First-Come, First-Served Invoice Order

The billing engine processes invoices strictly by their generation timestamp. The oldest unpaid invoice receives credit first. Remaining credit then rolls to the next invoice in sequence until the credit is exhausted or all open invoices are satisfied. This produces predictable behavior once you understand the timing of your services' renewal cycles.

  • Credits apply automatically at the moment an invoice is generated
  • Application is account-wide with no per-service isolation
  • Oldest invoices are paid before newer ones when credit is limited
  • Any credit left after an invoice rolls forward to the next

#Practical Example

Consider a member submitting a $5 Clan Pay payment on November 1. This increases the account credit balance by $5.00. On November 2 your web hosting service generates its monthly invoice for $12. The system applies the entire $5 credit to that invoice, reducing the amount due to $7. If a domain renewal invoice had generated on October 31, it would have been eligible for the credit first.

Scale this pattern to accounts with many services and staggered billing dates. A larger group contribution arriving just before several renewals will be consumed in the exact order the invoices enter the system. Timing therefore matters more than the intended purpose of any single payment.

Timestamp          | Event                          | Amount    | Credit Balance
-------------------|--------------------------------|-----------|----------------
Nov 1  14:22       | Clan Pay payment received      | +$25.00   | $25.00
Nov 2  00:05       | Hosting invoice INV-4412       | -$15.00   | $10.00
Nov 3  08:17       | Domain invoice INV-4413        | -$12.00   | $0.00
                   | (applied $10 credit, $2 due)   |           |

#Common Pitfalls and Considerations

The most frequent misunderstanding is assuming a Clan Pay contribution will only affect the contributor's chosen service. The system ignores such intent and follows invoice chronology exclusively. Services with earlier renewal dates can consume credits before later ones, even if the payment was notionally directed elsewhere.

  • Staggered service renewals can cause credits to be used by unexpected invoices
  • Credits do not expire but are only consumed when invoices are generated
  • Large credits may satisfy multiple small invoices generated in rapid succession

#Managing Your Account Credits

Regularly review the billing portal to see the current credit balance, payment history, and which invoices have already consumed prior credits. Align group contribution schedules with the known renewal dates of your highest-value services. This reduces the chance that an early minor invoice depletes funds needed for a larger upcoming renewal.

When coordinating Clan Pay activity among team members, treat contributions as general account funding rather than service-specific allocations. Maintain an internal calendar of upcoming invoice windows so the group can top up the credit balance ahead of clustered renewal activity.

Monitor the account after each Clan Pay deposit to confirm the credit appears and is available. Invoices generated immediately after a deposit will draw against it automatically. Understanding this flow lets groups maintain positive balances across all services without constant per-invoice intervention.

Treat Clan Pay payments as deposits into a shared account wallet. The billing system draws from this wallet automatically based on invoice creation order. Align contribution timing with your overall billing calendar to maximize value and avoid unexpected balances.