Codex Prompt for Safely Fixing Laravel Payment Checkout Bugs

You are an expert Laravel developer and payment integration specialist.

Context:
- Project details: [Project context]
- Relevant payment-related files or code snippets: [Relevant payment-related files or code snippets]
- Recent error messages or logs related to payment checkout or webhook failures: [Recent error messages or logs]
- Current checkout or webhook behavior: [Current checkout or webhook behavior]
- Expected correct behavior: [Expected correct behavior]
- Constraints or special considerations: [Constraints or special considerations]
- Environment details excluding secrets: [Environment details without secrets]
- Verification commands or tests available: [Verification commands or tests]
- Definition of done: [Definition of done]

Instructions:
1. Thoroughly inspect all provided relevant files and context before making any changes, including but not limited to:
   - Routes handling payment and checkout flows
   - Controllers managing payment logic and webhook processing
   - Payment gateway integration classes
   - Environment configurations related to payment credentials (ensure no secrets are exposed)
   - Application logs capturing payment errors or webhook failures
   - Database migrations affecting payment-related tables
   - Frontend checkout views and scripts

2. Identify the precise root cause of any bugs impacting checkout or webhook functionality.

3. Implement the smallest safe code change that resolves the identified issue, avoiding broad rewrites or risky modifications.

4. Preserve all existing payment gateway configurations and ensure compatibility with all integrated gateways.

5. Run syntax checks and all available automated tests to confirm no new errors or regressions.

6. Provide a detailed summary including:
   - Clear explanation of the root cause
   - List of all files modified with brief descriptions of changes
   - Exact code snippets added or modified
   - Verification steps performed and their outcomes
   - Recommended next actions or improvements, if any

Constraints:
- Do not expose or log any sensitive environment variables or secrets.
- Avoid broad or risky code rewrites.
- Maintain full compatibility with all existing payment gateways.

Before proceeding, confirm you have inspected all relevant files and gathered sufficient context.

After completing the fix, deliver the summary and verification results clearly.

Context to provide before editing:
- Relevant files: [Relevant files]
- Error message or logs: [Error message or logs]
- Verification commands: [Verification commands]
- Goal or task: [Goal or task]
- Current behavior: [Current behavior]
- Expected behavior: [Expected behavior]
- Constraints: [Constraints]