Enhanced (Decoupled) SCA Flow
- Why is Solarisbank not listed as a configuration ID? Does Solarisbank support the Enhanced SCA flow?
- How can I obtain the list of valid X-Custom-Property-Partner-Id values?
- 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 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?
- 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?
- Why do I receive the error HTTP 403 – SERVICE_BLOCKED – "Redirect Flow is not supported"?
- Why do I receive the error HTTP 400 – SERVICE_INVALID – "The addressed service is not valid." (Couldn't find 'Solaris::PartnerConfiguration' for id 'XXX')?
- Finom