markGuestCreditCardAsInvalid mutationCopy link

Reports a traveler’s credit card as invalid, which initiates Expedia’s secure, on-platform recapture process directly with the traveler.

The credit card associated with a reservation can only be marked as invalid once. Multiple recapture attempts are currently not supported and will result in this error: Recapture has already been requested for this reservation. In addition, if the original credit card was marked as invalid by Expedia, the reservation's payment method cannot be marked as invalid by the lodging partner using this mutation.

After this mutation request is received, if successful, Expedia sends an automated email to the traveler, prompting them to update card details through the Virtual Agent. The reservation cannot be cancelled by the property during this recapture window. After the recapture window expires, the reservation becomes eligible for cancellation, or the property can provide more time to the traveler so that they can submit a new credit card. Refer to Reservation update for complete details.

This mutation is not supported for

• Reservations created with a virtual credit card (VCC)
• Reservations paid for using ETF direct payments
• Last-minute reservations created with no credit card
• Expedia Collect reservations

Syntax

1mutation {
2  markGuestCreditCardAsInvalid( 
3    input: MarkGuestCreditCardAsInvalidInput! 
4  ): MarkGuestCreditCardAsInvalidPayload!
5}

Example

1mutation { 
2  markGuestCreditCardAsInvalid( 
3    input: { 
4      clientMutationId: "myPartnerMutationId", 
5      propertyId: "923352", 
6      reservationId: "123456789",  
7      reason: INCORRECT_VERIFICATION_NUMBER 
8    } 
9  ) { 
10      clientMutationId 
11      reservationId 
12  } 
13}