Automattic / wp-calypso

The JavaScript and API powered WordPress.com
https://developer.wordpress.com
GNU General Public License v2.0
12.41k stars 1.98k forks source link

Simple Payments: Create Option to Customize Email Notifications #18644

Open hnotess opened 6 years ago

hnotess commented 6 years ago

Steps to reproduce

  1. Within the dialog that allows a user to edit their Simple Payments information, they have an option to select the PayPal-associated email address that should receive the payment, but no option to select the email address that will receive notification from WordPress.com.

What I expected

Working with a user planning to transfer site ownership, they found they were receiving email notifications about their clients' simple payments, with no option to change who receives those notifications.

What happened instead

The WordPress.com docs state:

WordPress.com will also send an email for each purchase. This email will be sent to the user’s email who created the button. You can also expect a monthly report for all your Simple Payment buttons. This email is sent to the site plan owner.

This suggests the button creator will continue receiving all the email notifications, even following a transfer of site ownership.

Browser / OS version

n/a

Screenshot / Video

https://cloudup.com/cQHoQILcNOU

Context / Source

user-report

The user was setting up a site for a client of theirs, including payment options setup, but planning to transfer site ownership. Additionally, they wanted the payments email notifications to go to a site member other than the site owner.

680818-hc

721892-zen

retrofox commented 6 years ago

Thanks Hannah for report this issue. Working on this.

iamtakashi commented 6 years ago

This is the approach we're taking; The payment email will be sent to the site owner if the button creator is no longer in the site. In this way, for a majority of cases, the site owner just need to remove the creator from the site. However, for the cases like this where the email needs to be sent another user other than the site owner, we will change it manually on a request basis.

sstabrizi commented 6 years ago

Here is another instance where not having the option to select an email has created an issue:

I am working with a user in chat who has set up several Simple Payments all over the site, but we're working on this page right now: https://peterthorneycroft.com/meditative-music/ - In each Simple Payment settings the user has set an email address as the email for the PayPal account. However, when a purchase is made an email that notifies the user that money was paid for a product is sent to the creator of the button, not the owner of the account.

The owner needs the email sent to their address, but won't be removing the creator of the 50+ Simple Payment buttons on the site.

Is this the place to make a request to manually change the email for all simple payment buttons on the site, or should I submit that request elsewhere?

(internal reference: 1633127-hc and 924713-zen)

iamtakashi commented 6 years ago

Is this the place to make a request to manually change the email for all simple payment buttons on the site, or should I submit that request elsewhere?

At the moment, we'll change manually the email address on a request basis as it's an edge case. Please DM me the email address and we'll take care of that.

spncr commented 5 years ago

2741601-hc

Another user requested today that we add an option to choose which email address the notification goes to, per button (product). As they build out more products and more sites, they want to be able to control this themselves.

github-actions[bot] commented 3 years ago

This issue is stale because it has been 180 days with no activity. You can keep the issue open by adding a comment. If you do, please provide additional context and explain why you’d like it to remain open. You can also close the issue yourself — if you do, please add a brief explanation and apply one of relevant issue close labels.

github-actions[bot] commented 2 years ago

This issue is stale because it has been 180 days with no activity. You can keep the issue open by adding a comment. If you do, please provide additional context and explain why you’d like it to remain open. You can also close the issue yourself — if you do, please add a brief explanation and apply one of relevant issue close labels.

katiebethbrown commented 2 years ago

This issue has been stale for some time, but I wanted to take a moment to revisit it to see if anything had changed in our approach since @iamtakashi's comment in 2018.

We've run into this on Team 51, where a site is developed by an account that is not the site owner. This means that the PayPal blocks are created by an author account that is not the actual donation recipient. The block creator does not need to receive emails for each donation, but their account will need to remain on the site. I'd imagine a similar situation exists any time the work on a site is done by a third-party and not the site owner directly, or where there are organizational changes that don't include removing the original creator completely, like the ownership transfer mentioned in the original issue.

How It Works Now: My current understanding is that each PayPal block is setup as a post using the custom post type jp_pay_product and we're selecting the address for the email by referencing the post_author from each of those posts.

Workaround: Based on that, it seems like the current workaround is to manually update the post_author field in the database for each of the PayPal blocks to reflect the account of the user the email should be going to. Is that the correct approach?

For future uses of the block: Are there plans on the roadmap to update the block to include an option for selecting the email that's used, or is the best approach going to be manually updating each block in the database to reflect the proper owner?

github-actions[bot] commented 2 years ago

This issue is stale because it has been 180 days with no activity. You can keep the issue open by adding a comment. If you do, please provide additional context and explain why you’d like it to remain open. You can also close the issue yourself — if you do, please add a brief explanation and apply one of relevant issue close labels.