fix(deposit): update Bridge SEPA account holder name + deposit details bugs#2417
Open
kushagrasarathe wants to merge 2 commits into
Open
fix(deposit): update Bridge SEPA account holder name + deposit details bugs#2417kushagrasarathe wants to merge 2 commits into
kushagrasarathe wants to merge 2 commits into
Conversation
Bridge completed a legal entity migration on 2026-06-27; EUR/GBP vIBANs now reflect the new entity name 'Bridge Building S.A.' (was 'Bridge Building Sp. Z.o.o.'). Update the FE fallback account holder name to match and avoid sender name-mismatch confusion at deposit time.
Contributor
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
Code-analysis diffPainscore total: 6186.26 → 6187.43 (+1.17) 🆕 New findings (6)
✅ Resolved (7)
📈 Painscore deltas (top movers)
|
Contributor
🧪 UI test report — ✅ all greenSuites
📊 Coverage (unit)
⏱ 10 slowest test cases
|
The old fix only touched the fallback constant, which the FE uses solely when
Bridge omits account_holder_name (GBP faster_payments). For EUR/SEPA Bridge
returns the field directly and can still send the stale 'Sp. Z.o.o.' name, so
the fallback never applied and the sender's Confirmation-of-Payee check kept
flagging a mismatch.
Route both display sites through resolveBridgeAccountHolderName, which maps the
stale/absent legacy name to the current entity ('Bridge Building S.A.') while
passing through any other value. Banking Circle accepts either name so payments
still settle — this just removes the name-mismatch warning.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Batch of deposit-details bug fixes.
1. Bridge SEPA account holder name
Bridge completed a legal entity migration on 2026-06-27. Their EUR/GBP vIBANs now reflect the new entity name Bridge Building S.A. (previously Bridge Building Sp. Z.o.o.). Sending banks whose records still have the old name surface a name-mismatch warning; Banking Circle accepts payments to either name so transfers still process, but the mismatch confuses users.
Updated the FE fallback account holder name (
BRIDGE_DEFAULT_ACCOUNT_HOLDER_NAME) to match the current legal entity.Source: Bridge support (ticket #171111) confirmed the new entity name and that both names route correctly.
Notes
account_holder_nameon faster-payments deposit instructions.render-baseline.json) still carry the old name as mock server response inputs; left unchanged (not the display fallback).More deposit-details fixes to follow in this PR.