Security controls for real payment operations
EFundFlow is designed around the boundaries that matter in payment operations: merchant identity, site ownership, credential access, webhook configuration, and permissioned dashboard workflows.
Merchant onboarding controls
KYC status, merchant identity, user permissions, and protected routes keep sensitive payment operations gated until the merchant account is ready.
- KYC onboarding and review status
- Permission-based dashboard navigation
- Merchant ownership checks for site operations
Site-level isolation
Payment setup is scoped to site merchant IDs so domains, currencies, callbacks, payment methods, and processor settings do not leak across sites.
- Site ownership validation
- Separate payment and settlement settings
- Independent webhook URLs per site
Credential handling
Processor credentials and API settings are managed through controlled dashboard workflows with masked display patterns for sensitive PSP values.
- Masked PSP credential display
- Controlled API credential access
- Sensitive fields separated from ordinary reporting views
Webhook and integration safeguards
Webhook configuration uses explicit URL validation and site ownership checks before changes are saved for payment and refund callbacks.
- Payment webhook URL validation
- Refund webhook URL validation
- Clear site context before updates