Enhanced SCA Flow
- Documentation calls it a decoupled flow, yet it seems like it's still a redirect - but with app2app. Is that correct?
- Should we include the configuration id (and PSU-ID header) in the headers of the following requests: POST /consents and POST /payments/sepa-credit-transfer OR should we add it to the body of the request?
- Are there any additional requests where these headers should be added for the flow to be triggered?
- Does the value of aspsp-sca-approach change based on whether the enhanced flow is used or not, or does it stay as REDIRECT?
- Is the redirect URL where the user authenticates still Solaris regardless of partner configuration id?
- We have noticed that SolarisBank is not listed as an option in the available configuration IDs: https://xs2a-portal.solaris-sandbox.de/#/apis/46/1717 Does SolarisBank support enhanced SCA flow?
- Is the configuration_id returned for each partner (e.g., Kontist, Tomorrow, etc.) globally consistent across all TPPs OR or is the list of partners and their corresponding configuration_id values customized per TPP?