Skip to main content
Authorize a payment immediately but delay the capture, giving your team a fraud review window before funds are settled by your . The order stays in authorized status until FunnelFox Payments captures it and moves it to settled. A cancellation before capture costs nothing, while a capture followed by a refund is a real money movement. and payments use separate delay settings.
Purchases, subscriptions, and outbound webhooks fire at authorization, not at capture. Customers get access immediately, and only the money settles later.

​
Setup

  1. Configure the delayed_capture on the Settings page of your FunnelFox Payments dashboard. The delay is , and a change . delayed_capture is a JSON field. Paste the whole matrix into it and click Save.
    There is no partial fall-through inside the JSON. A Visa CIT entry that does not list your PSP goes straight to the cit fallback.A null fallback captures on the next run. To turn the hold off everywhere, set {"networks": {}, "fallback": {"cit": null, "mit": null}}.A fallback that sets only cit leaves mit as null, so renewals capture immediately. Always write both keys.An authorization expires if it is held too long, so every delay is capped. FunnelFox Payments rejects a value above its cap when you save.Both fallbacks are capped at 47 hours. An order with an unknown network or PSP could be on the strictest acquirer, so the tightest cap applies.
  1. Go to the Workflows page in your Primer dashboard.
  2. Open your workflow.
  1. Click Edit workflow at the top right.
  1. Select the Authorize payment stage and set Before processing the next workflow block to Continue payment flow.
  1. Click Save.

​
Capture behavior

A capture is attempted at most twice, after which the payment is blocked for 12 hours. Orders older than 480 hours (20 days) are no longer picked up and the authorization is treated as dead. You can also capture an authorized order manually at any time, which ignores the configured delay.

​
Next steps