Pickup card — The issuer wants the card seized at point-of-sale.
Usually fraud-related. The card is dead.
| Retry strategy | Don't retry |
|---|---|
| Customer-facing action | Send a card-update flow |
| Recovery rate (retry only) | ~0% |
| Recovery rate (with customer flow) | ~65% |
Card-update flow. Don't retry.
The recommended Stripe Customer Portal session for the recovery flow:
session = stripe.billing_portal.Session.create(
customer=customer_id,
return_url="https://yourapp.com/billing/thanks",
flow_data={"type": "payment_method_update"},
)
update_link = session.url
pickup_card is one of dozens of decline codes Stripe returns; recovery rates vary by code by 5x or more. The recovery-rate reference covers the full set; the card-update flow article covers the customer-facing side; dunning emails covers how to write the messages.
DunningKit's open-source CLI parses your Stripe failed-charges CSV and gives you the breakdown by code, with recoverable-revenue estimates. pip install dunningkit.