Skip to content
Moosewave
Demo

TransactionalBilling & payments

Payout returned by bank email template

A payout rejected because the account details were wrong.

Illustrative example. Replace the fictional sender, dates, amounts, locations, and account details before use.

Responsive design preview

See the message before you make it yours.

Compare the desktop and mobile compositions, or unfold the full design. The complete starting copy remains readable below.

Payout returned by bankIllustrative preview
Payout returned by bank email template preview

Auto follows your screen width. Scroll inside the frame to inspect the complete email.

A reviewed browser rendition of the payout returned by bank structure. It is not a send receipt or an inbox-placement claim.

Want to change the copy and style?

Try one of the editable browser templates.

This page is a read-only reference. The five hands-on studios let you edit a local preview, compare desktop and mobile, and review every change before continuing.

See editable templates

Message anatomy

A useful starting point, with the important parts named.

The money is back with us and safe. Banks reject rather than guess, which is the behaviour you want when it is your money.

What you can change

  • Brand name
  • Subject line
  • Preheader
  • Eyebrow
  • Headline
  • Supporting copy
  • Primary action label
  • Primary action URL

What to keep clear

  1. State or event context
  2. Plain-language explanation
  3. Three labelled facts
  4. Primary and secondary action
  5. Support or privacy footer

Complete starting copy

Read it as text, not only as a picture.

Sample details are fictional. Replace them with reviewed customer and event data before use.
From
Lockeridge Payouts
Subject
Your bank sent the payout back
Preheader
The account number and sort code do not agree.

Payout returned

Returned, because the details do not match

The money is back with us and safe. Banks reject rather than guess, which is the behaviour you want when it is your money.

Amount

£812.40

Returned

Today

Reason

Details do not match

Correct your bank detailsTalk to us about it
We will retry automatically once you correct the details. There is no charge for the returned payment.

Moosewave MCP

Give an agent the structure, the job, and a stopping point.

A compatible MCP app can inspect this reference and create a separate workspace draft when it has permission. The brief cannot send.

The brief asks for a new draft and stops before send.

Read the complete brief

Connected work

Take the design beyond the canvas.

Transactional email APIConnect the message to a real product event and keep its outcome visible.IntegrationsCarry the right customer and event context into the draft.SecurityKeep account, access, and recovery boundaries explicit.MCP for agentsAdapt presentation without quietly changing the event being explained.