Skip to main content

I’ve had a client able to schedule using the “card” feature through the Stripe integration, but a different client tried to use the “Apple Pay” feature and it doesn’t work. I tested it out and had the same issue - apparently this is an ongoing issue other folks have had as well via calendly. Is there a way to remove the Apple Pay feature altogether? It’s not ideal to have to have this back and forth with potential clients, making the steps to pay/schedule much more difficult than it needs to be. Not to mention apple pay is showing the client this payment is pending, I’m hoping it doesn’t process/go through. Any help is asspreciated. 

Hi ​@Malorie25036,

Thanks for flagging this. You’re right to suspect there’s an issue with Apple Pay specifically on the Calendly + Stripe checkout right now. Our teams are tracking a bug where Apple Pay either doesn’t appear or fails to complete, while other payment methods (card, Google Pay, Link/instant bank) continue to work. We don’t have an ETA to share yet, but this is actively escalated internally.

You can disable Apple Pay just for Calendly directly in your Stripe settings so your checkout only shows card (and any other methods you keep enabled).

  • In Stripe: Settings → Payment methods → Open the Calendly configuration → Turn off Apple Pay for Calendly. This hides Apple Pay from your Calendly booking pages while keeping other methods active.

  • In the meantime, customers can continue to pay with most major cards, Google Pay, and instant bank payments (Link).

If any invitee believes a “pending” Apple Pay transaction went through, you can verify in Stripe:

  • “Incomplete/Uncaptured” means no charge was taken and it will clear on its own.

  • If you ever see a fully “Succeeded” charge without a Calendly booking (rare), issue a refund in Stripe and share the payment_intent ID with us so we can investigate. Note that Calendly doesn’t process refunds. They’re managed in your Stripe dashboard.

  • “Pending” Apple Pay entries shown to clients correspond to incomplete authorizations; they are not captured charges and should fall off automatically if the booking didn’t complete.

Hope this helps and I hope we have a fix very soon!


this is so helpful thank you Jillian! :)