#nickderobertis

1 messages · Page 1 of 1 (latest)

azure spadeBOT
dry shard
#

We already have this set up for regular cards, just not Apple/Google pay

compact perch
dry shard
#

Oh so we're not actually using SetupIntents, we are saving during the payment process with PaymentIntents

#

with regular cards, we are listening to the payment_intent.successful webhook, then we get the latest_charge and request the charge, then we get the payment method from payment_method_details.card_present.generated_card

#

With Apple/Google pay, we noticed this generated_card is null. But the payment_method still has an ID. That payment_method ID didn't work for plain card, but do you think it would work here?

compact perch
dry shard
#

Ah ok, got it. And this is a restriction unique to Terminal, correct? We were planning out a plain Apple/Google pay integration before and I thought you could save the cards with that.

compact perch
#

Correct - this is something specific for card-present transactions. With online card payments w/ wallets you're able to save them fine

dry shard
#

Ok got it, thanks. Are there plans to support this in the future for Terminal, or you have explicitly decided not to support this for legal or other reasons?

compact perch
#

I'd check in with support (https://support.stripe.com/contact) - I don't think there are specific legal reasons for the restriction, I think it's more of a technical/implementation challenge

#

But I'm not sure, and I don't know what the timeline would be if we did choose to support it

dry shard
#

Ok, that makes sense. Thanks for the info.