Saved Credit Cards from Impersonator

Nuno Aguiar

Posted on 12/12/2023 17:57:58

Hi,

In our projects we use Impersonation so that a "Login" (real person - i.e. Nuno) can manage an "Account" (i.e. a company - i.e. Dynamicweb North America) and place orders for them.

So far so good as there are multiple "Logins" that can manage "Dynamicweb North America" and see all orders and do everything the same. The curve ball is Saved Credit Cards. We're needing to render "my" Saved Credit Cards, in other words, associated with my user (secondaryUser - the impersonator), instead of the primary user.

Customizing getting the list of cards seems relatively simple in the templates, but I can see that we'd likely need to customize the CheckoutHandlers as well, since there's some logic to get the cards by the (primary) user.

If that is all is takes, that would be "fine", but I wonder if there's anything else I might be missing as well. Or any thoughts on how this could be achieved differentlly.

Best Regards,

Nuno Aguiar

Replies

Nicolai Pedersen

Posted on 15/12/2023 14:36:16

Hi Nuno

There might be - I would say that this is a slipery slope and you are 'on your own'. Seems like it can cause a number of issues in relation to recurring orders and all sorts of things.

BR Nicolai

Nuno Aguiar

Posted on 15/12/2023 14:47:13

Hi Nicolai,

Good point about recurring orders, thanks. Indeed a slipery slope, and I'm still evaluating the lesser of 2 evils.

A simpler alternative is to NOT use impersonation at all. Using the same example, instead of "Nuno" impersonating "Dynamicweb North America", we have a "Nuno - Dynamicweb North America", and a "Mario - Dynamicweb North America". We should share a lot of data (including Customer Number) so we could see each other's orders (List by Customer Number) and likely have to use some duplicate content if we were to integrate addresses.

In this scenario, Saved Credit Cards are not the issue, but forces us to abandon a lot of our standardized way of integrating data (not saying it's a good nor bad, but there's definitely cost savings and lower risk there in making it consistent).

This request is not the first time it comes around, although definitely not the most common one. We can easily see it both ways (some customers wanting shared CC, while others want unique ones), and the integration architecture we have (Login + Customers) mirroring what the ERPs we work with have, makes things simple to explain (not necessarily maintain, since it leads to more data/endpoints to support the 2 user types + impersonations).

I guess we'll have to do some POC if it comes to it, and put some guard-rails around the scope.

Thanks for the input anyway.

Best Regards,

Nuno Aguiar

Nicolai Pedersen

Posted on 15/12/2023 14:53:37

This post has been marked as an answer

We have been around this numerous times and you know I do not agree on your solution. Solving a relatively small problem with a bigger one is not my cuppa :-).

2 users should not impersonate a parent to solve this.

2 users should share customer number and in that way share customer center order history etc. if needed. I agree addresses might be an issue missing the option to share addresses across customer number.

Votes for this answer: 1

Nuno Aguiar

Posted on 15/12/2023 15:05:57

Hi Nicolai,

If we can have the ability to "share addresses", maybe that could be the solution to pivot to it :-)

I can start feeding that concept into our team if you can consider the address sharing feature (even if it's on DW10 only)

I would love a simpler solution for sure.

You must be logged in to post in the forum

Developer forum

Saved Credit Cards from Impersonator

Replies