Looking at the Adyen connector code and the bug description, I need to understand how…
- User
Looking at the Adyen connector code and the bug description, I need to understand how the connector_customer field can be accessed in the router data. The bug states that Adyen should rely on the connector_customer field for customer and fallback to default behavior.
The problem is in the shopper_reference generation. Looking at lines 2901, 3509, 5825 in the transformers.rs file, it calls build_shopper_reference which builds a new shopper_reference instead of using an existing one.
Where in the payment flow does the connector_customer field get passed down to the connector layer so that we can use it instead of creating a new shopper_reference?
Assistant
I'll help you understand how the
connector_customerfield gets passed down to the connector layer and how it relates to the shopper reference generation in Adyen connector code. Let me explore the codebase to find the relevant files and understand the data flow.First, let me look for the Adyen connector implementation and the transformers.rs file mentioned in the bug description.
Assistant
Now let me look for the transformers.rs file that was mentioned in the bug description:
Assistant
Now let me look at the specific Adyen transformers file, which seems to be the most relevant one:
Assistant
Let me search for the build_shopper_reference function and related code around the line numbers mentioned in the bug description:
Assistant
Let me check the connector_customer field definition in the core structures:
Assistant
Let me search for the structure definitions to understand how connector_customer is used:
Assistant
Let me check the connector utils to see how data flows between different layers:
Assistant
Let me examine the payment flows to understand how connector_customer gets populated and passed through the system:
Assistant
Let me search more broadly in the payment operations to understand how connector_customer is handled:
Assistant
Let me check for how shopper_reference is created and used in the Adyen connector specifically. Let me look at the payment confirmation flow:
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-haiku-4-5-20251001Compare side by side →
claude-haiku-4-5-20251001Compare side by side →
claude-haiku-4-5-20251001Compare side by side →
claude-haiku-4-5-20251001Compare side by side →
claude-haiku-4-5-20251001Compare side by side →
claude-haiku-4-5-20251001Compare side by side →
claude-haiku-4-5-20251001Compare side by side →
claude-haiku-4-5-20251001Compare side by side →
claude-haiku-4-5-20251001Compare side by side →
claude-haiku-4-5-20251001Compare side by side →
claude-haiku-4-5-20251001Compare side by side →