RRP test cards

What RRP protects against

In a relay attack, a fraudster places one device near the victim's card and another at a terminal somewhere else, then forwards the contactless exchange between the two. Because the card and terminal still exchange valid messages, the cryptograms alone can't expose the attack.

RRP checks timing instead. The terminal sends the card an Exchange Relay Resistance Data command carrying fresh random data. The card answers with its own random data and the timing it has declared for itself: minimum and maximum processing time, plus estimated transmission time. The terminal measures the real round trip and compares it with those declared limits and its own thresholds. A relayed exchange takes measurably longer, so it gets flagged in the terminal verification results.

Why you need dedicated cards

A standard test card either doesn't support RRP or answers with one fixed set of timings, so your terminal only ever sees the passing case. To show that the kernel measures time correctly, sets the right relay-resistance indicators and makes the right decision when limits are exceeded, you need cards that declare different timing parameters on purpose.

What's in an RRP set

• Multiple parameter profiles, each with different minimum/maximum processing time and estimated transmission time values
• Baseline profile: RRP performed and within limits, which confirms the measurement path end to end
• Time-limit and threshold cases: profiles meant to push the measured round trip outside the card's declared window, so you can verify the relay-resistance indicators in the TVR and the resulting decision
• RRP-not-supported card, to check the kernel falls back correctly when the card doesn't offer RRP
• Custom parameter values on request, matched to your terminal's thresholds or a specific test case

Best for

At a glance