Hello Ulrich,

Thank you for reaching out! I'm sorry to hear about the issue you're experiencing with the payment field. Here's how we can troubleshoot this problem:

1. Check Stripe Keys:

   • Ensure that the Stripe keys are correctly configured in Amelia. You can find this under Amelia > Settings > Payments > Stripe. Make sure both the Publishable Key and Secret Key are accurate.

2. Verify Custom Fonts:

   • If the Stripe keys are correct, the issue might be related to a custom font affecting the Stripe fields.
   • Navigate to Amelia > Customize, and review the font settings.
   • In the "Font Family" field, ensure only standard font names are used, such as Manrope, sans-serif.
   • Avoid using special characters or unique identifiers (e.g., Manrope <custom>), as these can cause the input box to malfunction.

3. Test After Changes:

   • After updating the font settings, try booking again to confirm if the issue is resolved.

If the problem persists, please let me know so I can assist further.

Hello Ulrich,

Thank you for the update on this.

Please provide me a temporary WP-admin (administrator) user for your site where this happens, so we can log in and take a look ‘from the inside’ as that’s the most efficient way to see and resolve the issue. 

We do not interfere with any data or anything else except for the plugin (in case that’s a production version of the site), and of course, we do not provide login data to third parties. 

You can write credentials here just check PRIVATE Reply so nobody can see them except us.

Hello Ulrich,

I just wanted to check with you if this issue has been resolved.

Looking forward to your reply.

Hello,

Thank you for your message and for sharing the steps you took to resolve the issue. I understand how frustrating and time-consuming it must have been to modify each of the 133 services individually. This certainly isn’t the expected behavior, and I’ll be glad to assist further.

The default payment settings should not require such manual adjustments for each service. If this issue persists or arises again, please let me know so we can investigate it further. It’s possible that a bug or misconfiguration is causing this unexpected behavior in version 7.9.

Thank you for your patience and for bringing this to our attention. Let me know if there's anything else I can assist with!