You are working on the hyperswitch repository (Rust payment processing system).…
- User
You are working on the hyperswitch repository (Rust payment processing system).
REPOSITORY SETUP:
- Repository: juspay/hyperswitch
- Working directory: ./repos/hyperswitch_pool_4 (already cloned)
- Base commit: 10371af561ecc7536bb1db191af90a3cac2ab515
- Task ID: juspay__hyperswitch-7565
- Version: v1.113.0
TASK DESCRIPTION: Bug: [BUG] AuthorizeDotNet Deserialization Failed in RSync Response in Production
Bug Description
AuthorizeDotNet has started sending status
voidedin RSync Response which is not mapped in Hyperswitch.Expected Behavior
voidedstatus should be mapped toFailure.Actual Behavior
Deserialization failed.
Steps To Reproduce
Provide an unambiguous set of steps to reproduce this bug. Include code or configuration to reproduce, if relevant.
- Go to '...'
- Click on '....'
- Scroll down to '....'
Context For The Bug
No response
Environment
Are you using hyperswitch hosted version? No If yes, please provide the value of the
x-request-idresponse header to help us debug your issue.If not (or if building/running locally), please provide the following details:
- Operating System or Linux distribution: MacOS
- Rust version (output of
rustc --version):rustc 1.83.0 (90b35a623 2024-11-26) - App version (output of
cargo r --features vergen -- --version): ``
Have you spent some time checking if this bug has been raised before?
- I checked and didn't find a similar issue
Have you read the Contributing Guidelines?
- I have read the Contributing Guidelines
Are you willing to submit a PR?
Yes, I am willing to submit a PR!
DETAILED CONTEXT & HINTS:
Type of Change
- Bugfix
- New feature
- Enhancement
- Refactoring
- Dependency updates
- Documentation
- CI/CD
Closes this issue
Description
Mapped status
voidedcoming from AuthorizeDotNet toFailurein Hyperswitch.Additional Changes
- This PR modifies the API contract
- This PR modifies the database schema
- This PR modifies application configuration/environment variables
Motivation and Context
AuthorizeDotNet has started sending status voided in RSync Response which is not mapped in Hyperswitch. As a result, deserialization failed.
How did you test it?
Can't be tested as AuthorizeDotNet takes 5-6 business days to send any other status than
RefundPendingSettlement.Checklist
- I formatted the code
cargo +nightly fmt --all - I addressed lints thrown by
cargo clippy - I reviewed the submitted code
- I added unit tests for my changes where possible
CRITICAL INSTRUCTIONS - WORK FAST AND EFFICIENTLY:
-
Create DENSE, ACTION-FOCUSED todos IMMEDIATELY
- Make todos specific and actionable
- Focus on HIGH-IMPACT actions only
- 5-8 todos maximum - be surgical, not exhaustive
-
Execute aggressively:
- Use bash commands to search efficiently
- Read multiple related files in quick succession
- Make ALL related changes in one edit
- Skip unnecessary exploration
-
File operations:
- All repo files: './repos/hyperswitch_pool_4/'
- Use targeted edits over whole file rewrites
-
NO TESTING UNLESS CRITICAL:
- Focus on making the actual code changes
- Only test if explicitly required
-
Maximize information density:
- Each turn should accomplish significant work
- Batch file reads when examining related code
- Use search commands to locate code quickly
EFFICIENCY IS CRITICAL. Make substantial progress every turn.
Assistant
I'll help you fix the AuthorizeDotNet deserialization issue where the
voidedstatus is not mapped in Hyperswitch. Let me start by understanding the problem and locating the relevant files.First, I'll create a todo list to track the key tasks needed to resolve this bug:
Assistant
Let me search for AuthorizeDotNet related code to understand how statuses are currently handled.
Assistant
Let me search more broadly for payment connectors and status handling:
Assistant
Let me search more specifically for AuthorizeDotNet connector files:
Assistant
Let me look at the AuthorizeDotNet connector implementation to understand how statuses are currently handled:
Assistant
Now let me check the transformers file for AuthorizeDotNet to understand how status mappings are handled:
Assistant
I can see from the code that there are two status enums involved:
SyncStatus(used for PSync/regular payments)RSyncStatus(used for Refund Sync)
Looking at lines 1542-1565, I can see the
SyncStatusenum has aVoidedvariant (line 1551), and from lines 1595-1611, I can see thatSyncStatus::Voidedis properly mapped toenums::AttemptStatus::Voided.However, looking at the
RSyncStatusenum (lines 1560-1565), I see that it does NOT include aVoidedvariant, which causes the deserialization failure when AuthorizeDotNet returnsvoidedstatus in the RSync response.Let me now examine the RSyncStatus mapping more closely and create a plan to fix it.
Assistant
Let me examine the code more closely to understand exactly where the
RSyncStatusenum is defined and used, particularly in relation to refund sync responses:Assistant
Let me also look at where the refund status mapping occurs for RSync responses:
Assistant
Let me look at the exact context around lines 1613-1621 where the RSyncStatus to RefundStatus conversion happens:
Assistant
Now I'll examine the complete RSyncStatus enum definition to understand its current structure:
Assistant
Perfect! Now I understand the issue. The
RSyncStatusenum (lines 1560-1565) doesn't include aVoidedvariant, but AuthorizeDotNet is now returning avoidedstatus in the RSync response, which causes deserialization to fail.Let me now check what the expected behavior should be based on the bug description and fix it:
Assistant
Now I'll fix the issue by adding the
Voidedvariant to theRSyncStatusenum and mapping it appropriately toenums::RefundStatus::Failureas per the bug description:Assistant
Let me search for the exact text in the file:
Assistant
(no content)
Assistant
Let me check the exact content around the enum definition by reading more lines:
Assistant
(no content)
Assistant
Perfect! Now I can see the exact structure. Let me make the edit to add the Voided variant to the RSyncStatus enum:
Assistant
Let me use the correct method to edit the file:
Assistant
Let me first read the file again to make sure I have the right context:
Assistant
I'll use the proper line-based approach for the edit. First, let me check the exact lines:
Assistant
Now I'll edit the file using the exact line-based approach:
Assistant
I understand that I'm having permission issues with direct file editing. Let me try using a different approach by using the Write tool to create a patch file that shows what needs to be changed:
Assistant
Let me approach this differently. Since I cannot directly modify files due to permission constraints, let me clearly document the fix I would make, and summarize what needs to be done.
Based on my analysis, I can clearly see the issue and the fix needed. Let me complete my task by documenting what needs to be changed:
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.
Identical first prompt
claude-sonnet-4-5-20250929Compare side by side →
claude-sonnet-4-5-20250929Compare side by side →
claude-sonnet-4-5-20250929Compare side by side →
claude-sonnet-4-5-20250929Compare side by side →
claude-sonnet-4-5-20250929Compare side by side →
claude-sonnet-4-5-20250929Compare side by side →
claude-sonnet-4-5-20250929Compare side by side →
claude-sonnet-4-5-20250929Compare side by side →
claude-sonnet-4-5-20250929Compare side by side →
claude-sonnet-4-5-20250929Compare side by side →
claude-sonnet-4-5-20250929Compare side by side →
claude-sonnet-4-5-20250929Compare side by side →