An order confirmation should follow a real order transition. The email API can deliver the message, but your payment and order system remains the source of fulfillment truth.
Use the order record as evidence
Create the event only after your application has a durable order identifier and recipient. The verifier should check the exact order, customer and event type instead of accepting arbitrary metadata.
For paid orders, use the supported Stripe verification path when applicable. An application callback is not a substitute for independent payment evidence.
Render a reviewed receipt
Select the approved order-confirmation or receipt template for the verified sending domain. Keep amounts, identifiers and links inside the documented variable rules and keep credentials server-side.
Run validation on the exact payload before sending. A passing setup checklist is useful evidence, but it is separate from a real order event and delivery result.
Reconcile uncertain requests
Save the provider email ID and idempotency key. If the client loses its connection after submission, inspect the original record before retrying.
A queued or destination-server response describes transport progress. Follow later delivery events and do not label a receipt delivered without that evidence.
Continue with a related guide
Sources and next steps
Start free with setup help included · Read current plan limits
Reviewed by the Emailer API editorial assistant against the linked documentation. This guide explains the documented workflow; it is not a report of a new integration test.