evan-paypal-paymentmethod

[pearl adder]

Instead I think I should expect the payer_email to be fake.example.com or something like that

this is an example PM id pm_1NpbyvD9sYh65PYtp3WB4ZKS

[sage ibex]

And where exactly are you looking / expecting to see these values?

Is there a docs reference you can share that points to these?

[pearl adder]

I am basically retireving the payment method in the API so I can get more info about the payment method, like the card brand, last4, and payer email if it was a paypal PM.

[sage ibex]

Oh i see the null fields in the paypal hash now yea

[pearl adder]

So they can not be retireved ?

[sage ibex]

Looking now about whats expected here

Hmm seems like we should get a random payer_id but blank email

[pearl adder]

my integration follows this https://stripe.com/docs/payments/finalize-payments-on-the-server?platform=web&type=subscription#create-and-submit-payment

[sage ibex]

I wonder if this is related to the payment method creation flow, trying on my own integration

[pearl adder]

Yeah I thing am getting them after I confirm the intent on the client

but they are not there before confirming the intent

[sage ibex]

ok, yea, i see the same PM you shared now looks like it has a payer_id after you confirmed the PI

[sage ibex]

Ok poked at this a bit more, and a piece i'd missed what when using createPaymentMethod to get the paypal Payment Method, the server-confirmed PI goes to requires_action status and you need to redirect to the URL (next_action.redirect_to_url.url) to authorize the payment, after that the test payer details are populated on the PM