Payment Profile: Authorize.Net with ARB v1.5.0

[ActorMike]

Yes, validated on 2.3.2, PHP 8.2. There's no server errors? Do you have it deployed on a test board? If so, can you enable debug mode and see if the error bubbles up.

Why does the button need clicked twice? The first time I can see it briefly say "preparing payment" and the second time it works. This could cause confusion for some people on rare occasions, although most people will probably click the button twice.

 

[stromb0li]

That is not the experience I am seeing in my production environment.

The customer clicks the generic Purchase button to start checkout, the form popups up to gather their info, and they click Pay. No additional button clicks should be needed after that.

If you open developer tools, are you seeing any javascript errors?

 

[ActorMike]

That is not the experience I am seeing in my production environment.

The customer clicks the generic Purchase button to start checkout, the form popups up to gather their info, and they click Pay. No additional button clicks should be needed after that.

If you open developer tools, are you seeing any javascript errors?

There are no errors in the console. Briefly, you can see text under the payment button that says "preparing payment" then it disappears quickly. The second press of the button processing the payment successfully.

 

[stromb0li]

Sent you a PM...DM. I cannot repro this in our production environment.

 

[ActorMike]

Sent you a PM...DM. I cannot repro this in our production environment.

Sent. It's odd because no errors are generated and when it is clicked the second time, the payment processes with no issue.

 

[Andy.N]

@stromb0li @ActorMike
I just updated to XF 2.3.2 and 1.5.0 version of this addon.
I got the same issue where clicking the Pay button does not go anywhere, clicking on it the second time will process.
Can we get together to fix this?

 

[Andy.N]

Sent you a PM...DM. I cannot repro this in our production environment.

I have a live site you can test.

 

[Andy.N]

Sent. It's odd because no errors are generated and when it is clicked the second time, the payment processes with no issue.

Have you made any progress with this issue?

 

[ActorMike]

Have you made any progress with this issue?

I'm just going to wait until it's fixed in a future release. I operate a 20+ year old forum, we take paypal & AuthNet and 16 memberships were sold via AN in the last 2 days. Fortunately it's human nature to click the button again, otherwise it would be a real problem because there's no shopping cart in the 25 years I've used the internet that requires the end user to push the submit order button twice.

 

[Andy.N]

I'm just going to wait until it's fixed in a future release. I operate a 20+ year old forum, we take paypal & AuthNet and 16 memberships were sold via AN in the last 2 days. Fortunately it's human nature to click the button again, otherwise it would be a real problem because there's no shopping cart in the 25 years I've used the internet that requires the end user to push the submit order button twice.

Yes, this is related to the last update. Before this, I never experience it.
I test with several cards and same issues. You can always void the transactions on the back end for testing purpose.
Since @stromb0li said he never experience it in his testing environment, I wonder how we can help him diagnose this issue so he can fix it.

 

[ActorMike]

Yes, this is related to the last update. Before this, I never experience it.
I test with several cards and same issues. You can always void the transactions on the back end for testing purpose.
Since @stromb0li said he never experience it in his testing environment, I wonder how we can help him diagnose this issue so he can fix it.

They are aware of it now and were able to produce the issue after the post above. I got a message last Sunday that said:

I am able to reproduce this but have no idea why this behavior is happening. Based on traces, the first request is made directly to authorize.net to get a token for payment and the second request is what is actually making the payment; some sort of race condition going on here. Will probably take a while to work through this.

 

[ActorMike]

Yes, this is related to the last update. Before this, I never experience it.
I test with several cards and same issues. You can always void the transactions on the back end for testing purpose.
Since @stromb0li said he never experience it in his testing environment, I wonder how we can help him diagnose this issue so he can fix it.

@Andy.N

For now, I edited the "payments_processed_securely_by_x" and noted that some users may need to click the pay button twice.

 

[Andy.N]

@ActorMike
Appreciate you keep me updated on this. Yes, I think adding that phrase (I would bold or color them to get more attention) would minimize missed transaction.
The developer is aware and able to reproduce the issue so now we just have to keep our fingers crossed for a successful solution.

 

[Andy.N]

@stromb0li @ActorMike
I got this email from authorize today. I believe this will affect all of us, right?
Dear Authorize.net Merchant,

Authorize.net is updating the SSL/TLS certificates used for secure communication with our systems. This change affects both browser-based and server-to-server interactions.

Who is being affected: Merchants who utilize Authorize.net APIs and endpoint URLs in their websites or applications will need to make updates. They will need to integrate and use the newly-issued Root and Intermediate (CA) SSL certificates from DigiCert. This should be done before the scheduled revocation dates to avoid disruptions.

What you need to do: You must integrate and use the newly-issued Root and Intermediate (CA) SSL certificates from DigiCert by October 24 to avoid any disruptions. To help you fight fraud, AFDS is automatically enabled on your account, which gives you access to many powerful fraud filters, including:

For detailed instructions, please refer to the support articles below:
• Entrust to DigiCert SSL Certificate Migration (KA-05545)
• Latest Version of Authorize.net Server-Level SSL Certificates (000003009)

 

[stromb0li]

As long as the chain is up to date on your webserver you should be good to go. I don't see anything in code pinning the certificate, so the addon should be fine.

 

[Andy.N]

As long as the chain is up to date on your webserver you should be good to go. I don't see anything in code pinning the certificate, so the addon should be fine.

Do we use an end point URL in this addon?

 

[stromb0li]

Do we use an end point URL in this addon?

Do you have context to what you are referring to?

 

[Andy.N]

On your authorize.net, under Account -> Business Settings -> Webhooks, there is an end point.

 

[ActorMike]

This message is server/hosting related pertaining to the website server and the Root and Intermediate (CA) SSL certificates that are allowed and installed on the server.

 

[Andy.N]

Here is a more detailed explaination of who affected and what needs to be done,

Knowledge Article Detail Page - Anet | Authorize.net Support Center