Member Context Lost in GetProductSnapshot After Stripe Payment Completion

[Zarhead-CB]

Context

• Umbraco v14.2.0 + Umbraco.Commerce.PaymentProviders.Stripe v14.0.0.
• Multi-Account Members: Members can have multiple customer accounts (e.g., "North" and "South").
• Account-Based Pricing: Product pricing depends on the selected account (ActiveMemberAccount.Account.CrmObjectId).

Issue:
After Stripe payment completion, GetProductSnapshot re-runs, but GetCurrentCustomer() (which retrieves the current member) returns null, causing exceptions.

---

Code Snippets

Product Adapter:

public override IProductSnapshot GetProductSnapshot(...)  
{  
    // Fails here post-payment on throw new Exception($"Could not retrieve current customer"):
            var Customer = AsyncHelper.RunSync(() => MemberService.GetCurrentCustomer());
            if (Customer?.ActiveMemberAccount == null)
            {
                if (Customer == null)
                {
                    throw new Exception($"Could not retrieve current customer");
                }

                logger.LogError(
                    " customer with Member Key: '{CurrentCustomerMemberKey}' does not have a ActiveMemberAccount",
                    Customer.PublishedModelMember.Key);
                throw new Exception($"customer with Member Key: '{Customer.PublishedModelMember.Key}' does not have a ActiveMemberAccount");
            }

            // The available prices for this product/variant
            var productPrices = priceService.GetPrices(
                storeId,
                Customer.ActiveMemberAccount.Account.CrmObjectId,
                product.Sku,
                productVariantReference);
}  

Member Service:

public async Task<Customer?> GetCurrentCustomer()  
{  
  // Relies on HttpContext-bound IMemberManager:  
  var memberIdentityUser = await _memberManager.GetCurrentMemberAsync();  
  // ...  
}  

---

Problem Details

1. Member Context Lost Post-Payment:

   • After Stripe payment completes, GetProductSnapshot is called again during order finalization.
   • At this stage, GetCurrentCustomer() (which relies on IMemberManager.GetCurrentMemberAsync()) returns null.

2. Critical Dependency on Member Context:

   • Pricing logic requires PrimaryMemberAccount.Account.CrmObjectId, which is tied to the logged-in member’s selected account.
   • Without access to the member, the pricing logic fails, throwing an exception.

---

Questions

1. Accessing Member Context Post-Payment:

   • Is there a built-in way to persist the member ID or account ID on the order during checkout, so it can be retrieved in GetProductSnapshot after payment?

2. Overriding Upstream Logic:

   • Can we override or extend the code that runs before GetProductSnapshot (e.g., during payment finalization) to pass the required member/account context?
   • Are there extensibility points (e.g., events, services, or pipelines) that allow injecting this data earlier in the workflow?

3. Custom Implementation:

   • Would it be better to create a order pipeline to handle this use case?

[mattbrailsford]

I think this is likely because this will get called in the webhook handler which finalizes the order.

I think what you could do is use the seasion during checkout, but if the session isn’t available check the CustomerReference of the order and fallback to that user. During checkout, just before redirecting to a payment gateway the order should get auto assigned if there is a logged in member. This would make the customer reference the Key of the Umbraco Member. So you should be able to use that to look up the member.

[Zarhead-CB]

Hi Matt! Thanks for the swift response - I've tried to action getting the order in the ProductSnapshot, but getting stuck due to it requiring the customerRef _commerceApi.GetCurrentOrder(store.Id, currentCustomerRef);.
How would you suggest I get the current order on from within the product snapshot?

[mattbrailsford]

Ahhh, hmm, this might not actually work then as in a webhook request, the session probably won't be set either to get the current order 🤦‍♂️

I'll have to give this some thought on a better solution