Dear developers,
we are pleased to inform you that a new version of our interface will be available in production on 12th of September which will contain the following main features:
• Optimization of error handling: From now on, more precise error messages for failed requests are delivered via the interface.
• AIS Consent Creation:
The consent scope allpsd2 - allAccountsWithOwnerName is now also available and we recommend to always use that scope on every AIS Consent creation. (We do not provide official support for other scopes or manual account lists!)
• The old Account endpoints are still there but we will NOT deliver Card information via that endpoints anymore!
• There are new Card-Accounts endpoints from now on which have to be used if you want to get card account lists, details, balances or transactions.
New Endpoints:
• GET /v1/card-accounts
• GET /v1/card-accounts/{card-Id}
• GET /v1/card-accounts/{card-Id}/balances
• ATTENTION: We noticed that we currently have a problem that we deliver 2 "closingBooked" balances even if one of them is ment to be an expected balance type... Please take the "creditLimitIncluded" response field as indicator for the meaning of closingBooked or expected for now! ('true' means expected, 'false' means closingBooked). We will fix that in the near future.
• GET /v1/card-accounts/{card-Id}/transactions
The usage of the new requests behaves exactly like with the old account endpoints. (The responses might differ in their content layout!)
• We focused on improving the stability and performance of our decoupled workflow usages.
• We advise every TPP to use the decoupled workflow as the primary workflow as most of our customers support that workflow.
• We now support SCA exemptions (from a user's perspective) via decoupled! (if a combinedService AIS Consent is provided)
• The TPP still has to poll a SCA with a session token.
• But if the action is sca-exempted the first polling request will directly result in the 'finalized' state!
• We fixed an issue which could lead to freezing sca processes.
• We fixed an issue which could lead to very very long sca polling times.
• We did some improvements for the redirect workflow as well.
• Some Instant-Sepa-Credit-Transfers can also skip sca processes now (if a combinedService AIS Consent is provided)
• We fixed an issue where users had to login again, even if a valid combinedService AIS Consent was used.
• New Feature: TPPs can now create Funds Confirmation Consents (PiisConsents) themselves (user will have to do a SCA process)
• For now this will only work via the redirect workflow but we are already working on having this feature in decoupled in the near future as well!
If you are interested in detailed information on how to use comdirects psd2 api the best way as possible, you can ask us to send you a quick start guide via mail!
This quick start guide is available in German and English language. It contains a lot of useful information about which requests to send in which order and which data are important for which use cases.
It also contains some insights on which actions can be sca exempted and how our payment status flow works.
If you have further questions please do not hesitate to contact us.
Your comdirect XS2A-support