Save card details after payment

You can’t reuse the card_present PaymentMethod from an in-person transaction, but in most cases you can create a reusable generated_card PaymentMethod that represents the same card. From your customer’s perspective, they’re the same payment method.

Request a generated_card when you create a PaymentIntent by specifying a value for setup_future_usage. If the card supports being saved for future payments, successfully processing or confirming the payment returns the generated_card ID. If the PaymentIntent has an associated Customer, the generated_card automatically attaches to that Customer. If not, then you can manually attach it to a Customer later.

When you request a generated_card, always verify that the PaymentIntent.latest_charge contains a generated_card. In some cases, such as when using certain cards stored in digital wallets, a successful payment doesn’t create a generated_card. If that happens, and you require a generated_card, you have two options:

• Prompt the cardholder to save a different card using the flow to save a card without taking a payment.
• Refund the in-person payment, indicate that the transaction failed, and instruct the cardholder to use a different card.

The initial, in-person payment benefits from liability shift and, in certain markets, lower pricing for standard Terminal payments. However, subsequent payments using the generated_card are card-not-present online transactions. For example:

• A gym customer pays in person for an initial session and a membership subscription. The transaction sets up a generated_card to use for future automatic membership renewals.
• A customer at a clothing store provides their email address when making a purchase at the checkout counter. The transaction creates a customer record and an associated generated_card. That allows the customer to log into the store’s website later and place an order using the same card.

Client-side

With the iOS, Android, and React Native SDKs, you can create a PaymentIntent client-side and provide customer and set setup_future_usage.

Server-side

The JavaScript SDK and server-driven integration require you to create the PaymentIntent on your server. For iOS or Android, you can create the PaymentIntent on your server if the information required to start a payment isn’t readily available in your app.

curl https://api.stripe.com/v1/payment_intents \
  -u "
sk_test_4eC39HqLyjWDarjtT1zdp7dc
:" \
  -d "payment_method_types[]"=card_present \
  -d amount=1099 \
  -d currency=usd \
  -d customer={{CUSTOMER_ID}} \
  -d setup_future_usage=off_session

You can retrieve the saved card details by listing the card payment methods associated with that customer.