prompt stringlengths 6 90.9k | response stringlengths 121 18.6k | metadata stringlengths 314 42.3k |
|---|---|---|
<!-- Describe your changes in detail -->
Add service details struct in payments request api_model and authentication table for storing service_details during click to pay authentication via unified_authentication_service | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/payments.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/authentication.rs`
- `crates/diesel_models/src/schema.rs`
- `crates/diesel... | {"pr_number": 6757, "pr_title": "feat(core): Add service details field in authentication table", "merged_at": "2024-12-12T12:43:58Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["payment"]}, "hierarchy": {"api_models": ["crates/api_models/src/payments.rs"], "database": ["crates/diesel_mo... |
<!-- Describe your changes in detail -->
Reverts https://github.com/juspay/hyperswitch/pull/7921 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payments.rs`
**Detailed Identifier Changes:**
Commit e902d6d9:
Files to modify:
**crates/router/src/core/payments.rs**
Modify existing code | {"pr_number": 8207, "pr_title": "revert(routing): Add connectors from current active routing algorithm before adding fallback connectors", "merged_at": "2025-06-04T16:36:28Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_busin... |
<!-- Describe your changes in detail -->
A new type has been added to the domain models called `Address`. This type has been used in the application everywhere where we use address.
<!--
Provide links to the files with corresponding changes.
Following are the paths where you can find config files:
1. `confi... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/payments.rs`
**2. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/address.rs`
- `crates/hyperswitch_domain_models/src/paym... | {"pr_number": 6608, "pr_title": "refactor(address): change address to domain address in application", "merged_at": "2024-12-04T10:10:37Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/payments.r... |
<!-- Describe your changes in detail -->
This pr refactors the relay flow to add trait based implementation for it.
Changes made:-
1. `relay_flow_decider` decides the relay flow based on the relay types
2. Introduced `RelayInterface` trait that consists the methods required for different relay types
a. `vali... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/relay.rs`
**2. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/merchant_connector_account.rs`
- `crates/hyperswitch_domain... | {"pr_number": 7264, "pr_title": "refactor(relay): add trait based implementation for relay", "merged_at": "2025-03-03T07:59:12Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "refund", "connector"]}, "hierarchy": {"api_models": ["crates/api_models/src/relay.rs"], "domain"... |
Fixed the IataPay Cypress test cases as UPI_Collect payments were failing due to an invalid billing.address.country. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `cypress-tests/cypress/e2e/configs/Payment/Iatapay.js`
- `cypress-tests/cypress/e2e/spec/Payment/00022-Variations.cy.js`
**Code Patterns Applied:**
- Extend existing types with new fields (11 changes)
... | {"pr_number": 7698, "pr_title": "ci(cypress): fix iatapay upi payments", "merged_at": "2025-04-03T06:47:38Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user"]}, "hierarchy": {"tests": ["cypress-tests/cypress/e2e/configs/Payment/Iatapay.js", "cypress-tests/cypress/e2e/... |
<!-- Describe your changes in detail -->
PR : #[8238](https://github.com/juspay/hyperswitch/pull/8238) calls for a env variable before the .env file is sourced in the scripts/setup.sh file.
This PR fixes the above mentioned issue and handles the health checks using flags instead of exit codes, enabling the script to ... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Other**
- `scripts/setup.sh`
**Code Patterns Applied:**
- Add conditional logic for feature flags or filtering (1 changes) | {"pr_number": 8320, "pr_title": "fix: correct error for env not found", "merged_at": "2025-06-16T13:09:15Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"other": ["scripts/setup.sh"]}, "change_types": {"conditionals_added": 1}, "has_identifier_data": false, ... |
<!-- Describe your changes in detail -->
add capability to force challenge for 3DS Payments through Netcetera and send few optional fields
1. Profile level enablement `force_3ds_challenge` which would request netcetera for challenge flow
2. Send few optional fields like trans_type, which can potentially be require... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/admin.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/business_profile.rs`
- `crates/diesel_models/src/schema.rs`
- `crates/d... | {"pr_number": 7449, "pr_title": "feat(router): add capability to force challenge for 3DS Payments through Netcetera and send few optional fields ", "merged_at": "2025-03-06T14:29:40Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user", "connector"]}, "hierarchy": {"api_... |
<!-- Describe your changes in detail -->
This will handel the cases for constraint_graph for PML where setup_future_usage is not passed in payments. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payment_methods/cards.rs` | {"pr_number": 6810, "pr_title": "refactor(constraint_graph): handle PML for cases where setup_future_usage is not passed in payments", "merged_at": "2024-12-17T11:45:55Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business"... |
Added the testcases for unified error code and error message for stripe and adyen connector. And added failure payments testcases.
## How did you test it?
Stripe
<img width="729" alt="Screenshot 2024-12-10 at 7 58 49 PM" src="https://github.com/user-attachments/assets/1b7cc860-4d07-4891-b839-08749bb850d0">
... | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. Tests**
- `cypress-tests/cypress/e2e/PaymentTest/00022-Variations.cy.js`
- `cypress-tests/cypress/e2e/PaymentUtils/Adyen.js`
- `cypress-tests/cypress/e2e/PaymentUtils/Commons.js`
- ... and 1 more files
**Code Pa... | {"pr_number": 6796, "pr_title": "ci(cypress): Add testcases for unified error code and message", "merged_at": "2024-12-13T08:25:47Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["payment", "user", "connector"]}, "hierarchy": {"tests": ["cypress-tests/cypress/e2e/PaymentTest/00022-Variati... |
This PR removes any non mandatory fields from AdyenPlatform connector for card and SEPA payouts.
New list
- Card payouts
[payout_method_data.card.card_number](https://api-reference.hyperswitch.io/v1/payouts/payouts--create#body-payout-method-data-card-card-number)
[payout_method_data.card.expiry_month](https://... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/adyenplatform/transformers/payouts.rs`
**2. Configuration Files**
- `crates/router/src/configs/defaults/payout_required_fields.rs`... | {"pr_number": 8990, "pr_title": "refactor(connector): [AdyenPlatform] update required fields", "merged_at": "2025-08-19T11:08:21Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "merchant", "order"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connect... |
<!-- Describe your changes in detail -->
Add RSA SHA 256 source verification for webhook in Wise | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/wise.rs`
**Code Patterns Applied:**
- Implement new functions (4 changes)
- Extend existing types with new fields (4 changes) | {"pr_number": 9100, "pr_title": "feat(connector): [Wise] Add webhook source verification", "merged_at": "2025-08-29T13:57:04Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["merchant", "user", "webhook"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors/wi... |
Added comprehensive XSS (Cross-Site Scripting) and SQLi protection to dashboard metadata fields. Implemented a new `SafeString` type wrapper that validates input against XSS attacks during JSON deserialization.
**Dependencies Added**
- `ammonia = "3.3"` - HTML sanitization library
- `urlencoding = "2.1.3"` - URL d... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/user/dashboard_metadata.rs`
**2. Core Business Logic**
- `crates/router/src/core/user/dashboard_metadata.rs`
**3. Type Definitions**
- `crates/common_ty... | {"pr_number": 9104, "pr_title": "feat(security): add XSS and sqli validation for dashboard metadata fields", "merged_at": "2025-10-01T08:31:43Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"api_models": ["crates/api_models/src/user/dashboard_metadata.rs"], "core_... |
<!-- Describe your changes in detail -->
Hotfix for https://github.com/juspay/hyperswitch/pull/7828
Authentication with Netcetera was successful, but authorization with Cybersource failed with the below error:
Declined - The request is missing one or more fields, detailed_error_information: paymentInformation.card... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/cybersource/transformers.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (2 changes)
**Detailed Identifier Ch... | {"pr_number": 7840, "pr_title": "fix(connector): [Cybersource] send type selection indicator for co-batch cards", "merged_at": "2025-04-17T11:32:15Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "user"]}, "hierarchy": {"connectors": ["crates/hyperswitch_conne... |
<!-- Describe your changes in detail -->
the problem is that we previously extracted `nonce` instead of `signature` and entire regex match instead of `nonce`. this pr fixes webhook source verification for nmi connector by properly extracting `signature` (`2`) and `nonce` (`1`) values.
check attached issue for det... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/nmi.rs`
**Code Patterns Applied:** | {"pr_number": 8946, "pr_title": "fix(connector): [nmi] webhook source verification", "merged_at": "2025-08-13T15:58:58Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors/nmi.... |
<!-- Describe your changes in detail -->
1)Added Mandate flow for Paybox
2) Added a new field `additional_payment_method_data` in PaymentsAuthorizeData type
3) Added `connector_mandate_request_reference_id` in RouterData | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/payments.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/payment_attempt.rs`
**3. Domain Models (Business Logic Types)**
- `cra... | {"pr_number": 6378, "pr_title": "feat(connector): [Paybox] Add mandates Flow for Paybox", "merged_at": "2024-10-30T16:38:12Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/payments.rs"], "databa... |
<!-- Describe your changes in detail -->
This pull request includes changes to enhance the handling of billing and shipping address requirements for Samsung Pay and Google Pay session tokens. The most important changes include adding new fields to the `SamsungPaySessionTokenResponse` struct, updating the `create_samsu... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/payments.rs`
**2. Core Business Logic**
- `crates/router/src/core/payments/flows/session_flow.rs`
**3. Other**
- `api-reference-v2/openapi_spec.json`
... | {"pr_number": 7320, "pr_title": "feat(samsung_pay): collect customer address details form Samsung Pay based on business profile config and connector required fields", "merged_at": "2025-02-22T08:38:20Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]... |
<!-- Describe your changes in detail -->
this pr introduces apple pay hyperswitch decryption flow (simplified and manual) and predecrypt flow to tesouro connector.
connector does not support connector decryption flow. so, we throw an error in that case stating decrypted data is missing.
tesouro does not have any r... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/connector_configs/toml/development.toml`
- `crates/connector_configs/toml/production.toml`
- `crates/connector_configs/toml/sandbox.toml`
- ... and 2 more files
*... | {"pr_number": 9648, "pr_title": "feat(connector): [tesouro] apple pay", "merged_at": "2025-10-07T08:22:58Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/connector_configs/toml/development.toml", "crates/conne... |
<!-- Describe your changes in detail -->
- Added `customer_id` as a filter for payment intents
- Added `payment_processed_amount` metric for `payment_intents` table | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/analytics/payment_intents.rs`
**2. Database Layer (Queries & Schema)**
- `crates/analytics/src/query.rs`
**3. Core Business Logic**
- `crates/analytics/... | {"pr_number": 6344, "pr_title": "feat(analytics): add `customer_id` as filter for payment intents", "merged_at": "2024-10-30T10:11:12Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "user"]}, "hierarchy": {"api_models": ["crates/api_models/src/analytics/paymen... |
<!-- Describe your changes in detail -->
This PR introduces 2 new features:
- Multiple credentials for a connector
- Configuration flags
closes #6645 (check this issue for detailed documentation / flow / explanation) | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Utils**
- `cypress-tests/cypress/utils/featureFlags.js`
**2. Tests**
- `.github/workflows/cypress-tests-runner.yml`
- `cypress-tests/.gitignore`
- `cypress-tests/.prettierrc`
- ... and 64 more files
**... | {"pr_number": 6588, "pr_title": "feat(cypress): add multiple creds and flags support", "merged_at": "2024-12-03T11:39:21Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user", "refund", "connector"]}, "hierarchy": {"utils": ["cypress-tests/cypress/utils/featureFlags.js"], "tests": ... |
<!-- Describe your changes in detail -->
Update production endpoint for connector Airwallex (https://api.airwallex.com/) | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Configuration Files**
- `config/deployments/production.toml` | {"pr_number": 6632, "pr_title": "feat(connector): [AIRWALLEX] Update production endpoint", "merged_at": "2024-11-21T21:06:12Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["connector"]}, "hierarchy": {"config": ["config/deployments/production.toml"]}, "change_types": {}, "has_ident... |
<!-- Describe your changes in detail -->
Added `psp_tokenization_enabled` field to `CustomerPaymentMethod` that denotes whether `psp_tokenization` is enabled for a saved payment method | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/admin.rs`
- `crates/api_models/src/payment_methods.rs`
**2. Core Business Logic**
- `crates/router/src/core/payment_methods/transformers.rs`
**3. Other*... | {"pr_number": 7519, "pr_title": "feat(router): Return psp_tokenization_enabled in Customer PML", "merged_at": "2025-03-20T10:04:56Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/admin.rs", "cra... |
Add Phonepe, Paytm supported payment methods, currencies and countries in feature matrix. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/paytm.rs`
- `crates/hyperswitch_connectors/src/connectors/phonepe.rs`
**Code Patterns Applied:**
- Extend existing types with new ... | {"pr_number": 8822, "pr_title": "feat(feature_matrix): add feature matrix for both paytm and phonepe", "merged_at": "2025-08-04T07:49:08Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user", "refund"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/con... |
<!-- Describe your changes in detail -->
1) Add Response Redirection URL for PopupURL Next Action
2) Accept Empty Metadata for Adyen
3) Fix Coinbase Connector Config | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/payments.rs`
**2. Core Business Logic**
- `crates/router/src/core/payments.rs`
- `crates/router/src/core/payments/transformers.rs`
**3. External Connect... | {"pr_number": 8257, "pr_title": "fix(connector): Add RedirectInsidePopup response redirection URL", "merged_at": "2025-06-10T17:51:53Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/payments.rs"... |
Added PML test for Novalnet | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `cypress-tests/cypress/e2e/PaymentMethodListTest/00000-PaymentMethodListTests.cy.js`
- `cypress-tests/cypress/e2e/PaymentMethodListUtils/Commons.js`
- `cypress-tests/cypress/e2e/PaymentMethodListUtil... | {"pr_number": 6544, "pr_title": "Ci(Cypress): Add PML test and Dynamic Fields Test for Novalnet", "merged_at": "2025-01-06T07:27:36Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user"]}, "hierarchy": {"tests": ["cypress-tests/cypress/e2e/PaymentMethodListTest/00000-Pay... |
<!-- Describe your changes in detail -->
template for Tokenex integration | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/connector_endpoints.rs`
**2. External Connector Integration**
- `crates/common_enums/src/connector_enums.rs`
- `crates/connector_... | {"pr_number": 9416, "pr_title": "feat(connector): [Tokenex] add template code", "merged_at": "2025-09-22T10:01:50Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["token"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/connector_endpoints.rs"], "connectors": ["crate... |
Connector template code for new connector silverflow. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/configs.rs`
**2. External Connector Integration**
- `crates/connector_configs/src/connector.rs`
- `crates/connector_configs/toml/... | {"pr_number": 8553, "pr_title": "feat(connector): [silverflow] template code", "merged_at": "2025-07-08T08:39:05Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["connector"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/configs.rs"], "connectors": ["crates/connect... |
Hotfix for https://github.com/juspay/hyperswitch/pull/9508 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/webhooks/incoming.rs` | {"pr_number": 9530, "pr_title": "fix(webhooks): move webhook acknowledge config to cover early deserialization errors", "merged_at": "2025-09-24T05:41:00Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"core_business": ["crates/router/src/core/webhooks/incoming.rs"... |
<!-- Describe your changes in detail -->
Add PLN to the currency config of card, googlepay and applepay via Cybersource.
## Test Case
1) Do a googlepay payment via PLN cybersource
```
curl --location 'http://localhost:8080/payments' \
--header 'Content-Type: application/json' \
--header 'Accept: application/js... | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. Tests**
- `config/deployments/integration_test.toml`
**2. Configuration Files**
- `config/config.example.toml`
- `config/deployments/production.toml`
- `config/deployments/sandbox.toml`
- ... and 2 more files | {"pr_number": 6628, "pr_title": "feat(router): [Cybersource] add PLN to the currency config", "merged_at": "2024-11-26T12:02:00Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"tests": ["config/deployments/integration_test.toml"], "config... |
<!-- Describe your changes in detail -->
Changed required value for juspayThreedsserver config
## How did you test it?
<!--
Did you write an integration/unit/API test to verify the code changes?
Or did you test this change manually (provide relevant screenshots)?
-->
<img width="948" height="175" alt="Screen... | To implement this **connector_integration** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/connector_configs/toml/development.toml`
- `crates/connector_configs/toml/production.toml`
- `crates/connector_configs/toml/sandbox.toml` | {"pr_number": 8890, "pr_title": "fix(authentication): changed required value for juspayThreedsserver config", "merged_at": "2025-08-20T09:49:22Z", "intent": {"feature_type": "connector_integration", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"connectors": ["crates/connector_configs/toml/development.t... |
Hotfix for [PR](https://github.com/juspay/hyperswitch/pull/7623)
`cargo clippy output`
<img width="1098" alt="Screenshot 2025-03-25 at 4 24 55 PM" src="https://github.com/user-attachments/assets/7bfec754-cafb-4e58-b21c-05a96542eb95" /> | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/cybersource/transformers.rs` | {"pr_number": 7625, "pr_title": "fix(connector): [CYBERSOURCE] change ucaf_collection_indicator for mastercard payments via netcetera", "merged_at": "2025-03-25T11:20:23Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"connectors": ["crates/hyperswitch_conne... |
<!-- Describe your changes in detail -->
flattened paymentData in authentication trait functions | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/authentication.rs`
**2. Core Business Logic**
- `crates/router/src/core/payments.rs`
- `crates/router/src/core/payments/operations/payment_confirm.rs`
- `cr... | {"pr_number": 8365, "pr_title": "refactor(authentication): flattened paymentData in authentication trait functions", "merged_at": "2025-07-01T13:52:12Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/a... |
Reverts | To implement this **unknown** feature, you'll need to modify these architectural layers:
**1. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/authentication.rs`
**2. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/router_request_types/authentication.rs`
- `crat... | {"pr_number": 8021, "pr_title": "refactor(authentication): moved cavv storing from table to temp locker", "merged_at": "2025-05-14T07:50:11Z", "intent": {"feature_type": "unknown", "action": "unknown", "entities": []}, "hierarchy": {"database": ["crates/diesel_models/src/authentication.rs"], "domain": ["crates/hyperswi... |
<!-- Describe your changes in detail -->
Replace their vantiv's open sandbox url `: https://www.testvantivcnp.com/sandbox/communicator/online` with pre-live url
`https://payments.vantivprelive.com/vap/communicator/online` and fix typo
## How did you test it?
<!--
Did you write an integration/unit/API test to... | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/worldpayvantiv/transformers.rs`
**2. Tests**
- `config/deployments/integration_test.toml`
- `loadtest/config/development.toml`
**3. ... | {"pr_number": 8286, "pr_title": "refactor(connectors): [worldpayvantiv] replace sandbox url with pre-live url and fix typo", "merged_at": "2025-06-10T12:44:54Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["payment"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/conne... |
This pull request introduces a new helper function to update the default fallback connector configuration whenever a merchant connector account (MCA) is updated. This ensures that changes to connector status (such as disabling or enabling) are accurately reflected in both merchant and profile configurations. The change... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/admin.rs`
- `crates/router/src/core/routing.rs`
- `crates/router/src/core/routing/helpers.rs`
**Code Patterns Applied:**
- Implement new functions (2 changes)
-... | {"pr_number": 9659, "pr_title": "refactor(routing): update configs on updation of mca", "merged_at": "2025-10-07T16:53:24Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["merchant", "connector"]}, "hierarchy": {"core_business": ["crates/router/src/core/admin.rs", "crates/router/src/... |
<!-- Describe your changes in detail -->
Once the open router call is completed for the co-badged card lookup in a debit routing flow, it returns all the debit networks eligible for the card. These networks must be validated against the merchant-enabled debit networks for each merchant connector account.
This PR ad... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/debit_routing.rs`
**Code Patterns Applied:**
- Implement new functions (7 changes)
- Extend existing types with new fields (26 changes)
- Add conditional logic for fe... | {"pr_number": 8175, "pr_title": "refactor(debit_routing): filter debit networks based on merchant connector account configuration", "merged_at": "2025-06-12T13:15:05Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": [... |
<!-- Describe your changes in detail -->
Modified the v1 merchant list query to list only v1 merchant accounts, v2 merchants cannot deserialize in v1 application code.
This change is required, since now, both v1 and v2 merchant accounts are stored in the same schema.
This will affect the following flows:
- list... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/query/merchant_account.rs`
**Code Patterns Applied:**
- Modify database queries (3 changes) | {"pr_number": 7782, "pr_title": "refactor(users): modify query to list only v1 merchant_accounts for list v1 merchant accounts API", "merged_at": "2025-04-10T10:14:36Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["merchant", "user", "token"]}, "hierarchy": {"database": ["crates/di... |
<!-- Describe your changes in detail -->
Add click to pay and unified authentication service integration in core
## How did you test it?
<!--
Did you write an integration/unit/API test to verify the code changes?
Or did you test this change manually (provide relevant screenshots)?
-->
check payments sanity... | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/connector_enums.rs`
**2. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/payment_method_data.rs`
- `crates/hyperswitch_domain_mo... | {"pr_number": 6769, "pr_title": "feat(core): Add click to pay support in hyperswitch", "merged_at": "2024-12-16T14:25:44Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/connector_enums.rs"], "domain":... |
<!-- Describe your changes in detail -->
This PR
1. Adds payment method display name to feature matrix response
2. Replace the 2 digit country codes into 3 digit country codes
## How did you test it?
<!--
Did you write an integration/unit/API test to verify the code changes?
Or did you test this change manua... | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/feature_matrix.rs`
**2. Other**
- `api-reference-v2/openapi_spec.json`
- `api-reference/openapi_spec.json`
- `crates/common_enums/src/enums.rs`
- ... and... | {"pr_number": 7639, "pr_title": "feat(router): add payment method display name to feature matrix response", "merged_at": "2025-04-01T12:15:42Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["payment", "merchant", "refund"]}, "hierarchy": {"api_models": ["crates/api_models/src/feature_matr... |
implement payouts for Loonio | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/enums.rs`
- `crates/api_models/src/payouts.rs`
**2. Core Business Logic**
- `crates/router/src/core/payment_methods/cards.rs`
- `crates/router/src/cor... | {"pr_number": 9718, "pr_title": "feat(connector): [Loonio] implement payouts", "merged_at": "2025-10-08T16:47:56Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "merchant", "order"]}, "hierarchy": {"api_models": ["crates/api_models/src/enums.rs", "crates/api_models/src/p... |
1. Added supported currencies for novalnet
2. Removed browser info from required fields for novalnet | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/enums.rs`
**2. External Connector Integration**
- `crates/router/src/configs/defaults/payment_connector_required_fields.rs`
**3. Tests**
- `config/deplo... | {"pr_number": 6547, "pr_title": "feat(connector): [Novalnet] Add supported currencies", "merged_at": "2024-11-14T11:45:12Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["card"]}, "hierarchy": {"api_models": ["crates/api_models/src/enums.rs"], "connectors": ["crates/router/src/confi... |
This PR introduces UI revamps to the payment links by including below changes - (described in #6711)
- Introduce `branding_visibility` in business profile's payment link config
- Introduce `details_layout` and `background_image` in both business profile and payments create API
- Consume these values in payment link'... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/admin.rs`
- `crates/api_models/src/payments.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/business_profile.rs`
- `crates/di... | {"pr_number": 6725, "pr_title": "feat(core): payment links - add support for custom background image and layout in details section", "merged_at": "2024-12-12T15:48:18Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["c... |
<!-- Describe your changes in detail -->
Added validation check for amount in capture flow.
Fixed WASM for Peachpayments | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payments/helpers.rs`
**2. External Connector Integration**
- `crates/connector_configs/src/connector.rs`
- `crates/connector_configs/toml/development.toml`
-... | {"pr_number": 9434, "pr_title": "fix(core): Add Validation Check for Amount in Capture Flow", "merged_at": "2025-09-19T07:35:05Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user"]}, "hierarchy": {"core_business": ["crates/router/src/core/payments/helpers.rs"], "connec... |
<!-- Describe your changes in detail -->
main PR
https://github.com/juspay/hyperswitch/pull/7978
https://github.com/juspay/hyperswitch/pull/8035
## How did you test it?
<!--
Did you write an integration/unit/API test to verify the code changes?
Or did you test this change manually (provide relevant screens... | To implement this **connector_integration** feature, you'll need to modify these architectural layers:
**1. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/authentication.rs`
**2. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/router_request_types/authentication.... | {"pr_number": 8043, "pr_title": "refactor(authentication): moved cavv storing from table to temp locker", "merged_at": "2025-05-15T13:07:06Z", "intent": {"feature_type": "connector_integration", "action": "add_feature", "entities": []}, "hierarchy": {"database": ["crates/diesel_models/src/authentication.rs"], "domain":... |
<!-- Describe your changes in detail -->
Add support for record back flow for chargebee.
**What is record back flow ?**
After payment is retried by revenue recovery, we need to update the billing processor invoice.
Chargebee flow
We record the transaction in chargebee created by internal system. This transact... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/router_flow_types/revenue_recovery.rs`
**2. Core Business Logic**
- `crates/router/src/core/admin.rs`
- `crates/router/src/core/p... | {"pr_number": 7505, "pr_title": "feat(connector): [Chargebee] Add record back support for chargebee [V2]", "merged_at": "2025-03-18T13:16:25Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "transaction"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/rou... |
<!-- Describe your changes in detail -->
added support for fetching multiple keys for redis cluster.
Earlier, we were using `mget` to fetch multiple keys. While this works fine for standalone redis, it would fail for redis cluster(it won't work if redis keys are stored in multiple hash slots).
So, introduced a... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Other**
- `crates/redis_interface/src/commands.rs`
- `crates/redis_interface/src/lib.rs`
**Code Patterns Applied:**
- Implement new functions (4 changes)
- Extend existing types with new fields (8 changes)
- Add... | {"pr_number": 9019, "pr_title": "fix(redis): add support for fetching multiple keys for redis cluster", "merged_at": "2025-08-22T14:07:12Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"other": ["crates/redis_interface/src/commands.rs", "crates/redis_interface/src... |
<!-- Describe your changes in detail -->
Added comprehensive event logging for UCS operations to improve debugging and monitoring. The changes wrap UCS calls with structured logging that captures request/response data, timing, and errors across all payment flows. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payments/flows/authorize_flow.rs`
- `crates/router/src/core/payments/flows/external_proxy_flow.rs`
- `crates/router/src/core/payments/flows/psync_flow.rs`
- .... | {"pr_number": 9058, "pr_title": "feat(ucs): add event logging for UCS operations", "merged_at": "2025-09-02T08:13:26Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core/payments/flows/authorize_... |
<!-- Describe your changes in detail -->
This is continuation on this PR.
https://github.com/juspay/hyperswitch/pull/6607
Changes in this PR:
In this PR, I've added support for sending the request_extended_authorization flag to the connector module from core. And handling the response from the connector and upd... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/admin.rs`
- `crates/api_models/src/payments.rs`
- `crates/api_models/src/payments/trait_impls.rs`
**2. Database Layer (Queries & Schema)**
- `crates/d... | {"pr_number": 6766, "pr_title": "feat: core changes for extended authorization", "merged_at": "2025-03-21T12:57:19Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/admin.rs", "crates/api_models/s... |
<!-- Describe your changes in detail -->
Connector template code for new connector breadpay. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/connector_endpoints.rs`
**2. External Connector Integration**
- `crates/connector_configs/src/connector.rs`
- `crates/connector_c... | {"pr_number": 8655, "pr_title": "feat(connector): Add template code for breadpay", "merged_at": "2025-07-22T08:52:52Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["connector"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/connector_endpoints.rs"], "connectors": ... |
<!-- Describe your changes in detail -->
Hotfix for [PR](https://github.com/juspay/hyperswitch/pull/8518) | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/cybersource/transformers.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (8 changes)
- Add conditional logic f... | {"pr_number": 8541, "pr_title": "fix(connector): [CYBERSOURCE] Passing pares_status for MasterCard & Visa and transaction_type field", "merged_at": "2025-07-03T10:34:09Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/sr... |
The OrderId field in Nexixpay request is limited to 18 characters in size.
Along with that added validation checks for fields inside shipping and billing addresses. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/errors/api_error_response.rs`
**2. Core Business Logic**
- `crates/router/src/core/errors/utils.rs`
**3. External Connector Integra... | {"pr_number": 8345, "pr_title": "fix(connector): [NEXIXPAY] Add Validation Checks for Request Fields", "merged_at": "2025-06-23T10:09:18Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/sr... |
`payment_information.tokenized_card.transaction_type` should be 3 for GPay, APay and SamsungPay MIT payments via Cybersource, and 1 for all other cases.
Some parts of the Cybersource transformer file were missing this logic. This PR fixes those gaps. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/cybersource/transformers.rs`
**Code Patterns Applied:**
- Define new data structures (2 changes)
- Extend existing types with new fie... | {"pr_number": 9071, "pr_title": "fix(connector): [CYBERSOURCE] Fix transaction_type for Googlepay payments", "merged_at": "2025-08-28T12:39:03Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connec... |
<!-- Describe your changes in detail -->
- create a temporary payment_token for session confirm call and pass it in the response
- the payment_token is created against the payment_method_id and is saved in redis
- payment can be done using the payment_token generated by session confirm for the payment_method_data | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/payment_methods.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/payment_methods_session.rs`
**3. Domain Models (Business Logic Typ... | {"pr_number": 8391, "pr_title": "feat(payment-method): create payment_token for session confirm call", "merged_at": "2025-06-19T13:53:36Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "session", "token"]}, "hierarchy": {"api_models": ["crates/api_models/src/payment_metho... |
<!-- Describe your changes in detail -->
Data poi
nt related to Revenue Recovery
- There is a maximum limit on how much time we can do a retry, this limit is fixed by card network.
- What will be the maximum limit for other payment methods?
- `max_retry_count_by_network` refers to maximum limit.
- where can w... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/admin.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/merchant_connector_account.rs`
- `crates/diesel_models/src/schema_v2.rs`
... | {"pr_number": 7144, "pr_title": "refactor(router): add feature_metadata for merchant_connector_account create v2 flow", "merged_at": "2025-02-10T12:55:08Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "connector"]}, "hierarchy": {"api_models": ["crates/api_mo... |
<!-- Describe your changes in detail -->
Template PR for TOkenio | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/configs.rs`
**2. Core Business Logic**
- `crates/router/src/core/admin.rs`
**3. External Connector Integration**
- `crates/commo... | {"pr_number": 8095, "pr_title": "feat(tokenio): Add Template PR", "merged_at": "2025-05-23T09:40:21Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["token"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/configs.rs"], "core_business": ["crates/router/src/core/admin... |
Reverts juspay/hyperswitch#7832 | To implement this **unknown** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/noon.rs`
- `crates/hyperswitch_connectors/src/connectors/noon/transformers.rs`
**Code Patterns Applied:**
- Define new data structures (... | {"pr_number": 7859, "pr_title": "revert: fix(connector): [noon] address `next_action_url` being `null` for cards in 3ds payment", "merged_at": "2025-04-21T17:24:14Z", "intent": {"feature_type": "unknown", "action": "unknown", "entities": []}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors/no... |
<!-- Describe your changes in detail -->
This PR adds the following rule to `.gitattributes` to ensure `.patch` files always use LF line endings, regardless of developer OS:
```gitattributes
*.patch text eol=lf
```
This rule overrides Windows’ default `core.autocrlf` behavior and prevents errors during migra... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Other**
- `.gitattributes` | {"pr_number": 9333, "pr_title": "fix(gitattributes): enforce LF for `.patch` files to avoid CRLF parsing errors on Windows", "merged_at": "2025-09-17T10:03:30Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"other": [".gitattributes"]}, "change_types": {}, "has_ide... |
<!-- Describe your changes in detail -->
Need to make unused fields in novalnet refund response as optional. This will prevent the deserialization errors.
It's a configuration done on Novalnet side, only available in prod. Cannot test this specific case in sandbox. cc: @kashif-m | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/novalnet/transformers.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (2 changes) | {"pr_number": 7721, "pr_title": "fix(connector): [Novalnet] handle refund failure response in novalnet", "merged_at": "2025-04-06T12:25:39Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "refund"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/s... |
Fixed the wellsfargo cypress test
## How did you test it?
<img width="482" alt="Screenshot 2025-07-01 at 7 26 17 PM" src="https://github.com/user-attachments/assets/863ea827-7e79-438d-9e64-ffd485241b1b" />
Failure Reason:
3ds payments silently falling back to no-3ds(Should throw validation)
## Checklist
... | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. Tests**
- `cypress-tests/cypress/e2e/configs/Payment/Utils.js`
- `cypress-tests/cypress/e2e/configs/Payment/WellsFargo.js`
**Code Patterns Applied:**
- Extend existing types with new fields (120 changes) | {"pr_number": 8513, "pr_title": "ci(cypress): Fix wellsfargo test", "merged_at": "2025-07-02T10:33:27Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["payment", "user"]}, "hierarchy": {"tests": ["cypress-tests/cypress/e2e/configs/Payment/Utils.js", "cypress-tests/cypress/e2e/configs/Payme... |
<!-- Describe your changes in detail -->
This PR updates the production endpoint url environment value for GlobalPay while fixing minor inconsistencies | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/globalpay.rs`
**2. Configuration Files**
- `config/deployments/production.toml`
**3. Other**
- `api-reference-v2/openapi_spec.... | {"pr_number": 7588, "pr_title": "chore: update production endpoint url for globalPay", "merged_at": "2025-03-24T08:11:04Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors/globalpay.rs"], "config": ["config/... |
<!-- Describe your changes in detail -->
The payment flow starts in call_connector_service()
**1. Determining Unified Connector Service Eligibility:**
The flow starts with `should_call_unified_connector_service()` which determines if a payment should be routed through the unified connector service.
The func... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core.rs`
- `crates/router/src/core/fraud_check/flows/checkout_flow.rs`
- `crates/router/src/core/fraud_check/flows/record_return.rs`
- ... and 21 more files
**2. ... | {"pr_number": 8280, "pr_title": "feat(core): Hyperswitch <|> UCS Integration", "merged_at": "2025-07-04T17:42:01Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core.rs", "crates/router/src/core/... |
Add connector template code for Paysafe | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/connector_endpoints.rs`
**2. External Connector Integration**
- `crates/connector_configs/src/connector.rs`
- `crates/connector_c... | {"pr_number": 9011, "pr_title": "feat(connector): [Paysafe] add connector template code", "merged_at": "2025-08-26T07:01:33Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["connector"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/connector_endpoints.rs"], "connec... |
<!-- Describe your changes in detail -->
1. Move the Customer db to storage_impl and its interface to hyperswitch_domain_model
2. Added resource handling implementations in KVRouterStore, RouterStore, With this support all the resource handlers can now directly call these generic functions instead of handling the m... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/customer.rs`
**2. Other**
- `crates/router/src/db.rs`
- `crates/router/src/db/customers.rs`
- `crates/router/src/db/kafka_stor... | {"pr_number": 7538, "pr_title": "refactor(customer): refactor customer db with storage utils and move trait to domain_models and impl to storage_model", "merged_at": "2025-04-15T07:54:33Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy"... |
Hotfix for https://github.com/juspay/hyperswitch/pull/8473 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/payment_methods.rs`
**2. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/lib.rs`
- `crates/hyperswitch_domain_models/src/p... | {"pr_number": 8552, "pr_title": "feat(data-migration): add connector customer and mandate details support for multiple profiles", "merged_at": "2025-07-08T08:54:11Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"api_models": ["crates/api_models/src/payment_methods... |
<!-- Describe your changes in detail -->
Throw unsupported error incase of 3DS cards and in the BOA payment request, limit administrative area length to 20 characters .
## How did you test it?
<!--
Did you write an integration/unit/API test to verify the code changes?
Or did you test this change manually (provid... | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/bankofamerica/transformers.rs`
**2. Tests**
- `cypress-tests/cypress/e2e/configs/Payment/BankOfAmerica.js`
**Code Patterns Applied:**
-... | {"pr_number": 7174, "pr_title": "fix(connector): [BOA] throw unsupported error incase of 3DS cards and limit administrative area length to 20 characters ", "merged_at": "2025-02-05T14:21:55Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {... |
<!-- Describe your changes in detail -->
ORIGINAL PR: https://github.com/juspay/hyperswitch/pull/7591
Pass email in payment request body of Braintree as it is mandatory field for sending receipts in braintree | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/braintree/transformers.rs`
**Code Patterns Applied:**
- Define new data structures (1 changes)
- Extend existing types with new field... | {"pr_number": 7617, "pr_title": "refactor(connector): [BRAINTREE] Pass email in payment requests", "merged_at": "2025-03-25T10:47:02Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/c... |
<!-- Describe your changes in detail -->
this pr addresses the comments which is concerned about reducing repeated code by moving them into a separate function within impl block. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/mandate.rs`
**2. Type Definitions**
- `crates/router/src/types/api/mandates.rs`
**3. Other**
- `crates/router/src/db/mandate.rs`
**Code Patter... | {"pr_number": 8772, "pr_title": "refactor(mandate): move repeated code to a separate function within Mandate impl", "merged_at": "2025-08-01T12:59:37Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"database": ["crates/diesel_models/src/mandate.rs"], "types": ["cra... |
hotfix for https://github.com/juspay/hyperswitch/pull/6745 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payment_link/locale.js`
**Code Patterns Applied:**
- Extend existing types with new fields (30 changes) | {"pr_number": 6765, "pr_title": "feat(payments): [Payment links] Add support for traditional chinese locale for payment links", "merged_at": "2024-12-06T11:46:05Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"core_business": ["crates/router/src/core/payment_link/... |
Removed the unused variable declaration from the cy.get("body").then(...) callback.
## Motivation and Context
This change is made to resolve CI check failures related to Cypress linting rules.
## How did you test it?
No additional testing was required as the CI checks passed successfully, confirming complia... | To implement this **webhook** feature, you'll need to modify these architectural layers:
**1. Tests**
- `cypress-tests/cypress/support/redirectionHandler.js` | {"pr_number": 8011, "pr_title": "ci(cypress): Address lints", "merged_at": "2025-05-14T18:11:47Z", "intent": {"feature_type": "webhook", "action": "add_feature", "entities": []}, "hierarchy": {"tests": ["cypress-tests/cypress/support/redirectionHandler.js"]}, "change_types": {}, "has_identifier_data": false, "commits_m... |
Updated the currency and country code for the following connectors :
[Checkout](https://www.checkout.com/docs/developer-resources/codes/currency-codes), [BlueSnap](https://support.bluesnap.com/docs/currencies), [Nuvei](https://docs.nuvei.com/documentation/additional-links/country-and-currency-codes/#currency-codes), ... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `config/deployments/integration_test.toml`
- `loadtest/config/development.toml`
**2. Configuration Files**
- `config/config.example.toml`
- `config/deployments/production.toml`
- `config/deplo... | {"pr_number": 8383, "pr_title": "feat(connector): Added Supported Country and Currencies", "merged_at": "2025-07-16T10:00:35Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user", "connector"]}, "hierarchy": {"tests": ["config/deployments/integration_test.toml", "loadtes... |
<!-- Describe your changes in detail -->
This PR adds mandates support for Google Pay and Apple Pay Payment Method via `Authorize.Net` connector. It also supports Zero Auth Mandates. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/authorizedotnet.rs`
- `crates/hyperswitch_connectors/src/connectors/authorizedotnet/transformers.rs`
**2. Tests**
- `config/dep... | {"pr_number": 7412, "pr_title": "feat(connector): implement wallet mandates for authorizedotnet", "merged_at": "2025-03-11T14:41:15Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/co... |
<!-- Describe your changes in detail -->
This PR includes refactors around the customer payment methods list v2 code to follow some of the practices we've started enforcing in the recent few months. Additionally, I've picked up some minor refactors along the way.
This PR contains the following changes:
- Adds... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/admin.rs`
- `crates/api_models/src/payment_methods.rs`
- `crates/api_models/src/payments.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel... | {"pr_number": 6433, "pr_title": "refactor(payment_methods): refactor customer payment methods list v2 code to follow better code practices", "merged_at": "2024-11-08T14:57:43Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_mode... |
When deleting a merchant account, the code previously included a direct call to the **Decision Engine (DE)** to remove the merchant configuration (`delete_decision_engine_merchant`). This was gated behind the `dynamic_routing` and `v1` feature flags and executed synchronously within the merchant deletion flow. | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/admin.rs` | {"pr_number": 9076, "pr_title": "refactor(dynamic_routing): remove delete_merchant for DE", "merged_at": "2025-09-01T13:35:37Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"core_business": ["crates/router/src/core/admin.rs"]}, "change_types... |
<!-- Describe your changes in detail -->
This PR implements UPI Intent and QR code payment flows for the Unified Connector Service (UCS) integration, adding default implementations for Paytm and PhonePe connectors. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/connector_endpoints.rs`
**2. Core Business Logic**
- `crates/router/src/core/connector_validation.rs`
- `crates/router/src/core/u... | {"pr_number": 8732, "pr_title": "feat(core): Implement UCS based upi for paytm and phonepe", "merged_at": "2025-07-31T14:18:08Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/connec... |
<!-- Describe your changes in detail -->
This PR adds a check in Cypress `redirectionHandler` to verify that `payment_id` exists after the redirection completes without which it throws an error! | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `cypress-tests/cypress/support/redirectionHandler.js`
**Code Patterns Applied:**
- Add conditional logic for feature flags or filtering (2 changes) | {"pr_number": 7657, "pr_title": "ci(cypress): verify existence of `payment_id` after redirection", "merged_at": "2025-04-02T06:55:56Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user"]}, "hierarchy": {"tests": ["cypress-tests/cypress/support/redirectionHandler.js"]}, ... |
<!-- Describe your changes in detail -->
This PR makes raw_connector_response as a Secret and it also addresses unresolved comments of https://github.com/juspay/hyperswitch/pull/8499 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/payments.rs`
**2. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/router_data.rs`
**3. Core Business Logic**
- `crates/ro... | {"pr_number": 8565, "pr_title": "refactor(core): make raw_connector_response as secret", "merged_at": "2025-07-16T10:39:40Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/payments.rs"], "domain"... |
<!-- Describe your changes in detail -->
Added SecretString type definition in UCS proto files which will get swapped out with hyperswitch_masking::Secret type during build. This will allow us to mask any sensitive data like card_cvc, card _exp_month etc.
In this PR, all proto request types for which masked types... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/unified_connector_service.rs`
- `crates/router/src/core/unified_connector_service/transformers.rs`
**2. Configuration Files**
- `crates/external_services/Cargo.... | {"pr_number": 9044, "pr_title": "feat(core): Added support for unified_connector_service CardNumber and Secret<String> Type", "merged_at": "2025-08-27T15:50:04Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crate... |
<!-- Describe your changes in detail -->
Add ckh columns for 3ds intelligence analytics
Added nullable columns in CKH authentication table
```
`mcc` Nullable(String),
`amount` Nullable(UInt32),
`currency` LowCardinality(Nullable(String)),
`merchant_country` LowCardinality(Nullable(String)),
... | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. Other**
- `crates/analytics/docs/clickhouse/scripts/authentications.sql`
**Code Patterns Applied:**
- Modify database queries (2 changes) | {"pr_number": 8136, "pr_title": "feat(analytics): Add ckh columns for 3ds intelligence analytics", "merged_at": "2025-05-28T14:20:03Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["merchant", "card"]}, "hierarchy": {"other": ["crates/analytics/docs/clickhouse/scripts/authentications.sql"... |
<!-- 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-payment-methods.mdx`
- `payment-metho... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Other**
- `api-reference/docs.json`
- `api-reference/v2/customers/customers--update.mdx`
- `api-reference/v2/openapi_spec_v2.json`
- ... and 15 more files
**Detailed Identifier Changes:**
Commit 9319c7a6... | {"pr_number": 8382, "pr_title": "fix(openapi): Fix broken mintlify pages (v2)", "merged_at": "2025-06-20T13:54:03Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "refund"]}, "hierarchy": {"other": ["api-reference/docs.json", "api-reference/v2/customers/custome... |
<!-- Describe your changes in detail -->
Modified the Auth in the postman collection for payment connectors, from Admin API Key to API Key. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `postman/collection-dir/bankofamerica/API Key/Delete API Key/event.test.js`
- `postman/collection-dir/hyperswitch/API Key/Delete API Key/event.test.js`
- `postman/collection-dir/stripe/API Key/Delete... | {"pr_number": 7702, "pr_title": "chore(postman): update auth for payment connectors in postman collection", "merged_at": "2025-04-04T09:42:24Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user", "connector"]}, "hierarchy": {"tests": ["postman/collection-dir/bankofameri... |
<!-- Describe your changes in detail -->
to_state_code method of router is not updated so the implementation from hyperswitch_connectors needs to be used and the one from router is depreciated.
Note: Contains remaning European countries for ISO conversion
Note: hotfix against https://github.com/juspay/hyperswitc... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/utils.rs`
- `crates/router/src/connector/netcetera/netcetera_types.rs`
- `crates/router/src/connector/threedsecureio/transformers.rs`
- ... | {"pr_number": 7303, "pr_title": "refactor(utils): use to_state_code of hyperswitch_connectors in router", "merged_at": "2025-02-19T09:27:16Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "connector"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/utils... |
<!-- Describe your changes in detail -->
Add type for fields in juspay threeds server
## How did you test it?
<!--
Did you write an integration/unit/API test to verify the code changes?
Or did you test this change manually (provide relevant screenshots)?
-->
Complied wasm in local terminal
<img width="917... | To implement this **connector_integration** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/connector_configs/toml/development.toml`
- `crates/connector_configs/toml/production.toml`
- `crates/connector_configs/toml/sandbox.toml` | {"pr_number": 9744, "pr_title": "fix(core): Add type for fields in juspay threeds server", "merged_at": "2025-10-08T12:43:54Z", "intent": {"feature_type": "connector_integration", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"connectors": ["crates/connector_configs/toml/development.toml", "crates/conne... |
This PR introduces the following struct fix for netcetera authentication response since `message_extension` is recieved in Netcetera's authentication response ARes and not in AReq.
**Current structure**
```
NetceteraAuthenticationSuccessResponse{
....
authentication_request: {
message_extension: Option<serde_j... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/netcetera/transformers.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (1 changes) | {"pr_number": 9077, "pr_title": "fix(connector): [NETCETERA] Add fix for netcetera authentication response", "merged_at": "2025-09-02T13:35:01Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors/netcetera/tra... |
<!-- 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 less then 128 so after this origina... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/payment_attempt.rs`
**2. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/payments/payment_attempt.rs`
**Code Patter... | {"pr_number": 9017, "pr_title": "fix(payments): automatic connector_payment_id hashing in v2 if length > 128", "merged_at": "2025-09-01T14:34:13Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"database": ["crates/diesel_models/src/... |
<!-- Describe your changes in detail -->
Currently we are not marking users as verified if the user comes from SSO and there is no other way to verify if SSO is the only login method that is available. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/user.rs`
**Code Patterns Applied:**
- Add conditional logic for feature flags or filtering (1 changes) | {"pr_number": 6694, "pr_title": "fix(users): Mark user as verified if user logins from SSO", "merged_at": "2024-11-29T10:52:38Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"core_business": ["crates/router/src/core/user.rs"]}, "change_types": {"conditionals... |
<!-- Describe your changes in detail -->
`Paypal` wallet added in `BRAINTREE`.
API contract changes are done in `PaypalSessionTokenResponse` because we would need more details (client_token, amount, currency, etc) in session token response as mentioned in the test cases. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/payments.rs`
**2. Core Business Logic**
- `crates/router/src/core/payments/flows/session_flow.rs`
**3. External Connector Integration**
- `crates/connec... | {"pr_number": 8984, "pr_title": "feat(connector): [BRAINTREE] Paypal wallet added", "merged_at": "2025-10-09T15:25:24Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/payments.rs"], "core_busines... |
<!-- Describe your changes in detail -->
This API updates the lock status of customer token to unlock in revenue recovery. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/revenue_recovery_data_backfill.rs`
**2. Core Business Logic**
- `crates/router/src/core/revenue_recovery_data_backfill.rs`
**3. Other**
- `crates/router... | {"pr_number": 9403, "pr_title": "feat(revenue_recovery): Implement redis API to update the lock status for connector customer id", "merged_at": "2025-09-18T15:34:30Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "user", "token"]}, "hierarchy": {"api_models": ["crates/ap... |
<!-- Describe your changes in detail -->
Loomio webhooks for payments
## payment request
```json
{
"amount": 1500,
"currency": "CAD",
"confirm": true,
"capture_method": "automatic",
"customer_id": "aaaa",
"authentication_type": "three_ds",
"payment_method": "bank_redire... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/loonio.rs`
- `crates/hyperswitch_connectors/src/connectors/loonio/transformers.rs`
**Code Patterns Applied:**
- Define new data st... | {"pr_number": 9707, "pr_title": "feat(connector): Loonio Webhooks", "merged_at": "2025-10-07T17:37:38Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors/loonio.rs", "crates/h... |
Described in #6719
This PR introduces below changes
- `get_network_txn_id` fn in IncomingWebhook trait
- implement this new fn for Adyen for retrieving the network txn ID
- consume this fn in core flows for updating `network_transaction_id` in `payment_methods` table | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/payment_method.rs`
**2. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/router_flow_types/webhooks.rs`
**3. Core Bu... | {"pr_number": 6738, "pr_title": "feat(webhooks): adyen - consume and update connector's network_transaction_id in payment_methods", "merged_at": "2024-12-05T13:34:59Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user", "connector"]}, "hierarchy": {"database": ["crates/... |
<!-- Describe your changes in detail -->
- Add missing countries and currencies for nuvei | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `config/deployments/integration_test.toml`
- `loadtest/config/development.toml`
**2. Configuration Files**
- `config/config.example.toml`
- `config/deployments/production.toml`
- `config/deplo... | {"pr_number": 9563, "pr_title": "fix(nuvei): Update countries list for nuvei", "merged_at": "2025-09-25T16:22:29Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"tests": ["config/deployments/integration_test.toml", "loadtest/config/development.toml"], "config": ["c... |
<!-- Describe your changes in detail -->
Add fallback connectors to the list of eligible connectors for routing instead of connectors configured in the active routing rules
this PR reverts https://github.com/juspay/hyperswitch/pull/7921
Link for main branch revert PR - https://github.com/juspay/hyperswitch/pull/8207 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payments.rs`
**Detailed Identifier Changes:**
Commit 18262562:
Files to modify:
**crates/router/src/core/payments.rs**
Modify existing code | {"pr_number": 8259, "pr_title": "revert(routing): Add connectors from current active routing algorithm before adding fallback connectors", "merged_at": "2025-06-06T07:51:47Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_busin... |
<!-- Describe your changes in detail -->
Now that `analytics` depends on `currency_conversion` crate after this [PR](#6418), we need to include instructions in `analytics` documentation to set up this service.
## Fixes #6513 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Other**
- `crates/analytics/docs/README.md` | {"pr_number": 6516, "pr_title": "docs(analytics): add setup instructions for currency_conversion service", "merged_at": "2024-11-13T09:54:17Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"other": ["crates/analytics/docs/README.md"]}, "change_types": {}, "has_iden... |
<!-- Describe your changes in detail -->
make `endpoint_prefix` optional in three_ds_metadata for unified_authentication_service
Main PR - https://github.com/juspay/hyperswitch/pull/9717 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/router_request_types/unified_authentication_service.rs`
**2. Core Business Logic**
- `crates/router/src/core/payments/operations/pay... | {"pr_number": 9719, "pr_title": "fix(router): make `endpoint_prefix` optional in three_ds_metadata for unified_authentication_service", "merged_at": "2025-10-07T13:58:21Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_mod... |
Added Session Token Call Testcases in cypress | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `.github/workflows/cypress-tests-runner.yml`
- `cypress-tests/cypress/e2e/PaymentTest/00024-SessionCall.cy.js`
- `cypress-tests/cypress/e2e/PaymentUtils/Commons.js`
- ... and 3 more files
**Code ... | {"pr_number": 6683, "pr_title": "ci(cypress): Add Session Token Testcases", "merged_at": "2025-01-06T10:21:39Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user", "session", "token"]}, "hierarchy": {"tests": [".github/workflows/cypress-tests-runner.yml", "cypress-tests/cypress/e2... |
This PR adds below dynamic required fields for processing Worldpay payments -
- address.line1
- address.city
- address.country | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/router/src/configs/defaults/payment_connector_required_fields.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (12 changes) | {"pr_number": 7002, "pr_title": "chore(dynamic-fields): [Worldpay] update dynamic fields for payments", "merged_at": "2025-01-08T08:15:47Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user"]}, "hierarchy": {"connectors": ["crates/router/src/configs/defaults/payment_con... |
Described in the linked #6719 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/router/src/connector/adyen.rs`
- `crates/router/src/connector/adyen/transformers.rs`
**Code Patterns Applied:**
- Implement new functions (1 changes)
- Extend existing ... | {"pr_number": 6720, "pr_title": "fix(connector): adyen - propagate connector mandate details in incoming webhooks", "merged_at": "2024-12-02T18:30:38Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user", "connector", "webhook"]}, "hierarchy": {"connectors": ["crates/router/src/con... |
<!-- Describe your changes in detail -->
- pass external vault proxy metadata to uce for injector consumption
- it is passed in header as x-external-vault-metadata
- base64 encoded for parsing compatibility | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/merchant_connector_account.rs`
**2. Core Business Logic**
- `crates/router/src/core/payments.rs`
- `crates/router/src/core/paymen... | {"pr_number": 9108, "pr_title": "feat(core): [proxy payments] send external vault proxy metadata to UCS", "merged_at": "2025-09-01T11:21:32Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/merchant_connector_account.r... |
<!-- Describe your changes in detail -->
URLs are removed from config for Hyperswitch vault | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `config/deployments/integration_test.toml`
- `loadtest/config/development.toml`
**2. Configuration Files**
- `config/config.example.toml`
- `config/deployments/env_specific.toml`
- `config/dep... | {"pr_number": 8276, "pr_title": "refactor(config): redact config urls for hyperswitch vault", "merged_at": "2025-06-07T06:56:35Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"tests": ["config/deployments/integration_test.toml", "loadtest/config/development.toml"]... |
<!-- Describe your changes in detail -->
In this PR we will
1. Add display_name field to connector feature api
2. Rename non_threeDs to no_threeDs
## How did you test it?
<!--
Did you write an integration/unit/API test to verify the code changes?
Or did you test this change manually (provide relevant scre... | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/feature_matrix.rs`
**2. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/router_response_types.rs`
**3. External Connector Integrat... | {"pr_number": 7121, "pr_title": "refactor(router): add display_name field to connector feature api ", "merged_at": "2025-02-07T08:29:19Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["payment", "refund", "connector"]}, "hierarchy": {"api_models": ["crates/api_models/src/feature_matrix.rs... |
<!-- Describe your changes in detail -->
original pr's
https://github.com/juspay/hyperswitch/pull/7441
https://github.com/juspay/hyperswitch/pull/7424
## Checklist
<!-- Put an `x` in the boxes that apply -->
- [ ] I formatted the code `cargo +nightly fmt --all`
- [ ] I addressed lints thrown by `cargo cl... | To implement this **validation** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/admin.rs`
- `crates/router/src/core/authentication.rs`
- `crates/router/src/core/authentication/transformers.rs`
- ... and 5 more files
**2. External Connector ... | {"pr_number": 7446, "pr_title": "feat(connector): Added ThreeDs server integration template pr", "merged_at": "2025-03-06T12:14:51Z", "intent": {"feature_type": "validation", "action": "add_feature", "entities": []}, "hierarchy": {"core_business": ["crates/router/src/core/admin.rs", "crates/router/src/core/authenticati... |
<!-- Describe your changes in detail -->
Removed old add_connector.md file | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `add_connector.md`
- `add_connector_updated.md`
**Code Patterns Applied:**
- Define new data structures (4 changes)
- Implement new functions (13 changes)
- Extend existing typ... | {"pr_number": 8143, "pr_title": "chore(docs): remove old add_connector.md file", "merged_at": "2025-05-29T10:25:39Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["connector"]}, "hierarchy": {"connectors": ["add_connector.md", "add_connector_updated.md"]}, "change_types": {"structs_... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.