Implement Automated Fuel Dispenser (AFD) preset authorization and delayed capture for unattended gas station terminals
domain: payments-terminal · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
On transaction start, send a preset status-check/hold authorization (commonly up to $175 on Visa) rather than an open-ended amount, since an AFD can't know the final fuel volume upfront.
After fuel dispensing completes, send an authorization advice/completion message for the actual pumped amount within the required post-dispense window (about 60 minutes) rather than leaving the preset hold as final.
If using a true preauthorization (not just a status check), send the completion or a reversal within about 2 hours of receiving the approval response.
Clear/settle the final AFD transaction amount within the network's authorization-to-clearing window (around 2 calendar days for domestic AFD transactions), which is tighter than the multi-day windows allowed for other card-present merchant types.
Reverse any unused portion of the preset hold promptly once the actual sale amount is known, to avoid holding excess cardholder funds.
Reconcile the original preset-amount authorization against the final captured amount using the network's AFD-specific reporting fields before batch settlement.
Known gotchas
Treating an AFD hold like a normal retail open-to-buy authorization (settling days later) risks non-compliance, since AFD has its own tighter authorization-to-clearing windows.
Under-presetting the hold amount (e.g., $1) can cause a decline instead of the network-endorsed status-check flow designed to reserve a temporary buffer.
Forgetting to send the final actual-amount advice after dispensing leaves the cardholder charged only the preset hold or causes reconciliation breaks with the acquirer.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?