Fuente solo en imagen.
El registro de cambios oficial de STET se publica como un PDF solo en imagen, por lo que el texto a continuación no es buscable en el documento de origen. Reproducimos aquí la página rasterizada como referencia hasta que STET publique una revisión en formato de texto.
STET PSD2 API — Changelog
| Sévérité | Catégorie | Source | Identifiant Résumé |
|---|---|---|---|
| majeur | AISP | CASA | 416 How to handle multiple PSU contexts |
| EBA | 378 Access to account owners identities | ||
| LUXHUB | 386 Restructure end-user identity structure | ||
| TRUSTLY | 13 Added information about overdraft on a given account. | ||
| General | BG | 360 Add contact details in postal address | |
| 391 Compliance with EU Regulation 2019/518 | |||
| PISP | 369 Remove unsafe REDIRECT authentication flow | ||
| GTT | 279 Avoid duplication of beneficiary and RequestedExecutionDate | ||
| mineur | AISP | LBP | 410 Unify the way to provide information about the account owner id |
| Linxo | 354 Fix the transaction status for allignment with balance status | ||
| LUXHUB | 428 Providing EndToEndId for AISP | ||
| STET | 442 Consent on overdrafts | ||
| TRUSTLY | 18 Adding MCC code (Merchant Category Code) for a given card transaction | ||
| General | CASA | 389 Add new id schemes for CARD ids | |
| CMCIC | 371 Increase resource id size up to 100 characters | ||
| 372 Allow underscore character in resource ids | |||
| MFB/LBP | 375 Set up a check for redirect_uri | ||
| STET | 66 Provide the TPP with information on SCA execution | ||
| 355 Add LEI as party identification | |||
| PISP | BNPP | 425 Allow the PISP to explain it accepts a possible change of payment method | |
| CASA | 412 Add new information datetime on Payment Request | ||
| CM AF | 414 Clarify how to handle standing orders history to a PISP | ||
| STET | 422 Is there a need to confirm a cancellation? | ||
| SWIFT | 362 Add UETR (Unique End-To-End Transaction Reference) | ||
| texte | AISP | Linxo | 398 Clarify the use of dateFrom/dateTo |
| 399 Reinforce documentation of the possible dates that can be valued for a given transaction | |||
| 401 Clarify the unicity of entryReference | |||
| 417 CLBD balance is irrelevant for card transactions account | |||
| 418 Harmonizing the way to provide the card Id in a card transaction account | |||
| 430 Specify how to handle fixed and variable parts of transaction detail | |||
| 444 How to provide balances on an account with no transaction | |||
| TFH | 433 How to handle a Payment card that is blocked | ||
| 434 How to handle payment card renewal | |||
| General | AFEPAME | 379 Include App2App mechanism in the documentation | |
| ARKEA | 247 Specify the behaviour in case of unsuccessfull authentication flow negociation | ||
| 409 Specify the precise SHA-2 algorithm to use in Key-ID | |||
| BNPP | 289 Alternate way to retrieve the public key for HTTP signature (RFC 7515) | ||
| 419 Clarification about implicit idempotency | |||
| BPCE | 381 set [content-length] header as optional in HTTP-SIGNATURE | ||
| 382 Fix the SHA-256 value of the Http-Signature keyId value in §3.5 | |||
| Budget Insig | 407 Should a new SCA imply the revocation of a refresh-token | ||
| IETF | 402 Update documentation about MTLS | ||
| MFB/LBP | 374 redirect_uri must not be required in the token request in any cases | ||
| STET | 359 OAUTH2 Technical Setup | ||
| TFH | 432 Ability to handle ISO8601 date/datetime formats | ||
| PIISP/CISP | STET | 63 Exchange Rate in case of a fund coverage check | |
| PISP | BPCE | 423 The documentation of the confirmation end-point is inconsistent | |
| CMAF | 431 Specify the significance of booking and FundsAvailability | ||
| LBP | 403 Clarification about the need of authentication during a payment request cancellation | ||
| 404 Rename Modification of a payment/transfer request | |||
| SG | 217 Indicate the limit time for cancellation of a payment |