BitPay

@zaka888 since account is a sensitive issue that can’t be resolved on the forums, it would be great if you could reach out through https://bitpay.com/request-help/wizard and we can get you some clarification regarding acceptance. There’s a chatbot to get started and will help direct you to someone in support if you can’t find what you’re looking for.

Alrighty @zaka888 , I’ve talked to my teammates that handle this part of onboarding and they said that while we prefer the version that the plugin currently comes with, you can use other marks from the guidelines.

I believe this will give you two paths forward:

Near-Term

You could modify the plugin directly. This is not recommended and changes would be wiped on a plugin upgrade but that’s up to you and your development workflow.

Long-Term

We are putting a story on our backlog for review and will link it to a GitHub issue. This story will add a dropdown to the configuration to allow you to choose from the various buttons.

Thanks again for reaching out, this is a real-world feature that we’ll add to the plugin!

Hello,

We have guidelines for how the payment mark should be used in the link that was provided in our previous post (https://developer.bitpay.com/docs/checkout-page).

A screenshot would be very helpful, however without that available I believe you’re referencing the payment mark that is used, which is https://bitpay.com/cdn/merchant-resources/pay-with-bitpay-card-group.svg, which is the intended image.

NOTE: I do see that on the plugin page in the WP marketplace that the third screenshot shows an option to change the button, but it appears that this may be a cached file on the WP marketplace CDN and is not showing the latest screenshots as this option was removed for branding purposes.

If you are having a specific issue or the plugin is not working as intended, please provide as much information as possible. Examples include:

• Your operating system
• PHP version (I understand you’re on version 8.0.30)
• WordPress version
• WooCommerce version
• All other plugins and their versions

If the primary issue is that you are not happy with the default logo, you should be able to override the bitpay_logo CSS class, but I cannot guarantee that an image you choose would be in-line with brand usage guidelines.

Finally, the plugin is open source, so if you’d like to contribute to the codebase, we welcome you to submit a pull request our GitHub repository.

Awesome! Thanks for spotting it – it was a huge help. We didn’t catch it because our GitHub Actions runners were using ubuntu-latest, which very recently switched to 22.04. The image for this version does not include PHP 8.0, and does not fail when it’s passed into a version matrix. This resulted in 8.1 being used to run composer install as well as tests on 8.0 and 8.2 in the SDK.

We were able to stick with ubuntu-20.04 and run 8.0, 8.1, and 8.2, and have since split our tests between PHPUnit 9 and 10.

This was immensely helpful, and we really appreciate you reporting it. It’s a case that shows how the WP community really does help.

Hello again @risbo95 we just wanted to give you another quick update. We’ve updated the SDK and plugin repositories to address this specific issue and plan on releasing both either tomorrow or Monday.

Hello! We’ll take a look at this today. Please note that you do not need to use composer to install the plugin because we pre-package the vendor directory.

Hi Abel,

This is most likely because you havent finished setting up your BitPay account (settlement, compliance documentation, etc)