# Collect and save payment details for future use

Use your Stripe Terminal integration to collect and save payment methods for returning customers.

Use Stripe Terminal to collect and save *payment methods* ( NFC-based [mobile wallets](https://docs.stripe.com/payments/wallets.md)) for online reuse. Use an in-person payment to initiate an online *subscription* using [Billing](https://docs.stripe.com/billing.md), save payment details to a customer’s online account, or defer payment.

## Collect and save reusable payment details 

You can collect reusable payment details and save them for online use with Terminal:

- [Directly, without charging the payment method](https://docs.stripe.com/terminal/features/saving-payment-details/save-directly.md)
- [After payment](https://docs.stripe.com/terminal/features/saving-payment-details/save-after-payment.md)

## Create a reusable PaymentMethod 

When you create a PaymentIntent or SetupIntent with a card-present payment method, you can’t save the PaymentMethod directly. However, in most cases, Stripe can create a reusable `generated_card` PaymentMethod using the payment information. It represents the same payment method and can be reused for online payments.

## Charge a saved PaymentMethod 

You can charge customers at a later date using payment details that were saved during an earlier transaction.

[Create and confirm a PaymentIntent](https://docs.stripe.com/api/payment_intents/create.md#create_payment_intent-payment_method) with the saved payment method.

To [save a card from a Terminal PaymentIntent](https://docs.stripe.com/terminal/features/saving-payment-details/save-after-payment.md), attach the `generated_card` PaymentMethod to a Customer. This allows you to reuse it without having to collect payment details again. If you attach a PaymentMethod to a PaymentIntent without also attaching the PaymentMethod to a Customer, you won’t be able to reuse the Payment Method in future transactions.

## Charge customers outside the checkout flow 

If the customer isn’t in your checkout flow when you charge the customer, set [off_session](https://docs.stripe.com/api/payment_intents/confirm.md#confirm_payment_intent-off_session) to `true`. This causes the PaymentIntent to throw an error if customer authentication is required.

```bash
curl https://api.stripe.com/v1/payment_intents \
  -u <<secret key>>: \
  -d "payment_method_types[]"="card" \
  -d "amount"=1099 \
  -d "currency"="{{terminal.localized_currency}}" \
  -d "customer"="{{CUSTOMER_ID}}" \
  -d "payment_method"="{{PAYMENT_METHOD_ID}}"
```

```ruby
<<setup key>>

Stripe::PaymentIntent.create({
  payment_method_types: ['card'],
  amount: 1099,
  currency: '{{terminal.localized_currency}}',
  customer: '{{CUSTOMER_ID}}',
  payment_method: '{{PAYMENT_METHOD_ID}}',
})
```

```python
<<setup key>>

stripe.PaymentIntent.create(
  payment_method_types=['card'],
  amount=1099,
  currency='{{terminal.localized_currency}}',
  customer='{{CUSTOMER_ID}}',
  payment_method='{{PAYMENT_METHOD_ID}}',
)
```

```php
<<setup key>>

\Stripe\PaymentIntent::create([
  'payment_method_types' => ['card'],
  'amount' => 1099,
  'currency' => '{{terminal.localized_currency}}',
  'customer' => '{{CUSTOMER_ID}}',
  'payment_method' => '{{PAYMENT_METHOD_ID}}',
]);
```

```java
<<setup key>>

PaymentIntentCreateParams params =
  PaymentIntentCreateParams.builder()
    .setAmount(1099L)
    .setCurrency("{{terminal.localized_currency}}")
    .addPaymentMethodType("card")
    .setCustomer("{{CUSTOMER_ID}}")
    .setPaymentMethod("{{PAYMENT_METHOD_ID}}")
    .build();

PaymentIntent.create(params);
```

```javascript
<<setup key>>

const paymentIntent = await stripe.paymentIntents.create({
  payment_method_types: ['card'],
  amount: 1099,
  currency: '{{terminal.localized_currency}}',
  customer: '{{CUSTOMER_ID}}',
  payment_method: '{{PAYMENT_METHOD_ID}}',
});
```

```go
<<setup key>>

params := &stripe.PaymentIntentParams{
  PaymentMethodTypes: stripe.StringSlice([]string{
    "card",
  }),
  Amount: stripe.Int64(1099),
  Currency: stripe.String({{terminal.localized_go_currency}}),
  Customer: stripe.String("{{CUSTOMER_ID}}"),
  PaymentMethod: stripe.String("{{PAYMENT_METHOD_ID}}"),
}
paymentintent.New(params)
```

```csharp
<<setup key>>

var options = new PaymentIntentCreateOptions
{
    PaymentMethodTypes = new List<string> { "card" },
    Amount = 1099,
    Currency = "{{terminal.localized_currency}}",
    Customer = "{{CUSTOMER_ID}}",
    PaymentMethod = "{{PAYMENT_METHOD_ID}}",
};
var service = new PaymentIntentService();
service.Create(options);
```

When charging a saved card, you can’t use the [confirmPaymentIntent](https://docs.stripe.com/terminal/payments/collect-card-payment.md#confirm-payment) method. Payments with generated cards are online payments and can’t be processed with Terminal SDK methods.

## Track customer behavior with card fingerprints 

Use the Stripe API to recognize repeat customers across online and retail channels by correlating transactions by the same card. Like `card` payment methods, each `card_present` payment method has a [fingerprint](https://docs.stripe.com/api/payment_methods/object.md#payment_method_object-card-fingerprint) attribute that uniquely identifies a particular card number. Cards from [mobile wallets](https://docs.stripe.com/payments/wallets.md) (for example, Apple Pay or Google Pay) don’t share a fingerprint with cards used online.

Starting with [API version 2018-01-23](https://docs.stripe.com/upgrades.md#2018-01-23), Connect platforms see a fingerprint on `card_present` and `card` PaymentMethods that’s uniform across all connected accounts. You can use this fingerprint to look up a specific card’s charges in a connected account.

## Compliance 

You’re responsible for your compliance with all applicable laws, regulations, and network rules when saving a customer’s payment details. For example, the European Data Protection Board has issued guidance regarding saving payment details. These requirements generally apply if you want to save your customer’s payment method for future use, such as presenting a customer’s payment method to them in the checkout flow for a future purchase or charging them when they’re not actively using your website or app.

Add terms to your website or app that state how you plan to save payment method details and allow customers to opt in. If you plan to charge the customer while they’re offline, then at a minimum, make sure that your terms also cover the following:

* The customer’s agreement to your initiating a payment or a series of payments on their behalf for specified transactions.
* The anticipated timing and frequency of payments (for instance, whether charges are for scheduled installment or subscription payments, or for unscheduled top-ups).
* How the payment amount is determined.
* Your cancellation policy, if you’re setting up the payment method for a subscription service.

Make sure you keep a record of your customer’s written agreement to these terms.

When you save a payment method, it can only be used for the specific usage that you included in your terms. If you want to charge customers when they’re offline and also save the customer’s payment method to present to them as a saved payment method for future purchases, you must explicitly collect consent from the customer. One way to do so is with a “Save my payment method for future use” checkbox.