Completing Party

[dahkong]

Hi @jlane

Thanks for revisiting this. We were hoping it would be possible to consider this post as a potential solution.

User Authentication and Security for Premium Accounts

Currently, our system makes use of the BC Online user accounts to authenticate our firms’ account users. Through our screen scraping interface, they must log in. We also use the BC Online VerifyUser webservice to authenticate each user submitting records to our transaction service and ultimately to the BC Online DebtAcct webservice. For premium subscribers, our agreement specifies that we must authenticate our users. This means that each premium subscriber must do so using their own architectur…

I realize @thor mentioned there are internal challenges with getting approval for this, but it seems if we had that in place, changes to the architecture with respect to the completing party would be relatively minimal.

• Users that access the system outside of an API partner are required to use their BCeID, so seemingly something is already in place to facilitate use of the BCeID.
• The person that’s associated with the BCeID would be the completing party ;
• Any filing confirmations would be sent to the person that has logged in using their BCeID, addressing any potential privacy concerns;
• Potential creation of a “submitting party ID”, for recording of the API partner doing the submission.

Thank you for your time and consideration.