# Understanding the Credit Card Status API

The Credit Card Status API allows partners to check the validity of credit cards that guests provide when making a "Pay at property" reservation **and** notify them in case an invalid credit card was used. The partner can then request a card update from the guest or cancel the reservation. A valid credit card is required for late cancellations and no-shows as it allows Booking.com to collect the respective fees from the guest and pay them out to the partner.

The Credit Card Status API is only applicable for properties who use [Smart Pay-at-Property](https://partner.booking.com/en-gb/help/policies-payments/payment-products/smart-pay-at-property) as one of the payment methods and who have already implemented the [Reservations API](/connectivity/docs/reservations-api/reservations-overview/).

## Card verification flow

The validity of the credit card is checked several times after the guest makes a reservation. [Notifications](/connectivity/docs/credit-card-status-api/receiving-notifications) are sent in case the initial card verification failed or in case the card is invalid. You need to use the [use the Credit Card Status API](/connectivity/docs/credit-card-status-api/getting-the-credit-card-status) upon receiving the notification.

Therefore, card's validity is checked:

* **Within a few hours after the reservation was made**.
  * If the initial verification is successful, another one is performed 3 days before the free cancellation period.
  * If the initial verification fails, you receive a `CREDIT_CARD_STATUS_UPDATE` notification. At this point, the card has the status `INITIAL_CARD_CHECK_UNSUCCESSFUL`. You need to use the Credit Card Status API to check the actual current status of the card in case the guest has updated it in the short time frame after the initial notification was sent. If there is indeed an issue with the card, you can use Extranet to mark the card as invalid and request a card update from the guest.
* **24 hours after the guest received a card update request**.
If the guest didn't update the card details within 24 hours, you receive a `CREDIT_CARD_STATUS_UPDATE` notification. Use the Credit Card Status API to double-check the validity of the card, and if it's indeed  `INVALID_CARD`, use Extranet to cancel the reservation.
* **3 days before the free cancellation deadline**.
In case the initial verification is successful, another one is performed 3 days before the free cancellation deadline. If this verification fails, you receive a `CREDIT_CARD_STATUS_UPDATE`  notification. You need to use the Credit Card Status API to check the actual current status of the card in case the guest has updated it in the short time frame after the initial notification was sent. If the card status is indeed `INVALID_CARD`, use Extranet to request a card update from the guest.


## Main URL and use of shortened endpoint paths

The main URL of the Credit Card Status API is `https://payments-api.booking.com`. All shortened endpoint paths imply that you must add the main URL.

## Authentication

The Credit Card Status API uses the same [authentication methods](/connectivity/docs/authentication) as other APIs.

## Going live

Before you go live with your API integration, you'll need to meet certain requirements. For more information, see [Going Live](/connectivity/docs/going_live/).

## Contact us

Need help integrating with the Credit Card Status API? The experts in our [Connectivity Support team](https://portal.connectivity.booking.com/s/article/Contact-Us) are here to help.

Do you want us to improve this page?  Click `Yes` | `No` in the `Was this page helpful?` box at the bottom of this page.