Skip to content

Release testing instructions for WC Payments 4.0.0

Anurag Bhandari edited this page Mar 30, 2022 · 4 revisions

Exclude Level3 data when capturing a terminal payment

Expected outcome

We currently collect level 3 data for payments captured via terminal (in-person payments). This is no longer required. This change aims to exclude level 3 data while capturing a terminal payment.

Testing instructions

In-person payment
  • Create a new order in WooCommerce with "Cash on delivery" as the payment method.

  • Create a payment intent in Stripe Dashboard at https://dashboard.stripe.com/test/connect/accounts/<account_id>/payments/new. Make sure to have the "Capture funds later" option selected under "Manually enter card information."

  • Make a POST request to /payments/orders/<order_id>/capture_terminal_payment. Refer the docs to set up authorization correctly.

  • On the intent details page https://dashboard.stripe.com/test/connect/accounts/<account_id>/payments/<intent_id>, scroll down to the "Events and logs" section. In the latest event data, verify that level3 is null.

Capture later payment
  • On the page WP Admin → Payments → Settings, check the option "Issue an authorization on checkout, and capture later." This will force all payments on the site to be captured later instead of right away.

  • Create a new order in WooCommerce with "Credit card" as the payment method. After successfully checking out, notice that money from the card is not deducted yet.

  • Go to the detail page (in WP Admin) for the just-created order. The status of this order should be "On hold," indicating that the payment hasn't been captured yet.

  • You will also see this message in order notes: "A payment of $18.00 USD was authorized using WooCommerce Payments (intent_id)". Take a note of this intent id.

  • From the "Order actions" dropdown in the right sidebar, select the "Capture charge" option.

  • On the intent details page https://dashboard.stripe.com/test/connect/accounts/<account_id>/payments/<intent_id>, scroll down to the "Events and logs" section. In the latest event data, verify that level3 is populated with some data.

Clone this wiki locally