<!-- headlesslaw {"release":{"id":"a4f2a0495fe55b47323883f82977a9b34ab66171ec9623e39925d3a7045b6c81","published":"2026-11-01T16:41:30Z","pinned":false},"limits":{"coverage":{"history":"current_only","held_since":"2018-10-26","gaps":[],"covered":["EBA Q&A 2018_4049 — Q&A — Persistent authentication for wearable devices [Final Q&A] L3"],"not_covered":["national guidance","court decisions"]},"freshness":{"release_id":"a4f2a0495fe55b47323883f82977a9b34ab66171ec9623e39925d3a7045b6c81","release_published":"2026-11-01T16:41:30Z","checked_at":"2026-10-26","checked_against":"the EBA publication"},"truncation":null,"failures":[],"incomplete":[]},"page":{"path":"/psd2/level-3/q-and-a/eba/eba-qa-2018-4049-persistent-authentication-for-wearable-devices","url":"https://www.headlesslaw.com/psd2/level-3/q-and-a/eba/eba-qa-2018-4049-persistent-authentication-for-wearable-devices","title":"EBA Q&A 2018_4049 — Q&A — Persistent authentication for wearable devices [Final Q&A]","family":"l3","work_id":"spaces/psd2/level-3/q-and-a/eba/eba-qa-2018-4049-persistent-authentication-for-wearable-devices","status":"final q&a","force_status":null,"date_state":"current","requested_date":null,"as_of":"2026-11-02","applies_from":null,"application":null,"version_label":"EBA Q&A register, 26 October 2018","check":{"against":"the EBA publication","on":"2026-10-26"},"check_result":"matched","official_url":"https://www.eba.europa.eu/single-rule-book-qa/qna/view/publicId/2018_4049","valid_from":"0001-01-01","valid_until":null,"revision":1,"content_id":"1d12e9ee0f2ac7b2","change_date":null,"nearest_versions":["2018-10-26"],"first_text_date":null,"correction_applies":false,"versions":["2018-10-26"],"version_url":"https://www.headlesslaw.com/psd2/level-3/q-and-a/eba/eba-qa-2018-4049-persistent-authentication-for-wearable-devices/versions/2018-10-26","revision_url":"https://www.headlesslaw.com/psd2/level-3/q-and-a/eba/eba-qa-2018-4049-persistent-authentication-for-wearable-devices/versions/2018-10-26/rev/1d12e9ee0f2ac7b2","versions_url":"https://www.headlesslaw.com/psd2/level-3/q-and-a/eba/eba-qa-2018-4049-persistent-authentication-for-wearable-devices/versions","relations_url":"https://www.headlesslaw.com/psd2/level-3/q-and-a/eba/eba-qa-2018-4049-persistent-authentication-for-wearable-devices/relations","source_line":"Answer by the EBA, published in its Q&A tool · not legislation · published 26 Oct 2018 [Final Q&A]","attribution":{"prepared_by":"EBA","published_by":"EBA","published_in":"EBA Single Rulebook Q&A tool","document_type":"qa_answer","legal_nature":"not_legislation","addressees":"not stated in the document","dates":{"published_on":"2018-10-26","question_submitted_on":"2018-06-28","locators":{"published_on":"EBA Q&A register entry 2018_4049, field 'Final publishing date'","question_submitted_on":"EBA Q&A register entry 2018_4049, field 'Submission date'"}},"adoption":null}}} -->
---
title: "EBA Q&A 2018_4049 — Q&A — Persistent authentication for wearable devices [Final Q&A]"
shortTitle: "EBA Q&A 2018_4049 — Q&A — Persistent authentication for wearable devices [Final Q&A]"
answer_id: EBA_QA_2018_4049
status: "Final Q&A"
type: qa
instrument_type: qa
authority: EBA
binding: false
binding_character: non_binding
legal_status: in_force
regulation: "PSD2"
psd2_level3: true
mica_level2: false
legal_basis: "Article 97 PSD2"
date: 26 October 2018
source_link: https://www.eba.europa.eu/single-rule-book-qa/qna/view/publicId/2018_4049
lifecycle: "Final Q&A"
text_version: "EBA Q&A register, 26 October 2018"
source_url: "https://www.eba.europa.eu/single-rule-book-qa/qna/view/publicId/2018_4049"
check_status: matched
verified: true
last_checked: 2026-10-26
checked_against: "the EBA publication"
source:
  prepared_by: "EBA"
  published_by: "EBA"
  published_in: "EBA Single Rulebook Q&A tool"
  evidence:
    prepared_by: "Answer prepared by the EBA."
    locator: "EBA Q&A register entry 2018_4049, field 'Answer prepared by'"
document_type: "qa_answer"
legal_nature: "not_legislation"
addressees: "not stated in the document"
dates:
  published_on: "2018-10-26"
  question_submitted_on: "2018-06-28"
  locators:
    published_on: "EBA Q&A register entry 2018_4049, field 'Final publishing date'"
    question_submitted_on: "EBA Q&A register entry 2018_4049, field 'Submission date'"
lifecycle_label: "Final Q&A"
---

**Answer by the EBA, published in its Q&A tool · not legislation · published 26 Oct 2018 [Final Q&A]**

*Final Q&A · EBA Q&A register, 26 October 2018 · Checked against the EBA publication on 26 Oct 2026 · [Official source](https://www.eba.europa.eu/single-rule-book-qa/qna/view/publicId/2018_4049)*

| | |
|---|---|
| **Full title** | EBA Q&A 2018_4049 — Q&A — Persistent authentication for wearable devices \[Final Q&A\] |
| **Prepared by** | EBA |
| **Published by** | EBA, in the EBA Single Rulebook Q&A tool |
| **Reference** | EBA_QA_2018_4049 |
| **Document type** | Q&A |
| **Legal nature** | Not legislation |
| **Addressees** | Not stated in the document |
| **Dates** | Published 26 October 2018; question submitted 28 June 2018 |
| **Legal basis** | Article 97 PSD2 |
| **Related instruments** | None recorded |
| **Text on this page** | Word for word — the full text of the EBA publication |

**Persistent authentication for wearable devices**

### Question

Is persistent authentication for wearable devices compliant with the RTS?

### Background

New payment solutions can entail the use of wearable devices with payment capabilities (e.g. smartwatches and wristbands). A card can be registered in a wearable device so that the device can be used to pay. This makes the device (or the tokenized card registered in the device) an ownership factor (“something only the user possesses”).

Some devices have a screen and keyboard and can support for example PIN entry. In addition, for other devices the PIN may be entered on the POS terminal.

Other devices can continuously monitor and identify users through locking mechanisms that ensure that the user is continuously wearing the device. This is the so-called ‘persistent authentication’. For example, persistent authentication occurs when the device continuously monitors the cardholder is wearing the device through measuring the heartbeat. These devices authenticate through an ownership factor (the tokenized card registered in the device) and another factor (e.g. biometrics).

Additional security features may be implemented. For example, persistent authentication terminates (i) whenever wearable is detected ‘off-body’ and this ‘off-body’ detection must occur within 3 seconds, or (ii) after 24 hours of continuous use (‘time-out’).

Absent any clarification on persistent authentication in the PSD2 and in the RTS, we believe that persistent authentication for wearable devices is compliant with the RTS insofar as the registration of the card in the device is done in compliance with the RTS SCA requirements. In particular, the card must be securely associated with the wearable device through SCA by the issuer.

***

### Answer

PSD2 and the Commission Delegated Regulation (EU) 2018/389 (RTS on Strong customer authentication and secure communication) do not define ‘persistent authentication’.

Article 97 of PSD2 requires payment service providers to apply strong customer authentication (SCA) for all electronic transactions or log-in to an electronic account. Article 4(30) of PSD2 defines SCA as “an authentication based on the use of two or more elements categorised as knowledge (something only the user knows), possession (something only the user possesses) and inherence (something the user is) that are independent”. Articles 4 to 9 of the Delegated Regulation provide further detail on these two elements as well as the application of dynamic linking, where applicable. Article 22 of this Delegated Regulation details requirements on ensuring the confidentiality and integrity of the payment service user’s personalised security credentials, including authentication codes, during all phases of authentication.

The submitter suggests that some devices can continuously monitor and identify users through mechanisms that ensure that the user is continuously wearing the device (e.g. through measuring the heartbeat). Such an authentication would need to meet the legal requirements listed above.

With regard to ‘possession’, according to paragraph 35 of the EBA Opinion on the implementation of the RTS on SCA and secure communication “for a device to be considered possession, there needs to be a reliable means to confirm possession through the generation or receipt of a dynamic validation element on the device”. This leads to a unique SCA attempt for every situation, where SCA needs to be applied.

Finally, in situations where exemptions apply, such as under the contactless payments exemption under Article 11 of the Delegated Regulation, the requirement for SCA would not apply.

***

**Source:** [EBA original document](https://www.eba.europa.eu/single-rule-book-qa/qna/view/publicId/2018_4049)

## Related Level 1 articles

- [Article 97 — Authentication](../../../articles/97.md)
