For a Guesty connection, HomeRunner checkout only needs your Stripe publishable key to collect cards. Guesty charges the card through its own Stripe connection, and adding a secret key does not change that.
What the secret key turns on. Adding your Stripe secret key turns on card validation at checkout. When the guest submits, the checkout asks Stripe to verify the card first, including a CVC check and 3D Secure when the guest’s bank requires it. If the bank declines the card at this step, the guest sees the decline message on the checkout page and can try another card. The booking request is not created until a card passes. After the card passes, the flow is the same as before: the card is sent to Guesty with the request, and Guesty charges it on acceptance according to your Guesty payment settings.
What to expect. You should see far fewer requests arriving without a card, though not zero. A card can pass checkout validation and still fail when Guesty registers it on its side. In that case, the request still shows no card in Guesty.
Adding the key. You can enter the secret key yourself in your own HomeRunner dashboard, without involving the support team.
- Open the HomeRunner Central payment provider for your Guesty connection.
- Enter the secret key next to the publishable key and save it.
- Wait for a property sync to push the setting to your website. Until that sync runs, checkout behaves as before.
Both the publishable key and the secret key must come from the same Stripe account that is connected in Guesty.
If you rotate the key. If you rotate the secret key in Stripe later, enter the new one in the same place. Card validation depends on the current key being stored.