prompt stringlengths 6 90.9k | response stringlengths 121 18.6k | metadata stringlengths 314 42.3k |
|---|---|---|
<!-- Describe your changes in detail -->
In certain card networks like Amex and Visa, the `refusal_reason_raw` field inside `AdditionalData` comes as `51 : Insufficient funds/over credit limit`. In that case, we map `51` to `network_decline_code` and `Insufficient funds/over credit limit` to `network_error_message` | 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 (7 changes)
**Detailed Identifier Changes:... | {"pr_number": 9361, "pr_title": "fix(connector): [ADYEN] Add fallback parsing for refusal codes and messages", "merged_at": "2025-09-19T11:35:08Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_conn... |
<!-- Describe your changes in detail -->
Fix EPS Bank Redirect redirection in Cypress.
Closes #6528 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `cypress-tests/cypress/support/redirectionHandler.js` | {"pr_number": 6529, "pr_title": "fix: trustpay `eps` redirection in cypress", "merged_at": "2024-11-12T07:17:51Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"tests": ["cypress-tests/cypress/support/redirectionHandler.js"]}, "change_types": {}, "has_identif... |
<!-- Describe your changes in detail -->
This pr fixes semantic inconsistency with openapi_spec.json | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/organization.rs`
**2. External Connector Integration**
- `crates/openapi/src/routes/merchant_connector_account.rs`
**3. Other**
- `api-reference/openapi... | {"pr_number": 8099, "pr_title": "chore(openapi): resolve openapi semantic inconsistency", "merged_at": "2025-05-22T10:23:45Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"api_models": ["crates/api_models/src/organization.rs"], "connectors": ["crates/openapi/src/... |
<!-- Describe your changes in detail -->
* Updated to check if the payment method is `Wallet` before proceeding with the wallet decryption operation. | 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:**
- Add conditional logic for feature flags or filtering (1 changes) | {"pr_number": 8744, "pr_title": "fix(router): add payment method Wallet check for decrypted wallet payment method token logic", "merged_at": "2025-07-24T11:35:29Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["cra... |
<!-- Describe your changes in detail -->
This fixes the inconsistent nomenclature used for tenants in router and drainer code | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payment_methods/cards.rs`
- `crates/router/src/core/routing/helpers.rs`
**2. Type Definitions**
- `crates/router/src/types/storage/payment_attempt.rs`
**3. Tests**
... | {"pr_number": 6389, "pr_title": "fix(multitenancy): consistently use tenant nomenclature everywhere", "merged_at": "2024-10-28T15:42:38Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"core_business": ["crates/router/src/core/payment_methods/... |
<!-- Describe your changes in detail -->
Template code added for new connector JP Morgan
https://developer.payments.jpmorgan.com/docs/commerce/online-payments/capabilities/online-payments/payment-methods/cards | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/connector_enums.rs`
**2. Core Business Logic**
- `crates/router/src/core/payments/connector_integration_v2_impls.rs`
- `crates/router/src/core/payments/f... | {"pr_number": 6467, "pr_title": "Feat(connector): [JP MORGAN] Added Template code for cards integration", "merged_at": "2024-11-05T15:51:59Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "connector", "card"]}, "hierarchy": {"api_models": ["crates/api_models/src/connector... |
<!-- Describe your changes in detail -->
Added payment flows (Auth, PSync, Refund, RSync, and Webhooks) for Inespay Sepa Bank Debit. | 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/hypers... | {"pr_number": 6755, "pr_title": "feat(connector): [INESPAY] Integrate Sepa Bank Debit", "merged_at": "2025-02-05T15:18:13Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core/admin.rs"], "connect... |
<!-- Describe your changes in detail -->
The installation tracking system has been upgraded to capture more information, errors and behaviors during the installation period such as:
- User aborts
- Server failure errors
- Dependency errors
- Successful installations
Hotfix PR for #[8238](https://git... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Configuration Files**
- `docker-compose.yml`
**2. Other**
- `.gitignore`
- `scripts/create_default_user.sh`
- `scripts/notify_scarf.sh`
- ... and 3 more files
**Code Patterns Applied:**
- Extend existi... | {"pr_number": 8237, "pr_title": "fix: capture installation errors from one-click and docker compose setup", "merged_at": "2025-06-12T13:58:48Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"config": ["docker-compose.yml"], "other": [".gitignore", "scripts/cr... |
fix wasm for Loonio | 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": 9647, "pr_title": "refactor(connector): fix wasm for Loonio", "merged_at": "2025-10-01T13:42:36Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"connectors": ["crates/connector_configs/toml/development.toml", "crates/connector_configs/toml/production.... |
This PR introduces below changes
- Exposes two endpoints for
- Single card tokenization
- Tokenizing raw card details with the network
- Tokenizing an existing payment method in HS with the network (card only)
- Bulk tokenization
- Tokenizing using raw card details or an existing... | 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/bulk_tokenization.rs`
- `crates/hyperswitch_domai... | {"pr_number": 7066, "pr_title": "feat(core): add bulk tokenization flows", "merged_at": "2025-03-07T13:24:06Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/payment_methods.rs"], "domain": ["cra... |
Docker pull from latest stable tag | To implement this **validation** feature, you'll need to modify these architectural layers:
**1. Configuration Files**
- `docker-compose.yml`
**Code Patterns Applied:**
- Extend existing types with new fields (2 changes) | {"pr_number": 7700, "pr_title": "fix: web-docker pull from docker hub", "merged_at": "2025-04-03T07:29:59Z", "intent": {"feature_type": "validation", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"config": ["docker-compose.yml"]}, "change_types": {"fields_added": 2}, "has_identifier_data": false, "commi... |
Added a BadRequest response for SSO login when an invalid authorization code is provided.
<!-- Describe your changes in detail --> | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Other**
- `crates/router/src/services/openidconnect.rs`
**Code Patterns Applied:**
- Add conditional logic for feature flags or filtering (1 changes) | {"pr_number": 9244, "pr_title": "fix(users): add bad request for openidconnect", "merged_at": "2025-09-10T08:51:15Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"other": ["crates/router/src/services/openidconnect.rs"]}, "change_types": {"conditionals_added"... |
<!-- Describe your changes in detail -->
This PR revert #6734 in main
This is hotfix for https://github.com/juspay/hyperswitch/pull/7717
Reason: digit couldn't be added to nickname because nickname have the same validation as cardholder name. | 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/mandates.rs`
- `crates/api_models/src/payment_methods.rs`
- ... and 3 more files
**2. Domain Models (Business L... | {"pr_number": 7718, "pr_title": "revert: implement `NameType` for name validation (#6734)", "merged_at": "2025-04-03T16:24:25Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["card"]}, "hierarchy": {"api_models": ["crates/api_models/src/customers.rs", "crates/api_models/src/mandates.... |
This pull request enhances the data migration API to support migrating customer and payment method data across multiple business profiles in a single request.
Specifically, the following changes have been made:
1. **Customer Data Migration:**
* Updated `PaymentMethodRecord` to allow `merchant_connector_id... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/payment_methods.rs`
**2. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/lib.rs`
- `crates/hyperswitch_domain_models/src/p... | {"pr_number": 8473, "pr_title": "feat(data-migration): add connector customer and mandate details support for multiple profiles", "merged_at": "2025-07-01T10:07:08Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crat... |
<!-- Describe your changes in detail -->
Making `OpenSearchClient` optional based on the config for querying OpenSearch Server for dashboard based on the Deployment status of the same ( OpenSearch Server ). | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/health_check.rs`
**2. Configuration Files**
- `config/config.example.toml`
- `config/deployments/env_specific.toml`
- `config/development.toml`
- ... and ... | {"pr_number": 7810, "pr_title": "chore(analytics): opensearch client creation based on config", "merged_at": "2025-04-17T08:33:47Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"core_business": ["crates/router/src/core/health_check.rs"], "config": ["config/c... |
Earlier we used to store the connector mandate id only in case of charged payments, Ideally we should store for both authorized and charged | 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": 6379, "pr_title": "fix(mandates): Allow connector_mandate_detail updation in case of 'Authorized' Payments", "merged_at": "2024-10-21T14:18:31Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/... |
Includes below changes -
- Fixes Worldpay's payment method filters
- Makes `payment_method_type` non-mandatatory for Cards | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/router/src/connector/worldpay/transformers.rs`
**2. Configuration Files**
- `config/deployments/sandbox.toml`
**Code Patterns Applied:**
- Extend existing types with n... | {"pr_number": 6400, "pr_title": "fix(deployment-config): remove invalid currencies from worldpay filters", "merged_at": "2024-10-23T14:23:28Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/router/src/connector... |
<!-- Describe your changes in detail -->
Hotfix for https://github.com/juspay/hyperswitch/pull/9372
Add acknowledgement in adyen for incoming webhooks by sending status 200. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/common_enums/src/connector_enums.rs`
- `crates/hyperswitch_connectors/src/connectors/adyenplatform/transformers/payouts.rs` | {"pr_number": 9425, "pr_title": "feat(router): Handle incoming webhooks adyen", "merged_at": "2025-09-17T18:56:54Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/common_enums/src/connector_enums.rs", "crates/h... |
<!-- Describe your changes in detail -->
- (api_models): change the `poc_email` type to `Secret<String>`
- Add some `pii::Email` validation to check for input validity
- (diesel_models): change `data_value` to `Secret<serde_json::Value>`
## Fixes #7128 | 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. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/user/dashboard_metadata.rs`
**3. Core Business Logic**
... | {"pr_number": 7130, "pr_title": "fix(dashboard_metadata): mask `poc_email` and `data_value` for DashboardMetadata", "merged_at": "2025-02-06T15:16:20Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user", "token"]}, "hierarchy": {"api_models": ["crates/api_models/src/user/dashboard... |
<!-- Describe your changes in detail -->
We have expand attempts list in v1 payment sync response which is used by dashboard team. We need similar support in v2. By passing expand_attempts in psync query param, vector of payment attempts associated with the intent will be returned in the payments get response. | 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": 7209, "pr_title": "refactor(core): add support for expand attempt list in psync v2", "merged_at": "2025-02-11T11:34:47Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/payments.rs"]... |
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": 6820, "pr_title": "feat(payments): [Payment links] Add locale case fix", "merged_at": "2024-12-12T06:40:53Z", "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 -->
Hotfix for original PR: [7712](https://github.com/juspay/hyperswitch/pull/7712)
A recent change in [this PR](https://github.com/juspay/hyperswitch/pull/7537) removed the usage of DomainStorageError in all the places and started using StorageError everywhere.
Previously, ... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Other**
- `crates/storage_impl/src/errors.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (2 changes) | {"pr_number": 7719, "pr_title": "fix(errors): Entry not found error as 4xx instead of 5xx", "merged_at": "2025-04-04T10:35:44Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"other": ["crates/storage_impl/src/errors.rs"]}, "change_t... |
<!-- Describe your changes in detail -->
Connectors like Nuvei requires a field called as `storedCredentialMode` which represents if the merchant is using a card details which they previously used for same connector or any other PSP. This is used for risk lowering based on PSP's.
- Make a `is_stored_credential` i... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/payments.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/payment_attempt.rs`
- `crates/diesel_models/src/schema.rs`
- `crates... | {"pr_number": 9515, "pr_title": "feat(core): [Nuvei] add stored credentials flag ", "merged_at": "2025-09-30T12:33:11Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/payments.rs"], "database": [... |
Wasm changes for paysafe card 3ds | 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": 9380, "pr_title": "refactor(connector): wasm changes", "merged_at": "2025-09-16T07:22:05Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user", "card"]}, "hierarchy": {"connectors": ["crates/connector_configs/src/connector.rs", "crates/connector_configs/toml/developme... |
<!-- Describe your changes in detail -->
- Added Connector changes for VGS
- Implemented `ExternalVaultInsertFlow` and `ExternalVaultRetrieveFlow` for VGS
- This allows Payment methods to be vaulted in VGS when `is_external_vault_enabled` is set to true in profile
- Updated VGS URL in TOML files | 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`
**2. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/vgs.rs`
- `crates/hyperswitch_connectors/src/connector... | {"pr_number": 7942, "pr_title": "feat(connector): Add VGS connector impls", "merged_at": "2025-08-25T09:52:19Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "user"]}, "hierarchy": {"core_business": ["crates/router/src/core/payment_methods.rs"], "connectors": ... |
Added support for consuming eci for AuthNResponse in Authentication flow | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/authentication.rs`
**2. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/router_request_types/unified_authentication_... | {"pr_number": 8225, "pr_title": "feat(core): add support for consuming eci for AuthNResponse in Authentication flow", "merged_at": "2025-06-03T12:49:46Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "user"]}, "hierarchy": {"database": ["crates/diesel_models/s... |
<!-- Describe your changes in detail -->
Currently click to pay session token is failing as it is not able to parse card brands, which should ideally be fetched from union of payment processors
## How did you test it?
<!--
Did you write an integration/unit/API test to verify the code changes?
Or did you test t... | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/payments.rs` | {"pr_number": 9784, "pr_title": "fix(router): fixed click to pay metadata parsing issue", "merged_at": "2025-10-13T15:45:48Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["payment", "merchant", "connector"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/payments.rs"]}, ... |
The amount field in DisputePayload in `crates/hyperswitch_interfaces/src/disputes.rs` was String. Changed it to StringMinorUnit.
Made changes in the following connectors : Adyen, Airwallex, Bluesnap, Braintree, Checkout, Novalnet, Payme, Paypal, Rapyd, Stripe, Trustpay.
In the Dispute table, changed the amount ... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/disputes.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/dispute.rs`
**3. Core Business Logic**
- `crates/router/src/core/webho... | {"pr_number": 8131, "pr_title": "feat(core): Altered the amount field in DisputePayload to StringMinorUnit", "merged_at": "2025-05-30T14:57:38Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/dis... |
- Add api to create tenant users
- Add api to create orgs
- Support tenant level entity for the user hierarchy
A tenant level user should see dashboard as seen by the org admin. He will be pinned to one org, merchant and profile. And he can switch between any org in the given tenancy. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/events/user.rs`
- `crates/api_models/src/user.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/query/merchant_account.rs`
**3. C... | {"pr_number": 6708, "pr_title": "feat(users): add support for tenant level users", "merged_at": "2024-12-06T13:19:57Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["merchant", "user", "token"]}, "hierarchy": {"api_models": ["crates/api_models/src/events/user.rs", "crates/api_models... |
<!-- Describe your changes in detail -->
This PR does 3 things.
1. Throw 401 if cookies are not found in request or if JWT is not found in cookies.
2. Cache role info only if the ttl is greater than or equal to 0.
3. Use `UserEmail` type in DB functions. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/errors/api_error_response.rs`
**2. Core Business Logic**
- `crates/router/src/core/user.rs`
- `crates/router/src/core/user_role.r... | {"pr_number": 6699, "pr_title": "refactor(users): Use domain email type in user DB functions", "merged_at": "2024-11-29T13:37:38Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/errors/api_error_response.rs"], "... |
<!-- Describe your changes in detail -->
The FIUU Connector was not functioning as expected.
## Key Changes
- Added fiuu connector configs for `PaymentConfirmWithShippingCost`, `ZeroAuthMandate`, and `SaveCardConfirmAutoCaptureOffSessionWithoutBilling`.
- Added `billing.email` in some places in the configs wher... | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. Tests**
- `cypress-tests/cypress/e2e/configs/Payment/Fiuu.js`
- `cypress-tests/cypress/e2e/configs/Payment/Modifiers.js`
- `cypress-tests/cypress/e2e/configs/Payment/Utils.js`
- ... and 4 more files
**Code Patte... | {"pr_number": 7297, "pr_title": "refactor(cypress): Fiuu connector configuration changes", "merged_at": "2025-03-12T12:23:40Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["payment", "user", "connector"]}, "hierarchy": {"tests": ["cypress-tests/cypress/e2e/configs/Payment/Fiuu.js", "cypr... |
The following details are needed to be stored in the payment intent feature metadata as a part of transaction monitoring system for revenue recovery.
1. Card Network
2. Card Issuer
3. First Payment Gateway Error Code
4. First Network Error Code
5. First Network Advice Code
These will be constant through... | 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/types.rs`
**3. Domain Models (Business Logic Types)**
- `crates/hypers... | {"pr_number": 8250, "pr_title": "feat(core): consume card details from billing connectors and first error codes and store them in payment intent table", "merged_at": "2025-06-16T11:39:32Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy"... |
<!-- Describe your changes in detail -->
Currently normal 3ds payments are failing if we enable a merchant for UAS. This pr fixes that
## 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)?
-->
MCA... | 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/unified_authentication_service.rs`
**2. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/... | {"pr_number": 9545, "pr_title": "fix(core): fixed ctp bug for confirmation and added multi profile support for modular auth", "merged_at": "2025-09-24T17:21:34Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crate... |
<!-- Describe your changes in detail -->
Added currency as dimension and filter for disputes, required for Analytics V2 Dashboard. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/analytics/disputes.rs`
**2. Core Business Logic**
- `crates/analytics/src/disputes/core.rs`
**3. Type Definitions**
- `crates/analytics/src/disputes/typ... | {"pr_number": 7006, "pr_title": "feat(analytics): Add currency as dimension and filter for disputes", "merged_at": "2025-02-05T14:29:40Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user", "order"]}, "hierarchy": {"api_models": ["crates/api_models/src/analytics/disputes.rs"], "co... |
<!-- Describe your changes in detail -->
Currently if we cancel the transaction after initiating with netcetera we are trying hard fetch cavv stored in temp locker, which is causing 5xx.
with this PR we will be ignoring the cavv fetch error since it will be fetched in authorisation flow if authorisation need to be ... | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/authentication.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (1 changes) | {"pr_number": 8051, "pr_title": "fix(router): fixed netcetera flow for backward flow cavv fetching", "merged_at": "2025-05-16T09:17:20Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["transaction"]}, "hierarchy": {"core_business": ["crates/router/src/core/authentication.rs"]}, "change_typ... |
<!-- Describe your changes in detail -->
As FRM routing is not supported in DE we can remove support for it from DE migration endpoint | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/routing.rs` | {"pr_number": 8448, "pr_title": "fix(routing): remove frm rule migration support as it is not supported in DE", "merged_at": "2025-06-24T12:26:14Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"core_business": ["crates/router/src/core/routing.rs"]}, "change_types"... |
<!-- Describe your changes in detail -->
Added the `multiple_webhook_detail` field to the Profile DB and domain model. Also populated these fields to as `None`.
Also we need `webhook_endpoint_id`, added support for this idType as well in this PR. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/business_profile.rs`
**2. Type Definitions**
- `crates/router/src/types/transformers.rs`
**3. Utils**
- `crates/common_utils/src/id_type.rs`
... | {"pr_number": 9816, "pr_title": "feat(framework): Diesel and domain model changes to support multiple outgoing webhooks", "merged_at": "2025-10-16T10:36:29Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["webhook"]}, "hierarchy": {"database": ["crates/diesel_models/src/business_prof... |
main pr - https://github.com/juspay/hyperswitch/pull/7864 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/connector_configs/toml/production.toml`
- `crates/hyperswitch_connectors/src/connectors/noon.rs`
- `crates/hyperswitch_connectors/src/connectors/noon/transformers.rs`... | {"pr_number": 7868, "pr_title": "fix(connector): revert noon-paypal", "merged_at": "2025-04-22T14:00:11Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"connectors": ["crates/connector_configs/toml/production.toml", "crates/hyperswitch_connectors/src/connectors/noo... |
<!-- Describe your changes in detail -->
This PR addresses the clippy lints occurring due to new rust version 1.90.0 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/fraud_check/operation.rs`
- `crates/router/src/core/fraud_check/operation/fraud_check_post.rs`
- `crates/router/src/core/fraud_check/operation/fraud_check_pre.rs... | {"pr_number": 9511, "pr_title": "chore: address Rust 1.90.0 clippy lints", "merged_at": "2025-09-25T19:13:45Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"core_business": ["crates/router/src/core/fraud_check/operation.rs", "crates/router/src/core/fraud_che... |
<!-- Describe your changes in detail -->
closes https://github.com/juspay/hyperswitch/issues/6893
this pr also bumps cypress dependencies | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `cypress-tests/cypress.config.js`
- `cypress-tests/package-lock.json`
- `cypress-tests/package.json` | {"pr_number": 6894, "pr_title": "fix: cypress reports generation", "merged_at": "2024-12-20T08:19:41Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"tests": ["cypress-tests/cypress.config.js", "cypress-tests/package-lock.json", "cypress-tests/package.json"]}, "cha... |
<!-- 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.
## How did you test it?
<!--
... | 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": 8260, "pr_title": "fix(wasm): [Worldpayvantiv] add support for metadata.report_group", "merged_at": "2025-06-05T09:54:27Z", "intent": {"feature_type": "connector_integration", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"connectors": ["crates/connector_configs/src/connector.rs"]}, "chang... |
<!-- Describe your changes in detail -->
This will add dynamic_routing in core flows.
After which once the toggle route is hit with `feature = dynamic_connector_selection`, routable connectors will be evaluated on basis of success_based routing. | 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": 6333, "pr_title": "feat(euclid): add dynamic routing in core flows", "merged_at": "2024-10-25T11:39:01Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["merchant", "connector"]}, "hierarchy": {"api_models": ["crates/api_models/src/routing.rs"], "core_business": ["crates... |
This PR fixes the ApplePay integration with WorldPay. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/worldpay/transformers.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (1 changes) | {"pr_number": 7069, "pr_title": "fix(connectors): [worldpay] send decoded token for ApplePay", "merged_at": "2025-01-24T08:32:03Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/conne... |
<!-- Describe your changes in detail -->
add wasm changes for threedsecure.io for collecting acquirer_bin, acquirer_merchant_id and acquirer_country_code in MCA
<!--
Provide links to the files with corresponding changes.
## Checklist
<!-- Put an `x` in the boxes that apply -->
- [x] I formatted the code `ca... | To implement this **validation** 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": 8330, "pr_title": "feat(dashboard): added wasm changes for threedsecure.io for collecting acquirer_bin, acquirer_merchant_id and acquirer_country_code in MCA", "merged_at": "2025-06-12T11:02:04Z", "intent": {"feature_type": "validation", "action": "add_feature", "entities": ["merchant"]}, "hierarchy": {"c... |
<!-- Describe your changes in detail -->
Inespay enablement in dashboard. Added the changes in connector configs. | 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": 7233, "pr_title": "feat(connector): [INESPAY] Enable Inespay In Dashboard", "merged_at": "2025-02-11T12:49:47Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["connector"]}, "hierarchy": {"connectors": ["crates/connector_configs/toml/development.toml", "crates/connector... |
<!-- Describe your changes in detail -->
- Billing address was empty during payment request with payment_method_id
- This is due to not saving billing_address in payment_methods table while generating payment_method_id | 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/payments/operations/payment_response.rs`
- `crates/router/src/core/payments/tokenization.rs`
**Code Patterns Appli... | {"pr_number": 6411, "pr_title": "fix(core): populate billing_address for payment with pm_id", "merged_at": "2024-10-24T15:57:04Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core/payment_method... |
<!-- Describe your changes in detail -->
- Added diesel migration to make `payment_method_subtype` Nullable in `payment_attempt` table
- Made `payment_method_subtype` an `Option` in request and response structs | 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`
- `crates/api_models/src/payments.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/payment_attempt.rs`
- `... | {"pr_number": 7568, "pr_title": "feat(router): Make payment_method_subtype optional in payment_attempt [V2]", "merged_at": "2025-03-24T07:53:07Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/pa... |
<!-- Describe your changes in detail -->
This PR fixes following things
-> Required fileds for mandates for fiuu
-> fix check for required fileds for mandates
-> add 3ds cypress 3ds test case | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payment_methods/cards.rs`
**2. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/fiuu/transformers.rs`
- `crates/hyperswitch_conn... | {"pr_number": 6487, "pr_title": "fix(connector): [fiuu]fix mandates for fiuu", "merged_at": "2024-11-08T13:38:55Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"core_business": ["crates/router/src/core/payment_methods/cards.rs"], "connectors": ["crates/hyper... |
This PR introduces populating `connector_customer` field in `customers` table during payment method migration. | 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. Core Business Logic**
- `crates/router/src/core/customers.rs`
**3. Type Definitions**
- `crates/common_types/src/customers.rs`
... | {"pr_number": 8319, "pr_title": "feat(payment_methods): populate connector_customer during customer creation step in payment methods migrate flow", "merged_at": "2025-06-17T09:58:03Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"a... |
<!-- Describe your changes in detail -->
Adding a custom expiry time for Forex data saved in redis (172800 seconds ~ 2days).
A new config is added as well:
`redis_cache_expiry_in_seconds = 172800` | 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": 7455, "pr_title": "refactor(currency_conversion): add support for expiring forex data in redis", "merged_at": "2025-03-17T14:49:01Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"core_business": ["crates/router/src/core/currency.rs"], "utils": ["crat... |
<!-- Describe your changes in detail -->
This PR is just a minor refactor of removing duplicate / redundant `customer_acceptance` object by re-using it.
Moved the object to `Commons` and imported the object where ever the duplicate code exist. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `cypress-tests/cypress/e2e/configs/Payment/Adyen.js`
- `cypress-tests/cypress/e2e/configs/Payment/BankOfAmerica.js`
- `cypress-tests/cypress/e2e/configs/Payment/Bluesnap.js`
- ... and 10 more file... | {"pr_number": 7435, "pr_title": "ci(cypress): move customer acceptance in configs to a const within commons", "merged_at": "2025-03-06T07:19:11Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer"]}, "hierarchy": {"tests": ["cypress-tests/cypress/e2e/configs/Payment/Adyen.js",... |
<!-- Describe your changes in detail -->
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": 8214, "pr_title": "feat(events): adding infra level components to api-events", "merged_at": "2025-06-04T06:30:35Z", "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 -->
- 3ds transaction were not actually 3ds transactions in Nuvei system. This occurred because we were not passing previous transaction data while making 3ds complete-authorize call.
- Prevoiusly psync was implemeted with session token. If we make 3ds payment but not confirm an... | 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**
- `cypress-tests/cypress/e2e/conf... | {"pr_number": 9279, "pr_title": "fix(nuvei): nuvei 3ds fix + psync fix", "merged_at": "2025-09-11T14:31:03Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors/nuvei.rs", "crat... |
<!-- Describe your changes in detail -->
This PR adds a new endpoint called `finish_redirection` to payments v2.
## 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... | 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/payments.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/business_profile.rs`
**3. Domain Models (... | {"pr_number": 6549, "pr_title": "feat(payments_v2): add finish redirection endpoint", "merged_at": "2024-11-15T09:08:39Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/admin.rs", "crates/api_models/sr... |
<!-- Describe your changes in detail -->
I added dispute generation to function `generate_sample_data` in `utils/user/sample_data.rs`.
The number of disputes generated is based on the number of payments created:
2 disputes if the number of payments is between 50 and 100.
1 dispute if the number of payments is less... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/user/sample_data.rs`
**2. Utils**
- `crates/router/src/utils/user/sample_data.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (22 changes)
... | {"pr_number": 6341, "pr_title": "feat(sample_data): generate random disputes for sample data", "merged_at": "2024-10-25T08:45:37Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user"]}, "hierarchy": {"core_business": ["crates/router/src/core/user/sample_data.rs"], "utils... |
<!-- Describe your changes in detail -->
add three_ds_decision_rule support in routing apis
This pull request introduces support for a new `ThreeDsDecisionRule` routing algorithm and a corresponding `ThreeDsAuthentication` transaction type, while also implementing validation and error handling for these additions. ... | 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. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/enums.rs`
**3. Core Business Logic**
- `crates/router/src/core/admin.rs... | {"pr_number": 8132, "pr_title": "feat(router): add three_ds_decision_rule support in routing apis", "merged_at": "2025-05-30T14:04:43Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user", "connector", "transaction"]}, "hierarchy": {"api_models": ["crates/api_models/src/routing.rs"... |
<!-- Describe your changes in detail -->
1. This pr adds plan_id and price_id columns to the subscription table.
2. Created the subscription update call, which takes `plan_id`, `item_price_id`, `amount`, and `currency` as input.
3. Added payment update s2s call.
4. This PR removes all subscription information fro... | 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": 9778, "pr_title": "feat(subscriptions): Add update subscriptions APIs with payments update call", "merged_at": "2025-10-14T10:54:26Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/... |
<!-- Describe your changes in detail -->
Changed Dispute Currency from String to ENUM.
Connector create (Stripe):
`curl --location 'http://localhost:8080/account/merchant_1731933435/connectors' \
--header 'Content-Type: application/json' \
--header 'Accept: application/json' \
--header 'api-key: test_admin' \
... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/disputes.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/dispute.rs`
- `crates/diesel_models/src/schema.rs`
- `crates/diesel_... | {"pr_number": 6454, "pr_title": "fix(dispute): change dispute currency type to currency enum", "merged_at": "2024-11-20T14:14:53Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/disputes.rs"], "d... |
This pull request introduces new domain models for subscriptions and invoices, and refactors the codebase to use these models instead of the previous Diesel-based models. The changes improve type safety and abstraction for subscription and invoice handling, and update relevant interfaces and function calls throughout t... | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/invoice.rs`
- `crates/hyperswitch_domain_models/src/lib.rs`
- `crates/hyperswitch_domain_models/src/subscription.rs`
**2. Core Business... | {"pr_number": 9640, "pr_title": "feat(subscription): domain_model for subscription and invoice", "merged_at": "2025-10-09T10:51:00Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/invoice.rs... |
1. Consuming error message given by `DeutscheBank` in case of 2xx errors, because it is currently not handled for 2xx errors. Error message is only consumed for 4xx and 5xx.
2. Consuming error message given by `Fiuu` in case of 2xx errors only in case of `refunds`. In all other cases where 2xx errors are thrown, code... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/deutschebank/transformers.rs`
- `crates/hyperswitch_connectors/src/connectors/fiuu/transformers.rs`
**Code Patterns Applied:**
- I... | {"pr_number": 6727, "pr_title": "feat(connector): [DEUTSCHEBANK, FIUU ] Handle 2xx errors given by Connector", "merged_at": "2024-12-12T10:20:34Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["refund"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors/deu... |
<!-- Describe your changes in detail -->
In customer payment method list api, card scheme and card network are showing different value for co-branded card it they are saved with both the network, to fix this issue, both these fields are now fetching the data from the card locker | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/payment_method.rs`
**2. Core Business Logic**
- `crates/router/src/core/payment_methods/cards.rs`
- `crates/router/src/core/payments/tokenizatio... | {"pr_number": 6849, "pr_title": "fix(payment_methods): card_network and card_scheme should be consistent", "merged_at": "2024-12-17T14:16:31Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "user"]}, "hierarchy": {"database": ["crates/diesel_models/src/payment_... |
<!-- Describe your changes in detail -->
Currently, the following routes use `AdminApiAuthWithMerchantIdFromRoute` for authentication:
- Profile Create, Retrieve, Update
- Merchant Connector Account Create, List, Retrieve, Update
This is being updated to a more appropriate auth layer: `ApiKeyAuthWithMerchantIdFro... | 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": 7656, "pr_title": "refactor(authentication): modify auth for profiles and mca routes to `ApiKeyAuthWithMerchantIdFromRoute`", "merged_at": "2025-03-28T09:08:08Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "connector"]}, "hierarchy": {"tests": ... |
<!-- Describe your changes in detail -->
This PR introduces support for listing refunds in v2 apis.
Available filters for listing are as follows
- `payment_id`: Filter by a specific payment identifier.
- `refund_id`: Filter by a specific refund identifier.
- `limit`: Maximum number of refund records to return.
... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/refunds.rs`
**2. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/Cargo.toml`
- `crates/hyperswitch_domain_models/src/refunds.r... | {"pr_number": 7966, "pr_title": "feat(refunds_v2): Add refunds list flow in v2 apis", "merged_at": "2025-05-12T15:29:26Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "refund"]}, "hierarchy": {"api_models": ["crates/api_models/src/refunds.rs"], "domain": ["cr... |
Hotfix for https://github.com/juspay/hyperswitch/pull/6725 | 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": 6830, "pr_title": "feat(core): payment links - add support for custom background image and layout in details section", "merged_at": "2024-12-12T18:02:04Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"api_models": ["crates/api_models/src/admin.rs", "... |
- add a extra object `device_data` in payment request for both 3ds and no 3ds Cards for connector Airwallex | 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`
**3. External Connector Integrati... | {"pr_number": 6881, "pr_title": "refactor(connector): [Airwallex] add device_data in payment request", "merged_at": "2024-12-22T17:58:07Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/payments.... |
<!-- Describe your changes in detail -->
Added payment webhooks for Xendit. | 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": 7277, "pr_title": "feat(xendit): Add Payment Webhooks ", "merged_at": "2025-03-04T08:57:14Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/connector_configs/toml/development.toml", "crates/connec... |
<!-- Describe your changes in detail -->
- Added `check-gift-card-balance` API
- Added `GiftCardBalanceCheck` flow for connectors and implemented it for Adyen
- Updated PML flow to store gift card enabled MCA in redis
<img width="2314" height="1286" alt="image" src="https://github.com/user-attachments/assets/5008... | 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_data_... | {"pr_number": 9102, "pr_title": "feat(router): Add gift card balance check endpoint (v2)", "merged_at": "2025-09-17T07:50:47Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user", "connector"]}, "hierarchy": {"api_models": ["crates/api_models/src/events/payment.rs", "cra... |
<!-- Describe your changes in detail -->
Previously unified error codes and messages were Optional. Hence if nothing is being returned by the connector, it displays as null. Mapped it with the default ones now. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payouts.rs` | {"pr_number": 9262, "pr_title": "feat(payouts): Mapped Default Values to Unified Error Code and Message", "merged_at": "2025-09-03T15:49:59Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core/p... |
<!-- Describe your changes in detail -->
Main PR - https://github.com/juspay/hyperswitch/pull/8264
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" />
Ra... | 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": 8267, "pr_title": "refactor: add infra-values in intent kafka events", "merged_at": "2025-06-06T07:17:11Z", "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 -->
- Regex for matching card network is updated to keep it in consistency with the frontend
- fix bug for card network where even if it is a co-badged card, it takes card network from the card api
Note: This is a pr against https://github.com/juspay/hyperswitch/pull/6801 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payments/helpers.rs`
**2. Other**
- `crates/cards/src/validate.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (2 changes) | {"pr_number": 6804, "pr_title": "fix(router): card network for co-badged card and update regex", "merged_at": "2024-12-11T13:01:08Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core/payments/he... |
<!-- Describe your changes in detail -->
added merchant acquirer create and list module | 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/lib.rs`
- `crates/api_models/src/profile_acquirer.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/sr... | {"pr_number": 8155, "pr_title": "feat(authentication): added profile acquirer create module", "merged_at": "2025-06-11T13:53:52Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/admin.rs", "crates/api_m... |
This PR adds billing connector invoice sync flow to revenue recovery. This is used to fetch invoice details from billing connectors. There is some invoice related information which are needed for revenue recovery system but our current flow is not enough for it. This PR just adds BIllingConnectorInvoiceSync Flow to Rev... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/router_data_v2/flow_common_types.rs`
- `crates/hyperswitch_domain_models/src/router_flow_types/revenue_recovery.rs`
- `crates/hype... | {"pr_number": 7799, "pr_title": "feat(core): Adds Billing Connector Invoice Sync flow in Revenue Recovery", "merged_at": "2025-04-29T07:26:23Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "connector", "webhook"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_mode... |
<!-- Describe your changes in detail -->
google recently [introduced](https://developers.google.com/pay/api/web/reference/response-objects#CardInfo) new field called `cardFundingSource`. It is an upcoming gpay api change
it takes an enum:
- `UNKNOWN`
- `CREDIT`
- `DEBIT`
- `PREPAID`
google has mentioned ... | 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": 9571, "pr_title": "refactor(core): introduce new field `cardFundingSource` to `GooglePayPaymentMethodData`", "merged_at": "2025-10-01T09:57:43Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_... |
Handle Missing Sequential Automatic case for Paybox MIT | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/paybox/transformers.rs` | {"pr_number": 6833, "pr_title": "fix(connector): Handle Sequential Automatic case in MIT payments", "merged_at": "2025-03-18T13:06:55Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/... |
<!-- Describe your changes in detail -->
Open API reference for Intelligent router | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Configuration Files**
- `api-reference/hyperswitch_intelligent_router_open_api_spec.yml`
**2. Other**
- `api-reference/intelligent-router-api-reference/elimination/fetch-eliminated-processor-list.mdx`
- `api-... | {"pr_number": 7727, "pr_title": "feat: Add open API reference for Intelligent router", "merged_at": "2025-04-08T09:39:44Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"config": ["api-reference/hyperswitch_intelligent_router_open_api_spec.yml"], "other": ["a... |
<!-- Describe your changes in detail -->
Add SMTP support to allow mails through self-hosted/custom SMTP server
#5156 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `loadtest/config/development.toml`
**2. Configuration Files**
- `config/development.toml`
- `config/docker_compose.toml`
- `crates/external_services/Cargo.toml`
- ... and 1 more files
**3. Ot... | {"pr_number": 6617, "pr_title": "feat(email): Add SMTP support to allow mails through self hosted/custom SMTP server", "merged_at": "2024-11-20T14:48:30Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"tests": ["loadtest/config/development.toml"], "config": [... |
<!-- Describe your changes in detail -->
https://github.com/juspay/hyperswitch/pull/3953
We were not considering the status of payment method in above filtering logic | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payment_methods/cards.rs` | {"pr_number": 7004, "pr_title": "fix: consider status of payment method before filtering wallets in list pm", "merged_at": "2025-01-07T17:07:46Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/cor... |
<!-- Describe your changes in detail -->
remove unified_authentication_service base_url from integ, sandbox and production toml | 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/env_specific.toml`
- `config/deployments/production.toml`
- `config/deployments/sandbox.toml` | {"pr_number": 6865, "pr_title": "chore(env): remove unified_authentication_service base_url from integ, sandbox and production toml", "merged_at": "2024-12-18T08:28:08Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"tests": ["config/deployments/integration_test.to... |
<!-- Describe your changes in detail --> | 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": 8544, "pr_title": "feat(connector): [MPGS] template code", "merged_at": "2025-07-25T09:32:26Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/connector_endpoints.rs"], "connectors": ["crates/connector_co... |
<!-- Describe your changes in detail -->
This pr adds Samsung pay mandate support for Cybersource and enable samsung pay for cybersource on sandbox. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/connector_configs/toml/sandbox.toml`
- `crates/hyperswitch_connectors/src/connectors/cybersource.rs`
- `crates/hyperswitch_connectors/src/connectors/cybersource/trans... | {"pr_number": 7298, "pr_title": "feat(connector): add Samsung pay mandate support for Cybersource", "merged_at": "2025-02-22T08:40:23Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/connector_configs/toml/sand... |
<!-- Describe your changes in detail -->
add payment incoming webhooks support for v2 | 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`
- `crates/api_models/src/webhooks.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/payment_attempt.rs`
- `crates/... | {"pr_number": 6551, "pr_title": "feat(router): add payment incoming webhooks support for v2", "merged_at": "2024-11-19T09:35:08Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user", "webhook"]}, "hierarchy": {"api_models": ["crates/api_models/src/payments.rs", "crates/a... |
This PR exposes customizations for payment links. Below configs are added -
- SDK UI rules - https://docs.hyperswitch.io/explore-hyperswitch/merchant-controls/integration-guide/web/customization#id-4.-rules
- Payment Link UI rules - similar to SDK UI rules, but for payment link template* | 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": 7427, "pr_title": "feat(payment_link): expose payment link configs for SDK UI rules and payment button", "merged_at": "2025-03-05T17:28:25Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_mode... |
This PR adds capability for payouts to use billing address in payment_methods.
1. During first payout (with recurring: true) - payment_method entry created will store the billing address
2. During recurring payouts - stored billing address will be fetched and used | 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": 9277, "pr_title": "fix(payout): use billing address in payment_methods", "merged_at": "2025-09-08T11:39:06Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core/payments/routing.rs",... |
Before refund sync process tracker task was using pt_mapping_{connector} for sync retries (this is config name of Psync which was incorrect)
Fixes made in this PR -
- We are using pt_mapping_refund_sync_{connector}
- refund sync which was using retry_sync_task so made retry_refund_sync_task which will handle the... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/refunds.rs`
**Code Patterns Applied:**
- Implement new functions (1 changes)
- Extend existing types with new fields (4 changes)
**Detailed Identifier Changes:**
C... | {"pr_number": 8930, "pr_title": "refactor(core): refund sync process scheduled time", "merged_at": "2025-08-22T13:26:14Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core/refunds.rs"]}, "change... |
Noon has updated there Authentication api
- The mode selector has been deprecated because there is no more segregation of authentication for TEST/LIVE environment via the authorization header,
the endpoint used will take care of routing the request to the relevant environment.
Current
Mode selector is mandatory i... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/noon.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (1 changes) | {"pr_number": 7977, "pr_title": "refactor(connector): [Noon] auth header", "merged_at": "2025-05-12T15:28:52Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors/noon.rs"]}, "c... |
<!-- Describe your changes in detail -->
Instead of merchant secret we were passing webhook_verification_token which caused the build to fail
This PR raises the fix for this | 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": 7419, "pr_title": "fix(xendit): Fix wasm changes", "merged_at": "2025-03-06T10:30:04Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["merchant", "webhook", "token"]}, "hierarchy": {"connectors": ["crates/connector_configs/toml/development.toml", "crates/connector_confi... |
hotfix for [PR](https://github.com/juspay/hyperswitch/pull/6202)
1. Add support for a new endpoint post_session_tokens which can be called before the confirm call.
Use Case
- In PayPal, after the session call, when we click the PayPal button, we need to create an order. Previously, this was done in the `/confirm` ... | 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": 6346, "pr_title": "feat(core): add payments post_session_tokens flow", "merged_at": "2024-10-17T08:59:53Z", "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 -->
The installation tracking system has been upgraded to capture more information, errors and behaviors during the installation period such as:
- User aborts
- Server failure errors
- Dependency errors
- Successful installations | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Configuration Files**
- `docker-compose.yml`
**2. Other**
- `.gitignore`
- `scripts/create_default_user.sh`
- `scripts/notify_scarf.sh`
- ... and 3 more files
**Code Patterns Applied:**
- Extend existi... | {"pr_number": 8238, "pr_title": "fix: Unified scarf setup", "merged_at": "2025-06-09T07:59:11Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"config": ["docker-compose.yml"], "other": [".gitignore", "scripts/create_default_user.sh", "scripts/notify_scarf.sh"... |
Add mandates flow to paypal which they started handling recently | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `cypress-tests/cypress/e2e/PaymentUtils/Commons.js`
- `cypress-tests/cypress/e2e/PaymentUtils/Paypal.js`
**Code Patterns Applied:**
- Extend existing types with new fields (190 changes) | {"pr_number": 6794, "pr_title": "ci(cypress): Add Paypal Mandates", "merged_at": "2024-12-13T03:40:31Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"tests": ["cypress-tests/cypress/e2e/PaymentUtils/Commons.js", "cypress-tests/cypress/e2e/PaymentUtils/Paypal... |
<!-- Describe your changes in detail -->
- Refactored routing events in dynamic_routing core.
- have also added routing events for Euclid and Debit Routing | 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/errors.rs`
- `crates/router/src/core/payment... | {"pr_number": 8323, "pr_title": "refactor(routing): Routing events core refactor", "merged_at": "2025-06-17T14:49:02Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/open_router.rs", "crates/api_... |
<!-- Describe your changes in detail -->
Trigger refund outgoing webhooks in create and retrieve refund flows. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/refunds.rs`
**2. Utils**
- `crates/router/src/utils.rs`
**Code Patterns Applied:**
- Implement new functions (2 changes)
- Extend existing types with new fields (... | {"pr_number": 6635, "pr_title": "feat(refunds): Trigger refund outgoing webhooks in create and retrieve refund flows", "merged_at": "2024-11-24T20:29:33Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["merchant", "user", "refund"]}, "hierarchy": {"core_business": ["crates/router/src... |
<!-- Describe your changes in detail -->
Need to update the API doc to display Admin API Key instead of API key for Profile - Delete. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Other**
- `api-reference/openapi_spec.json`
- `crates/openapi/src/routes/profile.rs` | {"pr_number": 7697, "pr_title": "refactor(openapi): modify profile-delete auth to AdminAPIKey in API doc", "merged_at": "2025-04-03T08:06:32Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"other": ["api-reference/openapi_spec.json", "crates/openapi/src/routes/prof... |
<!-- Describe your changes in detail --> | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/router_data.rs`
**2. Core Business Logic**
- `crates/router/src/core/payments.rs`
- `crates/router/src/core/payments/helpers.rs`
... | {"pr_number": 8313, "pr_title": "fix(connector): [STRIPE] Throwing Missing Required Field Error if connector_customer is not present", "merged_at": "2025-06-11T13:24:52Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment"]}, "hierarchy": {"domain": ["crates/hyperswi... |
<!-- Describe your changes in detail -->
make `endpoint_prefix` optional in three_ds_metadata for unified_authentication_service | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/router_request_types/unified_authentication_service.rs`
**2. Core Business Logic**
- `crates/router/src/core/payments/operations/pay... | {"pr_number": 9717, "pr_title": "fix(router): make `endpoint_prefix` optional in three_ds_metadata for unified_authentication_service", "merged_at": "2025-10-07T16:44:53Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant"]}, "hierarchy": {"domain": ["crates/hypersw... |
<!-- Describe your changes in detail -->
Some cards have optional `eci_provider` which causes 4xx missing field error. Make that optional. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/nuvei/transformers.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (1 changes) | {"pr_number": 9509, "pr_title": "fix(nuvei): make `eci_provider` in applepay decrypt flow non mandatory field", "merged_at": "2025-09-24T16:51:54Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_con... |
<!-- Describe your changes in detail -->
This pull request introduces changes to improve the handling of optional configurations for dynamic routing in the gRPC client module. The updates include modifying the `GrpcClientSettings` structure to use `Option` types, enhancing error handling, and simplifying connection es... | 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/routing.rs`
- `crates/router/src/core/routing/helpers.rs`
**2. Other**
- `crates/external_services/src/grpc_cl... | {"pr_number": 8589, "pr_title": "refactor(dynamic_routing): make the dynamo configs optional", "merged_at": "2025-07-14T14:01:25Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"core_business": ["crates/router/src/core/payments/routing.rs", "crates/router/src/core/... |
<!-- Describe your changes in detail -->
Field type fixed for required fields, also enabled shift4 PMs in dashboard in this PR.
- permata_bank_transfer
- bca_bank_transfer
- bni_va
- bri_va
- cimb_va
- danamon_va
- mandiri_va
- seven_eleven
- mini_stop
- family_mart
- seicomart
- pay_easy
- lawson
- al... | 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 1 more files
*... | {"pr_number": 8997, "pr_title": "fix(connector): [ADYEN] field type fixed for required fields", "merged_at": "2025-09-17T12:12:59Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"connectors": ["crates/connector_configs/toml/development.... |
<!-- Describe your changes in detail -->
This PR enables and addresses the [`trivially_copy_pass_by_ref`](https://rust-lang.github.io/rust-clippy/master/index.html#trivially_copy_pass_by_ref) clippy lint. The lint helps identify places in code where types which implement the `Copy` trait are passed by reference, whi... | To implement this **refund** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/connector_enums.rs`
**2. Database Layer (Queries & Schema)**
- `crates/analytics/src/query.rs`
**3. Core Business Logic**
- `crates/analytics/src/api_event/cor... | {"pr_number": 6724, "pr_title": "chore: enable `clippy::trivially_copy_pass_by_ref` lint and address it", "merged_at": "2024-12-05T15:09:29Z", "intent": {"feature_type": "refund", "action": "add_feature", "entities": ["refund"]}, "hierarchy": {"api_models": ["crates/api_models/src/connector_enums.rs"], "database": ["cr... |
<!-- Describe your changes in detail -->
Changes in this PR.
* Changed the types of following fields in PaymentIntent Diesel and Domain models to appropriate Structs from `serde::Value`
* Renamed `struct AuthenticationDataV2 `to `AuthenticationData` and added v1 and v2feature flags | 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/lib.rs`
- `crates/diesel_models/src/payment_intent.rs`
- `crates/die... | {"pr_number": 6393, "pr_title": "chore: change serde value to strict type in payment intent domain and diesel model", "merged_at": "2024-11-08T07:49:50Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment"]}, "hierarchy": {"api_models": ["crates/api_models/src/payments.rs"], "da... |
<!-- Describe your changes in detail -->
this pr fixes typos. | 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. Core Business Logic**
- `crates/router/src/core/payments/routing/utils.rs`
**3. External Connector Integration**
- `crates/hyperswitch_co... | {"pr_number": 8918, "pr_title": "fix: typos", "merged_at": "2025-08-13T10:55:54Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"api_models": ["crates/api_models/src/admin.rs"], "core_business": ["crates/router/src/core/payments/routing/utils.rs"], "connectors": ["... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.