Hello Joost
I just opened a ticket via “request-support”.
I think it would be good to try out your beta package but bevore doing so i received another email from PP support.
This is really getting to deep for me but can you juge if the PP tech analysis is “talking” about the same fault we are seeing here?
`I was able to pull up the webhook notification for the payment token that was created (from the woocommerce logs you provided earlier), and found the following:
“event_type”: “VAULT.PAYMENT-TOKEN.CREATED”,
“summary”: “A payment token has been created.”,
“resource”: {
“time_created”: “2022-09-08T00:23:51.941Z”,
“links”: [
{
“href”: “https://api.paypal.com/v2/vault/payment-tokens/kjgmwn5”,
“rel”: “self”,
“method”: “GET”,
“encType”: “application/json”
},
{
“href”: “https://api.paypal.com/v2/vault/payment-tokens/kjgmwn5”,
“rel”: “delete”,
“method”: “DELETE”,
“encType”: “application/json”
},
{
“href”: “https://api.paypal.com/v2/vault/approval-tokens/73E41510S7056193J”,
“rel”: “approval_token”,
“method”: “GET”,
“encType”: “application/json”
}
],
“source”: {
“paypal”: {
“payer”: {
“email_address”: “REDACTING CUSTOMER INFO”,
“payer_id”: “Y9YWKJ6ULZ7S2”
}
}
},
“id”: “kjgmwn5”,
“customer_id”: “REWCPP-a2d65b9550136”,
“status”: “CREATED”
This is the notification from the token that was created and vaulted. Are you able to use the URL in a GET call (https://api.paypal.com/v2/vault/payment-tokens/kjgmwn5) to see the tokenized information? In the details here, we can see that the customer ID is passed as “REWCPP-a2d65b9550136” . When I pull the logs from the section where you saw the “Payment for subscription parent order #10767 was not saved on PayPal.”, I see this in the request to GET the details back “CUSTOMER_ID=REWCPP-34”.
It looks like for some reason, the request is not being sent to us with the correct customer ID, and that was causing a response in our logs of “reason_code=INVALID_RESOURCE_ID”.
It looks like the payment information was being saved in the vault, however the follow up requests to use that was not using the same resource ID. This would be something I’d recommend trying to get the WooCommerce support to look at.
I’m seeing your account is configured for this, but the details in the request aren’t matching the saved ID from the initial vault request.`
I dont want to install a beta package if it doesnt solve my issue ??
Thanks
