[Compliance] User-facing website messages are not wrapped for translation

[chromonav]

Branch

• dev

Evidence

• easebuzz/www/easebuzz/success.html#L9
• easebuzz/www/easebuzz/failure.html#L9

Current body texts are plain strings and not wrapped in translation helpers.

Problem

User-facing copy in website templates is partially untranslated. Titles use _() but descriptive messages do not.

Risk/Impact

• Inconsistent localization behavior in multilingual deployments.
• Breaks Frappe i18n expectations for visible copy.

Replication suggestion

1. Enable non-English language for website user.
2. Open success/failure pages.
3. Observe headings translated, but message body remains English.

Expected: all user-visible copy should be translation-ready.
Actual: body text is hardcoded English.

Resolution suggestion

Wrap the body messages with _() in Jinja templates.

Example:

{{ _("The payment was successful. You will receive an email with the details of the payment.") }}

Acceptance criteria

• All user-visible strings in success/failure templates are wrapped with _().
• Messages are extractable via translation pipeline and render in selected locale.