prompt stringlengths 6 90.9k | response stringlengths 121 18.6k | metadata stringlengths 314 42.3k |
|---|---|---|
1) Added a new CaptureMethod : SequentialAutomatic -> does Auth and capture in two api calls one after the other
1. **For Paybox**:
- If the payment is a Customer-Initiated Transaction (CIT), two API calls will be made:
- First for Authorization (`Auth`)
- Followed by Capture (`Capture`)
... | 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_response_types.rs`
**2. Core Business Logic**
- `crates/router/src/core/fraud_check/operation/fraud_check_post.rs`
- `crat... | {"pr_number": 6587, "pr_title": "feat(connector): Added a new CaptureMethod SequentialAutomatic to Support CIT Mandates for Paybox", "merged_at": "2024-12-05T14:03:43Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"domain": ["crate... |
<!-- Describe your changes in detail -->
Implementing a retry logic for forex crate call with linear time increment in retry counter | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/currency.rs`
**2. Other**
- `crates/router/src/consts.rs`
**Code Patterns Applied:**
- Add conditional logic for feature flags or filtering (2 changes)
**Detaile... | {"pr_number": 7280, "pr_title": "fix(analytics): retry implementation for forex crate call", "merged_at": "2025-03-20T14:26:48Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user", "token"]}, "hierarchy": {"core_business": ["crates/router/src/core/currency.rs"], "other"... |
<!-- Describe your changes in detail -->
This PR introduces a new JWT authenticated endpoint for listing unique webhook events for a profile. The endpoint URL is `/events/profile/list` and it will support only JWT authentication.
The profile ID and merchant ID will be extracted directly from JWT token. The router ha... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Other**
- `api-reference-v2/openapi_spec.json`
- `api-reference/openapi_spec.json`
- `crates/openapi/src/openapi.rs`
- ... and 4 more files
**Code Patterns Applied:**
- Implement new functions (2 changes)
... | {"pr_number": 7325, "pr_title": "refactor(webhook): add jwt authenticated endpoint to list unique webhook events for a profile", "merged_at": "2025-03-24T12:00:35Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "refund"]}, "hierarchy": {"other": ["api-referenc... |
<!-- 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": 8528, "pr_title": "feat(connectors): [Worldpayvantiv] add NTI flow and refactor sync flows", "merged_at": "2025-07-02T10:16:30Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/... |
<!-- Describe your changes in detail -->
add three_ds decision rule execute api
This pull request introduces a new feature for executing 3DS decision rules, along with supporting changes across multiple modules. The changes include adding new structures for handling 3DS decision rule inputs and outputs, integrating... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/lib.rs`
- `crates/api_models/src/three_ds_decision_rule.rs`
**2. Core Business Logic**
- `crates/router/src/core.rs`
- `crates/router/src/core/payment... | {"pr_number": 8148, "pr_title": "feat(router): add three_ds decision rule execute api", "merged_at": "2025-06-06T16:52:13Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "user"]}, "hierarchy": {"api_models": ["crates/api_models/src/lib.rs", "crates/api_models/... |
<!-- Describe your changes in detail -->
If the business profile does not have a country set, we cannot perform debit routing, because the merchant_business_country will be treated as the acquirer_country, which is used to determine whether a transaction is local or global in the open router. For now, since debit rout... | 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:**
- Add conditional logic for feature flags or filtering (2 changes) | {"pr_number": 8162, "pr_title": "refactor(debit_routing): Handle missing merchant_business_country by defaulting to US", "merged_at": "2025-05-28T07:10:06Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["merchant", "transaction"]}, "hierarchy": {"core_business": ["crates/router/src/... |
<!-- Describe your changes in detail -->
This PR introduces multiple fixes for Cypress V2 at framework level. The fixes include:
- When Error is thrown, we would usually get `undefined` instead of valid error message. This [commit](https://github.com/juspay/hyperswitch/commit/3fdcbdbee3e45f2122135f024dec65c255c5a... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Utils**
- `cypress-tests-v2/cypress/utils/RequestBodyUtils.js`
**2. Tests**
- `cypress-tests-v2/cypress/e2e/configs/Payment/Utils.js`
- `cypress-tests-v2/cypress/e2e/configs/Payment/_Reusable.js`
- `cypres... | {"pr_number": 6493, "pr_title": "ci(cypressV2): update cypress v2 framework to accommodate hyperswitch v2 changes", "merged_at": "2024-11-08T13:06:37Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user"]}, "hierarchy": {"utils": ["cypress-tests-v2/cypress/utils/RequestB... |
<!-- Describe your changes in detail -->
Changed readme content to make it lean and easier for Contributor to consume content | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Other**
- `README.md` | {"pr_number": 6306, "pr_title": "docs: simplify README", "merged_at": "2024-10-16T09:34:00Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"other": ["README.md"]}, "change_types": {}, "has_identifier_data": false, "commits_matched": 0, "match_method": "none"} |
<!-- Describe your changes in detail -->
update env for network tokenization service with webhook source verification key | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payments/tokenization.rs`
**2. Type Definitions**
- `crates/common_types/src/callback_mapper.rs`
**3. Configuration Files**
- `config/config.example.toml`
-... | {"pr_number": 8472, "pr_title": "fix(env): update env for network tokenization service", "merged_at": "2025-06-27T10:30:48Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["webhook", "token"]}, "hierarchy": {"core_business": ["crates/router/src/core/payments/tokenization.rs"], "types... |
<!-- Describe your changes in detail -->
This change updates the idempotent_event_id generation to first hash the base string with SHA256 and then encode it using URL-safe Base64 without padding. By doing this, the generated IDs are guaranteed to be short and deterministic, ensuring they always fit within the 64-chara... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/errors.rs`
- `crates/router/src/core/webhooks/outgoing.rs`
- `crates/router/src/core/webhooks/outgoing_v2.rs`
- ... and 2 more files
**2. Utils**
- `crate... | {"pr_number": 9405, "pr_title": "fix(webhooks): add idempotent_event_id generation using URL-safe Base64 (no padding) and SHA256 digest", "merged_at": "2025-09-22T08:30:21Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"core_business":... |
<!-- Describe your changes in detail -->
Since schema for both v1 and v2 can be unified, it paves way for a new bug.
In v1, while querying a record with a column that is common for both v1 and v2, the query may retrieve list of records belonging to both v1 and v2.
Now v1 application will be able to deserialise ... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/query.rs`
- `crates/diesel_models/src/query/generics.rs`
- `crates/diesel_models/src/query/utils.rs`
**Code Patterns Applied:**
- Implement new ... | {"pr_number": 7785, "pr_title": "feat: add primary key not null query to generic filter function", "merged_at": "2025-04-17T05:38:08Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"database": ["crates/diesel_models/src/query.rs", "crat... |
Hotfix for https://github.com/juspay/hyperswitch/pull/7993 | 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`
**2. Configuration Files**
- `crates/router/locales/en-GB.yml`
- `crates/router/locales/fr-BE.yml`
**3. Other**
- `crates/router/src... | {"pr_number": 8018, "pr_title": "fix(core): language consumption from locale in payment and payout links", "merged_at": "2025-05-13T11:44:37Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"core_business": ["crates/router/src/core/payment_link/locale.js"], "config"... |
<!-- Describe your changes in detail -->
1. Add NTID proxy support for nuvei. ( NOTE: Nuvei is not responding with NTID as of now hence we cant make ntid originated flow via nuvei to other connector. We are verifying NTID originated from other connector through nuvei. )
2. Extend mandate support for googlepay and app... | 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`
- `crates/hyperswitch_connectors/src/connectors/nuvei/transformers.rs`
**2. Tests**
- `config/deployments/integration... | {"pr_number": 9081, "pr_title": "feat(nuvei): NTID Support + googlepay & applepay mandate support", "merged_at": "2025-08-29T13:21:26Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/... |
<!-- Describe your changes in detail -->
added wasm changes for juspayThreeds server metadata
## 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="980" height="236" alt="Scree... | 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": 9708, "pr_title": "fix(core): added wasm changes for juspayThreeds server metadata", "merged_at": "2025-10-08T07:16:28Z", "intent": {"feature_type": "connector_integration", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"connectors": ["crates/connector_configs/toml/development.toml", "crat... |
<!-- Describe your changes in detail -->
Hotfix PR for: [https://github.com/juspay/hyperswitch/pull/6403](https://github.com/juspay/hyperswitch/pull/6403)
- Additional filters are added to `PaymentIntentFilters` as new analytics APIs are expected to be calculated from `Sessionizer Payment Intents` table.
- Existin... | 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. Core Business Logic**
- `crates/analytics/src/payment_intents/core.rs`
**3. Type Definitions**
- `crates/analytics/sr... | {"pr_number": 6407, "pr_title": "feat(analytics): remove additional filters from PaymentIntentFilters", "merged_at": "2024-10-23T09:58:10Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"api_models": ["crates/api_models/src/analytics/pa... |
<!-- Describe your changes in detail -->
This PR implements the complete Peachpayments connector integration for Hyperswitch, adding support for payment processing, 3DS authentication, void transactions, and comprehensive validation.
Key features implemented:
- Complete Peachpayments connector with payment aut... | 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": 9030, "pr_title": "feat(connector): [PeachPayments] Add Cards Flow", "merged_at": "2025-09-12T07:36:01Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core/connector_validation.rs"]... |
<!-- Describe your changes in detail -->
This PR addresses the clippy lints occurring due to new rust version 1.82.0.
Majorly addresses below warning -
 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/connector_onboarding.rs`
- `crates/api_models/src/payouts.rs`
- `crates/api_models/src/webhooks.rs`
**2. Database Layer (Queries & Schema)**
- `crates... | {"pr_number": 6401, "pr_title": "chore: address Rust 1.82.0 clippy lints", "merged_at": "2024-10-24T16:04:52Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"api_models": ["crates/api_models/src/connector_onboarding.rs", "crates/api_models/src/payouts.rs", "c... |
<!-- Describe your changes in detail -->
The #[serde(deny_unknown_fields)] lines are now commented out to handle backward incompatibility | 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": 8980, "pr_title": "fix(core): Address Deserialization issue ", "merged_at": "2025-08-19T10:38:56Z", "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 -->
Implemented gRPC based health check | 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/health_check.rs`
**2. Core Business Logic**
- `crates/router/src/core/health_check.rs`
**3. Configuration Files**
- ... | {"pr_number": 6441, "pr_title": "feat: Added grpc based health check", "merged_at": "2024-11-26T13:58:33Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"api_models": ["crates/api_models/Cargo.toml", "crates/api_models/src/health_check.rs"], "core_business": ... |
<!-- Describe your changes in detail -->
Mask custom outgoing webhook headers in profile response. This changes is required to mask the custom outgoing webhook headers in the profile dashboard. This also requires control center changes, BE changes will only be merged and
deployed after dashboard changes. | 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. Type Definitions**
- `crates/router/src/types/api/admin.rs`
**3. Other**
- `Cargo.lock`
**Code Patterns Applied:**
- Define new data str... | {"pr_number": 6823, "pr_title": "fix(webhooks): mask custom outgoing webhook headers in profile response", "merged_at": "2024-12-12T08:42:26Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/admin... |
<!-- Describe your changes in detail -->
`first_attempt` as a group by is getting added internally in the queries as it is required by the new PaymentIntent based metrics for Analytics V2 Dashboard.
The logic was added for the existing older metrics as well for PaymentIntents on the older dashboard, and is failing ... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Other**
- `crates/analytics/src/payment_intents/metrics/payment_processed_amount.rs`
- `crates/analytics/src/payment_intents/metrics/payments_success_rate.rs`
- `crates/analytics/src/payment_intents/metrics/se... | {"pr_number": 6627, "pr_title": "fix(analytics): remove first_attempt group by in Payment Intent old metrics", "merged_at": "2024-11-22T08:52:30Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"other": ["crates/analytics/src/payment_int... |
<!-- Describe your changes in detail -->
Update scylla driver on masking crate
## 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
can foc... | 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`
**Code Patterns Applied:**
- Implement new functions (1 changes)
- Extend existing ... | {"pr_number": 6799, "pr_title": "chore(deps): update scylla driver", "merged_at": "2024-12-16T09:20:21Z", "intent": {"feature_type": "connector_integration", "action": "add_feature", "entities": []}, "hierarchy": {"config": ["crates/masking/Cargo.toml"], "other": ["Cargo.lock", "crates/masking/src/cassandra.rs"]}, "cha... |
<!-- Describe your changes in detail -->
The ClickHouse queue table for connector events was configured to consume from the wrong Kafka topic in the local and Docker config files.
Current (incorrect) topic in config: `hyperswitch-connector-api-events`
Expected (correct) topic: `hyperswitch-outgoing-connector-eve... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Configuration Files**
- `config/development.toml`
- `config/docker_compose.toml`
**2. Other**
- `crates/analytics/docs/clickhouse/scripts/authentications.sql`
**Code Patterns Applied:**
- Modify database que... | {"pr_number": 8169, "pr_title": "fix(kafka): add correct topic name for connector-logs for docker config and local development", "merged_at": "2025-05-30T08:02:47Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user", "connector"]}, "hierarchy": {"config": ["config/devel... |
<!-- Describe your changes in detail -->
Add RSA-SHA-256 signature verification in crypto module.
- rsa crate is used for cryptography implementation | 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`
**2. Utils**
- `crates/common_utils/Cargo.toml`
- `crates/common_utils/src/crypto.rs`
**3. Other**
- `Cargo.lock`
... | {"pr_number": 9080, "pr_title": "feat(crypto): add RSA-SHA-256 signature verification", "merged_at": "2025-09-03T14:33:36Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors/wise.rs"], "utils": ["crates... |
<!-- Describe your changes in detail -->
Magic link will send one more email along with magic link email if user is signing up. | 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. Other**
- `crates/router/src/consts/user.rs`
- `crates/router/src/servic... | {"pr_number": 6639, "pr_title": "feat(users): Send welcome to community email in magic link signup", "merged_at": "2024-11-26T09:10:41Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"core_business": ["crates/router/src/core/user.rs"], "types": ["crates/route... |
<!-- Describe your changes in detail -->
The hyperswitch server would run even without the completion of migration runner polluting the data in the scarf dashboard. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Configuration Files**
- `docker-compose.yml`
**2. Other**
- `scripts/poststart_hook.sh`
**Code Patterns Applied:**
- Extend existing types with new fields (3 changes) | {"pr_number": 7999, "pr_title": "fix: fixes the docker setup to clean up the scarf data", "merged_at": "2025-05-12T08:26:50Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"config": ["docker-compose.yml"], "other": ["scripts/poststart_hook.sh"]}, "change_types": {"... |
<!-- Describe your changes in detail -->
the existing amount conversion framework for certain connector is outdated. we need to migrate those connector to using the latest and greatest amount converter framework.
base - float/string major unit
minor - minor unit / string minor unit | 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`
- `crates/hyperswitch_conne... | {"pr_number": 8878, "pr_title": "refactor(connector): implement amount converter framework for authorizedotnet, bankofamerica", "merged_at": "2025-08-26T07:22:25Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates... |
<!-- Describe your changes in detail -->
ci checks are failing on every pr because of failed lint check. this pr aims to address that. | 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:**
- Extend existing types with new fields (2 changes)
- Add conditional logic for feature flags or filtering (2 changes) | {"pr_number": 7437, "pr_title": "ci(cypress): address lints and refactor redirection handler", "merged_at": "2025-03-07T11:57:27Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"tests": ["cypress-tests/cypress/support/redirectionHandler.js"]}, "change_types":... |
<!-- Describe your changes in detail -->
Add product authentication id's column in business profile | To implement this **authentication** 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/... | {"pr_number": 6811, "pr_title": "feat(core): Add product authentication ids in business profile", "merged_at": "2024-12-12T15:01:35Z", "intent": {"feature_type": "authentication", "action": "add_feature", "entities": []}, "hierarchy": {"api_models": ["crates/api_models/src/admin.rs"], "database": ["crates/diesel_models... |
<!-- Describe your changes in detail -->
This Facilitapay PR introudces 2 new features and a bug fix which is described below:
- Add support for webhooks
- Source verification supported
- Payments
- Refunds (It is only supported for pix payment when a third party makes a transaction instead of the actual... | 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 4 more files
*... | {"pr_number": 8778, "pr_title": "feat(connector): [facilitapay] fix refunds, add webhook and void support", "merged_at": "2025-07-31T07:07:17Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/connector_configs/t... |
<!-- Describe your changes in detail -->
Fixed Open API Spec until Payment methods - tag
Changes done in this PR
1. SDK generation from Open API failed due to having a unit variant in an untagged enum. In this PR, we have refactored the `NoSessionResponse` variant to use Custom `NullObject` with serialize_none()
... | 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/hypers... | {"pr_number": 8127, "pr_title": "fix(openapi): correct schema references and semantics for v1 openApi spec", "merged_at": "2025-06-20T13:23:26Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/pay... |
1)Fix Wasm changes for Tokenio Open Banking | 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` | {"pr_number": 8347, "pr_title": "feat(core): Fix Wasm changes for Tokenio Open Banking", "merged_at": "2025-06-16T08:54:07Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user", "token"]}, "hierarchy": {"connectors": ["crates/connector_configs/toml/development.toml", "crates/connec... |
For Novalnet Connector, for Applepay, Googlepay, Paypal the following fields are not required
```
payment_method_data.billing.address.first_name
payment_method_data.billing.address.last_name
```
This PR removes these required fields for Applepay, Googlepay, Paypal for Novalnet | 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`
- `crates/hyperswitch_connectors/src/utils.rs`
- `crates/router/src/configs/defaults/payment_connector... | {"pr_number": 7152, "pr_title": "fix(connector): [novalnet] Remove first name, last name as required fields for Applepay, Googlepay, Paypal ", "merged_at": "2025-02-04T19:22:41Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "user"]}, "hierarchy": {"connectors... |
<!-- Describe your changes in detail -->
This PR introduces necessary refactoring to add support for locker specific tests. This includes `addition of delete payment method` (which is restricted to work only on hosted environments and not local given `tartarus` is unavailable and is complicated to setup things) but ... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Utils**
- `cypress-tests/cypress/utils/RequestBodyUtils.js`
- `cypress-tests/cypress/utils/featureFlags.js`
**2. Tests**
- `cypress-tests/cypress/e2e/PaymentTest/00003-ConnectorCreate.cy.js`
- `cypress-tes... | {"pr_number": 6735, "pr_title": "ci: add tests that make use of locker", "merged_at": "2024-12-26T12:15:14Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user", "connector"]}, "hierarchy": {"utils": ["cypress-tests/cypress/utils/RequestBodyUtils.js", "cypress-tests/cypr... |
Added the `v2/payments/filter` and `v2/payments/profile/filter` API to retrieve available payment filters (connectors, statuses, payment methods, authentication types, etc.) at merchant and profile level. | 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/payments.rs`
**3. Type Definitions**
- `c... | {"pr_number": 7171, "pr_title": "feat(router): Add v2 endpoint to retrieve payment filters at merchant and profile level", "merged_at": "2025-02-25T18:48:16Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_... |
<!-- Describe your changes in detail -->
Add zero auth mandate flow for nexixpay connector. It uses 3ds payments flow to create mandates. | 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": 7532, "pr_title": "feat(connector): [Nexixpay] add setup mandate flow", "merged_at": "2025-03-18T18:15:56Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/router_request_... |
remove chasenet from jpmorgan wasm as ChaseNet doesn’t exist in PMT | 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": 6927, "pr_title": "fix(wasm): remove chasenet from jpmorgan wasm as ChaseNet doesn\u2019t exist in PMT", "merged_at": "2024-12-24T09:11:48Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"connectors": ["crates/connector_configs/src/connector.rs", "cra... |
<!-- Describe your changes in detail -->
This PR updates Cypress documentation to deal with recent file structure change.
- `cypress-tests` folder structure to reduce confusion and chaos in within `e2e` directory
- previous:
```sh
.
└── cypress
├── e2e
│ ├── PaymentMethodListTest
... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `cypress-tests/README.md`
- `cypress-tests/cypress/support/e2e.js` | {"pr_number": 7016, "pr_title": "docs(cypress): update file structure", "merged_at": "2025-01-13T07:50:55Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment"]}, "hierarchy": {"tests": ["cypress-tests/README.md", "cypress-tests/cypress/support/e2e.js"]}, "change_types": {}, "ha... |
<!-- Describe your changes in detail -->
This PR updates all **user-related Redis operations** to consistently use the **global Redis key prefix** (`global:`) instead of environment-specific prefixes like `public:` (V1) or `public_v2:` (V2).
Previously, different deployments used different prefixes, which caused in... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Utils**
- `crates/router/src/utils/user.rs`
- `crates/router/src/utils/user/two_factor_auth.rs`
**2. Other**
- `crates/router/src/db.rs`
- `crates/router/src/db/kafka_store.rs`
- `crates/router/src/rout... | {"pr_number": 7932, "pr_title": "fix(users): use global Redis prefix for all user-related cache operations", "merged_at": "2025-05-05T16:02:25Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user", "token"]}, "hierarchy": {"utils": ["crates/router/src/utils/user.rs", "crates/router... |
Reverts juspay/hyperswitch#8205 | To implement this **unknown** 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
**Detai... | {"pr_number": 8224, "pr_title": "revert(connector): [Worldpay] add root CA certificate", "merged_at": "2025-06-10T08:33:22Z", "intent": {"feature_type": "unknown", "action": "unknown", "entities": []}, "hierarchy": {"connectors": ["crates/connector_configs/toml/development.toml", "crates/connector_configs/toml/producti... |
<!-- Describe your changes in detail -->
This PR modifies critical paths , specifically the `decide_connector` function and the `route_connector_v1_for_payments` function in the payments confirm flow.
These changes are made corresponding to a use case for Narvar. In case the connector specified in straight through ro... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payments.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (1 changes)
**Detailed Identifier Changes:**
Commit c2ad04f4:
Files to modify:
**... | {"pr_number": 7921, "pr_title": "refactor(routing): Add connectors from current active routing algorithm before adding fallback connectors", "merged_at": "2025-05-14T18:35:38Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_bus... |
Passing a field `transaction_type` as 3 if its an MIT. For all others, we should be passing 1. | 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": 8518, "pr_title": "fix(connector): [CYBERSOURCE] Passing pares_status for MasterCard & Visa and transaction_type field", "merged_at": "2025-07-03T07:01:38Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": [... |
<!-- Describe your changes in detail -->
This will interpolate the success_based_routing config params with the specific payment's values:
So for now the redis key was something like PaymentMethod:Currency
After this change it will be something like Card:USD | 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/errors.rs`
- `crates/router/src/core/payments.rs`
- `crates/router/src/core/payments/... | {"pr_number": 6448, "pr_title": "Refactor(core): interpolate success_based_routing config params with their specific values", "merged_at": "2024-11-08T13:06:37Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user", "card"]}, "hierarchy": {"api_models": ["crates/api_model... |
<!-- Describe your changes in detail -->
Added connector field in `PaymentRevenueRecoveryMetadata` and made `insert_execute_pcr_task` function
which creates and inserts a process tracker entry for executing a PCR (Payment Control & Reconciliation) workflow. It generates a unique `process_tracker_id`, fetches the sc... | 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/process_tracker.rs`
- `crates/diesel_models/src/types.rs`
**3. Domain ... | {"pr_number": 7462, "pr_title": "feat(router): add connector field to PaymentRevenueRecoveryMetadata and implement schedule_failed_payment ", "merged_at": "2025-03-13T10:04:27Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_m... |
<!-- Describe your changes in detail -->
Add apple_pay and google_pay mandate support for nuvei in integ,sbx and prod ( updation of config files)
Parent pr : https://github.com/juspay/hyperswitch/pull/9081
Refer test cases with above pr | 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/docker_compose.toml` | {"pr_number": 9256, "pr_title": "feat(nuvei): add mandate support for integ,prod,and sbx for googlepay applepay", "merged_at": "2025-09-03T12:35:52Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"tests": ["config/deployments/integration_test.toml"], "config": ["co... |
<!-- Describe your changes in detail -->
change click_to_pay const to snake_case and remove camel_case serde rename for clicktopay metadata | 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/payments.rs`
**3. Other**
- `api-reference-v2/openapi_s... | {"pr_number": 6852, "pr_title": "fix(router): change click_to_pay const to snake_case and remove camel_case serde rename for clicktopay metadata", "merged_at": "2024-12-16T14:27:33Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "connector"]}, "hierarchy": {"a... |
<!-- Describe your changes in detail -->
This PR addresses the clippy lints occurring due to new rust version 1.86.0
https://rust-lang.github.io/rust-clippy/master/index.html | To implement this **connector_integration** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/errors/utils.rs`
**2. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/bluesnap.rs`
- `crates/hyperswitch_connectors/src... | {"pr_number": 7735, "pr_title": "chore: address Rust 1.86.0 clippy lints", "merged_at": "2025-04-11T12:07:07Z", "intent": {"feature_type": "connector_integration", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"core_business": ["crates/router/src/core/errors/utils.rs"], "connectors": ["crates/hyperswitc... |
<!-- Describe your changes in detail -->
Consume merchant_account_id and merchant_config_currency from payment requests for braintree. | 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": 7408, "pr_title": "fix(connector): [Braintree] Consume merchant_account_id and merchant_config_currency in payment requests", "merged_at": "2025-03-05T12:09:19Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_model... |
<!-- Describe your changes in detail --> | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/archipel/transformers.rs` | {"pr_number": 8451, "pr_title": "feat(connector): [ARCHIPEL] fix Mastercard scheme string for Applepay payments", "merged_at": "2025-06-24T14:29:45Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors/archipel... |
<!-- Describe your changes in detail -->
This change adds support for capturing the reportGroup in the dashboard.
Currently, the dashboard does not extract the reportGroup from the metadata. With this update, it will start collecting and displaying the reportGroup field correctly.
Hotfix for https://github.com/jus... | To implement this **connector_integration** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/connector_configs/src/connector.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (1 changes) | {"pr_number": 8270, "pr_title": "fix(wasm): [Worldpayvantiv] add support for metadata.report_group", "merged_at": "2025-06-06T08:00:24Z", "intent": {"feature_type": "connector_integration", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"connectors": ["crates/connector_configs/src/connector.rs"]}, "chang... |
This is hot fix for the [PR](https://github.com/juspay/hyperswitch/pull/6446)
Earlier, for setup mandate flows we were not populating the Payment Method Info field, due to which for the Setup Mandate Payments the connector_mandate_details where not getting populated in the payment methods table. This PR fixes setup ... | 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`
**Code Patterns Applied:**
- Add conditional logic for feature flags or filtering (1 changes) | {"pr_number": 6450, "pr_title": "fix(core): fix setup mandate payments to store connector mandate details", "merged_at": "2024-10-28T10:08:40Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core/... |
Added Adyen and Checkout connectors in feature matrix api | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/adyen.rs`
- `crates/hyperswitch_connectors/src/connectors/checkout.rs`
**2. Tests**
- `config/deployments/integration_test.toml... | {"pr_number": 7914, "pr_title": "feat(connector): [ADYEN, CHECKOUT] Added In Feature Matrix API", "merged_at": "2025-05-12T14:31:35Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "refund", "connector"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/con... |
<!-- Describe your changes in detail -->
Support MOTO payments for checkout.
Updated status flag - if capture method is Automatic, we can map the Authorized status received from the connector 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/checkout/transformers.rs`
- `crates/hyperswitch_connectors/src/utils.rs`
**2. Tests**
- `cypress-tests/cypress/e2e/configs/Paym... | {"pr_number": 9327, "pr_title": "feat(connector): [checkout] add support for MOTO payments", "merged_at": "2025-09-10T14:18:55Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connect... |
- Add core flow for Void after Capture
- Add PostCaptureVoid Flow in worldpayVantiv connector | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/events/payment.rs`
- `crates/api_models/src/open_router.rs`
- `crates/api_models/src/payments.rs`
**2. Domain Models (Business Logic Types)**
- `crate... | {"pr_number": 8839, "pr_title": "feat(core): Add support for Void after Capture", "merged_at": "2025-08-06T08:04:14Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/events/payment.rs", "crates/ap... |
<!-- Describe your changes in detail -->
Stop sending back mandate reference from connector response in case of non-CIT payments to avoid making connector mandate details entry in payment_methods table. This should only be done in case of CIT payments to store correct PSP token which will be used in MIT payments. | 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:**
- Extend existing types with new fields (12 changes)
**Detailed Identifier Chan... | {"pr_number": 9614, "pr_title": "fix(connectors): [Nexixpay] fix for failing MITs", "merged_at": "2025-09-30T14:08:59Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors/nexix... |
<!-- Describe your changes in detail -->
Database Changes
Payment Intent: Added tax_status, discount_amount, shipping_amount_tax, duty_amount, customer_order_date
Customer: Added tax_registration_id for tax information
Address: Added origin_zip
API Models
Extended OrderDetailsWithAmount with SKU, UPC, commod... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/customers.rs`
- `crates/api_models/src/payment_methods.rs`
- `crates/api_models/src/payments.rs`
**2. Database Layer (Queries & Schema)**
- `crates/di... | {"pr_number": 8828, "pr_title": "feat(core): Add L2_L3 Data Support ", "merged_at": "2025-08-05T13:22:10Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/customers.rs", "crates/api_models/src/pay... |
Added webhooks integration support in hyperswitch so that for webhooks hyperswitch can call UCS and get the response.
Closes #8880 | 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/unified_connector_service.rs`
- `crates/router/src/core/unified_connector_service/transformers.rs`
- ... and 1 ... | {"pr_number": 8814, "pr_title": "feat(core): Adding integration for webhooks through UCS", "merged_at": "2025-08-08T14:35:40Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"core_business": ["crates/router/src/core/payments/helpers.rs",... |
<!-- Describe your changes in detail -->
This PR addresses clippy lints stabilized / enabled in Rust 1.83.0. The major warnings being thrown due to the version bump were [`empty_line_after_doc_comments`](https://rust-lang.github.io/rust-clippy/master/index.html#empty_line_after_doc_comments) and [`empty_line_after_o... | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/admin.rs`
- `crates/api_models/src/analytics.rs`
- `crates/api_models/src/api_keys.rs`
- ... and 7 more files
**2. Database Layer (Queries & Schema)**
- ... | {"pr_number": 6705, "pr_title": "chore: address Rust 1.83.0 clippy lints and enable more clippy lints", "merged_at": "2024-12-02T14:57:14Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["card"]}, "hierarchy": {"api_models": ["crates/api_models/src/admin.rs", "crates/api_models/src/analyti... |
<!-- Describe your changes in detail -->
Added the script for showing output of ```docker compose up -d``` command, along with links to access individual components. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Other**
- `README.md`
- `scripts/docker_output.sh`
**Code Patterns Applied:**
- Add conditional logic for feature flags or filtering (1 changes) | {"pr_number": 7806, "pr_title": "fix: script for one click docker setup", "merged_at": "2025-04-13T18:11:03Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"other": ["README.md", "scripts/docker_output.sh"]}, "change_types": {"conditionals_added": 1}, "has_id... |
<!-- Describe your changes in detail -->
fix fingerprint implementation in v2.
Earlier, Card number is sent as the key to generate fingerprint, which restricted us to add same card for different customer and different merchant.
this pr fix the above by sending customer id as key while generation of fingerpri... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payment_methods.rs`
- `crates/router/src/core/payment_methods/vault.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (2 changes) | {"pr_number": 7270, "pr_title": "fix(payment_methods_v2): update fingerprint implementation in v2", "merged_at": "2025-02-20T13:53:58Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core/payment_... |
<!-- Describe your changes in detail -->
This pr adds support for the invoice-generated event type for the incoming webhook for Chargebee and creates a process tracker entry that will trigger a S2S call and invoice sync. | 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. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/router_flow_types/subscriptions.rs`
- `crates/hyperswitc... | {"pr_number": 9400, "pr_title": "feat: Implement subscriptions workflow and incoming webhook support", "merged_at": "2025-10-03T16:39:11Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/webhooks.... |
<!-- Describe your changes in detail -->
Add happy cases + variation cases for manual retry feature | 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/Cybersource.js`
- `cypress-tests/cypress/e2e/configs/Payment/Utils.js`
- ... and 1 more files
*... | {"pr_number": 9505, "pr_title": "feat(cypress): add cypress test-cases for manual retry", "merged_at": "2025-09-26T09:01:20Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"tests": ["cypress-tests/cypress/e2e/configs/Payment/Commons.js", "cypress-tests/cypres... |
<!-- Describe your changes in detail -->
This PR ensures that the entity_id is backfilled in the user_roles table, preventing issues for V1 users when switching organizations and logging in. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Other**
- `migrations/2024-12-02-110129_update-user-role-entity-type/down.sql`
- `migrations/2024-12-02-110129_update-user-role-entity-type/up.sql`
- `migrations/2024-12-13-080558_entity-id-backfill-for-user-r... | {"pr_number": 6847, "pr_title": "fix(user_roles): migrations for backfilling user_roles entity_id", "merged_at": "2024-12-16T13:36:14Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["merchant", "user"]}, "hierarchy": {"other": ["migrations/2024-12-02-110129_update-user-role-entity-t... |
<!-- Describe your changes in detail -->
- when webhook url is configured in psp's dashboard, some psp send a sample webhook for acknowledgement.
- this feature helps in bypassing business logic in case of an setup webhook and send 200 ok status
- the setup webhook is triggered if the IncomingWebhookEvent type is Se... | 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/webhooks/incoming.rs`
- `crates/router/src/core/webhooks/incoming_v2.rs`
- `crates/r... | {"pr_number": 9420, "pr_title": "feat(core): add webhook setup event handler", "merged_at": "2025-09-22T07:58:41Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "merchant", "order"]}, "hierarchy": {"api_models": ["crates/api_models/src/webhooks.rs"], "core_business": ["c... |
Added Tests for Customer Deletion and Psync flows | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `cypress-tests/cypress/e2e/spec/Payment/00026-DeletedCustomerPsyncFlow.cy.js`
- `cypress-tests/cypress/e2e/spec/Payment/00026-BusinessProfileConfigs.cy.js`
- `cypress-tests/cypress/e2e/spec/Payment/0... | {"pr_number": 7158, "pr_title": "ci(cypress): Add Tests for Customer Deletion and Psync flows", "merged_at": "2025-02-07T07:45:21Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "user"]}, "hierarchy": {"tests": ["cypress-tests/cypress/e2e/spec/Payment/00026-DeletedCustom... |
<!-- Describe your changes in detail -->
The format of csv:-
<img width="1720" height="33" alt="Screenshot 2025-09-02 at 13 57 36" src="https://github.com/user-attachments/assets/d8e57dc8-1707-49b2-a27f-79888ee5a8b9" />
<img width="1711" height="32" alt="Screenshot 2025-09-02 at 13 57 54" src="https://github.com/use... | 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/revenue_recovery_data_backfill.rs`
**2. Core Business Logic**
- `crates/router/src/c... | {"pr_number": 9233, "pr_title": "feat(revenue_recovery): add support for updating additional card info data from csv to redis", "merged_at": "2025-09-18T11:31:08Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates... |
<!-- Describe your changes in detail -->
fixed notification_url and updated authentication bug
## 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)?
-->
Do Authentication create
```
curl --lo... | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/unified_authentication_service.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (29 changes)
- Add conditional logic for feature flags or filtering (1... | {"pr_number": 8843, "pr_title": "fix(authentication): fixed notification_url and updated authentication bug", "merged_at": "2025-08-08T10:06:35Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"core_business": ["crates/router/src/core/unified_... |
<!-- Describe your changes in detail -->
In the debit routing call we require the card number or the network token bin to perform the lookup to get the co-badged networks associated with the card. Currently the wallet decryption happens in the call connector service which will be called in the confirm call. In wallets... | 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/payment_method_data.rs`
**2. Core Business Logic**
- `crates/router/src/core/payments.rs`
- `crates/router/src/core/payments/oper... | {"pr_number": 8598, "pr_title": "refactor(router): decrypt the wallet token before the debit routing call", "merged_at": "2025-07-18T12:55:27Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_mode... |
<!-- 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 | 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": 7287, "pr_title": "refactor(utils): use to_state_code of hyperswitch_connectors in router", "merged_at": "2025-02-17T13:28:13Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "connector"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/utils... |
<!-- Describe your changes in detail -->
This PR resolves the v2 warnings generated in diesel_models. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/merchant_connector_account.rs`
- `crates/diesel_models/src/payment_attempt.rs`
- `crates/diesel_models/src/query/merchant_account.rs`
- ... an... | {"pr_number": 7359, "pr_title": "chore: resolve v2 warnings in diesel_models", "merged_at": "2025-04-29T10:25:05Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"database": ["crates/diesel_models/src/merchant_connector_account.rs", "crates/diesel_models/src/payment... |
<!-- Describe your changes in detail --> | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `postman/collection-dir/nmi/Flow Testcases/Happy Cases/Scenario12-Save card payment with manual capture/Save card payments - Confirm/event.test.js`
- `postman/collection-dir/nmi/Flow Testcases/Happy Cas... | {"pr_number": 7458, "pr_title": "fix(postman): update expected status from `processing` to `requires_capture` in payment confirmation tests", "merged_at": "2025-03-11T11:00:10Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user", "connector"]}, "hierarchy": {"tests": ["... |
<!-- Describe your changes in detail -->
made changes to populate id column in merchant account while creating a new merchant_account record in v1.
So that the merchant account created in v1 can be read from v2. | 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/query/merchant_account.rs`
**3. Domain Models (Business Logic Types)**
- ... | {"pr_number": 7426, "pr_title": "chore: make v1 merchant account forward compatible", "merged_at": "2025-03-07T11:44:45Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"api_models": ["crates/api_models/src/admin.rs"], "database": ["crat... |
<!-- Describe your changes in detail -->
- Modified response handling logic to only populate `amount_captured` in router_data when payment status is `Charged`.
- Removed the integrity check error that was preventing overpaid payments from being processed correctly.
- The `PaymentsSyncData::get_captured_amount` metho... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/cryptopay/transformers.rs`
- `crates/router/src/connector/utils.rs`
**2. Type Definitions**
- `crates/router/src/types.rs`
**C... | {"pr_number": 9674, "pr_title": "fix(connector): [Cryptopay] fix amount_captured population logic in response handling", "merged_at": "2025-10-10T08:50:42Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hypers... |
- Implement 3ds decision manger for V2
- Merchant can configure different 3ds rule for each profile. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/conditional_configs.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/business_profile.rs`
- `crates/diesel_models/src/schema_v2.r... | {"pr_number": 7022, "pr_title": "feat(core): Implement 3ds decision manger for V2", "merged_at": "2025-02-05T14:59:36Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"api_models": ["crates/api_models/src/conditional_configs.rs"], "datab... |
<!-- Describe your changes in detail -->
Hotfix PR
Original PR: [https://github.com/juspay/hyperswitch/pull/7656](https://github.com/juspay/hyperswitch/pull/7656) | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `cypress-tests-v2/cypress/support/commands.js`
- `cypress-tests/cypress/support/commands.js`
**2. Other**
- `crates/router/src/routes/admin.rs`
- `crates/router/src/routes/profiles.rs`
- `crat... | {"pr_number": 7663, "pr_title": "refactor(authentication): modify auth for profiles and mca routes to `ApiKeyAuthWithMerchantIdFromRoute`", "merged_at": "2025-03-28T09:29:21Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"tests": ["cypress-tests-v2/cypress/support... |
<!-- Describe your changes in detail -->
Context: In case of some billing connectors we don't get the enough data in the webhook itself to support creation of payment intent and payment attempt in our system. So previously we derived a flow named "BillingConnectorPaymentSync" in this PR:https://github.com/juspay/hyper... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/recurly.rs`
- `crates/hyperswitch_connectors/src/connectors/recurly/transformers.rs`
- `crates/hyperswitch_connectors/src/connec... | {"pr_number": 7497, "pr_title": "feat(connector): Add recovery support for recurly [v2]", "merged_at": "2025-04-08T10:46:18Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors/rec... |
<!-- Describe your changes in detail -->
This pull request introduces a new feature to support an "exploration percentage" parameter in success-based routing configurations and adds a "RoutingApproach" enum to define routing strategies. These changes span multiple files, including API specifications, Rust models, and ... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/open_router.rs`
- `crates/api_models/src/routing.rs`
**2. Core Business Logic**
- `crates/router/src/core/payments/routing.rs`
**3. Tests**
- `cypres... | {"pr_number": 8158, "pr_title": "refactor(success_based): add support for exploration", "merged_at": "2025-05-27T17:51:02Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["merchant", "connector"]}, "hierarchy": {"api_models": ["crates/api_models/src/open_router.rs", "crates/api_model... |
Hotfix for - https://github.com/juspay/hyperswitch/pull/8988
fix message extension , change type of data from string to json | 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/authentication.rs`
**2. Core Business Logic**
- `crates/router/src/core/payments.rs`
- `crates/router/src/co... | {"pr_number": 8975, "pr_title": "refactor: [Netcetera] Handle response deserialization error ", "merged_at": "2025-08-20T07:30:02Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/router_request_types/authentication.rs... |
<!-- Describe your changes in detail -->
data in tokenize flow for tokenex accepts only length of 13-19 chars, we are sending complete card data. | 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/payment_method_data.rs`
- `crates/hyperswitch_domain_models/src/vault.rs`
**2. Core Business Logic**
- `crates/router/src/core/pa... | {"pr_number": 9528, "pr_title": "fix(connector): [Tokenex] fix tokenize flow response handling for tokenex", "merged_at": "2025-09-25T16:22:29Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_mod... |
<!-- Describe your changes in detail -->
This PR adds Cypress tests for validating the existence of card fields are updating the card info in the save card flow.
We cannot directly verify what has been updated in list customer payment method call since only the `globalState` is passed into the command. So, in ord... | 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/cypress/e2e/spec/Payment/00014-SaveCardFlow.cy.js`
- `cypress-tests/cypress/support/commands.js`
**Code Patterns Appl... | {"pr_number": 7743, "pr_title": "ci(cypress): verify if card fields are populated on updating card info", "merged_at": "2025-04-11T07:52:48Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "user"]}, "hierarchy": {"utils": ["cypress-tests/cypress/utils/RequestBo... |
This PR filters the `error_code` and `error_message` in Payments API response to ensure HyperSwitch does not send back any 'invented' codes or messages. This is achieved by filtering such error codes and error messages are not sent back in the API response.
Details in ticket - https://github.com/juspay/hyperswitch/i... | 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/fiuu/transformers.rs`
**Code Patterns Applied:**
-... | {"pr_number": 7801, "pr_title": "chore(payments): filter NO_ERROR_CODE and NO_ERROR_MESSAGE from payments API response", "merged_at": "2025-04-22T17:58:10Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/rou... |
<!-- Describe your changes in detail -->
This PR introduces support for Refunds Retrieve flow and Refunds Sync flow (Rsync) in V2 apis. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/events/refund.rs`
- `crates/api_models/src/refunds.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/refund.rs`
**3. Domain Model... | {"pr_number": 7835, "pr_title": "feat(refunds_v2): Add Refunds Retrieve and Refunds Sync Core flow", "merged_at": "2025-05-07T07:05:31Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/events/refu... |
Add support for traditional chinese locale for payment links
SDK PR https://github.com/juspay/hyperswitch-web/pull/822 | 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": 6745, "pr_title": "feat(payments): [Payment links] Add support for traditional chinese locale for payment links", "merged_at": "2024-12-05T13:37:28Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["cra... |
<!-- Describe your changes in detail -->
Using values in allowed_payment_method_types that were not configured during the creation of the connector results in breaking the SDK flow which shows something went wrong, as the PML call returned an empty payment method list. We need to apply this check during intent creatio... | 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_create.rs`
**2. Other**
- `crates/router/src/routes/metrics.rs`
**Code Patterns Appl... | {"pr_number": 7019, "pr_title": "refactor: check allowed payment method types in enabled options", "merged_at": "2025-01-21T10:22:05Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "user"]}, "hierarchy": {"core_business": ["crates/router/src/core/payments/help... |
<!-- Describe your changes in detail -->
We need to start sending execute_three_d as false in adyen no3ds payments request to skip 3ds auth at adyen ends. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/adyen/transformers.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (4 changes) | {"pr_number": 9339, "pr_title": "feat(connector): [ADYEN ]: send execute_three_d in no3ds adyen", "merged_at": "2025-09-23T14:51:38Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/co... |
<!-- Describe your changes in detail -->
Add V2 payments_cancel flow by endpoint `{{baseUrl}}/v2/payments/:payment_id/cancel`.A payment can be cancelled when the status is RequiresCapture, PartiallyAuthorizedAndRequiresCapture, or PartiallyCapturedAndCapturable. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/events/payment.rs`
- `crates/api_models/src/payments.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/payment_attempt.rs`
**3. D... | {"pr_number": 9083, "pr_title": "feat(router): Add v2 payment cancellation flow", "merged_at": "2025-09-22T18:39:33Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/events/payment.rs", "crates/ap... |
This PR updates the regex used for forming the CompleteAuthorize URL for Worldpay post DDC submission.
Change made - the regex is updated to match any character except `/` for matching the query parameters. Earlier `/w` was being used which matched only the alphanumeric characters and underscore.
Defined in https:/... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Other**
- `crates/router/src/services/api.rs` | {"pr_number": 8027, "pr_title": "fix(core): fix redirection for Worldpay for specific payment IDs", "merged_at": "2025-05-15T12:40:13Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"other": ["crates/router/src/services/api.rs"]}, "... |
<!-- Describe your changes in detail -->
Added Payment Webhooks for Coingate | 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": 7489, "pr_title": "feat(coingate): Add Payment webhooks", "merged_at": "2025-03-21T12:57:19Z", "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 -->
Implemented Payment Method Samsung Pay for connector Bankofamerica | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/bankofamerica/transformers.rs`
**Code Patterns Applied:**
- Define new data structures (3 changes)
- Implement new functions (2 chang... | {"pr_number": 6888, "pr_title": "feat(connector): [BANKOFAMERICA] Implement Samsung Pay", "merged_at": "2025-03-25T07:43:43Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors... |
<!-- Describe your changes in detail -->
Integrate Dwolla connector
Added ACH bank debit flow.
<details>
<summary> Flow </summary>
- Customer Creation - We create a customer using their email ID and receive the customer ID in the response headers.
- Payment Method Token (PMT) - We use the customer ID and ban... | 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. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/errors/api_error_response.rs`
- `crates/hyperswitch_domain_... | {"pr_number": 8586, "pr_title": "feat(connector): [DWOLLA] Connector integration", "merged_at": "2025-08-20T08:01:28Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/enums.rs"], "domain": ["crate... |
Change connector fields that are currently implemented as required in the code to optional - billing address and card holder name are optional fields | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/archipel/transformers.rs`
**Code Patterns Applied:**
- Implement new functions (3 changes)
- Extend existing types with new fields (6... | {"pr_number": 8342, "pr_title": "fix(connector): [ARCHIPEL] Change connector fields that are currently implemented as required in the code to optional", "merged_at": "2025-06-13T13:01:53Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user", "connector"]}, "hierarchy": {... |
<!-- Describe your changes in detail -->
Adding Superposition as an independent module in External Services to abstract the complexity of integrating it with the core application. | 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/configs.rs`
- `crates/router/src/core/payment_methods/cards.rs`
**2. Type Definitions**
- `crates/external_services/src/superpo... | {"pr_number": 9289, "pr_title": "feat: introduce a framework to fetch configs from superposition", "merged_at": "2025-10-09T11:05:38Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user", "card"]}, "hierarchy": {"core_business": ["crates/router/src/core.rs", "crates/router/src/core... |
Hotfix for https://github.com/juspay/hyperswitch/pull/7189 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/fiuu.rs`
**Code Patterns Applied:**
- Implement new functions (2 changes)
- Add conditional logic for feature flags or filtering (2 c... | {"pr_number": 7239, "pr_title": "chore(connector): [Fiuu] log keys in the PSync response", "merged_at": "2025-02-12T06:26:43Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors/fiuu.rs"]}, "change_ty... |
<!-- Describe your changes in detail -->
Template for Tesouro 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/connector_configs/src/connector.rs`
- `crates/connector_c... | {"pr_number": 9555, "pr_title": "feat(connector): [Tesouro] Add template code", "merged_at": "2025-09-25T18:03:31Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/connector_endpoints.rs"], "connectors": ["crates/conne... |
This PR is a part of v2 implementation of refunds. This PR contains the necessary database schema refactoring as well as handling this in the storage_impl crate. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Database Layer (Queries & Schema)**
- `crates/diesel_models/Cargo.toml`
- `crates/diesel_models/src/kv.rs`
- `crates/diesel_models/src/query/refund.rs`
- ... and 3 more files
**2. Type Definitions**
- `... | {"pr_number": 7503, "pr_title": "feat(refunds): Add refunds diesel model support in V2 API", "merged_at": "2025-03-24T11:16:20Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["refund"]}, "hierarchy": {"database": ["crates/diesel_models/Cargo.toml", "crates/diesel_models/src/kv.rs", ... |
<!-- Describe your changes in detail -->
Fix Serde derserialization issue -Elavon/Adyen
updated Serde lib was showing some errors | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/adyen/transformers.rs`
- `crates/hyperswitch_connectors/src/connectors/elavon.rs`
- `crates/hyperswitch_connectors/src/connector... | {"pr_number": 7823, "pr_title": "feat(connector): Fix Serde derserialization issue -Elavon/Adyen", "merged_at": "2025-05-05T10:49:22Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors/adyen/transformer... |
Implement card 3ds flow for Paysafe | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/paysafe.rs`
- `crates/hyperswitch_connectors/src/connectors/paysafe/transformers.rs`
- `crates/hyperswitch_connectors/src/defaul... | {"pr_number": 9305, "pr_title": "feat(connector): [Paysafe] Implement card 3ds flow", "merged_at": "2025-09-11T15:53:05Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors/pay... |
<!-- Describe your changes in detail -->
This PR adds a referer field to the BrowserInformation struct to capture the HTTP Referer header value from client requests. | 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/unified_connector_service/transformers.rs`
**3. Exter... | {"pr_number": 9474, "pr_title": "feat(core): add referer field to browser_info", "merged_at": "2025-09-24T16:51:54Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/router_request_types.rs"... |
Hotfix for https://github.com/juspay/hyperswitch/pull/9277 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payments/routing.rs`
- `crates/router/src/core/payouts.rs`
- `crates/router/src/core/payouts/helpers.rs`
- ... and 1 more files
**Code Patterns Applied:**
- ... | {"pr_number": 9311, "pr_title": "fix(payout): use billing address in payment_methods", "merged_at": "2025-09-09T11:27:30Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"core_business": ["crates/router/src/core/payments/routing.rs", "crates/router/src/core/payouts.... |
<!-- Describe your changes in detail -->
Fixed net_amount on Incremental Authorization Update. Additional amount gets added again during incremental authorization. Additional amount should get added once only during payments-create call | 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_attempt.rs`
**2. Core Business Logic**
- `crates/router/src/core/payments/operations/payment_response.rs`
**Code P... | {"pr_number": 9073, "pr_title": "fix(core): Fix net_amount on Incremental Authorization Update", "merged_at": "2025-09-01T12:44:33Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/paym... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.