Public Payment Anonymous and Masked Payer Display

1. Overview & Purpose

PublicPaymentSubmission includes an is_anonymous flag and model properties that mask payer name and email for display.

2. Requirements & Setup

The masking logic preserves a recognizable first/last character pattern while obscuring the rest of the value.

3. Step-by-Step Workflow

1. Open a public payment submission.
2. Check whether the submission is marked anonymous.
3. Use the masked name and masked email properties for public-facing display where applicable.
4. Keep the underlying payer data available only to authorized internal workflows.

4. Rules & Troubleshooting

Do not expose raw payer email or identity data merely because the underlying submission contains it.

5. Verification & Next Steps

Use the masked properties for public contribution or participation displays and the raw fields only in authorized internal contexts.