Berlin Group Consent Settings

|OBP provides configuration options for Berlin Group consent creation and SCA (Strong Customer Authentication) flows. | |## Frequency Per Day Limit | |* berlin_group_frequency_per_day_upper_limit - Maximum allowed value for the frequencyPerDay field when creating a Berlin Group consent. Default: 4. | |When a TPP creates a consent, the requested frequencyPerDay must be greater than 0 and less than or equal to this upper limit. For one-off access consents, the frequency must be exactly 1. | |Example: | | # Allow up to 10 requests per day per consent | berlin_group_frequency_per_day_upper_limit = 10 | |## ASPSP SCA Approach | |* berlin_group_aspsp_sca_approach - Defines the SCA approach advertised by the ASPSP (Account Servicing Payment Service Provider) in the ASPSP-SCA-Approach response header for consent creation endpoints. Default: redirect. | |Possible values include: | |* redirect - The PSU is redirected to the ASPSP for authentication |* embedded - Authentication is performed within the TPP interface |* decoupled - Authentication is performed on a separate device/channel | |This header is returned in the response to POST /consents requests to inform the TPP which SCA method the ASPSP supports. | |Example: | | # Use embedded SCA approach | berlin_group_aspsp_sca_approach = embedded |