Closed (fixed)
Project:
Commerce Authorize.Net
Version:
8.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Reporter:
Created:
19 Jun 2025 at 13:38 UTC
Updated:
2 Dec 2025 at 08:54 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
vmarchukComment #4
vmarchukComment #5
vmarchukComment #6
vmarchukComment #7
vmarchukComment #8
vmarchukComment #10
imbatman commentedNew patch ensures anonymous checkouts only send the email (no customer ID) to Authorize.Net, preventing all guest profiles from being assigned to customer ID 0. Authenticated users still send both ID and email. Fixes CIM profile misattribution.
Comment #11
vmarchukComment #12
vmarchukComment #13
vmarchukAdded integration with webhooks.
Comment #14
vmarchukComment #15
vmarchukComment #16
tkiehne commentedSimilar work in #3019539; not sure if quite the same but has the same objective
Comment #17
vmarchuk@tkiehne I think it's something else. We're working on integrating https://developer.authorize.net/api/reference/features/accept-hosted.html.
Comment #18
morbus iff@vmarchuk, what's the difference between this one and #3452993?
Comment #19
tkiehne commented@vmarchuk - yes, it appears they are two different approaches, however, from an initial appraisal, this feature and the AcceptJsUI feature will interact in various parts of the module code. I have been using the AcceptJsUI patch in production for three years and the issue that created it has been ongoing since 2018. I think it wise that the maintainers provide some guidance as to what features will end up being supported/integrated given the interactions.
That said, I am interested in seeing where this implementation goes as it might provide for my needs, and if it ends up merged into contrib will be more stable.
Comment #20
vmarchukComment #23
jsacksick commented