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: 3e7db573211ed61eadde3b601575f3472bda2b1f
- Task ID: juspay__hyperswitch-7522
- Version: v1.113.0
TASK DESCRIPTION: Bug: [BUG] Incorrect mapping of attempt status in AuthorizeDotNet connector
Bug Description
When the
capture_methodisautomatic, AuthorizeDotNet connector first sends aCapturedPendingSettlementstatus which is mapped toChargeInitiatedin our codebase. That results inprocessingtransaction status in the Hyperswitch's response (in production environment).Expected Behavior
It should show the status of "succeeded".
Actual Behavior
When the
capture_methodisautomatic, AuthorizeDotNet connector first sends aCapturedPendingSettlementstatus which is mapped toChargeInitiatedin our codebase. That results inprocessingtransaction status in the Hyperswitch's response (in production environment).Steps To Reproduce
Bug can only be seen in production environment.
Context For The Bug
No response
Environment
Are you using hyperswitch hosted version? Yes/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
Changed the attempt status mapping of
CapturedPendingSettlementgiven by AuthorizeDotNet fromChargeInitiatedtoChargedAdditional Changes
- This PR modifies the API contract
- This PR modifies the database schema
- This PR modifies application configuration/environment variables
Motivation and Context
When the capture_method is automatic, AuthorizeDotNet connector first sends a
CapturedPendingSettlementstatus which is mapped toChargeInitiatedin our codebase. That results inprocessingtransaction status in the Hyperswitch's response (in production environment).How did you test it?
Postman tests are not valid since AuthorizeDotNet directly sends
SettledSuccessfullystatus in local/sandbox environment.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 tackle this bug in the AuthorizeDotNet connector where
CapturedPendingSettlementstatus is incorrectly mapped toChargeInitiatedinstead ofCharged. Let me start by exploring the codebase to understand the current implementation.Assistant
I'll work on fixing the AuthorizeDotNet connector status mapping issue. Let me start by finding the relevant files.
Assistant
(no content)
Assistant
Let me examine the main AuthorizeDotNet connector implementation:
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 →