#Jkas
1 messages · Page 1 of 1 (latest)
Hi there, Apple Pay generates PaymentMethods yes
I'm seeing Apple Pay Sources with a src_ prefix.
Would you like an example?
I'm wondering if we're doing this wrong, if you think it should be an apple_pay should be a Payment Method.
src_1LhybmEkTO8kaKcKzNgYmRIQ
Here is also an andriod_pay that is stored (seemingly) as a source: src_1LhyYREkTO8kaKcKS5cEvKDL
Yep okay
So this was indeed via the Hosted Invoice Page
Which is different and does use our legacy APIs
So that's why you see a Source here
If you used Payment Request Button (the Web integration), for instance, then a PaymentMethod would be generated
Is there any harm in continuing to use the Hosted Invoice Page?
Nope not at all
Is there concern on your end with handling the different IDs?
Or are you just checking this is expected?
It just requires us to write more conditional code around how to handle sources vs methods on our backend. But really I just wanted to confirm that this is expected, since I know Stripe has somewhat deprecated Sources. Is updating the Hosted Invoice Page to generate Payment Methods on the roadmap at this time?
Not on the roadmap in the short-term as far as I'm aware.
I do recommend just handling both for now
Got it, thanks for your help!