Steve

Hey @tanmay-kumar-das ,

Excellent, glad to hear you solved the issue!

With the blocks on Checkout, were you using the WooCommerce Cart and Checkout Blocks plugin to create the Checkout page?

Cheers,
Steve

Hey @tanmay-kumar-das ,

Thanks for contacting us about GoDaddy Payments for WooCommerce! I’m happy to help out ??

I went through the Checkout process on your site and saw the no payment available message.

We often see this when there is an issue with the Application ID or Private Key. To make sure that these are correct, can you please go through the following steps again and make sure that these are both correct?

1. Login to your GoDaddy Payments dashboard and go to Advanced Tools > Business Settings > Contact Info.
2. Copy your Application ID and Private Key in the Poynt Collect API Settings section.
3. In your WooCommerce store, go to WooCommerce > Settings > Payments > Credit Card and paste these credentials in the Application ID and Private Key fields.
4. Click?Save Changes.

Once you have verified that the credentials are correct, can you please let me know if the issue persists?

Cheers,
Steve

Hey @esd3104 ,

Thanks for contacting us about GoDaddy Payments! I’m happy to help out ??

Currently, the plugin only supports the iframe method for loading the credit card form fields. Your assumptions on what is happening with the blank fields until page refresh are correct, the iframe loading isn’t getting triggered until the page refresh.

I have the site URL from your previous post but didn’t see the country dropdown option. Would it be possible to add this back to Checkout so I can take a look at the behavior?

Cheers,
Steve

Hey @esd3104 ,

Thanks for contacting us about GoDaddy Payments for WooCommerce! I’m happy to help out ??

I took a look at the Checkout page and was able to see the issue. It seems that the container for the checkout form isn’t adjusting the height to fit correctly with the theme.

Making some changes to the CSS seems to help to get it to fit correctly:

https://cloud.skyver.ge/E0uXEG8l

While customizations are not covered under our?support policy, I’m happy to point you in the right direction here. Please be sure you know how to?add custom CSS to your site, and then, this CSS can be used:

.poynt-collect-payment-container {
    height: 230px;
    display: flex;
    flex-direction: column;
    justify-content: center;
}

Can you please add this CSS and let me know if it helps to remove the scroll bars on the payment form?

Cheers,
Steve

Hey @web4studio2019,

Just wanted to follow up to make sure that everything is working correctly now on your staging site. Were you able to get test transactions to process OK?

Cheers,
Steve

Hey @web4studio2019,

Thanks! I checked the credentials listed for the live site and added these to the staging site. With these in place, the transaction went through with the OpenSSL error. I also see that the 1.4.1 version of the plugin is installed.

Everything should be working OK now. You may want to make a copy of the credentials for GoDaddy Payments from the staging site. The live site was using the built-in GoDaddy Payments and these are stored slightly differently than the plugin.

Can you please run a test transaction on staging and let me know if everything seems to be working OK now?

Cheers,
Steve

Hey @web4studio2019 ,

Sorry that reply wasn’t clear on the account!

I was hoping to access the live site to take a look over the settings there, as the issue doesn’t seem to be occurring there. Is the live site https://lightlifetechnology.com/ ? Would it be OK for me to access the account and take a look at the GoDaddy Payments settings there?

Cheers,
Steve

Hey @eric4 ,

I’m very sorry for any impact the v1.4.0 version may have had on your business.
We were notified of this issue and shortly afterward released v1.4.1 of the plugin which resolves this issue.

Cheers,
Steve

Hey @web4studio2019 ,

Thanks for getting back on this!

I logged in and checked the Private Key at WooCommerce > Settings > Payments > GoDaddy Payments and it still looks to be rather short. The Private Key should be several lines and the Private Key is only showing 30 or so characters.

Are you getting the Private Key from your GoDaddy Payments account directly? Would you please let me know if I can access the account to take a look at the settings?

Cheers,
Steve

Hey @web4studio2019,

The SSL tests correct now, but I was still seeing the OpenSSL errors with the previous version when attempting to place a test transaction.

With the earlier version active, I was able to check the settings for the plugin. It looked like the Private Key was shorter than it should be, so I swapped over some other credentials from one of my test accounts and the Open SSL error went away on Checkout. It seems that the Private Key is incorrect, and therefore wasn’t able to authenticate, as well as causing the issues with the update.

I put your original credentials back in place. What you will want to do next is:

• Login to your GoDaddy Payments dashboard and go to Advanced Tools > Business Settings > Contact Info.
• Copy your Application ID and Private Key in the Poynt Collect API Settings section.
• In your WooCommerce store, go to WooCommerce > Settings > Payments > GoDaddy Payments and paste these credentials in the Application ID and Private Key fields.
• Click Save Changes.

Once this is done, can you please let me know and I can test out another transaction to see if the OpenSSL error is resolved, then attempt to update the plugin.

Cheers,
Steve

Hey @web4studio2019

Hope your weekend was good!

How did you go about creating the staging site? Was this originally on a GoDaddy WordPress/WooCommerce Managed plan?

I’m wondering if there might be some references to a previous SSL Certificate from the move to staging. There are ways to install an SSL Certificate on the staging site, which might help with the OpenSLL errors when trying to authenticate. This would be a bit out of our support policy, but I can send some ideas to get you started on this.

Cheers,
Steve

Hey @web4studio2019 ,

Thanks! ??</img>
I logged in and installed the previous version, which installed and activated without issues. I then ran a test transaction using a test card number to see if it would connect through and send an invalid card response.

I received an “OpenSSL unable to sign data” error on Checkout with this test. I ran some SSL tests against the domain and they are seeing a certificate that is self-signed/untrusted. I tried with the site set to https as well. The certificate was created Nov 22. Do you happen to know if it was created and applied to the staging site around that time, or any other information on it?

Cheers,
Steve

Hey @web4studio2019,

The password reset link doesn’t appear to work on the staging site.

Would it be possible to send a password for the account you created to the same support@ e-mail address via QuickForget?

Cheers,
Steve

Hey @web4studio2019,

For the staging site, can you please?add and account using the e-mail?[email protected]?so I can recover the account password and access the site to take a look?

Cheers,
Steve

Hey @web4studio2019 ,

Thanks for trying that out. I’m still wondering if there might be something with the SSL or some data that might be in GoDaddy Payments somehow.

You mentioned admin access earlier on. Would that be a possibility? Is the staging site on GoDaddy?

Cheers,
Steve