ZenotiHelp

Manage batch payments

ZTZenoti Docs Team Updated September 17, 2026 4 min readGuide

Batch payment processing handles high-volume payment operations including recurring collections, one-time charges, and ACH transfers. The system processes payments in batches to optimize throughput and manage processor rate limits.

Audience: Organization administrators and finance staff who monitor recurring payment collections and batch processing outcomes.

Before you begin

  • Batch processing runs automatically based on system schedules. No manual intervention is typically required.
  • Individual batch payments can be monitored through the payment dashboard.

Permission: Available to staff with payment-configuration permissions; specific security object under verification.

Steps

View batch payment progress

Batch payment progress is visible in the payment dashboard. You can:

  • View the overall batch status and completion percentage.
  • Drill into individual payments within a batch.
  • Identify failed payments that need attention.

Identify and respond to failed payments

When a payment fails, the system records the failure reason. Depending on your configuration, the system may automatically retry the payment or escalate it through the dunning process.

For recurring membership and package collections, failed payments follow the dunning rules configured for your organization. For membership billing configuration, see the Memberships category.

Monitor stale payments

Payments that remain in a non-terminal state for an extended period are automatically flagged and may be marked as failed to prevent indefinite processing.

What batch processing does

The batch payment system handles two primary scenarios:

  • Recurring collections — Batches of recurring payment requests for memberships, packages, and other subscription charges.
  • Non-recurring collections — Single payment operations processed in bulk.

The system creates a batch containing multiple payment requests, processes each payment through the configured processor, and tracks the batch to completion.

Batch lifecycle

Batches progress through the following states:

State Meaning
Created Batch has been created with payment requests queued for processing.
Active Batch is being processed. Payments are being sent to processors.
Dispatched All payments in the batch have been submitted to processors.
Completed All payments have reached a terminal state (success or failure).
Cancelled Batch was cancelled before completion.
Failed Batch encountered a system-level error.
Retry Batch is queued for a retry attempt after a transient failure.
Inactive Batch is paused and not currently being processed.
Picked Batch has been picked up by a processor consumer for handling.
Ready Batch is prepared and waiting to be picked up for processing.

The system checks batch status periodically and updates the batch state when all individual payments have reached a terminal state.

Individual payment statuses

Each payment within a batch has its own status:

Status Meaning
Initiated Payment request created, waiting for processing.
Pending Payment submitted to processor, awaiting response.
Processing Processor is actively processing the payment.
Success Payment completed successfully.
Failed Payment was rejected by the processor.
Cancelled Payment was cancelled before processing.
Refunded Payment was refunded after successful processing.
Chargeback Payment was reversed due to a dispute.
Unknown Payment status could not be determined; requires manual investigation.

Supported processors

Batch processing supports the following payment processors:

  • Adyen
  • Stripe
  • WorldPay
  • BBVA/Scotia (ACH batch processing)

Each processor has a dedicated processing path optimized for its specific requirements and rate limits.

Note: ACH payments follow a separate processing path from card-based batch payments. ACH batch collections are handled by a dedicated periodic task rather than the standard card-payment consumer path.

Tips

  • Monitor the payment dashboard regularly during peak recurring collection periods (for example, at the start of a billing cycle) to catch failed payments early and minimize dunning escalations.
  • When a batch shows a high proportion of Failed payments, check whether the issue is processor-wide (such as a network outage) or guest-specific (such as expired cards). Processor-wide issues typically resolve on retry; guest-specific failures require dunning follow-up.
  • For ACH collections, allow additional processing time compared to card-based batches. ACH transfers typically take 2–3 business days to settle, so a payment in Pending or Processing state does not necessarily indicate a problem.
  • If the system returns an HTTP 429 (too many requests) response during high-volume periods, the batch will be automatically retried by the system. No manual action is required; monitor the payment dashboard to confirm the batch progresses to Completed.

Troubleshooting

Batch remains in Active state for an extended period Check whether individual payments within the batch have reached terminal states. If payments are stuck in Pending or Processing, the processor may be experiencing delays. Contact your payment processor support if the state persists beyond the expected processing window.

Large number of Failed payments in a batch Verify that the processor is operational and that the payment methods on file for affected guests are current. Expired cards and closed bank accounts are the most common causes of batch failures. Use the dunning configuration to set up automatic retry schedules. For membership billing configuration, see the Memberships category.

ACH payment remains in Pending state longer than expected ACH transfers are subject to bank processing windows and typically take 2–3 business days. If a payment remains in Pending beyond 5 business days, verify the bank account details on file for the guest and contact your ACH processor for a status update.

Payment shows status Unknown An Unknown status indicates the system could not determine the final outcome from the processor response. Review the payment in the payment dashboard and, if the status does not resolve automatically within one business day, contact Zenoti Support with the batch reference for investigation.

Was this article helpful?
Your feedback helps us improve our documentation.