Authorize.net API with Card on File transactions support thread...

[swguy]

I have a customer whose customers.customers_default_address_id values are getting scrambled - sometimes 0, sometimes another customer's address_book entry. Have you ever heard of this? Running authorizenet_cim version 2.3.2.

[carlwhat]

I have a customer whose customers.customers_default_address_id values are getting scrambled - sometimes 0, sometimes another customer's address_book entry. Have you ever heard of this? Running authorizenet_cim version 2.3.2.

i have not had problems with customers_default_address_id getting scrambled as part of this module. my customers who use this module also use FEC.

i have one customer who uses OPC along with this module, and that customer would occasionally have problems associated with their address book entries being screwed up. i think the latest version of OPC addressed those problems.

on sites where you are seeing that problem, i would look to see if admins had placed an order for a different customer just prior to the customer getting screwed up. a difficult bug to track down, but that has been my only experience where address_book_id entries getting out of sync.

if you think it is related to this module, there is only 1 spot where this module updates the default address book entry and i would think that could be commented out with no ill effect.

best.

[swguy]

> if you think it is related to this module, there is only 1 spot where this module updates the default address book entry and i would think that could be commented out with no ill effect.

Agreed, I might do that.

The trouble is, this customer has a template from the vendor which must not be named, so that could be the root cause and auth.cim could be a victim. Still digging.

[swguy]

I put a log create in updateDefaultCustomerBillto() just before the update when the value of $id (cast as an int).
The original value was 'new'. Hope this casts some light.

[carlwhat]

I put a log create in updateDefaultCustomerBillto() just before the update when the value of $id (cast as an int).
The original value was 'new'. Hope this casts some light.

it does.

there are a few changes to 2 files that you can see in this commit.

in addition, can test this whole branch. that branch should work with php 8.2; although the sdk was updated by some users and not authorize.net.

you can see the discussion over here.

at some point, i will create a new release for this most awesome payment module.

best.