Invoice Auto-Capture

Set up automatic invoice payment capture

Where to find it: Admin → Payment V2 → Setup, and Admin → Add On Features

When you'd use this: When customers pay invoices with a pre-authorized card, and you want the charge and the ERP posting to happen without admin action.

What you need first:

• A payment processor in Pre Auth mode (Admin → Payment V2 → Setup)
• Enable Invoice Payment Auto-Capture turned on (Admin → Add On Features)
• An Authorisation Lifespan value on the processor

What it does:

Auto-capture charges the pre-authorized card at the gateway. Then it posts the payment document to your ERP. The two steps are independent. Each step can fail, and you can retry each one on its own.

Business Central and Sage X3 support automatic invoice payment capture.

The Authorisation Lifespan value drives the expiry warnings only. It does not change the real authorization window at the gateway. Set it to match the window that your gateway applies.

Gateway support:

Gateway	Auto-capture	Auto funds release	Notes
Bambora	Yes	No
Braintree	Yes	No
Fat Zebra	Yes	Yes	Manual release of the authorization is also available
Global Payments	Yes	No	Multiple captures are standard behavior. No setting is necessary
Paya Connect	Yes	No
Shift Finance	Yes	Yes
Stripe	Yes	No
Westpac PayWay	Yes	No

These gateways do not support automatic invoice payment capture: Fortis, iSolutions, PayPal Checkout, Spreedly, Versapay, and Windcave eCommerce.

Behavior to know:

• The platform captures one payment at a time for each invoice. Two attempts at the same time cannot charge the customer twice.
• If the authorized amount is less than the invoice total, the capture ends as Partially Captured. This state is final. You cannot retry the remaining amount.
• Automatic retries stop after 60 minutes by default. After that time, retry the capture from Payment Management.
• If the platform finds no matching webstore order inside the sync window, it marks the capture Abandoned. Then you must run the sync again and capture the payment again.

Troubleshooting:

• The capture shows Partially Captured — The authorization was for less than the invoice total. Collect the remaining amount as a new payment. You cannot retry the shortfall on the same authorization.
• The capture shows Abandoned — The platform found no matching webstore order inside the sync window. Run the sync again, then capture the payment again.
• A capture or an ERP posting failed — Retry it from Payment Management. For the full list of lanes, retries, and release steps, see Retry failed payment captures and invoice payments.

Automatic retry of failed invoice payment captures

Where to find it: Admin → Payment Management → Invoice Payments (the system handles retries automatically; you can also trigger manual retries for individual invoices)

When you'd use this: When an invoice payment capture succeeds at the payment gateway but fails to post to your ERP system. The platform automatically retries the ERP posting without re-charging the customer.

What you need first:

• Invoice payments enabled for your store
• ERP integration configured

How it works:

When a payment is successfully captured from the customer's card but fails to post to your ERP (for example, due to a temporary connection issue), the platform:

1. Marks the capture as retryable
2. Automatically attempts to repost the payment to your ERP at scheduled intervals
3. Only posts the payment record — never re-charges the customer's card
4. Continues retrying until the ERP accepts the posting or the retry limit is reached

Manual retry:

If you need to retry a failed posting immediately:

1. Go to Admin → Payment Management
2. Find the invoice with the failed capture
3. Click the retry option
4. The system reposts only the current payment to your ERP

Troubleshooting:

• Captured amount shown is higher than the actual charge — If an invoice number has been reused across different customers or time periods, the system now displays only the captured amount for the current customer's payment, not the sum of unrelated historical payments.

• Manual retry fails with "customer not found" or similar ERP error — The system now reposts only the payment record associated with the invoice's most recent transaction. If you see this error, verify that the customer account exists in your ERP and matches the current invoice.

• Automatic retry stops advancing after ERP rejects the posting — The system filters out stale payment records from prior transactions when an invoice number has been reused. Only the current customer's payment is retried. If retries have stopped, check that the payment record in Payment Management matches the customer and amount on the current invoice.