Real-World Example
Jane has an active installment plan. A family member gives $3.63 toward her earliest $2.63 installments. While the gift is pending, the first installment shows $2.63 pending and the second shows $1.00 pending. Both installments remain visible as Processing, the other installments remain Scheduled, and her balance stays unchanged until the gift succeeds.Make a Partial Payment
Enter an amount from $0.01 through the remaining amount of the selected installment. You can enter up to two decimal places. The authorization shows the amount you entered before you confirm. If the remaining installment is $400.00 and you confirm $100.05, the charge is $100.05 and the installment drops to $299.95 after the payment succeeds. Enter $400.00 to pay the installment in full. If the payment shows as processing, wait for the confirmed result before submitting another payment.Visual Flow
How It Should Work
- It should show upcoming and historical schedule transactions for the selected account. Processing installments stay visible, including the amount of any pending gift.
- It should reserve only the gift amount, following the chosen earliest-first or latest-first allocation. An installment partly covered by a pending gift remains unavailable for overlapping actions until the outcome is known.
- It should leave untouched installments available for eligible individual actions. It should pause payoff, extra-payment, recurring schedule rebuild and cancellation actions while an installment is processing.
- It should reduce balances and installment amounts only after success, or release the affected reservation after a confirmed failure.
- It should allow only supported plan actions for the current state.
- It should update calendar events when dates, amounts, holds, skips, or cancellations affect the schedule.
- It should keep payment history consistent with manual and background payments.
How It Should Not Work
- It should not hide processing installments or mark the whole schedule as processing for a smaller gift.
- It should not show a pending gift as paid, reduce the balance before confirmation, or retry an unresolved payment as a failure.
- It should not let a consumer change past successful transactions.
- It should not allow hold, skip, or date changes when the plan rules block them.
- It should not update the UI without updating the underlying schedule transactions.

