Use an email-verification hold when you want staff to review an order until the customer has confirmed an email address. The customer can place the order; this control is a hold after order creation, rather than a requirement to verify before checkout.

Check the verification prerequisite

Confirm that Blesta has actually requested email verification for the intended contact and that the contact can receive and complete that request. PD Shield reads contact verification; do not look for a global email-verification switch in PD Shield. A customer who has never been asked to verify is treated as verified for this rule.

Where a client has several contacts, one verified contact is sufficient for this check. It is not a requirement that every contact has verified.

Enable the hold

1. Open PD Modules → PD Shield → Settings.
2. Enable Hold an order for review until the customer verifies their email address.
3. Review Alert recipient email(s) and your customer email templates, including PD Shield Order Under Review and PD Shield Order Cleared.
4. Press Save settings.
5. Review the intended order and activation workflow before relying on the rule for an automatically provisioned offering.

This setting is separate from Action when a rule matches, which controls velocity. Switching velocity to Flag does not turn this verification hold into observation mode.

Understand the customer and order states

An unverified customer’s order is placed and should enter Blesta’s fraud state for review. PD Shield attempts to send the under-review notice; check actual delivery rather than assuming that a recorded hold proves an email arrived.

The hold is intended to preserve the client’s ability to sign in, while holding the order and its services. Do not rely on older wording that says the invoice always stays open: the platform’s fraud transition can void it. On release, the integration attempts to reopen the relevant voided invoice. Check the order, service and invoice separately.

Check release after verification

PD Shield checks eligible verification holds through its scheduled work. Confirm that the normal cron is running, then review Activity and the actual order after the customer verifies. Release depends on scheduled checks; confirm payment and provisioning separately.

Automatic release is limited to a hold caused only by email verification. Another recorded hold, a staff review decision, or a client marked fraud or closed can keep the order with staff. Confirm the original reason before approving an order; email confirmation alone does not establish that the order is safe.

If the order stays held

Check that the platform recognises the relevant user or contact as verified, that the rule caused the hold, and that scheduled work has run. Inspect other hold reasons and staff decisions. Keep verification links, personal details and account credentials out of shared screenshots.

See the PD Shield Blesta guide for related setup, or explore PD Shield.