# Karte

Erfahren Sie mehr über Kartenablehnungen und wie Sie Ihre Ablehnungsquote senken können.

Kartenzahlungen können aus verschiedenen Gründen fehlschlagen. Zu den häufigsten gehören:

- **Insufficient funds:** If a customer has insufficient funds or credit, the card issuer declines the transaction. To help minimize declines due to insufficient funds, consider adding a [buy now, pay later (BNPL)](https://docs.stripe.com/payments/buy-now-pay-later.md) option.

- **Incorrect card data:** If a customer enters an incorrect card number, CVC, or expiration date, the card issuer might decline the transaction. In these cases, ask your customer to re-enter their card information.

- **Fraudulent activity:** If a card issuer suspects fraudulent activity, which can be triggered by large purchases or a large volume of transactions over a short period of time, they might decline payments. Your customer must resolve this issue by communicating with their card issuer and confirming their identity.

Use [Stripe Sigma](https://docs.stripe.com/data.md) to analyze your decline rate. Its interactive SQL reporting environment offers prebuilt queries for this purpose. To investigate declines outside Sigma, consider the `Card` object [fingerprints](https://docs.stripe.com/api/cards/object.md#card_object-fingerprint) instead of charge IDs to exclude repeat attempts.

## Kartenablehnungen

Wenn der Kartenaussteller Ihres Kunden/Ihrer Kundin eine Abbuchung erhält, entscheiden dessen automatisierte Systeme und Modelle über die Autorisierung. Diese Tools analysieren Signale wie Ausgabegewohnheiten, Kontostand und Kartendaten, einschließlich Ablaufdatum, Adressinformationen und CVC.

If the card issuer declines a payment, Stripe shares some of the decline information it receives. This information is available in the Dashboard and through the API. Sometimes, issuers provide specific explanations, such as an incorrect card number or low funds. Stripe shows these as [decline codes](https://docs.stripe.com/declines/codes.md).

Card issuers categorize most declines as generic ([generic_decline](https://docs.stripe.com/declines/codes.md#generic_decline)), making the exact decline reason unclear. If the card information is correct, ask your customer to contact their card issuer to understand why a transaction was declined. For privacy and security reasons, card issuers discuss the specifics of a decline only with their cardholders.

### Netzwerkcodes

Bei einer Ablehnung stellt der Kartenaussteller zwei Arten von Netzwerkcodes zur Verfügung:

- **Network decline code:** The card network provides this 2-4 digit code. When Stripe doesn’t receive a response code from the card network for a declined charge, the `network_decline_code` field is null. The meaning of a code differs based on the card network. For this reason, take the card’s brand into consideration when interpreting the code.

- **Network advice code:** The card network provides this 2-4 digit code. The code offers guidance on managing a decline. When Stripe doesn’t receive a response code from the card network for a declined charge, the `network_advice_code` field is null. The meaning of a code differs based on the card network. For this reason, take the card’s brand into consideration when interpreting the code. Mastercard refers to network advice codes as Merchant Advice Codes (MAC).

## Kartenablehnungen reduzieren

Sie können Ablehnungen des Kartenausstellers, die auf ungenaue Kartenangaben (zum Beispiel eine inkorrekte Kartennummer oder ein falsches Ablaufdatum) zurückzuführen sind, in der Regel beheben, indem Sie Ihre Kundinnen/Kunden bitten, den Fehler zu korrigieren oder eine andere Karte oder Zahlungsmethode zu verwenden. [Checkout](https://docs.stripe.com/payments/checkout.md) gibt dem Kunden/der Kundin beispielsweise Feedback, wenn eine Karte abgelehnt wird, und ermöglicht ihm/ihr, es erneut zu versuchen.

To avoid declines that stem from suspected fraudulent activity, ask your customers to provide their CVC and postal code during checkout. The impact of other data that you gather, such as the full billing address, might vary by card brand and country. If you continue to see elevated decline rates, Stripe recommends collecting extra customer information. You can also implement [3D Secure](https://docs.stripe.com/payments/3d-secure.md) to authenticate payment, which can lower decline rates in countries that support it.

For a clear insight into why the card issuer declined the card during generic or [do_not_honor](https://docs.stripe.com/declines/codes.md#do_not_honor) declines, examine the associated data. For example, if CVC or Address Verification Service (AVS) checks fail when your customer adds a card, ask your customer to verify both of these details before initiating another charge.

Wenn Sie feststellen, dass eine Kundin/ein Kunde eine in einem Land ausgestellte Karte verwendet, während er/sie von einer IP-Adresse in einem anderen Land aus operiert, könnte es sich um eine legitime Ablehnung aufgrund möglicher nicht autorisierter Kartennutzung handeln. Es kann jedoch zu Ausnahmen kommen, insbesondere wenn Kundinnen/Kunden international unterwegs sind und ihre Karten an verschiedenen Standorten nutzen.

### Arten von Karteneinschränkungen

Some customers find that their card has restrictions on the types of purchasable items. *FSA or HSA* (Flexible Spending Account or Health Savings Account debit cards use pre-tax funds to cover certain types of purchases, such as medical expenses. Their use is restricted only to businesses that directly provide eligible products and services) cards are often limited to certain types of businesses (for example, healthcare providers), so card issuers decline any other type of purchase. Additionally, some card issuers might not allow purchases from certain countries or outside of their own. In either case, your customer must contact their card issuer to inquire about potential restrictions.

### Auswirkungen des geografischen Standorts

If your customers use cards issued in a different country than where you registered your Stripe account, they might see an increased rate of declines. To resolve this, your customer must contact their card issuer to authorize the charge. If you have a global customer base with concentrations in various locations, you might want to set up Stripe accounts in larger markets, or in regions that encounter higher decline rates. This allows you to process charges locally.

## Abgelehnte Kartenwiederholungen

Wenn eine Zahlung abgelehnt wird, bietet Stripe einen Grund für die Ablehnung an und schlägt kurz einen Lösungsweg vor.
![Zahlung aufgrund unzureichender Deckung abgelehnt](https://b.stripecdn.com/docs-statics-srv/assets/declined-payment-dashboard.5fb1d634ab6b87c89db2c0078e076393.png)

Zahlung aufgrund unzureichender Deckung abgelehnt

If you’re a [Stripe Billing](https://docs.stripe.com/billing.md) user, you can create a custom retry schedule for subscriptions. Use [Smart Retries](https://docs.stripe.com/invoicing/automatic-collection.md#smart-retries) to choose the best times to retry failed payment attempts. Be aware that card networks limit the number of times you can reattempt a single charge. Stripe recommends a maximum of eight retries for charges that permit retries. Card issuers might see creating additional retries as potential fraud, which can result in increased declines for legitimate charges.

In the API, the [reason](https://docs.stripe.com/api.md#charge_object-outcome-reason) in the [outcome](https://docs.stripe.com/api/charges/object.md#charge_object-outcome) uses decline codes to tell you why the card issuer declined the authorization. The [advice_code](https://docs.stripe.com/api.md#charge_object-outcome-advice-code) in the `outcome` tells you what to do next.

| Hinweiscode | Nächste Schritte |
| --- | --- |
| `do_not_try_again` | Die Karte wurde abgelehnt, und Sie sollten sie nicht für die gleiche Transaktion erneut verwenden. | See the decline code for the reason why the card issuer declined the authorization. Your customer might need to contact their card issuer for more information. |
| `try_again_later` | Der Kartenaussteller hat die Transaktion abgelehnt, aber Sie können sie [erneut versuchen](https://docs.stripe.com/declines/card.md#retrying-issuer-declines). | Bitten Sie den/die Kund/in um einen erneuten Zahlungsversuch. Wenn nachfolgende Zahlungen ebenfalls abgelehnt werden, muss der/die Kund/in sich bezüglich weiterer Informationen an seinen/ihren Kartenaussteller wenden. |
| `confirm_card_data` | Der Kartenaussteller hat die Transaktion abgelehnt, da einige der angegebenen Informationen falsch sind. | See the decline code for the reason why the card issuer declined authorization. The customer needs to validate the information on their card. |

## Ablehnungen programmgesteuert verwalten

Es gibt mehrere Möglichkeiten, Ablehnungen programmgesteuert zu handhaben:

- Retrieve the `decline_code` property of [last_payment_error](https://docs.stripe.com/api/payment_intents/object.md#payment_intent_object-last_payment_error) from the [PaymentIntent](https://docs.stripe.com/api/payment_intents/object.md) object to see why the card issuer declined the payment attempt.
- Durchlaufen Sie die [Zahlungsversuche](https://docs.stripe.com/payments/payment-intents/verifying-status.md#identifying-charges) des PaymentIntents erneut und untersuchen Sie die [Fehlermeldung](https://docs.stripe.com/api/charges/object.md#charge_object-failure_message).
- Verwenden Sie [Webhooks](https://docs.stripe.com/payments/payment-intents/verifying-status.md#webhooks), um Statusaktualisierungen des PaymentIntent zu überwachen. Das Ereignis `payment_intent.payment_failed` wird zum Beispiel ausgelöst, wenn ein Zahlungsversuch nicht erfolgreich war.

Möglicherweise müssen Sie auch zusätzliche Situationen mit fehlgeschlagenen Zahlungen handhaben, zum Beispiel wenn Ihr Kunde/Ihre Kundin während des Bezahlvorgangs anwesend (On-Session) oder abwesend (Off-Session) ist. Wenn Sie Ihre Integration entwickeln, empfiehlt Stripe, alle möglichen API-Ausnahmen zu handhaben, einschließlich unerwarteter [Fehler](https://docs.stripe.com/error-codes.md).

> Stripe Billing handles many of these payment failure scenarios with features like [Automatic Collection](https://docs.stripe.com/invoicing/automatic-collection.md) and [Hosted Invoices](https://docs.stripe.com/invoicing/hosted-invoice-page.md).

### Abgelehnte Zahlungen On-Session

Wenn Ihr/e Kund/in während des Bezahlvorgangs Ihrer Website oder Anwendung anwesend ist, fordern Sie ihn/sie auf, es erneut mit seiner/ihrer Zahlungsmethode zu versuchen oder fragen Sie nach einer neuen Zahlungsmethode.

### Abgelehnte Zahlungen Off-Session

If your customer isn’t available to make a payment or update a payment method, notify them (for example, send them an email or in-app notification) to visit your website or application. If your business is affected by regulations like [Strong Customer Authentication](https://docs.stripe.com/strong-customer-authentication.md), payment attempts might also require authentication and fail with an `authentication_required` decline code. For more information on handling these scenarios, see [off-session payments with saved cards](https://docs.stripe.com/payments/save-during-payment.md?platform=web&payment-ui=elements#charge-saved-payment-method).

## See also

- [Ablehnungscodes](https://docs.stripe.com/declines/codes.md)
- [Zahlungsanfechtungen und Betrug](https://docs.stripe.com/disputes.md)