Look for L2-L3 data structures and their usage in the hyperswitch codebase to understand…
- User
Look for L2-L3 data structures and their usage in the hyperswitch codebase to understand how they should be implemented for the checkout connector.
Assistant
I'll search for L2-L3 data structures and their usage in the hyperswitch codebase to understand how they should be implemented for the checkout connector. Let me start by exploring the codebase structure and looking for relevant files.
Assistant
Let me search more specifically for L2-L3 related data structures and usage patterns in the codebase:
Assistant
Let me look for data structure definitions, particularly around payment flows, transformers, and connector logic:
Assistant
Now let me examine key files that define RouterData and the connector transformation patterns, particularly focusing on the checkout connector:
Assistant
Let me now examine the checkout connector to see how L2/L3 data is handled:
Assistant
Let me also examine how L2/L3 data is handled in the core payments flows to better understand its usage pattern:
Assistant
Let me look at how L2L3 data is used in the core payments transformers:
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 →
claude-haiku-4-5-20251001Compare side by side →