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_0 (already cloned)
- Base commit: bc767b9131e2637ce90997da9018085d2dadb80b
- Task ID: juspay__hyperswitch-8430
- Version: v1.114.0
TASK DESCRIPTION: Bug: [BUG] adyen connector creates connector's customer reference on the fly
Bug Description
Connector's customer ID is a unique identifier for a customer's entity in the underlying connector for HyperSwitch for mapping a customer. This identifier is stored under
connector_customerincustomerstable.However, for Adyen - this field is a combination of merchant ID and customer ID in HyperSwitch which is unique across different merchants and customers.
This is a blocker for migrated customers whose
shopperReference(customer ID in Adyen) can be in a different format.Expected Behavior
Adyen should rely on the
connector_customerfield for customer and fallback to any default connector specific behavior.Actual Behavior
Adyen uses a default behavior for generating
connector_customer_idSteps To Reproduce
--
Context For The Bug
--
Environment
--
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?
None
DETAILED CONTEXT & HINTS:
Type of Change
- Bugfix
- New feature
- Enhancement
- Refactoring
- Dependency updates
- Documentation
- CI/CD
Description
Adyen now uses
connector_customer_idto formshopper_referenceif the field is present, else falls to previous implementation.Additional Changes
- This PR modifies the API contract
- This PR modifies the database schema
- This PR modifies application configuration/environment variables
Motivation and Context
How did you test it?
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_0/'
- 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 this Adyen connector bug where it's creating connector customer references on the fly instead of using the existing
connector_customerfield. Let me first understand the problem and locate the relevant files.Assistant
Let me search for Adyen connector related files to understand the current implementation:
Assistant
Let me examine the main Adyen connector implementation:
Assistant
Let me search for specific terms related to connector_customer and shopperReference in the Adyen connector:
Assistant
Let me search more broadly for Adyen-related code that might handle customer references:
Assistant
Let me look at the Adyen transformers file which seems to contain the shopperReference logic:
Assistant
Let me search for specific patterns in the Adyen connector files to understand how shopperReference is generated:
Assistant
Let me try a broader search for the customer-related implementation:
Assistant
Let me approach this differently by looking at the connector structure and understanding the codebase better:
Assistant
Let me search more specifically for where the connector_customer is used and how it relates to shopperReference:
Assistant
Now let me check the utils.rs file to understand how connector_customer is typically handled:
Assistant
(no content)
Assistant
Let me try to get a better understanding by examining the entire adyen.rs file structure:
Assistant
Now let me look at the transformers.rs file where shopperReference is likely to be defined:
Assistant
Let me look further into the Adyen transformer file to find how shopperReference is generated:
Assistant
Let me search for how the shopper_reference field is populated in the transformation process:
Assistant
Let me search for the try_from implementations in transformers.rs more broadly:
Assistant
Let me look at the end of the transformers.rs file where the implementations likely are:
Assistant
Let me continue looking at the transformers.rs file to find the implementations that create AdyenPaymentRequest:
Assistant
Perfect! Now I found the key function. Let me search for the
build_shopper_referencefunction which is likely responsible for creating the shopper reference:Assistant
Let me look for where the connector_customer is handled:
Assistant
Let me look at the end of the transformers.rs file to see how shopper_reference is built:
Assistant
I can see the issue! Let me examine how the
shopper_referenceis constructed in lines 2901-2904:let shopper_reference = build_shopper_reference( &item.router_data.customer_id, item.router_data.merchant_id.clone(), );This is the line that's causing the issue. Let me find the
build_shopper_referencefunction:Assistant
Let me find it in the whole file with a broader search:
Assistant
Let me look at the
build_shopper_referencefunction definition:Assistant
Now I need to understand the problem better. Based on my findings, the issue is that in the Adyen connector implementation, the
shopper_referencefield is generated usingbuild_shopper_referencefunction that combines merchant ID and customer ID to form a unique identifier. However, according to the bug report, the system should use an existingconnector_customerfield if it's available, rather than always generating one.Let me look at the function that handles recurring processing model which also sets shopper_reference:
Assistant
Let me check what the issue is exactly by examining how the connector_customer is supposed to be used. Let me also look for where it's referenced in the context of migrations:
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 →