Troubleshoot a webhook API-key warning
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Correct a publishable-key/secret-key mismatch or invalid secret.
Where to goAdmin Area → Setup → Settings → Payment Gateways → Stripe iDEAL V2
Before you start
- Use the exact navigation above and confirm the intended invoice, case, client, property, document or environment.
- Verify module activation and the stated permission before attempting the action.
- Use a controlled test record for payments, emails, public/portal access, provider calls and deletion.
What this guide helps you do
Correct a publishable-key/secret-key mismatch or invalid secret. These instructions follow the supplied module’s live hooks, menus, controllers, forms, model rules and downstream effects.
Follow these steps
- Read the exact Stripe exception shown in the warning.
- Verify the secret-key field contains a secret key, not the publishable key.
- Save matching environment keys and reload.
Fields and options
Typical causeStripe API rejects the configured key
Category/help-centre/category/stripe-ideal-payment-gateway/
Topic/help-centre/topic/stripe-ideal-webhook-management/
Rules and limits
- The webhook check catches the API exception and prints its message in a warning.
Check it worked
- Troubleshoot a webhook API-key warning completes through the supplied module flow.
- Reopen the source record or settings page and verify the stored value, status, payment, file, timeline entry or notification.
Security, privacy and operational checks
- Use the correct Stripe test/live account and protect signing credentials.
- Do not call webhook-management routes from an untrusted session.
Related guides
Was this guide useful?Your response is stored only in this browser.