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: a56d78a46a3ee80cdb2b48f9abfd2cd7b297e328
- Task ID: juspay__hyperswitch-8575
- Version: v1.116.0
TASK DESCRIPTION: Bug: [FEATURE] Cellero commerce integration
Feature Description
Integrate celero commerce Connector
Possible Implementation
Celero commerce integration
Have you spent some time checking if this feature request 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?
Yes, I am willing to submit a PR!
DETAILED CONTEXT & HINTS:
Type of Change
- Bugfix
- New feature
- Enhancement
- Refactoring
- Dependency updates
- Documentation
- CI/CD
Description
Integrate celero commerce connector
Doc : https://sandbox.gotnpgateway.com/docs/api/transactions [x] Cards [x] Avs
Additional Changes
- This PR modifies the API contract
- This PR modifies the database schema
- This PR modifies application configuration/environment variables
MOCK SERVER results
Motivation and Context
https://github.com/juspay/hyperswitch/issues/8575
How did you test it?
No creds for testing
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 Celero Commerce connector integration for the Hyperswitch payment processing system. Let me start by exploring the repository structure to understand how connectors are implemented.
First, I'll create a todo list to track the implementation steps:
Assistant
Let me first explore the repository structure to understand how connectors are organized:
Assistant
Now let me examine the existing Celero connector implementation to understand what's already there and what needs to be completed:
Assistant
Let me look at the existing Celero connector implementation to understand what's already there:
Assistant
Now let me check the transformer module to understand the data structures:
Assistant
Let me also look at some working connector implementations to understand the proper patterns. Let me check the Checkout connector as a good example:
Assistant
Let me also look at the configuration files to understand how connectors are registered:
Assistant
Let me look at the main config files to understand the structure better:
Assistant
Let me also look at the connectors configuration file:
Assistant
Let me check the connector endpoints to understand how connectors are defined:
Assistant
(no content)
Assistant
Perfect! I can see that Celero is already included in the connector endpoints as a
ConnectorParamstype on line 37. Now I have a good understanding of the structure. Let me update my todos to focus on the actual implementation tasks:Assistant
Let me now look at a working connector to understand how to properly implement the missing parts. Let me check the checkout connector implementation in more detail:
Assistant
Now I have a better understanding of how to properly implement the Celero connector. Let me check what the API documentation says by looking at the provided mock server screenshots and API endpoints. But first, let me implement the complete Celero connector based on the existing patterns.
Assistant
Let me now completely rewrite the Celero connector implementation with proper functionality:
Assistant
Let me first create a proper implementation of the Celero connector file. Since the current implementation is incomplete, I'll create a complete implementation based on what I understand of the connector patterns:
Assistant
Let me first read the complete current file to understand what exactly needs to be replaced:
Assistant
Now let me replace the complete implementation with a proper one by creating a new file with the correct content:
Assistant
Let me create the new file content for the Celero connector:
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 →