The EVSE DirectorySubscribe

Ingenico / payment

Field hub — common codes, ownership boundaries, and links into the fault database.

Ingenico — field brand hub (payment / PED)

Ingenico (and similar) PED tickets are money-path problems. FreeVend or RFID may still start sessions while cards fail. Always split Authorize / PED / host from energy / contactors / ISO. Do not RMA a power module because the terminal timed out.

When this OEM shows up / ownership

Payment ops / merchant owns: Host config, MID, decline rules, key injection, firmware profiles.

EVSE tech owns: Prove FreeVend/RFID vs card; reseat power/data to PED; known-good PED swap; capture Authorize timeline; keep PCI handling clean.

Network owns: Firewall/DNS/TLS to host; VLAN for PED.

Guide: /guides/metering-payment · /learn/evse-levels-and-tickets.

How faults typically present

PED / HMI

  • Timeout / unable to process / reader error (PAY-*).
  • Dark PED, reboot loop, wet chip slot, flaky NFC.

OCPP / EVSE

  • Authorize never arrives or IdTag timeout; energy path Ready or FreeVend OK.
  • ReaderFailure after firmware—re-pair PED before module crates (/guides/ocpp-faulted-triage).

Physical cues

  • Loose USB-C, water in hood, cracked NFC antenna area, recent PED firmware, sun-heated terminal.

Ranked common failure patterns

  1. Payment terminal timeout — Host path or PED reboot mid-auth. Free sample: /entries/ingenico-pay-to-payment-terminal-timeout.

  2. Chip read fail wet weather — Moisture/contamination in slot; dry and inspect before board. /entries/ingenico-pay-chip-chip-read-fail-wet-weather.

  3. Host authorize decline loop — Merchant/host rules, not EVSE HV. /entries/ingenico-pay-host-host-authorize-decline-loop. Related: /entries/protocol-ocpp-f03-authorize-rejected-invalid-idtag.

  4. USB-C power to PED unstable — Soft reboot mid-tap. /entries/ingenico-pay-usb-usb-c-power-to-ped-unstable.

  5. NFC tap intermittent — Antenna/alignment/EMI; prove chip path separately. /entries/ingenico-pay-nfc-nfc-tap-intermittent.

Log sources / tools

SourceWhat you pull
PED menu / hostResponse codes, reboot log, firmware
OCPPAuthorize timeline vs StartTransaction
FreeVend / RFID testEnergy-path prove
USB power checkStable 5V / cable integrity

Field checklist (first 15 minutes)

  1. FreeVend or RFID start while card fails? → money path.
  2. Photo PED screen + EVSE Ready state.
  3. Timeout vs decline vs chip vs NFC vs power—name one.
  4. Reseat power/data; known-good PED if available.
  5. Check host reachability before EVSE LOTO.
  6. PCI: no test PANs left on site; handle PED swaps per policy.
  7. Do not open HV for PED-only.

When to escalate

Payment host / merchant — Decline storms, MID config, keys.

Network — Firewall to host, DNS/TLS.

OEM PED — Confirmed hardware after power/host proven.

EVSE OEM — Only if energy path also fails with protective codes.

Worked examples

A — Cards timeout; FreeVend works; modules cool. PAY-TO / host—leave contactors closed.

B — Chip fails in rain; NFC sometimes works. Dry slot; PAY-CHIP before PED condemn.

C — PED reboots when customer taps. USB-C power path.

False friends

Looks likeOften actually
Dead chargerPED timeout / host decline
Bad RFID boardPED power reboot
Needs power moduleAuthorize never sent
Random FaultedReaderFailure after FW—re-pair PED

Ticket hygiene

Capture Authorize timestamps, PED firmware, FreeVend prove, and scrub cardholder data. Prefer /request with scrubbed PED photo when the code is missing.

/help · /guides/metering-payment · brand hubs for the EVSE that mounts the PED (e.g. /brands/chargepoint)

Money vs energy (drill)

If FreeVend works and cards fail, you are done with HV for this ticket. If neither works and StatusNotification is GroundFailure, you are not on a PED ticket. If Authorize is Invalid for one card and others work, chase the account—not the gun. If the PED reboots on every tap, chase USB-C power before host config. Write the prove steps in the closeout so the next tech does not reopen the cabinet.

Host decline vs timeout vs hardware

Decline loops return host codes—call merchant support with the code, not EVSE OEM. Timeouts with PED reboot logs point at power/data. Timeouts with stable PED and no host reachability point at network. Chip wet-weather fails that clear when dry are environmental—replace seals/hood before boards. NFC intermittents with solid chip reads are antenna/EMI—don’t replace the whole EVSE for NFC. After any PED FW update, re-pair and run a known-good test card per site PCI rules. Mounting PED on a vibrating dispenser door can look like “random timeouts”—check mechanical strain on USB-C. Browse Ingenico entries below or database. Cross-link the EVSE brand hub that mounts the PED when the money path and energy path both appear in one ticket—keep them as two branches in the write-up.

Closeout template

“Energy path: FreeVend/RFID [pass/fail]. Money path: chip/NFC/host [result + code]. PED power: [stable/rebooting]. Host reachability: [ok/fail]. Next owner: [payment/network/OEM PED]. HV opened: no.” That closeout stops the next shift from tearing into contactors for a decline loop. Prefer one clear money-path branch; never merge PED timeouts into an isolation RMA narrative on the same work order.

Models

Fault index (5)