OPT-PIS-003Bank's choiceregulatedinconsistencyPayment initiation

Payment request types

Which types of payment request does the bank accept?

The options

  • Single transfer

    One instruction, one beneficiary.

  • Several beneficiaries

    On the same execution date.

  • Several dates

    For the same beneficiary.

  • Standing order

    One instruction, one beneficiary, one frequency.

Bank side
Each implementation must say which cases it supports. Several beneficiaries and several dates at once is technically allowed, but the spec sees little point in it.
TPP side
Check the supported cases bank by bank before offering a flow.
Regulation

If the bank offers bulk, future-dated or recurring payments directly, it must allow them through a PISP (the EBA's 2018 Opinion, §29, Q&A 2021_6318 and 2021_6236).

Texts cited

Spec inconsistency
The text places the execution date and the beneficiary at payment level, the schema only at instruction level. 1.6.2 gave placement rules that 1.6.3 removed without a CR.

Entry checked on October 19, 2026.

Based on the STET PSD2 API 1.6.3 specification, licensed CC BY 3.0 FR.

The entry as stored
{
  "id": "OPT-PIS-003",
  "edition": "1.6.3",
  "chooser": "aspsp",
  "title": {
    "fr": "Types de demandes de paiement",
    "en": "Payment request types",
    "es": "Tipos de solicitudes de pago",
    "pt-br": "Tipos de solicitação de pagamento"
  },
  "question": {
    "fr": "Quels types de demandes de paiement la banque accepte-t-elle ?",
    "en": "Which types of payment request does the bank accept?",
    "es": "¿Qué tipos de solicitudes de pago acepta el banco?",
    "pt-br": "Quais tipos de solicitação de pagamento o banco aceita?"
  },
  "options": [
    {
      "label": {
        "fr": "Virement unique",
        "en": "Single transfer",
        "es": "Transferencia única",
        "pt-br": "Transferência única"
      },
      "text": {
        "fr": "Une instruction, un bénéficiaire.",
        "en": "One instruction, one beneficiary.",
        "es": "Una instrucción, un beneficiario.",
        "pt-br": "Uma instrução, um beneficiário."
      }
    },
    {
      "label": {
        "fr": "Plusieurs bénéficiaires",
        "en": "Several beneficiaries",
        "es": "Varios beneficiarios",
        "pt-br": "Vários beneficiários"
      },
      "text": {
        "fr": "À la même date d'exécution.",
        "en": "On the same execution date.",
        "es": "Con la misma fecha de ejecución.",
        "pt-br": "Na mesma data de execução."
      }
    },
    {
      "label": {
        "fr": "Plusieurs dates",
        "en": "Several dates",
        "es": "Varias fechas",
        "pt-br": "Várias datas"
      },
      "text": {
        "fr": "Pour le même bénéficiaire.",
        "en": "For the same beneficiary.",
        "es": "Para el mismo beneficiario.",
        "pt-br": "Para o mesmo beneficiário."
      }
    },
    {
      "label": {
        "fr": "Ordre permanent",
        "en": "Standing order",
        "es": "Orden permanente",
        "pt-br": "Ordem permanente"
      },
      "text": {
        "fr": "Une instruction, un bénéficiaire, une fréquence.",
        "en": "One instruction, one beneficiary, one frequency.",
        "es": "Una instrucción, un beneficiario, una frecuencia.",
        "pt-br": "Uma instrução, um beneficiário, uma frequência."
      }
    }
  ],
  "stet": {
    "sections": [
      {
        "part": "framework",
        "section": "2.2.5",
        "page": 15
      },
      {
        "part": "functional-model",
        "section": "4.12.1.1",
        "page": 56
      }
    ],
    "openapi": [
      "POST /payment-requests"
    ],
    "flows": [
      "8-1-payment-request-with-multiple-instructions-having-different-execution-dates",
      "8-2-payment-request-with-multiple-instructions-having-different-beneficiaries",
      "8-3-standing-orders-request"
    ],
    "changes": [],
    "remark": null
  },
  "aspsp": {
    "fr": "Chaque implémentation doit dire quels cas elle supporte. Plusieurs bénéficiaires et plusieurs dates à la fois est permis techniquement, mais la spec le juge peu pertinent.",
    "en": "Each implementation must say which cases it supports. Several beneficiaries and several dates at once is technically allowed, but the spec sees little point in it.",
    "es": "Cada implementación debe indicar qué casos soporta. Combinar varios beneficiarios y varias fechas está permitido técnicamente, pero la especificación lo considera poco pertinente.",
    "pt-br": "Cada implementação deve dizer quais casos suporta. Vários beneficiários e várias datas ao mesmo tempo é tecnicamente permitido, mas a especificação considera isso pouco pertinente."
  },
  "tpp": {
    "fr": "Vérifier les cas supportés banque par banque avant de proposer un parcours.",
    "en": "Check the supported cases bank by bank before offering a flow.",
    "es": "Comprobar los casos soportados banco por banco antes de ofrecer un flujo.",
    "pt-br": "Verificar os casos suportados banco a banco antes de oferecer um fluxo."
  },
  "regulation": {
    "text": {
      "fr": "Si la banque propose en direct les paiements groupés, différés ou récurrents, elle doit les permettre via un PISP (avis EBA de 2018, §29, Q&A 2021_6318 et 2021_6236).",
      "en": "If the bank offers bulk, future-dated or recurring payments directly, it must allow them through a PISP (the EBA's 2018 Opinion, §29, Q&A 2021_6318 and 2021_6236).",
      "es": "Si el banco ofrece en acceso directo los pagos agrupados, diferidos o recurrentes, debe permitirlos a través de un PISP (dictamen de la EBA de 2018, §29, Q&A 2021_6318 y 2021_6236).",
      "pt-br": "Se o banco oferece em acesso direto pagamentos em lote, agendados ou recorrentes, deve permiti-los via PISP (parecer da EBA de 2018, §29, Q&A 2021_6318 e 2021_6236)."
    },
    "sources": [
      {
        "act": "eba-opinion-2018",
        "ref": "§29"
      },
      {
        "act": "eba-qa",
        "ref": "2021_6236"
      },
      {
        "act": "eba-qa",
        "ref": "2021_6318"
      }
    ]
  },
  "note": {
    "fr": "Le texte place la date d'exécution et le bénéficiaire au niveau du paiement, le schéma seulement au niveau de l'instruction. La 1.6.2 donnait des règles de placement que la 1.6.3 a retirées sans CR.",
    "en": "The text places the execution date and the beneficiary at payment level, the schema only at instruction level. 1.6.2 gave placement rules that 1.6.3 removed without a CR.",
    "es": "El texto sitúa la fecha de ejecución y el beneficiario a nivel del pago, y el esquema solo a nivel de la instrucción. La 1.6.2 daba reglas de ubicación que la 1.6.3 retiró sin CR.",
    "pt-br": "O texto coloca a data de execução e o beneficiário no nível do pagamento, e o schema só no nível da instrução. A 1.6.2 dava regras de posicionamento que a 1.6.3 retirou sem CR."
  },
  "production": null,
  "verifiedAt": "2026-10-19"
}