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_7 (already cloned)
- Base commit: f3ab3d63f69279af9254f15eba5654c0680a0747
- Task ID: juspay__hyperswitch-9332
- Version: v1.117.0
TASK DESCRIPTION: Bug: Create Customer
DETAILED CONTEXT & HINTS:
Type of Change
- Bugfix
- New feature
- Enhancement
- Refactoring
- Dependency updates
- Documentation
- CI/CD
Summary
This PR introduces a create customer handler for the Chargebee connector. It enables merchants to create and manage customers in Chargebee directly through Hyperswitch by mapping customer data between our domain models and Chargebee’s API.
Key Changes
-
New Connector Integration
- Added
ConnectorIntegration<CreateConnectorCustomer, ConnectorCustomerData, PaymentsResponseData>implementation for Chargebee. - Added response mapper to convert Chargebee’s response into
PaymentsResponseData::ConnectorCustomerResponse.
- Added
-
Extended Response Model
-
ConnectorCustomerResponsenow carries optional fields:nameemailbilling_address
-
-
Domain Models & Flow Types
- Extended
ConnectorCustomerDatato support new fields (customer_id,billing_address).
- Extended
Benefits
- Merchants can now create customers in Chargebee via Hyperswitch.
- Unified model for customer creation across connectors.
- Future-proofing: response carries richer customer metadata, making subscription flows easier to support.
How did you test it?
cargo r
just clippy
just clippy_v2
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_7/'
- 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 implement the Chargebee connector's customer creation feature. Let me start by understanding the current codebase structure and identifying the key files that need to be modified.
First, let me explore the repository structure to understand how connectors are organized:
- Adding a new connector integration for Chargebee customer creation
- Extending response models to include customer metadata
- Modifying domain models to support new fields
Let me start by exploring the repository structure to understand where connector implementations are located and how they're organized.
Assistant
Let me explore the broader connector structure to understand how Chargebee is implemented:
Assistant
(no content)
Assistant
Let me look at the chargebee connector directory specifically:
Assistant
(no content)
Assistant
Now let me check the main connector module to understand how connectors are structured:
Assistant
(no content)
Assistant
(no content)
Assistant
Let me look at the domain models to understand the connector customer data structures:
Assistant
(no content)
Assistant
Let me check the domain models for connector customer data:
Assistant
(no content)
Assistant
Let me also check the existing connector integration traits to understand how connector integrations work:
Assistant
(no content)
Assistant
(no content)
Assistant
Let me check the types module to understand connector integration:
Assistant
(no content)
Assistant
Let me check the connector integration interface definition in hyperswitch_interfaces:
Assistant
(no content)
Assistant
Now I need to understand what connector flow types exist to see how I should add the customer creation functionality. Let me look at what flow types exist in the router_flow_types:
Assistant
(no content)
Assistant
Let me check what's in the payments module for router flow types:
Assistant
Great! I can see there's already a
CreateConnectorCustomerflow type defined. This is what I need to implement for the Chargebee connector. Now I'll look at a few more files to understand the complete structure. Let me also look at some connector examples to see the pattern:Assistant
Let me look at what the current state of the Chargebee implementation looks like and then create a plan for implementing the connector customer creation.
Assistant
Now I need to examine what existing implementations look like for customer creation to understand the pattern. Let me search for similar implementations in other connectors:
Assistant
Let me look at one of these implementations, for example, Stripe's implementation to understand the pattern:
Assistant
(no content)
Assistant
Let me check what's in the default implementations file to understand the pattern:
Assistant
Let me see more of this file to find the connector customer implementation pattern:
Assistant
Let me also look at how ConnectorCustomer is defined in other connectors, especially looking at a simpler connector implementation to get the full picture. Let me focus on actually creating the implementation now:
Assistant
Let me look for more specific examples of how CreateConnectorCustomer is implemented in other connectors to understand the pattern:
Assistant
Let me approach this differently. I'll implement the functionality needed for the Chargebee connector to create customers based on what I understand from the task description. Based on my research, I need to:
- Extend ConnectorCustomerData to include customer_id and billing_address fields
- Implement the ConnectorIntegration for CreateConnectorCustomer with Chargebee
- Add response mapper for ConnectorCustomerResponse
Let me start with the main chargebee implementation file to add these changes:
Assistant
Let me find the correct location to add this:
Assistant
(no content)
Assistant
Now I'll add the customer response structs after the payments response struct:
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 →