prompt stringlengths 6 90.9k | response stringlengths 121 18.6k | metadata stringlengths 314 42.3k |
|---|---|---|
<!-- Describe your changes in detail -->
- `is_manual_retry_enabled` is added to business profile
- it is a nullable value
- this provide control over the manual retry of payment for merchant
- [note] respective dashboard changes need to be picked | 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": 9266, "pr_title": "feat(business_profile): add field in profile for manual retry", "merged_at": "2025-09-08T10:44:41Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/admin.rs"], "da... |
Hotfix for https://github.com/juspay/hyperswitch/pull/7897 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/worldpay.rs`
- `crates/hyperswitch_connectors/src/connectors/worldpay/transformers.rs`
- `crates/payment_methods/src/configs/pay... | {"pr_number": 7900, "pr_title": "chore: add cardholder name as mandatory field for Worldpay card transactions", "merged_at": "2025-04-25T07:55:56Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["merchant", "card", "transaction"]}, "hierarchy": {"connectors": ["crates/hyperswitch_con... |
This PR corrects the Worldpay integration for NTI flows by removing `threeDS` from Authorize request. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/worldpay/requests.rs`
- `crates/hyperswitch_connectors/src/connectors/worldpay/transformers.rs` | {"pr_number": 7097, "pr_title": "fix(connector): [worldpay] remove threeDS data from Authorize request for NTI flows", "merged_at": "2025-02-05T15:13:19Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswi... |
<!-- Describe your changes in detail -->
Movement of dummy connector form `router` crate to `hyperswitch_connectors` crate | 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/payments/flows.rs`
**2. External Connector Integration**
- `crates/hyperswitch_connectors/Cargo.toml`
- `crates/hyperswit... | {"pr_number": 8372, "pr_title": "feat(connector): [DUMMY_CONNECTOR] crate restructuring", "merged_at": "2025-06-20T13:24:23Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["connector"]}, "hierarchy": {"core_business": ["crates/router/src/core/admin.rs", "crates/router/src/core/payme... |
API Reference : https://developer.santander.com.br/api/documentacao/pix-visao-geral#/api/documentacao/pix-visao-geral/
https://developer.santander.com.br/api/user-guide/pix-visao-geral | 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": 8369, "pr_title": "feat(connector): [SANTANDER] Add Template Code", "merged_at": "2025-06-20T13:28:33Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/configs.rs"], "core_business": ["crates/router... |
<!-- Describe your changes in detail -->
Wasm build is failing because of adding `actix-multipart` dependency in `api-models`. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/Cargo.toml`
- `crates/api_models/src/events/user.rs`
- `crates/api_models/src/user.rs`
**2. Configuration Files**
- `crates/router/Cargo.toml`
**Code Pat... | {"pr_number": 6747, "pr_title": "fix(api_models): Fix `wasm` build problems caused by `actix-multipart`", "merged_at": "2024-12-05T11:09:38Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"api_models": ["crates/api_models/Cargo.toml", "crates/api_models/src/e... |
<!-- Describe your changes in detail -->
- Save the context of payment_method_id in the session
- Create temporary token for payment_method_id to pass to payment confirm
- Save the cvc as a temporary data against the payment_token to be accessed by payment
- Evict the cvc after first use
- Encrypt/Decrypt the payl... | 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": 8525, "pr_title": "feat(payment-methods): create payment_token in vault confirm / do payment-confirm with temp token from session", "merged_at": "2025-07-07T11:56:09Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api... |
Added cypress test for this PR(https://github.com/juspay/hyperswitch/pull/8616/files).
Increased the Cypress timeout to ensure all redirection flows complete successfully during CI checks.
## How did you test it?
<img width="551" height="703" alt="image" src="https://github.com/user-attachments/assets/209a3fd8-386... | To implement this **validation** feature, you'll need to modify these architectural layers:
**1. Tests**
- `cypress-tests/cypress.config.js`
- `cypress-tests/cypress/e2e/configs/Payment/Commons.js`
**Code Patterns Applied:**
- Extend existing types with new fields (11 changes) | {"pr_number": 8790, "pr_title": "ci(cypress): Making a mandate payment with large customer user agents", "merged_at": "2025-07-30T10:07:15Z", "intent": {"feature_type": "validation", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"tests": ["cypress-tests/cypress.config.js", "cypress-tests/cypress/e2e/con... |
<!-- 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. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/user_role.rs`
**2. Utils**
- `crates/router/src/utils/user_role.rs`
**3. Other**
- `crates/router/src/services/authorization/info.rs`
- `crates/route... | {"pr_number": 6376, "pr_title": "refactor(permissions): Remove permissions field from permission info API response", "merged_at": "2024-10-22T10:15:42Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "user"]}, "hierarchy": {"api_models": ["crates/api_models/src... |
Implement interac Bank Redirect Payment Method
- Payments
- Psync | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/connector_validation.rs`
**2. External Connector Integration**
- `crates/common_enums/src/connector_enums.rs`
- `crates/connector_configs/src/connector.rs`
-... | {"pr_number": 9620, "pr_title": "feat(connector): [Loonio] Implement interac Bank Redirect Payment Method", "merged_at": "2025-09-30T15:41:22Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core/... |
<!-- Describe your changes in detail -->
https://github.com/user-attachments/assets/89bb0a3f-b160-4b60-91fe-6306a806c554
FE PR : https://github.com/juspay/hyperswitch-control-center/pull/3505
This pull request makes significant updates to the dashboard configuration and theming system. The main changes include a... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Configuration Files**
- `config/dashboard.toml`
- `config/dashboard_theme.json`
- `docker-compose.yml` | {"pr_number": 9243, "pr_title": "feat: customise default theme", "merged_at": "2025-09-09T09:37:32Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["merchant", "user", "order"]}, "hierarchy": {"config": ["config/dashboard.toml", "config/dashboard_theme.json", "docker-compose.yml"]}, ... |
<!-- Describe your changes in detail -->
moved cavv storing from table to temp locker
## Motivation and Context
<!--
Why is this change required? What problem does it solve?
If it fixes an open issue, please link to the issue here.
If you don't have an issue, we'd recommend starting with one first so the PR
... | To implement this **payment** 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": 7978, "pr_title": "refactor(authentication): moved cavv storing from table to temp locker", "merged_at": "2025-05-12T11:24:55Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["customer", "payment", "user"]}, "hierarchy": {"database": ["crates/diesel_models/src/authentication.... |
<!-- Describe your changes in detail -->
Show Error Message during 3ds un-sussessful error redirection | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/nuvei.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (1 changes) | {"pr_number": 9471, "pr_title": "Fix(connector): [NUVEI] 3ds unsuccessful redirection error msg", "merged_at": "2025-09-23T16:31:06Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/co... |
# Refactor: Change UCS connector configuration from array to comma-separated string | To implement this **connector_integration** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/unified_connector_service.rs`
**2. External Connector Integration**
- `crates/external_services/src/grpc_client/unified_connector_service.rs`
**3. Utils**... | {"pr_number": 8905, "pr_title": "refactor(config): change UCS connector list from array to comma-separated string", "merged_at": "2025-08-13T15:11:30Z", "intent": {"feature_type": "connector_integration", "action": "add_feature", "entities": ["connector"]}, "hierarchy": {"core_business": ["crates/router/src/core/unifie... |
<!-- Describe your changes in detail -->
Add customer phone_number and email to session token response for click to pay
## 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)?
-->
Add Ctp_master... | 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. Core Business Logic**
- `crates/router/src/core/payments.rs`
**3. Other**
- `api-reference-v2/openapi_spec.json`
- `api-reference/openapi... | {"pr_number": 6863, "pr_title": "feat(core): added customer phone_number and email to session token response for click to pay", "merged_at": "2024-12-19T12:03:50Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_m... |
<!-- Describe your changes in detail -->
This PR aims at refactoring:
- `cypress-tests` folder structure to reduce confusion and chaos in within `e2e` directory
- previous:
```sh
.
└── cypress
├── e2e
│ ├── PaymentMethodListTest
│ ├── PaymentMethodListUtils
│ ├── Payment... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Utils**
- `cypress-tests/cypress/utils/RequestBodyUtils.js`
**2. Tests**
- `cypress-tests/README.md`
- `cypress-tests/cypress/e2e/PaymentUtils/Adyen.js`
- `cypress-tests/cypress/e2e/PaymentUtils/BankOfAmer... | {"pr_number": 6992, "pr_title": "refactor(cypress): move memory cache tests out of payment for misc", "merged_at": "2025-01-24T17:23:22Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"utils": ["cypress-tests/cypress/utils/RequestBodyUt... |
<!-- Describe your changes in detail -->
- A new field in introduced in payment_intent table called extended_return_url
- This deprecate the existing return_url field since it can take string only upto length 255
- extended_return_url can now take length upto 2048 size
- write is done into the new field (extended_r... | 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_intent.rs`
- `crates/diesel_models/src/schema.rs`
**3. Domain ... | {"pr_number": 8279, "pr_title": "refactor(core): introduce new field in payment_intent to handle longer return_url", "merged_at": "2025-06-07T08:22:10Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "user"]}, "hierarchy": {"api_models": ["crates/api_models/src... |
Hotfix for PR https://github.com/juspay/hyperswitch/pull/7340
`cargo clippy` output
<img width="801" alt="Screenshot 2025-02-27 at 19 25 27" src="https://github.com/user-attachments/assets/b1026453-719c-4efe-85c8-4ec8807443c6" /> | 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": 7394, "pr_title": "feat(payments): [Payment links] add configs for payment link", "merged_at": "2025-02-27T14:19:17Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"api_models": ["crates/api_models/src/admin.rs", "crates/api_models/src/payments.... |
<!-- 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. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/events/routing.rs`
- `crates/api_models/src/open_router.rs`
**2. Core Business Logic**
- `crates/router/src/core/payments/routing/utils.rs`
- `crates/... | {"pr_number": 8640, "pr_title": "feat(routing): Add API key auth for decision engine endpoints", "merged_at": "2025-07-21T13:38:52Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/events/routing.... |
<!-- Describe your changes in detail -->
Implement `revolut_pay` for stripe | 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/payment_method_data.rs`
**3. External Connector Integratio... | {"pr_number": 8066, "pr_title": "feat(connector): Stripe revolut pay wallet integration", "merged_at": "2025-05-27T07:32:38Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/payments.rs"], "domain... |
Hotfix for https://github.com/juspay/hyperswitch/pull/7182 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `config/deployments/integration_test.toml`
**2. Configuration Files**
- `config/deployments/production.toml`
- `config/deployments/sandbox.toml`
- `config/development.toml` | {"pr_number": 7238, "pr_title": "chore(connectors): [fiuu] update pm_filters for apple pay and google pay", "merged_at": "2025-02-11T14:24:48Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"tests": ["config/deployments/integration_test.toml"], "config": ["config/d... |
<!-- Describe your changes in detail -->
Added supported countries and currencies for Cashtocode. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `config/deployments/integration_test.toml`
**2. Configuration Files**
- `config/deployments/production.toml`
- `config/deployments/sandbox.toml`
- `config/development.toml`
- ... and 1 more fi... | {"pr_number": 8101, "pr_title": "fix(connector): [CASHTOCODE] Added supported countries and currencies", "merged_at": "2025-05-21T13:11:19Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"tests": ["config/deployments/integration_test.toml"], "config": ["config/depl... |
<!-- Describe your changes in detail -->
add capability to force challenge for 3DS Payments through Netcetera and send few optional fields
Note: hotfix raised against: https://github.com/juspay/hyperswitch/pull/7429
1. Profile level enablement `force_3ds_challenge` which would request netcetera for challenge flo... | 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": 7434, "pr_title": "feat(router): add capability to force challenge for 3DS Payments through Netcetera and send few optional fields", "merged_at": "2025-03-05T14:59:55Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user", "connector"]}, "hierarchy": {"api_m... |
<!-- Describe your changes in detail -->
This PR exposes all headers set by the application in the `access-control-expose-headers` header value. This should thus allow our headers like `x-request-id` to be accessed by the browser.
## Motivation and Context
<!--
Why is this change required? What problem does it ... | To implement this **connector_integration** feature, you'll need to modify these architectural layers:
**1. Other**
- `crates/router/src/cors.rs` | {"pr_number": 6877, "pr_title": "fix(cors): expose all headers set by application in `access-control-expose-headers` header value", "merged_at": "2024-12-24T07:04:04Z", "intent": {"feature_type": "connector_integration", "action": "add_feature", "entities": []}, "hierarchy": {"other": ["crates/router/src/cors.rs"]}, "c... |
<!-- Describe your changes in detail -->
Refactoring connector enums to separate files to give code ownership to connector team for connector related changes. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/connector_enums.rs`
- `crates/api_models/src/enums.rs`
- `crates/api_models/src/lib.rs`
**2. External Connector Integration**
- `crates/common_enums/s... | {"pr_number": 6459, "pr_title": "refactor(connnector): Structure connector enums in separate files for improved team ownership", "merged_at": "2024-10-30T10:42:37Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["connector"]}, "hierarchy": {"api_models": ["crates/api_models/src/conne... |
- implemented currency_conversion for calculating values of amount related metrics from their currency (i.e `INR`) to
`USD` and store it in a separate field variant I created `<fieldname>_in_usd`
- Implemented a total_amount_in_usd variant for all the total fields related to amounts in query Metadata | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/analytics.rs`
- `crates/api_models/src/analytics/payment_intents.rs`
- `crates/api_models/src/analytics/payments.rs`
**2. Core Business Logic**
- `cra... | {"pr_number": 6418, "pr_title": "feat(analytics): implement currency conversion to power multi-currency aggregation", "merged_at": "2024-11-06T09:51:02Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"api_models": ["crates/api_models/sr... |
<!-- Describe your changes in detail -->
- To skip authorization, SCA exemption field is added to the transaction to flag it from authentication for frictionless flow for the user.
- The field is passed during the request and accept 2 values: `low_value` and, `transaction_risk_analysis` | 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/enums.rs`
- `crates/diesel_models/src/payment_intent.rs`
- `crates/d... | {"pr_number": 6578, "pr_title": "feat(core): add SCA exemption field", "merged_at": "2024-11-25T11:44:53Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "user"]}, "hierarchy": {"api_models": ["crates/api_models/src/payments.rs"], "database": ["crates/diesel_mo... |
<!-- Describe your changes in detail -->
- A new field in introduced in payment_intent table called extended_return_url
- This deprecate the existing return_url field since it can take string only upto length 255
- extended_return_url can now take length upto 2048 size
- write is done into the new field (extended_r... | 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_intent.rs`
- `crates/diesel_models/src/schema.rs`
**3. Domain ... | {"pr_number": 8321, "pr_title": "refactor(core): introduce new field in payment_intent to handle longer return_url", "merged_at": "2025-06-11T13:20:45Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "user"]}, "hierarchy": {"api_models": ["crates/api_models/src... |
This PR contains changes for two connector integrations
1. Fiuu - omit `bank_code` from the refund request for enabling ORF feature from Fiuu's side
2. RedSys - fix the field for sending `browserJavascriptEnabled` field properly | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/fiuu/transformers.rs`
- `crates/hyperswitch_connectors/src/connectors/redsys/transformers.rs`
**Code Patterns Applied:**
- Extend existi... | {"pr_number": 8079, "pr_title": "refactor(connector): [Fiuu] enable refund ORF feature [RedSys] fix the request structure", "merged_at": "2025-05-20T15:13:20Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["refund", "connector", "card"]}, "hierarchy": {"connectors": ["crates/hyperswitch_c... |
1. Remove multiple connector support for Trustpay payments as refunds works with single connector
2. Fix Session call test cases
3. Fix EPS payment method | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `cypress-tests/cypress/e2e/configs/Payment/Commons.js`
- `cypress-tests/cypress/e2e/configs/Payment/Trustpay.js`
- `cypress-tests/cypress/e2e/spec/Payment/00014-SaveCardFlow.cy.js`
- ... and 1 mor... | {"pr_number": 7797, "pr_title": "ci(cypress): fix trustpay refund test cases", "merged_at": "2025-04-25T07:50:18Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user", "refund"]}, "hierarchy": {"tests": ["cypress-tests/cypress/e2e/configs/Payment/Commons.js", "cypress-te... |
<!-- Describe your changes in detail -->
Initial commit to modular authentication create
This PR introduces a new modular authentication system to Hyperswitch, specifically adding an authentication creation API that allows merchants to initiate authentication flows independently of payment processing. | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/authentication.rs`
- `crates/api_models/src/lib.rs`
- `crates/api_models/src/webhooks.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/s... | {"pr_number": 8085, "pr_title": "feat(authentication): Initial commit to modular authentication create", "merged_at": "2025-06-24T12:14:25Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["payment", "merchant", "connector"]}, "hierarchy": {"api_models": ["crates/api_models/src/authenticati... |
<!-- Describe your changes in detail -->
This PR adds APIs to manage themes.
These are the following APIs
1. Create Theme
2. Delete Theme
3. Update Theme
4. Upload Asset
5. Find Theme by Theme ID
6. Find Theme by Lineage | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/Cargo.toml`
- `crates/api_models/src/events/user.rs`
- `crates/api_models/src/user.rs`
- ... and 1 more files
**2. Database Layer (Queries & Schema)**
... | {"pr_number": 6658, "pr_title": "feat(themes): Create APIs for managing themes", "merged_at": "2024-12-04T11:06:34Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["merchant", "user", "order"]}, "hierarchy": {"api_models": ["crates/api_models/Cargo.toml", "crates/api_models/src/event... |
## Summary | 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/transformers.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (2 changes) | {"pr_number": 9269, "pr_title": "fix: change precedence order in address that we send to ucs", "merged_at": "2025-09-03T17:28:26Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core/unified_conne... |
<!-- Describe your changes in detail -->
Addresses Failed Cypress Test Cases for `deutschebank` and `worldpayxml`. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `cypress-tests/cypress/e2e/configs/Payment/Deutschebank.js`
- `cypress-tests/cypress/e2e/configs/Payment/Utils.js`
- `cypress-tests/cypress/e2e/configs/Payment/Worldpayxml.js`
- ... and 3 more fil... | {"pr_number": 8193, "pr_title": "ci(cypress): fix `worldpayxml`, and `deutschebank` cypress test cases", "merged_at": "2025-07-04T14:47:44Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"tests": ["cypress-tests/cypress/e2e/configs/Payment/Deutschebank.js", "... |
PayPal added some extra parameters in the response, which caused the bank redirects to fail. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/router/src/connector/paypal/transformers.rs`
**Code Patterns Applied:**
- Define new data structures (2 changes)
- Extend existing types with new fields (7 changes) | {"pr_number": 6864, "pr_title": "fix(connector): Paypal BankRedirects (Ideal/EPS) ", "merged_at": "2024-12-20T07:16:57Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"connectors": ["crates/router/src/connector/paypal/transformers.rs"]}, "change_types": {"str... |
Add Nexinets connector to cypress test suits.
- This connector doesn't support MIT payments hence mapped accordingly
- Added 3ds flows | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `cypress-tests/cypress/e2e/configs/Payment/Nexinets.js`
- `cypress-tests/cypress/e2e/configs/Payment/Utils.js`
- `cypress-tests/cypress/support/redirectionHandler.js`
**Code Patterns Applied:**
- Ex... | {"pr_number": 8510, "pr_title": "ci(cypress): add nexinets connector", "merged_at": "2025-07-02T10:33:27Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "user"]}, "hierarchy": {"tests": ["cypress-tests/cypress/e2e/configs/Payment/Nexinets.js", "cypress-tests/c... |
<!-- Describe your changes in detail -->
Previously, we were accepting void_reason as string, but since Nmi accepts specific values for void_reason, those values have been added to an enum. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/router/src/connector/nmi/transformers.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (7 changes) | {"pr_number": 7221, "pr_title": "fix(connector): [NMI] Added enum for Void Reason", "merged_at": "2025-02-24T20:56:28Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/router/src/connector/nmi/transformers.rs"]}... |
For some billing connectors, we get limited data in the webhook that is not sufficient to use. So we need to make an additional api call for this extra data. This pr adds that flow. | 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_data_v2/flow_common_types.rs`
- `crates/hyperswitch_domain_models/src/router_flow_types.rs`
- `crates/hyperswitch_domain_mo... | {"pr_number": 7402, "pr_title": "feat(core): add additional revenue recovery call flow", "merged_at": "2025-03-06T07:14:02Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["connector", "webhook"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/router_data_v2/flow_com... |
<!-- Describe your changes in detail -->
Added recurring payments support for split payments in Stripe | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payments/transformers.rs`
**2. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/stripe/transformers.rs`
**Code Patterns Applied:**... | {"pr_number": 8271, "pr_title": "feat(connector): Added recurring payments support for split payments in Stripe", "merged_at": "2025-06-08T12:57:33Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src... |
<!-- Describe your changes in detail -->
main PR
https://github.com/juspay/hyperswitch/pull/8214
Adding infra level information to `ApiEvent` based on config from deployment config under `infra_values` | 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`
- `crates/router/src/core/webhooks/incoming_v2.rs`
**2. Configuration Files**
- `config/config.example.toml`
- `config/development.toml... | {"pr_number": 8242, "pr_title": "feat(events): adding infra level components to api-events", "merged_at": "2025-06-04T14:48:46Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"core_business": ["crates/router/src/core/webhooks/incoming.rs", "crates/router/src/... |
This pr adds fetches payment method data in payment attempt list v2 api. | 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/payments.rs`
**2. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/connector_endpoints.r... | {"pr_number": 8681, "pr_title": "refactor(payments): fetch payment method information in attempts list api v2 and add custom billing connector template", "merged_at": "2025-07-21T19:08:33Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "order", "connector"]}, "hierarchy":... |
<!-- Describe your changes in detail -->
- Add `PreAuthenticate`, `Authenticate` and `PostAuthenticate` connector integration and implement them for cybersource | 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.rs`
- `crates/hyperswitch_domain_models/src/types.rs`
**2. External Connector Integration**
- `crates/hypers... | {"pr_number": 9117, "pr_title": "feat(router): Add Connector changes for 3ds (v2)", "merged_at": "2025-09-11T14:33:57Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["connector"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/router_request_types.rs", "crates/hyper... |
<!-- Describe your changes in detail -->
An incorrect TOML format has been added to the ctp_mastercard due to which the wasm build is getting failed.
Add development as feature in wasm config | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/connector_configs/toml/production.toml`
- `crates/connector_configs/toml/sandbox.toml`
**2. Other**
- `docker/wasm-build.Dockerfile` | {"pr_number": 6967, "pr_title": "chore: fix `toml` format to address wasm build failure", "merged_at": "2025-01-28T09:17:26Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["card"]}, "hierarchy": {"connectors": ["crates/connector_configs/toml/production.toml", "crates/connector_confi... |
<!-- Describe your changes in detail -->
This PR update Cypress packages to address [CVE-2024-21538](https://vulert.com/vuln-db/CVE-2024-21538).
Closes https://github.com/juspay/hyperswitch/issues/6623 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `cypress-tests-v2/package-lock.json`
- `cypress-tests-v2/package.json`
- `cypress-tests/package-lock.json`
- ... and 1 more files | {"pr_number": 6624, "pr_title": "chore(deps): update cypress packages to address CVE", "merged_at": "2024-11-25T13:31:10Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"tests": ["cypress-tests-v2/package-lock.json", "cypress-tests-v2/package.json", "cypress-tests/... |
<!-- Describe your changes in detail -->
Hotfix for :
- https://github.com/juspay/hyperswitch/pull/8956
Issue : https://github.com/juspay/hyperswitch/issues/8953
On successful redirection on CARDS3ds Friction , eps bank redirect, even when fully captured the status is `partially_captured` | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/stripe/transformers.rs`
- `crates/hyperswitch_connectors/src/utils.rs`
**Code Patterns Applied:**
- Implement new functions (1 changes)
... | {"pr_number": 8976, "pr_title": "fix(stripe): partial capture issue when fully captured on redirection flow like card3ds , eps bank redirect", "merged_at": "2025-08-20T08:38:43Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors":... |
<!-- Describe your changes in detail -->
Template code added for new connector Elavon
https://developer.elavon.com/products/xml-api/v1/api-reference#tag/Process-Transaction-Online | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payments/connector_integration_v2_impls.rs`
- `crates/router/src/core/payments/flows.rs`
**2. External Connector Integration**
- `crates/hyperswitch_connectors/... | {"pr_number": 6309, "pr_title": "Feat(connector): [ELAVON] Template PR", "merged_at": "2024-11-05T10:02:55Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["connector", "transaction"]}, "hierarchy": {"core_business": ["crates/router/src/core/payments/connector_integration_v2_impls.rs... |
<!-- Describe your changes in detail -->
In order to use `Secret<String>` and `StrongSecret<String>` as field types of proto requests in other gRPC services (like Unified Connector Service), the `prost::Message` trait has been implemented for the types `Secret<String>` and `StrongSecret<String>` | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Configuration Files**
- `crates/masking/Cargo.toml`
**2. Other**
- `Cargo.lock`
- `crates/masking/src/secret.rs`
- `crates/masking/src/strong_secret.rs`
**Code Patterns Applied:**
- Implement new function... | {"pr_number": 8458, "pr_title": "feat(masking): implement `prost::Message` trait for `Secret` and `StrongSecret` types", "merged_at": "2025-07-02T07:16:20Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"config": ["crates/masking/Cargo.... |
<!-- Describe your changes in detail -->
For Fiuu, the mandate ID is updated via webhooks in the case of 3DS payments. The payment webhook body was not consumed when the payment was successful, causing intermittent issues in the sandbox environment. This PR adds support to address this issue.
**more detailed issue ... | 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`
- `crates/h... | {"pr_number": 6523, "pr_title": "fix(webhooks): add support for updating mandate details in webhooks flow ", "merged_at": "2024-11-13T10:20:29Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "connector", "webhook"]}, "hierarchy": {"database": ["crates/diesel_models/src/pa... |
<!-- Describe your changes in detail -->
Added Payments Webhooks | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/gigadat.rs`
- `crates/hyperswitch_connectors/src/connectors/gigadat/transformers.rs`
**Code Patterns Applied:**
- Define new data ... | {"pr_number": 9775, "pr_title": "feat(connector): [Gigadat] Add Payments Webhook", "merged_at": "2025-10-10T10:19:38Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors/gigada... |
<!-- Describe your changes in detail -->
`Googlepay`, `Applepay` wallets added in `BRAINTREE`.
In the current implementation of the session-token response flow, only the core layer logic is triggered for apple_pay and google_pay. However, for Braintree, we require a client_token generated from the connector layer.
... | 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/payment_method_data.rs`
- `crates/hyperswitch_domain_mod... | {"pr_number": 8728, "pr_title": "feat(connector): [BRAINTREE] Googlepay, Applepay wallets added", "merged_at": "2025-10-07T09:30:42Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/payments.rs"],... |
<!-- Describe your changes in detail -->
- Handle default case where card network is null because in case of co-badged cards, we will always get the card network from frontend | 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`
**Code Patterns Applied:**
- Extend existing types with new fields (2 changes) | {"pr_number": 6825, "pr_title": "fix(router): handle default case for card_network for co-badged cards", "merged_at": "2024-12-16T12:49:30Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core/pay... |
Added changes for the emails as per the email theme config.
Changes are done for:
- verify.html
- reset.html
- invite.html
- magic_link.html | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/user.rs`
**2. Type Definitions**
- `crates/router/src/services/email/types.rs`
**3. Configuration Files**
- `config/config.example.toml`
- `config/developme... | {"pr_number": 7580, "pr_title": "feat(themes): Add email configuration support for themes", "merged_at": "2025-03-26T14:19:46Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"core_business": ["crates/router/src/core/user.rs"], "types": ["crates/router/src/services/... |
<!-- Describe your changes in detail -->
In this PR
1. We have implemented the CIT and MIT payments, only for - network transaction id flow
2. Completely refactored the status handling
3. Refactored Psync and Rsync flow.
Any payment operation triggered to Vantiv (if didn't cause an API failure) will be marked as... | To implement this **payment** 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/hyperswitch_connectors/src/connectors/worldpayvantiv.rs`
- `crates/hyperswi... | {"pr_number": 8495, "pr_title": "feat(connectors): [Worldpayvantiv] add NTI flow and refactor sync flows", "merged_at": "2025-07-01T11:22:23Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/... |
Described in #6316 point # 4 (read comments) | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `cypress-tests/cypress/fixtures/create-connector-body.json`
**2. Tests**
- `cypress-tests/cypress/e2e/PaymentTest/00006-VoidPayment.cy.js`
- `cypress-tests/cypress/e2e/Payme... | {"pr_number": 6420, "pr_title": "feat(cypress-test): include worldpay's request / response structure for test suite", "merged_at": "2024-10-30T10:11:29Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user", "connector"]}, "hierarchy": {"connectors": ["cypress-tests/cypre... |
<!-- Describe your changes in detail -->
**Revenue record operation**
In revenue recovery webhook flow, we mainly consume 3 types of events
1) PaymentFailure
2) PaymentSuccess
3) InvoiceCancel
For PaymentFailure or PaymentSuccess scenario we need to record the attempt and update the payment intent fields. Thi... | 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": 7236, "pr_title": "feat(core): Add record attempt operation for revenue recovery webhooks", "merged_at": "2025-03-07T14:39:19Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/paymen... |
<!-- Describe your changes in detail -->
This Pr implements setup mandate flow, fixes card mandate flow and maps network_txn_id
Hotfix for https://github.com/juspay/hyperswitch/pull/8929
## How did you test it?
<!--
Did you write an integration/unit/API test to verify the code changes?
Or did you test th... | 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.rs`
**2. Core Business Logic**
- `crates/router/src/core/payments/transformers.rs`
**3. External Connector Int... | {"pr_number": 8950, "pr_title": "fix(connectors): [worldpayvantiv] add setup mandate flow, map network txn id and fix mandate flow", "merged_at": "2025-08-14T10:04:21Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"domain": ["crate... |
Hotfix for [7137](https://github.com/juspay/hyperswitch/pull/7137) | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payments.rs`
- `crates/router/src/core/payments/operations/payment_status.rs`
**Code Patterns Applied:**
- Implement new functions (1 changes)
- Extend existing ty... | {"pr_number": 7205, "pr_title": "fix(core): Add payment_link_data in PaymentData for Psync", "merged_at": "2025-02-07T06:58:02Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"core_business": ["crates/router/src/core/payments.rs", "crates/router/src/core/payments/o... |
<!-- Describe your changes in detail -->
fix connector metadata deserialization
Currently we deserialize to camelCase.
but dashboard always sends in snake_case. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/peachpayments/transformers.rs` | {"pr_number": 9826, "pr_title": "fix(connector): [Peach Payments] fix connector metadata deserialization", "merged_at": "2025-10-14T10:15:43Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user", "connector"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connec... |
<!-- Describe your changes in detail -->
We need to update payment link expired msg for traditional chinese locale. | 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 (2 changes) | {"pr_number": 9007, "pr_title": "feat(payment-link): update traditional chinese paymentlink exp msg", "merged_at": "2025-08-21T11:16:26Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"core_business": ["crates/router/src/core/payment_li... |
<!-- Describe your changes in detail -->
Previously due to the DB insertion code being in `post_update_tracker` was being called several times as our payment's status keeps on changing, due to this our DB broke as we had a unique constraint on `attempt_id` in the `dynamic_routing_stats` table.
To fix this we have add... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payments/operations/payment_response.rs`
**2. Other**
- `crates/common_enums/src/enums.rs`
**Code Patterns Applied:**
- Implement new functions (1 changes)
- Add ... | {"pr_number": 6900, "pr_title": "refactor(dynamic_routing): perform db operations for dynamic_routing_stats table only when payments are in terminal state", "merged_at": "2025-01-15T10:59:13Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierar... |
<!-- Describe your changes in detail -->
The opensearch query should be built manually in the code, based on the request body.
There is a component called `filter_array` which comprises of the free-text search query, addition of case sensitive filters and also the time_range (if provided).
When all the three sub par... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Other**
- `crates/analytics/src/opensearch.rs` | {"pr_number": 6716, "pr_title": "fix(opensearch): fix empty filter array query addition in globalsearch query", "merged_at": "2024-12-02T15:02:27Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user", "order"]}, "hierarchy": {"other": ["crates/analytics/src/opensearch.rs"]}, "chang... |
<!-- Describe your changes in detail -->
Hotfix for this [PR](https://github.com/juspay/hyperswitch/pull/9476) | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/nexixpay/transformers.rs`
**Code Patterns Applied:**
- Define new data structures (1 changes)
- Extend existing types with new fields... | {"pr_number": 9516, "pr_title": "fix(connector): [NEXIXPAY] Updated the Api Response Schema", "merged_at": "2025-09-24T05:53:33Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors/nexixpay/transformers.... |
<!-- Describe your changes in detail -->
On TrustPay's SEPA redirection page, the customer is shown the necessary details to complete the bank transfer, including an E2E reference number. This reference is used by TrustPay to match the incoming payment with the original payment request. If the customer omits this nu... | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/trustpay.rs`
- `crates/hyperswitch_connectors/src/connectors/trustpay/transformers.rs`
**Code Patterns Applied:**
- Extend existing type... | {"pr_number": 8116, "pr_title": "fix(connector): [trustpay] fix webhook deserialization error", "merged_at": "2025-06-11T13:57:53Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors... |
<!-- Describe your changes in detail -->
Helps closing - #6318 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Other**
- `api-reference/essentials/error_codes.mdx` | {"pr_number": 6319, "pr_title": "docs(error_codes): add unified error codes", "merged_at": "2024-10-15T14:02:06Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"other": ["api-reference/essentials/error_codes.mdx"]}, "change_types": {}, "has_identifier_data": false,... |
This PR fixes the bug report - https://github.com/juspay/hyperswitch/issues/8392#issuecomment-3032692625
Introduces below changes
- Use `get_string_repr` for formatting payoutIDs which were using default formatter
- Update connector configs for `adyenplatform` (WASM)
- Update payout method filters for `adyenplatf... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payouts.rs`
**2. External Connector Integration**
- `crates/connector_configs/toml/development.toml`
- `crates/connector_configs/toml/production.toml`
- `cra... | {"pr_number": 8547, "pr_title": "fix(payout): use get_string_repr for formatting payout IDs", "merged_at": "2025-07-05T15:11:29Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core/payouts.rs"], ... |
<!-- Describe your changes in detail -->
Changed the Attempt Status Mapping of `SubmittedForSettlement` and `SettlementPending` to `Charged` | 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` | {"pr_number": 7471, "pr_title": "fix(connector): [BRAINTREE] Changed Attempt Status Mapping for Braintree", "merged_at": "2025-03-11T11:23:21Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connect... |
Enhanced Globalpay Connector in cypress for Comprehensive Testing.
## How did you test it?
**Globalpay**
<img width="545" alt="globalpay" src="https://github.com/user-attachments/assets/ccbae99d-bf75-4498-a08a-0deae5976fdb" />
Note: 1. 3ds payments silently falling back to no-3ds(Should throw validation)
2... | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `cypress-tests/cypress/fixtures/create-connector-body.json`
**2. Tests**
- `cypress-tests/cypress/e2e/configs/Payment/Globalpay.js`
- `cypress-tests/cypress/e2e/configs/Payment/Ut... | {"pr_number": 8403, "pr_title": "ci(cypress): Add Globalpay connector test in cypress", "merged_at": "2025-06-24T14:54:39Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["payment", "user", "connector"]}, "hierarchy": {"connectors": ["cypress-tests/cypress/fixtures/create-connector-body.js... |
Reverts juspay/hyperswitch#9689 | To implement this **unknown** 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:**
**Detailed Identifier Changes:**
Commit 1b... | {"pr_number": 9740, "pr_title": "revert(routing): update configs on updation of mca", "merged_at": "2025-10-08T08:46:29Z", "intent": {"feature_type": "unknown", "action": "unknown", "entities": []}, "hierarchy": {"core_business": ["crates/router/src/core/admin.rs", "crates/router/src/core/routing.rs", "crates/router/sr... |
- Integrate Razorpay's API directly
- Payment Method - UPI Collect
- Added a new flow create order
- Added connector_request_reference_id in payment_attempt | 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`
- `crates/diesel_models/src/schema_v2.rs`
**3. Dom... | {"pr_number": 8009, "pr_title": "feat(connector): Implement Razorpay UPI Collect", "merged_at": "2025-06-11T14:05:03Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/payments.rs"], "database": ["... |
<!-- Describe your changes in detail -->
This PR introduces two new authentication mechanisms that enhance the existing `AdminApiAuth` and `AdminApiAuthWithMerchantIdFromRoute` by allowing fallback to regular API key-based authentication when the admin key check fails. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Configuration Files**
- `crates/router/src/configs/secrets_transformers.rs`
- `crates/router/src/configs/settings.rs`
**2. Other**
- `crates/router/src/routes/admin.rs`
- `crates/router/src/routes/api_keys... | {"pr_number": 7744, "pr_title": "feat(authentication): create authentications to fallback to ApiKeyAuth if AdminApiAuth fails", "merged_at": "2025-04-08T07:49:01Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"config": ["crates/router/... |
This PR updates the webhooks for Adyen's BalancePlatform for payouts.
Main changes -
For status `booked` from Adyen, map it to
`success` for cards
`processing` for banks - reason being status `credited` is received from Adyen for successful credits.
Check the relevant issue for more details. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/adyenplatform.rs`
- `crates/hyperswitch_connectors/src/connectors/adyenplatform/transformers/payouts.rs`
**Code Patterns Applied:*... | {"pr_number": 9002, "pr_title": "refactor(connector): [AdyenPlatform] update incoming webhooks for payouts", "merged_at": "2025-08-21T14:18:29Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "merchant", "user"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connector... |
<!-- Describe your changes in detail -->
This adds `SerializeValue` and `FromCQL` traits for masking StrongSecret
## Motivation and Context
<!--
Why is this change required? What problem does it solve?
If it fixes an open issue, please link to the issue here.
If you don't have an issue, we'd recommend startin... | To implement this **connector_integration** feature, you'll need to modify these architectural layers:
**1. Configuration Files**
- `crates/masking/Cargo.toml`
**2. Other**
- `Cargo.lock`
- `crates/masking/src/cassandra.rs`
- `crates/masking/src/lib.rs`
**Code Patterns Applied:**
- Implement new functio... | {"pr_number": 6500, "pr_title": "feat: implement scylla traits for StrongSecret", "merged_at": "2024-11-14T09:25:29Z", "intent": {"feature_type": "connector_integration", "action": "add_feature", "entities": []}, "hierarchy": {"config": ["crates/masking/Cargo.toml"], "other": ["Cargo.lock", "crates/masking/src/cassandr... |
<!-- Describe your changes in detail -->
add confirm flag in kafka payment intent events | 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/payments/payment_intent.rs`
**2. Core Business Logic**
- `crates/router/src/core/payments/operations/payment_confirm.rs`
- `crate... | {"pr_number": 8432, "pr_title": "feat(router): add confirm flag in kafka payment intent events", "merged_at": "2025-06-24T09:09:14Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/payments/payment_int... |
<!-- Describe your changes in detail -->
Adding metrics, and support for Refund Page in Analytics V2 Dashboard through sessionizer.
The metrics added are as follows:
- **Static Metrics in overview section:**
- Refund Success Rate
- Total Refunds Processed (Amount)
- Successful Refunds
- Failed Refunds
... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/analytics.rs`
- `crates/api_models/src/analytics/refunds.rs`
**2. Database Layer (Queries & Schema)**
- `crates/analytics/src/query.rs`
**3. Core Busine... | {"pr_number": 6616, "pr_title": "feat(analytics): Add refund sessionized metrics for Analytics V2 dashboard", "merged_at": "2024-12-05T12:09:55Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/an... |
while handling the response of UCS for webhooks Hyperswitch used to use the existing connector code (Psync's Handle Respnse) which gave error for UCS response so fixed this issue.
Closes #9027 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/webhooks.rs`
**2. Core Business Logic**
- `crates/router/src/core/payments.rs`
- `crates/router/src/core/unified_connector_service/transformers.rs`
- ... | {"pr_number": 9021, "pr_title": "fix: Resolved issue of webhooks response from ucs", "merged_at": "2025-08-29T15:11:29Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["connector", "webhook"]}, "hierarchy": {"api_models": ["crates/api_models/src/webhooks.rs"], "core_business": ["crat... |
<!-- Describe your changes in detail -->
Added fields in the google pay connector wallet details for the google pay `direct` and `payment gateway` flow
Development.toml
- adyen
- airwallex
- authorizedotnet
- bankofamerica
- bluesnap
- checkout
- cybersource
- globalpay
- multisafepay
- nmi
- noon
- ... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/connector_configs/src/connector.rs`
- `crates/connector_configs/toml/development.toml`
- `crates/connector_configs/toml/production.toml`
- ... and 1 more files
**... | {"pr_number": 7616, "pr_title": "feat(wasm): google pay decryption flow changes", "merged_at": "2025-03-28T11:03:29Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "connector"]}, "hierarchy": {"connectors": ["crates/connector_configs/src/connector.rs", "crates/connector_c... |
<!-- Describe your changes in detail -->
This PR updates the hotfix PR check workflow to conditionally enforce the requirement of the `main` branch PR being merged, based on the value of a repository variable.
## Motivation and Context
<!--
Why is this change required? What problem does it solve?
If it fixes a... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Configuration Files**
- `.github/workflows/hotfix-pr-check.yml`
**Code Patterns Applied:**
- Extend existing types with new fields (1 changes)
- Add conditional logic for feature flags or filtering (4 changes) | {"pr_number": 7351, "pr_title": "ci(hotfix-pr-check): conditionally enforce requirement of main branch PR being merged", "merged_at": "2025-02-25T06:52:22Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"config": [".github/workflows/hotfix-pr-check.yml"]}, "c... |
<!-- Describe your changes in detail -->
add dynamic fields support for samsung_pay | 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`
**2. Tests**
- `config/deployments/integration_test.toml`
- `loadtest/config/development.toml`
**3... | {"pr_number": 7090, "pr_title": "fix(router): add dynamic fields support for `samsung_pay`", "merged_at": "2025-02-04T12:06:23Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/router/src/configs/defaults/paymen... |
<!-- Describe your changes in detail -->
reverted this commit: 2f7cd4f752d98e23910c37502d8748e9842682ef | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/api_locking.rs`
**2. Type Definitions**
- `crates/redis_interface/src/types.rs`
**3. Other**
- `crates/redis_interface/src/commands.rs`
- `crates/redis_inte... | {"pr_number": 9029, "pr_title": "revert: feat(core): add support for api locking with multiple keys for a single api", "merged_at": "2025-08-22T09:32:07Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"core_business": ["crates/router/src/core/api_locking.rs"], "typ... |
<!-- Describe your changes in detail -->
This PR implements the following
- Added support for Reward payment methods for HS <> UCS integration
- Added support for CurrencyAuthKey auth type for HS <> UCS integration
- Send encoded_data as transaction_id when connector_transaction_id is None for PSync via UCS
- ... | 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. External Connector Integration**
- `crates/external_serv... | {"pr_number": 8767, "pr_title": "feat(core): Added Reward PaymentMethod & CurrencyAuthKey for Hyperswitch <> UCS Integration", "merged_at": "2025-08-13T11:41:49Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["cra... |
<!-- Describe your changes in detail -->
change amount conversion from MInorUnit to FloatMajorUnit | 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`
- `crates/hyperswitch_connectors/src/connectors/wise/transformers.rs`
**Code Patterns Applied:**
- Implement new function... | {"pr_number": 8991, "pr_title": "fix(connector): [Wise] change amount conversion unit", "merged_at": "2025-08-19T14:54:18Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors/w... |
<!-- Describe your changes in detail -->
Fix WASM changes for Dwolla | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/connector_configs/src/connector.rs`
- `crates/connector_configs/toml/development.toml`
- `crates/connector_configs/toml/production.toml`
- ... and 1 more files
**... | {"pr_number": 9051, "pr_title": "fix(wasm): [dwolla] fix WASM changes", "merged_at": "2025-08-28T11:58:47Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"connectors": ["crates/connector_configs/src/connector.rs", "crates/connector_configs/toml/development.toml", "... |
<!-- Describe your changes in detail -->
Fix wrong api methods for the endpoint resulting error is parsing. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Other**
- `api-reference/api-reference/customer-set-default-payment-method/customers--set-default-payment-method.mdx`
- `api-reference/api-reference/event/events--list.mdx`
- `api-reference/api-reference/payme... | {"pr_number": 8112, "pr_title": "chore(mintlify): fix mintlify api methods for endpoint", "merged_at": "2025-05-22T14:25:18Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"other": ["api-reference/api-reference/customer-set-default-payment-method/customers--set-def... |
<!-- Describe your changes in detail -->
- Added Chargebee subscription creation request/response structures.
- Implemented conversion traits for Chargebee subscription data.
- Enhanced Recurly connector to support subscription creation flows.
- Introduced new router flow types and request/response types for subscr... | 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_data_v2/flow_common_types.rs`
- `crates/hyperswitch_domain_models/src/router_flow_types.rs`
- `crates/hyperswitch_domain_mo... | {"pr_number": 9303, "pr_title": "feat: Implement subscription create for Chargebee", "merged_at": "2025-09-19T14:08:48Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user", "connector"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/router_data_v2/flow_common_typ... |
This PR adds below changes
- Add required field for Worldpay card transactions - card holder name.
- Fix 3DS SetupMandate flows for Worldpay card transactions | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/worldpay.rs`
- `crates/hyperswitch_connectors/src/connectors/worldpay/transformers.rs`
- `crates/payment_methods/src/configs/pay... | {"pr_number": 7897, "pr_title": "chore: add cardholder name as mandatory field for Worldpay card transactions", "merged_at": "2025-04-24T16:45:27Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_con... |
Reverts juspay/hyperswitch#9079 | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/authorizedotnet/transformers.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (12 changes)
**Detailed Identifier Cha... | {"pr_number": 9253, "pr_title": "fix(connector): Revert [AUTHORIZEDOTNET] customer id population fixed in authorize flow", "merged_at": "2025-09-04T07:19:18Z", "intent": {"feature_type": "payment", "action": "fix_bug", "entities": ["customer", "payment", "connector"]}, "hierarchy": {"connectors": ["crates/hyperswitch_c... |
<!-- Describe your changes in detail -->
Make the RevenueRecoveryRecordBack functionality generic to make it usable by subscription after making a successful payment.
This pull request refactors the "record back" functionality in the revenue recovery flow by renaming types and data structures from RevenueRecoveryReco... | 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_data_v2/flow_common_types.rs`
- `crates/hyperswitch_domain_models/src/router_flow_types/revenue_recovery.rs`
- `crates/hype... | {"pr_number": 9321, "pr_title": "refactor(connector): rename RevenueRecoveryRecordBack as InvoiceRecordBack", "merged_at": "2025-09-10T14:50:33Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "connector"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/ro... |
<!-- Describe your changes in detail -->
This pull request introduces a new feature to track and analyze debit routing savings and integrates it across multiple components of the analytics system. It also refactors the handling of co-badged card networks to provide additional details, such as saving percentages. Below... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/analytics/payments.rs`
- `crates/api_models/src/open_router.rs`
- `crates/api_models/src/payment_methods.rs`
**2. Domain Models (Business Logic Types)**
... | {"pr_number": 8519, "pr_title": "feat(debit_routing): add `debit_routing_savings` in analytics payment attempt", "merged_at": "2025-07-04T14:14:37Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src... |
<!-- Describe your changes in detail -->
This PR implements a very basic version of the list customer payment methods v2 route, including some refactors made along the way.
This PR includes the following changes:
- Modifies the `created` field to be a required field in `CustomerPaymentMethod`. I've also fixed ... | 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/payment_methods.rs`
**3. Core Business Logic**
-... | {"pr_number": 6649, "pr_title": "feat(payment_methods_v2): implement a barebones version of list customer payment methods v2", "merged_at": "2024-12-02T10:41:09Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/... |
<!-- Describe your changes in detail -->
This pull request modifies the default configuration for `SuccessBasedRoutingConfig` in the `crates/api_models/src/routing.rs` file. The changes adjust the values for aggregate sizes, success rate thresholds, and block duration to better align with updated routing requirements.... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/routing.rs`
**2. Core Business Logic**
- `crates/router/src/core/payments/routing.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (4... | {"pr_number": 8098, "pr_title": "refactor(success_rate): update the default configs", "merged_at": "2025-05-21T20:44:44Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["merchant", "connector"]}, "hierarchy": {"api_models": ["crates/api_models/src/routing.rs"], "core_business": ["cra... |
<!-- Describe your changes in detail -->
The #[serde(deny_unknown_fields)] lines are now commented out to handle backward incompatibility
Hotfix for https://github.com/juspay/hyperswitch/pull/8980 | 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. Other**
- `api-reference/v1/openapi_spec_v1.json`
- `api-reference/v2/openapi_spec_v2.json` | {"pr_number": 8994, "pr_title": "fix(core): Address Deserialization issue ", "merged_at": "2025-08-19T12:57:43Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/payments.rs"], "other": ["api-refer... |
<!-- Describe your changes in detail -->
add `merchant_configuration_id` in netcetera metadata and make other merchant configurations optional
Main PR - https://github.com/juspay/hyperswitch/pull/7347
Clippy successful locally
<img width="1229" alt="image" src="https://github.com/user-attachments/assets/6790b543-... | 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`
- `crates/router/src/core/payments/operations/payment_confirm.rs`
**2. External Connector Integration**
- `crates/connector_configs/src/com... | {"pr_number": 7372, "pr_title": "feat(router): add `merchant_configuration_id` in netcetera metadata and make other merchant configurations optional", "merged_at": "2025-02-25T12:17:30Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["merchant", "user"]}, "hierarchy": {"core_business... |
<!-- Describe your changes in detail -->
Update status mapping in case of setup mandate flow response for nexixpay connector. PR also involves config changes, added new supported countries. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/nexixpay/transformers.rs`
- `crates/hyperswitch_connectors/src/utils.rs`
**2. Tests**
- `config/deployments/integration_test.to... | {"pr_number": 7612, "pr_title": "fix(connector): [Nexixpay] update status mapping nexixpay", "merged_at": "2025-03-26T18:28:26Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connect... |
<!-- Describe your changes in detail -->
This will add a value `non_deterministic` in `SuccessBasedRoutingConclusiveState` type. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Other**
- `migrations/2024-12-18-124527_add_new_value_in_success_based_routing_conclusive_state/down.sql`
- `migrations/2024-12-18-124527_add_new_value_in_success_based_routing_conclusive_state/up.sql`
**Code Pa... | {"pr_number": 6878, "pr_title": "refactor(dynamic_routing): add non_deterministic value in SuccessBasedRoutingConclusiveState type", "merged_at": "2024-12-30T07:55:16Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant"]}, "hierarchy": {"other": ["migrations/2024-12... |
<!-- Describe your changes in detail -->
Add merchant Id auth for payments_create_and_confirm_intent. This is enabled on merchant_id_auth_enabled. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Configuration Files**
- `config/config.example.toml`
- `config/deployments/env_specific.toml`
- `config/development.toml`
- ... and 3 more files
**2. Other**
- `crates/router/src/routes/payments.rs`
... | {"pr_number": 8239, "pr_title": "feat(router): add merchantId authentication for Payments v2", "merged_at": "2025-06-06T08:57:20Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"config": ["config/config.example.toml", "config/deploy... |
<!-- Describe your changes in detail -->
Introduced a global accounts schema in code. Accounts related tables like organization, merchant_account and business_profile will be moved to this schema in future.
For now, in this PR we will be using the existing v1 schema for each tenant as accounts schema. Right now onl... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/organization.rs`
**2. Core Business Logic**
- `crates/router/src/core/admin.rs`
- `crates/router/src/core/user.rs`
- `crates/router/src/core/... | {"pr_number": 7113, "pr_title": "feat(core): introduce accounts schema for accounts related tables", "merged_at": "2025-02-14T13:59:41Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["merchant", "user"]}, "hierarchy": {"database": ["crates/diesel_models/src/organization.rs"], "core_... |
<!-- Describe your changes in detail -->
This PR fixes 5xx thrown by JPMorgan connector during payments authorize and void call.
Connector expects the expiry month and year to be `i32` and not a `String` which is why it used to a 5xx due to deserialization failure.
And for Void, the connector expects a limited... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/jpmorgan.rs`
- `crates/hyperswitch_connectors/src/connectors/jpmorgan/transformers.rs`
**2. Tests**
- `cypress-tests/cypress/e2... | {"pr_number": 8282, "pr_title": "fix(connector): [jpmorgan] 5xx during payment authorize and `cancellation_reason`", "merged_at": "2025-06-10T09:08:18Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user", "connector"]}, "hierarchy": {"connectors": ["crates/hyperswitch_c... |
<!-- Describe your changes in detail -->
added support for api locking with multiple keys for a single api.
* introduced a couple of redis interface commands to support this feature. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/api_locking.rs`
**2. Type Definitions**
- `crates/redis_interface/src/types.rs`
**3. Other**
- `crates/redis_interface/src/commands.rs`
- `crates/redis_inte... | {"pr_number": 8887, "pr_title": "feat(core): add support for api locking with multiple keys for a single api", "merged_at": "2025-08-13T07:57:06Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "user"]}, "hierarchy": {"core_business": ["crates/router/src/core/a... |
<!-- Describe your changes in detail -->
-> Why?
With new features being added, it is becoming increasingly difficult to track all the additions. This information is essential for accurately representing Hyperswitch's offerings. Having this solution will eliminate inconsistencies between the documentation and the act... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/feature_matrix.rs`
- `crates/api_models/src/lib.rs`
**2. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/router_response_t... | {"pr_number": 6612, "pr_title": "feat(router): add endpoint for listing connector features ", "merged_at": "2024-12-24T09:35:07Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/feature_matrix.rs"... |
<!-- Describe your changes in detail -->
The Proxy allows you to use tokens with HTTP APIs without needing to access sensitive data directly within your systems. This enables solving both these problems securely while keeping your systems out of compliance scope.
proxy takes any connector request, replaces the to... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/Cargo.toml`
- `crates/api_models/src/lib.rs`
- `crates/api_models/src/proxy.rs`
- ... and 1 more files
**2. Core Business Logic**
- `crates/router/src/... | {"pr_number": 7901, "pr_title": "feat(router): Add support for Proxy api", "merged_at": "2025-05-22T13:34:33Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"api_models": ["crates/api_models/Cargo.toml", "crates/api_models/src/lib.rs", ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.