#Jkas

1 messages · Page 1 of 1 (latest)

charred heronBOT
wary venture
#

Hi there, Apple Pay generates PaymentMethods yes

timid scaffold
#

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.

wary venture
#

Hmm is this via the Hosted Invoice Page?

#

Yes an example would be great

timid scaffold
#

src_1LhybmEkTO8kaKcKzNgYmRIQ

#

Here is also an andriod_pay that is stored (seemingly) as a source: src_1LhyYREkTO8kaKcKS5cEvKDL

wary venture
#

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

timid scaffold
#

Is there any harm in continuing to use the Hosted Invoice Page?

wary venture
#

Nope not at all

#

Is there concern on your end with handling the different IDs?

#

Or are you just checking this is expected?

timid scaffold
#

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?

wary venture
#

Not on the roadmap in the short-term as far as I'm aware.

#

I do recommend just handling both for now

timid scaffold
#

Got it, thanks for your help!