Payments

Concept

QueueJump uses Stripe Connect to move an order from checkout intent to paid status and eventual payout.

You remain merchant of record. QueueJump does not hold customer funds. Payments are created on your connected Stripe account and settled by Stripe to your payout bank account.

Operationally, the flow is:

1. A customer checks out against an active public session.
2. QueueJump validates basket totals server-side before creating payment intent.
3. Payment outcome updates order status.
4. Paid orders move into fulfilment flow.
5. Stripe settles funds to your account on your payout schedule.

Why it matters

Reliable payment flow protects service quality and financial clarity.

• Teams avoid prepping unpaid orders.
• Basket and charge mismatches are reduced.
• Refund handling remains traceable to original payment.
• Daily reconciliation becomes repeatable and lower risk.
• Customer trust improves when payment and order state stay aligned.

For most vendors, payment mistakes do not come from card rails. They come from operational drift around status handling and reconciliation discipline.

How to configure it

1. Connect Stripe in Dashboard -> Settings -> Payments.
2. Complete onboarding until your account is ready to both charge cards and receive payouts.
3. Confirm your active session is published and linked to the correct menu and location.
4. Place a low-value live order from a customer device.
5. Confirm the order reaches paid status before prep starts.
6. Run one controlled refund test so your team understands refund flow.
7. Set a daily reconciliation routine using Payouts and reconciliation.
8. Keep prep workflow strict: no prep begins until payment is confirmed as paid.

If Stripe readiness is incomplete, paid checkout should be treated as blocked until capability status is resolved.

How to verify it worked

• A low-value live order produces a paid order status in queue.
• Failed payments do not appear as prep-ready orders.
• Refund actions are recorded against the original payment.
• Daily order totals and Stripe settlement data align.
• Your team follows paid-status-only prep discipline during service.

Related guides: Connect Stripe, Refunds, and Payouts and reconciliation.

Common mistakes

• Starting prep before paid status is confirmed.
• Treating Stripe setup as complete before charge and payout capability are ready.
• Skipping daily reconciliation.
• Assuming payout timing is controlled outside Stripe policy.
• Assuming QueueJump holds or releases funds.
• Running live service after major changes without a low-value live order check.