Skip to content
Moosewave
Choose the moment

Orders & receipts

When someone needs a receipt or order update, clarity is the feature. Put the state, reference, amount, and next action where they can be found.

Make the next step deliberate.

  1. Read the event

    Check which transaction or order state actually changed.

  2. Preserve important details

    Keep identifiers, amounts, dates, and recovery routes exact.

  3. Separate purposes

    Do not silently turn an essential update into a marketing campaign.

A brief with boundaries.

Prepare an order update from the supplied transaction record. Preserve identifiers, amounts, dates, and support links. Do not add a marketing offer.

Read the complete text
Prepare an order update from the supplied transaction record. Preserve identifiers, amounts, dates, and support links. Do not add a marketing offer.

Use your own approved source records. This page does not connect an assistant, activate a journey, or send email.

Published designs to start from.

Real entries in the public library. Preview each design, choose its delivery flow, and replace illustrative content with your approved facts.

These are starting points, not a claim of a completed or activated campaign. Studio examples may need structural changes for your use case.

Keep these checks close.

  • Never include real payment credentials in a public example.
  • A receipt must not imply a payment succeeded without its source event.

Talk to Moosewave about your workflow. For technical context, see documentation and security.