Verified BursaPay workflow: Explains the Pay-for-Me fields stored on PublicPaymentSubmission.
1. Overview & Purpose
PublicPaymentSubmission stores is_pay_for_me, the delegated payer identity fields, a UUID token and a status with pending, accepted, or rejected choices.
2. Requirements & Setup
The workflow can also retain a rejection reason for the delegated payment.
3. Step-by-Step Workflow
- Create or open a PublicPayment submission configured for Pay-for-Me.
- Review the payer-for-me identity and generated token context.
- Track whether the delegated payment is pending, accepted, or rejected.
- Use the rejection reason when support needs to explain a rejected delegation.
4. Rules & Troubleshooting
A pending delegation should not be reported as accepted or paid until its relevant state has changed and the underlying payment is verified.
5. Verification & Next Steps
For support issues, use the delegation token/reference and status to trace the workflow without exposing unnecessary payer information.