#taylorbrooks-paymentmethod-attach
strong narwhal
@arctic vale you can't do that. card_present PaymentMethods are single use. So that's not how it works
Instead, we generate a separate card PaymentMethod that is re-usable. See https://stripe.com/docs/terminal/features/saving-cards#saving-payment-intent-card
arctic vale
Interesting, so would the "off_session" payment intent be separate from the payment intent used for card_present?
strong narwhal
They have to. Each PaymentIntent represents the attempt to collect one specific payment. Once it succeeds it's a terminal state, to take another payment, you create a separate PaymentIntent
arctic vale
"You can automatically attach the generated_card PaymentMethod to a customer object to easily retrieve saved card details in the future. When creating a PaymentIntent, provide a customer id and set the setup_future_usage parameter to indicate you intend to make future payments with the payment method."
How do I attached the generated_card to a customer?
strong narwhal
what have you tried? You copied the doc text but did you try? Do you have a successful card present PaymentIntent? What do you see and what's blocking you?
arctic vale
What are you asking me to try?
strong narwhal
What is documented
There are many different ways to integrate. I'm trying to understand where you are blocked and what you tried
for example you redacted the request id above so I can't look at it, trying to grasp what you are doing exactly
arctic vale
req_QiBaUXJGhyadtF
strong narwhal
Okay so that request was a PaymentIntent confirmation call via Terminal. It charged the customer's card and that's it. It never generated a card PM for you since you didn't pass setup_future_usage as recommended in the doc
arctic vale
Is there a default value for setup_future_usage ?
arctic vale
Does choosing null or "off_session" have an effect on the interchange rate?
strong narwhal
no change on the interchange rate. But passing off_session or on_session will let you get a saved card for future one-off payments
arctic vale
Is there a downside to always passing "off_session"?
strong narwhal
no
arctic vale
I think I understand the terms of "off_session" and "on_session" but I don't understand how things behave differently depending upon the values that are set.
strong narwhal
https://stripe.com/docs/api/payment_intents/create#create_payment_intent-setup_future_usage is our documentation for this. Overall it's all about how you plan to charge the customer's card again in the future. Are you always going to have them pay when they visit your website and order new things, or might you charge them without any action from them. That informs which enum value to use
arctic vale
pi_3Jv8t5LMHLcGMW3Q0JzBLQV0
I setup a PI with "off_session" as the under setup_future_usage and I still get a null value for generated_card
strong narwhal
looking
okay you seem to be using tap instead of inserting the card and in that case the card can't be saved
arctic vale
interesting.
I want to restate to make sure I understand this correctly.
If you use Apple Pay as part of a digital wallet or you use a RFID from a card, those payment methods will be unavailable for future use.
Is that correct?
strong narwhal
correct