Source en image uniquement.
Le journal des modifications officiel de STET est publié sous forme de PDF en image uniquement ; le texte ci-dessous n'est donc pas recherchable dans le document source. Nous reproduisons ici la page matricielle à titre de référence, jusqu'à ce que STET publie une révision au format texte.
STET PSD2 API — Changelog
| id | source | résumé | |
|---|---|---|---|
| 1 | BNPParibas/Mercatel | Allow a TPP to suggest a SCA execution or a SCA exemption through the API | |
| 93 | HSBC | Client Credential OAUTH2 TOKEN for PIISP | |
| 148 | CASA | Allow the use of the payment-request also for payment on behalf of the ordering party | |
| 158 | CNPS | Implementation of access (Read-Only) to the list of trusted beneficiaries | |
| 159 | CNPS | Payment request with no immediate execution of an instruction | |
| 160 | CNPS | Recurrent payments handling | |
| 161 | CNPS | Payment initiation with multiple instructions | |
| 164 | API EG | Implement mixed consent management model for AISP | |
| 174 | BudgetInsight | Suggest a standardisation on how to retrieve the public key for HTTP Signature | |
| 178 | BNPP | Adding an HTTP header for mobile identification | |
| 179 | CNPS | Forward Information about the beneficiary registered as trusted or not to the PISP | |
| 180 | CNPS | Forward Information about the availability of funds to the PISP | |
| 181 | CNPS | Removal of FULL ASPSP (B2) consent model | |
| 182 | CNPS | Cancellation of payment requests | |
| 184 | GTM | Removal of transfer-requests resource | |
| 185 | STET | Add CARD account payment Type | |
| 187 | SG | Lifetime of the "Authorization Code" or "Resource Owner Password" OAUTH2 token for PIISP | |
| 188 | GTT | Externalize common HTTP return codes | |
| 189 | BNPP | Add a payload to each HTTP return code | |
| 190 | CASA | Set [_links] and [resourceId] fields as optional in [AccountResource] structure | |
| 191 | CDC | Set a Max value for [numberOfTransactions] field | |
| 194 | GTT | Merge "payment-requests" and "periodic-payment-requests" API entry-points | |
| 195 | GTT | Use a PUT entry-point in order to implement cancellation of payments | |
| 196 | LBP/SG | Additional information for international payments | |
| 197 | CNPS | Add connected PSU's last name et first name | |
| 198 | CNPS | Allow the PISP to suggest the insertion the beneficiary of the payment within the trusted beneficiaries list | |
| 199 | GTM | Apply HTTP signature on response sent by ASPSP | |
| 200 | HSBC | Unclarity about the forwarding of the PSU username on REDIRECT approach | |
| 201 | HSBC | Suggest a modification of the Authorization Code OAUTH2 grant | |
| 202 | LUXHUB | Add a precision about the absence ou invalidity of http signature | |
| 203 | API WORKSHOP | Detail the MTLS mechanism | |
| 204 | ARKEA | Clarify how to use the data for payment, transfer and standing orders | |
| 205 | CDC | Add a transactionDate | |
| 208 | LINXO | Alignment of ASPSP definition on PSD2 | |
| 209 | STET | Clarify the title of § 3.8 "Specific HTTP messages to be used" | |
| 211 | SWIFT | Add a value date for transactions | |
| 212 | SWIFT | Make GenericIdentification/Issuer optional | |
| 218 | SG | Change on ServiceLevel field (Removal of NURG value) |
| id | source | résumé | |
|---|---|---|---|
| 220 | SG | Extend the length of the remittance information | |
| 222 | CGI | Clarify that AISP and PIISP roles should be handled through separate OAUTH2 tokens | |
| 226 | BNPP-Fortis | Add a currency code in order to specify a multicurrency account | |
| 228 | FIME | Check the value of the HAL links when answering a payment request confirmation (documentation) | |
| 230 | CGI | Clarify the behaviour about communicating the PSU identity (GDPR issue) | |
| 231 | CGI | Set "isTrusted" field as readOnly after EBA answers on registration of a new trusted beneficiary | |
| 232 | FIS | Avoid "Donnor of order" (Documentation) | |
| 233 | Orange Bank | Set the cardinality of "acceptedAuthenticationApproach" to 1 at least | |
| 234 | STET | Replace PIISP by CBPII (Card Based Payment Instrument Issuers) | |
| 235 | FIME | Fix the definition of QTSP (Documentation) | |
| 236 | FIME | Inconsistency in HTTP in case of expired tokens (documentation) | |
| 237 | FIME | Eliminate duplicate documentation | |
| 238 | FIME | Wrong date format (documentation examples) | |
| 239 | BNPP | Fix the description of HTTP signature header (documentation) | |
| 240 | BNPP | Add HTTP501 as possible return code for PUT /consents | |
| 241 | BNPP | Add HTTP501 as possible return code for GET /trusted-beneficiaries | |
| 245 | CMCIC | Remaining examples with Paymentreport (Documentation) | |
| 249 | LCL | Specify which headers should be taken into account or excluded from the HTTP signature | |
| 250 | ARKEA | Clarify the possibility or not of having multiple beneficiaries and multiple execution dates in the same payment request | |
| 251 | Workshop TPP | Clarify how to specify the list of usable schemes | |
| 252 | STET | Fix "Must be values with "Bearer"" (Documentation) | |
| 254 | Workshop TPP | Fix the definition of "EndToEndId" property (Documentation) |