Skip to content

Prioritize SCA-required responses over generic init errors#216

Open
mo22 wants to merge 1 commit into
raphaelm:masterfrom
mo22:mo22/prescan-sca-required
Open

Prioritize SCA-required responses over generic init errors#216
mo22 wants to merge 1 commit into
raphaelm:masterfrom
mo22:mo22/prescan-sca-required

Conversation

@mo22
Copy link
Copy Markdown
Contributor

@mo22 mo22 commented May 13, 2026

When a response message contains both a generic not-yet-open-dialog 9xxx error, such as 9050, and a later 9075 response, the generic PIN/auth handling currently runs first. That blocks the PIN and raises FinTSClientPINError before the explicit strong-customer-authentication response is inspected.\n\nThis pre-scans the HIRMG/HIRMS response set while processing a message and lets the explicit 9075 handling take precedence over generic unopened-dialog 9xxx handling. Explicit PIN-related return codes still block the PIN as before.\n\nTested with:\n\n uv run --with pytest pytest tests/test_client.py::test_sca_required_takes_precedence_over_unopened_dialog_error\n uv run --with pytest pytest tests/test_client.py

@raphaelm
Copy link
Copy Markdown
Owner

raphaelm commented Jun 2, 2026

How do you end up with these weird linebreaks in your GitHub PR description, did you write the PRs yourself or are they AI-generated?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants