How do I set up a fuel payment system for EMV transactions at the pump and in-store checkout?

Setting up a fuel payment system for EMV transactions at the pump and in-store usually means building a payment flow that supports:

• Card-present EMV chip
• Contactless tap
• Fallback magstripe only if allowed by your risk policy
• Offline/stand-in handling
• Fuel preauthorization/capture logic
• Separate flows for pump and cashier POS

Here’s a practical implementation roadmap.

---

1) Define the two payment environments

A. Pay-at-the-pump

This is usually the more complex flow because the final fuel amount is unknown when the customer starts.

Typical flow:

1. Customer inserts card/taps at dispenser.
2. Pump terminal sends an EMV authorization request for a preauth amount.
3. Issuer approves or declines.
4. Fuel is dispensed.
5. Final amount is captured/cleared after fueling completes.

B. In-store checkout

This is a normal card-present retail transaction:

1. Customer presents card at POS.
2. POS requests authorization for the exact sale amount.
3. Approval/decline.
4. Capture/settlement follows standard card-present rules.

---

2) Choose the right payment stack

You generally need:

• EMV-certified payment terminals for pump and store
• A payment gateway/processor that supports:
  • card-present EMV
  • fuel merchant category handling
  • partial approvals
  • incremental auths or completion/capture
  • tokenization
• A POS/Pump controller integration
• A merchant account configured for fuel retail

If you’re using a third-party processor, confirm they support:

• card-present EMV at unattended terminals
• fuel dispenser transactions
• preauth + completion
• contactless at unattended/kiosk terminals
• reversals and timeouts properly

---

3) Get the hardware right

For the pump

You’ll need:

• EMV-capable dispenser reader
• Contactless reader (if supported)
• PIN pad if debit PIN is required
• Secure communications path to your payment host
• Fuel controller integration for start/stop and amount finalization

Important:

• The device must be certified for unattended EMV
• It must support consumer device cardholder verification methods as applicable
• Ensure environmental ratings for outdoor use

For the store

You’ll need:

• EMV card reader/PIN pad for attended checkout
• Contactless reader
• POS software integrated to your processor/gateway
• Receipt printer and settlement reporting

---

4) Configure the fuel transaction logic

Fuel transactions are different from regular retail because the amount is not known at card-presentment time.

Common pump authorization model

1. Preauthorization
   • Authorize an estimated amount, often a fixed ceiling or pump-configured limit.
   • Example: $100, $125, or a station-defined amount.
2. Dispense fuel
3. Completion / capture
   • Capture the actual amount dispensed.
4. Reversal of unused hold
   • If the final sale is lower than the preauth, reverse the difference where supported.

Key things to support

• Partial approvals: If cardholder’s available funds are less than the hold amount
• Auto-reversal: Release excess hold after final amount
• Timeouts: If customer walks away or fueling doesn’t start
• Offline behavior: Decide whether to decline offline or allow limited offline risk

---

5) Integrate EMV kernel and certification

To accept EMV, your terminal software needs an EMV kernel and must pass certification with your processor/acquirer.

You’ll usually need:

• EMV Level 1 hardware certification
• EMV Level 2 kernel certification
• PCI PTS certified devices
• PCI DSS compliance for your environment
• Processor/acquirer certification for:
  • authorization messages
  • completion messages
  • reversals
  • contactless rules
  • unattended fuel flows

If you’re using an integrated vendor, ask whether their solution is already certified for:

• Unattended fuel
• EMV contactless
• Debit PIN
• Force sale/stand-in handling
• Preauth/completion
• International card support if needed

---

6) Define the transaction message flow

Pump authorization example

• Card inserted/tapped
• Terminal reads EMV data and performs CVM
• Terminal sends auth request with:
  • merchant ID
  • terminal ID
  • fuel indicators
  • preauth amount
  • EMV data elements
• Issuer approves $100 hold
• Dispensing begins
• Final amount = $67.42
• Completion/capture submitted for $67.42
• Reversal for remaining $32.58, if supported

Store checkout example

• Card inserted/tapped
• POS sends exact sale amount
• Issuer approves/declines
• Sale captured in settlement

---

7) Handle edge cases

You should plan for:

• Declined preauth
• Card removed early
• Pump authorization approved but no fuel dispensed
• Fueling interrupted
• Partial approval
• Card network timeouts
• Network outages
• Chargeback/dispute handling
• Receipt and settlement reconciliation

For pumps, make sure the UI clearly tells the customer:

• approved amount
• fueling start
• stop conditions
• if another card is required

---

8) Security and compliance requirements

At minimum, you’ll need to address:

• PCI DSS
• PCI PTS terminal compliance
• EMVCo certified devices
• Point-to-point encryption (P2PE) if possible
• Tokenization for stored card data
• Secure key management
• Restricted access to admin and settlement systems

If you store loyalty or fleet data alongside payment data, keep those systems segregated where possible.

---

9) Work with your acquirer/processor on fuel-specific settings

Tell your processor you are:

• a fuel merchant
• supporting unattended EMV at the pump
• supporting in-store EMV POS
• needing preauth completion and reversal handling

Ask them to configure:

• merchant category code / fuel settings
• floor limits
• preauth amounts
• stand-in authorization rules
• partial approval support
• contactless rules
• debit/credit routing
• settlement batch rules

---

10) Test the full end-to-end journey

Before going live, test:

Pump tests

• chip insert approve/decline
• tap approve/decline
• debit PIN
• partial approval
• no-fuel after auth
• fueling over/under auth amount
• reversal behavior
• communication failure recovery

Store tests

• chip and tap for exact sale amount
• voids
• refunds
• tips if applicable
• offline/backup procedure

Also validate settlement reports and reconciliation between:

• dispenser logs
• POS logs
• gateway logs
• acquirer batch reports

---

11) Recommended implementation approach

If you’re starting from scratch, the easiest path is usually:

1. Pick a processor/gateway that supports fuel
2. Choose certified unattended pump hardware
3. Use a POS vendor with EMV/fuel integration
4. Implement preauth/completion logic
5. Run certification with processor and networks
6. Test exception handling thoroughly
7. Go live with monitoring and settlement reconciliation

---

12) Simple architecture

Pump side

• EMV reader + contactless + PIN pad
• Pump controller
• Fuel POS controller / middleware
• Payment gateway/processor
• Acquirer/issuer

Store side

• EMV POS terminal
• POS software
• Payment gateway/processor
• Acquirer/issuer

---

If you want, I can also give you:

1. a sample transaction flow diagram,
2. a checklist for processor/vendor selection, or
3. a technical integration spec for pump preauth/completion messages.