Onboarding | BPNL creation and check is skipped when BPN was provided in registration | DB misalignment

[typecastcloud]

Current Behavior

While onboarding a company, the BPN Creation step is skipped (set to done) without verifying if the BPN already exists and the data is correct IF the BPN was provided by user in any way.

This can create misalignment between Portal and BPDM database!

Expected Behavior

Company data should always be verified against BPDM Pool even if using search.

Pool is source of truth! Right now a customer could enter any BPN via API and as long as the same is not yet used in portal db, the onboarding will succeed and create wallet/sd for this BPN.

Steps To Reproduce

1. Invite company
2. Set any existing BPNL in search for company details
3. Save company data
4. Submit application
5. BPN Creation step is DONE instantly

Additional info

• POST: application/{applicationId}/companyDetailsWithAddress
  • Endpoint allows customers to set ANY bpn they want
• Initial checklist creation sets the BPN Creation step to DONE if BPN already exists

[typecastcloud]

Hi @MaximilianHauer,
did you have time to have a look at this? I'll add it to the open meeting tomorrow.

@Phil91 @ntruchsess already gave some feedback in our committer meeting but you are welcome to add some comments before I start implementing a solution.

1. Fix to reduce the current risk of problematic onboardings
2. Reevaluate the BPDM validation process in onboarding and create changes based on this.

[evegufy]

Hi @typecastcloud ,

as discussed in today's open meeting, here the 3 scenario for the BPN creation (as I said, scenario 3 can be ignored, only scenarios 1 and 2 are valid).