Dataset Viewer
prompt
stringlengths 24
6.44k
| response
stringlengths 728
14.4k
| metadata
stringlengths 148
152
|
|---|---|---|
refactor(permissions): Deprecate permissions from permission info API response
The permissions in the permission info API are not being used and should be removed.
|
<think>
PR Context:
- Title: refactor(permissions): Remove permissions field from permission info API response
- Merged: 2024-10-22T10:15:42Z
- Files changed: 4 files
- Commits: 1 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [ ] New feature
- [ ] Enhancement
- [x] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
<!-- Describe your changes in detail -->
The permissions in the permission info API are not being used and this PR will remove them.
This will help the future PRs which will introduce new kind of Permissions.
### Additional Changes
- [x] This PR modifies the API contract
-
</think>
To implement this, you'll need to modify:
**Detailed Implementation:**
**Commit 1:** refactor(permissions): Remove permissions field from permission info API response (#6376)
Files to modify:
**crates/api_models/src/user_role.rs**
Remove:
- struct: pub::PermissionInfo
- enum: pub::Permission
**crates/router/src/services/authorization/info.rs**
Remove:
- function: pub::get_permission_info_from_permissions
**crates/router/src/services/authorization/permissions.rs**
Remove:
- function: pub::get_permission_description
- impl: impl Permission
**crates/router/src/utils/user_role.rs**
Remove:
- function: private::from
- impl: impl From<Permission> for user_role_api::Permission
|
{"issue_number": 6375, "pr_number": 6376, "commits_count": 1, "files_changed": 4, "response_length": 1448, "file_count": 6, "needs_breakdown": false}
|
[FIX] Re-revert changes done in `pr#7866` by `pr#7882`
### Context
[PR#7882](https://github.com/juspay/hyperswitch/pull/7882) accidentally reverted changes made in [PR#7882](https://github.com/juspay/hyperswitch/pull/7866), which was a merchant critical PR.
### Proposed Fix
Re revert the changes.
|
<think>
PR Context:
- Title: fix(payment_methods): Re-revert changes done in `pr#7866` by `pr#7882`
- Merged: 2025-05-05T12:58:42Z
- Files changed: 1 files
- Commits: 1 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [x] Bugfix
- [ ] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
<!-- Describe your changes in detail -->
Context
https://github.com/juspay/hyperswitch/pull/7882 accidentally reverted changes made in https://github.com/juspay/hyperswitch/pull/7866, which was a merchant critical PR.
Reason:
- This might have occured due to incorrect resolution
</think>
To implement this, you'll need to modify:
**Detailed Implementation:**
**Commit 1:** fix(payment_methods): Re-revert changes done in `pr#7866` by `pr#7882` (#7954)
Files to modify:
**crates/router/src/core/payment_methods/cards.rs**
Modify existing code
|
{"issue_number": 7952, "pr_number": 7954, "commits_count": 1, "files_changed": 1, "response_length": 975, "file_count": 3, "needs_breakdown": false}
|
[BUG] Logging sensitive information on deserialization failure
### Bug Description
In `common_utils/src/ext_traits.rs` we are logging serde_json Values in plaintext when deserialization fails. This is a problem in cases where the JSON objects contain sensitive data.
### Expected Behavior
Sensitive data is not logged. Values are logged after masking.
### Actual Behavior
Sensitive information is logged.
### Steps To Reproduce
Supply malformed data to the `parse_value` method in `ValueExt` trait.
### Context For The Bug
_No response_
### Environment
Are you using hyperswitch hosted version? Yes
### Have you spent some time checking if this bug has been raised before?
- [x] I checked and didn't find a similar issue
### Have you read the Contributing Guidelines?
- [x] I have read the [Contributing Guidelines](https://github.com/juspay/hyperswitch/blob/main/docs/CONTRIBUTING.md)
### Are you willing to submit a PR?
Yes, I am willing to submit a PR!
|
<think>
PR Context:
- Title: fix(common_utils): Prevent logging sensitive information on deserialization failure
- Merged: 2025-09-24T13:24:48Z
- Files changed: 1 files
- Commits: 6 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [x] Bugfix
- [ ] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
- Modified `parse_value` method in `ValueExt` trait to log the JSON object after masking on deserialization failure.
- Modified `parse_struct` method in `BytesExt`, `ByteSliceExt` and `StringExt` to log values after converting them into a `serde_json::Value` and then masking
### A
</think>
To implement this, you'll need to modify:
**Detailed Implementation:**
**Commit 1:** fix(common_utils): Prevent logging sensitive information on deserialization failure (#8970)
Files to modify:
**crates/common_utils/src/ext_traits.rs**
Modify existing code
|
{"issue_number": 8969, "pr_number": 8970, "commits_count": 1, "files_changed": 1, "response_length": 991, "file_count": 3, "needs_breakdown": false}
|
[CHORE] FIX TYPOS IN THE REPO
Its been months since the typos in the repo being unaddressed.
This has resulted in negligence leading to even more typos being introduced.
|
<think>
PR Context:
- Title: chore: fix typos in the repo
- Merged: 2025-05-23T07:52:09Z
- Files changed: 29 files
- Commits: 9 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [ ] New feature
- [ ] Enhancement
- [x] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
<!-- Describe your changes in detail -->
This PR updates all the typos in the repository. For reference, check: https://github.com/juspay/hyperswitch/actions/runs/15082629873/job/42401247676?pr=8056
### Additional Changes
- [ ] This PR modifies the API contract
- [ ] This PR
</think>
To implement this, you'll need to modify:
**Detailed Implementation:**
**Commit 1:** chore: fix typos in the repo (#8063)
Co-authored-by: hyperswitch-bot[bot] <148525504+hyperswitch-bot
Files to modify:
**crates/api_models/src/payments.rs**
Modify existing code
**crates/common_types/src/payment_methods.rs**
Modify existing code
**crates/common_utils/src/macros.rs**
Modify existing code
**crates/common_utils/src/types.rs**
Modify existing code
**crates/hyperswitch_connectors/src/connectors/braintree/transformers.rs**
Modify existing code
**crates/hyperswitch_connectors/src/connectors/fiuu/transformers.rs**
Remove:
- struct: pub::FiuuWebhookSignauture
Add:
- struct: pub::FiuuWebhookSignature
**crates/hyperswitch_connectors/src/connectors/recurly.rs**
Modify existing code
**crates/hyperswitch_connectors/src/connectors/worldpay/response.rs**
Modify existing code
**crates/hyperswitch_domain_models/src/router_request_types/unified_authentication_service.rs**
Modify existing code
**crates/router/src/core/payment_methods.rs**
Modify existing code
**crates/router/src/core/payments.rs**
Modify existing code
**crates/router/src/core/payments/retry.rs**
Modify existing code
**crates/router/src/core/revenue_recovery.rs**
Modify existing code
**crates/router/src/core/unified_authentication_service.rs**
Modify existing code
**crates/router/src/utils/currency.rs**
Modify existing code
|
{"issue_number": 8064, "pr_number": 8063, "commits_count": 1, "files_changed": 29, "response_length": 2124, "file_count": 17, "needs_breakdown": true}
|
One click docker setup
A script is needed to ensure one click docker setup, to minimise issues faced by users.
> Run the whole setup with simple command
> Show output with localhost links for different setups
|
<think>
PR Context:
- Title: feat(deploy): Add one-click Docker setup script
- Merged: 2025-05-02T12:35:09Z
- Files changed: 4 files
- Commits: 15 commits
Implementation approach:
Implements a comprehensive bash script that simplifies the Hyperswitch Docker setup process with the following features:
- Prerequisites checking for Docker and Docker Compose
- Port availability validation
- Multiple deployment profiles (Minimal, Standard, Full, Development)
- Automatic configuration setup
- Service health monitoring
- Detailed documentation in README.md and docs/one_click_setup.md
Resolves issue #7761
## Type of Change
<!-- Put an `x` in the boxes that apply -->
</think>
To implement this, you'll need to modify:
(No detailed commit information available)
|
{"issue_number": 7761, "pr_number": 7804, "commits_count": 0, "files_changed": 4, "response_length": 778, "file_count": 0, "needs_breakdown": false}
|
[REFACTOR] Worldpay payments integration
### Feature Description
WorldPay payments integration currently makes use of modular APIs which gives more control over the integration. This approach is not best compatible with HyperSwitch due to WP's 3DS flows - which requires sending PAN (card numbers) in multiple places. For `on_session` transactions, this would contribute to the added complexity since data is not stored in such transactions (or stored for ~15mins in redis cache).
Migrating to WP's standard payments API follows payment resource creation in an uniform way.
### Possible Implementation
Migrate from modular APIs [[ref](https://developer.worldpay.com/products/access/card-payments)] to standard payment APIs [[ref](https://developer.worldpay.com/products/access/payments/openapi)].
### Have you spent some time checking if this feature request has been raised before?
- [X] I checked and didn't find a similar issue
### Have you read the Contributing Guidelines?
- [X] I have read the [Contributing Guidelines](https://github.com/juspay/hyperswitch/blob/main/docs/CONTRIBUTING.md)
### Are you willing to submit a PR?
Yes, I am willing to submit a PR!
|
<think>
PR Context:
- Title: refactor(connector): [WorldPay] propagate refusal codes as error code and messages
- Merged: 2024-10-22T13:03:52Z
- Files changed: 3 files
- Commits: 1 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [ ] New feature
- [x] Enhancement
- [x] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
Described in #6316 (point # 2)
### Additional Changes
- [ ] This PR modifies the API contract
- [ ] This PR modifies the database schema
- [ ] This PR modifies application configuration/environment variables
<!--
Provide links to the files with corresponding changes.
Fo
</think>
To implement this, you'll need to modify:
**Detailed Implementation:**
**Commit 1:** refactor(connector): [WorldPay] propagate refusal codes as error code and messages (#6392)
Files to modify:
**crates/router/src/connector/worldpay.rs**
Add:
- function: private::get_5xx_error_response
- function: private::get_5xx_error_response
- function: private::get_5xx_error_response
- function: private::get_5xx_error_response
- function: private::get_5xx_error_response
**crates/router/src/connector/worldpay/response.rs**
Modify existing code
**crates/router/src/connector/worldpay/transformers.rs**
Modify existing code
|
{"issue_number": 6316, "pr_number": 6392, "commits_count": 1, "files_changed": 3, "response_length": 1373, "file_count": 5, "needs_breakdown": false}
|
refactor(tenant): use tenant id type
Refactor: Use tenant_id type instead of string for better type safety
|
<think>
PR Context:
- Title: refactor(tenant): use tenant id type
- Merged: 2024-11-26T09:12:05Z
- Files changed: 30 files
- Commits: 6 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [ ] New feature
- [ ] Enhancement
- [x] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
Use tenant_id type for better type safety
### Additional Changes
- [ ] This PR modifies the API contract
- [ ] This PR modifies the database schema
- [ ] This PR modifies application configuration/environment variables
<!--
Provide links to the files with corresponding c
</think>
To implement this, you'll need to modify:
**Detailed Implementation:**
**Commit 1:** refactor(tenant): use tenant id type (#6643)
Co-authored-by: hyperswitch-bot[bot] <148525504+hypersw
Files to modify:
**crates/common_utils/src/id_type.rs**
Add:
- mod: private::tenant
**crates/common_utils/src/id_type/organization.rs**
Modify existing code
**crates/common_utils/src/id_type/tenant.rs**
Add:
- function: pub::try_from_string
- impl: impl TenantId
**crates/common_utils/src/types/theme.rs**
Modify existing code
**crates/diesel_models/src/user/theme.rs**
Modify existing code
**crates/diesel_models/src/user_role.rs**
Modify existing code
**crates/drainer/src/handler.rs**
Modify existing code
**crates/drainer/src/health_check.rs**
Modify existing code
**crates/drainer/src/lib.rs**
Modify existing code
**crates/drainer/src/settings.rs**
Remove:
- struct: pub::TenantConfig
Add:
- struct: pub::TenantConfig
**crates/router/src/configs/settings.rs**
Remove:
- struct: pub::TenantConfig
Add:
- struct: pub::TenantConfig
**crates/router/src/core/payment_methods/transformers.rs**
Modify existing code
**crates/router/src/core/routing/helpers.rs**
Modify existing code
**crates/router/src/core/user.rs**
Modify existing code
**crates/router/src/db/events.rs**
Modify existing code
**crates/router/src/db/merchant_connector_account.rs**
Modify existing code
**crates/router/src/db/merchant_key_store.rs**
Modify existing code
**crates/router/src/routes/app.rs**
Modify existing code
**crates/router/src/services/api.rs**
Modify existing code
**crates/router/src/services/authentication.rs**
Modify existing code
**crates/router/src/services/authorization.rs**
Modify existing code
**crates/router/src/types/domain/user.rs**
Modify existing code
**crates/router/src/utils/user.rs**
Modify existing code
**crates/router/tests/cache.rs**
Modify existing code
**crates/router/tests/connectors/aci.rs**
Modify existing code
**crates/router/tests/connectors/utils.rs**
Modify existing code
**crates/router/tests/payments.rs**
Modify existing code
**crates/router/tests/payments2.rs**
Modify existing code
**crates/router/tests/services.rs**
Modify existing code
**crates/scheduler/src/consumer.rs**
Modify existing code
**crates/scheduler/src/producer.rs**
Modify existing code
**crates/scheduler/src/scheduler.rs**
Modify existing code
|
{"issue_number": 6642, "pr_number": 6643, "commits_count": 1, "files_changed": 30, "response_length": 3142, "file_count": 34, "needs_breakdown": true}
|
[BUG] fix(payments): add connector error details in response when payment void fails
### Bug Description
When a payment void fails at the connector level, the error was not being propagated back in the API response.
This change ensures connector error details are included in the response, so clients can handle failures appropriately.
### Expected Behavior
When a payment void fails at the connector level, the error was not being propagated back in the API response.
This change ensures connector error details are included in the response, so clients can handle failures appropriately.
### Actual Behavior
Currently error is not coming in payment void if failed at connector level.
### Steps To Reproduce
Provide an unambiguous set of steps to reproduce this bug. Include code or configuration to reproduce, if relevant.
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
### Context For The Bug
_No response_
### Environment
Are you using hyperswitch hosted version? Yes/No
If yes, please provide the value of the `x-request-id` response header to help us debug your issue.
If not (or if building/running locally), please provide the following details:
1. Operating System or Linux distribution:
2. Rust version (output of `rustc --version`): ``
3. App version (output of `cargo r --features vergen -- --version`): ``
### Have you spent some time checking if this bug has been raised before?
- [x] I checked and didn't find a similar issue
### Have you read the Contributing Guidelines?
- [x] I have read the [Contributing Guidelines](https://github.com/juspay/hyperswitch/blob/main/docs/CONTRIBUTING.md)
### Are you willing to submit a PR?
Yes, I am willing to submit a PR!
|
<think>
PR Context:
- Title: fix(payments): update error handling for payment void v2
- Merged: 2025-10-07T08:22:58Z
- Files changed: 6 files
- Commits: 17 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [x] Bugfix
- [ ] New feature
- [x] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
<!-- Describe your changes in detail -->
Add error details when payment void is failed at connector level and update the status accordingly.
### Additional Changes
- [x] This PR modifies the API contract
- [ ] This PR modifies the database schema
- [ ] This PR modifies applic
</think>
To implement this, you'll need to modify:
**Detailed Implementation:**
**Commit 1:** fix(payments): update error handling for payment void v2 (#9595)
Co-authored-by: hyperswitch-bot[bot
Files to modify:
**crates/api_models/src/payments.rs**
Modify existing code
**crates/hyperswitch_domain_models/src/router_data.rs**
Modify existing code
**crates/hyperswitch_domain_models/src/router_data_v2/flow_common_types.rs**
Modify existing code
**crates/hyperswitch_interfaces/src/conversion_impls.rs**
Modify existing code
**crates/router/src/core/payments/transformers.rs**
Modify existing code
|
{"issue_number": 9616, "pr_number": 9595, "commits_count": 1, "files_changed": 6, "response_length": 1309, "file_count": 7, "needs_breakdown": false}
|
feat(analytics): add `sessionized_metrics` for disputes (backwards compatibility)
## Current Behaviour
- There is no `sessionized_metrics` module for disputes like there is for `payments` and `payment_intents`
## Proposed Changes
- create `sessionized_metrics` module for disputes
|
<think>
PR Context:
- Title: feat(analytics): add `sessionized_metrics` for disputes analytics
- Merged: 2024-11-26T13:58:33Z
- Files changed: 13 files
- Commits: 6 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [x] New feature
- [x] Enhancement
- [x] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
<!-- Describe your changes in detail -->
- Add sessionized metrics module and implement backwards compatibility.
- Add the `sessionizer_dispute` table support for Sessionized metrics.
### Fixes #6572
### Additional Changes
- [ ] This PR modifies the API contract
- [ ] This PR
</think>
To implement this, you'll need to modify:
**Detailed Implementation:**
**Commit 1:** feat(analytics): add `sessionized_metrics` for disputes analytics (#6573)
Co-authored-by: hyperswitc
Files to modify:
**crates/analytics/src/clickhouse.rs**
Modify existing code
**crates/analytics/src/disputes/accumulators.rs**
Modify existing code
**crates/analytics/src/disputes/core.rs**
Modify existing code
**crates/analytics/src/disputes/metrics.rs**
Add:
- mod: private::sessionized_metrics
**crates/analytics/src/disputes/metrics/sessionized_metrics/dispute_status_metric.rs**
Add:
- function: private::load_metrics
- struct: pub::DisputeStatusMetric
- impl: impl super::DisputeMetric<T> for DisputeStatusMetric
**crates/analytics/src/disputes/metrics/sessionized_metrics/mod.rs**
Add:
- mod: private::dispute_status_metric
- mod: private::total_amount_disputed
- mod: private::total_dispute_lost_amount
**crates/analytics/src/disputes/metrics/sessionized_metrics/total_amount_disputed.rs**
Add:
- function: private::load_metrics
- struct: pub::TotalAmountDisputed
- impl: impl super::DisputeMetric<T> for TotalAmountDisputed
**crates/analytics/src/disputes/metrics/sessionized_metrics/total_dispute_lost_amount.rs**
Add:
- function: private::load_metrics
- struct: pub::TotalDisputeLostAmount
- impl: impl super::DisputeMetric<T> for TotalDisputeLostAmount
**crates/analytics/src/sqlx.rs**
Modify existing code
**crates/analytics/src/types.rs**
Modify existing code
**crates/api_models/src/analytics.rs**
Add:
- struct: pub::DisputesAnalyticsMetadata
- struct: pub::DisputesMetricsResponse
**crates/api_models/src/analytics/disputes.rs**
Modify existing code
**crates/api_models/src/events.rs**
Add:
- function: private::get_api_event_type
- impl: impl ApiEventMetric for DisputesMetricsResponse<T>
|
{"issue_number": 6572, "pr_number": 6573, "commits_count": 1, "files_changed": 13, "response_length": 2614, "file_count": 15, "needs_breakdown": false}
|
feat(router): Add `eligible_connector` to PML response (v2)
We need to return `eligible_connector` in PML response, required by SDK
|
<think>
PR Context:
- Title: feat(router): Return eligible_connector in PML for payment (v2)
- Merged: None
- Files changed: 3 files
- Commits: 2 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [x] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
<!-- Describe your changes in detail -->
Add `eligible_connector` in PML response
### Additional Changes
- [ ] This PR modifies the API contract
- [ ] This PR modifies the database schema
- [ ] This PR modifies application configuration/environment variables
<!--
Provide
</think>
To implement this, you'll need to modify:
(No detailed commit information available)
|
{"issue_number": 8375, "pr_number": 8376, "commits_count": 0, "files_changed": 3, "response_length": 777, "file_count": 0, "needs_breakdown": false}
|
feat(connector): add template code for stripebilling
add a template code for stripe billing connector
|
<think>
PR Context:
- Title: feat(connector): add template code for stripebilling
- Merged: None
- Files changed: 30 files
- Commits: 2 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [ ] New feature
- [x] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
connector integration template code for stripe billing.
Issue: This PR closes the issue #7212
### Additional Changes
- [ ] This PR modifies the API contract
- [ ] This PR modifies the database schema
- [ ] This PR modifies application configuration/environment variables
</think>
To implement this, you'll need to modify:
(No detailed commit information available)
|
{"issue_number": 7212, "pr_number": 7214, "commits_count": 0, "files_changed": 30, "response_length": 767, "file_count": 0, "needs_breakdown": false}
|
[FEATURE]: Enable client_secret auth for payments - Get Intent [v2]
Required for SDK
|
<think>
PR Context:
- Title: feat(router): Enable client_secret auth for payments_get_intent [v2]
- Merged: 2025-05-27T10:56:27Z
- Files changed: 1 files
- Commits: 1 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [x] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
<!-- Describe your changes in detail -->
Added support for `client_secret` authentication in `Payments - Get Intent`
### Additional Changes
- [ ] This PR modifies the API contract
- [ ] This PR modifies the database schema
- [ ] This PR modifies application configuration/envi
</think>
To implement this, you'll need to modify:
**Detailed Implementation:**
**Commit 1:** feat(router): Enable client_secret auth for payments_get_intent [v2] (#8119)
Files to modify:
**crates/router/src/routes/payments.rs**
Modify existing code
|
{"issue_number": 8118, "pr_number": 8119, "commits_count": 1, "files_changed": 1, "response_length": 960, "file_count": 3, "needs_breakdown": false}
|
[FEATURE] Cypress test for UCS through Hyperswitch
### Feature Description
there should be a cypress test supported for ucs through hyperswitch
### Possible Implementation
make code changes in cypress folder and call ucs related api's
### Have you spent some time checking if this feature request has been raised before?
- [x] I checked and didn't find a similar issue
### Have you read the Contributing Guidelines?
- [x] I have read the [Contributing Guidelines](https://github.com/juspay/hyperswitch/blob/main/docs/CONTRIBUTING.md)
### Are you willing to submit a PR?
None
|
<think>
PR Context:
- Title: feat(cypress): Cypress test for ucs
- Merged: 2025-09-02T15:36:00Z
- Files changed: 5 files
- Commits: 30 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [x] New feature
- [x] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
<!-- Describe your changes in detail -->
added cypress test for ucs by maintaing the flow
Closes #8968
### Additional Changes
- [ ] This PR modifies the API contract
- [ ] This PR modifies the database schema
- [ ] This PR modifies application configuration/environment vari
</think>
To implement this, you'll need to modify:
(No detailed commit information available)
|
{"issue_number": 8968, "pr_number": 8967, "commits_count": 0, "files_changed": 5, "response_length": 766, "file_count": 0, "needs_breakdown": false}
|
[REFACTOR] facilitapay destination bank account number should be merchant facing
destination bank account number should be added by merchant, not customer. this is a design flaw that needs to be fixed.
|
<think>
PR Context:
- Title: refactor(connector): [facilitapay] move destination bank account number to connector metadata
- Merged: 2025-07-25T12:44:09Z
- Files changed: 11 files
- Commits: 7 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [ ] New feature
- [ ] Enhancement
- [x] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
<!-- Describe your changes in detail -->
Destination bank account id should be merchant facing, not customer. This PR removes any references to destination bank account id and moves it to connector metadata instead.
### Additional Changes
- [ ] This PR modifies the API contra
</think>
To implement this, you'll need to modify:
**Detailed Implementation:**
**Commit 1:** refactor(connector): [facilitapay] move destination bank account number to connector metadata (#8704
Files to modify:
**crates/api_models/src/payments.rs**
Modify existing code
**crates/api_models/src/payments/additional_info.rs**
Modify existing code
**crates/hyperswitch_connectors/src/connectors/facilitapay/transformers.rs**
Remove:
- function: private::from_auth_type
- function: private::try_from
- function: private::try_from
- struct: pub::FacilitapayAuthType
- impl: impl FacilitapayAuthRequest
- impl: impl TryFrom<&ConnectorAuthType> for FacilitapayAuthType
- impl: impl TryFrom<&RefreshTokenRouterData> for FacilitapayAuthRequest
Add:
- function: private::from_auth_type
- function: private::try_from
- function: private::try_from
- function: private::try_from
- struct: pub::FacilitapayAuthType
- struct: pub::FacilitapayConnectorMetadataObject
- impl: impl FacilitapayAuthRequest
- impl: impl TryFrom<&ConnectorAuthType> for FacilitapayAuthType
- impl: impl TryFrom<&RefreshTokenRouterData> for FacilitapayAuthRequest
- impl: impl TryFrom<&Option<pii::SecretSerdeValue>> for FacilitapayConnectorMetadataObject
**crates/payment_methods/src/configs/payment_connector_required_fields.rs**
Modify existing code
**crates/router/src/core/connector_validation.rs**
Modify existing code
|
{"issue_number": 8703, "pr_number": 8704, "commits_count": 1, "files_changed": 11, "response_length": 2205, "file_count": 7, "needs_breakdown": false}
|
Update broken readme icon
Updating broken readme icon along with reposition of the hero image
|
<think>
PR Context:
- Title: docs(README): Updated the icon and repositioned the hero image
- Merged: 2024-11-03T14:12:33Z
- Files changed: 1 files
- Commits: 2 commits
Implementation approach:
TOC icon and reposition of the hero image in readme
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [ ] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [x] Documentation
- [ ] CI/CD
## Description
<!-- Describe your changes in detail -->
Updated the icon of CI Push and repositioned the hero image
closes #6449
### Additional Changes
- [ ] This PR modifies the API contract
- [ ] This PR modifies the database schema
</think>
To implement this, you'll need to modify:
(No detailed commit information available)
|
{"issue_number": 6449, "pr_number": 6445, "commits_count": 0, "files_changed": 1, "response_length": 792, "file_count": 0, "needs_breakdown": false}
|
[REFACTOR] Worldpay payments integration
### Feature Description
WorldPay payments integration currently makes use of modular APIs which gives more control over the integration. This approach is not best compatible with HyperSwitch due to WP's 3DS flows - which requires sending PAN (card numbers) in multiple places. For `on_session` transactions, this would contribute to the added complexity since data is not stored in such transactions (or stored for ~15mins in redis cache).
Migrating to WP's standard payments API follows payment resource creation in an uniform way.
### Possible Implementation
Migrate from modular APIs [[ref](https://developer.worldpay.com/products/access/card-payments)] to standard payment APIs [[ref](https://developer.worldpay.com/products/access/payments/openapi)].
### Have you spent some time checking if this feature request has been raised before?
- [X] I checked and didn't find a similar issue
### Have you read the Contributing Guidelines?
- [X] I have read the [Contributing Guidelines](https://github.com/juspay/hyperswitch/blob/main/docs/CONTRIBUTING.md)
### Are you willing to submit a PR?
Yes, I am willing to submit a PR!
|
<think>
PR Context:
- Title: fix(connector): [Worldpay] use 4 digit expiry year
- Merged: 2024-11-19T15:34:37Z
- Files changed: 3 files
- Commits: 2 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [x] Bugfix
- [ ] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
Described in #6316 point # 7
### Additional Changes
- [ ] This PR modifies the API contract
- [ ] This PR modifies the database schema
- [ ] This PR modifies application configuration/environment variables
<!--
Provide links to the files with corresponding changes.
Fo
</think>
To implement this, you'll need to modify:
**Detailed Implementation:**
**Commit 1:** fix(connector): [Worldpay] use 4 digit expiry year (#6543)
Files to modify:
**crates/hyperswitch_connectors/src/connectors/worldpay/transformers.rs**
Modify existing code
**crates/hyperswitch_connectors/src/utils.rs**
Add:
- function: private::get_expiry_year_as_4_digit_i32
|
{"issue_number": 6316, "pr_number": 6543, "commits_count": 1, "files_changed": 3, "response_length": 1068, "file_count": 4, "needs_breakdown": false}
|
feat(router): Include `payment_experience` in PML for payments response (v2)
Required by SDK
|
<think>
PR Context:
- Title: feat(router): Return payment_experience in PML for payment (v2)
- Merged: 2025-06-05T16:40:31Z
- Files changed: 3 files
- Commits: 1 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [x] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
<!-- Describe your changes in detail -->
Added `payment_experience` in Payment Method List for Payments Response
### Additional Changes
- [x] This PR modifies the API contract
- [ ] This PR modifies the database schema
- [ ] This PR modifies application configuration/environm
</think>
To implement this, you'll need to modify:
**Detailed Implementation:**
**Commit 1:** feat(router): Return payment_experience in PML for payment (v2) (#8255)
Files to modify:
**crates/api_models/src/payments.rs**
Modify existing code
**crates/router/src/core/payments/payment_methods.rs**
Modify existing code
|
{"issue_number": 8254, "pr_number": 8255, "commits_count": 1, "files_changed": 3, "response_length": 1026, "file_count": 4, "needs_breakdown": false}
|
Add audit events for PaymentCreate update
Created from https://github.com/juspay/hyperswitch/issues/4525
This covers adding events for PaymentCreate operation
This event should include the payment data similar to https://github.com/juspay/hyperswitch/pull/4166
It should also include any metadata for the event
e.g reason for payment rejection, error codes, rejection source etc
|
<think>
PR Context:
- Title: feat(payments): Add audit events for PaymentCreate update
- Merged: 2024-11-07T13:39:25Z
- Files changed: 2 files
- Commits: 4 commits
Implementation approach:
## Type of Change
- [ ] Bugfix
- [x] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
This PR adds an Audit event for the PaymentCreate operation.
### Additional Changes
- [x] This PR modifies the files below
- `crates/router/src/core/payments/operations/payment_create.rs`
- `crates/router/src/events/audit_events.rs`
## Motivation and Context
This PR fixes #4672
## How did you test it
H
</think>
To implement this, you'll need to modify:
**Detailed Implementation:**
**Commit 1:** feat(payments): Add audit events for PaymentCreate update (#6427)
Files to modify:
**crates/router/src/core/payments/operations/payment_create.rs**
Modify existing code
**crates/router/src/events/audit_events.rs**
Modify existing code
|
{"issue_number": 4672, "pr_number": 6427, "commits_count": 1, "files_changed": 2, "response_length": 1031, "file_count": 4, "needs_breakdown": false}
|
fix(payments_list): handle same payment/attempt IDs for different merchants
The query planner was applying the merchant_id filter before the join operation, which caused incorrect results when different merchants had the same payment_id or attempt_id. This prematurely filtered out valid rows from the payment_attempt table that had matching payment_id or attempt_id but a different merchant_id.
|
<think>
PR Context:
- Title: fix(payments_list): handle same payment/attempt ids for different merchants
- Merged: 2024-12-24T13:29:37Z
- Files changed: 1 files
- Commits: 4 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [x] Bugfix
- [ ] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
Changed the query to apply the merchant_id filter after the join. This ensures valid rows aren’t excluded too early and fixes an issue where **payments with the same IDs but different merchants** were being handled incorrectly.
### Additional Changes
- [ ] This PR modifies the A
</think>
To implement this, you'll need to modify:
**Detailed Implementation:**
**Commit 1:** fix(payments_list): handle same payment/attempt ids for different merchants (#6917)
Files to modify:
**crates/storage_impl/src/payments/payment_intent.rs**
Modify existing code
|
{"issue_number": 6916, "pr_number": 6917, "commits_count": 1, "files_changed": 1, "response_length": 988, "file_count": 4, "needs_breakdown": false}
|
One click docker setup
A script is needed to ensure one click docker setup, to minimise issues faced by users.
> Run the whole setup with simple command
> Show output with localhost links for different setups
|
<think>
PR Context:
- Title: docs: update the setup docs
- Merged: 2025-04-24T07:56:02Z
- Files changed: 2 files
- Commits: 5 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [ ] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [X] Documentation
- [ ] CI/CD
## Description
<!-- Describe your changes in detail -->
Updated the readme and local setup guide to add the new script
### Additional Changes
- [ ] This PR modifies the API contract
- [ ] This PR modifies the database schema
- [ ] This PR modifies application configuration/environment varia
</think>
To implement this, you'll need to modify:
(No detailed commit information available)
|
{"issue_number": 7761, "pr_number": 7839, "commits_count": 0, "files_changed": 2, "response_length": 757, "file_count": 0, "needs_breakdown": false}
|
[BUG] mandate details are not persisted for Adyen connector
### Bug Description
This is specific to Adyen's connector integration.
In case mandate details were not present in the response of payment sync with Adyen, these details are sent through webhooks. However, these details are not being persisted in DB leading to MIT failures.
### Expected Behavior
Mandate details sent in the webhook's request should be persisted in payment_methods table for future MITs
### Actual Behavior
Mandate details sent in the webhook's request are not persisted in `payment_methods` table.
### Steps To Reproduce
Provide an unambiguous set of steps to reproduce this bug. Include code or configuration to reproduce, if relevant.
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
### Context For The Bug
_No response_
### Environment
Are you using hyperswitch hosted version? Yes/No
If yes, please provide the value of the `x-request-id` response header to help us debug your issue.
If not (or if building/running locally), please provide the following details:
1. Operating System or Linux distribution:
2. Rust version (output of `rustc --version`): ``
3. App version (output of `cargo r --features vergen -- --version`): ``
### Have you spent some time checking if this bug has been raised before?
- [X] I checked and didn't find a similar issue
### Have you read the Contributing Guidelines?
- [X] I have read the [Contributing Guidelines](https://github.com/juspay/hyperswitch/blob/main/docs/CONTRIBUTING.md)
### Are you willing to submit a PR?
Yes, I am willing to submit a PR!
|
<think>
PR Context:
- Title: fix(connector): adyen - propagate connector mandate details in incoming webhooks
- Merged: 2024-12-02T18:30:38Z
- Files changed: 2 files
- Commits: 2 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [x] Bugfix
- [ ] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
Described in the linked #6719
### Additional Changes
- [ ] This PR modifies the API contract
- [ ] This PR modifies the database schema
- [ ] This PR modifies application configuration/environment variables
<!--
Provide links to the files with corresponding changes.
Fo
</think>
To implement this, you'll need to modify:
**Detailed Implementation:**
**Commit 1:** fix(connector): adyen - propagate connector mandate details in incoming webhooks (#6720)
Files to modify:
**crates/router/src/connector/adyen.rs**
Add:
- function: private::get_mandate_details
**crates/router/src/connector/adyen/transformers.rs**
Modify existing code
|
{"issue_number": 6719, "pr_number": 6720, "commits_count": 1, "files_changed": 2, "response_length": 1091, "file_count": 4, "needs_breakdown": false}
|
[FEATURE]: Add `Payment Method - Delete` endpoint to payment methods session for V2
Required for Payment Methods Service
|
<think>
PR Context:
- Title: feat(router): Add payment_methods_session_delete_payment_method endpoint [V2]
- Merged: 2025-03-27T12:05:05Z
- Files changed: 11 files
- Commits: 12 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [x] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
<!-- Describe your changes in detail -->
This endpoint allows deleting saved payment methods for a customer
### Additional Changes
- [x] This PR modifies the API contract
- [ ] This PR modifies the database schema
- [ ] This PR modifies application configuration/environment
</think>
To implement this, you'll need to modify:
**Detailed Implementation:**
**Commit 1:** feat(router): Add payment_methods_session_delete_payment_method endpoint [V2] (#7409)
Co-authored-by
Files to modify:
**crates/api_models/src/payment_methods.rs**
Add:
- struct: pub::PaymentMethodSessionDeleteSavedPaymentMethod
**crates/openapi/src/openapi_v2.rs**
Modify existing code
**crates/openapi/src/routes/payment_method.rs**
Add:
- function: pub::payment_method_session_delete_saved_payment_method
**crates/router/src/core/payment_methods.rs**
Add:
- function: pub::payment_methods_session_delete_payment_method
**crates/router/src/routes/app.rs**
Modify existing code
**crates/router/src/routes/lock_utils.rs**
Modify existing code
**crates/router/src/routes/payment_methods.rs**
Add:
- function: pub::payment_method_session_delete_saved_payment_method
**crates/router_env/src/logger/types.rs**
Modify existing code
|
{"issue_number": 7407, "pr_number": 7409, "commits_count": 1, "files_changed": 11, "response_length": 1678, "file_count": 10, "needs_breakdown": false}
|
feat(users): Send welcome to community email in magic link signup
Send [this](https://www.figma.com/design/lhmTvW2vuc2p5B4ZvsEOTw/Email-Tempalte-Design?node-id=0-1&t=OKWmXqVOsidKUk7y-1) email when user signs up with magic link.
|
<think>
PR Context:
- Title: feat(users): Send welcome to community email in magic link signup
- Merged: 2024-11-26T09:10:41Z
- Files changed: 4 files
- Commits: 4 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [ ] New feature
- [x] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
<!-- Describe your changes in detail -->
Magic link will send one more email along with magic link email if user is signing up.
### Additional Changes
- [ ] This PR modifies the API contract
- [ ] This PR modifies the database schema
- [ ] This PR modifies application configu
</think>
To implement this, you'll need to modify:
**Detailed Implementation:**
**Commit 1:** feat(users): Send welcome to community email in magic link signup (#6639)
Co-authored-by: hyperswitc
Files to modify:
**crates/router/src/consts/user.rs**
Modify existing code
**crates/router/src/core/user.rs**
Modify existing code
**crates/router/src/services/email/types.rs**
Add:
- function: private::get_email_data
- struct: private::WelcomeToCommunity
- impl: impl EmailData for WelcomeToCommunity
|
{"issue_number": 6638, "pr_number": 6639, "commits_count": 1, "files_changed": 4, "response_length": 1222, "file_count": 5, "needs_breakdown": false}
|
Add checks around Cypress mandates payments
Just verifying the payment method status isn't enough. We also need to verify the existence of connector mandate id. this can be done by updating the `mitusingpmid` command.
|
<think>
PR Context:
- Title: ci(cypress): verify mandate id to be `null` if payment id not `succeeded`
- Merged: 2025-04-16T10:47:24Z
- Files changed: 2 files
- Commits: 8 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [ ] New feature
- [x] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [x] CI/CD
## Description
<!-- Describe your changes in detail -->
This PR adds a check to verify if the `payment_status` is not any of `succeeded`, `partially_captured` or `requires_capture` and if so, then the `connector_mandate_id` should be `null`.
### Additional Changes
- [ ] This PR modifies the
</think>
To implement this, you'll need to modify:
(No detailed commit information available)
|
{"issue_number": 7748, "pr_number": 7749, "commits_count": 0, "files_changed": 2, "response_length": 803, "file_count": 0, "needs_breakdown": false}
|
[BUG] FEATURE_MATRIX shows JPMorgan does not support Refunds
I added support for refunds 3 weeks ago in #8436. Feature matrix needs to be updated.
|
<think>
PR Context:
- Title: fix(feature_matrix): refunds are supported by jpmorgan
- Merged: 2025-07-24T13:32:53Z
- Files changed: 1 files
- Commits: 1 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [x] Bugfix
- [ ] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
<!-- Describe your changes in detail -->
This PR marks refunds as supported by JPMorgan connector. Although this does not affect refund flow, the feature matrix marking is wrong.
### Additional Changes
- [ ] This PR modifies the API contract
- [ ] This PR modifies the datab
</think>
To implement this, you'll need to modify:
**Detailed Implementation:**
**Commit 1:** fix(feature_matrix): refunds are supported by jpmorgan (#8699)
Files to modify:
**crates/hyperswitch_connectors/src/connectors/jpmorgan.rs**
Modify existing code
|
{"issue_number": 8698, "pr_number": 8699, "commits_count": 1, "files_changed": 1, "response_length": 952, "file_count": 3, "needs_breakdown": false}
|
Gift Card Balance check API for split payments
We need to add an API to check balance for gift card.
This API will be called by the SDK and based on the gift card balance and transaction amount, we will collect either only gift card details or gift card details + another payment method
|
<think>
PR Context:
- Title: feat(router): Add gift card balance check endpoint (v2)
- Merged: 2025-09-17T07:50:47Z
- Files changed: 29 files
- Commits: 25 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [x] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
<!-- Describe your changes in detail -->
- Added `check-gift-card-balance` API
- Added `GiftCardBalanceCheck` flow for connectors and implemented it for Adyen
- Updated PML flow to store gift card enabled MCA in redis
<img width="2314" height="1286" alt="image" src="https://gith
</think>
To implement this, you'll need to modify:
**Detailed Implementation:**
**Commit 1:** feat(router): Add gift card balance check endpoint (v2) (#9102)
Files to modify:
**crates/api_models/src/events/payment.rs**
Add:
- function: private::get_api_event_type
- impl: impl ApiEventMetric for payments::GiftCardBalanceCheckResponse
**crates/api_models/src/payments.rs**
Add:
- struct: pub::GiftCardBalanceCheckResponse
- struct: pub::PaymentsGiftCardBalanceCheckRequest
**crates/common_utils/src/id_type/global_id/payment.rs**
Add:
- function: pub::get_gift_card_connector_key
**crates/hyperswitch_connectors/src/connectors/adyen.rs**
Add:
- function: private::get_headers
- function: private::get_url
- function: private::get_request_body
- function: private::build_request
- function: private::handle_response
- function: private::get_error_response
- function: private::get_5xx_error_response
- impl: impl api::PaymentsGiftCardBalanceCheck for Adyen
- impl: impl ConnectorIntegration<
GiftCardBalanceCheck,
GiftCardBalanceCheckRequestData,
GiftCardBalanceCheckResponseData,
> for Adyen
**crates/hyperswitch_connectors/src/connectors/adyen/transformers.rs**
Add:
- function: private::try_from
- function: private::try_from
- impl: impl TryFrom<&PaymentsGiftCardBalanceCheckRouterData> for AdyenBalanceRequest<'_>
- impl: impl TryFrom<
ResponseRouterData<
GiftCardBalanceCheck,
AdyenBalanceResponse,
GiftCardBalanceCheckRequestData,
GiftCardBalanceCheckResponseData,
>,
> for RouterData<
GiftCardBalanceCheck,
GiftCardBalanceCheckRequestData,
GiftCardBalanceCheckResponseData,
>
**crates/hyperswitch_connectors/src/default_implementations.rs**
Add:
- impl: impl PaymentsGiftCardBalanceCheck for connectors::DummyConnector<T>
- impl: impl ConnectorIntegration<
GiftCardBalanceCheck,
GiftCardBalanceCheckRequestData,
GiftCardBalanceCheckResponseData,
> for connectors::DummyConnector<T>
**crates/hyperswitch_connectors/src/default_implementations_v2.rs**
Add:
- impl: impl PaymentsGiftCardBalanceCheckV2 for $connector
- impl: impl ConnectorIntegrationV2<
GiftCardBalanceCheck,
GiftCardBalanceCheckFlowData,
GiftCardBalanceCheckRequestData,
GiftCardBalanceCheckResponseData,
> for $connector
**crates/hyperswitch_domain_models/src/router_data_v2/flow_common_types.rs**
Add:
- struct: pub::GiftCardBalanceCheckFlowData
**crates/hyperswitch_domain_models/src/router_flow_types/payments.rs**
Add:
- struct: pub::GiftCardBalanceCheck
**crates/hyperswitch_domain_models/src/router_request_types.rs**
Add:
- struct: pub::GiftCardBalanceCheckRequestData
**crates/hyperswitch_domain_models/src/router_response_types.rs**
Add:
- struct: pub::GiftCardBalanceCheckResponseData
**crates/hyperswitch_domain_models/src/types.rs**
Modify existing code
**crates/hyperswitch_interfaces/src/api/payments.rs**
Modify existing code
**crates/hyperswitch_interfaces/src/api/payments_v2.rs**
Add:
- trait: pub::PaymentsGiftCardBalanceCheckV2
**crates/hyperswitch_interfaces/src/conversion_impls.rs**
Add:
- function: private::from_old_router_data
- function: private::to_old_router_data
- impl: impl RouterDataConversion<T, Req, Resp> for GiftCardBalanceCheckFlowData
**crates/hyperswitch_interfaces/src/types.rs**
Modify existing code
**crates/openapi/src/openapi_v2.rs**
Modify existing code
**crates/openapi/src/routes/payments.rs**
Add:
- function: pub::payment_check_gift_card_balance
**crates/router/src/core.rs**
Add:
- mod: pub::gift_card
**crates/router/src/core/gift_card.rs**
Add:
- function: pub::payments_check_gift_card_balance_core
**crates/router/src/core/payments/payment_methods.rs**
Add:
- function: private::store_gift_card_mca_in_redis
**crates/router/src/routes/app.rs**
Modify existing code
**crates/router/src/routes/lock_utils.rs**
Modify existing code
**crates/router/src/routes/payments.rs**
Add:
- function: pub::payment_check_gift_card_balance
**crates/router/src/services/api.rs**
Modify existing code
**crates/router_env/src/logger/types.rs**
Modify existing code
|
{"issue_number": 9101, "pr_number": 9102, "commits_count": 1, "files_changed": 29, "response_length": 5096, "file_count": 28, "needs_breakdown": true}
|
[FEATURE] : [TRUSTPAY] Add Integrity Check Support for Authorize, PSync, Refund and RSync Flows
### Feature Description/Summary
Integrity check is a scenario where there is a discrepancy between the amount sent in the request and the amount received from the connector, which is checked during response handling.
### Context
Integrity checks in a payments flow are critical for ensuring data consistency, correctness, and security when dealing with amounts between Hyperswitch and connectors like Adyen, Stripe, Razorpay, etc.
### Starter Tasks
- In the `handle_response` function of Authorize/PSync/Refund/RSync, you will have to call the respective functions - `get_authorise_integrity_object` for Authorize, `get_sync_integrity_object` for Payments Sync, `get_refund_integrity_object` for Refund and RSync and `get_capture_integrity_object` for Capture.
- You would have to call these functions from `crates/hyperswitch_connectors/src/utils.rs`.
- These functions expect `amount_convertor`, `amount` and `currency`.
- You can take a look at this [PR](https://github.com/juspay/hyperswitch/pull/8075) for reference.
### Implementation Hints
- You can go to `crates/hyperswitch_connectors/src/connectors/trustpay.rs` and call the respective integrity check function as stated above in the `handle_response` function
### Acceptance Criteria
- [ ] Request and Response body added for each of the flows where integrity check is applied.
- [ ] All the required GitHub checks passing
- [ ] Formatted the code using `cargo +nightly fmt --all`
### How to Test it
- Hardcode the amount or currency field that is being passed to the connector different from the one you are passing in the request body
- This way you would be able to reproduce the integrity checks error message while testing.
### Mentor Contact
- Tag @bsayak03 [Sayak Bhattacharya] in the comments if you have any doubts/queries
### Resources
Here are a few sample PRs :
- https://github.com/juspay/hyperswitch/pull/8075
- https://github.com/juspay/hyperswitch/pull/8049
### Pre-Flight
#### Have you spent some time checking if this feature request has been raised before?
- [x] I checked and didn't find a similar issue
#### Have you read the Contributing Guidelines?
- [x] I have read the [Contributing Guidelines](https://github.com/juspay/hyperswitch/blob/main/docs/CONTRIBUTING.md)
### Submission Process:
- Ask the maintainers for assignment of the issue, you can request for assignment by commenting on the issue itself.
- Once assigned, submit a pull request (PR).
- Maintainers will review and provide feedback, if any.
- Maintainers can unassign issues due to inactivity, [read more here](https://github.com/juspay/hyperswitch/wiki/Hacktoberfest-Contribution-Rules).
Refer [here](https://github.com/juspay/hyperswitch/blob/main/docs/TERMS_OF_CONTEST.md) for Terms and conditions for the contest.
|
<think>
PR Context:
- Title: feat(connector): [TRUSTPAY] Add Integrity Check Support for Authorize, PSync, Refund and RSync Flows
- Merged: None
- Files changed: 1 files
- Commits: 1 commits
Implementation approach:
# PR: Add Integrity Check Support for Trustpay (Authorize, PSync, Refund, RSync)
## Type of Change
- [ ] Bugfix
- [x] New feature
- [x] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
Added integrity check support for Trustpay connector across the following flows:
- Authorize (automatic and manual)
- Payment Sync (PSync)
- Refund Execute
- Refund Sync (RSync)
The connector now constructs response integrity objects from am
</think>
To implement this, you'll need to modify:
(No detailed commit information available)
|
{"issue_number": 9228, "pr_number": 9301, "commits_count": 0, "files_changed": 1, "response_length": 814, "file_count": 0, "needs_breakdown": false}
|
Add support to call decision engine Dynamic Routing from hyperswitch after API key authentication
|
<think>
PR Context:
- Title: feat(routing): Add API key auth for decision engine endpoints
- Merged: 2025-07-21T13:38:52Z
- Files changed: 8 files
- Commits: 10 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [x] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
<!-- Describe your changes in detail -->
This PR adds API key auth to the decision engine endpoints for the decide gateway call and the update gateway score call.
### Additional Changes
- [x] This PR modifies the API contract
- [ ] This PR modifies the database schema
- [ ] T
</think>
To implement this, you'll need to modify:
**Detailed Implementation:**
**Commit 1:** feat(routing): Add API key auth for decision engine endpoints (#8640)
Co-authored-by: hyperswitch-bo
Files to modify:
**crates/api_models/src/events/routing.rs**
Add:
- function: private::get_api_event_type
- function: private::get_api_event_type
- function: private::get_api_event_type
- function: private::get_api_event_type
- impl: impl ApiEventMetric for crate::open_router::DecideGatewayResponse
- impl: impl ApiEventMetric for crate::open_router::OpenRouterDecideGatewayRequest
- impl: impl ApiEventMetric for crate::open_router::UpdateScorePayload
- impl: impl ApiEventMetric for crate::open_router::UpdateScoreResponse
**crates/api_models/src/open_router.rs**
Add:
- struct: pub::DecideGatewayResponse
- struct: pub::PriorityLogicOutput
- struct: pub::PriorityLogicData
**crates/router/src/core/payments/routing/utils.rs**
Modify existing code
**crates/router/src/core/routing.rs**
Add:
- function: pub::decide_gateway_open_router
- function: pub::update_gateway_score_open_router
**crates/router/src/routes/app.rs**
Modify existing code
**crates/router/src/routes/lock_utils.rs**
Modify existing code
**crates/router/src/routes/routing.rs**
Add:
- function: pub::call_decide_gateway_open_router
- function: pub::call_update_gateway_score_open_router
**crates/router_env/src/logger/types.rs**
Modify existing code
|
{"issue_number": 8613, "pr_number": 8640, "commits_count": 1, "files_changed": 8, "response_length": 2201, "file_count": 10, "needs_breakdown": false}
|
[CHORE] Bump Cypress to v14
bump cypress version to `v14` from `v13.17.0`. there's a ton of under the hood changes and improvements.
check: [docs.cypress.io/app/references/changelog](https://docs.cypress.io/app/references/changelog)
cypress v14 has significant impact on the way we do the redirection flow. check pr description for detailed information.
|
<think>
PR Context:
- Title: chore: bump cypress to `v14.0.0`
- Merged: 2025-02-03T13:52:14Z
- Files changed: 10 files
- Commits: 30 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [ ] New feature
- [ ] Enhancement
- [ ] Refactoring
- [x] Dependency updates
- [ ] Documentation
- [x] CI/CD
## Description
<!-- Describe your changes in detail -->
closes #7103
- video recording
- video recording gets around the race condition that resulted in parallel tests to fail when a payment failed at the same time
- connector specific recording
- store only failed payment recording
</think>
To implement this, you'll need to modify:
(No detailed commit information available)
|
{"issue_number": 7103, "pr_number": 7102, "commits_count": 0, "files_changed": 10, "response_length": 764, "file_count": 0, "needs_breakdown": false}
|
[FEATURE] feat(router): verify service for applepay merchant registration v2
### Feature Description
verify service for applepay merchant registration in v2
### Possible Implementation
Add POST /v2/verify/apple-pay/{merchant_id} endpoint for verify domains with Apple
### Have you spent some time checking if this feature request has been raised before?
- [x] I checked and didn't find a similar issue
### Have you read the Contributing Guidelines?
- [x] I have read the [Contributing Guidelines](https://github.com/juspay/hyperswitch/blob/main/docs/CONTRIBUTING.md)
### Are you willing to submit a PR?
Yes, I am willing to submit a PR!
|
<think>
PR Context:
- Title: feat(router): verify service for applepay merchant registration v2
- Merged: 2025-08-22T13:36:37Z
- Files changed: 5 files
- Commits: 1 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [X] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
<!-- Describe your changes in detail -->
Add Apple Pay merchant registration and verified domains retrieval for v2
### Additional Changes
- [X] This PR modifies the API contract
- [ ] This PR modifies the database schema
- [ ] This PR modifies application configuration/enviro
</think>
To implement this, you'll need to modify:
**Detailed Implementation:**
**Commit 1:** feat(router): verify service for applepay merchant registration v2 (#8999)
Files to modify:
**crates/router/src/core/verification.rs**
Modify existing code
**crates/router/src/core/verification/utils.rs**
Modify existing code
**crates/router/src/lib.rs**
Modify existing code
**crates/router/src/routes/app.rs**
Add:
- function: pub::server
- impl: impl Verify
**crates/router/src/routes/verification.rs**
Add:
- function: pub::apple_pay_merchant_registration
|
{"issue_number": 8998, "pr_number": 8999, "commits_count": 1, "files_changed": 5, "response_length": 1286, "file_count": 7, "needs_breakdown": false}
|
[BUG]: [TSYS] Payments Failing Across All Flows
### Feature Description/Summary
TSYS (Total System Services) is a global payment processing platform that provides payment gateway services for merchants, payment facilitators, and acquirers. It enables businesses to accept credit and debit card payments securely across multiple channels (e-commerce, in-store, mobile, etc.). The gateway facilitates authorization, capture, settlement, and reporting while ensuring compliance with industry security standards such as PCI DSS.
### Context
While attempting to process payments across all available flows using the TSYS gateway, we are consistently running into the following error response from their API in our current Hyperswitch integration:
```
SaleResponse(ErrorResponse(TsysErrorResponse { status: Fail, response_code: "F9901", response_message: "Invalid content was found starting with element 'orderNumber'. One of '{paymentFacilitatorIdentifier, paymentFacilitatorName, subMerchantIdentifier, subMerchantName, subMerchantCountryCode, subMerchantStateCode, subMerchantCity, subMerchantPostalCode, subMerchantEmailID, subMerchantPhone, isRecurring, isoIdentifier, registeredUserIndicator, laneID, authorizationIndicator, splitTenderPayment, splitTenderID, customerDetails, industryType, merchantCategoryCode, customFieldDetails, IVRMid, IVRVnumber, recipientDetails, acquirerInternalReferenceNumber, acceptorStreetAddress, serviceLocationCity, serviceLocationGeoCoordinates, skipDuplicateCheck}' is expected., " }))
```
### Starter Tasks
- Go ahead to the connector documentation and attempt to hit the connector's direct cURLs and make a happy case.
- Identify the current integration issue in Hyperswitch by comparing the connector's request body and make relevant changes in the Hyperswitch codebase.
### Implementation Hints
- You can go to `crates/hyperswitch_connectors/src/connectors/tsys.rs` and `crates/hyperswitch_connectors/src/connectors/tsys/transformers.rs` and make relevant changes according to what's gone in the current integration.
- Head to this documentation to get some clarity about the request and response schemas : [URL](https://www.google.com/url?q=https://developerportal.transit-pass.com/developerportal/resources/dist/%23/api-specs/.%252Fassets%252Fbuild%252Fapi%252FAPI3.0%252FCreditServices%252FAuth%252Findex.html%2523auth&sa=D&source=editors&ust=1757917256458963&usg=AOvVaw0Yt5vvn4-D6Z0T09ock1aK)
### Acceptance Criteria
- [ ] Request and Response body added for each of the flows where integrity check is applied.
- [ ] All the required GitHub checks passing
- [ ] Formatted the code using `cargo +nightly fmt --all`
### How to Test it
- Create a Merchant Account in local
- Create an API Key
- Add the connector - Tsys
- Test out the flows
### Mentor Contact
- Tag @bsayak03 [Sayak Bhattacharya] in the comments if you have any doubts/queries
### Resources
Here is the connector documentation link : [URL](https://www.google.com/url?q=https://developerportal.transit-pass.com/developerportal/resources/dist/%23/api-specs/.%252Fassets%252Fbuild%252Fapi%252FAPI3.0%252FCreditServices%252FAuth%252Findex.html%2523auth&sa=D&source=editors&ust=1757917256458963&usg=AOvVaw0Yt5vvn4-D6Z0T09ock1aK)
### Pre-Flight
#### Have you spent some time checking if this feature request has been raised before?
- [x] I checked and didn't find a similar issue
#### Have you read the Contributing Guidelines?
- [x] I have read the [Contributing Guidelines](https://github.com/juspay/hyperswitch/blob/main/docs/CONTRIBUTING.md)
### Submission Process:
- Ask the maintainers for assignment of the issue, you can request for assignment by commenting on the issue itself.
- Once assigned, submit a pull request (PR).
- Maintainers will review and provide feedback, if any.
- Maintainers can unassign issues due to inactivity, [read more here](https://github.com/juspay/hyperswitch/wiki/Hacktoberfest-Contribution-Rules).
Refer [here](https://github.com/juspay/hyperswitch/blob/main/docs/TERMS_OF_CONTEST.md) for Terms and conditions for the contest.
|
<think>
PR Context:
- Title: fix(connectors): [TSYS] change order of order_number in tsys auth request body
- Merged: 2025-10-08T15:39:41Z
- Files changed: 1 files
- Commits: 2 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [x] Bugfix
- [ ] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
This PR fixes the request body order of the TSYS contract for the auth request
### Additional Changes
- [ ] This PR modifies the API contract
- [ ] This PR modifies the database schema
- [ ] This PR modifies application configuration/environment variables
<!--
Provide li
</think>
To implement this, you'll need to modify:
**Detailed Implementation:**
**Commit 1:** fix(connectors): [TSYS] change order of order_number in tsys auth request body (#9579)
Files to modify:
**crates/hyperswitch_connectors/src/connectors/tsys/transformers.rs**
Modify existing code
|
{"issue_number": 9375, "pr_number": 9579, "commits_count": 1, "files_changed": 1, "response_length": 1009, "file_count": 3, "needs_breakdown": false}
|
[FEATURE] : [PAYTM] Add Integrity Check Support for Authorize, PSync, Refund and RSync Flows
### Feature Description/Summary
Integrity check is a scenario where there is a discrepancy between the amount sent in the request and the amount received from the connector, which is checked during response handling.
### Context
Integrity checks in a payments flow are critical for ensuring data consistency, correctness, and security when dealing with amounts between Hyperswitch and connectors like Adyen, Stripe, Razorpay, etc.
### Starter Tasks
- In the `handle_response` function of Authorize/PSync/Refund/RSync, you will have to call the respective functions - `get_authorise_integrity_object` for Authorize, `get_sync_integrity_object` for Payments Sync, `get_refund_integrity_object` for Refund and RSync and `get_capture_integrity_object` for Capture.
- You would have to call these functions from `crates/hyperswitch_connectors/src/utils.rs`.
- These functions expect `amount_convertor`, `amount` and `currency`.
- You can take a look at this [PR](https://github.com/juspay/hyperswitch/pull/8075) for reference.
### Implementation Hints
- You can go to `crates/hyperswitch_connectors/src/connectors/paytm.rs` and call the respective integrity check function as stated above in the `handle_response` function
### Acceptance Criteria
- [ ] Request and Response body added for each of the flows where integrity check is applied.
- [ ] All the required GitHub checks passing
- [ ] Formatted the code using `cargo +nightly fmt --all`
### How to Test it
- Hardcode the amount or currency field that is being passed to the connector different from the one you are passing in the request body
- This way you would be able to reproduce the integrity checks error message while testing.
### Mentor Contact
- Tag @bsayak03 [Sayak Bhattacharya] in the comments if you have any doubts/queries
### Resources
Here are a few sample PRs :
- https://github.com/juspay/hyperswitch/pull/8075
- https://github.com/juspay/hyperswitch/pull/8049
### Pre-Flight
#### Have you spent some time checking if this feature request has been raised before?
- [x] I checked and didn't find a similar issue
#### Have you read the Contributing Guidelines?
- [x] I have read the [Contributing Guidelines](https://github.com/juspay/hyperswitch/blob/main/docs/CONTRIBUTING.md)
### Submission Process:
- Ask the maintainers for assignment of the issue, you can request for assignment by commenting on the issue itself.
- Once assigned, submit a pull request (PR).
- Maintainers will review and provide feedback, if any.
- Maintainers can unassign issues due to inactivity, [read more here](https://github.com/juspay/hyperswitch/wiki/Hacktoberfest-Contribution-Rules).
Refer [here](https://github.com/juspay/hyperswitch/blob/main/docs/TERMS_OF_CONTEST.md) for Terms and conditions for the contest.
|
<think>
PR Context:
- Title: feat(connector): [PAYTM] Add Integrity Check Support for Authorize, PSync,Refund and RSync Flows
- Merged: None
- Files changed: 1 files
- Commits: 2 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [x] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
<!-- Describe your changes in detail -->
[FEATURE] : [PAYTM] Add Integrity Check Support for Authorize, PSync, Refund and RSync Flows #9211
Resolves Issue #9211
- Added integrity check functions to the paytm connector
### Additional Changes
- [ ] This PR modifies the API
</think>
To implement this, you'll need to modify:
(No detailed commit information available)
|
{"issue_number": 9211, "pr_number": 9246, "commits_count": 0, "files_changed": 1, "response_length": 810, "file_count": 0, "needs_breakdown": false}
|
docs(openapi): Show API version selection dropdown in API Reference
Add a version selection dropdown in API reference to allow exploring v2 APIs
|
<think>
PR Context:
- Title: docs(openapi): Show API version selection dropdown in Mintlify
- Merged: 2025-06-13T09:03:06Z
- Files changed: 30 files
- Commits: 7 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [ ] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [x] Documentation
- [ ] CI/CD
## Description
<!-- Describe your changes in detail -->
- Moved both `v1` and `v2` API docs under `api-reference` directory
- Renamed `openapi_spec.json` files for v1 and v2
- Updated OpenAPI spec file paths in `openapi` crate
- Modified OpenAPI spec path in CI pipeline
### Additional Changes
</think>
To implement this, you'll need to modify:
**Detailed Implementation:**
**Commit 1:** docs(openapi): Show API version selection dropdown in Mintlify (#8333)
Files to modify:
**crates/openapi/src/main.rs**
Modify existing code
|
{"issue_number": 8332, "pr_number": 8333, "commits_count": 1, "files_changed": 30, "response_length": 939, "file_count": 3, "needs_breakdown": false}
|
Adding events for Payment Reject
Created from #4525
This covers adding events for Payment Reject operation
This event should include the payment data similar to [PaymentCancel](https://github.com/juspay/hyperswitch/pull/4166)
It should also include any metadata for the event
e.g reason for payment rejection, error codes, rejection source etc
|
<think>
PR Context:
- Title: feat(events): Add payment reject audit events
- Merged: 2024-11-12T07:18:54Z
- Files changed: 2 files
- Commits: 3 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [ ] New feature
- [X] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
<!-- Describe your changes in detail -->
Pass along request_state to payment_core
Modify the UpdateTracker trait to accept request state
Modify the PaymentReject implementation of UpdateTracker to generate an event
### Additional Changes
- [ ] This PR modifies the API contr
</think>
To implement this, you'll need to modify:
**Detailed Implementation:**
**Commit 1:** feat(events): Add payment reject audit events (#6465)
Co-authored-by: Anish Kacham <f2010091@hyderab
Files to modify:
**crates/router/src/core/payments/operations/payment_reject.rs**
Modify existing code
**crates/router/src/events/audit_events.rs**
Modify existing code
|
{"issue_number": 4669, "pr_number": 6465, "commits_count": 1, "files_changed": 2, "response_length": 1054, "file_count": 4, "needs_breakdown": false}
|
[Cypress] Add more connectors to GitHub CI
- Bluesnap
- PayPal
- Iatapay
|
<think>
PR Context:
- Title: ci(cypress): fix nmi and paypal
- Merged: 2025-02-06T10:39:20Z
- Files changed: 5 files
- Commits: 30 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [ ] New feature
- [x] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [x] CI/CD
## Description
<!-- Describe your changes in detail -->
This PR fixes NTID for PayPal by disabling it from running.
closes #7172
### Additional Changes
- [ ] This PR modifies the API contract
- [ ] This PR modifies the database schema
- [ ] This PR modifies application configuration/e
</think>
To implement this, you'll need to modify:
(No detailed commit information available)
|
{"issue_number": 7172, "pr_number": 7173, "commits_count": 0, "files_changed": 5, "response_length": 762, "file_count": 0, "needs_breakdown": false}
|
Add audit events for PaymentStatus update
Created from #4525
This covers adding events for PaymentStatus operation
This event should include the payment data similar to [PaymentCancel](https://github.com/juspay/hyperswitch/pull/4166)
It should also include any metadata for the event
e.g reason for payment rejection, error codes, rejection source etc
### Submission Process:
- Ask the maintainers for assignment of the issue, you can request for assignment by commenting on the issue itself.
- Once assigned, submit a pull request (PR).
- Maintainers will review and provide feedback, if any.
- Maintainers can unassign issues due to inactivity, [read more here](https://github.com/juspay/hyperswitch/wiki/Hacktoberfest-Contribution-Rules).
Refer [here](https://github.com/juspay/hyperswitch/blob/main/docs/TERMS_OF_CONTEST.md) for Terms and conditions for the contest.
|
<think>
PR Context:
- Title: feat(payments): Add audit events for PaymentStatus update
- Merged: 2024-12-16T12:08:46Z
- Files changed: 2 files
- Commits: 8 commits
Implementation approach:
## Type of Change
- [ ] Bugfix
- [x] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
This PR adds an Audit event for the PaymentStatus operation.
### Additional Changes
- [x] This PR modifies the files below
- `crates/router/src/core/payments/operations/payment_status.rs`
- `crates/router/src/events/audit_events.rs`
## Motivation and Context
This PR fixes #4677
## How did you test it
-
</think>
To implement this, you'll need to modify:
**Detailed Implementation:**
**Commit 1:** feat(payments): Add audit events for PaymentStatus update (#6520)
Files to modify:
**crates/router/src/core/payments/operations/payment_status.rs**
Modify existing code
**crates/router/src/events/audit_events.rs**
Modify existing code
|
{"issue_number": 4677, "pr_number": 6520, "commits_count": 1, "files_changed": 2, "response_length": 1031, "file_count": 4, "needs_breakdown": false}
|
Connector changes for 3ds in v2
In v2, the `PreProcessing` and `CompleteAuthorize` flows will not be present.
We will introduce new flows `PreAuthenticate`, `Authenticate` and `PostAuthenticate` to better represent the domain.
|
<think>
PR Context:
- Title: feat(router): Add Connector changes for 3ds (v2)
- Merged: 2025-09-11T14:33:57Z
- Files changed: 8 files
- Commits: 1 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [ ] New feature
- [x] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
<!-- Describe your changes in detail -->
- Add `PreAuthenticate`, `Authenticate` and `PostAuthenticate` connector integration and implement them for cybersource
### Additional Changes
- [ ] This PR modifies the API contract
- [ ] This PR modifies the database schema
- [ ] T
</think>
To implement this, you'll need to modify:
**Detailed Implementation:**
**Commit 1:** feat(router): Add Connector changes for 3ds (v2) (#9117)
Files to modify:
**crates/hyperswitch_connectors/src/connectors/cybersource.rs**
Add:
- function: private::get_headers
- function: private::get_content_type
- function: private::get_url
- function: private::get_request_body
- function: private::build_request
- function: private::handle_response
- function: private::get_error_response
- function: private::get_headers
- function: private::get_content_type
- function: private::get_url
- function: private::get_request_body
- function: private::build_request
- function: private::handle_response
- function: private::get_error_response
- function: private::get_headers
- function: private::get_content_type
- function: private::get_url
- function: private::get_request_body
- function: private::build_request
- function: private::handle_response
- function: private::get_error_response
- function: private::get_headers
- function: private::get_content_type
- function: private::get_url
- function: private::get_request_body
- function: private::build_request
- function: private::handle_response
- function: private::get_error_response
- function: private::get_5xx_error_response
- impl: impl api::PaymentsPreAuthenticate for Cybersource
- impl: impl api::PaymentsPostAuthenticate for Cybersource
- impl: impl api::PaymentsAuthenticate for Cybersource
- impl: impl ConnectorIntegration<PreAuthenticate, PaymentsPreAuthenticateData, PaymentsResponseData> for Cybersource
- impl: impl ConnectorIntegration<Authenticate, PaymentsAuthenticateData, PaymentsResponseData> for Cybersource
- impl: impl ConnectorIntegration<PostAuthenticate, PaymentsPostAuthenticateData, PaymentsResponseData> for Cybersource
- impl: impl ConnectorIntegration<Authorize, PaymentsAuthorizeData, PaymentsResponseData> for Cybersource
**crates/hyperswitch_connectors/src/connectors/cybersource/transformers.rs**
Remove:
- struct: pub::CybersourceConsumerAuthValidateResponse
- struct: pub::CybersourceThreeDSMetadata
- struct: pub::CybersourceConsumerAuthInformationEnrollmentResponse
- struct: pub::ClientAuthCheckInfoResponse
- enum: pub::CybersourceAuthEnrollmentStatus
- enum: pub::CybersourcePreProcessingResponse
- impl: impl TryFrom<&CybersourceRouterData<&PaymentsCompleteAuthorizeRouterData>> for [serde(rename_all = "SCREAMING_SNAKE_CASE")]
Add:
- function: private::from
- function: private::try_from
- impl: impl From<&CybersourceRouterData<&PaymentsPreAuthenticateRouterData>> for ClientReferenceInformation
- impl: impl TryFrom<&CybersourceRouterData<&PaymentsPreAuthenticateRouterData>> for CybersourceAuthSetupRequest
- impl: impl TryFrom<&CybersourceRouterData<&PaymentsAuthenticateRouterData>> for (item.router_data.connector_request_reference_id.clone())
- impl: impl TryFrom<&CybersourceRouterData<&PaymentsPostAuthenticateRouterData>> for (item.router_data.connector_request_reference_id.clone())
**crates/hyperswitch_connectors/src/default_implementations.rs**
Modify existing code
**crates/hyperswitch_domain_models/src/router_request_types.rs**
Add:
- function: private::try_from
- function: private::try_from
- function: private::try_from
- struct: pub::PaymentsPreAuthenticateData
- struct: pub::PaymentsAuthenticateData
- struct: pub::PaymentsPostAuthenticateData
- impl: impl TryFrom<PaymentsAuthorizeData> for PaymentsPreAuthenticateData
- impl: impl TryFrom<PaymentsAuthorizeData> for PaymentsAuthenticateData
- impl: impl TryFrom<PaymentsAuthorizeData> for PaymentsPostAuthenticateData
**crates/hyperswitch_domain_models/src/types.rs**
Modify existing code
**crates/hyperswitch_interfaces/src/api/payments.rs**
Add:
- trait: pub::PaymentsPreAuthenticate
- trait: pub::PaymentsAuthenticate
- trait: pub::PaymentsPostAuthenticate
**crates/hyperswitch_interfaces/src/api/payments_v2.rs**
Add:
- trait: pub::PaymentsPreAuthenticateV2
- trait: pub::PaymentsAuthenticateV2
- trait: pub::PaymentsPostAuthenticateV2
**crates/hyperswitch_interfaces/src/types.rs**
Modify existing code
|
{"issue_number": 9116, "pr_number": 9117, "commits_count": 1, "files_changed": 8, "response_length": 5050, "file_count": 10, "needs_breakdown": true}
|
FIX[Config]: Add VGS baseurl to deployment toml files
Need to add baseurl for VGS in `config/deployments/{integration_test, production, sandbox}.toml`
|
<think>
PR Context:
- Title: fix(config): Add VGS baseurl to deployments toml files
- Merged: 2025-05-16T13:03:19Z
- Files changed: 3 files
- Commits: 1 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [ ] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [x] CI/CD
## Description
<!-- Describe your changes in detail -->
Added baseurl for `VGS` connector in relevant deployment TOML files
### Additional Changes
- [ ] This PR modifies the API contract
- [ ] This PR modifies the database schema
- [x] This PR modifies application configuration/environment
</think>
To implement this, you'll need to modify:
(No detailed commit information available)
|
{"issue_number": 8058, "pr_number": 8059, "commits_count": 0, "files_changed": 3, "response_length": 784, "file_count": 0, "needs_breakdown": false}
|
[FEATURE] Add payment type to Get Intent Response (v2)
### Feature Description
We need to return `payment_type` in `Get Intent`. Required by SDK
### Possible Implementation
Add a field `payment_type` to Get Intent Response
### Have you spent some time checking if this feature request has been raised before?
- [x] I checked and didn't find a similar issue
### Have you read the Contributing Guidelines?
- [x] I have read the [Contributing Guidelines](https://github.com/juspay/hyperswitch/blob/main/docs/CONTRIBUTING.md)
### Are you willing to submit a PR?
Yes, I am willing to submit a PR!
|
<think>
PR Context:
- Title: feat(router): Add payment_type to Get Intent response (v2)
- Merged: 2025-08-28T06:22:39Z
- Files changed: 3 files
- Commits: 3 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [ ] New feature
- [x] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
<!-- Describe your changes in detail -->
- Add `payment_type` to Payments Get Intent response
### Additional Changes
- [x] This PR modifies the API contract
- [ ] This PR modifies the database schema
- [ ] This PR modifies application configuration/environment variables
<!
</think>
To implement this, you'll need to modify:
**Detailed Implementation:**
**Commit 1:** feat(router): Add payment_type to Get Intent response (v2) (#9066)
Co-authored-by: Hrithikesh <61539
Files to modify:
**crates/api_models/src/payments.rs**
Modify existing code
**crates/router/src/core/payments/transformers.rs**
Modify existing code
|
{"issue_number": 9065, "pr_number": 9066, "commits_count": 1, "files_changed": 3, "response_length": 1047, "file_count": 4, "needs_breakdown": false}
|
Adding Contributors Guide to the Readme of the repository
Being an open source project, we look forward to contributors from across the world. For that we have outlined few changes which will make it easier for contributors to navigate through the project with more ease, and quickly develop a better understanding of the working of different components of Hyperswitch.
|
<think>
PR Context:
- Title: docs: upload new logos
- Merged: 2024-10-18T14:34:22Z
- Files changed: 5 files
- Commits: 9 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [ ] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [x] Documentation
- [ ] CI/CD
## Description
<!-- Describe your changes in detail -->
Closes - #5175
### Additional Changes
- [ ] This PR modifies the API contract
- [ ] This PR modifies the database schema
- [ ] This PR modifies application configuration/environment variables
<!--
Provide links to the files with c
</think>
To implement this, you'll need to modify:
(No detailed commit information available)
|
{"issue_number": 5175, "pr_number": 6368, "commits_count": 0, "files_changed": 5, "response_length": 752, "file_count": 0, "needs_breakdown": false}
|
ci: run cybersource along with stripe
ci: run cybersource along with stripe
|
<think>
PR Context:
- Title: ci: introduce `cybersource` cypress test to run in parallel
- Merged: 2024-11-14T11:52:04Z
- Files changed: 1 files
- Commits: 1 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [ ] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [x] CI/CD
## Description
<!-- Describe your changes in detail -->
Run Cybersource in parallel along with Stripe.
closes #6542
### Additional Changes
- [ ] This PR modifies the API contract
- [ ] This PR modifies the database schema
- [ ] This PR modifies application configuration/environment var
</think>
To implement this, you'll need to modify:
(No detailed commit information available)
|
{"issue_number": 6542, "pr_number": 6541, "commits_count": 0, "files_changed": 1, "response_length": 789, "file_count": 0, "needs_breakdown": false}
|
Removing mailhog container from the docker setup
Removing mailhog container from the docker setup
|
<think>
PR Context:
- Title: fix: fixes the docker setup to clean up the scarf data
- Merged: 2025-05-12T16:21:53Z
- Files changed: 6 files
- Commits: 12 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [ ] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [X] Documentation
- [ ] CI/CD
## Description
<!-- Describe your changes in detail -->
Corrected the docker setup, for demo app, control-center, and removed mailhog.
### Additional Changes
- [ ] This PR modifies the API contract
- [ ] This PR modifies the database schema
- [ ] This PR modifies application configuration/e
</think>
To implement this, you'll need to modify:
(No detailed commit information available)
|
{"issue_number": 7962, "pr_number": 7963, "commits_count": 0, "files_changed": 6, "response_length": 785, "file_count": 0, "needs_breakdown": false}
|
[FEATURE] integrate 3DS for Worldpay connector
### Feature Description
WorldPay offers 3DS capabilities for a card txn. Same needs to be integrated in HyperSwitch.
Flow - https://developer.worldpay.com/products/access/3ds/web
### Possible Implementation
Implementing 3DS for WorldPay requires one additional step of running DDC flows. Flow can be looked at in WorldPay's dev docs
1. Redirect to Worldpay's DDC
2. Redirect to Wordlpay's 3DS redirection form
3. Capture details in HyperSwitch's `/redirect/complete` flow
4. Perform a PSync (optional)
Reference
https://developer.worldpay.com/products/access/3ds/web
### Have you spent some time checking if this feature request has been raised before?
- [X] I checked and didn't find a similar issue
### Have you read the Contributing Guidelines?
- [X] I have read the [Contributing Guidelines](https://github.com/juspay/hyperswitch/blob/main/docs/CONTRIBUTING.md)
### Are you willing to submit a PR?
None
|
<think>
PR Context:
- Title: feat(connector): add 3DS flow for Worldpay
- Merged: 2024-10-21T14:14:20Z
- Files changed: 8 files
- Commits: 30 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [x] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
Described in #6177
### Additional Changes
- [ ] This PR modifies the API contract
- [ ] This PR modifies the database schema
- [ ] This PR modifies application configuration/environment variables
<!--
Provide links to the files with corresponding changes.
Following are
</think>
To implement this, you'll need to modify:
**Detailed Implementation:**
**Commit 1:** feat(connector): add 3DS flow for Worldpay (#6374)
Co-authored-by: hyperswitch-bot[bot] <148525504+h
Files to modify:
**crates/diesel_models/src/query/payment_attempt.rs**
Modify existing code
**crates/hyperswitch_domain_models/src/router_response_types.rs**
Modify existing code
**crates/router/src/connector/worldpay.rs**
Add:
- function: private::get_headers
- function: private::get_content_type
- function: private::get_url
- function: private::get_request_body
- function: private::build_request
- function: private::handle_response
- function: private::get_error_response
- function: private::get_flow_type
- impl: impl api::PaymentsCompleteAuthorize for Worldpay
- impl: impl ConnectorIntegration<
api::CompleteAuthorize,
types::CompleteAuthorizeData,
types::PaymentsResponseData,
> for Worldpay
- impl: impl services::ConnectorRedirectResponse for Worldpay
**crates/router/src/connector/worldpay/requests.rs**
Add:
- struct: pub::ThreeDSRequest
- struct: pub::ThreeDSRequestDeviceData
- struct: pub::ThreeDSRequestChallenge
- struct: pub::WorldpayCompleteAuthorizationRequest
- enum: pub::ThreeDSRequestChannel
**crates/router/src/connector/worldpay/response.rs**
Remove:
- function: pub::new
- impl: impl PaymentsResPaymentInstrument
Add:
- function: private::fmt
- struct: pub::ThreeDsChallengedResponse
- struct: pub::AuthenticationResponse
- struct: pub::ThreeDsChallenge
- struct: pub::CompleteThreeDsActionLink
**crates/router/src/connector/worldpay/transformers.rs**
Modify existing code
**crates/router/src/core/payments/flows.rs**
Modify existing code
**crates/router/src/services/api.rs**
Modify existing code
|
{"issue_number": 6177, "pr_number": 6374, "commits_count": 1, "files_changed": 8, "response_length": 2551, "file_count": 10, "needs_breakdown": false}
|
fix(users): Only use lowercase letters in emails
Currently uppercase letters in emails are being using at it is. Ideally we should convert them to lowercase before performing any DB operations with it.
|
<think>
PR Context:
- Title: feat(users): Convert emails to lowercase from requests
- Merged: 2024-11-20T13:41:03Z
- Files changed: 1 files
- Commits: 2 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [x] Bugfix
- [ ] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
<!-- Describe your changes in detail -->
This PR changes will convert emails from request to lowercase before performing any DB operations.
### Additional Changes
- [ ] This PR modifies the API contract
- [ ] This PR modifies the database schema
- [ ] This PR modifies applica
</think>
To implement this, you'll need to modify:
**Detailed Implementation:**
**Commit 1:** feat(users): Convert emails to lowercase from requests (#6601)
Files to modify:
**crates/router/src/types/domain/user.rs**
Modify existing code
|
{"issue_number": 6600, "pr_number": 6601, "commits_count": 1, "files_changed": 1, "response_length": 934, "file_count": 3, "needs_breakdown": false}
|
[BUG] Various errors in `rust_locker_open_api_spec.yml`
### Bug Description
The two identical files [`api-reference/rust_locker_open_api_spec.yml`](https://github.com/juspay/hyperswitch/blob/d06d19fc96e1a74d20e2fe3613f86d541947e0ae/api-reference/rust_locker_open_api_spec.yml) and [`api-reference-v2/rust_locker_open_api_spec.yml`](https://github.com/juspay/hyperswitch/blob/d06d19fc96e1a74d20e2fe3613f86d541947e0ae/api-reference-v2/rust_locker_open_api_spec.yml) contain some mistakes and errors.
### Expected Behavior
The documentation should be clear.
### Actual Behavior
The documentation contains some errors.
### Steps To Reproduce
Not relevant.
### Context For The Bug
Some examples:
https://github.com/juspay/hyperswitch/blob/d06d19fc96e1a74d20e2fe3613f86d541947e0ae/api-reference/rust_locker_open_api_spec.yml#L5
https://github.com/juspay/hyperswitch/blob/d06d19fc96e1a74d20e2fe3613f86d541947e0ae/api-reference/rust_locker_open_api_spec.yml#L12
https://github.com/juspay/hyperswitch/blob/d06d19fc96e1a74d20e2fe3613f86d541947e0ae/api-reference/rust_locker_open_api_spec.yml#L14
https://github.com/juspay/hyperswitch/blob/d06d19fc96e1a74d20e2fe3613f86d541947e0ae/api-reference/rust_locker_open_api_spec.yml#L42
### Environment
Not relevant.
### Have you spent some time checking if this bug has been raised before?
- [X] I checked and didn't find a similar issue
### Have you read the Contributing Guidelines?
- [X] I have read the [Contributing Guidelines](https://github.com/juspay/hyperswitch/blob/main/docs/CONTRIBUTING.md)
### Are you willing to submit a PR?
Yes, I am willing to submit a PR!
|
<think>
PR Context:
- Title: docs(openapi): improve `rust_locker_open_api_spec`
- Merged: 2024-10-24T13:31:41Z
- Files changed: 2 files
- Commits: 1 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [ ] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [x] Documentation
- [ ] CI/CD
## Description
<!-- Describe your changes in detail -->
Improved wording in the edit files.
### Additional Changes
- [ ] This PR modifies the API contract
- [ ] This PR modifies the database schema
- [ ] This PR modifies application configuration/environment variables
<!--
Provide lin
</think>
To implement this, you'll need to modify:
(No detailed commit information available)
|
{"issue_number": 6321, "pr_number": 6322, "commits_count": 0, "files_changed": 2, "response_length": 780, "file_count": 0, "needs_breakdown": false}
|
[REFCTOR]: Move CustomerAcceptance type to `common_types`
`CustomerAcceptance` is currently defined separately in `api_models` and `hyperswitch_domain_models`. These types are exactly the same, so they can be moved to `common_types`.
Additionally, in V2, we can use this strict type in `diesel_models` as well, instead of having a `SecretSerdeValue`
|
<think>
PR Context:
- Title: refactor: Move CustomerAcceptance to common_types
- Merged: 2025-06-25T06:30:07Z
- Files changed: 30 files
- Commits: 11 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [ ] New feature
- [ ] Enhancement
- [x] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
<!-- Describe your changes in detail -->
- Moved `CustomerAcceptance`, `AcceptanceType`, `OnlineMandate` to `common_types`
- Removed unnecessary conversions from the code
- Changed `payment_attempt` domain model and diesel model in v2 to use strict type
### Additional Changes
</think>
To implement this, you'll need to modify:
**Detailed Implementation:**
**Commit 1:** refactor: Move CustomerAcceptance to common_types (#8299)
Co-authored-by: hyperswitch-bot[bot] <1485
Files to modify:
**crates/api_models/src/mandates.rs**
Modify existing code
**crates/api_models/src/payments.rs**
Remove:
- struct: pub::CustomerAcceptance
- struct: pub::OnlineMandate
- enum: pub::AcceptanceType
**crates/common_types/src/payments.rs**
Add:
- function: pub::get_ip_address
- function: pub::get_user_agent
- function: pub::get_accepted_at
- struct: pub::CustomerAcceptance
- struct: pub::OnlineMandate
- enum: pub::AcceptanceType
- impl: impl CustomerAcceptance
- impl: impl masking::SerializableSecret for CustomerAcceptance
**crates/diesel_models/src/payment_attempt.rs**
Modify existing code
**crates/hyperswitch_connectors/src/connectors/stripe/transformers.rs**
Modify existing code
**crates/hyperswitch_domain_models/src/mandates.rs**
Remove:
- function: private::from
- function: private::from
- function: private::from
- function: private::from
- function: private::from
- function: private::from
- function: pub::get_ip_address
- function: pub::get_user_agent
- function: pub::get_accepted_at
- struct: pub::CustomerAcceptance
- struct: pub::OnlineMandate
- enum: pub::AcceptanceType
- impl: impl From<ApiCustomerAcceptance> for CustomerAcceptance
- impl: impl From<CustomerAcceptance> for ApiCustomerAcceptance
- impl: impl From<ApiAcceptanceType> for AcceptanceType
- impl: impl From<AcceptanceType> for ApiAcceptanceType
- impl: impl From<ApiOnlineMandate> for OnlineMandate
- impl: impl From<OnlineMandate> for ApiOnlineMandate
- impl: impl CustomerAcceptance
**crates/hyperswitch_domain_models/src/payments/payment_attempt.rs**
Modify existing code
**crates/hyperswitch_domain_models/src/router_request_types.rs**
Modify existing code
**crates/openapi/src/openapi.rs**
Modify existing code
**crates/openapi/src/openapi_v2.rs**
Modify existing code
**crates/router/src/compatibility/stripe/payment_intents/types.rs**
Modify existing code
**crates/router/src/core/mandate.rs**
Modify existing code
**crates/router/src/core/mandate/helpers.rs**
Modify existing code
**crates/router/src/core/payments.rs**
Modify existing code
**crates/router/src/core/payments/flows.rs**
Modify existing code
**crates/router/src/core/payments/flows/authorize_flow.rs**
Modify existing code
**crates/router/src/core/payments/flows/setup_mandate_flow.rs**
Modify existing code
**crates/router/src/core/payments/operations/payment_complete_authorize.rs**
Modify existing code
**crates/router/src/core/payments/operations/payment_confirm.rs**
Modify existing code
**crates/router/src/core/payments/operations/payment_create.rs**
Modify existing code
**crates/router/src/core/payments/operations/payment_update.rs**
Modify existing code
**crates/router/src/core/payments/routing.rs**
Modify existing code
**crates/router/src/core/payments/routing/transformers.rs**
Modify existing code
**crates/router/src/core/payments/session_operation.rs**
Modify existing code
**crates/router/src/core/payments/tokenization.rs**
Modify existing code
**crates/router/src/core/payments/transformers.rs**
Modify existing code
**crates/router/src/core/payments/vault_session.rs**
Modify existing code
**crates/router/src/services/kafka/payment_attempt.rs**
Modify existing code
**crates/router/src/services/kafka/payment_attempt_event.rs**
Modify existing code
**crates/router/src/types/api/payments.rs**
Modify existing code
**crates/router/src/types/transformers.rs**
Modify existing code
|
{"issue_number": 8298, "pr_number": 8299, "commits_count": 1, "files_changed": 30, "response_length": 4477, "file_count": 33, "needs_breakdown": true}
|
[BUG]: Decryption failure in chat prevents retrieval of conversation history
Internal users are unable to view their past chat conversations through the chat/ai/list endpoint, which is meant to be used for internal users. When attempting to retrieve the chat history, the system fails to decrypt the stored messages, resulting in error.
|
<think>
PR Context:
- Title: fix(chat): alter encryption logic for ai service
- Merged: 2025-10-01T13:05:25Z
- Files changed: 1 files
- Commits: 2 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [x] Bugfix
- [ ] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
This PR addresses an issue where chat conversation history could not be decrypted in the `chat/ai/list` endpoint. The root cause was an inconsistency between the encryption method used when storing chat interactions (`chat/ai/data`) and the decryption method used when retrieving them
</think>
To implement this, you'll need to modify:
**Detailed Implementation:**
**Commit 1:** fix(chat): alter encryption logic for ai service (#9562)
Files to modify:
**crates/router/src/utils/chat.rs**
Modify existing code
|
{"issue_number": 9561, "pr_number": 9562, "commits_count": 1, "files_changed": 1, "response_length": 915, "file_count": 3, "needs_breakdown": false}
|
feat(authz): Make permissions entity and scope aware
Currently the permissions we use doesn't have any entity level context. But some of our APIs need that context.
For example,
1. `payment/list` - This can only be accessible by merchant level users or higher. Profile level users should not be able to access it.
2. `payment/profile/list` - This can be accessible by all level of users.
With current setup, this is not directly possible by the permissions. We had to introduce `min_entity_level` to solve this, but this is very separated from the permissions.
To solve this, we need to have entity level context at permissions level itself.
### Scope for permissions
The write permissions currently doesn't have access to read APIs, but since write is a superset of read, they should be able to access read APIs as well.
So, this PR also introduces scope context in permissions.
|
<think>
PR Context:
- Title: feat(authz): Create a permission generator
- Merged: 2024-10-24T14:36:07Z
- Files changed: 30 files
- Commits: 11 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [ ] New feature
- [x] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
<!-- Describe your changes in detail -->
### Entity level context in Permissions
Currently the permissions we use doesn't have any entity level context. But some of our APIs need that context.
For example,
1. `payment/list` - This can only be accessible by merchant level users o
</think>
To implement this, you'll need to modify:
**Detailed Implementation:**
**Commit 1:** feat(authz): Create a permission generator (#6394)
Co-authored-by: hyperswitch-bot[bot] <148525504+h
Files to modify:
**crates/api_models/src/user_role.rs**
Remove:
- enum: pub::ParentGroup
**crates/common_enums/src/enums.rs**
Add:
- enum: pub::ParentGroup
- enum: pub::Resource
- enum: pub::PermissionScope
**crates/router/src/analytics.rs**
Modify existing code
**crates/router/src/core/user_role.rs**
Modify existing code
**crates/router/src/routes/admin.rs**
Modify existing code
**crates/router/src/routes/api_keys.rs**
Modify existing code
**crates/router/src/routes/blocklist.rs**
Modify existing code
**crates/router/src/routes/connector_onboarding.rs**
Modify existing code
**crates/router/src/routes/customers.rs**
Modify existing code
**crates/router/src/routes/disputes.rs**
Modify existing code
**crates/router/src/routes/mandates.rs**
Modify existing code
**crates/router/src/routes/payment_methods.rs**
Modify existing code
**crates/router/src/routes/payments.rs**
Modify existing code
**crates/router/src/routes/payouts.rs**
Modify existing code
**crates/router/src/routes/profiles.rs**
Modify existing code
**crates/router/src/routes/recon.rs**
Modify existing code
**crates/router/src/routes/refunds.rs**
Modify existing code
**crates/router/src/routes/routing.rs**
Modify existing code
**crates/router/src/routes/user.rs**
Modify existing code
**crates/router/src/routes/user_role.rs**
Modify existing code
**crates/router/src/routes/verification.rs**
Modify existing code
**crates/router/src/routes/verify_connector.rs**
Modify existing code
**crates/router/src/routes/webhook_events.rs**
Modify existing code
**crates/router/src/services/authentication.rs**
Modify existing code
**crates/router/src/services/authorization.rs**
Remove:
- function: pub::check_entity
**crates/router/src/services/authorization/info.rs**
Modify existing code
**crates/router/src/services/authorization/permission_groups.rs**
Add:
- function: private::scope
- function: private::parent
- function: private::resources
- function: private::accessible_groups
- function: private::resources
- trait: pub::PermissionGroupExt
- trait: pub::ParentGroupExt
- impl: impl PermissionGroupExt for PermissionGroup
- impl: impl ParentGroupExt for ParentGroup
**crates/router/src/services/authorization/permissions.rs**
Remove:
- enum: pub::Permission
**crates/router/src/services/authorization/roles.rs**
Modify existing code
**crates/router_derive/src/lib.rs**
Add:
- function: pub::generate_permissions
**crates/router_derive/src/macros.rs**
Add:
- mod: pub::generate_permissions
**crates/router_derive/src/macros/generate_permissions.rs**
Add:
- function: private::parse
- function: private::parse
- function: private::parse_label_with_punctuated_data
- function: pub::generate_permissions_inner
- struct: private::ResourceInput
- struct: private::Input
- impl: impl Parse for Input
- impl: impl Parse for ResourceInput
|
{"issue_number": 6391, "pr_number": 6394, "commits_count": 1, "files_changed": 30, "response_length": 3882, "file_count": 34, "needs_breakdown": true}
|
feat(connector): add template code for recurly
add a template code for recurly connector
|
<think>
PR Context:
- Title: feat(connector): add template code for recurly
- Merged: 2025-03-05T10:40:40Z
- Files changed: 24 files
- Commits: 13 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [ ] New feature
- [x] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
<!-- Describe your changes in detail -->
connector integration template code for recurly.
Issue: This PR closes the issue #7283
### Additional Changes
- [ ] This PR modifies the API contract
- [ ] This PR modifies the database schema
- [ ] This PR modifies application conf
</think>
To implement this, you'll need to modify:
**Detailed Implementation:**
**Commit 1:** feat(connector): add template code for recurly (#7284)
Co-authored-by: Aniket Burman <aniket.burman@
Files to modify:
**crates/common_enums/src/connector_enums.rs**
Modify existing code
**crates/hyperswitch_connectors/src/connectors.rs**
Add:
- mod: pub::recurly
**crates/hyperswitch_connectors/src/connectors/recurly.rs**
Add:
- function: pub::new
- function: private::build_headers
- function: private::id
- function: private::get_currency_unit
- function: private::common_get_content_type
- function: private::base_url
- function: private::get_auth_header
- function: private::build_error_response
- function: private::get_headers
- function: private::get_content_type
- function: private::get_url
- function: private::get_request_body
- function: private::build_request
- function: private::handle_response
- function: private::get_error_response
- function: private::get_headers
- function: private::get_content_type
- function: private::get_url
- function: private::build_request
- function: private::handle_response
- function: private::get_error_response
- function: private::get_headers
- function: private::get_content_type
- function: private::get_url
- function: private::get_request_body
- function: private::build_request
- function: private::handle_response
- function: private::get_error_response
- function: private::get_headers
- function: private::get_content_type
- function: private::get_url
- function: private::get_request_body
- function: private::build_request
- function: private::handle_response
- function: private::get_error_response
- function: private::get_headers
- function: private::get_content_type
- function: private::get_url
- function: private::build_request
- function: private::handle_response
- function: private::get_error_response
- function: private::get_webhook_object_reference_id
- function: private::get_webhook_event_type
- function: private::get_webhook_resource_object
- struct: pub::Recurly
- impl: impl Recurly
- impl: impl api::Payment for Recurly
- impl: impl api::PaymentSession for Recurly
- impl: impl api::ConnectorAccessToken for Recurly
- impl: impl api::MandateSetup for Recurly
- impl: impl api::PaymentAuthorize for Recurly
- impl: impl api::PaymentSync for Recurly
- impl: impl api::PaymentCapture for Recurly
- impl: impl api::PaymentVoid for Recurly
- impl: impl api::Refund for Recurly
- impl: impl api::RefundExecute for Recurly
- impl: impl api::RefundSync for Recurly
- impl: impl api::PaymentToken for Recurly
- impl: impl ConnectorIntegration<PaymentMethodToken, PaymentMethodTokenizationData, PaymentsResponseData> for Recurly
- impl: impl ConnectorCommonExt<Flow, Request, Response> for Recurly
- impl: impl ConnectorCommon for Recurly
- impl: impl ConnectorValidation for Recurly
- impl: impl ConnectorIntegration<Session, PaymentsSessionData, PaymentsResponseData> for Recurly
- impl: impl ConnectorIntegration<AccessTokenAuth, AccessTokenRequestData, AccessToken> for Recurly
- impl: impl ConnectorIntegration<SetupMandate, SetupMandateRequestData, PaymentsResponseData> for Recurly
- impl: impl ConnectorIntegration<Authorize, PaymentsAuthorizeData, PaymentsResponseData> for Recurly
- impl: impl ConnectorIntegration<PSync, PaymentsSyncData, PaymentsResponseData> for Recurly
- impl: impl ConnectorIntegration<Capture, PaymentsCaptureData, PaymentsResponseData> for Recurly
- impl: impl ConnectorIntegration<Void, PaymentsCancelData, PaymentsResponseData> for Recurly
- impl: impl ConnectorIntegration<Execute, RefundsData, RefundsResponseData> for Recurly
- impl: impl ConnectorIntegration<RSync, RefundsData, RefundsResponseData> for Recurly
- impl: impl webhooks::IncomingWebhook for Recurly
- impl: impl ConnectorSpecifications for Recurly
- mod: pub::transformers
**crates/hyperswitch_connectors/src/connectors/recurly/transformers.rs**
Add:
- function: private::from
- function: private::try_from
- function: private::try_from
- function: private::from
- function: private::try_from
- function: private::try_from
- function: private::from
- function: private::try_from
- function: private::try_from
- struct: pub::RecurlyRouterData
- struct: pub::RecurlyPaymentsRequest
- struct: pub::RecurlyCard
- struct: pub::RecurlyAuthType
- struct: pub::RecurlyPaymentsResponse
- struct: pub::RecurlyRefundRequest
- struct: pub::RefundResponse
- struct: pub::RecurlyErrorResponse
- enum: pub::RecurlyPaymentStatus
- enum: pub::RefundStatus
- impl: impl From<(StringMinorUnit, T)> for RecurlyRouterData<T>
- impl: impl TryFrom<&RecurlyRouterData<&PaymentsAuthorizeRouterData>> for RecurlyPaymentsRequest
- impl: impl TryFrom<&ConnectorAuthType> for RecurlyAuthType
- impl: impl From<RecurlyPaymentStatus> for common_enums::AttemptStatus
- impl: impl TryFrom<ResponseRouterData<F, RecurlyPaymentsResponse, T, PaymentsResponseData>> for RouterData<F, T, PaymentsResponseData>
- impl: impl TryFrom<&RecurlyRouterData<&RefundsRouterData<F>>> for RecurlyRefundRequest
- impl: impl From<RefundStatus> for enums::RefundStatus
- impl: impl TryFrom<RefundsResponseRouterData<Execute, RefundResponse>> for RefundsRouterData<Execute>
- impl: impl TryFrom<RefundsResponseRouterData<RSync, RefundResponse>> for RefundsRouterData<RSync>
**crates/hyperswitch_connectors/src/default_implementations.rs**
Modify existing code
**crates/hyperswitch_connectors/src/default_implementations_v2.rs**
Modify existing code
**crates/hyperswitch_interfaces/src/configs.rs**
Modify existing code
**crates/router/src/connector.rs**
Modify existing code
**crates/router/src/core/payments/connector_integration_v2_impls.rs**
Modify existing code
**crates/router/src/core/payments/flows.rs**
Modify existing code
**crates/router/src/types/api.rs**
Modify existing code
**crates/router/src/types/transformers.rs**
Modify existing code
**crates/router/tests/connectors/main.rs**
Add:
- mod: private::recurly
**crates/router/tests/connectors/recurly.rs**
Add:
- function: private::get_data
- function: private::get_auth_token
- function: private::get_name
- function: private::get_default_payment_info
- function: private::payment_method_details
- function: private::should_only_authorize_payment
- function: private::should_capture_authorized_payment
- function: private::should_partially_capture_authorized_payment
- function: private::should_sync_authorized_payment
- function: private::should_void_authorized_payment
- function: private::should_refund_manually_captured_payment
- function: private::should_partially_refund_manually_captured_payment
- function: private::should_sync_manually_captured_refund
- function: private::should_make_payment
- function: private::should_sync_auto_captured_payment
- function: private::should_refund_auto_captured_payment
- function: private::should_partially_refund_succeeded_payment
- function: private::should_refund_succeeded_payment_multiple_times
- function: private::should_sync_refund
- function: private::should_fail_payment_for_incorrect_cvc
- function: private::should_fail_payment_for_invalid_exp_month
- function: private::should_fail_payment_for_incorrect_expiry_year
- function: private::should_fail_void_payment_for_auto_capture
- function: private::should_fail_capture_for_invalid_payment
- function: private::should_fail_for_refund_amount_higher_than_payment_amount
- struct: private::RecurlyTest
- impl: impl ConnectorActions for RecurlyTest
- impl: impl utils::Connector for RecurlyTest
**crates/test_utils/src/connector_auth.rs**
Modify existing code
|
{"issue_number": 7283, "pr_number": 7284, "commits_count": 1, "files_changed": 24, "response_length": 8808, "file_count": 17, "needs_breakdown": true}
|
refactor(permissions): Give access to connector view group in operation groups
Currently `connector_label` is not visible in payments page of control-center. This is because, the payment retrieve API doesn't send the `connector_label`. As it is a big change in the payments flow, we are providing access to connector list API, so that control-center can fetch the data from there.
|
<think>
PR Context:
- Title: refactor(authz): Make connector list accessible by operation groups
- Merged: 2024-12-16T09:22:57Z
- Files changed: 2 files
- Commits: 3 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [ ] New feature
- [ ] Enhancement
- [x] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
<!-- Describe your changes in detail -->
This PR will make connector_view group accessible by operation groups.
This PR will also change the permission of connector_retrieve API from connector_read to connector_write as it contains sensitive data.
### Additional Changes
</think>
To implement this, you'll need to modify:
**Detailed Implementation:**
**Commit 1:** refactor(authz): Make connector list accessible by operation groups (#6792)
Files to modify:
**crates/router/src/routes/admin.rs**
Modify existing code
**crates/router/src/services/authorization/permission_groups.rs**
Modify existing code
|
{"issue_number": 6788, "pr_number": 6792, "commits_count": 1, "files_changed": 2, "response_length": 1045, "file_count": 4, "needs_breakdown": false}
|
[FEATURE] [DEUTSCHEBANK] Integrate SEPA Payments
### Feature Description
Integrate SEPA Payments for connector Deutsche Bank
### Possible Implementation
https://testmerch.directpos.de/rest-api/apidoc/v2.1/index.html#chap_sdd
### Have you spent some time checking if this feature request has been raised before?
- [X] I checked and didn't find a similar issue
### Have you read the Contributing Guidelines?
- [X] I have read the [Contributing Guidelines](https://github.com/juspay/hyperswitch/blob/main/docs/CONTRIBUTING.md)
### Are you willing to submit a PR?
Yes, I am willing to submit a PR!
|
<think>
PR Context:
- Title: feat(payments): propagate additional payment method data for google pay during MIT
- Merged: 2024-11-26T14:14:16Z
- Files changed: 5 files
- Commits: 3 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [x] New feature
- [x] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
Described in #5858 # 2 point
### Additional Changes
- [ ] This PR modifies the API contract
- [ ] This PR modifies the database schema
- [ ] This PR modifies application configuration/environment variables
<!--
Provide links to the files with corresponding changes.
Fo
</think>
To implement this, you'll need to modify:
**Detailed Implementation:**
**Commit 1:** feat(payments): propagate additional payment method data for google pay during MIT (#6644)
Co-author
Files to modify:
**crates/api_models/src/payment_methods.rs**
Add:
- function: private::from
- function: private::from
- struct: pub::PaymentMethodDataWalletInfo
- impl: impl From<payments::additional_info::WalletAdditionalDataForCard> for PaymentMethodDataWalletInfo
- impl: impl From<PaymentMethodDataWalletInfo> for payments::additional_info::WalletAdditionalDataForCard
**crates/hyperswitch_domain_models/src/payment_method_data.rs**
Add:
- function: private::from
- impl: impl From<GooglePayWalletData> for payment_methods::PaymentMethodDataWalletInfo
**crates/router/src/core/payment_methods/cards.rs**
Modify existing code
**crates/router/src/core/payments/operations/payment_create.rs**
Modify existing code
**crates/router/src/core/payments/tokenization.rs**
Modify existing code
|
{"issue_number": 5858, "pr_number": 6644, "commits_count": 1, "files_changed": 5, "response_length": 1748, "file_count": 7, "needs_breakdown": false}
|
[FEATURE] align the JSON deserialization errors into expected ErrorResponse format
### Feature Description
HyperSwitch uses an error format for responding back with the errors in the API. This error structure is uniform across different stages of the flow. For any deserialization errors in the API, error response with a different structure is returned.
Expected
```
{
"error": {
"error_type": "invalid_request",
"message": "Json deserialize error: unknown variant `automatiac`, expected one of `automatic`, `manual`, `manual_multiple`, `scheduled` at line 5 column 34",
"code": "IR_06"
}
}
```
Actual
```
{
"error": "Json deserialize error: unknown variant `automatiac`, expected one of `automatic`, `manual`, `manual_multiple`, `scheduled` at line 5 column 34"
}
```
### Possible Implementation
Update the `Display` implementation of `CustomJsonError`
### Have you spent some time checking if this feature request has been raised before?
- [X] I checked and didn't find a similar issue
### Have you read the Contributing Guidelines?
- [X] I have read the [Contributing Guidelines](https://github.com/juspay/hyperswitch/blob/main/docs/CONTRIBUTING.md)
### Are you willing to submit a PR?
Yes, I am willing to submit a PR!
|
<think>
PR Context:
- Title: refactor: update API response for JSON deserialization errors
- Merged: 2024-11-21T22:26:21Z
- Files changed: 6 files
- Commits: 7 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [ ] New feature
- [ ] Enhancement
- [x] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
Described in #6609
### Additional Changes
- [x] This PR modifies the API contract
- [ ] This PR modifies the database schema
- [ ] This PR modifies application configuration/environment variables
<!--
Provide links to the files with corresponding changes.
Following are
</think>
To implement this, you'll need to modify:
**Detailed Implementation:**
**Commit 1:** refactor: update API response for JSON deserialization errors (#6610)
Files to modify:
**crates/router/src/utils.rs**
Modify existing code
|
{"issue_number": 6609, "pr_number": 6610, "commits_count": 1, "files_changed": 6, "response_length": 936, "file_count": 3, "needs_breakdown": false}
|
feat(users): support tenant level users
- Add api to create tenant_admin
- Create org by tenant level user
- Support tenant entity: tenant level roles/permission
|
<think>
PR Context:
- Title: feat(users): add support for tenant level users
- Merged: 2024-12-06T13:19:57Z
- Files changed: 22 files
- Commits: 15 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [x] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
- Add api to create tenant users
- Add api to create orgs
- Support tenant level entity for the user hierarchy
A tenant level user should see dashboard as seen by the org admin. He will be pinned to one org, merchant and profile. And he can switch between any org in the given ten
</think>
To implement this, you'll need to modify:
**Detailed Implementation:**
**Commit 1:** feat(users): add support for tenant level users (#6708)
Co-authored-by: hyperswitch-bot[bot] <148525
Files to modify:
**crates/api_models/src/events/user.rs**
Modify existing code
**crates/api_models/src/user.rs**
Add:
- struct: pub::CreateTenantUserRequest
- struct: pub::UserOrgMerchantCreateRequest
**crates/common_enums/src/enums.rs**
Modify existing code
**crates/common_utils/src/consts.rs**
Modify existing code
**crates/diesel_models/src/query/merchant_account.rs**
Add:
- function: pub::list_all_merchant_accounts
**crates/router/src/analytics.rs**
Modify existing code
**crates/router/src/consts/user.rs**
Modify existing code
**crates/router/src/core/user.rs**
Add:
- function: pub::create_tenant_user
- function: pub::create_org_merchant_for_user
**crates/router/src/core/user_role.rs**
Modify existing code
**crates/router/src/core/user_role/role.rs**
Modify existing code
**crates/router/src/db/kafka_store.rs**
Add:
- function: private::list_merchant_and_org_ids
**crates/router/src/db/merchant_account.rs**
Add:
- function: private::list_merchant_and_org_ids
- function: private::list_merchant_and_org_ids
**crates/router/src/routes/app.rs**
Modify existing code
**crates/router/src/routes/lock_utils.rs**
Modify existing code
**crates/router/src/routes/user.rs**
Add:
- function: pub::create_tenant_user
- function: pub::user_org_create
**crates/router/src/services/authorization/permissions.rs**
Modify existing code
**crates/router/src/services/authorization/roles/predefined_roles.rs**
Modify existing code
**crates/router/src/types/domain/user.rs**
Add:
- function: private::from
- function: private::foreign_from
- function: private::from
- function: private::try_from
- function: private::from
- struct: pub::MerchantAccountIdentifier
- struct: pub::TenantLevel
- impl: impl From<(user_api::CreateTenantUserRequest, MerchantAccountIdentifier)> for NewUserOrganization
- impl: impl ForeignFrom<api_models::user::UserOrgMerchantCreateRequest> for diesel_models::organization::OrganizationNew
- impl: impl From<(user_api::CreateTenantUserRequest, MerchantAccountIdentifier)> for NewUserMerchant
- impl: impl TryFrom<(user_api::CreateTenantUserRequest, MerchantAccountIdentifier)> for NewUser
- impl: impl From<TenantLevel> for EntityInfo
**crates/router/src/types/domain/user/decision_manager.rs**
Modify existing code
**crates/router/src/utils/user.rs**
Add:
- function: pub::create_merchant_account_request_for_org
**crates/router/src/utils/user_role.rs**
Add:
- function: pub::get_single_org_id
**crates/router_env/src/logger/types.rs**
Modify existing code
|
{"issue_number": 6707, "pr_number": 6708, "commits_count": 1, "files_changed": 22, "response_length": 3525, "file_count": 24, "needs_breakdown": true}
|
[FEATURE] add cypress tests for void payment in v2
### Feature Description
This implementation adds comprehensive V2 API testing for payment void/cancel operations across different payment states. The feature introduces a new Cypress test suite that validates three critical scenarios: successfully voiding a payment in the requires_capture state `after manual capture confirmation`, attempting to void a payment in the `requires_payment_method` state, and attempting to void a completed payment in the `succeeded` state.
### Possible Implementation
A new test file `VoidPayments.cy.js` contains three separate test contexts that verify void behavior across payment states using both manual and automatic capture flows.
### Have you spent some time checking if this feature request has been raised before?
- [x] I checked and didn't find a similar issue
### Have you read the Contributing Guidelines?
- [x] I have read the [Contributing Guidelines](https://github.com/juspay/hyperswitch/blob/main/docs/CONTRIBUTING.md)
### Are you willing to submit a PR?
Yes, I am willing to submit a PR!
|
<think>
PR Context:
- Title: test(cypress): add cypress tests for void payment in v2
- Merged: 2025-10-07T17:28:46Z
- Files changed: 9 files
- Commits: 7 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [X] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
<!-- Describe your changes in detail -->
This implementation adds comprehensive V2 API testing for payment void/cancel operations across different payment states. The feature introduces a new Cypress test suite that validates three critical scenarios: successfully voiding a payment i
</think>
To implement this, you'll need to modify:
(No detailed commit information available)
|
{"issue_number": 9638, "pr_number": 9646, "commits_count": 0, "files_changed": 9, "response_length": 785, "file_count": 0, "needs_breakdown": false}
|
[FEATURE] Kv Redis feature for V2 models
### Feature Description
Extend kv support for v2 models
### Possible Implementation
Use existing construct to extend to v2 models
### Have you spent some time checking if this feature request has been raised before?
- [x] I checked and didn't find a similar issue
### Have you read the Contributing Guidelines?
- [x] I have read the [Contributing Guidelines](https://github.com/juspay/hyperswitch/blob/main/docs/CONTRIBUTING.md)
### Are you willing to submit a PR?
Yes, I am willing to submit a PR!
|
<think>
PR Context:
- Title: feat: Kv changes for V2 feature
- Merged: 2025-06-26T14:22:59Z
- Files changed: 15 files
- Commits: 26 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [ ] New feature
- [x] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
#8389
- Added Kv Redis support to - payment_intent V2, payment_attempt V2 models
- Added enable Kv route for v2 merchant-account
added enable kv api for v2 merchant account
`
curl --location 'https://<host>/v2/merchant-accounts/:mid/kv' \
--header 'Authorization: admin-api
</think>
To implement this, you'll need to modify:
**Detailed Implementation:**
**Commit 1:** feat: Kv changes for V2 feature (#8198)
Co-authored-by: Akshay S <[email protected]>
Co-authored-by
Files to modify:
**crates/diesel_models/src/kv.rs**
Add:
- struct: pub::PaymentAttemptUpdateMems
**crates/diesel_models/src/payment_attempt.rs**
Add:
- function: pub::apply_changeset
- impl: impl PaymentAttemptUpdateInternal
**crates/diesel_models/src/payment_intent.rs**
Add:
- function: pub::apply_changeset
- impl: impl PaymentIntentUpdateInternal
**crates/router/src/lib.rs**
Modify existing code
**crates/router/src/routes/admin.rs**
Add:
- function: pub::merchant_account_toggle_kv
- function: pub::merchant_account_kv_status
**crates/router/src/routes/app.rs**
Add:
- function: pub::server
- impl: impl DummyConnector
**crates/router/src/routes/dummy_connector.rs**
Modify existing code
**crates/router/src/routes/dummy_connector/core.rs**
Modify existing code
**crates/storage_impl/src/customers.rs**
Add:
- function: pub::get_global_id_label
- function: pub::get_merchant_scoped_id_label
- mod: private::label
**crates/storage_impl/src/lib.rs**
Add:
- function: private::unique_constraints
- function: private::table_name
- impl: impl UniqueConstraints for diesel_models::PaymentAttempt
**crates/storage_impl/src/payments/payment_attempt.rs**
Add:
- function: pub::get_profile_id_connector_transaction_label
- function: pub::get_global_id_label
- mod: private::label
**crates/storage_impl/src/payments/payment_intent.rs**
Modify existing code
**crates/storage_impl/src/redis/kv_store.rs**
Modify existing code
|
{"issue_number": 8389, "pr_number": 8198, "commits_count": 1, "files_changed": 15, "response_length": 2397, "file_count": 15, "needs_breakdown": false}
|
refactor(router): add revenue_recovery_metadata to payment intent in diesel and api model for v2 flow
Add the following fields to the api and diesel models Feature meta data
retry_count: Total number of billing connector + recovery retries for a payment intent.
payment_connector_transmission: It's supposed to tell if the payment_connector has been called or not.
billing_connector_id: To update the invoice at billing connector.
active_attempt_payment_connector_id : Process tracker needs payment merchant connector account id to schedule the retry attempt.
billing_connector_mit_token_details : MIT related information given by billing connector contains two fields.
1. customer_id : Customer Id of the customer in billing connector
2. payment_processor_token : The token used by the payment processor to retry the payment.
payment_method_type: This represents payment Method type like Card,Crypto,Mandate etc..
payment_method_subtype : This represents the subtype of the payment method like Credit, CryptoCurrency etc..
|
<think>
PR Context:
- Title: refactor(router): add revenue_recovery_metadata to payment intent in diesel and api model for v2 flow
- Merged: 2025-02-14T11:41:35Z
- Files changed: 6 files
- Commits: 23 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [ ] New feature
- [ ] Enhancement
- [x] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
Adds the following fields to the api and diesel models Feature meta data
retry_count: Total number of billing connector + recovery retries for a payment intent.
payment_connector_transmission: It's supposed to tell if the payment_connector has been called or not.
billing_con
</think>
To implement this, you'll need to modify:
**Detailed Implementation:**
**Commit 1:** refactor(router): add revenue_recovery_metadata to payment intent in diesel and api model for v2 fl
Files to modify:
**crates/api_models/src/payments.rs**
Add:
- struct: pub::FeatureMetadata
- struct: pub::PaymentRevenueRecoveryMetadata
- struct: pub::BillingConnectorPaymentDetails
**crates/common_enums/src/enums.rs**
Add:
- enum: pub::PaymentConnectorTransmission
**crates/diesel_models/src/types.rs**
Add:
- struct: pub::FeatureMetadata
- struct: pub::PaymentRevenueRecoveryMetadata
- struct: pub::BillingConnectorPaymentDetails
**crates/hyperswitch_domain_models/src/lib.rs**
Add:
- function: private::convert_from
- function: private::convert_back
- function: private::convert_from
- function: private::convert_back
- function: private::convert_from
- function: private::convert_back
- impl: impl ApiModelToDieselModelConvertor<ApiFeatureMetadata> for FeatureMetadata
- impl: impl ApiModelToDieselModelConvertor<ApiRevenueRecoveryMetadata> for PaymentRevenueRecoveryMetadata
- impl: impl ApiModelToDieselModelConvertor<ApiBillingConnectorPaymentDetails> for BillingConnectorPaymentDetails
**crates/openapi/src/openapi_v2.rs**
Modify existing code
|
{"issue_number": 7177, "pr_number": 7176, "commits_count": 1, "files_changed": 6, "response_length": 2069, "file_count": 7, "needs_breakdown": false}
|
disable stripe
disable stripe
|
<think>
PR Context:
- Title: ci: disable stripe in cypress
- Merged: 2025-02-04T10:41:55Z
- Files changed: 1 files
- Commits: 2 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [ ] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [x] CI/CD
## Description
<!-- Describe your changes in detail -->
disable sprite.
closes #7184
### Additional Changes
- [ ] This PR modifies the API contract
- [ ] This PR modifies the database schema
- [ ] This PR modifies application configuration/environment variables
<!--
Provide links
</think>
To implement this, you'll need to modify:
(No detailed commit information available)
|
{"issue_number": 7184, "pr_number": 7183, "commits_count": 0, "files_changed": 1, "response_length": 759, "file_count": 0, "needs_breakdown": false}
|
feat(vsaas): add processor_merchant_id and created_by column in payment_intents and payments_attempts for v1
Tracking issue #1: https://github.com/juspay/hyperswitch-control-center/issues/2544
Tracking issue #2: https://github.com/juspay/hyperswitch-control-center/issues/2546
|
<think>
PR Context:
- Title: feat(vsaas): add processor_merchant_id and created_by column in payment_intents and payments_attempts for v1
- Merged: 2025-04-22T08:56:56Z
- Files changed: 30 files
- Commits: 27 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [x] New feature
- [x] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
<!-- Describe your changes in detail -->
- added `processor_merchant_id` and` created_by` column in `diesel_models` and `hyperswitch_domain_models`
- added migrations
- ~added backfilling `processor_merchant_id` column in migrations~ (Due to staggered release backfilling should be
</think>
To implement this, you'll need to modify:
**Detailed Implementation:**
**Commit 1:** feat(vsaas): add processor_merchant_id and created_by column in payment_intents and payments_attempt
Files to modify:
**crates/common_utils/src/macros.rs**
Add:
- function: private::test_enum_from_str_ok
- function: private::test_enum_from_str_failures_yield_invalid
- function: private::test_enum_display_and_serialize
- function: private::test_enum_deserialize
- mod: private::tests
**crates/common_utils/src/types.rs**
Modify existing code
**crates/diesel_models/src/payment_attempt.rs**
Modify existing code
**crates/diesel_models/src/payment_intent.rs**
Modify existing code
**crates/diesel_models/src/schema.rs**
Modify existing code
**crates/diesel_models/src/schema_v2.rs**
Modify existing code
**crates/diesel_models/src/user/sample_data.rs**
Modify existing code
**crates/hyperswitch_domain_models/src/payments.rs**
Modify existing code
**crates/hyperswitch_domain_models/src/payments/payment_attempt.rs**
Modify existing code
**crates/hyperswitch_domain_models/src/payments/payment_intent.rs**
Modify existing code
**crates/router/src/core/payments/helpers.rs**
Modify existing code
**crates/router/src/core/payments/operations/payment_approve.rs**
Modify existing code
**crates/router/src/core/payments/operations/payment_cancel.rs**
Modify existing code
**crates/router/src/core/payments/operations/payment_capture.rs**
Modify existing code
**crates/router/src/core/payments/operations/payment_capture_v2.rs**
Modify existing code
**crates/router/src/core/payments/operations/payment_create.rs**
Modify existing code
**crates/router/src/core/payments/operations/payment_get.rs**
Modify existing code
**crates/router/src/core/payments/operations/payment_get_intent.rs**
Modify existing code
**crates/router/src/core/payments/operations/payment_reject.rs**
Modify existing code
**crates/router/src/core/payments/operations/payment_status.rs**
Modify existing code
**crates/router/src/core/payments/operations/payment_update_intent.rs**
Modify existing code
**crates/router/src/core/payments/operations/payments_incremental_authorization.rs**
Modify existing code
**crates/router/src/core/payments/retry.rs**
Modify existing code
**crates/router/src/core/utils.rs**
Remove:
- function: private::validate_platform_merchant
- function: private::get_platform_merchant_id
- trait: pub::ValidatePlatformMerchant
- impl: impl ValidatePlatformMerchant for storage::PaymentIntent
**crates/router/src/types/storage/payment_attempt.rs**
Modify existing code
**crates/router/src/utils/user/sample_data.rs**
Modify existing code
**crates/storage_impl/src/mock_db/payment_attempt.rs**
Modify existing code
**crates/storage_impl/src/payments/payment_attempt.rs**
Modify existing code
|
{"issue_number": 7769, "pr_number": 7768, "commits_count": 1, "files_changed": 30, "response_length": 3643, "file_count": 30, "needs_breakdown": true}
|
[BUG] recurring mandate through bancontact card bank redirect via stripe fails
connector throws below error:
```
"The provided bancontact PaymentMethod cannot be used again. It was used in a previous PaymentIntent or SetupIntent to set up a sepa_debit PaymentMethod, which can be used for multiple payments. To find the ID of the sepa_debit PaymentMethod, list the sepa_debit PaymentMethods associated with the Customer used to set up this PaymentMethod."
```
this is because we're just passing bancontact card payment method id instead of sepa direct debit payment method id.
check:
- https://docs.stripe.com/payments/bancontact
- https://docs.stripe.com/payments/bancontact/save-during-payment?platform=web#web-charge-sepa-pm
|
<think>
PR Context:
- Title: fix(connector): [stripe] fix bank redirect (`bancontact_card`) recurring mandate
- Merged: 2025-05-13T07:07:45Z
- Files changed: 1 files
- Commits: 2 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [x] Bugfix
- [ ] New feature
- [ ] Enhancement
- [x] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
<!-- Describe your changes in detail -->
this pr aims to fix the stripe bank redirect recurring mandate.
for context, `bancontact` recurring mandates happen via `sepa direct debit` and hence, stripe sends 2 connector mandate ids as shown below:
```json
{
"payment_method": "
</think>
To implement this, you'll need to modify:
**Detailed Implementation:**
**Commit 1:** fix(connector): [stripe] fix bank redirect (`bancontact_card`) recurring mandate (#7990)
Files to modify:
**crates/router/src/connector/stripe/transformers.rs**
Add:
- function: pub::get_payment_method_id
|
{"issue_number": 7989, "pr_number": 7990, "commits_count": 1, "files_changed": 1, "response_length": 1025, "file_count": 3, "needs_breakdown": false}
|
docs: API-ref revamp for better user experience
API-ref revamp for better user experience
|
<think>
PR Context:
- Title: docs: changes for api ref
- Merged: 2025-02-25T19:02:34Z
- Files changed: 4 files
- Commits: 8 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [ ] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [X] Documentation
- [ ] CI/CD
## Description
<!-- Describe your changes in detail -->
We have changes the Intro page of the API-ref to make it more informative and navigable.
Also, The API sidebar is now re-organised basis of different use-cases to improve the dev experience.
Added an introduction page to payments API expla
</think>
To implement this, you'll need to modify:
(No detailed commit information available)
|
{"issue_number": 7323, "pr_number": 7324, "commits_count": 0, "files_changed": 4, "response_length": 755, "file_count": 0, "needs_breakdown": false}
|
[REFACTOR] Worldpay payments integration
### Feature Description
WorldPay payments integration currently makes use of modular APIs which gives more control over the integration. This approach is not best compatible with HyperSwitch due to WP's 3DS flows - which requires sending PAN (card numbers) in multiple places. For `on_session` transactions, this would contribute to the added complexity since data is not stored in such transactions (or stored for ~15mins in redis cache).
Migrating to WP's standard payments API follows payment resource creation in an uniform way.
### Possible Implementation
Migrate from modular APIs [[ref](https://developer.worldpay.com/products/access/card-payments)] to standard payment APIs [[ref](https://developer.worldpay.com/products/access/payments/openapi)].
### Have you spent some time checking if this feature request has been raised before?
- [X] I checked and didn't find a similar issue
### Have you read the Contributing Guidelines?
- [X] I have read the [Contributing Guidelines](https://github.com/juspay/hyperswitch/blob/main/docs/CONTRIBUTING.md)
### Are you willing to submit a PR?
Yes, I am willing to submit a PR!
|
<think>
PR Context:
- Title: refactor(connector): [WorldPay] migrate from modular to standard payment APIs
- Merged: 2024-10-21T10:24:32Z
- Files changed: 12 files
- Commits: 30 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [ ] New feature
- [x] Enhancement
- [x] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
Described in #6316
### Additional Changes
- [ ] This PR modifies the API contract
- [ ] This PR modifies the database schema
- [ ] This PR modifies application configuration/environment variables
<!--
Provide links to the files with corresponding changes.
Following a
</think>
To implement this, you'll need to modify:
**Detailed Implementation:**
**Commit 1:** refactor(connector): [WorldPay] migrate from modular to standard payment APIs (#6317)
Co-authored-by
Files to modify:
**crates/router/src/connector/utils.rs**
Add:
- function: private::get_capture_method
**crates/router/src/connector/worldpay.rs**
Modify existing code
**crates/router/src/connector/worldpay/requests.rs**
Remove:
- struct: pub::WorldpayPaymentsRequest
- struct: pub::Instruction
- struct: pub::RequestAutoSettlement
- struct: pub::CardToken
- struct: pub::WalletPayment
- struct: pub::ExpiryDate
- enum: pub::PaymentInstrument
- enum: pub::PaymentType
Add:
- struct: pub::WorldpayPaymentsRequest
- struct: pub::Merchant
- struct: pub::Instruction
- struct: pub::CardPayment
- struct: pub::CardToken
- struct: pub::WalletPayment
- struct: pub::ExpiryDate
- struct: pub::AutoSettlement
- enum: pub::PaymentInstrument
- enum: pub::PaymentType
**crates/router/src/connector/worldpay/response.rs**
Remove:
- function: private::try_from
- function: private::foreign_try_from
- enum: pub::RefundOutcome
- impl: impl ForeignTryFrom<Option<PaymentLinks>> for types::ResponseId
Add:
- struct: pub::AuthorizedResponse
- struct: pub::FraudHighRiskResponse
- struct: pub::RefusedResponse
- struct: pub::ThreeDsResponse
- struct: pub::DDCResponse
- struct: pub::DDCToken
- struct: pub::DDCActionLink
- struct: pub::SelfLinkInner
- struct: pub::ActionLinks
- struct: pub::ActionLink
- struct: pub::Fraud
- enum: pub::WorldpayPaymentResponseFields
- enum: pub::IssuerResponse
- enum: pub::FraudOutcome
**crates/router/src/connector/worldpay/transformers.rs**
Add:
- function: private::try_from
- struct: pub::WorldpayConnectorMetadataObject
- impl: impl TryFrom<&Option<pii::SecretSerdeValue>> for WorldpayConnectorMetadataObject
**crates/router/src/consts.rs**
Modify existing code
**crates/router/src/lib.rs**
Modify existing code
|
{"issue_number": 6316, "pr_number": 6317, "commits_count": 1, "files_changed": 12, "response_length": 2831, "file_count": 9, "needs_breakdown": false}
|
[FEATURE] Payment void endpoint for v2
### Feature Description
Add support for Payment Cancel in V2.
### Possible Implementation
Add V2 payments_cancel flow by completing GetTracker, UpdateTracker, and Domain traits for payment cancel endpoint.
### Have you spent some time checking if this feature request has been raised before?
- [x] I checked and didn't find a similar issue
### Have you read the Contributing Guidelines?
- [x] I have read the [Contributing Guidelines](https://github.com/juspay/hyperswitch/blob/main/docs/CONTRIBUTING.md)
### Are you willing to submit a PR?
Yes, I am willing to submit a PR!
|
<think>
PR Context:
- Title: feat(router): Add v2 payment cancellation flow
- Merged: 2025-09-22T18:39:33Z
- Files changed: 17 files
- Commits: 14 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [x] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
<!-- Describe your changes in detail -->
Add V2 payments_cancel flow by endpoint `{{baseUrl}}/v2/payments/:payment_id/cancel`.A payment can be cancelled when the status is RequiresCapture, PartiallyAuthorizedAndRequiresCapture, or PartiallyCapturedAndCapturable.
### Additional Cha
</think>
To implement this, you'll need to modify:
**Detailed Implementation:**
**Commit 1:** feat(router): Add v2 payment cancellation flow (#9083)
Co-authored-by: hyperswitch-bot[bot] <1485255
Files to modify:
**crates/api_models/src/events/payment.rs**
Add:
- function: private::get_api_event_type
- function: private::get_api_event_type
- impl: impl ApiEventMetric for payments::PaymentsCancelRequest
- impl: impl ApiEventMetric for payments::PaymentsCancelResponse
**crates/api_models/src/payments.rs**
Add:
- struct: pub::PaymentsCancelRequest
- struct: pub::PaymentsCancelResponse
**crates/diesel_models/src/payment_attempt.rs**
Modify existing code
**crates/hyperswitch_domain_models/src/payments.rs**
Add:
- struct: pub::PaymentCancelData
**crates/hyperswitch_domain_models/src/payments/payment_attempt.rs**
Modify existing code
**crates/hyperswitch_domain_models/src/payments/payment_intent.rs**
Modify existing code
**crates/hyperswitch_domain_models/src/router_data.rs**
Add:
- function: private::get_payment_intent_update
- function: private::get_payment_attempt_update
- function: private::get_amount_capturable
- function: private::get_captured_amount
- function: private::get_attempt_status_for_db_update
- impl: impl TrackerPostUpdateObjects<
router_flow_types::Void,
router_request_types::PaymentsCancelData,
payments::PaymentCancelData<router_flow_types::Void>,
> for RouterData<
router_flow_types::Void,
router_request_types::PaymentsCancelData,
router_response_types::PaymentsResponseData,
>
**crates/hyperswitch_interfaces/src/conversion_impls.rs**
Modify existing code
**crates/router/src/core/payments.rs**
Add:
- function: private::set_cancellation_reason
- function: private::set_cancellation_reason
- function: private::set_cancellation_reason
- function: private::set_cancellation_reason
- function: private::get_payment_attempt
- function: private::list_payments_attempts
- function: private::get_client_secret
- function: private::get_payment_intent
- function: private::get_merchant_connector_details
- function: private::get_payment_method_info
- function: private::get_payment_method_token
- function: private::get_mandate_id
- function: private::get_address
- function: private::get_creds_identifier
- function: private::get_token
- function: private::get_multiple_capture_data
- function: private::get_payment_link_data
- function: private::get_ephemeral_key
- function: private::get_setup_mandate
- function: private::get_poll_config
- function: private::get_authentication
- function: private::get_frm_message
- function: private::get_refunds
- function: private::get_disputes
- function: private::get_authorizations
- function: private::get_attempts
- function: private::get_recurring_details
- function: private::get_payment_intent_profile_id
- function: private::get_currency
- function: private::get_amount
- function: private::get_payment_attempt_connector
- function: private::get_merchant_connector_id_in_attempt
- function: private::get_connector_customer_id
- function: private::get_billing_address
- function: private::get_payment_method_data
- function: private::get_sessions_token
- function: private::get_token_data
- function: private::get_mandate_connector
- function: private::get_force_sync
- function: private::get_capture_method
- function: private::get_optional_payment_attempt
- function: private::get_pre_routing_result
- function: private::get_optional_external_vault_session_details
- function: private::set_payment_intent
- function: private::set_client_secret
- function: private::set_payment_attempt
- function: private::set_payment_method_data
- function: private::set_payment_method_token
- function: private::set_email_if_not_present
- function: private::set_payment_method_id_in_attempt
- function: private::set_pm_token
- function: private::set_connector_customer_id
- function: private::push_sessions_token
- function: private::set_surcharge_details
- function: private::set_merchant_connector_id_in_attempt
- function: private::set_card_network
- function: private::set_co_badged_card_data
- function: private::set_frm_message
- function: private::set_payment_intent_status
- function: private::set_authentication_type_in_attempt
- function: private::set_recurring_mandate_payment_data
- function: private::set_mandate_id
- function: private::set_setup_future_usage_in_payment_intent
- function: private::set_prerouting_algorithm_in_payment_intent
- function: private::set_connector_in_payment_attempt
- function: private::set_connector_request_reference_id
- function: private::set_connector_response_reference_id
- function: private::set_vault_session_details
- function: private::set_routing_approach_in_attempt
- function: private::set_connector_request_reference_id_in_payment_attempt
- function: private::set_cancellation_reason
- impl: impl OperationSessionGetters<F> for PaymentCancelData<F>
- impl: impl OperationSessionSetters<F> for PaymentCancelData<F>
**crates/router/src/core/payments/flows/cancel_flow.rs**
Remove:
- function: private::construct_router_data
Add:
- function: private::construct_router_data
- impl: impl ConstructFlowSpecificData<api::Void, types::PaymentsCancelData, types::PaymentsResponseData> for hyperswitch_domain_models::payments::PaymentCancelData<api::Void>
**crates/router/src/core/payments/operations.rs**
Add:
- mod: pub::payment_cancel_v2
**crates/router/src/core/payments/operations/payment_cancel_v2.rs**
Add:
- function: private::to_validate_request
- function: private::to_get_tracker
- function: private::to_domain
- function: private::to_update_tracker
- function: private::to_validate_request
- function: private::to_get_tracker
- function: private::to_domain
- function: private::to_update_tracker
- function: private::validate_request
- function: private::get_trackers
- function: private::update_trackers
- function: private::get_customer_details
- function: private::make_pm_data
- function: private::perform_routing
- function: private::validate_status_for_operation
- struct: pub::PaymentsCancel
- impl: impl Operation<F, api::PaymentsCancelRequest> for &PaymentsCancel
- impl: impl Operation<F, api::PaymentsCancelRequest> for PaymentsCancel
- impl: impl ValidateRequest<
F,
api::PaymentsCancelRequest,
hyperswitch_domain_models::payments::PaymentCancelData<F>,
> for PaymentsCancel
- impl: impl GetTracker<
F,
hyperswitch_domain_models::payments::PaymentCancelData<F>,
api::PaymentsCancelRequest,
> for PaymentsCancel
- impl: impl UpdateTracker<
F,
hyperswitch_domain_models::payments::PaymentCancelData<F>,
api::PaymentsCancelRequest,
> for PaymentsCancel
- impl: impl Domain<F, api::PaymentsCancelRequest, hyperswitch_domain_models::payments::PaymentCancelData<F>> for PaymentsCancel
- impl: impl ValidateStatusForOperation for PaymentsCancel
**crates/router/src/core/payments/operations/payment_response.rs**
Add:
- function: private::to_post_update_tracker
- function: private::update_tracker
- impl: impl Operation<F, types::PaymentsCancelData> for PaymentResponse
- impl: impl PostUpdateTracker<
F,
hyperswitch_domain_models::payments::PaymentCancelData<F>,
types::PaymentsCancelData,
> for PaymentResponse
**crates/router/src/core/payments/transformers.rs**
Add:
- function: pub::construct_cancel_router_data_v2
- function: pub::construct_router_data_for_cancel
- function: private::generate_response
- impl: impl GenerateResponse<api_models::payments::PaymentsCancelResponse> for hyperswitch_domain_models::payments::PaymentCancelData<F>
**crates/router/src/routes/app.rs**
Modify existing code
**crates/router/src/routes/payments.rs**
Add:
- function: pub::payments_cancel
|
{"issue_number": 9082, "pr_number": 9083, "commits_count": 1, "files_changed": 17, "response_length": 9004, "file_count": 18, "needs_breakdown": true}
|
feat(core): setup platform merchant account
- Setup platform merchant account.
Platform merchant account is a special type of merchant account which can do operations on behalf of other merchant account present in the same organisation.
- Add APIs to create a platform merchant account / convert a merchant account into platform account.
- Feature should be disabled in sandbox and production.
|
<think>
PR Context:
- Title: feat(core): implemented platform merchant account
- Merged: 2024-12-23T13:21:14Z
- Files changed: 30 files
- Commits: 30 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [X] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
#### About the feature
- This the first PR for the Platform Account feature.
- Feature is under development and behind the feature flag.
- Feature is supposed to be disabled for sandbox and production environments.
#### Enabling the platform account.
- New API has been created t
</think>
To implement this, you'll need to modify:
**Detailed Implementation:**
**Commit 1:** feat(core): implemented platform merchant account (#6882)
Co-authored-by: Narayanbhat166 <narayan.bh
Files to modify:
**crates/diesel_models/src/merchant_account.rs**
Modify existing code
**crates/diesel_models/src/payment_intent.rs**
Modify existing code
**crates/diesel_models/src/schema.rs**
Modify existing code
**crates/diesel_models/src/schema_v2.rs**
Modify existing code
**crates/hyperswitch_domain_models/src/errors/api_error_response.rs**
Modify existing code
**crates/hyperswitch_domain_models/src/merchant_account.rs**
Modify existing code
**crates/hyperswitch_domain_models/src/payments.rs**
Modify existing code
**crates/hyperswitch_domain_models/src/payments/payment_intent.rs**
Modify existing code
**crates/router/build.rs**
Modify existing code
**crates/router/src/compatibility/stripe/errors.rs**
Modify existing code
**crates/router/src/compatibility/stripe/payment_intents.rs**
Modify existing code
**crates/router/src/compatibility/stripe/setup_intents.rs**
Modify existing code
**crates/router/src/configs/secrets_transformers.rs**
Modify existing code
**crates/router/src/configs/settings.rs**
Add:
- struct: pub::Platform
**crates/router/src/core/admin.rs**
Add:
- function: pub::enable_platform_account
**crates/router/src/core/fraud_check.rs**
Modify existing code
**crates/router/src/core/fraud_check/operation.rs**
Modify existing code
**crates/router/src/core/fraud_check/operation/fraud_check_post.rs**
Modify existing code
**crates/router/src/core/payments.rs**
Modify existing code
**crates/router/src/core/payments/helpers.rs**
Modify existing code
**crates/router/src/core/payments/operations.rs**
Modify existing code
**crates/router/src/core/payments/operations/payment_approve.rs**
Modify existing code
**crates/router/src/core/payments/operations/payment_cancel.rs**
Modify existing code
**crates/router/src/core/payments/operations/payment_capture.rs**
Modify existing code
**crates/router/src/core/payments/operations/payment_capture_v2.rs**
Modify existing code
**crates/router/src/core/payments/operations/payment_complete_authorize.rs**
Modify existing code
**crates/router/src/core/payments/operations/payment_confirm.rs**
Modify existing code
**crates/router/src/core/payments/operations/payment_confirm_intent.rs**
Modify existing code
**crates/router/src/core/payments/operations/payment_create.rs**
Modify existing code
**crates/router/src/core/payments/operations/payment_create_intent.rs**
Modify existing code
**crates/router/src/core/payments/operations/payment_get.rs**
Modify existing code
**crates/router/src/core/payments/operations/payment_get_intent.rs**
Modify existing code
**crates/router/src/core/payments/operations/payment_post_session_tokens.rs**
Modify existing code
**crates/router/src/core/payments/operations/payment_reject.rs**
Modify existing code
**crates/router/src/core/payments/operations/payment_session.rs**
Modify existing code
**crates/router/src/core/payments/operations/payment_session_intent.rs**
Modify existing code
**crates/router/src/core/payments/operations/payment_start.rs**
Modify existing code
**crates/router/src/core/payments/operations/payment_status.rs**
Modify existing code
**crates/router/src/core/payments/operations/payment_update.rs**
Modify existing code
**crates/router/src/core/payments/operations/payment_update_intent.rs**
Modify existing code
**crates/router/src/core/payments/operations/payments_incremental_authorization.rs**
Modify existing code
**crates/router/src/core/payments/operations/tax_calculation.rs**
Modify existing code
**crates/router/src/core/payments/session_operation.rs**
Modify existing code
**crates/router/src/core/webhooks/incoming.rs**
Modify existing code
**crates/router/src/lib.rs**
Modify existing code
**crates/router/src/routes/admin.rs**
Add:
- function: pub::merchant_account_enable_platform_account
**crates/router/src/routes/app.rs**
Modify existing code
**crates/router/src/routes/lock_utils.rs**
Modify existing code
**crates/router/src/routes/payments.rs**
Modify existing code
**crates/router/src/services/authentication.rs**
Add:
- function: pub::get_id_type_from_header_if_present
- function: private::get_connected_merchant_account
- function: private::get_platform_merchant_account
- function: private::get_and_validate_connected_merchant_id
- function: private::throw_error_if_platform_merchant_authentication_required
**crates/router/src/utils/user/sample_data.rs**
Modify existing code
**crates/router/src/workflows/outgoing_webhook_retry.rs**
Modify existing code
**crates/router/src/workflows/payment_sync.rs**
Modify existing code
**crates/router/tests/payments.rs**
Modify existing code
**crates/router/tests/payments2.rs**
Modify existing code
**crates/router_env/src/logger/types.rs**
Modify existing code
|
{"issue_number": 6883, "pr_number": 6882, "commits_count": 1, "files_changed": 30, "response_length": 5751, "file_count": 58, "needs_breakdown": true}
|
[FEAT] Add mandates for Payload
- Add MIT payments to Payload connector
- Add connector customer
- Fix amount conversion
Relevant docs:
- https://docs.payload.com/apis/payments/
- https://docs.payload.com/apis/payments/charging-a-customer/
- https://docs.payload.com/apis/automatic-payments/
- https://docs.payload.com/apis/customers/
- https://docs.payload.com/apis/object-reference/customers/
- https://docs.payload.com/apis/object-reference/transactions/
- https://docs.payload.com/apis/api-design/
|
<think>
PR Context:
- Title: feat(connector): [payload] add recurring payments
- Merged: 2025-07-31T07:04:50Z
- Files changed: 23 files
- Commits: 29 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [x] New feature
- [ ] Enhancement
- [x] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [x] CI/CD
## Description
<!-- Describe your changes in detail -->
This PR targets Payload connector and has multiple fixes and a new feature introduced:
- Add support for mandates (PMID and MandateID)
- Add filters
- Enable connector customer
- Enable mandates
- Add currency filter
- Change A
</think>
To implement this, you'll need to modify:
**Detailed Implementation:**
**Commit 1:** feat(connector): [payload] add recurring payments (#8597)
Files to modify:
**crates/hyperswitch_connectors/src/connectors/payload.rs**
Remove:
- impl: impl ConnectorIntegration<Session, PaymentsSessionData, PaymentsResponseData> for Payload
Add:
- impl: impl ConnectorIntegration<Session, PaymentsSessionData, PaymentsResponseData> for Payload
**crates/hyperswitch_connectors/src/connectors/payload/requests.rs**
Modify existing code
**crates/hyperswitch_connectors/src/connectors/payload/responses.rs**
Modify existing code
**crates/hyperswitch_connectors/src/connectors/payload/transformers.rs**
Remove:
- struct: pub::PayloadAuthType
Add:
- function: private::try_from
- function: private::try_from
- struct: pub::PayloadAuth
- struct: pub::PayloadAuthType
- impl: impl TryFrom<(&ConnectorAuthType, enums::Currency)> for PayloadAuth
- impl: impl TryFrom<&ConnectorAuthType> for PayloadAuthType
**crates/hyperswitch_connectors/src/default_implementations.rs**
Modify existing code
**crates/hyperswitch_connectors/src/utils.rs**
Add:
- function: private::is_mandate_payment
**crates/hyperswitch_domain_models/src/router_request_types.rs**
Modify existing code
**crates/router/tests/connectors/utils.rs**
Modify existing code
**crates/test_utils/src/connector_auth.rs**
Add:
- function: private::from
- impl: impl From<CurrencyAuthKey> for ConnectorAuthType
|
{"issue_number": 8610, "pr_number": 8597, "commits_count": 1, "files_changed": 23, "response_length": 2221, "file_count": 11, "needs_breakdown": false}
|
Removing mailhog container from the docker setup
Removing mailhog container from the docker setup
|
<think>
PR Context:
- Title: fix: docker changes in setup script
- Merged: 2025-05-08T09:01:27Z
- Files changed: 7 files
- Commits: 7 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [X] Bugfix
- [ ] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
<!-- Describe your changes in detail -->
Repopulating the docker changes in the stable release
### Additional Changes
- [ ] This PR modifies the API contract
- [ ] This PR modifies the database schema
- [ ] This PR modifies application configuration/environment variables
<
</think>
To implement this, you'll need to modify:
(No detailed commit information available)
|
{"issue_number": 7962, "pr_number": 7979, "commits_count": 0, "files_changed": 7, "response_length": 765, "file_count": 0, "needs_breakdown": false}
|
[ENHANCE] Improve Error Reporting in change_password with Printable Context
This issue aims to improve the debuggability of the `change_password` function by adding a printable message to a potential database error. Currently, if the database update fails, a generic `InternalServerError` is returned. By attaching a specific, contextual message, we can make debugging and logging much more effective.
In the [change_password](https://github.com/juspay/hyperswitch/blob/cf30da2df05aac69fd82b676e639b2fbc85dcae5/crates/router/src/core/user.rs#L429) function located in `crates/router/src/core/user.rs`, we update the user's password in the database. The relevant code block is:
If the update_user_by_user_id operation fails (e.g., due to a database connection issue, a constraint violation, etc.), it's wrapped in a [UserErrors::InternalServerError](https://github.com/juspay/hyperswitch/blob/cf30da2df05aac69fd82b676e639b2fbc85dcae5/crates/router/src/core/user.rs#L461). While this correctly signals a server-side problem, the error itself lacks specific context. When debugging, an engineer seeing this error in the logs would have to trace back the execution flow to understand which operation and for which user it failed.
#### __Proposed Solution 💡__
We can enhance this by using the `.attach_printable()` method from the `error-stack` crate. This method allows us to attach a static or pre-formatted string message to the error context.
The goal is to modify the code to include the error message, making it immediately clear what failed during InternalServerError
#### __How to Test Your Changes 🧪__
1. __Make the code change__: Apply the suggested modification to the `change_password` function.
2. __Build the project__: Run `cargo build` or `cargo check` to ensure your changes compile correctly. __If it compiles, the `attach_printable` should work fine.__
3. __Simulate an error (Advanced)__:
- A good way to test this end-to-end is to:
1. Create a user via the signup flow.
2. Log in and get an authentication token.
3. Call the `change_password` endpoint.
- To reliably trigger the error for observation, you could temporarily modify the `update_user_by_user_id` method in its respective implementation to always return an error.
- A simpler way to verify the message is being constructed is to temporarily introduce a `panic!` or a different, guaranteed error inside the `attach_printable` argument to see if it gets hit (remember to remove this temporary change!).
4. __Observe the output__: If you can trigger the error, you should see your new, more descriptive message in the application logs or error response, making it clear that the failure happened during the password update for a specific user.
####
####
|
<think>
PR Context:
- Title: feat: Add attach_printable() for better error logging
- Merged: 2025-10-15T16:19:48Z
- Files changed: 1 files
- Commits: 25 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [ ] New feature
- [✔️ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
Just modified the error logging on change of password for getting better error details and description. This helps in knowing about error in more detail.
### Additional Changes
- [ ] This PR modifies the API contract
- [ ] This PR modifies the database schema
- [ ] This PR
</think>
To implement this, you'll need to modify:
**Detailed Implementation:**
**Commit 1:** feat: Add attach_printable() for better error logging (#9667)
Files to modify:
**crates/router/src/core/user.rs**
Modify existing code
|
{"issue_number": 9641, "pr_number": 9667, "commits_count": 1, "files_changed": 1, "response_length": 925, "file_count": 3, "needs_breakdown": false}
|
[FEATURE] Automatic connector_payment_id hashing in v2 if length > 128 in v2
### Feature Description
Automatically hash connector_payment_id longer than 128 chars and store the original in connector_payment_data.
### Possible Implementation
Implement hashing in PaymentAttemptUpdate conversion by using ConnectorTransactionId::form_id_and_data, setting connector_payment_id to the hash and preserving the original in connector_payment_data.
### Have you spent some time checking if this feature request has been raised before?
- [x] I checked and didn't find a similar issue
### Have you read the Contributing Guidelines?
- [x] I have read the [Contributing Guidelines](https://github.com/juspay/hyperswitch/blob/main/docs/CONTRIBUTING.md)
### Are you willing to submit a PR?
Yes, I am willing to submit a PR!
|
<think>
PR Context:
- Title: fix(payments): automatic connector_payment_id hashing in v2 if length > 128
- Merged: 2025-09-01T14:34:13Z
- Files changed: 2 files
- Commits: 6 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [x] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
<!-- Describe your changes in detail -->
Implement hashing in PaymentAttemptUpdate conversion by using ConnectorTransactionId::form_id_and_data, setting connector_payment_id to the hash and preserving the original in connector_payment_data.For worldpay connector_payment_id should be
</think>
To implement this, you'll need to modify:
**Detailed Implementation:**
**Commit 1:** fix(payments): automatic connector_payment_id hashing in v2 if length > 128 (#9017)
Files to modify:
**crates/diesel_models/src/payment_attempt.rs**
Modify existing code
**crates/hyperswitch_domain_models/src/payments/payment_attempt.rs**
Modify existing code
|
{"issue_number": 9016, "pr_number": 9017, "commits_count": 1, "files_changed": 2, "response_length": 1074, "file_count": 4, "needs_breakdown": false}
|
[FEATURE] Alter refund schema to support VSAAS cases
### Feature Description
Make changes to support the integration of the (VSAAS) into the refund flow. The new columns, `processor_merchant_id` and `created_by`, are essential for storing specific information related to VSAAS transactions within the refund record.
This will allow for better tracking and management of refunds, which is a key requirement for Vertical SaaS implementations.
### Possible Implementation
Add new columns to refunds schema
### Have you spent some time checking if this feature request has been raised before?
- [x] I checked and didn't find a similar issue
### Have you read the Contributing Guidelines?
- [x] I have read the [Contributing Guidelines](https://github.com/juspay/hyperswitch/blob/main/docs/CONTRIBUTING.md)
### Are you willing to submit a PR?
Yes, I am willing to submit a PR!
|
<think>
PR Context:
- Title: feat(refunds): add new columns in refund table for vsaas
- Merged: None
- Files changed: 9 files
- Commits: 1 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [x] New feature
- [ ] Enhancement
- [x] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
This PR adds new columns to the `refund` table to support VSAAS functionality.
This PR introduces changes to add new columns (`processor_merchant_id`, `created_by`) to the `refund` table and integrate them into the application logic to support Vertical SaaS (VSAAS).
## Changes
</think>
To implement this, you'll need to modify:
(No detailed commit information available)
|
{"issue_number": 8366, "pr_number": 8367, "commits_count": 0, "files_changed": 9, "response_length": 770, "file_count": 0, "needs_breakdown": false}
|
Refactor(routing): Fallback to current active routing algorithm
Add connectors from the current active routing algorithm before fallback connectors
|
<think>
PR Context:
- Title: refactor(routing): Add connectors from current active routing algorithm before adding fallback connectors
- Merged: 2025-05-14T18:35:38Z
- Files changed: 1 files
- Commits: 11 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [ ] New feature
- [ ] Enhancement
- [x] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
<!-- Describe your changes in detail -->
This PR modifies critical paths , specifically the `decide_connector` function and the `route_connector_v1_for_payments` function in the payments confirm flow.
These changes are made corresponding to a use case for Narvar. In case the connect
</think>
To implement this, you'll need to modify:
**Detailed Implementation:**
**Commit 1:** refactor(routing): Add connectors from current active routing algorithm before adding fallback conne
Files to modify:
**crates/router/src/core/payments.rs**
Modify existing code
|
{"issue_number": 7920, "pr_number": 7921, "commits_count": 1, "files_changed": 1, "response_length": 1020, "file_count": 3, "needs_breakdown": false}
|
refactor(NMI,PAYONE) , Move files from router to hyperswitch connectors
Move the connectors from routers to hyperswitch_connectors
|
<think>
PR Context:
- Title: refactor(connector): [NMI,PAYONE,RISKIFIED] moved to hyperswitch_connectors
- Merged: 2025-04-24T10:35:43Z
- Files changed: 20 files
- Commits: 27 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [ ] New feature
- [ ] Enhancement
- [x] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
<!-- Describe your changes in detail -->
Moving connectors (NMI,Riskified,and payone) from `router` crate to `hyperswitch_connector` crate
### Additional Changes
- [ ] This PR modifies the API contract
- [ ] This PR modifies the database schema
- [ ] This PR modifies applicat
</think>
To implement this, you'll need to modify:
**Detailed Implementation:**
**Commit 1:** refactor(connector): [NMI,PAYONE,RISKIFIED] moved to hyperswitch_connectors (#7666)
Files to modify:
**crates/hyperswitch_connectors/src/connectors.rs**
Add:
- mod: pub::nmi
- mod: pub::payone
- mod: pub::riskified
**crates/hyperswitch_connectors/src/connectors/riskified/transformers/auth.rs**
Add:
- function: private::try_from
- struct: pub::RiskifiedAuthType
- impl: impl TryFrom<&ConnectorAuthType> for RiskifiedAuthType
**crates/hyperswitch_connectors/src/default_implementations.rs**
Modify existing code
**crates/hyperswitch_connectors/src/default_implementations_v2.rs**
Modify existing code
**crates/hyperswitch_connectors/src/types.rs**
Modify existing code
**crates/hyperswitch_connectors/src/utils.rs**
Add:
- function: private::is_payment_successful
- function: private::get_order_details
- function: private::get_currency
- trait: pub::FrmTransactionRouterDataRequest
- trait: pub::FraudCheckCheckoutRequest
- trait: pub::FraudCheckTransactionRequest
- impl: impl FrmTransactionRouterDataRequest for FrmTransactionRouterData
- impl: impl FraudCheckCheckoutRequest for FraudCheckCheckoutData
- impl: impl FraudCheckTransactionRequest for FraudCheckTransactionData
**crates/router/src/connector.rs**
Remove:
- mod: pub::nmi
- mod: pub::payone
- mod: pub::riskified
**crates/router/src/connector/riskified/transformers/auth.rs**
Remove:
- function: private::try_from
- struct: pub::RiskifiedAuthType
- impl: impl TryFrom<&types::ConnectorAuthType> for RiskifiedAuthType
**crates/router/src/core/payments/flows.rs**
Modify existing code
**crates/router/src/macros.rs**
Modify existing code
|
{"issue_number": 7715, "pr_number": 7666, "commits_count": 1, "files_changed": 20, "response_length": 2525, "file_count": 12, "needs_breakdown": false}
|
fix(user_roles): migrations for backfilling user_roles entity_id
Backfill entity_id with entity_type in user_roles table to avoid dashboard breaking
|
<think>
PR Context:
- Title: fix(user_roles): migrations for backfilling user_roles entity_id
- Merged: 2024-12-16T13:36:14Z
- Files changed: 4 files
- Commits: 3 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [ ] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
<!-- Describe your changes in detail -->
This PR ensures that the entity_id is backfilled in the user_roles table, preventing issues for V1 users when switching organizations and logging in.
### Additional Changes
- [ ] This PR modifies the API contract
- [ ] This PR modifies
</think>
To implement this, you'll need to modify:
(No detailed commit information available)
|
{"issue_number": 6843, "pr_number": 6847, "commits_count": 0, "files_changed": 4, "response_length": 794, "file_count": 0, "needs_breakdown": false}
|
[FIX]: Make v2 endpoints follow standard API conventions
There are a lot of minor inconsistencies in v2 endpoints. Fix them in accordance with https://google.aip.dev/general
|
<think>
PR Context:
- Title: fix(router): Make v2 endpoints follow standard naming conventions
- Merged: 2025-07-21T15:41:20Z
- Files changed: 24 files
- Commits: 6 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [ ] New feature
- [x] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
<!-- Describe your changes in detail -->
- Consistently use kebab case in endpoint URLs
- Use plural form of resources in URLs, i.e. instead of `/v2/organization`, use `/v2/organizations`
Renamed (current version removed) endpoints:
`/v2/organization` -> `/v2/organizations`
`/v
</think>
To implement this, you'll need to modify:
**Detailed Implementation:**
**Commit 1:** fix(router): Make v2 endpoints follow standard naming conventions (#8630)
Co-authored-by: hyperswitc
Files to modify:
**crates/hyperswitch_connectors/src/connectors/hyperswitch_vault.rs**
Modify existing code
**crates/openapi/src/routes/organization.rs**
Modify existing code
**crates/openapi/src/routes/payment_method.rs**
Modify existing code
**crates/openapi/src/routes/refunds.rs**
Modify existing code
**crates/openapi/src/routes/revenue_recovery.rs**
Modify existing code
**crates/openapi/src/routes/routing.rs**
Modify existing code
**crates/router/src/lib.rs**
Modify existing code
**crates/router/src/routes.rs**
Modify existing code
**crates/router/src/routes/app.rs**
Remove:
- struct: pub::User
Add:
- function: pub::server
- function: pub::server
- struct: pub::User
- struct: pub::ProcessTrackerDeprecated
- impl: impl User
- impl: impl ProcessTrackerDeprecated
|
{"issue_number": 8629, "pr_number": 8630, "commits_count": 1, "files_changed": 24, "response_length": 1732, "file_count": 11, "needs_breakdown": false}
|
fix(openapi): Fix broken pages in mintlify (v2)
v2 mintlify docs have several broken pages and some endpoints are missing.
|
<think>
PR Context:
- Title: fix(openapi): Fix broken mintlify pages (v2)
- Merged: 2025-06-20T13:54:03Z
- Files changed: 18 files
- Commits: 4 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [x] Bugfix
- [ ] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [x] Documentation
- [ ] CI/CD
## Description
<!-- Describe your changes in detail -->
Fixed the following mintlify pages:
- `v2/customers/customers--update.mdx`
- `payment-method-session--confirm-a-payment-method-session.mdx`
- `payment-method-session--delete-a-saved-payment-method.mdx`
- `payment-method-session--list-pay
</think>
To implement this, you'll need to modify:
**Detailed Implementation:**
**Commit 1:** fix(openapi): Fix broken mintlify pages (v2) (#8382)
Co-authored-by: hyperswitch-bot[bot] <148525504
Files to modify:
**crates/openapi/src/routes/payments.rs**
Modify existing code
**crates/openapi/src/routes/tokenization.rs**
Modify existing code
|
{"issue_number": 8381, "pr_number": 8382, "commits_count": 1, "files_changed": 18, "response_length": 1032, "file_count": 4, "needs_breakdown": false}
|
Propage request id to chat service
Send request id to chat service in headers.
|
<think>
PR Context:
- Title: fix(chat): append request id to headers for chat request
- Merged: 2025-07-25T07:27:38Z
- Files changed: 4 files
- Commits: 7 commits
Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [x] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
Propagation request-id to chat service for consistency.
Propagate chat session id as well in request
Add count metric for chat api
### Additional Changes
- [ ] This PR modifies the API contract
- [ ] This PR modifies the database schema
- [ ] This PR modifies application c
</think>
To implement this, you'll need to modify:
**Detailed Implementation:**
**Commit 1:** fix(chat): append request id to headers for chat request (#8680)
Files to modify:
**crates/common_utils/src/consts.rs**
Modify existing code
**crates/router/src/core/chat.rs**
Modify existing code
**crates/router/src/routes/chat.rs**
Modify existing code
**crates/router/src/routes/metrics.rs**
Modify existing code
|
{"issue_number": 8679, "pr_number": 8680, "commits_count": 1, "files_changed": 4, "response_length": 1117, "file_count": 6, "needs_breakdown": false}
|
End of preview. Expand
in Data Studio
Rust Commit Dataset - Hyperswitch
Dataset Description
This dataset contains Rust commit messages paired with their corresponding code patches from the Hyperswitch repository.
Dataset Summary
- Total Examples: 231
- Language: Rust
- Source: Hyperswitch GitHub repository
- Format: Prompt-response pairs for supervised fine-tuning (SFT)
Data Fields
prompt: The commit message describing the changeresponse: The git patch/diff showing the actual code changes
Example
{
"prompt": "fix: update payment status handling",
"response": "diff --git a/src/payment.rs b/src/payment.rs\n..."
}
Usage
from datasets import load_dataset
# Load dataset
dataset = load_dataset("archit11/hyperswitch-issue-to-code2")
# Access train/test splits
train_data = dataset['train']
test_data = dataset['test']
# Example
print(train_data[0]['prompt'])
print(train_data[0]['response'])
Training
This dataset is designed for fine-tuning code generation models on Rust commit-to-patch generation tasks.
Example training command:
python train_sft.py \
--dataset archit11/hyperswitch-issue-to-code2 \
--model Qwen/Qwen3-4B \
--output_dir ./qwen-rust-sft \
--use_4bit \
--use_lora
Data Collection
The data was collected using PyDriller and tree-sitter for parsing Rust identifiers:
- Only commits with 20+ lines changed are included
- Rust-specific identifier tracking (functions, structs, enums, traits, impls, modules)
Citation
If you use this dataset, please cite the Hyperswitch repository:
@misc{hyperswitch2024,
title={Hyperswitch},
author={Juspay},
year={2024},
url={https://github.com/juspay/hyperswitch}
}
License
This dataset follows the same license as the Hyperswitch project.
- Downloads last month
- 17