Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update WordPress.org copy to reflect changes and correct errors #10033

Closed
csmcneill opened this issue Dec 24, 2024 · 4 comments · Fixed by #10096
Closed

Update WordPress.org copy to reflect changes and correct errors #10033

csmcneill opened this issue Dec 24, 2024 · 4 comments · Fixed by #10096
Assignees
Labels
focus: misc or unknown Issues that need to be added to a focus area (aka "needs focus"). focus: ops General (non dev) operations bugs and enhancements, not matching any other focus area good first issue The issue is a good candidate for the first community contribution/for a newcomer to the team. type: enhancement The issue is a request for an enhancement.

Comments

@csmcneill
Copy link
Contributor

Description

The readme.txt file populates on WordPress.org here. However, some of this information could use a refresh:


WooPayments is **free to install**, with **no setup fees or monthly fees**. Pay-as-you-go fees start at 2.9% + $0.30 per transaction for U.S.-issued cards. [Read more about transaction fees](https://woocommerce.com/document/woopayments/fees-and-debits/fees/).

This is only true if you're a US merchant accepting domestic cards.


Our global support team is available to answer questions you may have about WooPayments installation, setup, or use. For assistance, [open a ticket on woocommerce.com](https://woocommerce.com/my-account/create-a-ticket/?select=5278104).

The URL is now https://woocommerce.com/my-account/contact-support/?select=5278104.


* PHP 7.3 or newer is recommended.

This is recommended, but 7.3 is noted as required here.


= What countries and currencies are supported? =
If you are an individual or business based in [one of these countries](https://woocommerce.com/document/woopayments/compatibility/countries/#supported-countries), you can sign-up with WooPayments. After completing sign up, you can accept payments from customers anywhere in the world.
We are actively planning to expand into additional countries based on your interest. Let us know where you would like to [see WooPayments launch next](https://woocommerce.com/payments/#request-invite).

This section indicates which countries are supported but not which currencies. Currencies are covered in this document.


= Why is a WordPress.com account and connection required? =
WooPayments uses the WordPress.com connection to authenticate each request, connecting your store with our payments partner.

We can expand on this and link out to this document.


WooPayments has experimental support for the Checkout block from [WooCommerce Blocks](https://wordpress.org/plugins/woo-gutenberg-products-block/). Please check the [FAQ section](#faq) for more information.

= How does the Checkout block work? =
You need the [WooCommerce Blocks](https://wordpress.org/plugins/woo-gutenberg-products-block/) plugin to be installed and active to use the Checkout block. Once you add the block to a page, WooPayments will automatically appear as an option.
Please note that our support for the checkout block is still experimental and the following features of the gateway will probably not work:
* Using saved cards and saving cards.
* Integration with WooCommerce Subscriptions.

Unless I'm mistaken, these items are full of incorrect information. I'm pretty sure that:

  1. WooPayments is fully compatible with the Cart and Checkout Blocks.
  2. The Checkout Block is no longer a separate extension.

This section should either be heavily modified or deleted entirely.

Acceptance criteria

The above items are addressed in the readme.txt file.

@csmcneill csmcneill added good first issue The issue is a good candidate for the first community contribution/for a newcomer to the team. type: enhancement The issue is a request for an enhancement. labels Dec 24, 2024
@vbelolapotkov
Copy link
Collaborator

@csmcneill thanks for flagging those! I agree it would be nice to fix those, do you have edits suggestions? Asking because in order to fix those we'd come to your team eventually for preferred wording 🙂 So my suggestion to you would be to open a PR with changes, or share edited readme version (here or somewhere internally) so we could assist with merging the changes.

@vbelolapotkov vbelolapotkov added the focus: misc or unknown Issues that need to be added to a focus area (aka "needs focus"). label Dec 24, 2024
@aheckler
Copy link
Member

I can take a look when I'm back from AFK.

@aheckler aheckler self-assigned this Dec 24, 2024
aheckler added a commit that referenced this issue Jan 7, 2025
@haszari haszari added the focus: ops General (non dev) operations bugs and enhancements, not matching any other focus area label Jan 9, 2025
@haszari
Copy link
Contributor

haszari commented Jan 9, 2025

Marking this as ops focus since @aheckler is on it. Thanks Adam! If you want to flesh out an updated draft, that would be superb 🏅

@aheckler aheckler linked a pull request Jan 9, 2025 that will close this issue
@aheckler
Copy link
Member

aheckler commented Jan 9, 2025

This should have already been closed by #10096 Not sure why it didn't work.

@aheckler aheckler closed this as completed Jan 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
focus: misc or unknown Issues that need to be added to a focus area (aka "needs focus"). focus: ops General (non dev) operations bugs and enhancements, not matching any other focus area good first issue The issue is a good candidate for the first community contribution/for a newcomer to the team. type: enhancement The issue is a request for an enhancement.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants