• Resolved Philip Sola

    (@philsola)


    I am looking at using WooCommerce for a headless WordPress build coming up, and in particular the new StoreAPI to handle the cart and checkout experience.

    On the official WooCommerce GitHub documentation on the attached link, they give an example of the POST request data you would need to send the endpoint to process the order. One of the parameters is a payment_data array of objects.

    On The official WooCommerce documentation for the Store API, they suggest reaching out to the authors of the payment gateway plugins you’re working with for further information.

    I have to submit an array for payment_data with the POST request but I can’t find anywhere what this array would be for this plugin using PayPal.

    Many thanks,

    Phil

    • This topic was modified 4 months, 2 weeks ago by Philip Sola.

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter Philip Sola

    (@philsola)

    Hi,

    It’s been quite a few days with no response, I was wondering if I could get some support please?

    Thanks,

    Phil

    Plugin Author Payment Plugins

    (@mrclayton)

    Hi @philsola

    You can see all of the data and keys that are sent in the WooCommerce checkout request by opening your browser’s developer tools and capturing the network request data. That will show you ever key used by the plugin.

    You can will notice there are 3 keys, one for the PayPal order ID, one for the billing token if a billing agreement is needed, and the the 3rd which designates if the customer is saving their payment method. The 3rd key is not used by the plugin and is generated by WooCommerce.

    Kind Regards

    Thread Starter Philip Sola

    (@philsola)

    Thanks @mrclayton for the response and screenshot. I’ve been able to successfully hook this up and process payments both in sandbox and production mode which is great.

    Many thanks,

    Phil

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.