prompt stringlengths 6 90.9k | response stringlengths 121 18.6k | metadata stringlengths 314 42.3k |
|---|---|---|
Integ and Sbx payment link urls have **/api/** in their path, which currently gets ignored in the url when payment reaches terminal state
- e.g. url for integ/sbx - https://integ.hyperswitch.io/api/payment_link/merchant_1234/pay_1234?locale=en
- e.g. url for others (does not have /api/) - https://abc.dev.co... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payment_link/payment_link_initiate/payment_link_initiator.js`
- `crates/router/src/core/payment_link/payment_link_initiate/secure_payment_link_initiator.js`
**Code... | {"pr_number": 7232, "pr_title": "fix(payments): [Payment links] Add fix for payment link redirection url", "merged_at": "2025-02-11T11:29:35Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"core_business": ["crates/router/src/core/payme... |
<!-- Describe your changes in detail -->
Pass along request_state to payment_core
Modify the UpdateTracker trait to accept request state
Modify the PaymentReject implementation of UpdateTracker to generate an event | 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_reject.rs`
**2. Other**
- `crates/router/src/events/audit_events.rs`
**Code Patterns Applied:**
- Extend existing types with new field... | {"pr_number": 6465, "pr_title": "feat(events): Add payment reject audit events", "merged_at": "2024-11-12T07:18:54Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment"]}, "hierarchy": {"core_business": ["crates/router/src/core/payments/operations/payment_reject.rs"], "other": [... |
Replaced lazystatic macros with LazyLock
Lazy initialization means that the variable is not initalized at program startup, its initialized when used. This means the variable is created when used first not at a start of a program. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/bitpay.rs`
- `crates/hyperswitch_connectors/src/connectors/digitalvirgo.rs`
- `crates/hyperswitch_connectors/src/connectors/helc... | {"pr_number": 7524, "pr_title": "fix(connector): [JPMORGAN, PAYU, DIGITALVIRGO, BITPAY, HELCIM, PAYBOX] Replaced lazystatic macros with LazyLock", "merged_at": "2025-04-02T13:36:03Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"co... |
<!-- Describe your changes in detail -->
**Payments Eligibility API**
This PR introduces the Payments Eligibility API, which is invoked by the SDK after the payment method data filled event. The API pre-processes the submitted payment method data to determine the appropriate next action and checks eligibility based... | 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. Core Business Logic**
- `crates/router/src/core/blocklist/utils.rs`
- `crates/router/src... | {"pr_number": 9774, "pr_title": "feat(router): add pre-confirm payments eligibility api", "merged_at": "2025-10-16T07:16:20Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user", "card"]}, "hierarchy": {"api_models": ["crates/api_models/src/events/payment.rs", "crates/ap... |
<!-- Describe your changes in detail -->
- Fixed 3DS payments for Shift4.
- Updated shift4 authentication to use the direct secret key from shift4 dashboard, removing the need for manual Base64 encoding.
- Updated error messages for unsupported flows like Void and Partial Captures. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/shift4.rs`
**2. Tests**
- `cypress-tests/cypress/e2e/configs/Payment/Shift4.js`
**Code Patterns Applied:**
- Implement new functi... | {"pr_number": 9480, "pr_title": "fix(connector): [SHIFT4] Fix 3DS payments and api key", "merged_at": "2025-09-24T14:07:54Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user", "card"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors/shift4.r... |
<!-- Describe your changes in detail -->
Add support for record back flow for recurly. | 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/defaul... | {"pr_number": 7544, "pr_title": "feat(connector): [Recurly] Add record back support for recurly [V2]", "merged_at": "2025-03-24T12:01:57Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user", "connector"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/... |
<!-- Describe your changes in detail -->
Since `id` column is introduced as varchar for a few major tracker tables in v2, index creation was missed in v2_compatible_migrations directory. This PR includes that. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Other**
- `v2_compatible_migrations/2025-10-07-131000_add_indexes_on_id_columns/down.sql`
- `v2_compatible_migrations/2025-10-07-131000_add_indexes_on_id_columns/up.sql` | {"pr_number": 9704, "pr_title": "chore: create indexes on required id columns for v2 application", "merged_at": "2025-10-08T15:44:43Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"other": ["v2_compatible_migrations/2025-10-07-131000_add_indexes_on_id_columns/down... |
<!-- Describe your changes in detail -->
This PR changes will convert emails from request to lowercase before performing any DB operations. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Type Definitions**
- `crates/router/src/types/domain/user.rs` | {"pr_number": 6601, "pr_title": "feat(users): Convert emails to lowercase from requests", "merged_at": "2024-11-20T13:41:03Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"types": ["crates/router/src/types/domain/user.rs"]}, "change_types": {}, "has_identifi... |
<!-- Describe your changes in detail -->
Run Cybersource in parallel along with Stripe.
closes #6542 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `.github/workflows/cypress-tests-runner.yml`
**Code Patterns Applied:**
- Extend existing types with new fields (1 changes) | {"pr_number": 6541, "pr_title": "ci: introduce `cybersource` cypress test to run in parallel", "merged_at": "2024-11-14T11:52:04Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"tests": [".github/workflows/cypress-tests-runner.yml"]}, "change_types": {"fields_added... |
<!-- Describe your changes in detail -->
This PR implements a **database-driven enable/disable configuration** for the Unified Connector Service (UCS) integration, providing operators with immediate control to enable or disable UCS without requiring code changes or deployments.
**Key Features Implemented:**
... | 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/helpers.rs`
- `crates/router/src/core/unified_connector_service.rs`
**2. Other**
- `crates/router/src/consts.... | {"pr_number": 8651, "pr_title": "feat(core): Implement UCS kill switch for emergency fallback", "merged_at": "2025-07-22T09:00:55Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "connector", "card"]}, "hierarchy": {"core_business": ["crates/router/src/core/payments.rs", "... |
Add feature_metadata in the payments response for revenue recovery in v2. Also added it in the open api spec | 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/lib.rs`
**3. Core Business Logic**
- `crates/router/src... | {"pr_number": 8667, "pr_title": "feat(payments): Add feature_metadata in the payments response for v2", "merged_at": "2025-07-16T16:48:18Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/payments... |
- Added adaptive timeout scaling__ based on environment detection
- Implemented intelligent retry logic__ with environment-aware configuration
- Enhanced test reliability__ through dynamic timeout adjustments | 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.config.js`
- `cypress-tests/cypress/support/redirectionHandler.js`
**Code Patterns Applied:**
- Extend existi... | {"pr_number": 8942, "pr_title": "ci(cypress): Add adaptive timeout configuration with retry mechanisms", "merged_at": "2025-09-16T12:33:04Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"utils": ["cypress-tests/cypress/utils/RequestBodyUtils.js"], "tests": ["cypre... |
This module implements a **Redis-backed system** for managing and selecting the best **payment processor token** during **payment retries**.
It ensures:
- **Safe** token usage (no race conditions with locks) locked on connector customer level - if a payment has been scheduled then all other invoices for that custom... | 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.rs`
- `crates/hyperswitch_domain_models/src/revenue_recovery.rs`
- `crates/hyperswitch_domain_models/src/router_response_... | {"pr_number": 8846, "pr_title": "feat(revenue_recovery): Add redis-based payment processor token tracking for revenue recovery", "merged_at": "2025-08-25T09:44:24Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"domain": ["crates/hy... |
This PR adds below changes for the Worldpay connector
1. Add a root CA certificate for Worldpay's request client
2. Add a new AuthType for Worldpay - MultiAuthType
3. Use `MultiAuthType` in wasm crate for Worldpay | 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": 8205, "pr_title": "fix(connector): [Worldpay] add root CA certificate", "merged_at": "2025-06-02T11:44:49Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["connector"]}, "hierarchy": {"connectors": ["crates/connector_configs/toml/development.toml", "crates/connector_con... |
<!-- Describe your changes in detail -->
This PR introduces two new API:-
1) To get data from Redis for monitoring purpose **v2/recovery/data-backfill/redis-data/:id?key_type=Status**
2) To update additional token data(error code, hard decline flag and schedule at fields) **v2/recovery/data-backfill/update-token** | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/revenue_recovery_data_backfill.rs`
**2. Core Business Logic**
- `crates/router/src/core/revenue_recovery_data_backfill.rs`
**3. Type Definitions**
- `cr... | {"pr_number": 9611, "pr_title": "feat(revenue_recovery): add support to fetch data and update additional token data in redis", "merged_at": "2025-10-01T15:38:04Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "user"]}, "hierarchy": {"api_models": ["crates/api_... |
Add Tsys, Square connector to cypress test suits.
## How did you test it?
<img width="502" alt="Screenshot 2025-07-03 at 3 30 26 PM" src="https://github.com/user-attachments/assets/95fb08b1-bccb-45f1-816e-f39da4e473fe" />
<img width="462" alt="Screenshot 2025-07-03 at 4 06 24 PM" src="https://github.com/user-atta... | To implement this **connector_integration** feature, you'll need to modify these architectural layers:
**1. Tests**
- `cypress-tests/cypress/e2e/configs/Payment/Square.js`
- `cypress-tests/cypress/e2e/configs/Payment/Tsys.js`
- `cypress-tests/cypress/e2e/configs/Payment/Utils.js`
**Code Patterns Applied:**
... | {"pr_number": 8543, "pr_title": "ci(cypress): Add Tsys,Square cypress test", "merged_at": "2025-07-07T11:16:07Z", "intent": {"feature_type": "connector_integration", "action": "add_feature", "entities": ["user", "connector"]}, "hierarchy": {"tests": ["cypress-tests/cypress/e2e/configs/Payment/Square.js", "cypress-tests... |
<!-- Describe your changes in detail -->
This PR addresses the clippy lints occurring due to new rust version 1.84.0
Majorly addresses `unnecessary_map_or` clippy lint - https://rust-lang.github.io/rust-clippy/master/index.html#unnecessary_map_or | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/query/address.rs`
**2. Core Business Logic**
- `crates/router/src/core/admin.rs`
- `crates/router/src/core/blocklist/transformers.rs`
- `crat... | {"pr_number": 7021, "pr_title": "chore: address Rust 1.84.0 clippy lints", "merged_at": "2025-01-15T13:17:35Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"database": ["crates/diesel_models/src/query/address.rs"], "core_business": ["crates/router/src/core/a... |
This PR adds a validation for `return_url` when creating payment links. Return URL must be a required parameter as payment links is client side facing and needs to be redirected to an end URL post payment completion. | 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`
**Code Patterns Applied:**
- Extend existing types with new fields (3 changes... | {"pr_number": 7802, "pr_title": "fix(payment_link): add validation for return_url during payment link creation", "merged_at": "2025-04-12T15:04:20Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/... |
<!-- Describe your changes in detail -->
Move cybersource, bankofamerica, wellsfargo code to crate hyperswitch_connectors. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/types.rs`
**2. Core Business Logic**
- `crates/router/src/core/payments/connector_integration_v2_impls.rs`
- `crates/router/src/c... | {"pr_number": 6908, "pr_title": "refactor: [CYBERSOURCE, BANKOFAMERICA, WELLSFARGO] Move code to crate hyperswitch_connectors", "merged_at": "2025-01-22T18:23:12Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["connector"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models... |
Propagation request-id to chat service for consistency.
Propagate chat session id as well in request
Add count metric for chat api | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/chat.rs`
**2. Utils**
- `crates/common_utils/src/consts.rs`
**3. Other**
- `crates/router/src/routes/chat.rs`
- `crates/router/src/routes/metrics.rs`
**Cod... | {"pr_number": 8680, "pr_title": "fix(chat): append request id to headers for chat request", "merged_at": "2025-07-25T07:27:38Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user", "session"]}, "hierarchy": {"core_business": ["crates/router/src/core/chat.rs"], "utils": ["crates/com... |
<!-- Describe your changes in detail -->
There will be a mapping of email domain and auth methods.
This PR will restrict users to enter into the dashboard based on the email domain. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/user.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/query/user_authentication_method.rs`
- `crates/diesel_models/src/schema.rs`... | {"pr_number": 6940, "pr_title": "feat(users): Add email domain based restriction for dashboard entry APIs", "merged_at": "2024-12-30T07:37:08Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"api_models": ["crates/api_models/src/user.rs"], "database": ["crates... |
- Template Code for addition of new connector Moneris | 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/common_enums/src/connec... | {"pr_number": 7216, "pr_title": "feat(connector): [Moneris] add template code", "merged_at": "2025-02-13T10:29:15Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["connector"]}, "hierarchy": {"core_business": ["crates/router/src/core/payments/connector_integration_v2_impls.rs", "crat... |
This PR enables reading NTI from Novalnet's payments response. And also updates the integration for raw card + NTI flow. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/novalnet/transformers.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (5 changes) | {"pr_number": 9337, "pr_title": "feat(connector): [Novalnet] read and send scheme_tid for NTI flows", "merged_at": "2025-09-16T12:08:30Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/sr... |
<!-- Describe your changes in detail -->
This PR removes the open-router configuration from docker_compose.toml | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Configuration Files**
- `config/docker_compose.toml` | {"pr_number": 7885, "pr_title": "fix(config): remove open-router configuration from docker compose toml", "merged_at": "2025-04-25T07:11:05Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"config": ["config/docker_compose.toml"]}, "change_types": {}, "has_identifie... |
Added `get-intent` API for payments | 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. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/router_flow_... | {"pr_number": 6396, "pr_title": "feat(router): Add payments get-intent API for v2", "merged_at": "2024-10-30T16:28:52Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/events/payment.rs", "crates/... |
<!-- Describe your changes in detail -->
Update readme with vision, product offering, architecture diagram, setup steps and output | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Other**
- `README.md`
- `docs/imgs/features.png`
- `docs/imgs/hyperswitch-architecture-v1.png`
- ... and 1 more files | {"pr_number": 7024, "pr_title": "chore: Update readme with juspay's vision, product offering, architecture diagram, setup steps and output", "merged_at": "2025-01-17T11:28:54Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"other": ["README.md", "docs/imgs/features... |
Renamed the spec file | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `cypress-tests/cypress/e2e/spec/Payment/00029-IncrementalAuth.cy.js`
- `cypress-tests/cypress/e2e/spec/Payment/00028-DynamicFields.cy.js` | {"pr_number": 9786, "pr_title": "ci(cypress): fix paypal cypress", "merged_at": "2025-10-10T11:30:11Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user", "connector"]}, "hierarchy": {"tests": ["cypress-tests/cypress/e2e/spec/Payment/00029-IncrementalAuth.cy.js", "cypress-tests/cy... |
<!-- Describe your changes in detail -->
Added coingate, paystack connector specifications | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/coingate.rs`
- `crates/hyperswitch_connectors/src/connectors/paystack.rs`
**2. Tests**
- `config/deployments/integration_test.t... | {"pr_number": 7996, "pr_title": "feat(connector): add coingate, paystack connector specifications", "merged_at": "2025-05-15T11:57:04Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "refund", "connector"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/c... |
<!-- Describe your changes in detail -->
Paystack template PR.
Follow the steps outlined in the add_connector.md file. Execute the script provided in the markdown file, then run the following commands:
cargo clippy
cargo +nightly fmt --all | 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/connector_integration_v2_impls.rs`
- `crates/router/src/core/payments/flows.rs`
**2. External Connector Integration... | {"pr_number": 7285, "pr_title": "feat(connector): [PAYSTACK] Template PR", "merged_at": "2025-02-27T09:26:22Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["connector"]}, "hierarchy": {"core_business": ["crates/router/src/core/admin.rs", "crates/router/src/core/payments/connector_i... |
<!-- Describe your changes in detail -->
<img width="861" alt="image" src="https://github.com/user-attachments/assets/d85ea702-cd5d-444b-86bd-1f5f50363d40" />
connector throws above error when using VISA card. Replacing that with MasterCard fixes it:
<img width="1206" alt="image" src="https://github.com/user-a... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `cypress-tests/cypress/e2e/configs/Payment/Paypal.js`
**Code Patterns Applied:**
- Extend existing types with new fields (2 changes) | {"pr_number": 7491, "pr_title": "ci(cypress): fix paypal failures", "merged_at": "2025-03-12T08:00:38Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user", "connector"]}, "hierarchy": {"tests": ["cypress-tests/cypress/e2e/configs/Payment/Paypal.js"]}, "change_types": {"... |
Reverts juspay/hyperswitch#7856 | To implement this **unknown** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/noon.rs`
- `crates/hyperswitch_connectors/src/connectors/noon/transformers.rs`
**Code Patterns Applied:**
- Define new data structures (... | {"pr_number": 7860, "pr_title": "revert: fix(connector): [noon] address `next_action_url` being `null` for cards in 3ds payment", "merged_at": "2025-04-21T14:52:28Z", "intent": {"feature_type": "unknown", "action": "unknown", "entities": []}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors/no... |
<!-- Describe your changes in detail -->
This PR adds support for connector testing data in payment requests, specifically for Adyen connector. It allows merchants to send testing values via `connector_metadata` to simulate different scenarios in the sandbox environment.
The implementation includes:
1. Added a new... | 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. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/router_request_types.rs`
**3. Core Business Logic**
- `crates... | {"pr_number": 7874, "pr_title": "feat(payments): add support for connector testing (Adyen)", "merged_at": "2025-04-24T15:31:10Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/payments.rs"], "domain": ... |
<!-- Describe your changes in detail -->
hotfix pr for https://github.com/juspay/hyperswitch/pull/6665
Currently in payment link after redirection in case of non 3ds, we return to merchant url with following query params
- payment id, status
But for non 3ds we return to merchant url with following query params... | 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` | {"pr_number": 6669, "pr_title": "fix(core): add payment_id as query param in merchant return url", "merged_at": "2024-11-27T06:52:16Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"core_business": ["crates/router/src/core/payments/help... |
1.Enhanced Fiserv Connector in cypress for Comprehensive Testing
2.Fixed the Fallback scenarios for mandates:
- When Hyperswitch attempts to process a payment as "off_session" (saved card payment without customer present), some connectors like Fiserv don't fully support this flow and fall back to "on_session" process... | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. Tests**
- `cypress-tests/cypress/e2e/configs/Payment/Fiserv.js`
- `cypress-tests/cypress/e2e/configs/Payment/Utils.js`
- `cypress-tests/cypress/support/commands.js`
**Code Patterns Applied:**
- Extend existing type... | {"pr_number": 8171, "pr_title": "ci(cypress): Added Fiserv Connector Test", "merged_at": "2025-06-03T07:34:40Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["customer", "payment", "user"]}, "hierarchy": {"tests": ["cypress-tests/cypress/e2e/configs/Payment/Fiserv.js", "cypress-tests/cypr... |
<!-- Describe your changes in detail -->
For connector Datatrans add new payment status: ChallengeOngoing and ChallengeRequired | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/datatrans/transformers.rs` | {"pr_number": 7327, "pr_title": "fix(connector): [DATATRANS] Add new payment status", "merged_at": "2025-02-20T17:43:47Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors/dat... |
<!-- Describe your changes in detail -->
This PR fixes payment redirects in v2. This was due to the field merchant_connector_details set as todo!() | 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) | {"pr_number": 8405, "pr_title": "fix: Payments redirects for v2", "merged_at": "2025-06-23T08:03:51Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core/payments.rs"]}, "change_types": {"fields_a... |
<!-- Describe your changes in detail -->
Moving db interfaces in router crate to hyperswitch_domain_models and its implementation is added in storage_impl
**Refactored Interfaces**
1. MerchantAccount
2. MerchantConnectorAccount
3. MerchantKeyStore
4. BusinessProfile
5. Configs
Also, moving the execute_con... | 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/business_profile.rs`
- `crates/hyperswitch_domain_models/src/configs.rs`
- `crates/hyperswitch_domain_models/src/customer.rs`
-... | {"pr_number": 9830, "pr_title": "refactor(db_interfaces): move db interfaces in router to domain_models", "merged_at": "2025-10-15T07:33:48Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models... |
<!-- Describe your changes in detail -->
This PR introduces lineage context caching to enhance login and account-switch flows with better continuity and reduced DB load. | 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/types/domain/user.rs`
- `crates/router/src/types/domain/user/decision_manager.rs`
**3. Utils**
- `crat... | {"pr_number": 7871, "pr_title": "feat(users): add support for caching and resolving last used lineage context", "merged_at": "2025-04-23T14:09:48Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["merchant", "user", "session"]}, "hierarchy": {"core_business": ["crates/router/src/core/... |
<!-- Describe your changes in detail -->
Newline in billing address failing the payment in production (speculated). This pr removes the newline (if present) in billing address with space. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/router/src/connector/cybersource/transformers.rs`
**Code Patterns Applied:**
- Implement new functions (3 changes)
- Extend existing types with new fields (6 changes) | {"pr_number": 6478, "pr_title": "fix(connector): [Cybersource] remove newline in billing address with space", "merged_at": "2024-11-05T10:39:42Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/router/src/connec... |
<!-- Describe your changes in detail -->
https://github.com/juspay/hyperswitch/pull/7705 | 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/helpers.rs`
- `crates/router/src/core/unified_authentication_service.rs`
**3.... | {"pr_number": 7714, "pr_title": "refactor(core): made provider field in ctp_service_details backward compatible", "merged_at": "2025-04-03T11:10:42Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"api_models": ["crates/api_models/src/payments.rs"], "core_business":... |
<!-- Describe your changes in detail -->
Paypal requires creation of access token before payment/payouts in its flow.
In Access token flow, we do get error response
```
PaypalAccessTokenErrorResponse { error: \"invalid_client\", error_description: \"Client Authentication failed\" }
```
The error response gets upd... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payouts.rs`
- `crates/router/src/core/payouts/helpers.rs`
**Code Patterns Applied:**
- Implement new functions (1 changes)
- Extend existing types with new fields ... | {"pr_number": 9531, "pr_title": "fix(payouts): add should_continue flag for propagating error for each call", "merged_at": "2025-10-10T07:57:50Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/cor... |
This PR adds support for propagating the wallet details during MIT txns for PayPal. This ensures PayPal is propagated with same wallet details during CIT and MIT which in turn ensures the return type for `payment_method_data` is same for CIT and MIT.
**Notes**
- `address_id` is not propagated during MIT today. Trac... | 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_create.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (7 changes)
**Detailed Identifier Changes:**
Commit 75947... | {"pr_number": 7423, "pr_title": "refactor(payment_methods): propagate empty wallet details for paypal \u2026", "merged_at": "2025-03-04T13:41:10Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/co... |
<!-- Describe your changes in detail -->
- Removed the unwanted changes (like addition of conector_name in RoutableConnectors enum, etc)
- Amount convertor code is generated in the template
- Connector Specification is also added in the template
- Network error codes added
- validate_mandate_payment, validate_ps... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `connector-template/mod.rs`
- `connector-template/test.rs`
- `connector-template/transformers.rs`
- ... and 2 more files
**Code Patterns Applied:**
- Implement new functi... | {"pr_number": 8213, "pr_title": "refactor(connector): update add connector script with new connector features", "merged_at": "2025-07-01T14:47:37Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user", "order"]}, "hierarchy": {"connectors": ["connector-template/mod.rs", "... |
Hotfix for https://github.com/juspay/hyperswitch/pull/7427 | 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": 7442, "pr_title": "feat(payment_link): expose payment link configs for SDK UI rules and payment button", "merged_at": "2025-03-06T11:27:39Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment"]}, "hierarchy": {"api_models": ["crates/api_models/src/admin.rs", "crate... |
Refactoring to recieve json response instead of string
Updated `ConfigApiClient::send_decision_engine_request` calls in `crates/router/src/core/routing/helpers.rs` to return `serde_json::Value` instead of `String`.
This ensures the response is parsed as JSON for better type safety and avoids manual string-to-JSON... | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/routing/helpers.rs`
**Code Patterns Applied:**
- Modify database queries (1 changes) | {"pr_number": 8965, "pr_title": "refactor(routing): receive json value instead of string", "merged_at": "2025-09-03T12:58:02Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"core_business": ["crates/router/src/core/routing/helpers.rs"]}, "cha... |
<!-- Describe your changes in detail -->
add infra-values in intent kafka events
cluster populating in payment_intent kafka event
<img width="1327" alt="image" src="https://github.com/user-attachments/assets/f1a57f86-b657-4eec-a0e4-d2eee6d29e78" />
Ran clippy locally
<img width="1056" alt="image" src="https://... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Type Definitions**
- `crates/common_utils/src/types/keymanager.rs`
- `crates/router/src/types/domain/types.rs`
**2. Other**
- `crates/router/src/db/kafka_store.rs`
- `crates/router/src/services/kafka.rs`
... | {"pr_number": 8265, "pr_title": "refactor: add infra-values in intent kafka events", "merged_at": "2025-06-05T10:58:30Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user"]}, "hierarchy": {"types": ["crates/common_utils/src/types/keymanager.rs", "crates/router/src/types... |
<!-- Describe your changes in detail -->
This PR introduces the payment methods list endpoint for payments. Only the initial structure is introduced in this PR.
<!--
Provide links to the files with corresponding changes.
Following are the paths where you can find config files:
1. `config`
2. `crates/router/sr... | 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/events/payment.rs`
- `crates/api_models/src/payment_methods.rs`
- ... and 1 more files
**2. Database Layer (Queries... | {"pr_number": 6805, "pr_title": "feat(payments_v2): add payment method list endpoint", "merged_at": "2024-12-23T10:43:44Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "user"]}, "hierarchy": {"api_models": ["crates/api_models/src/admin.rs", "crates/api_models... |
<!-- Describe your changes in detail -->
CUG Hotfix for [9444](https://github.com/juspay/hyperswitch/pull/9444) | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/cybersource/transformers.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (2 changes) | {"pr_number": 9513, "pr_title": "fix(connector): [CYBERSOURCE] Pass transaction type for only wallet MITs", "merged_at": "2025-09-23T11:32:36Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors/cybersou... |
<!-- Describe your changes in detail -->
Add single use token implementation for Payment Method Service
The feature would help to provide a single use PSP token for creating payment | 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_method_data.rs`
**3. Core Business Logic**
... | {"pr_number": 7485, "pr_title": "feat(payment_methods_v2): single use token implementation", "merged_at": "2025-04-01T12:37:38Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/payment_methods.rs"... |
Add support for hard-decline switch for revenue-recovery service. If we encounter a hard-decline we would not call the external service . This PR also adds support for gsm apis in v2 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/revenue_recovery/types.rs`
**2. Type Definitions**
- `crates/router/src/types/storage/revenue_recovery.rs`
**3. Other**
- `api-reference/v1/openapi_spec_v1.jso... | {"pr_number": 8879, "pr_title": "feat(revenue): Add support for hard-decline switch for revenue-recovery service", "merged_at": "2025-08-21T18:16:12Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user", "connector"]}, "hierarchy": {"core_business": ["crates/router/src/core/revenue... |
<!-- Describe your changes in detail -->
Added an enum `V2Auth` (name subject to change) to encapsulate different authentication scenarios. Currently only works for Client Authentication using `publishable_key` and `ephemeral_key` in `Authorization` header | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/ephemeral_key.rs`
- `crates/api_models/src/events/payment.rs`
- `crates/api_models/src/payment_methods.rs`
- ... and 2 more files
**2. Database Layer ... | {"pr_number": 7038, "pr_title": "feat(router): [V2] Introduce V2Auth and use it for payment_methods_list_enabled", "merged_at": "2025-01-31T08:37:18Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/s... |
<!-- Describe your changes in detail --> | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payments.rs`
**2. External Connector Integration**
- `crates/common_enums/src/connector_enums.rs`
- `crates/hyperswitch_connectors/src/connectors/nuvei/transfor... | {"pr_number": 9468, "pr_title": "feat(connector): [Nuvei] Add Support for External 3DS Auth ", "merged_at": "2025-09-22T18:35:56Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core/payments.rs"]... |
<!-- Describe your changes in detail --> | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Other**
- `api-reference/logo/dark.svg`
- `api-reference/logo/light.svg`
- `docs/imgs/hyperswitch-logo-dark.svg`
- ... and 1 more files | {"pr_number": 6741, "pr_title": "docs: Updating logo for Api ref", "merged_at": "2024-12-05T11:09:38Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"other": ["api-reference/logo/dark.svg", "api-reference/logo/light.svg", "docs/imgs/hyperswitch-logo-dark.svg", "doc... |
<!-- Describe your changes in detail -->
Add payment id in authentication router data
This change is done to populate payment id in clickhouse authentication table and kafka to get authentication analytics since analytics is dependent on payment_id.
## How did you test it?
<!--
Did you write an integration/uni... | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/authentication.rs`
- `crates/router/src/core/authentication/transformers.rs`
- `crates/router/src/core/authentication/utils.rs`
- ... and 2 more files
**Code Patte... | {"pr_number": 7441, "pr_title": "refactor(core): Added payment id in authentication router data", "merged_at": "2025-03-06T11:08:41Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["payment", "user"]}, "hierarchy": {"core_business": ["crates/router/src/core/authentication.rs", "crates/rout... |
This PR adds an Audit event for the PaymentUpdate operation. | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payments/operations/payment_update.rs`
**2. Other**
- `crates/router/src/events/audit_events.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (3 c... | {"pr_number": 6426, "pr_title": "feat(payments): Add audit events for PaymentUpdate update", "merged_at": "2024-11-08T13:37:22Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["customer", "payment", "user"]}, "hierarchy": {"core_business": ["crates/router/src/core/payments/operations/payme... |
<!-- Describe your changes in detail -->
add `merchant_configuration_id` in netcetera metadata and make other merchant configurations optional
This would allow merchant to do the required configuration on netcetera dashboard, and just provide us the merchant_configuration_id to process the payment authentications | 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": 7347, "pr_title": "feat(router): add `merchant_configuration_id` in netcetera metadata and make other merchant configurations optional", "merged_at": "2025-02-21T19:52:15Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant"]}, "hierarchy": {"core_busin... |
<!-- Describe your changes in detail -->
This PR includes minor refactors and improvements to our CI workflows:
1. The Docker build workflow files are not being used, and have been removed.
2. The connector sanity and UI sanity workflows are not being actively used. I didn't want to remove them completely, so in... | To implement this **connector_integration** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `.github/workflows/connector-sanity-tests.yml`
- `.github/workflows/connector-ui-sanity-tests.yml`
**2. Tests**
- `.github/workflows/cypress-tests-runner.yml`
**3. ... | {"pr_number": 7308, "pr_title": "ci: minor refactors and improvements", "merged_at": "2025-02-24T22:05:59Z", "intent": {"feature_type": "connector_integration", "action": "add_feature", "entities": ["connector"]}, "hierarchy": {"connectors": [".github/workflows/connector-sanity-tests.yml", ".github/workflows/connector-... |
<!-- Describe your changes in detail -->
Moved `merchant_key_store` table to accounts schema.
Since `merchant_account` is already moved to schema. `merchant_key_store` must also be present there.
Other changes:
* introduced `ShouldCollectCvvDuringPayment` bool wrapper for `should_collect_cvv_during_payment` colum... | 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_v2.rs`
**3. Domai... | {"pr_number": 7746, "pr_title": "refactor: move merchant_key_store table to accounts schema", "merged_at": "2025-04-08T12:20:57Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/admin.rs"], "datab... |
This PR fixes the missing additional payout method details in the response when using stored payment methods (via PSP tokens) for processing payouts. | 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/payouts.rs`
**Code Patterns Applied:**
- Implement new... | {"pr_number": 9426, "pr_title": "fix(payouts): populate additional payout method data during recurring payouts", "merged_at": "2025-09-18T14:29:16Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain... |
<!-- Describe your changes in detail -->
Added logs for routing engine. | 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/routing.rs` | {"pr_number": 8962, "pr_title": "refactor(euclid): add logs for euclid routing", "merged_at": "2025-08-18T14:59:20Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"core_business": ["crates/router/src/core/payments.rs", "crates/router/src/core/payments/routing.rs"]}... |
<!-- Describe your changes in detail -->
This PR fixes an inconsistency in the redis `key_prefix` that was used when invalidating the cache entries which affected all the cache types (configs, accounts, routing, etc).
The `delete_key` redis call during cache invalidation was using `global` as the `key_prefix` (key li... | 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/cache.rs`
- `crates/router/src/core/routing.rs`
- ... and 1 more files
**2. Configuration Files**
- `crates/router/src... | {"pr_number": 6976, "pr_title": "fix(cache): address in-memory cache invalidation using global tenant as `key_prefix`", "merged_at": "2025-01-03T08:18:56Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"core_business": ["crates/router/src/core/admin.rs", "cra... |
hotfix for https://github.com/juspay/hyperswitch/pull/6789 | 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 (3 changes) | {"pr_number": 6795, "pr_title": "feat(payments): [Payment links] Add locale case fix", "merged_at": "2024-12-10T15:38:40Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"core_business": ["crates/router/src/core/payment_link/locale.js"]}, "change_types": {"fields_ad... |
<!-- Describe your changes in detail -->
Added Wasm changes for Datatrans (acquirer_country_code,acquirer_merchant_id,acquirer_bin) | 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": 7229, "pr_title": "feat(connector): [Datatrans] Add Wasm Changes ", "merged_at": "2025-02-10T08:58:34Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["merchant"]}, "hierarchy": {"connectors": ["crates/connector_configs/toml/development.toml", "crates/connector_configs/... |
<!-- Describe your changes in detail -->
Parent issue describing the feature (https://github.com/juspay/hyperswitch/issues/6841)
We need to rename `management_url` to `management_u_r_l` in the apple pay session response as our sdk converts the apple pay session request to camelCase before sending it to the apple pa... | 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/transformers.rs`
**3. Other**
- `api-reference-v2/openapi_spec.json`
- `ap... | {"pr_number": 6945, "pr_title": "fix(router): rename `management_url` to `management_u_r_l` in the apple pay session response", "merged_at": "2024-12-27T06:46:27Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates... |
<!-- Describe your changes in detail --> | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payments/flows/session_flow.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (1 changes) | {"pr_number": 6311, "pr_title": "fix(router): replace underscore by hyphen in Samsung pay session call", "merged_at": "2024-10-14T17:19:38Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core/pay... |
<!-- Describe your changes in detail -->
Supported capture methods fix for feature matrix. This change is done for connector `Itaubank` and `Nuvei`. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/itaubank.rs`
- `crates/hyperswitch_connectors/src/connectors/nuvei.rs` | {"pr_number": 8057, "pr_title": "fix(connector): Supported capture methods fix for feature matrix", "merged_at": "2025-05-20T10:44:25Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/... |
<!-- Describe your changes in detail -->
This pull request includes a minor improvement to error message formatting in the `build_unified_connector_service_payment_method` function.
* [`crates/router/src/core/unified_connector_service.rs`](diffhunk://#diff-b8e808846f58e455687a9e192c1c8d192598081aac942628640c42c1d39... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payment_methods/vault.rs`
- `crates/router/src/core/unified_connector_service.rs` | {"pr_number": 8607, "pr_title": "chore: address Rust 1.88.0 clippy lints", "merged_at": "2025-07-10T15:38:02Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "connector"]}, "hierarchy": {"core_business": ["crates/router/src/core/payment_methods/vault.rs", "crates/router/sr... |
Add Payment connector template for Worldpayvantiv.
Hotfix PR for https://github.com/juspay/hyperswitch/pull/8226
Worldpay Vantiv, also known as the Worldpay CNP API, is a robust XML-based interface used to process online (card-not-present) transactions such as e-commerce purchases, subscription billing, and digi... | 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. Core Business Logic**
- `crates/router/src/core/admin.rs`
**3. External Connector Integration**
- `crates/common_enum... | {"pr_number": 8245, "pr_title": "feat(connectors): [Template] add Worldpayvantiv ", "merged_at": "2025-06-05T05:31:47Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["payment", "connector", "card"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/configs.rs"], "core_busine... |
<!-- 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": 8253, "pr_title": "feat(events): adding infra level components to api-events", "merged_at": "2025-06-05T06:17:41Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"core_business": ["crates/router/src/core/webhooks/incoming.rs", "crates/router/src/... |
<!-- Describe your changes in detail -->
add custom header to connector call for hitting sandbox custom pod | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/hyperswitch_vault.rs`
- `crates/hyperswitch_connectors/src/constants.rs` | {"pr_number": 8471, "pr_title": "fix(payment-method): add custom header to connector call for hitting sandbox custom pod", "merged_at": "2025-06-26T10:59:25Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["connector"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src... |
<!-- Describe your changes in detail -->
add api_models and openapi changes for refunds create api v2 | 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/Cargo.toml`
- `crates/diesel_m... | {"pr_number": 6385, "pr_title": "feat(router): add api_models and openapi changes for refunds create api v2", "merged_at": "2024-10-23T11:49:07Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user", "refund"]}, "hierarchy": {"api_models": ["crates/api_models/src/events/refund.rs", ... |
<!-- Describe your changes in detail -->
Add support to paysera and skrill PMs and shift4 | 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": 8487, "pr_title": "feat(payment_methods): [Paysera, Skrill] Add support to paysera and skrill wallets and in shift4 ", "merged_at": "2025-07-15T08:13:50Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["c... |
To consume transaction id for some error cases , where currently its not consumed. This PR addresses this issue. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/fiuu/transformers.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (12 changes) | {"pr_number": 6998, "pr_title": "feat(connector): [Fiuu] Consume transaction id for error cases for Fiuu", "merged_at": "2025-01-07T08:04:42Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connecto... |
Enhanced Nuvei Connector in cypress for Comprehensive Testing.
## How did you test it?
<img width="685" alt="Screenshot 2025-06-21 at 3 53 16 AM" src="https://github.com/user-attachments/assets/298be3ca-e563-4b30-ab7a-6c2259c8996a" />## Checklist
<!-- Put an `x` in the boxes that apply -->
- [ ] I formatted... | To implement this **connector_integration** feature, you'll need to modify these architectural layers:
**1. Tests**
- `cypress-tests/cypress/e2e/configs/Payment/Nuvei.js`
- `cypress-tests/cypress/e2e/configs/Payment/Utils.js`
- `cypress-tests/cypress/support/redirectionHandler.js`
**Code Patterns Applied:**... | {"pr_number": 8414, "pr_title": "ci(cypress): Add Nuvei connector test in cypress", "merged_at": "2025-07-15T12:05:53Z", "intent": {"feature_type": "connector_integration", "action": "add_feature", "entities": ["user", "connector"]}, "hierarchy": {"tests": ["cypress-tests/cypress/e2e/configs/Payment/Nuvei.js", "cypress... |
<!-- Describe your changes in detail -->
Adding Cypress Test Case Flows related Configs for the `Braintree` Payment Processor.
~_Note: The Connector Update Test will fail until https://github.com/juspay/hyperswitch/pull/7622 is not merged to the `main` branch._~ (#7622 is Merged) | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `cypress-tests/cypress/e2e/configs/Payment/Braintree.js`
- `cypress-tests/cypress/e2e/configs/Payment/Utils.js`
- `cypress-tests/cypress/support/commands.js`
**Code Patterns Applied:**
- Extend exis... | {"pr_number": 7266, "pr_title": "ci(cypress): add Braintree connector configs for cypress test flows", "merged_at": "2025-04-24T07:23:48Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user", "connector"]}, "hierarchy": {"tests": ["cypress-tests/cypress/e2e/configs/Payme... |
<!-- Describe your changes in detail -->
Add worldpay vantiv as a payment connector. Integrated non 3ds cards flow.
> Note: Report Group for each transaction is collected from the payment's metadata. If not provided - then the default report group provided in the MCA is used
> Note: Currency for the transacti... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/admin.rs`
**2. External Connector Integration**
- `crates/common_enums/src/connector_enums.rs`
- `crates/connector_configs/src/connector.rs`
- `crates/connec... | {"pr_number": 8219, "pr_title": "feat(connectors): [Worldpayvantiv] add card support", "merged_at": "2025-06-04T14:32:32Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core/admin.rs"], "connecto... |
<!-- Describe your changes in detail -->
This pull request introduces several enhancements and refactors to the subscription API, focusing on improving authentication, response structure, and data handling. The main changes include adding payment and invoice details to subscription responses, updating authentication l... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/subscription.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/invoice.rs`
- `crates/diesel_models/src/schema.rs`
- `crates/die... | {"pr_number": 9713, "pr_title": "feat(subscriptions): Add client secret auth support in subscriptions APIs", "merged_at": "2025-10-08T15:44:43Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/sub... |
<!-- Describe your changes in detail --> | 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/admin.rs`
- `crates/router/src/core/payments/transformers.rs`
**3. External Connector ... | {"pr_number": 8463, "pr_title": "feat(connector): [SANTANDER] Added Authorize, PSync, Void, Refund & RSync Flows for Pix QR Code Bank Transfer ", "merged_at": "2025-07-01T14:51:00Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"api_models": ["crates/api_mode... |
<!-- Describe your changes in detail -->
The total count in the payments response was incorrect when the card-network filter was applied. With this PR, the count will now be accurately filtered as well. | 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/query/payment_attempt.rs`
**3. Domain Models (Business Logic Types)**
... | {"pr_number": 6397, "pr_title": "fix(payments): filter total count by card-network value", "merged_at": "2024-10-24T14:32:45Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/payments.rs"], "datab... |
- Modified `parse_value` method in `ValueExt` trait to log the JSON object after masking on deserialization failure.
- Modified `parse_struct` method in `BytesExt`, `ByteSliceExt` and `StringExt` to log values after converting them into a `serde_json::Value` and then masking | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Utils**
- `crates/common_utils/src/ext_traits.rs` | {"pr_number": 8970, "pr_title": "fix(common_utils): Prevent logging sensitive information on deserialization failure", "merged_at": "2025-09-24T13:24:48Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"utils": ["crates/common_utils/src/ext_traits.rs"]}, "chan... |
- implement session update flow for Paypal
- implement post_update_tracker for SessionUpdate Flow
hotfix for [PR](https://github.com/juspay/hyperswitch/pull/6299) | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/payments.rs`
**2. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/router_request_types.rs`
- `crates/hyperswitch_domain_mo... | {"pr_number": 6328, "pr_title": "feat(router): implement post_update_tracker for SessionUpdate Flow and add support for session_update_flow for Paypal", "merged_at": "2024-10-15T20:37:06Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy"... |
<!-- Describe your changes in detail -->
Hotfix PR
Original PR: [https://github.com/juspay/hyperswitch/pull/7782](https://github.com/juspay/hyperswitch/pull/7782) | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/query/merchant_account.rs`
**Code Patterns Applied:**
- Modify database queries (3 changes) | {"pr_number": 7788, "pr_title": "refactor(users): modify query to list only v1 merchant_accounts for list v1 merchant accounts API", "merged_at": "2025-04-10T14:12:38Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"database": ["crates/diesel_models/src/query/merch... |
1. Added config `skip_status_screen` in payment links to decide whether to skip status screen after payment completion
- If config is true user will be redirected to return url directly
- If config is false,or not passed redirect user to status screen and then to return url `(default flow)`
2. Added config `bac... | 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": 7410, "pr_title": "feat(payments): [Payment links] add configs for payment link", "merged_at": "2025-03-03T17:25:06Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/admin.rs", "crat... |
<!-- Describe your changes in detail -->
Due to redis lock being held for a long time, which made the forex api-calls synchronous, we had to re-frame the way how things were being operated for forex rates fetch, The changes includes:
1. Acquiring redis lock, just before api-call and releasing it once data is written ... | 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. Utils**
- `crates/router/src/utils/currency.rs`
**3. Tests**
- `loadtest/config/development.toml`
**4. Configuration Files**
- `config/co... | {"pr_number": 6906, "pr_title": "refactor(currency_conversion): re frame the currency_conversion crate to make api calls on background thread", "merged_at": "2025-01-28T18:59:14Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"core_business": ["crates/router/... |
<!-- Describe your changes in detail -->
this pr cleans up the ci-pr check. ci hack consumes a lot of time to execute hogging up runners. ci check should be more than enough.
also, this pr removes the commented out code since its been the same since like last 2+ years. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Configuration Files**
- `.github/workflows/CI-pr.yml`
**Code Patterns Applied:**
- Extend existing types with new fields (2 changes) | {"pr_number": 9819, "pr_title": "ci: remove cargo check", "merged_at": "2025-10-15T16:19:48Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"config": [".github/workflows/CI-pr.yml"]}, "change_types": {"fields_added": 2}, "has_identifier_data": false, "commits_match... |
This PR addresses below issues specifically for payment links
- improper use of innerHTML for API inputs - for rendering transaction details
- improper use of receiving event (isFormReadyForSubmission) from HS SDK
Overall, this PR sanitizes API text based inputs which are rendered in the payment link UI using URI ... | 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/api.rs`
**2. Core Business Logic**
- `crates/router/src/core/payment_link.rs`
- `crates/router/src/core/payment_link/payment_link... | {"pr_number": 7736, "pr_title": "fix(payment_link): sanitize embedded payment link data", "merged_at": "2025-05-29T08:22:03Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/api.rs"], "... |
<!-- Describe your changes in detail -->
Add support for confirm-intent proxy flow which accepts Card payment method data with card number vault token instead of raw card number.
new route - `http://localhost:8080/v2/payments/{{payment_id}}/confirm-intent/external-vault-proxy` | 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": 8923, "pr_title": "feat(router): Add support for confirm-intent external vault proxy flow", "merged_at": "2025-08-18T11:23:48Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "connector"]}, "hierarchy": {"api_models": ["crates/api_models/src/payme... |
<!-- Describe your changes in detail -->
This PR introduces support for associating ProdIntent with specific product_types and transitions the feature from being user-scoped to merchant-scoped, enabling more flexible usage across different products.
## Changes Introduced | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/user/dashboard_metadata.rs`
**2. Core Business Logic**
- `crates/router/src/core/user.rs`
- `crates/router/src/core/user/dashboard_metadata.rs`
**3. Typ... | {"pr_number": 7638, "pr_title": "feat(users): refactor `ProdIntent` to support product-type context and merchant-scope", "merged_at": "2025-04-10T10:14:36Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["merchant", "user", "token"]}, "hierarchy": {"api_models": ["crates/api_models/s... |
Hotfix for https://github.com/juspay/hyperswitch/pull/8079 | To implement this **search_filter** 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 ... | {"pr_number": 8087, "pr_title": "refactor(connector): [Fiuu] enable refund ORF feature [RedSys] fix the request structure", "merged_at": "2025-05-20T15:56:12Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user", "refund", "card"]}, "hierarchy": {"connectors": ["crates/hyperswitch_... |
<!-- 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/coinbase.rs`
- `crates/hyperswitch_connectors/src/connectors/coinbase/transformers.rs`
- `crates/hyperswitch_connectors/src/conn... | {"pr_number": 8915, "pr_title": "refactor(connector): implement amount converter framework for coinbase, dummyconnector and gocardless", "merged_at": "2025-08-18T14:45:50Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors":... |
<!-- Describe your changes in detail -->
Optional billing details should be used for non-mandatory billing fields. Billing address is optional field for making requests to nexixpay. Either billing.first_name or billing.second_name should be present mandatorily.
Includes ENV changes related to support of currency an... | 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/router/src/configs/defaults/payment_connector_required_fields.rs`
**2. Tests**
- `config/de... | {"pr_number": 7465, "pr_title": "fix(connectors): [Nexixpay] handle optional fields in nexixpay payments requests.", "merged_at": "2025-03-17T09:43:04Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitc... |
<!-- Describe your changes in detail -->
connector integration template code for recurly.
Issue: This PR closes the issue #7283 | 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/common_enums/src/connec... | {"pr_number": 7284, "pr_title": "feat(connector): add template code for recurly", "merged_at": "2025-03-05T10:40:40Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["connector"]}, "hierarchy": {"core_business": ["crates/router/src/core/payments/connector_integration_v2_impls.rs", "cr... |
<!-- Describe your changes in detail -->
Added `docker.io` registry prefix to all images in the `docker-compose.yml` to avoid confusions when the host machine has a different default registry set. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Configuration Files**
- `docker-compose-development.yml`
- `docker-compose.yml`
**Code Patterns Applied:**
- Extend existing types with new fields (36 changes) | {"pr_number": 9771, "pr_title": "chore: added explicit docker.io registry to all images in docker-compose.yml", "merged_at": "2025-10-15T12:08:32Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"config": ["docker-compose-development.yml", "docker-compose.yml"... |
<!-- Describe your changes in detail -->
There is a serialization issue for `card_last_4` and `authentication_type` fields when filters are getting applied for `PaymentIntentFilters`.
`card_last_4` was being processed as `card_last4` .
`auth_type` is being used to add the filters and not serialized into `Authenticat... | 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` | {"pr_number": 6595, "pr_title": "fix(analytics): fix `authentication_type` and `card_last_4` fields serialization for payment_intent_filters", "merged_at": "2024-11-19T20:39:12Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user", "order"]}, "hierarchy": {"api_models": ... |
<!-- Describe your changes in detail -->
Add external vault support in v1 payments flow.
Currently we only save card in hs-card-vault
Added new support to save card in external vault based merchant-profile configuration.
Changes in code -
During First CIT (fresh card for a customer c1 - setup future usage - on_... | 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. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/business_profile.rs`
- `cr... | {"pr_number": 9274, "pr_title": "feat(router): Add external vault support in v1 payments flow", "merged_at": "2025-09-23T07:20:31Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/admin.rs", "crat... |
<!-- Describe your changes in detail -->
- RELATED PR : https://github.com/juspay/hyperswitch/pull/9581
- Refunds via authorizedot net are getting into `pending` state where no connector call is made
- This happens when `connector_metadata` is empty in attempt table
- In usual cases `connector_metadata` is no... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/authorizedotnet/transformers.rs`
**Code Patterns Applied:**
- Implement new functions (2 changes)
- Extend existing types with new fi... | {"pr_number": 9599, "pr_title": "fix(authorizedotnet): refund via ucs missing connector_metadata", "merged_at": "2025-09-30T06:37:14Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/c... |
<!-- Describe your changes in detail -->
add network token support for peach payments connector | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payment_methods/network_tokenization.rs`
**2. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/peachpayments/transformers.rs`
**3.... | {"pr_number": 9754, "pr_title": "feat(connector): [Peach Payments] add network token support for connector", "merged_at": "2025-10-13T12:38:13Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core... |
<!-- Describe your changes in detail -->
Updating the connector documentation | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `add_connector.md`
**2. Configuration Files**
- `.typos.toml`
**Code Patterns Applied:**
- Define new data structures (2 changes)
- Implement new functions (14 changes)
- Exte... | {"pr_number": 8739, "pr_title": "docs: update connector guide", "merged_at": "2025-08-19T11:00:18Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["connector"]}, "hierarchy": {"connectors": ["add_connector.md"], "config": [".typos.toml"]}, "change_types": {"structs_added": 2, "functi... |
Adds support of consuming the incoming webhook and verifying it. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/admin.rs`
**2. External Connector Integration**
- `crates/connector_configs/src/connector.rs`
- `crates/hyperswitch_connectors/src/connectors/stripebilling.rs`
... | {"pr_number": 7417, "pr_title": "feat(connector): [Stripebilling] add incoming webhook support", "merged_at": "2025-03-17T15:22:33Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"core_business": ["crates/router/src/core/admin.rs"], "co... |
<!-- Describe your changes in detail -->
This change will add `payment_method_type` in dynamic_routing_stats. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/dynamic_routing_stats.rs`
- `crates/diesel_models/src/schema.rs`
- `crates/diesel_models/src/schema_v2.rs`
**2. Core Business Logic**
- `crat... | {"pr_number": 6853, "pr_title": "refactor(dynamic_routing): add col payment_method_type in dynamic_routing_stats", "merged_at": "2024-12-20T08:33:42Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user"]}, "hierarchy": {"database": ["crates/diesel_models/src/dynamic_rout... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.