<!-- headlesslaw {"release":{"id":"a4f2a0495fe55b47323883f82977a9b34ab66171ec9623e39925d3a7045b6c81","published":"2026-11-01T16:41:30Z","pinned":false},"limits":{"coverage":{"history":"current_only","held_since":"2019-12-20","gaps":[],"covered":["EBA Q&A 2018_4415 — Q&A — Dynamic linking for batch transactions [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-4415-dynamic-linking-for-batch-transactions","url":"https://www.headlesslaw.com/psd2/level-3/q-and-a/eba/eba-qa-2018-4415-dynamic-linking-for-batch-transactions","title":"EBA Q&A 2018_4415 — Q&A — Dynamic linking for batch transactions [Final Q&A]","family":"l3","work_id":"spaces/psd2/level-3/q-and-a/eba/eba-qa-2018-4415-dynamic-linking-for-batch-transactions","status":"final q&a","force_status":null,"date_state":"current","requested_date":null,"as_of":"2026-11-01","applies_from":null,"application":null,"version_label":"EBA Q&A register, 20 December 2019","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_4415","valid_from":"0001-01-01","valid_until":null,"revision":1,"content_id":"a127c69ea5ca60f3","change_date":null,"nearest_versions":["2019-12-20"],"first_text_date":null,"correction_applies":false,"versions":["2019-12-20"],"version_url":"https://www.headlesslaw.com/psd2/level-3/q-and-a/eba/eba-qa-2018-4415-dynamic-linking-for-batch-transactions/versions/2019-12-20","revision_url":"https://www.headlesslaw.com/psd2/level-3/q-and-a/eba/eba-qa-2018-4415-dynamic-linking-for-batch-transactions/versions/2019-12-20/rev/a127c69ea5ca60f3","versions_url":"https://www.headlesslaw.com/psd2/level-3/q-and-a/eba/eba-qa-2018-4415-dynamic-linking-for-batch-transactions/versions","relations_url":"https://www.headlesslaw.com/psd2/level-3/q-and-a/eba/eba-qa-2018-4415-dynamic-linking-for-batch-transactions/relations","source_line":"Answer by the EBA, published in its Q&A tool · not legislation · published 20 Dec 2019 [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":"2019-12-20","question_submitted_on":"2018-12-11","locators":{"published_on":"EBA Q&A register entry 2018_4415, field 'Final publishing date'","question_submitted_on":"EBA Q&A register entry 2018_4415, field 'Submission date'"}},"adoption":null}}} -->
---
title: "EBA Q&A 2018_4415 — Q&A — Dynamic linking for batch transactions [Final Q&A]"
shortTitle: "EBA Q&A 2018_4415 — Q&A — Dynamic linking for batch transactions [Final Q&A]"
answer_id: EBA_QA_2018_4415
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: 20 December 2019
source_link: https://www.eba.europa.eu/single-rule-book-qa/qna/view/publicId/2018_4415
lifecycle: "Final Q&A"
text_version: "EBA Q&A register, 20 December 2019"
source_url: "https://www.eba.europa.eu/single-rule-book-qa/qna/view/publicId/2018_4415"
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_4415, field 'Answer prepared by'"
document_type: "qa_answer"
legal_nature: "not_legislation"
addressees: "not stated in the document"
dates:
  published_on: "2019-12-20"
  question_submitted_on: "2018-12-11"
  locators:
    published_on: "EBA Q&A register entry 2018_4415, field 'Final publishing date'"
    question_submitted_on: "EBA Q&A register entry 2018_4415, field 'Submission date'"
lifecycle_label: "Final Q&A"
---

**Answer by the EBA, published in its Q&A tool · not legislation · published 20 Dec 2019 [Final Q&A]**

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

| | |
|---|---|
| **Full title** | EBA Q&A 2018_4415 — Q&A — Dynamic linking for batch transactions \[Final Q&A\] |
| **Prepared by** | EBA |
| **Published by** | EBA, in the EBA Single Rulebook Q&A tool |
| **Reference** | EBA_QA_2018_4415 |
| **Document type** | Q&A |
| **Legal nature** | Not legislation |
| **Addressees** | Not stated in the document |
| **Dates** | Published 20 December 2019; question submitted 11 December 2018 |
| **Legal basis** | Article 97 PSD2 |
| **Related instruments** | None recorded |
| **Text on this page** | Word for word — the full text of the EBA publication |

**Dynamic linking for batch transactions**

### Question

In relation to payment transactions for a batch of remote electronic payments to one or several payees, please clarify whether the payer needs to be made aware of every payee in the batch?

### Background

Paragraph 3b of Article 5 stipulates that, in relation to payment transactions for which the payer has given consent to execute a batch of remote electronic payment transactions to one or several payees, the authentication code shall be specific to the total amount of the batch of payment transactions and to the specified payees.

Paragraph 1 of Article 5 stipulates that payment service providers shall adopt security measures to ensure that the payer is made aware of the amount of the payment transaction and of the payee.

Batch transactions might consist of a large number payments, so that it is impractical for a payer to be made aware of every payee in the batch during the payment authentication process.

***

### Answer

Article 5(1)(a) of the Commission Delegated Regulation (EU) 2018/389 states that “where payment service providers apply strong customer authentication in accordance with Article 97(2) of Directive (EU) 2015/2366, in addition to the requirements of Article 4, they shall adopt security measures that meet”, among others, the following requirement: “a) the payer is made aware of the amount of the payment transaction and of the payee”. This means that the payer should be able to check the payees list, included in the batch of remote payment transactions, should the payer wish to do so.

Article 5(3)(b) of the Delegated Regulation, in turn, states that “in relation to payment transactions for which the payer has given consent to execute a batch of remote electronic payment transactions to one or several payees, the authentication code shall be specific to the total amount of the batch of payment transactions and to the specified payees”. As clarified in Q&A 2018\_4435, this means that the payment service provider should dynamically link the authentication code for a batch of remote electronic payment transactions to every single payee included in that batch.

Q&A 2019\_4556 provides further details on the identification of the payee and the generation of the authentication code.

***

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

## Related Level 1 articles

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