feat(platform): Add Dispute & Refund resolution process

[majdyz]

Changes 🏗️

Added the dispute & refund handling on the system.

Screen.Recording.Feb.11.2025.Video.Speed.mp4

Checklist 📋

For code changes:

• I have clearly listed my changes in the PR description
• I have made a test plan
• I have tested my changes according to the test plan:
  • ...

Example test plan

• Create from scratch and execute an agent with at least 3 blocks
• Import an agent from file upload, and confirm it executes correctly
• Upload agent to marketplace
• Import an agent from marketplace and confirm it executes correctly
• Edit an agent from monitor, and confirm it executes correctly

For configuration changes:

• .env.example is updated or already compatible with my changes
• docker-compose.yml is updated or already compatible with my changes
• I have included a list of my configuration changes in the PR description (under Changes)

Examples of configuration changes

• Changing ports
• Adding new services that need to communicate with each other
• Secrets or environment variable changes
• New or infrastructure changes such as databases

[netlify]

✅ Deploy Preview for auto-gpt-docs-dev canceled.

Name	Link
🔨 Latest commit	ee2a92b
🔍 Latest deploy log	https://app.netlify.com/sites/auto-gpt-docs-dev/deploys/67b44c1430bb950008733199

[qodo-merge-pro]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 4 🔵🔵🔵🔵⚪

🧪 No relevant tests

🔒 Security concerns Sensitive information exposure: The dispute evidence text includes detailed transaction history and user email which is sent to Stripe. While Stripe is a trusted provider, consider minimizing the exposed information to only what's necessary for dispute resolution.

⚡ Recommended focus areas for review Error Handling The refund amount validation logic may allow invalid refund amounts. The code should validate that the refund amount is positive and less than or equal to both the original transaction amount and current balance. if request.amount <= 0 or request.amount > transaction.amount: raise AssertionError( f"Invalid amount to deduct ${request.amount/100} from ${transaction.amount/100} top-up" ) Race Condition The dispute handling logic checks balance and makes decisions without proper transaction isolation. This could lead to race conditions if multiple disputes are processed simultaneously. if balance >= transaction.amount: logger.warning(f"Accepting dispute from {user_id} for ${amount/100}") dispute.close() return Data Truncation The dispute evidence text is truncated to 20000 characters without warning. This could silently drop important transaction history information. "uncategorized_text": evidence_text[:20000],

[deepsource-io]

Here's the code health analysis summary for commits 0117006..ee2a92b. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
JavaScript	✅ Success	❗ 48 occurences introduced 🎯 31 occurences resolved	View Check ↗
Python	✅ Success	❗ 12 occurences introduced 🎯 8 occurences resolved	View Check ↗

---

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

[netlify]

✅ Deploy Preview for auto-gpt-docs canceled.

Name	Link
🔨 Latest commit	ee2a92b
🔍 Latest deploy log	https://app.netlify.com/sites/auto-gpt-docs/deploys/67b44c14ed672e00087da63d

[itsababseh]

Looks good to me, great job! Thanks for attaching the video. The CI passed let me know if you need me to approve this if someone else already checked the code.

Quick question @majdyz is there a reason a user has to click the refresh on balance before the changes happen?

[majdyz]

@itsababseh thanks! @kcze will review the code part so it's fine :)

Quick question @majdyz is there a reason a user has to click the refresh on balance before the changes happen?

We just don't know how fast the refund is processed by the payment processor, so we might sometimes get a delay when the user needs to manually refresh the balance. It's the same reason why the refresh balance button is there in the first place.

We can fix this holistically by having a more proactive balance check or server sent events containing balance updates, but this is outside the scope of this PR and more general product improvement.

addressed