open-banking-gateway
open-banking-gateway copied to clipboard
adorsys
Provides RESTful API, tools, adapters, and connectors for transparent access to open banking API's (for banks that support PSD2 and XS2A as well as HBCI/FinTS)
Could not find artifact de.adorsys.opba:fintech-impl:jar:1.0.1-SNAPSHOT in snapshots-repo
Currently, we are redirected to the consent initiation screen because the Consent object is missing as it can't be supplied by Fintech. Obviously, if consent object can be supplied by...
As redirection URL is computed value that may come from 3rd party protocol, in order to protect user from phishing attacks, we need to add: - [ ] API level...
Drop `ValidationInfo(ui = @FrontendCode(STRING), ctx = @ContextCode(FieldCode.PSU_IP_ADDRESS))` and fix tests accordingly. PSU IP address is not something that can be provided by the user and if it is missing there...
Currently, `confirmConsent` uses authorization-id that is shared with the client device to activate consent. We need to heighten the security so that one needs a secret code additionally like in...
Starting from the new Xs2a spec, there is new support for paging in transaction list requests. We need to support this Commerzbank and Fiducia should already support this
Avoid showing 'Consent confirmation' screen for HBCI. HBCI does not have a consent configuration
support transaction response with multiple categorisation response Client needs to decide which categorisation engine he needs to use
Xs2aAdapter does not seem to handle Oauth2-prestep exception for payment properly for Adorsys Sandbox. Instead of throwing `OAuthException` it throws `ErrorResponseException`. Need to check with their latest version and raise...
Currently, all (almost) context codes are in the form of JSON path like this: `recurringIndicator` We need to extract them to constants shared between api and protocols. Also frontend code...