# OB-DB-007 — The TPP sends each consent to the ASPSP

> The TPP tells the ASPSP without undue delay about each new consent, with its name, the account, the purpose, the validity and the data categories, and the ASPSP shows only what the TPP sent it.

- Article: PSR 43(3b) (See also PSR 43(4))
- Who is bound: AISP, PISP, ASPSP
- Who it is for: API, Product
- Application: 21 months after entry into force, the general application date (Article 112).
- Level 2: RTS under Article PSR 89(1)(e), draft due at T + 12 months.
- Origin: New, with no equivalent in PSD2 or in the 2018 RTS.

Provisional numbering of the April 2026 compromise (Council doc. 8221/26). The final numbering will be added when the Official Journal publishes the text, without changing the id.

## STET 1.6.3: Partial

`PUT /consents` sends the accounts and data types, with no purpose, validity or date. Nothing exists for recurring PIS consents.

- <https://openfinanceguide.com/en/stet/1.6.3/endpoints/aisp/consents-put>
- <https://openfinanceguide.com/en/stet/1.6.3/flows/6-2-consent-forwarding>

## Sources

- [Council doc. 8221/26, page 260](https://data.consilium.europa.eu/doc/document/ST-8221-2026-INIT/en/pdf#page=260)

Checked on 2026-10-04. https://openfinanceguide.com/en/dsp3/obligations/ob-db-007