Digital-key delivery email failed: retry notifications without allocating keys twice

A paid order may already have its digital keys allocated even when its delivery email fails. Repair notification and retrieval instead of allocating another set or marking payment failed. 稳付pay handles the agreed payment confirmation and callback; the merchant manages key inventory, email and retrieval permissions.

Continue by topic

Keep payment, allocation and notification states separate

An order should distinguish paid, keys allocated, email queued and notification failed. Link each key permanently to its order and make the notification reference that allocation instead of invoking inventory allocation again. For multiple items, retain item-level assignment records so support can distinguish unfulfilled from allocated-but-not-notified orders.

Classify errors and interpret acceptance correctly

SMTP 4xx replies generally indicate temporary failure; 5xx requires correction or review. Use the email provider’s detailed classification to choose retry or manual repair. Server acceptance does not prove the customer read the message, and a bounce can arrive later. Keep job IDs, provider message IDs and redacted error codes, not complete digital keys in ordinary logs.

Retry the original delivery record

Use a stable notification job ID, uniqueness protection, retry limits and backoff. Manual resend must reference the same order allocation. If an order bought two keys and the first email timed out, the retry sends information for those same two keys. Even if the provider actually accepted the first message, a timeout must not cause two more keys to leave inventory.

Offer retrieval with ownership checks

Signed-in customers can reopen their orders. A retrieval link should use an unpredictable identifier, appropriate expiry and access controls. Verify order ownership before changing the destination email and retain an audit record. A stranger’s chat screenshot is not enough to release keys. Prefer protected retrieval where forwarding an email could otherwise expose credentials.

Use evidence for support and refund decisions

Check payment confirmation, allocated items, email submission, bounce or delivery feedback and retrieval records in order. Follow product rules and verifiable key-revocation or redemption states for refunds; a bounced email does not prove a key was unused. Test duplicate callbacks, mail timeouts, bounces, changed addresses, manual resends and multi-item orders to confirm a single allocation.

Frequently asked questions

Should a missing email generate a new key?

Check the existing allocation first. Restore the notification or retrieval route for allocated keys. Any replacement needs an explicit revocation and inventory review.

Does email-provider success prove fulfillment?

It usually confirms a submission stage, not that the customer read or used the key. Consider later delivery/bounce feedback and the merchant’s retrieval records.

References