Verified BursaPay workflow: Explains how PublicPayment submissions connect to payment records and verification state.
1. Overview & Purpose
PublicPaymentSubmission stores payer identity, custom form_data, a unique transaction reference, is_paid state and a link to the financial PaymentRecord.
2. Requirements & Setup
Submission records can also represent anonymous display preferences and Pay-for-Me workflow state.
3. Step-by-Step Workflow
- Open the public payment's submissions or payment records.
- Check payer information and form data.
- Confirm the transaction reference and payment state.
- Use the linked PaymentRecord where reconciliation requires the financial transaction context.
4. Rules & Troubleshooting
A submission existing in the system is not itself proof of settlement; use the payment state and linked financial record for verification.
5. Verification & Next Steps
For support cases, preserve the reference and relevant submission context when tracing the payment.