Mihail Podtykalenko
- Total activity 100
- Last activity
- Member since
- Following 0 users
- Followed by 0 users
- Votes 0
- Subscriptions 38
Articles
Recent activity by Mihail Podtykalenko-
Any other useful information that we should know about Bulk Payments?
Currently, there are no additional limitations. We will keep you informed if there are any updates or plans for future changes through our documentation.
-
Do you support multi-authentication for bulk payments?
Yes, we do support .
-
Which accounts are accessible for Account Information Services (AIS) through the PSD2 API?
We generally support all payment accounts and business accounts too. The main product groups that we have are:Current accountsRestricted accountsAccounts opened for Cards products:Emoney accounts f...
-
Documentation calls it a decoupled flow, yet it seems like it's still a redirect - but with app2app. Is that correct?
Yes, it is correct, solaris uses the enhanced SCA flow in redirect as mentioned here - https://xs2a-portal.solaris-sandbox.de/#/apis/root.~.xs2a-interface/v1/136#decoupled-sca-approach
-
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?
When initiating Account Information Service (AIS) or Payment Initiation Service (PIS) flows, include the partner configuration id as part of the request in the X-Custom-Property-Partner-Id header. ...
-
Are there any additional requests where these headers should be added for the flow to be triggered?
There is no additional requests required on this
-
Does the value of aspsp-sca-approach change based on whether the enhanced flow is used or not, or does it stay as REDIRECT?
Response_headers_aspsp-sca-approach header will be always redirect
-
Is the redirect URL where the user authenticates still Solaris regardless of partner configuration id?
When the partner configuration ID is supplied in the initiation requests then it will be connected with the respective partner and no need of user login for the end user in the my.solarisbank.de.
-
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?
This enhanced SCA flow allows end-users to select their preferred brand on the TPP page instead of Solarisbank as highlighted in the documentation part. So Solarisbank’s configuration ID wont be li...
-
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?
The GET /psd2/partners endpoint https://xs2a-portal.solaris-sandbox.de/#/apis/46/1717 returns a list of Solarisbank partners with a unique configuration_id for each partner. All data in this list i...