Real-World Example
Jane has an installment payment due tonight. The scheduled payment command runs, checks that her account and payment method are eligible, then dispatches the correct merchant job for Authorize.net, Stripe, or USAePay.
Visual Flow
Schedule Ownership
YouNegotiate is the source of truth for payment-plan schedules. Merchant processors receive individual payment requests when a payment becomes due; they do not own the plan schedule.
Processing must use the current scheduled date after any consumer-approved date change, frequency change, skip, hold, or restart. The platform schedule and BillPay Calendar must update before a payment request is sent.
When a plan is on hold, scheduled payments and payment reminders remain suspended. Processing resumes only when the plan reaches an eligible restart state.
How It Should Work
- It should process due schedule transactions through the scheduled command and merchant-specific queued jobs.
- It should check consumer status, accepted offer, merchant configuration, and payment profile before charging.
- It should process only the most current active schedule after permitted plan changes.
- It should keep schedule, payment history, and BillPay Calendar state aligned.
- It should record success, failure, attempts, and payment history consistently.
- It should avoid overlapping processing for the same scheduled transaction.
How It Should Not Work
- It should not charge consumers whose plans are on hold or not eligible for processing.
- It should not let a merchant processor become the source of truth for the payment schedule.
- It should not process an outdated date after a skip, hold, restart, or date change.
- It should not process the same scheduled transaction twice at the same time.
- It should not bypass gateway-specific services or payment profile rules.
Last modified on August 10, 2026
