search

Automattic / woocommerce-payments

Accept payments via credit card. Manage transactions within WordPress.
https://wordpress.org/plugins/woocommerce-payments/
Other
173 stars 69 forks source link

Remove BNPL options in WooCommerce core > Additional payments options #8603

Closed vladolaru closed 2 months ago

vladolaru commented 5 months ago

Description

In line with this issue (https://github.com/Automattic/woocommerce-payments/issues/8578) related to the WooPayments Connect-in-core page, we should not show options that WooPayments already provides when merchants click on the Set up additional payment options task list.

Screenshot 2024-04-09 at 16 47 34

Acceptance criteria

Designs

cc @elizaan36 if more design work is needed

Testing instructions

  1. Make sure you have WooPayments set up with a connected account
  2. Click on the Set up additional payment options task item in the Things to do next list of the WooCommerce home page
  3. There should not be BNPL options provided by WooPayments (in the Payments > Settings page), regardless if they are enabled or not.

Dev notes

We should be informed by the actual capabilities of the connected merchant account, the same way the Payments > Settings page is. This would make our logic resilient to various per-country payment options. This would also require us to dynamically parse the list of recommended additional payments options shown in the WC core page.

Additional context

https://github.com/Automattic/woocommerce-payments/issues/8578

cc @pierorocca @timmy5685 @anu-rock

pierorocca commented 5 months ago

To double check, has anyone reached out to Partnerships in case those placements are tied to commercial agreements? Would be good due diligence to conduct.

vladolaru commented 5 months ago

@pierorocca I've pinged Payments Partnerships here: p1712749196233489-slack-CSPAQH38F

pierorocca commented 5 months ago

Nice @vladolaru. Looks like a healthy discussion got triggered. :)

anu-rock commented 5 months ago

@vladolaru Is this something we are still pursuing? Looks like the discussion on Slack has stalled.

vladolaru commented 5 months ago

I don't have any update about it. Maybe @timmy5685 has an update about it.

timmy5685 commented 4 months ago

@anu-rock - catching up on this thread. Just followed up on slack to summarize what I think I understand to get final confirmation from the team. Standby.

elizaan36 commented 4 months ago

as long as it is overtly clear to the merchant that one or all of the additional payment methods (BNPLs) are available (but not enabled) or already enabled within WooPayments, then you can remove the duplication.

Building off Web's comment in Slack, we could potentially direct people through the WooPayments APM setup from this core task as well.

Here are a couple options. Copy TBD, just to illustrate the concept. Let me know what you think.

1.

Payments _ WooCommerce Payments 1
  1. Payments _ WooCommerce Payments 2
anu-rock commented 4 months ago

I like how @elizaan36's Option 1 above hits two targets with one rock - remove confusion related to BNPLs and make WooPayments the very obvious pick (I have to say that banner is quite attractive 😄).

pierorocca commented 4 months ago

In both options, I'm not clear why any WooPayments payment methods would be in this flow. I'd expect WooPayments payment methods to only be within an amazing WooPayments flow.

timmy5685 commented 4 months ago

@elizaan36 - similar to unsupported countries - let's include this in our overall onboarding review!

vladolaru commented 4 months ago

Great ideas, @elizaan36! For clarity, those WooPayments tiles will appear when WooPayments is already activated and properly onboarded, linking to the WooPayments Payments > Settings page, right?

elizaan36 commented 4 months ago

those WooPayments tiles will appear when WooPayments is already activated and properly onboarded

Thanks @vladolaru. Correct, these tiles only appear once WooPayments is connected and enabled and the user makes their way back to the "Set up additional payments" task on Woo Home.

linking to the WooPayments Payments > Settings page, right?

The thinking is that the tiles would replicate the behavior of the "Set up additional payments" task that appears only on the Payments Overview. It currently leads to the guided payment method setup.

New merchants - Enable local payment methods

If we decide in the future to remove the guided setup the tasks would lead to settings.

@timmy5685, Orcun and I are taking a look at the overall onboarding review and will include this path.

anu-rock commented 3 months ago

@elizaan36 I saw in pe69sR-1ot-p2#comment-1095 that this issue is ready for engineering. Confirming it is no longer blocked and we can pull it in an upcoming sprint?

elizaan36 commented 3 months ago

I'd confirm with @timmy5685 but I think this should be done relatively soon because it solves a usability issue with confusion on duplicate payment methods.

The only thing I'd like to do is align the visual design and messaging with @orcunomattic 's latest work in pfHfG4-cO. Will reach out on the latest in Figma to align on this.

vladolaru commented 3 months ago

@elizaan36 @timmy5685 Could we get an update on the latest state of things here?

timmy5685 commented 3 months ago

@anu-rock @vladolaru - thanks for the patience. @orcunomattic and I caught up on this today and we are good to move forward with this.

Here is the final version of the page from @orcunomattic:

Set up payments task B

Figma: VLWDmeuIXQ7XAK4flyqTFO-fi-2566_58764

Criteria: WooPayments is installed and enabled.

Expected behavior:

  1. Clicking "Set up additional payment options" from the WooCommerce "Things to do next" list brings you to the page above.
  2. Clicking get started brings you to the same page as when you click "Set up additional payments" on the payments overview page: image

Let me know if you have any questions. cc: @elizaan36

vladolaru commented 3 months ago

Thank you for sharing these details @timmy5685. A couple of questions:

Criteria: WooPayments is installed and enabled.

Isn't the criteria also that WooPayments has a connected Stripe account (aka is fully setup)? Because without a working account there will be no way to enable BNPLs. Or maybe enabled means our current understanding of connected.

I see there is a "Get started" CTA and a "Dismiss" button. I assume the "Dismiss" button will permanently hide the section and BNPL payment gateways recommendations will remain hidden. Could we NOT make this dismissable? The same way all the other payment gateways recommendations are NOT dismissable?

timmy5685 commented 2 months ago

Isn't the criteria also that WooPayments has a connected Stripe account (aka is fully setup)? Because without a working account there will be no way to enable BNPLs. Or maybe enabled means our current understanding of connected.

@vladolaru - yes. sorry for the confusion. When I said enabled - I meant fully connected.

Could we NOT make this dismissable? The same way all the other payment gateways recommendations are NOT dismissable?

Great callout and I agree. @orcunomattic can we remove the dismiss?

vladolaru commented 2 months ago

Excellent, @timmy5685! This makes the logic simpler and clearer.

orcunomattic commented 2 months ago

I updated it, you can view it here on Figma: VLWDmeuIXQ7XAK4flyqTFO-fi-2566_58764

@vladolaru, do you need me to export any assets? Let me know.

vladolaru commented 2 months ago

Due to unforeseen complexities, I am bumping the estimate from 2️⃣ to 3️⃣

vladolaru commented 2 months ago

@orcunomattic I've pinged you in the WooCommerce core PR for design review.