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_8 (already cloned)
- Base commit: 8446ffbf5992a97d79d129cade997effc60fcd85
- Task ID: juspay__hyperswitch-9028
- Version: v1.116.0
TASK DESCRIPTION: Bug: [FEATURE] CELERO CIT_MIT (ALPHACONNECTOR)
Feature Description
IMPLEMENT CIT & MIT for celero
Possible Implementation
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?
None
DETAILED CONTEXT & HINTS:
Type of Change
- Bugfix
- New feature
- Enhancement
- Refactoring
- Dependency updates
- Documentation
- CI/CD
Description
CIT-MIT implementation for CELERO (alpha connector)
DOCS
Caviats
- Connector expecting initial_transaction_id which is nothing but prev txn id
- Connector not returning
payment_method_idormandate_id
Note this is an alpha connector and we depend on alpha cypress test which
Additional Changes
- This PR modifies the API contract
- This PR modifies the database schema
- This PR modifies application configuration/environment variables
Motivation and Context
How did you test it?
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_8/'
- 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 CIT & MIT for Celero alpha connector. Let me start by understanding the current implementation and then make the necessary changes.
First, let me explore the repository structure to locate the Celero connector implementation.
Assistant
(no content)
Assistant
Let me first look at the Celero connector implementation to understand its current structure and then check for any existing CIT/MIT related code.
Assistant
Let me examine the main Celero connector implementation file:
Assistant
Now let me check the transformers module to understand how the Celero connector handles requests and responses:
Assistant
Let me also check the existing tests for the Celero connector to understand how it's tested:
Assistant
Let me also examine the configuration files to see how the Celero connector is set up:
Assistant
(no content)
Assistant
Let me search for the Celero configuration in the config files:
Assistant
(no content)
Assistant
Let me also check the documentation link mentioned in the task to understand what CIT & MIT means for this connector:
Assistant
Let me now look at the existing connector specifications and understand how mandate-based payments work in the hyperswitch system to determine what needs to be implemented for CIT & MIT:
Assistant
Now let me search for CIT and MIT related implementations in the codebase:
Assistant
Let me check one of the connectors that might have CIT/MIT implementation to understand the pattern:
Assistant
Let me check the existing mandate setup flow to understand what's needed:
Assistant
Let me examine the mandate flow in more detail to understand how it works in the system:
Assistant
Let me examine the connector's current implementation of mandate setup and how the supported features are defined:
Assistant
Looking at the existing code, I can see that the Celero connector doesn't currently have support for SetupMandate, and from the supported features in the connector configuration, it shows that mandates are marked as "NotSupported".
Let me now plan the implementation. Based on the documentation and typical payment processor behavior, CIT (Cardholder Initiated Transaction) and MIT (Merchant Initiated Transaction) are typically mandate-based payment types where:
- CIT: Customer initiates the transaction using saved payment method details
- MIT: Merchant initiates the transaction using saved payment method details (for recurring payments)
I need to:
- Enable mandate support in the connector
- Add CIT/MIT specific request handling
- Handle the required transaction fields like initial_transaction_id
Let me first create a detailed implementation plan:
Assistant
Based on my analysis of the codebase, I now understand what needs to be done to implement CIT & MIT for the Celero connector.
Looking at the current implementation, I can see:
- The Celero connector currently has mandates marked as
NotSupportedin its supported features - There's no
SetupMandateimplementation in the connector - The payment flow doesn't handle CIT/MIT specific parameters
Let me now implement the required changes to enable CIT & MIT support in the Celero connector.
First, I'll update the supported features to indicate mandate support:
- The Celero connector currently has mandates marked as
Assistant
Let me get the exact text from the file to match correctly:
Assistant
I see there's a typo in the code - it says
supported_card_networkinstead ofsupported_card_networks. Let me fix this and update the mandate support:Assistant
I need to understand more about how CIT/MIT payments work before making code changes. Let me research this further.
Assistant
Let me check what the actual test configuration says to better understand the current state:
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 →