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

In case you see this again, my context is PHP 8.1/ZC 1.5.8.
It's not the module that gets disabled, it's the card in the customers_cc table. Sorry, should have clarified.

In case anyone else is getting mismatches between authorize's invoice number and Zen Cart's order number for orders which are NOT placed at the same time, it may be worth changing includes/modules/payment/authorizenet_cim.php nextOrderNumber() function to do

$result = $db->Execute("SELECT max(orders_id)+1 AS orders_id FROM " . TABLE_ORDERS . " ORDER BY orders_id");
$next_order_id = $result->fields['orders_id'];
return $next_order_id;

instead of pulling the auto_increment value from SHOW TABLE STATUS.

The use of max(orders_id) mirrors the "next id prediction" logic used by other parts of Zen Cart, such as the attributes controller and specials/featured product management.

At the end of before_process() in authorizenet_cim.php you call chargeCustomerProfile(). Should this be wrapped in a check like

if ($this->authorizationType != 'Authorize')

I'm asking because I have configured CIM to Auth Only but it seems to be charging.

Quote:

---

Originally Posted by swguy

At the end of before_process() in authorizenet_cim.php you call chargeCustomerProfile(). Should this be wrapped in a check like

if ($this->authorizationType != 'Authorize')

I'm asking because I have configured CIM to Auth Only but it seems to be charging.

---

scott,
I am really trying to understand your question. I suppose I could understand it if it was coming from a store owner with limited coding experience. but as you are one of the big machers in ZC, I do not understand it.

in a word:

NO.

I would suggest looking at the code. and then looking at it again.

$this→authorizationType gets initialized to `Authorize`. and then it does not get changed and or used until the method (chargeCustomerProfile) that you are asking to not be called.

I could go on. and on. but I will not.

if you would like me to figure out what is happening on your clients site with regards to this module, I am certainly available for hire.

this payment module is mature. the ability to authorize only or authorize and capture together has been well established since I initially made this payment module available for community use.

best.

for those of you using this most excellent payment module, and who read this post; and then breathed a sigh of relief; that post is not applicable to this payment module.

this payment module WILL require an update to the new certificates to continue working after the cutoff date.

best.

Quote:

---

Originally Posted by carlwhat

for those of you using this most excellent payment module, and who read this post; and then breathed a sigh of relief; that post is not applicable to this payment module.

this payment module WILL require an update to the new certificates to continue working after the cutoff date.

best.

---

Thank you for clarifying. I assumed the opposite, of course.

Will you make an updated version available?

Quote:

---

Originally Posted by jeking

Thank you for clarifying. I assumed the opposite, of course.

Will you make an updated version available?

---

i am now unclear as to whether the cert file will need to get replaced. it is a definite maybe...

in any event, i will be supporting this module for whatever needs to get done. i am still working out some of the details.

and i am following the situation rather closely.

best.

Thanks for taking care of this, @carlwhat.

Quote:

---

Originally Posted by carlwhat

i am now unclear as to whether the cert file will need to get replaced. it is a definite maybe...

in any event, i will be supporting this module for whatever needs to get done. i am still working out some of the details.

and i am following the situation rather closely.

best.

---

I'm also confused. I'm assuming that the SPK needs to be updated, or at least the PEM file. I checked GitHub for the latest release yesterday, but it hasn't been updated yet.

https://github.com/AuthorizeNet/sdk-php

https://github.com/AuthorizeNet/sdk-...master/lib/ssl

Quote:

---

Originally Posted by marcopolo

I'm also confused. I'm assuming that the SPK needs to be updated, or at least the PEM file. I checked GitHub for the latest release yesterday, but it hasn't been updated yet.

https://github.com/AuthorizeNet/sdk-php

https://github.com/AuthorizeNet/sdk-...master/lib/ssl

---

that repo is the source of much consternation...

this PR has an updated version of the pem file that i have tested and currently works... as to whether it will work on 10/23 is the big question.

best.