Based on the analysis of the hyperswitch codebase for implementing L2-L3 data support…
- User
Based on the analysis of the hyperswitch codebase for implementing L2-L3 data support for checkout connector, create a comprehensive summary of what changes need to be made to implement this feature. Focus on exactly what code modifications are required in the files identified, without writing any actual code. Provide the exact changes needed for both the API model and connector implementation.
Assistant
I'll analyze the hyperswitch codebase to understand what changes are needed for implementing L2-L3 data support for checkout connector. Let me first explore the codebase structure to identify relevant files.
Assistant
Let me search for files related to checkout connectors and authentication to understand the structure better.
Assistant
Let me also look for authentication-related files to understand how L2-L3 data is handled.
Assistant
Let me look for connector-related files to understand how they're structured:
Assistant
Now let me examine the checkout connector transformer file to understand its structure:
Assistant
Now let me check the authentication related types to understand how L2-L3 data is currently handled:
Assistant
Let me examine the authentication transformer file to understand how authentication flows work:
Assistant
Let me check the domain models to understand the L2-L3 data structure:
Assistant
(no content)
Assistant
Let me check the main router_data structure in hyperswitch_domain_models:
Assistant
(no content)
Assistant
Now let me also look at some other connectors to see how they handle L2-L3 data to understand what needs to be implemented:
Assistant
Let me examine how L2-L3 data is handled in other connectors:
Assistant
(no content)
Assistant
Let me search for the specific connector's handling of L2/L3 data more broadly:
Assistant
(no content)
Assistant
Let me examine a different approach to understand how L2-L3 data works. Let me search for examples of connectors implementing L2-L3 data support:
Assistant
Let me check what other connectors actually do with L2/L3 data to get a clearer picture:
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 →