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.

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.

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?

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.

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-php/tree/master/lib/ssl

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-php/tree/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.

for those of you waiting on the new certificate file, you can get it here.

there is no charge for this file, although you will probably need to create an account on my site.

this file has all of the latest certificates as stated in the authorize.net knowledgebase articles.

i have tested this file on 2 live sites located in the US with zero problems. in addition to having run cursory tests, those 2 sites are both now using this new certificate file in production environments with no ill effect.

for now, i know this new file works in the environments i have tested. when authorize.net makes the changeover on October 23rd and 24th, 2024 will be the real test.

i will be closely monitoring the situation at that time, so that users of this module can continue using it hopefully uninterrupted.

best.

carlwhat:

for those of you waiting on the new certificate file, you can get it here.

there is no charge for this file, although you will probably need to create an account on my site.

this file has all of the latest certificates as stated in the authorize.net knowledgebase articles.

i have tested this file on 2 live sites located in the US with zero problems. in addition to having run cursory tests, those 2 sites are both now using this new certificate file in production environments with no ill effect.

for now, i know this new file works in the environments i have tested. when authorize.net makes the changeover on October 23rd and 24th, 2024 will be the real test.

i will be closely monitoring the situation at that time, so that users of this module can continue using it hopefully uninterrupted.

best.

Thank you for this!

Just to make sure the certs installed, what should we be seeing? I was looking at the DigiCert Root page and I see G5 Root Certificates along with other certs. I see some of the other certs after importing your file, but none of the G5. I didn't see a specification of required certs from the notification email.

bustin98:

Just to make sure the certs installed, what should we be seeing? I was looking at the DigiCert Root page and I see G5 Root Certificates along with other certs. I see some of the other certs after importing your file, but none of the G5. I didn't see a specification of required certs from the notification email.

you only need to replace 1 file...

all of the research that i have done suggests that file has the correct certificates.

i will be monitoring the situation very closely on the 23rd and 24th. and if there is a problem, i will be posting the situation here as well as any solutions.

with regards to what you should be seeing, feel free to do your own research and correct anything you think i may have done wrong. for me to post the contents of the file seems superfluous and unnecessary. if you got the file from my site as i suggested, you should be good to go.

best.

carlwhat:

you only need to replace 1 file...

all of the research that i have done suggests that file has the correct certificates.

i will be monitoring the situation very closely on the 23rd and 24th. and if there is a problem, i will be posting the situation here as well as any solutions.

with regards to what you should be seeing, feel free to do your own research and correct anything you think i may have done wrong. for me to post the contents of the file seems superfluous and unnecessary. if you got the file from my site as i suggested, you should be good to go.

best.

I downloaded your file and when I compared it to the pem file I already have on the server it is the same? Can you confirm the file you have available to downland "cert-mcj9hl.pem" is actually the new version.

marcopolo:

I downloaded your file and when I compared it to the pem file I already have on the server it is the same? Can you confirm the file you have available to downland "cert-mcj9hl.pem" is actually the new version.

Hello,

Pardon my ignorance, but where does one install this certificate?

Thanks,

marcopolo:

I downloaded your file and when I compared it to the pem file I already have on the server it is the same? Can you confirm the file you have available to downland "cert-mcj9hl.pem" is actually the new version.

we all make mistakes!

good catch. thank you.

the new file name is:

cert-3rlvqi.pem

for those of you who have already ordered and created an account, please just login and go to your downloads page.

you will see the new file there ready for download.

as indicated in the products description, here is how to change the file:

***the certificates file contained here needs to replace the existing file in this location:

YOUR_STORE_ROOT/includes/modules/payment/authorizenet/authorizenet-sdk/lib/ssl/cert.pem

there is only 1 file that needs to be replaced.

when you download the file, you want to rename the file to cert.pem and upload it to the directory above using an FTP manager.***

the file has been tested and has been in production for a few weeks now without problem.

apologies about the little extra work.

and thanks to marcopolo for the good catch!

carlwhat:

we all make mistakes!

good catch. thank you.

the new file name is:

cert-3rlvqi.pem

for those of you who have already ordered and created an account, please just login and go to your downloads page.

you will see the new file there ready for download.

as indicated in the products description, here is how to change the file:

***the certificates file contained here needs to replace the existing file in this location:

YOUR_STORE_ROOT/includes/modules/payment/authorizenet/authorizenet-sdk/lib/ssl/cert.pem

there is only 1 file that needs to be replaced.

when you download the file, you want to rename the file to cert.pem and upload it to the directory above using an FTP manager.***

the file has been tested and has been in production for a few weeks now without problem.

apologies about the little extra work.

and thanks to marcopolo for the good catch!

Many thanks to all!!!

@carlwhat Are you sure you have updated your client sites with the new cert? It seems as though they were saying that the new cert wouldn't work until the cutover, so I thought we'd all have to scramble and do it at the last minute.

swguy:

@carlwhat Are you sure you have updated your client sites with the new cert? It seems as though they were saying that the new cert wouldn't work until the cutover, so I thought we'd all have to scramble and do it at the last minute.

100% sure. without question.

best.