Configure and use the iDEAL payment integration
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Enable the bundled iDEAL integration, configure webhook handling and test payment callbacks.
Before you startThe screen or action may be hidden when your role lacks permission, the related module is inactive, or a required setting has not been configured. Ask an administrator to review access rather than using another person’s account.
What this guide helps you do
Enable the bundled iDEAL integration, configure webhook handling and test payment callbacks. Pixie CRM keeps the result connected to the relevant customer, staff member and operational history where the feature supports those relationships. That connection is important for search, reporting, client portal visibility and future automation.
Follow these steps
- Go to Payment gateway settings / Customer checkout using an administrator or appropriately permitted account.
- Check the current value and understand which users, records or automated processes it affects.
- Enter or select the new configuration values. Keep labels concise and use the approved business terminology.
- Where credentials, email, webhooks or cron are involved, begin with a test or sandbox configuration.
- Save the change and confirm that Pixie CRM reports success.
- Test the affected workflow with a non-critical record and with a restricted user where permissions are relevant.
- Document the operational change and use the available reset or rollback option if the result is not correct.
Settings to check
Record title or nameCheck this value against the source record before saving. If the field is optional and no verified value is available, leave it blank rather than entering placeholder data.
Related customer or recordCheck this value against the source record before saving. If the field is optional and no verified value is available, leave it blank rather than entering placeholder data.
Owner or assigneeCheck this value against the source record before saving. If the field is optional and no verified value is available, leave it blank rather than entering placeholder data.
StatusCheck this value against the source record before saving. If the field is optional and no verified value is available, leave it blank rather than entering placeholder data.
DatesCheck this value against the source record before saving. If the field is optional and no verified value is available, leave it blank rather than entering placeholder data.
Notes and attachmentsCheck this value against the source record before saving. If the field is optional and no verified value is available, leave it blank rather than entering placeholder data.
Checks before you finish
- Verify the related record.
- Use clear, searchable text.
- Check visibility and permissions before saving.
- Check whether the result should be visible to a customer contact or only to staff.
- Confirm the final status, activity entry, generated document or notification before leaving the record.
Permission and data safetyDeletion, refunds, signature clearing, module changes, payment configuration and privacy actions can affect linked records or legal history. Use the least destructive action available and follow your organisation’s approval process.
Related guides
Was this guide useful?Your response is stored only in this browser.