prompt stringlengths 6 90.9k | response stringlengths 121 18.6k | metadata stringlengths 314 42.3k |
|---|---|---|
<!-- Describe your changes in detail -->
https://github.com/juspay/hyperswitch/pull/9629
This pull request enhances cache management for connector creation by introducing a new mechanism to invalidate related cache entries whenever a new connector is added. The main change is the addition of the `redact_cgraph_cache`... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/admin.rs`
- `crates/router/src/core/routing/helpers.rs`
**Code Patterns Applied:**
- Implement new functions (1 changes)
- Extend existing types with new fields (3... | {"pr_number": 9639, "pr_title": "refactor(core): add cache redaction for cgraph", "merged_at": "2025-10-01T11:30:08Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core/admin.rs", "crates/router/... |
<!-- Describe your changes in detail -->
After making a `capture` call following the `Payments-Create` call, the backend was returning an incorrect error message, incorrectly indicating an issue with the `capture_method`. This is because, after the `Payments-Create` call, the payment status was being set to `process... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/router/src/connector/nmi/transformers.rs` | {"pr_number": 7200, "pr_title": "fix(connector): fix incorrect mapping of attempt status in NMI connector", "merged_at": "2025-02-10T13:04:10Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/router/src/connecto... |
<!-- Describe your changes in detail --> | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/adyen/transformers.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (12 changes) | {"pr_number": 8871, "pr_title": "feat(connector): add support of passing metadata in adyen payment request", "merged_at": "2025-08-11T10:19:22Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connec... |
<!-- Describe your changes in detail -->
Hotfix for https://github.com/juspay/hyperswitch/pull/9075
We need to make update payment methods API which can update the fields of the records in payment methods table. It will consume a CSV file which will have batch update entries. Currently it should only update connect... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/payment_methods.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/payment_method.rs`
**3. Domain Models (Business Logic Types)**
... | {"pr_number": 9242, "pr_title": "feat(core): Update payment methods api", "merged_at": "2025-09-02T13:22:22Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"api_models": ["crates/api_models/src/payment_methods.rs"], "database": ["crates... |
The PR
- Add merchant order reference id filter for payments list
- Fix bug for search by refund id (or payment_id), using `or` instead of `or_filter`. Earlier we were searching in whole list, ignoring the filter previously applied in the query.
However this was the only case for when we were searching dynamically f... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/payments.rs`
**2. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/payments/payment_intent.rs`
**3. Type Definitions**
- `... | {"pr_number": 6630, "pr_title": "feat(payments): add merchant order ref id filter", "merged_at": "2024-11-25T14:06:30Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/payments.rs"], "domain": ["c... |
<!-- Describe your changes in detail -->
HOTFIX main pr : https://github.com/juspay/hyperswitch/pull/7970#
issue : https://github.com/juspay/hyperswitch-cloud/issues/9421
Disable payment update via client config and allow using config if needed
🔴 remove from config after some time and completely depricate upd... | 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_update.rs`
**2. Utils**
- `crates/common_utils/src/id_type/merchant.rs`
**Code Patte... | {"pr_number": 8012, "pr_title": "fix(payment): disable payment update via client config", "merged_at": "2025-05-13T13:37:56Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core/payments/helpers.r... |
This removes the redundant `ReconOps` variant from `PermissionGroup` enum which is stored in DB. This was kept back in application for backwards compatibility. Migrations are added for this and this will not be needed anymore. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Other**
- `crates/common_enums/src/enums.rs`
- `crates/router/src/services/authorization/info.rs`
- `crates/router/src/services/authorization/permission_groups.rs`
- ... and 2 more files
**Code Patterns Ap... | {"pr_number": 6985, "pr_title": "chore(roles): remove redundant variant from PermissionGroup", "merged_at": "2025-02-06T14:29:12Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"other": ["crates/common_enums/src/enums.rs", "crates/router/src/services/authorization/... |
<!-- Describe your changes in detail -->
Remove metadata, additional_merchant_data and connector_wallets_details from connector list API. To prevent exposure of sensitive data. | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/admin.rs`
**2. Type Definitions**
- `crates/router/src/types/transformers.rs`
**3. Tests**
- `cypress-tests/cypress/support/commands.js`
**4. Other**
- `a... | {"pr_number": 6583, "pr_title": "refactor(router): remove metadata, additional_merchant_data and connector_wallets_details from connector list api", "merged_at": "2024-11-20T14:48:30Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"api_models... |
<!-- Describe your changes in detail -->
This PR adds outgoing payment webhooks for v2. This PR improves the webhook delivery flow by introducing traits to enhance extensibility and modularity. Additionally, it optimizes the raise_webhooks_analytics_event process by removing an unnecessary database fetch. | 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/events.rs`
**3. Domain Models (B... | {"pr_number": 6613, "pr_title": "feat(router): add outgoing payment webhooks for v2", "merged_at": "2025-05-13T19:15:19Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/payments.rs", "crates/api_... |
Fixes https://github.com/juspay/hyperswitch/issues/9822 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/adyenplatform/transformers/payouts.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (1 changes) | {"pr_number": 9823, "pr_title": "fix(connector): [adyenplatform] use YYYY format for expiry year", "merged_at": "2025-10-14T08:40:47Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/c... |
<!-- Describe your changes in detail -->
in the previous pr that targeted nordea integration, metadata changes were lost due to conflicts resolutions. this pr adds that back. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/connector_validation.rs` | {"pr_number": 8958, "pr_title": "fix(connector): [nordea] add missing metadata in connector validation", "merged_at": "2025-08-18T14:48:49Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["connector"]}, "hierarchy": {"core_business": ["crates/router/src/core/connector_validation.rs"]... |
<!-- Describe your changes in detail -->
add support for network tokenization for v2/payment-methods
- added network tokenization support for create+confirm payment methods api v2
- introduced new type for network token | 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/n... | {"pr_number": 7145, "pr_title": "feat(payment_methods_v2): add support for network tokenization", "merged_at": "2025-02-14T13:51:59Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "user"]}, "hierarchy": {"api_models": ["crates/api_models/src/payment_methods.rs... |
<!-- Describe your changes in detail -->
Added Feature Matrix supported payment methods, countries and currencies for ACI, Authorizedotnet, Braintree, Fiuu, Forte and Placetopay. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/aci.rs`
- `crates/hyperswitch_connectors/src/connectors/authorizedotnet.rs`
- `crates/hyperswitch_connectors/src/connectors/brai... | {"pr_number": 7854, "pr_title": "feat(connector): [ACI, AUTHORIZEDOTNET, BRAINTREE, FIUU, FORTE, PLACETOPAY] Supported features for feature matrix", "merged_at": "2025-05-12T16:21:53Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "refund"]}, "hierarchy": {"co... |
<!-- Describe your changes in detail -->
**Overcapture** allows a merchant to capture more than the originally authorized amount for a transaction. In most cases, this is controlled by a connector-level configuration. However, some connectors (such as Stripe) also allow merchants to explicitly request overcapture via ... | 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": 8949, "pr_title": "feat(router): add support for overcapture", "merged_at": "2025-09-09T09:37:16Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/admin.rs", "crates/api_models/src/p... |
<!-- Describe your changes in detail -->
- Add split_txns_enabled field to business_profile DB, create+update API calls
- Add split_txns_enabled field in PaymentIntent
- PML changes to filter payment methods based on split_enabled in MCA and split_txns_enabled in Intent | 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": 9049, "pr_title": "feat(router): Payment Intent and MCA changes for split payments", "merged_at": "2025-09-01T13:47:28Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/admin.rs", "c... |
Update cypress to latest version `14.2.0` | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `cypress-tests/package-lock.json`
- `cypress-tests/package.json` | {"pr_number": 7640, "pr_title": "chore(cypress): bump cypress to `v14.2.0`", "merged_at": "2025-03-26T11:42:11Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"tests": ["cypress-tests/package-lock.json", "cypress-tests/package.json"]}, "change_types": {}, "ha... |
Hotfix for [8342](https://github.com/juspay/hyperswitch/pull/8342) | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/archipel/transformers.rs`
**Code Patterns Applied:**
- Implement new functions (3 changes)
- Extend existing types with new fields (6... | {"pr_number": 8364, "pr_title": "fix(connector): [ARCHIPEL] Change connector fields that are currently implemented as required in the code to optional", "merged_at": "2025-06-17T09:29:52Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"connectors": ["crates/hypersw... |
connector integration template code for stripe billing.
Issue: This PR closes the issue #7212 | 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": 7228, "pr_title": "feat(connector): add template code for stripebilling", "merged_at": "2025-03-03T10:35:30Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["connector"]}, "hierarchy": {"core_business": ["crates/router/src/core/payments/connector_integration_v2_impls.rs... |
<!-- Describe your changes in detail -->
This pull request includes a number of changes to the `gsm` module across multiple files to introduce new features and improve the existing code structure. The most important changes include the addition of new fields and enums, refactoring of existing enums, and introducing do... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/gsm.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/gsm.rs`
- `crates/diesel_models/src/schema.rs`
- `crates/diesel_models/sr... | {"pr_number": 7771, "pr_title": "feat(router): introduce `feature` and `feature_data` to gsm", "merged_at": "2025-07-31T10:59:53Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/gsm.rs"], "datab... |
<!-- Describe your changes in detail -->
This PR revert #6734 in main
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": 7717, "pr_title": "revert: implement `NameType` for name validation (#6734)", "merged_at": "2025-04-03T13:50:46Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["card"]}, "hierarchy": {"api_models": ["crates/api_models/src/customers.rs", "crates/api_models/src/mandates.... |
<!-- Describe your changes in detail -->
In our current implementation of `Card Testing Guard`, the `card_testing_guard_config` can be `NULL`
for existing profiles. That has been fixed in this PR to return the default values for `card_testing_guard_config` in case the underlying data is `NULL` | 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. Core Business Logic**
- `crates/router/src/core/admin.rs`
**3. Type Definitions**
- `crates/router/src/types/api/admi... | {"pr_number": 7478, "pr_title": "fix(core): [CARD TESTING GUARD] Added Card Testing Guard Config response in case of NULL", "merged_at": "2025-04-21T08:49:18Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"database": ["crates/diese... |
<!-- Describe your changes in detail -->
Original PR - https://github.com/juspay/hyperswitch/pull/8158 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/open_router.rs`
- `crates/api_models/src/routing.rs`
**2. Core Business Logic**
- `crates/router/src/core/payments/routing.rs`
**3. Configuration Files*... | {"pr_number": 8160, "pr_title": "refactor(success_based): add support for exploration", "merged_at": "2025-05-28T06:51:15Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"api_models": ["crates/api_models/src/open_router.rs", "crates/api_models/src/routing.rs"], "co... |
<!-- Describe your changes in detail -->
This PR resolves the v2 warnings generated in api_models. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/admin.rs`
- `crates/api_models/src/events/payment.rs`
- `crates/api_models/src/events/refund.rs`
- ... and 2 more files
**Code Patterns Applied:**
- I... | {"pr_number": 7353, "pr_title": "chore: resolve v2 warnings in api_models", "merged_at": "2025-04-30T11:34:53Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"api_models": ["crates/api_models/src/admin.rs", "crates/api_models/src/events/payment.rs", "crates/api_mod... |
This PR adds functionality to
- Create QR image data URI for a given hex color
- Send back the border color and display text message along with the QR data in `NextActionData` - which is consumed by SDK to take next action
Described in #7405 | 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. External Connector Integration**
- `crates/hyperswitch_... | {"pr_number": 7414, "pr_title": "feat(connector): add functionality for transforming QR image color", "merged_at": "2025-03-04T11:14:11Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/payments.r... |
<!-- Describe your changes in detail -->
**Problem Statement:**
Card testing attacks involve fraudsters using stolen credit card details to make small transactions on e-commerce sites using different combinations of CVC to verify if the CVC is valid. Successful transactions indicate the card is active and the CV... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/admin.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/business_profile.rs`
- `crates/diesel_models/src/schema.rs`
- `crates/d... | {"pr_number": 7108, "pr_title": "feat(core): [Card Testing Guard] Implement Card Testing Guard ", "merged_at": "2025-02-25T01:14:06Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/admin.rs"], "d... |
<!-- Describe your changes in detail -->
Fixing the failed cypress test cases for `HiPay` connector. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `cypress-tests/cypress/e2e/configs/Payment/Hipay.js`
**Code Patterns Applied:**
- Extend existing types with new fields (151 changes) | {"pr_number": 8563, "pr_title": "ci(cypress): fix `hipay` test cases", "merged_at": "2025-07-09T07:59:35Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user", "connector"]}, "hierarchy": {"tests": ["cypress-tests/cypress/e2e/configs/Payment/Hipay.js"]}, "change_types": {"fields_ad... |
<!-- Describe your changes in detail -->
- Add a fallback for Redis gets with prefix
- Add a Domain type for Redis for the correctness of adding a prefix
## 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 do... | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/api_locking.rs`
- `crates/router/src/core/health_check.rs`
- `crates/router/src/core/payment_methods/cards.rs`
- ... and 10 more files
**2. External Connector Inte... | {"pr_number": 7044, "pr_title": "fix(multitenancy): add a fallback for get commands in redis", "merged_at": "2025-01-16T11:11:32Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["payment", "user", "card"]}, "hierarchy": {"core_business": ["crates/router/src/core/api_locking.rs", "crates/ro... |
<!-- Describe your changes in detail -->
In Adyen: Removed enums variants with the same renamed name. Affected payment methods include
-> Lawson
-> MiniStop
-> FamilyMart
-> Seicomart
-> PayEasy
This PR doesn't cause any change to the payment request sent to Adyen.
## How did you test it?
<!--
Did you wr... | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/adyen/transformers.rs` | {"pr_number": 7601, "pr_title": "fix(connectors): [Adyen] remove redundant enums ", "merged_at": "2025-03-26T10:26:02Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors/adyen/trans... |
Currently we are not recieving field **_three_ds_requestor_challenge_ind_** in Netcetera's authentication response since the struct is incorrectly declared in the transformers file.
1. **_three_ds_requestor_challenge_ind_** is currently a part of _**NetceteraAuthenticationSuccessResponse**_ enum, but it should be a ... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/netcetera/transformers.rs`
**Code Patterns Applied:**
- Define new data structures (1 changes)
- Extend existing types with new field... | {"pr_number": 8850, "pr_title": "fix(connector): [NETCETERA] fix response field for netcetera authentication response", "merged_at": "2025-08-06T13:40:16Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connect... |
<!-- Describe your changes in detail -->
- Add SdkUpiIntentInformation struct and NextActionData variant for URI responses
- Add UpiQr payment method type with exhaustive pattern matching across all connectors | 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/payments/additional_info.rs`
**2. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/pa... | {"pr_number": 9716, "pr_title": "feat(core): add support for upi_intent and upi_qr", "merged_at": "2025-10-13T13:09:37Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/payments.rs", "crates/api_m... |
<!-- Describe your changes in detail -->
This PR adds batch encryption for the payment intent create and payment intent confirm apis. This also refactors the `to_encryptable` operation to fix a small bug which considers the inner type and ignores the annotated types in certain conditions.
This PR also adds a domain... | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/address.rs`
- `crates/hyperswitch_domain_models/src/lib.rs`
- `crates/hyperswitch_domain_models/src/payments.rs`
- ... and 1 more fil... | {"pr_number": 6589, "pr_title": "refactor(payments_v2): use batch encryption for intent create and confirm intent", "merged_at": "2024-11-26T09:10:41Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["payment"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/address.rs", "c... |
#8389
- Added Kv Redis support to - payment_intent V2, payment_attempt V2 models
- Added enable Kv route for v2 merchant-account
added enable kv api for v2 merchant account
`
curl --location 'https://<host>/v2/merchant-accounts/:mid/kv' \
--header 'Authorization: admin-api-key=***' \
--header 'x-organization... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/kv.rs`
- `crates/diesel_models/src/payment_attempt.rs`
- `crates/diesel_models/src/payment_intent.rs`
**2. Core Business Logic**
- `crates/ro... | {"pr_number": 8198, "pr_title": "feat: Kv changes for V2 feature", "merged_at": "2025-06-26T14:22:59Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant"]}, "hierarchy": {"database": ["crates/diesel_models/src/kv.rs", "crates/diesel_models/src/payment_attempt.rs", "... |
Hotfix for https://github.com/juspay/hyperswitch/pull/9791 | 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/payment_methods/migration.rs`
**Code Patterns Applied:**
- Implement new functions... | {"pr_number": 9812, "pr_title": "feat(migration): add connector_customer updation support to batch PM update API", "merged_at": "2025-10-13T11:58:33Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"api_models": ["crates/api_models/src/payment_methods.rs"], "core_bu... |
<!-- Describe your changes in detail -->
Added Authorize/PSync/IncomingWebhooks flow for Boleto Payment Method in Santander Connector | 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": 9008, "pr_title": "feat(connector): [SANTANDER] Added Boleto Payment Method", "merged_at": "2025-09-03T13:16:18Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user", "connector"]}, "hierarchy": {"api_models": ["crates/api_models/src/payments.rs"], "domain"... |
<!-- Describe your changes in detail -->
A 5xx error log in DR metrics was spamming in alerts.
Have removed the log | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/routing/helpers.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (32 changes)
- Add conditional logic for feature flags or filtering (6 changes)... | {"pr_number": 7335, "pr_title": "fix(routing): Fixed 5xx error logs in dynamic routing metrics", "merged_at": "2025-02-21T18:31:05Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user"]}, "hierarchy": {"core_business": ["crates/router/src/core/routing/helpers.rs"]}, "cha... |
<!-- Describe your changes in detail -->
1. Allow Accept Liability/ Submit Evidence during pre-arbitration and when the dispute is in challenge state
2. Remove the list_dispute_supported_connectors flag from prod as vantiv's prod url for the same is unknow
3. Extensively handle the dispute status from vantiv
##... | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/disputes.rs`
- `crates/router/src/core/utils.rs`
**2. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/worldpayvantiv/transformers.rs`... | {"pr_number": 8862, "pr_title": "fix(router): [worldpayvantiv] dispute validations and statuses", "merged_at": "2025-08-07T08:13:17Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["payment", "merchant", "connector"]}, "hierarchy": {"core_business": ["crates/router/src/core/disputes.rs", "... |
<!-- Describe your changes in detail -->
this pr adds comprehensive apple pay support to the paysafe connector, enabling merchants to process apple pay transactions through paysafe's payment gateway
- dynamic account id detection for apple pay for both encrypt and decrypt flows
- payment via apple pay in paysafe... | 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/connector_configs/src/connector.rs`
- `crates/connector_configs/toml/development.toml`
- `crates... | {"pr_number": 9358, "pr_title": "feat(connector): [paysafe] introduce applepay encrypt and predecrypt flow", "merged_at": "2025-09-24T16:58:56Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core... |
<!-- Describe your changes in detail -->
remove straight through routing from routing approach so that it does not break in stagger.
main PR - https://github.com/juspay/hyperswitch/pull/8695 | 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`
**2. Other**
- `crates/common_enums/src/enums.rs`
**Code Patterns Applied:**
- Modify database quer... | {"pr_number": 8694, "pr_title": "fix: remove straight through routing from routing approach", "merged_at": "2025-07-21T11:07:17Z", "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 -->
This pull request introduces significant updates to the dynamic routing logic, focusing on enhancing the success-based routing mechanism and improving the integration with the "open router" service. Key changes include the addition of a new helper method, refactoring of existin... | 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": 7961, "pr_title": "refactor(open_router): call elimination routing of open router if enabled instead of dynamo", "merged_at": "2025-05-12T14:19:41Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment"]}, "hierarchy": {"api_models": ["crates/api_models/src/routing.r... |
<!-- Describe your changes in detail -->
- card network fetch from db was not being populated in payment call resulting in sending the default value which failed the payment
- util function have been added to collect the card network from additional_payment_method_data
- ucaf_indicator is being populated for masterc... | 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`
**2. Core Business Logic**
- `crates/router/src/core/admin.rs`
- `crates/router/src/core/payments/transforme... | {"pr_number": 7473, "pr_title": "fix(router): pass card network for external 3DS from additional_payment_method_data", "merged_at": "2025-03-11T15:06:05Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"domain": ["crates/hyperswitch_... |
<!-- Describe your changes in detail -->
This PR is for code changes which sends the metadata passed in payment intent create to authorizedotnet as request payload, as per merchant requirements.
The merchant receives a receipt of the transaction through email, which contains the metadata passed by the merchant ... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/router/src/connector/authorizedotnet/transformers.rs`
**Code Patterns Applied:**
- Define new data structures (2 changes)
- Implement new functions (1 changes)
- Extend ex... | {"pr_number": 7011, "pr_title": "refactor(connector): [AUTHORIZEDOTNET] Add metadata information to connector request", "merged_at": "2025-02-05T14:48:45Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/router/... |
fix amount conversion framework for Rapyd
According to doc - https://docs.rapyd.net/en/create-payment.html , amount should be of FloatType (BaseUnit).
hotfix for -[7466]( https://github.com/juspay/hyperswitch/pull/7466) | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/rapyd.rs`
- `crates/hyperswitch_connectors/src/connectors/rapyd/transformers.rs`
**Code Patterns Applied:**
- Implement new functi... | {"pr_number": 7515, "pr_title": "refactor(connector): [Rapyd] fix amount conversion framework", "merged_at": "2025-03-13T08:50:05Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "connector"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors/rapy... |
Integrate Paysafe connector - No 3ds Cards
Flows
- Payment
- Psync
- Capture
- Void
- Refund
- Refund Sync | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/connector_validation.rs`
- `crates/router/src/core/payments.rs`
**2. External Connector Integration**
- `crates/common_enums/src/connector_enums.rs`
- `crate... | {"pr_number": 9127, "pr_title": "feat(connector): [Paysafe] Integrate no 3ds card", "merged_at": "2025-09-08T16:13:30Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core/connector_validation.rs"... |
<!-- Describe your changes in detail -->
This PR includes minor fixes suggested in my previous PR #6836. This PR includes the following changes:
- Import `CustomerUpdateRequestInternal` instead of fully qualifying it.
- Renames the `fetch_domain_model_and_update_and_generate_delete_customer_response()` method to... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/events/customer.rs`
- `crates/api_models/src/payments.rs`
**2. Core Business Logic**
- `crates/router/src/core/customers.rs`
- `crates/router/src/core... | {"pr_number": 6876, "pr_title": "refactor(customers_v2): include minor fixes for customer v2 flows", "merged_at": "2024-12-20T08:30:05Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment"]}, "hierarchy": {"api_models": ["crates/api_models/src/events/customer.rs", "c... |
<!-- Describe your changes in detail -->
Update open-api spec of /relay request to make the data untagged enum. | 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/relay.rs` | {"pr_number": 6942, "pr_title": "docs(openapi): update /relay request example", "merged_at": "2024-12-26T10:48:35Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"other": ["api-reference/openapi_spec.json", "crates/openapi/src/routes/relay.rs"]}, "change_type... |
<!-- Describe your changes in detail -->
Add support to retry a transaction with clear PAN or Network Token
- added support for clear pan retry with same connector when previous attempt failed with payment method data - network token.
- refactored `make_pm_data` which does fetch payment method data from locker and c... | 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/gsm.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/business_profile.rs`
- `crates/diesel_... | {"pr_number": 6905, "pr_title": "feat(router): Add support for retries with clear pan and network token payment method data", "merged_at": "2025-03-03T09:21:24Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "connector", "session"]}, "hierarchy": {"api_models": ["crates/a... |
<!-- Describe your changes in detail -->
Enable configuration of extended authorization through the profile update call, and include supported payment methods and payment method types for extended authorization. | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/admin.rs`
**2. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/business_profile.rs`
**3. Core Business Logic**
- `crates/router... | {"pr_number": 9237, "pr_title": "fix(core): add extended authorization to profile update and add supported payment method types ", "merged_at": "2025-09-03T08:31:41Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/ap... |
<!-- Describe your changes in detail -->
Added a dummy billing connector whose conector type is **billing processor** to support recovery flow. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/enums.rs`
**2. Core Business Logic**
- `crates/router/src/core/admin.rs`
**3. External Connector Integration**
- `crates/common_enums/src/connector_enum... | {"pr_number": 7819, "pr_title": "feat(connector): Add dummy billing connector auth flow", "merged_at": "2025-04-23T07:00:54Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "connector"]}, "hierarchy": {"api_models": ["crates/api_models/src/enums.rs"], "core_bus... |
Changed currency from MinorUnit to FloatMajorUnit | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/bitpay.rs`
- `crates/hyperswitch_connectors/src/connectors/bitpay/transformers.rs`
**Code Patterns Applied:**
- Implement new func... | {"pr_number": 7378, "pr_title": "fix(connector): [BITPAY] Fixed Currency Conversion", "merged_at": "2025-03-03T09:07:19Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user", "card"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors/bitpay.rs",... |
<!-- Describe your changes in detail -->
Fixed Fiuu connector to properly handle and return `error_code` and `error_message` for failed FPX transactions. The connector was previously receiving error information during redirection back to Hyperswitch but was not populating these fields in API responses after redirect... | 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:**
- Define new data structures (3 changes)
- Implement new functions (1 changes)
- Ext... | {"pr_number": 8124, "pr_title": "fix(connector): [Fiuu] populate error_code and error_desc for redirection flows if they're not present in PSync", "merged_at": "2025-05-23T12:12:54Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"co... |
This PR includes following changes
1. Added Access Token Error struct for Deutschebank
DeutscheBank connector can send error of following type in case of Access Token issues
https://testmerch.directpos.de/rest-api/apidoc/v2.1/index.html#api-securityAccessTokenError
![Image](https://github.com/user-attachments/... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/deutschebank.rs`
- `crates/hyperswitch_connectors/src/connectors/deutschebank/transformers.rs`
**2. Configuration Files**
- `co... | {"pr_number": 7127, "pr_title": "feat(connector): [Deutschebank] Add Access Token Error struct", "merged_at": "2025-02-05T15:34:18Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "user"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connect... |
<!-- Describe your changes in detail -->
Hotfix raised against: https://github.com/juspay/hyperswitch/pull/8881 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payments.rs`
**Detailed Identifier Changes:**
Commit 7e816b69:
Files to modify:
**crates/router/src/core/payments.rs**
Modify existing code | {"pr_number": 8882, "pr_title": "fix(core): Fix Applepay/Gpay for Trustpay", "merged_at": "2025-08-08T16:18:53Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core/payments.rs"]}, "change_types":... |
<!-- Describe your changes in detail -->
The S3 Source File Name in Postman Collection Runner Workflow has been changed because the Connector Auth File has been updated. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Configuration Files**
- `.github/workflows/postman-collection-runner.yml`
**Code Patterns Applied:**
- Extend existing types with new fields (1 changes) | {"pr_number": 8172, "pr_title": "chore(ci): update postman ci credentials", "merged_at": "2025-05-29T15:47:43Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["connector"]}, "hierarchy": {"config": [".github/workflows/postman-collection-runner.yml"]}, "change_types": {"fields_added":... |
<!-- Describe your changes in detail -->
For iDEAL, Adyen sends the recurringDetailReference in the webhook with event_code: RECURRING_CONTRACT, instead of including it in the Authorize response. Since we currently don’t process this webhook, MIT transactions were failing.
This PR adds support to consume the requi... | 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 (12 changes)
- Add conditional logic for fe... | {"pr_number": 9347, "pr_title": "feat(connector): [ADYEN] Add support to ideal Mandate Webhook", "merged_at": "2025-09-11T14:32:09Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/con... |
Implement payments, psync and refunds flow for Gigadat | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/connector_validation.rs`
**2. External Connector Integration**
- `crates/common_enums/src/connector_enums.rs`
- `crates/connector_configs/src/common_config.rs`
... | {"pr_number": 9525, "pr_title": "feat(connector): [Gigadat] integrate interac bank redirect payment method", "merged_at": "2025-09-25T07:17:21Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core... |
Hotfix for https://github.com/juspay/hyperswitch/pull/9508 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/webhooks/incoming.rs` | {"pr_number": 9533, "pr_title": "fix(webhooks): move webhook acknowledge config to cover early deserialization errors", "merged_at": "2025-09-24T07:26:28Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"core_business": ["crates/router/src/core/webhooks/incoming.rs"... |
<!-- Describe your changes in detail -->
Add saved card flow for proxy payments:
- Card metadata is collected in the request along with tokens (bin_number and last_four digits for Card Number)
- Card Bin API is used to fetch data against card like card_network and issuer using bin number
- Card metadata is stored i... | 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_method.rs`
- `c... | {"pr_number": 8964, "pr_title": "feat(payment-methods): [Proxy] add saved card flow for proxy payments", "merged_at": "2025-08-20T11:34:48Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "token", "card"]}, "hierarchy": {"api_models": ["crates/api_models/src/payment_method... |
<!-- Describe your changes in detail -->
* Modified the `UpdateThemeRequest` API to include `email_config` for updating email theme configurations.
* Removed `lineage` from `UploadFileRequest` API. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/user/theme.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/query/user/theme.rs`
- `crates/diesel_models/src/user/theme.rs`
**3.... | {"pr_number": 8033, "pr_title": "feat(themes): Add ability to update email config for themes", "merged_at": "2025-05-16T14:17:51Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["merchant", "user"]}, "hierarchy": {"api_models": ["crates/api_models/src/user/theme.rs"], "database": ["c... |
<!-- Describe your changes in detail -->
Enabled platform feature on sandbox
With this change, users (org_admins) can create platform organizations and a default platform merchant account in the platform organization.
```toml
[platform]
enabled = true # Enable or disable platform features
allow_connected_me... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Configuration Files**
- `config/config.example.toml`
- `config/deployments/sandbox.toml` | {"pr_number": 8580, "pr_title": "feat(config): enabled platform feature on sandbox", "merged_at": "2025-07-15T07:50:56Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["merchant", "user"]}, "hierarchy": {"config": ["config/config.example.toml", "config/deployments/sandbox.toml"]}, "c... |
<!-- Describe your changes in detail -->
Added support for filters and dimensions for authentication analytics.
Filters added:
- AuthenticationConnector
- MessageVersion
Dimensions added:
- AuthenticationStatus,
- TransactionStatus,
- ErrorMessage,
- AuthenticationConnector,
- MessageVersion,
New metric... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/analytics.rs`
- `crates/api_models/src/analytics/auth_events.rs`
- `crates/api_models/src/events.rs`
**2. Database Layer (Queries & Schema)**
- `crate... | {"pr_number": 7451, "pr_title": "feat(analytics): add new filters, dimensions and metrics for authentication analytics", "merged_at": "2025-03-06T16:53:37Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user", "connector", "transaction"]}, "hierarchy": {"api_models": ["crates/api_m... |
This PR introduces the **`/create`** endpoints for dynamic routing algorithm types (Success-Based and Elimination), allowing merchants to initialize and register dynamic routing logic via a new payload-capable flow. The implementation includes support for optional configuration payloads and integration with the existin... | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/events/routing.rs`
- `crates/api_models/src/routing.rs`
**2. Core Business Logic**
- `crates/router/src/core/routing.rs`
- `crates/router/src/core/routing/h... | {"pr_number": 8755, "pr_title": "feat: added create endpoint for dynamic_routing", "merged_at": "2025-08-19T07:52:25Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/events/routing.rs", "crates/api_mod... |
1. Added zero auth mandates for Novalnet
2. Made changes so that `create_webhook_url` fn can accept `merchant_connector_account_id` instead of `connector_name` | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/router_request_types.rs`
**2. Core Business Logic**
- `crates/router/src/core/payments.rs`
- `crates/router/src/core/payments/hel... | {"pr_number": 6631, "pr_title": "feat(connector): [Novalnet] Add zero auth mandate", "merged_at": "2025-01-10T09:44:13Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/router_request_types... |
This PR introduces support for listing both static and dynamic routing algorithms under a unified API interface. To accomplish this, it refactors how routing algorithms are represented and parsed, introducing clear separation between `StaticRoutingAlgorithm` and `DynamicRoutingAlgorithm`. The new enum `RoutingAlgorithm... | 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/routing.rs`
- `crates/api_models/src/payouts.rs`
- ... and 1 more files
**2. Core Business Logic**
- `cra... | {"pr_number": 8111, "pr_title": "feat: list for dynamic routing", "merged_at": "2025-05-27T10:32:49Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "connector"]}, "hierarchy": {"api_models": ["crates/api_models/src/admin.rs", "crates/api_models/src/events/rout... |
<!-- Describe your changes in detail -->
Mandatorily send cvv to nexixpay card payments. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/nexixpay/transformers.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (3 changes) | {"pr_number": 9459, "pr_title": "fix(connectors): [Nexixpay] send cvv in nexixpay requests", "merged_at": "2025-09-21T17:12:17Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connect... |
Disable payouts in github ci check | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `.github/workflows/cypress-tests-runner.yml` | {"pr_number": 6729, "pr_title": "ci(cypress): disable payouts in PR check ", "merged_at": "2024-12-03T11:08:51Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["connector"]}, "hierarchy": {"tests": [".github/workflows/cypress-tests-runner.yml"]}, "change_types": {}, "has_identifier_d... |
<!-- Describe your changes in detail -->
- enabled video recording for tests that fail
- cybersource connector in github ci, randomly goes through `frictionless` flow without challenge which results in certain expected elements to go missing resulting in respective tests to fail
- this pr forces cybersource to use... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `.github/workflows/cypress-tests-runner.yml`
- `cypress-tests/.gitignore`
- `cypress-tests/cypress.config.js`
- ... and 3 more files
**Code Patterns Applied:**
- Extend existing types with new fi... | {"pr_number": 7057, "pr_title": "fix(cypress): address cybersource redirection inconsistency", "merged_at": "2025-01-21T07:06:52Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user", "connector", "card"]}, "hierarchy": {"tests": [".github/workflows/cypress-tests-runner.yml", "cypr... |
<!-- Describe your changes in detail -->
updated add_connector.sh script, to make a entry in required places. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `add_connector_updated.md`
- `scripts/add_connector.sh`
**Code Patterns Applied:**
- Define new data structures (4 changes)
- Implement new functions (18 changes)
- Extend exis... | {"pr_number": 7301, "pr_title": "fix(connector): [SCRIPT] Update template generating script and updated connector doc", "merged_at": "2025-02-19T21:09:17Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["connector"]}, "hierarchy": {"connectors": ["add_connector_updated.md", "scripts/... |
<!-- Describe your changes in detail -->
Updated dashboard.toml to reflect the latest dashboard changes for open-source users.
 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Configuration Files**
- `config/dashboard.toml` | {"pr_number": 7703, "pr_title": "chore(dashboard): update dashboard toml", "merged_at": "2025-04-04T09:43:48Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"config": ["config/dashboard.toml"]}, "change_types": {}, "has_identifier_data": false, "commits_match... |
## Summary | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/lib.rs`
- `crates/api_models/src/subscription.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/query/subscription.rs`
- `crates/dies... | {"pr_number": 9123, "pr_title": "feat(subscriptions): add route for creating subscription intent", "merged_at": "2025-09-18T12:36:03Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/lib.rs", "crates/ap... |
Fix the locale handling in the payment and payout links translation functionality to properly support language-location combinations like `es-ES`. Currently, the system is using the full locale value from the `Accept-Language` header without parsing it, causing translations for such locales to fail when the header incl... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payment_link/locale.js`
**2. Configuration Files**
- `crates/router/locales/en-GB.yml`
- `crates/router/locales/fr-BE.yml`
**3. Other**
- `crates/router/src... | {"pr_number": 7993, "pr_title": "fix(core): language consumption from locale in payment and payout links", "merged_at": "2025-05-12T15:38:24Z", "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 -->
Added payment_intent payment_attempt and refund kafka events for v2
Other changes:
* populate connector_metadata in AuthorizaRouterData in 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`
**2. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/payments.rs`
**3. Core Business Logic**
- `crates/route... | {"pr_number": 8328, "pr_title": "feat(kafka): add payment_intent payment_attempt and refund kafka events for v2", "merged_at": "2025-06-19T07:08:22Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user", "refund"]}, "hierarchy": {"api_models": ["crates/api_models/src/paym... |
<!-- Describe your changes in detail -->
add `apply_three_ds_strategy` in payments confirm flow
In payments confirm flow, we are calling apply_three_ds_strategy which would decide the three ds strategy based on the rule configuration
1. authentication_type - three_ds / no_three_ds
2. exemption_type - low_value / ... | 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/business_profile.rs`
**3. Core Business Logic**
- `crat... | {"pr_number": 8357, "pr_title": "feat(router): add `apply_three_ds_strategy` in payments confirm flow", "merged_at": "2025-06-23T14:32:10Z", "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 -->
use `prod` instead of `prev` in base_url for production config | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Configuration Files**
- `config/deployments/production.toml` | {"pr_number": 7381, "pr_title": "fix(connector): [NETCETERA] use `prod` instead of `prev` in base_url for production config", "merged_at": "2025-02-26T16:30:58Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"config": ["config/deployments/production.toml"]}, "chang... |
The required fields were not added for mandates for some connectors. Those fields have been configured as `required` in this PR.
Connectors I have checked for : Aci, Adyen, Authorizeddotnet, Globalpay, Multisafepay, Worldpay, Nexinets, Noon, Novalnet, Payme, Stripe, Bankofamerica, Cybersource, Wellsfargo | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/router/src/configs/defaults/payment_connector_required_fields.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (8 changes) | {"pr_number": 6930, "pr_title": "fix(connector): fix required fields for mandates supported connectors", "merged_at": "2025-03-26T12:15:45Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/router/src/configs/def... |
Template code added for new connector Xendit
https://developers.xendit.co/api-reference | 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. External Connector Integration**
- `crates/common_enums/src/connector_enums.rs`
- `crates/connector_configs/src/connector.rs`
... | {"pr_number": 6593, "pr_title": "feat(connector): [Xendit] Template PR", "merged_at": "2024-11-21T19:28:56Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["connector"]}, "hierarchy": {"api_models": ["crates/api_models/src/connector_enums.rs"], "connectors": ["crates/common_enums/src... |
<!-- Describe your changes in detail -->
Currently Click to pay is breaking due to CAVV being populated as null in the flow this PR fixes it.
## 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)... | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/router_request_types.rs`
- `crates/hyperswitch_domain_models/src/router_request_types/authentication.rs`
**2. Core Business Logic**
- `... | {"pr_number": 8019, "pr_title": "fix(router): fix Click to Pay cavv None error", "merged_at": "2025-05-20T10:46:27Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/router_request_types.rs", ... |
There is a bug fix for cybersource where the billing address contains new line then the payments are getting failed. To address that in automation have added billling address with newlinw in confirm call and expecting succeeded in the response.
## Motivation and Context
To enhance the testcase
## How did you... | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. Tests**
- `cypress-tests/cypress/e2e/PaymentUtils/Cybersource.js`
**Code Patterns Applied:**
- Extend existing types with new fields (14 changes) | {"pr_number": 6721, "pr_title": "ci(Cypress): Add testcase for newline in address", "merged_at": "2024-12-09T09:39:55Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["payment", "user"]}, "hierarchy": {"tests": ["cypress-tests/cypress/e2e/PaymentUtils/Cybersource.js"]}, "change_types": {"f... |
<!-- Describe your changes in detail -->
Moved connector Airwallex, Multisafepay, Razorpay, Shift4, Worldpay and Zsl from Router crate to hyperswitch_connectors crate. | 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": 6369, "pr_title": "refactor(connector): [AIRWALLEX, MULTISAFEPAY, RAZORPAY, SHIFT4, WORLDPAY, ZSL] Move connectors from `router` to `hyperswitch_connectors` crate", "merged_at": "2024-11-04T15:29:10Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment",... |
<!-- Describe your changes in detail -->
This pr enables payout for release | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Configuration Files**
- `crates/router/Cargo.toml` | {"pr_number": 8817, "pr_title": "refactor(config): enable payout in prod release", "merged_at": "2025-08-04T18:59:20Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"config": ["crates/router/Cargo.toml"]}, "change_types": {}, "has_identifier_data": false, "co... |
This PR introduces the following changes
1. Added additional authentication fields for 3ds external authentication, the fields are as following
- challenge_code
- challenge_code_reason
- challenge_cancel
- message_extension
2. Added additional fields for Cybersource payments request corresponding to the... | 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`
- `crates/diesel_models/src/schema.rs`
- `crates/diesel_models/src/schema_v2.rs`
**2. Domain Models (Business Logic Types)**
... | {"pr_number": 8758, "pr_title": "feat(core): Added additional authentication fields for 3ds external authentication", "merged_at": "2025-08-05T18:05:07Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user", "connector"]}, "hierarchy": {"database": ["crates/diesel_models/... |
<!-- Describe your changes in detail -->
added delay between api-locking retries for `HoldMultiple` locking mechanism.
This was missed during development before.
This is already available for Single id locking. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/api_locking.rs` | {"pr_number": 9308, "pr_title": "fix(api_locking): add delay between api-locking retries", "merged_at": "2025-09-09T13:04:26Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"core_business": ["crates/router/src/core/api_locking.rs"]}, "change_types": {}, "has_identi... |
<!-- Describe your changes in detail -->
Implemented rule based routing in payments v2.
Straight through routing in v2 will be achieved by first configuring a straight through algorithm using `routing` endpoint and then passing the `routing_algorithm_id` field in payment create intent request.
* Added validation f... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/payment_intent.rs`
- `crates/diesel_models/src/schema_v2.rs`
**2. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src... | {"pr_number": 7709, "pr_title": "feat(payments): implement routing in payments v2", "merged_at": "2025-06-03T07:37:28Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"database": ["crates/diesel_models/src/payment_intent.rs", "crates... |
<!-- Describe your changes in detail -->
- card network fetch from db was not being populated in payment call resulting in sending the default value which failed the payment
- util function have been added to collect the card network from additional_payment_method_data
- ucaf_indicator is being populated for masterc... | 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`
**2. Core Business Logic**
- `crates/router/src/core/admin.rs`
- `crates/router/src/core/payments/transforme... | {"pr_number": 7545, "pr_title": "fix(router): pass card network for external 3DS from additional_payment_method_data", "merged_at": "2025-03-18T10:03:26Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"domain": ["crates/hyperswitch_... |
<!-- Describe your changes in detail -->
- A new field in introduced in payment_intent table called extended_return_url
- This deprecate the existing return_url field since it can take string only upto length 255
- extended_return_url can now take length upto 2048 size
- write is done into the new field (extended_r... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/payments.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/payment_intent.rs`
- `crates/diesel_models/src/schema.rs`
**3. Domain ... | {"pr_number": 8135, "pr_title": "refactor(core): introduce new field in payment_intent to handle longer return_url", "merged_at": "2025-06-07T10:03:35Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "user"]}, "hierarchy": {"api_models": ["crates/api_models/src... |
<!-- Describe your changes in detail -->
This PR fixes MIT payments failing especially during NTID flow.
We previously used to get below error message during MIT Confirm call:
```log
"The provided Expiry Date is not valid.: Expiry year should be a 4 digit number greater than 2000: 30"
```
closes https://git... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/router/src/connector/adyen/transformers.rs` | {"pr_number": 6851, "pr_title": "fix(connector): add expiry year conversion for adyen mit transactions", "merged_at": "2024-12-17T11:32:24Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user"]}, "hierarchy": {"connectors": ["crates/router/src/connector/adyen/transformer... |
<!-- Describe your changes in detail -->
- Add Cards Payout through Nuvei
- Add Webhook support for Payouts in Nuvei
- Propagate error from failure response in payouts
- Create webhook_url in PayoutsData Request to pass to Psp's
Note: hotfix pr raised against https://github.com/juspay/hyperswitch/pull/9618 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/enums.rs`
**2. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/router_request_types.rs`
**3. Core Business Logic**
- `cra... | {"pr_number": 9635, "pr_title": "feat(payouts): [Nuvei] add payout flows", "merged_at": "2025-10-01T12:46:51Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "merchant", "user"]}, "hierarchy": {"api_models": ["crates/api_models/src/enums.rs"], "domain": ["crates/hyperswit... |
- Handle response deserialization error
- three_ds_requestor_challenge_ind can be vector or string | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/router_request_types/authentication.rs`
**2. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/netcet... | {"pr_number": 8988, "pr_title": "refactor: [Netcetera] Handle response deserialization error ", "merged_at": "2025-08-19T11:19:02Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/route... |
<!-- Describe your changes in detail -->
string value for each state is being refactored to the values provided by the the given file: https://github.com/juspay/hyperswitch-web/edit/main/src/States.json | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/utils.rs`
**2. Other**
- `crates/common_enums/src/enums.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (42 changes)
... | {"pr_number": 7300, "pr_title": "refactor(utils): match string for state with SDK's naming convention", "merged_at": "2025-02-19T11:00:15Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/utils.rs"], "other": ["crates... |
<!-- Describe your changes in detail -->
- Change VGS auth type from BodyKey to SignatureKey | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/vgs/transformers.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (1 changes) | {"pr_number": 9068, "pr_title": "fix(connector): Use SignatureKey for VGS auth_type", "merged_at": "2025-08-28T02:44:22Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "connector"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors/vg... |
<!-- Describe your changes in detail -->
Currently we always fetch network token for the connector that does not support network tokenization.
Fix: we ll only fetch network token if the connector supports network tokenization else fetch card details to make CIT repeat. | 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/helpers.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (2 changes)
- Add conditional... | {"pr_number": 6749, "pr_title": "fix(core): add validation to check if routable connector supports network tokenization in CIT repeat flow", "merged_at": "2024-12-10T12:40:31Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "user"]}, "hierarchy": {"core_busine... |
<!-- Describe your changes in detail -->
1. For different creds, ACI sends different redirection_data (for default account setting and the one with proper 3DS configuration). This PR handles both types of responses.
2. `connector_mandate_id` is populated.
3. Error handling added for payments that failed in redirec... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/aci/transformers.rs`
**Code Patterns Applied:**
- Implement new functions (1 changes)
- Extend existing types with new fields (58 cha... | {"pr_number": 9367, "pr_title": "fix(connector): [ACI] 3DS, connector mandate id, error handling fixed", "merged_at": "2025-09-17T17:59:19Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors... |
<!-- Describe your changes in detail -->
This pull request introduces support for **payment redirection inside an iframe**.
- **New flag added**:
- `is_iframe_redirection_enabled` has been introduced in both:
- `PaymentIntent`
- `BusinessProfile`
- **New `NextActionType`**:
- Added `RedirectI... | 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": 7976, "pr_title": "feat(core): Add Support for redirection inside Iframe ", "merged_at": "2025-05-15T11:46:48Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user", "order"]}, "hierarchy": {"api_models": ["crates/api_models/src/admin.rs", "crates/api_models... |
Add `three_ds_requestor_app_url` in business profile
Context: This is for merchant app declaring their URL within the CReq message so that the Authentication app can call the Merchant app after OOB authentication has occurred.
Scenario:
- A user is making a purchase on a merchant's mobile app.
- The transaction... | 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`
**3. Core Busi... | {"pr_number": 7589, "pr_title": "feat(core): Add three_ds_requestor_app_url in business_profile", "merged_at": "2025-03-24T11:30:28Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/admin.rs", "cr... |
<!-- Describe your changes in detail -->
add support for 3ds exemption rules in euclid crate
add
DirKeyKind::IssuerName - Name of the card issuing bank
DirKeyKind::IssuerCountry - Country of the card issuing bank
DirKeyKind::CustomerDevicePlatform - Platform of the customer's device (Web, Android, iOS)
DirKeyKi... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Type Definitions**
- `crates/common_types/src/lib.rs`
- `crates/common_types/src/three_ds_decision_rule_engine.rs`
- `crates/euclid/src/types.rs`
**2. Other**
- `crates/euclid/src/dssa/graph.rs`
- `crat... | {"pr_number": 8013, "pr_title": "feat: add support for 3ds exemption rules in euclid crate", "merged_at": "2025-05-16T14:25:55Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "merchant", "card"]}, "hierarchy": {"types": ["crates/common_types/src/lib.rs", "crates/common_t... |
<!-- Describe your changes in detail -->
Currently in non-email flow, users who are invited are not forced to change their password. This PR will add that. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Type Definitions**
- `crates/router/src/types/domain/user.rs`
**Code Patterns Applied:**
- Define new data structures (1 changes)
- Implement new functions (1 changes)
- Extend existing types with new fields (13 ch... | {"pr_number": 6483, "pr_title": "fix(users): Add force rotate password on first login for non-email flow", "merged_at": "2024-11-07T10:37:29Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["merchant", "user", "token"]}, "hierarchy": {"types": ["crates/router/src/types/domain/user.rs... |
<!-- Describe your changes in detail -->
add total-payment-method-count api. this is olap api to fetch total count of payment method of customer of given merchant 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. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/query/payment_method.rs`
**3. Domain Models (Business Logic Types)... | {"pr_number": 7479, "pr_title": "feat(payment_methods_v2): add total-payment-method-count api", "merged_at": "2025-03-12T19:11:12Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/payment_methods.... |
<!-- Describe your changes in detail -->
/relay is a api that will be used to just forward the request sent by merchant without performing any application logic on it. In this pr the changes is particular to support the refunds for the payments that was directly performed with the connector (example stripe) with out h... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/relay.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/enums.rs`
- `crates/diesel_models/src/lib.rs`
- `crates/diesel_models/s... | {"pr_number": 6879, "pr_title": "feat(router): add db interface for `/relay`", "merged_at": "2024-12-22T17:37:57Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "refund"]}, "hierarchy": {"api_models": ["crates/api_models/src/relay.rs"], "database": ["crates/di... |
Hotfix for https://github.com/juspay/hyperswitch/pull/6791 | 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. Core Business Logic**
- `c... | {"pr_number": 6793, "pr_title": "fix(core): payments - map billing first and last name to card holder name", "merged_at": "2024-12-10T17:40:27Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"api_models": ["crates/api_models/src/payments.rs"], "domain": ["crates/hy... |
<!-- Describe your changes in detail -->
The main feature is the addition of a new authentication synchronization API that allows syncing authentication data between systems. | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/authentication.rs`
**2. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/authentication.rs`
- `crates/hyperswitch_domain_models/s... | {"pr_number": 8596, "pr_title": "feat(authentication): added authentication sync api", "merged_at": "2025-07-31T07:34:43Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"api_models": ["crates/api_models/src/authentication.rs"], "domain": ["cr... |
<!-- Describe your changes in detail -->
Currently to list refunds in v2, we are using GET verb, but we are passing filters through body which is not correct. Since listing requests are generally GET requests, we pass filters through query params.
In the current scenario, passing filters through query params may re... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Other**
- `api-reference-v2/openapi_spec.json`
- `crates/openapi/src/routes/refunds.rs`
- `crates/router/src/routes/app.rs` | {"pr_number": 8289, "pr_title": "refactor(refunds_v2): Change refunds v2 list request verb from GET to POST", "merged_at": "2025-06-11T14:06:22Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"other": ["api-reference-v2/openapi_spec... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.