prompt stringlengths 6 90.9k | response stringlengths 121 18.6k | metadata stringlengths 314 42.3k |
|---|---|---|
<!-- Describe your changes in detail -->
This PR adds support for payments get intent in v2 using merchant reference id.
Note : In a distributed setup we will be having many partition, to access data efficiently we need `partition_key`. For payments partition_key is `payment_intent global-id` . So to get the partit... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/query/payment_intent.rs`
**2. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/payments/payment_intent.rs`
**3. Core... | {"pr_number": 7123, "pr_title": "feat(core): Add support for v2 payments get intent using merchant reference id", "merged_at": "2025-02-06T15:07:01Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"database": ["crates/diesel_models/s... |
<!-- Describe your changes in detail -->
add three_ds_decision_rule_algorithm to the domain and diesel models of business_profile
This is a Micro PR towards three_ds decision rule exemption engine, would be adding support to three_ds decision rules in routing apis in future PRs | 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`
- `crates/diesel_models/src/schema.rs`
- `crates/diesel_models/src/schema_v2.rs`
**2. Domain Models (Business Logic Types)*... | {"pr_number": 8106, "pr_title": "feat(router): add three_ds_decision_rule_algorithm to the domain and diesel models of business_profile", "merged_at": "2025-05-23T07:46:26Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"database": ["crates/diesel_models/src/busine... |
<!-- Describe your changes in detail -->
WASM fixed in Getnet | 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": 7564, "pr_title": "fix(connector): WASM fixed in Getnet", "merged_at": "2025-03-19T11:18:51Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"connectors": ["crates/connector_configs/toml/development.toml", "crates/connector_configs/toml/production.toml... |
<!-- Describe your changes in detail -->
1)Make installment_payment_enabled,recurring_enabled Optional
2) is_frame_redirection_enabled Field Missing in Create Business Profile API Response
3)Move CaptureMethodNotSupported error to 4xx instead of 5xx. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/admin.rs`
- `crates/api_models/src/payment_methods.rs`
**2. Core Business Logic**
- `crates/router/src/core/errors/utils.rs`
- `crates/router/src/core... | {"pr_number": 8201, "pr_title": "feat(core): Make installment_payment_enabled,recurring_enabled Optional", "merged_at": "2025-06-10T11:04:30Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/admin... |
Fixes race condition in Worldpay 3DS Device Data Collection (DDC) flow causing `bodyDoesNotMatchSchema` errors.
**Changes made:**
- Extended DDC timeout from 8s to 10s in client-side JavaScript
- Added `ddcProcessed` flag to prevent duplicate submissions on client-side
- Reject `collectionReference` submissions w... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/worldpay.rs`
- `crates/hyperswitch_connectors/src/connectors/worldpay/transformers.rs`
**2. Tests**
- `cypress-tests/cypress/e2... | {"pr_number": 8741, "pr_title": "fix(connector): [Worldpay] handle multiple ddc submission for CompleteAuthorize", "merged_at": "2025-07-29T08:47:11Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/c... |
Implement Interac payouts | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/enums.rs`
- `crates/api_models/src/payments.rs`
- `crates/api_models/src/payouts.rs`
**2. Domain Models (Business Logic Types)**
- `crates/hyperswitch... | {"pr_number": 9566, "pr_title": "feat(connector): [Gigadat] Implement interac payouts", "merged_at": "2025-10-01T09:32:28Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"api_models": ["crates/api_models/src/enums.rs", "crates/api_models/src/payments.rs", "crates/a... |
Refactored customer email and browser information in router data
## Motivation and Context
<!--
Why is this change required? What problem does it solve?
If it fixes an open issue, please link to the issue here.
If you don't have an issue, we'd recommend starting with one first so the PR
can focus on the imple... | 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`
**2. Core Business Logic**
- `crates/router/src/core/payments/transformers.rs`
**Code Patterns Applied:**
- Impl... | {"pr_number": 7034, "pr_title": "Refactor: Customer email and browser Information", "merged_at": "2025-01-21T08:49:43Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/router_request_types.rs... |
Modified api key auth to support control over VSAAS operations.
The PR provides fine grained control over routes authentication
- allowing Platform to perform payments in V1 (MVP case)
- disallowing all the operations in v2
- disallowing all other operations other than payments, for platform
- context of connected... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Other**
- `crates/router/src/compatibility/stripe/customers.rs`
- `crates/router/src/compatibility/stripe/payment_intents.rs`
- `crates/router/src/compatibility/stripe/refunds.rs`
- ... and 21 more files
*... | {"pr_number": 7593, "pr_title": "feat(vsaas): modify api key auth to support vsaas cases", "merged_at": "2025-04-16T10:50:02Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"other": ["crates/router/src/compatibility/stripe/customers... |
<!-- Describe your changes in detail -->
Add the following features in nuvie
1. Google pay decrypt flow S2S
2. Apple pay decrypt flow S2S
3. Google pay encrypt flow
4. Partial Authorization
5. Send shipping address for nuvei (previously not sent)
## Test attachment
<details>
<summary> <b>APPLE PAY ... | 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`
- `crates/router/src/types/api/connector_mappin... | {"pr_number": 8985, "pr_title": "feat(nuvei): Googlepay , applepay and partial authorization integration for nuvei", "merged_at": "2025-08-22T12:06:10Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitc... |
<!-- Describe your changes in detail --> | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/subscription.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/invoice.rs`
**3. Domain Models (Business Logic Types)**
- `crates/... | {"pr_number": 9353, "pr_title": "feat(subscriptions): Add Subscription confirm handler", "merged_at": "2025-09-25T16:22:29Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/subscription.rs"], "dat... |
Earlier a connector was occurring twice while doing a session token call for wallets. This PR fixes merchant payment method list to retain a mca based on connector_name and mca_id. So that with every distinct mca_id the connector is listed just once for wallets. | 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/cards.rs`
- `crates/router/src/core/payments.rs`
**Code Pattern... | {"pr_number": 6408, "pr_title": "fix(payment_methods): fix merchant payment method list to retain a mca based on connector_name and mca_id", "merged_at": "2024-10-24T15:05:19Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_mode... |
<!-- Describe your changes in detail -->
reordered v2 migrations folders.
* All misplaced v2 migrations are moved to `v2_compatible_migrations` directory.
* Removed `Add not null` constraints to newly added v2 columns.
* `v2_migrations` directory will only contain queries for dropping deprecated v1 columns and tab... | 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`
- `crates/diesel_models/src/customers.rs`
- `crates/diesel_models/src/lib.rs`
- ... and 5 more files
**2. External Conne... | {"pr_number": 8671, "pr_title": "chore: reorder v2 migrations folders", "merged_at": "2025-08-05T08:25:35Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"database": ["crates/diesel_models/src/business_profile.rs", "crates/diesel_mo... |
Return redacted customer response instead of error when querying deleted customers.
## Motivation and Context
Upon merging this PR, the API will return deleted Customer with redacted values instead of error.
https://github.com/juspay/hyperswitch/issues/7126
## How did you test it?
- Create Customer API Ca... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/customers.rs` | {"pr_number": 7122, "pr_title": "refactor(customer): return redacted customer instead of error", "merged_at": "2025-02-06T15:04:45Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment"]}, "hierarchy": {"core_business": ["crates/router/src/core/customers.rs"]}, "chang... |
<!-- Describe your changes in detail -->
Main pr - https://github.com/juspay/hyperswitch/pull/7004 | 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": 7012, "pr_title": "fix: consider status of payment method before filtering wallets in list pm", "merged_at": "2025-01-09T07:49:41Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"core_business": ["crates/router/src/core/payment_methods/cards.rs"]}, "c... |
<!-- Describe your changes in detail -->
- Added RoutingApproach column in Payment attempt
- Added RoutingApproach as a filter and dimension in payment analytics
- Added routing metric endpoints
DB queries -
```sql
CREATE TYPE "RoutingApproach" AS ENUM (
'success_rate_exploitation',
'success_rate_explora... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/analytics/payments.rs`
**2. Database Layer (Queries & Schema)**
- `crates/analytics/src/query.rs`
- `crates/diesel_models/src/enums.rs`
- `crates/dies... | {"pr_number": 8408, "pr_title": "feat(analytics): Add RoutingApproach filter in payment analytics", "merged_at": "2025-06-23T17:55:20Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"api_models": ["crates/api_models/src/analytics/paymen... |
Enhanced Billwerk Connector in cypress for Comprehensive Testing.
## How did you test it?
<img width="515" alt="Billwerk" src="https://github.com/user-attachments/assets/feb4d3ec-b263-4143-ba0b-2d5b4db61ea9" />
1.Savecard flow is not working (on_session & off_session) both throwing no eligible connector erro... | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. Tests**
- `cypress-tests/cypress/e2e/configs/Payment/Billwerk.js`
- `cypress-tests/cypress/e2e/configs/Payment/Utils.js`
**Code Patterns Applied:**
- Extend existing types with new fields (653 changes) | {"pr_number": 8397, "pr_title": "ci(cypress): Add billwerk connector test in cypress", "merged_at": "2025-06-20T11:28:25Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["payment", "user", "connector"]}, "hierarchy": {"tests": ["cypress-tests/cypress/e2e/configs/Payment/Billwerk.js", "cypr... |
This PR exposes three configurations for payment links
1. `payment_form_header_text` - for rendering a header text for payment links
2. `payment_form_label_type` - for specifying the type of payment form labels (floating / above / never)
3. `show_card_terms` - for controlling visibility of the terms for cards (auto ... | 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": 7742, "pr_title": "feat(payment_link): expose configurations for payment links", "merged_at": "2025-04-09T07:47:51Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/admin.rs", "crate... |
<!-- Describe your changes in detail -->
We are removing `merchant_reference_id` from all API updates, due to possible bugs on merchant side db and HS db as there might be mismatch in their's and our's db records. This exists only in customers and refunds v2 apis, a separate PR has been implemented for refunds update,... | 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`
**2. Other**
- `api-reference-v2/openapi_spec.json` | {"pr_number": 7879, "pr_title": "refactor(customers_v2): Remove merchant reference id from v2 customer update", "merged_at": "2025-06-09T07:54:14Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/... |
<!-- Describe your changes in detail -->
This pull request introduces significant changes to the Wise connector in the `crates/router` module, focusing on the integration of a new amount conversion utility and refactoring to utilize a new `WiseRouterData` struct. The changes enhance how amounts are handled and improve... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/router/src/connector/wise.rs`
- `crates/router/src/connector/wise/transformers.rs`
- `crates/router/tests/connectors/wise.rs`
**2. Type Definitions**
- `crates/ro... | {"pr_number": 6469, "pr_title": "refactor(connector): Added amount conversion framework to Wise.", "merged_at": "2024-11-07T07:36:11Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["connector"]}, "hierarchy": {"connectors": ["crates/router/src/connector/wise.rs", "crates/router/src/... |
<!-- Describe your changes in detail -->
Added support for making the sdk session token call.
The following features are not included:
1. Session routing
2. Session surcharge
Will be taken up in a different PR. | 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/merchant_con... | {"pr_number": 6502, "pr_title": "feat: add support for sdk session call in v2", "merged_at": "2024-11-28T10:28:43Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"api_models": ["crates/api_models/src/events/payment.rs", "crates/api_mode... |
<!-- Describe your changes in detail -->
add `click_to_pay` block in payments sessions response if enabled | 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": 6829, "pr_title": "feat(router): add `click_to_pay` block in payments sessions response if enabled", "merged_at": "2024-12-13T11:04:09Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "session"]}, "hierarchy": {"api_models": ["crates/api_models/src/payments.r... |
<!-- Describe your changes in detail -->
resolve spell check fail introduced by the following PR: https://github.com/juspay/hyperswitch/pull/7300 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Configuration Files**
- `.typos.toml` | {"pr_number": 7342, "pr_title": "fix(router): resolve spell check for state introduced for ISO representation", "merged_at": "2025-02-24T08:12:39Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"config": [".typos.toml"]}, "change_types": {}, "has_identifier_data": ... |
## Type of Change | 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_response_types.rs`
**2. Core Business Logic**
- `crates/router/... | {"pr_number": 9304, "pr_title": "feat(connector): Create Customer for Chargebee", "merged_at": "2025-09-18T14:29:16Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/router_request_types.rs",... |
This PR adds an Audit event for the PaymentApprove operation. | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payments/operations/payment_approve.rs`
**2. Other**
- `crates/router/src/events/audit_events.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (1 ... | {"pr_number": 6432, "pr_title": "feat(payments): Add audit events for PaymentApprove update", "merged_at": "2024-11-08T10:20:37Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["payment"]}, "hierarchy": {"core_business": ["crates/router/src/core/payments/operations/payment_approve.rs"], "o... |
<!-- Describe your changes in detail -->
connector integration template code for chargebee. | 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": 7036, "pr_title": "feat(connector): add template code for chargebee", "merged_at": "2025-01-29T11:46:59Z", "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 --> | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/user_role.rs`
**2. Core Business Logic**
- `crates/router/src/core/user_role.rs`
**3. External Connector Integration**
- `crates/router/src/routes/conne... | {"pr_number": 6394, "pr_title": "feat(authz): Create a permission generator", "merged_at": "2024-10-24T14:36:07Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"api_models": ["crates/api_models/src/user_role.rs"], "core_business": ["cra... |
<!-- Describe your changes in detail -->
This PR adds the payment methods session endpoints.
- Create a payment method session
- Retrieve a payment method session
- List the payment methods for a payment method session
- Update a saved payment method using the payment method session
## Motivation and Context
... | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/customers.rs`
- `crates/api_models/src/ephemeral_key.rs`
- `crates/api_models/src/events.rs`
- ... and 4 more files
**2. Database Layer (Queries & Schema)**... | {"pr_number": 7107, "pr_title": "feat(payment_methods_session_v2): add payment methods session endpoints", "merged_at": "2025-02-11T12:32:02Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/customers.r... |
<!-- Describe your changes in detail -->
Currently in external 3ds authentication if we cancel a txn in acs bank page it is not getting handled gracefully rather its throwing an error stating failed to fetch authentication value from temp locker.
## How did you test it?
<!--
Did you write an integration/unit/AP... | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payments/operations/payment_confirm.rs`
**2. Other**
- `crates/common_enums/src/enums.rs`
**Code Patterns Applied:**
- Implement new functions (1 changes)
- Extend exis... | {"pr_number": 9769, "pr_title": "fix(router): Added authentication success check for fetching authentication value", "merged_at": "2025-10-16T12:06:01Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/co... |
Hotfix for https://github.com/juspay/hyperswitch/pull/7211 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/fiuu.rs`
- `crates/hyperswitch_connectors/src/connectors/fiuu/transformers.rs`
**Code Patterns Applied:**
- Extend existing types ... | {"pr_number": 7231, "pr_title": "fix(connector): [fiuu] update PSync and webhooks response", "merged_at": "2025-02-10T12:37:44Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["connector"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors/fiuu.rs", "crates/... |
<!-- Describe your changes in detail -->
This PR adds version column to the organisation. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Database Layer (Queries & Schema)**
- `crates/diesel_models/Cargo.toml`
- `crates/diesel_models/src/organization.rs`
- `crates/diesel_models/src/schema.rs`
- ... and 1 more files
**2. Domain Models (Busine... | {"pr_number": 7418, "pr_title": "refactor(organization): add api version column", "merged_at": "2025-03-28T08:05:54Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"database": ["crates/diesel_models/Cargo.toml", "crates/diesel_models/src/organization.rs", "cr... |
<!-- Describe your changes in detail -->
Added support for xdel if redis client uses legacy version
https://github.com/juspay/hyperswitch/issues/8389 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Other**
- `crates/drainer/src/handler.rs`
- `crates/drainer/src/metrics.rs`
- `crates/drainer/src/services.rs`
- ... and 1 more files
**Code Patterns Applied:**
- Implement new functions (2 changes)
- Exte... | {"pr_number": 8515, "pr_title": "fix: replace xtrim with xdel to support older redis version", "merged_at": "2025-07-29T10:59:44Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"other": ["crates/drainer/src/handler.rs", "crates/drainer/src/metrics.rs", "crates/dra... |
This PR includes changes to make billing details related fields optional during batched operation of data 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/payment_methods/src/core/migration/payment_methods.rs`
**Code Patterns Applied:**
- Implement new ... | {"pr_number": 8438, "pr_title": "refactor: make billing details optional during data migration", "merged_at": "2025-06-24T17:23:39Z", "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 -->
Added Google Pay Predecrypt Flow | 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/hyperswitch_connectors/src/connectors/checkout/transformers.rs`
**3. Tests**
- `config/deployments... | {"pr_number": 9130, "pr_title": "feat(connector): [Checkout] Add Google Pay Predecrypt Flow", "merged_at": "2025-09-26T08:09:57Z", "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 PR will make connector_view group accessible by operation groups.
This PR will also change the permission of connector_retrieve API from connector_read to connector_write as it contains sensitive data. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Other**
- `crates/router/src/routes/admin.rs`
- `crates/router/src/services/authorization/permission_groups.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (1 changes) | {"pr_number": 6792, "pr_title": "refactor(authz): Make connector list accessible by operation groups", "merged_at": "2024-12-16T09:22:57Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["merchant", "user", "connector"]}, "hierarchy": {"other": ["crates/router/src/routes/admin.rs", "c... |
<!-- Describe your changes in detail -->
## Overview of the Three Crates | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/smithy-core/Cargo.toml`
- `crates/smithy-core/src/generator.rs`
- `crates/smithy-core/src/lib.rs`
- ... and 1 more files
**2. Configuration Files**
- `crates/smithy-gener... | {"pr_number": 9249, "pr_title": "feat(framework): Added smithy, smithy-core and smithy-generator crates", "merged_at": "2025-09-26T08:06:07Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment"]}, "hierarchy": {"core_business": ["crates/smithy-core/Cargo.toml", "crates/smithy-co... |
<!-- Describe your changes in detail -->
`customer_user_agent` column in `mandate` table has a `255` character length limit. Lately, there have been increased number of `5xx` errors due to the values in `customer_user_agent` column hitting that limit. This PR addresses this by introducing a new column `customer_devi... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/mandate.rs`
- `crates/diesel_models/src/schema.rs`
- `crates/diesel_models/src/schema_v2.rs`
**2. Core Business Logic**
- `crates/router/src/... | {"pr_number": 8616, "pr_title": "refactor(schema): add a new column for storing large customer user agents in mandate table", "merged_at": "2025-07-25T09:48:06Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"database": ["crates/die... |
<!-- Describe your changes in detail -->
populate `profile_id` in for the HeaderAuth of v1
And also this pr involves the changes to unmask the profile id that is sent in the headers. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `config/deployments/integration_test.toml`
- `loadtest/config/development.toml`
**2. Configuration Files**
- `config/deployments/production.toml`
- `config/deployments/sandbox.toml`
- `config/... | {"pr_number": 6936, "pr_title": "fix(router): populate `profile_id` in for the HeaderAuth of v1", "merged_at": "2024-12-26T10:49:20Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"tests": ["config/deployments/integration_test.toml", "loadtest/config/development.to... |
<!-- Describe your changes in detail -->
- Store the user query and response from the ai service for the analysis.
- Allow the api only for internal user | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/chat.rs`
- `crates/api_models/src/events/chat.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/hyperswitch_ai_interaction.rs`
... | {"pr_number": 8831, "pr_title": "feat: add hyperswitch ai chats table", "merged_at": "2025-09-16T09:14:36Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"api_models": ["crates/api_models/src/chat.rs", "crates/api_models/src/events/chat... |
This PR updates the migration flow around card validation to skip card expiry validation for `PayPal` and `SamsungPay` - these payment methods do not have the linked card's expiry details. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/payment_methods/src/core/migration/payment_methods.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (1 changes)
- Add conditional logic for feature flags or fil... | {"pr_number": 9131, "pr_title": "feat(migration): perform card validation only for allowed payment methods", "merged_at": "2025-09-03T13:04:56Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/payment_methods... |
<!-- Describe your changes in detail -->
This PR reduces build jobs to 3 to see if it helps pass Cypress CI checks | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `.github/workflows/cypress-tests-runner.yml`
**Code Patterns Applied:**
- Extend existing types with new fields (1 changes) | {"pr_number": 6453, "pr_title": "ci(cypress): reduce cargo build jobs to 3", "merged_at": "2024-10-28T15:05:23Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"tests": [".github/workflows/cypress-tests-runner.yml"]}, "change_types": {"fields_added": 1}, "has_identi... |
This PR fixes the state update for `payout_attempt` where latest status resides. This fixes the bug mentioned in https://github.com/juspay/hyperswitch/issues/9278 | 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`
**Code Patterns Applied:**
- Extend existing types with new fields (2 changes) | {"pr_number": 9283, "pr_title": "fix(payout): send latest status in outgoing webhook notifications during IncomingWebhook flow", "merged_at": "2025-09-07T14:38:56Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "merchant", "order"]}, "hierarchy": {"core_business": ["crat... |
<!-- 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": 7637, "pr_title": "chore(ci): update postman ci credentials", "merged_at": "2025-03-27T12:12:57Z", "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 -->
This PR modifies authentication queries to improve the way we distinguish between authentication flows. Previously, `trans_status` was used for this purpose, but it has now been replaced with `authentication_type`, which more explicitly differentiates between **frictionless flo... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/analytics/auth_events.rs`
- `crates/api_models/src/analytics/sdk_events.rs`
**2. Database Layer (Queries & Schema)**
- `crates/analytics/src/query.rs`
*... | {"pr_number": 7483, "pr_title": "feat(analytics): modified authentication queries and added generate report for authentications", "merged_at": "2025-03-12T11:35:14Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"api_models": ["crates/a... |
<!-- Describe your changes in detail -->
Add amount, currency and email to paze session 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. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/router_request_types.rs`
**3. Core Business Logic**
- `... | {"pr_number": 6412, "pr_title": "feat: Add amount, currency and email to paze session response", "merged_at": "2024-10-25T13:52:21Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "session", "token"]}, "hierarchy": {"api_models": ["crates/api_models/src/payments.rs"], "dom... |
In this PR, we have added integrity checks for Authorize, Capture, Refund and RSync flows for Xendit Connector
Also, moved the integrity functions from `crates/router/src/connector/utils.rs` to `crates/hyperswitch_connectors/src/utils.rs`. Thereby also changing the imports in `Stripe.rs`.
What is an integrity chec... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/xendit.rs`
- `crates/hyperswitch_connectors/src/connectors/xendit/transformers.rs`
- `crates/hyperswitch_connectors/src/utils.rs... | {"pr_number": 8049, "pr_title": "feat(connector): [XENDIT] Added Integrity Check for Authorize, Capture, Refund & RSync flows", "merged_at": "2025-05-23T09:53:17Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates... |
- This PR adds support for updating the retry Algorithm from Monitoring to Smart , once the threshold is reached
- It also adds support in the process tracker workflow for revenue recovery , to consume schedule time for retry based on different retry algorithms | 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`
- `crates/router/src/core/errors.rs`
- `crates/router/src... | {"pr_number": 7915, "pr_title": "feat(reveue_recovery): Add support for multiple retry algorithms in revenue recovery workflow", "merged_at": "2025-05-20T13:04:35Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user", "connector"]}, "hierarchy": {"database": ["crates/diesel_models/... |
Context - Cybersource payments via Netcetera are failing for a France based acquirer in prod, the PR provides fix for the same by introducing field **_consumerAuthenticationInformation. effectiveAuthenticationType_** and making sure **_consumerAuthenticationInformation.specificationVersion** is sent. | 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/types.rs`
**3. External Connector Integratio... | {"pr_number": 8768, "pr_title": "feat(connector): [cybersource] add changes for field CybersourceConsumerAuthInformation", "merged_at": "2025-07-31T09:51:22Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"domain": ["crates/hyperswi... |
<!-- Describe your changes in detail -->
This PR introduces the capability to send the Merchant Order Reference ID to the Unified Connector Service (UCS) as part of gRPC request headers. This enhancement allows the UCS to be aware of the merchant's original identifier for a transaction, which can be crucial for trac... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/payments.rs`
- `crates/hyperswitch_domain_models/src/router_request_types.rs`
**2. Core Business Logic**
- `crates/router/src/cor... | {"pr_number": 9352, "pr_title": "feat(ucs): transmit merchant order reference id to unified connector service", "merged_at": "2025-09-18T08:51:58Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_... |
<!-- Describe your changes in detail -->
The length of receipt for Trustpay order request should not exceed 35 characters. So added generate_connector_request_reference_id specific to trustpay which generates less than 35 charcters. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/trustpay.rs`
**Code Patterns Applied:**
- Implement new functions (1 changes)
- Extend existing types with new fields (2 changes) | {"pr_number": 8925, "pr_title": "fix(trustpay): add connector request reference ID generation for v2", "merged_at": "2025-09-10T08:51:15Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/s... |
<!-- Describe your changes in detail -->
Paystack EFT flow (Payments, PSync, Refunds, RSync, Webhooks). | 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": 7286, "pr_title": "feat(connector): [PAYSTACK] EFT Payment Flows", "merged_at": "2025-03-03T14:28:32Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/connector_configs/toml/development.toml", "cra... |
<!-- Describe your changes in detail -->
Added trustpay in authentication providers config | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `config/deployments/integration_test.toml`
**2. Configuration Files**
- `config/deployments/production.toml`
- `config/deployments/sandbox.toml`
- `config/development.toml`
- ... and 1 more fi... | {"pr_number": 8622, "pr_title": "fix(connector): Add Trustpay in Authentication Providers Config", "merged_at": "2025-07-22T12:49:13Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user", "session", "card"]}, "hierarchy": {"tests": ["config/deployments/integration_test.toml"], "con... |
<!-- Describe your changes in detail -->
This PR adds support for API Event Metric logging, the events will be logged to clickhouse when a request/response is triggered.
In refunds v2, it will be for requests and responses for 4 apis
1. Refunds Create
2. Refunds Metadata Update
3. Refunds Retrieve
4. Refunds Li... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/events/refund.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/refund.rs`
**3. Core Business Logic**
- `crates/router/src/core/r... | {"pr_number": 8041, "pr_title": "Refactor(refunds_v2): Refactor api event metric for refunds v2 apis", "merged_at": "2025-05-27T07:22:39Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["refund"]}, "hierarchy": {"api_models": ["crates/api_models/src/events/refund.rs"], "database": ["... |
Revert [7610](https://github.com/juspay/hyperswitch/pull/7610) | 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": 7864, "pr_title": "fix(connector): revert noon-paypal", "merged_at": "2025-04-22T11:39:01Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/connector_configs/toml/production.toml", "crates/hyperswi... |
<!-- Describe your changes in detail -->
Instead of using a forked repo to support empty payloads in josekit's JWT implementation, switch to using the josekit JWS directly, which supports empty payloads. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/Cargo.toml`
- `crates/hyperswitch_connectors/src/connectors/nomupay.rs`
**2. Other**
- `Cargo.lock` | {"pr_number": 8183, "pr_title": "fix(connector): removed forked josekit dependency from payout connector Nomupay", "merged_at": "2025-06-10T07:09:21Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "merchant", "user"]}, "hierarchy": {"connectors": ["crates/hyperswitch_con... |
Fix save card flow for braintree , earlier we were passing on_session for off_session flow | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `cypress-tests/cypress/e2e/configs/Payment/Braintree.js`
**Code Patterns Applied:**
- Extend existing types with new fields (11 changes) | {"pr_number": 9435, "pr_title": "ci(cypress): fix braintree connector", "merged_at": "2025-09-18T11:59:06Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user", "session", "card"]}, "hierarchy": {"tests": ["cypress-tests/cypress/e2e/configs/Payment/Braintree.js"]}, "change_types": ... |
adding `stripe` in connector list for network transaction id. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Configuration Files**
- `config/deployments/production.toml` | {"pr_number": 7096, "pr_title": "chore: add stripe to network transaction id support", "merged_at": "2025-01-28T20:16:00Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["connector", "transaction"]}, "hierarchy": {"config": ["config/deployments/production.toml"]}, "change_types": {},... |
<!-- Describe your changes in detail -->
This PR addresses the clippy lints occurring due to new rust version 1.87.0
https://rust-lang.github.io/rust-clippy/master/index.html | To implement this **connector_integration** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payments/helpers.rs`
**2. Utils**
- `crates/kgraph_utils/src/error.rs`
- `crates/kgraph_utils/src/transformers.rs`
**3. Other**
- `crates/external_s... | {"pr_number": 8130, "pr_title": "chore: address Rust 1.87.0 clippy lints", "merged_at": "2025-05-27T10:37:27Z", "intent": {"feature_type": "connector_integration", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"core_business": ["crates/router/src/core/payments/helpers.rs"], "utils": ["crates/kgraph_util... |
<!-- Describe your changes in detail -->
Updated the outdated/incorrect base urls for some connectors with the new ones. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/chargebee.rs`
**2. Configuration Files**
- `config/deployments/production.toml` | {"pr_number": 7582, "pr_title": "refactor(configs): prod base url updated for connectors", "merged_at": "2025-04-30T10:46:14Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "connector"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connecto... |
<!-- Describe your changes in detail -->
add template code for katapult | 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": 8783, "pr_title": "feat(connector): [katapult]add template code for katapult", "merged_at": "2025-07-31T11:50:55Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/connector_endpoints.rs"], "connectors": [... |
<!-- Describe your changes in detail --> | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/admin.rs`
**2. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/merchant_account.rs`
- `crates/hyperswitch_domain_models/sr... | {"pr_number": 8992, "pr_title": "feat(core): Add Merchant Tax ID in Merchant Profile ", "merged_at": "2025-09-01T11:02:55Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"api_models": ["crates/api_models/src/admin.rs"], "domain": ["crat... |
<!-- Describe your changes in detail -->
Worldpayvantiv supports non 3ds payments. Recurring payments are not supported.
Mandate using PMID failing because of the missing connector id - which is expected. But throws an unexpected error
<img width="416" alt="Screenshot 2025-06-04 at 11 31 41 AM" src="https://github.c... | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. Tests**
- `cypress-tests/cypress/e2e/configs/Payment/Utils.js`
- `cypress-tests/cypress/e2e/configs/Payment/Worldpayvantiv.js`
**Code Patterns Applied:**
- Extend existing types with new fields (367 changes) | {"pr_number": 8234, "pr_title": "feat(cypress): [worldpayvantiv] add cypress test", "merged_at": "2025-07-07T12:53:33Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["payment", "user", "connector"]}, "hierarchy": {"tests": ["cypress-tests/cypress/e2e/configs/Payment/Utils.js", "cypress-te... |
<!-- Describe your changes in detail -->
Add cardbrand union fetch logic for click to pay session response
Previously for click to pay card brands was needed to be configured via dashboard in click to pay connector create tab, with this change we will provide card brands as a union of all card networks under active... | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/payments.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/query/merchant_connector_account.rs`
**3. Core Business Logic**
- `crates/ro... | {"pr_number": 7858, "pr_title": "feat(core): Add cardbrand union fetch logic for click to pay session response", "merged_at": "2025-04-28T12:21:01Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"api_models": ["crates/api_models/src/payments.... |
<!-- Describe your changes in detail -->
Generally in case of external payments we don't get the network error code and error messages from the billing connector. Since this data is important we need to fetch them using Psync call for the Payment connectors and update our payment attempts. In this PR we have added sup... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/payments.rs`
**2. Core Business Logic**
- `crates/router/src/core/payments.rs`
- `crates/router/src/core/payments/operations/paym... | {"pr_number": 7855, "pr_title": "feat(core): add psync support for recovery external payments", "merged_at": "2025-05-12T14:30:04Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/payme... |
Fetch email from customer email whenever billing email is not present for payment request | 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`
**Code Patterns Applied:**
- Implement new functions (1 changes)
- Extend existing types with new fields (2 changes) | {"pr_number": 6676, "pr_title": "feat(connector): [Adyen] Fetch email from customer email for payment request", "merged_at": "2024-11-29T10:28:36Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment"]}, "hierarchy": {"connectors": ["crates/router/src/connector/adyen/... |
- Accept merchant_connector_credentials in the Request Body of payments and psync
- Add a new POST endpoint `payments_status_with_gateway_creds`
- Add merchant_reference_id in payments 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. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/customer.rs`
- `crates/hyperswitch_domain_models/src/mer... | {"pr_number": 8199, "pr_title": "feat(core): accept merchant_connector_details in Payments and Psync flow", "merged_at": "2025-06-17T15:54:49Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/paym... |
<!-- Describe your changes in detail -->
klarna in router crate uses to_state_code in branch hotfix-2025.02.05, thus, to_state_code implementation needs to be present in router as well | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/router/src/connector/utils.rs`
**Code Patterns Applied:**
- Implement new functions (4 changes)
- Add conditional logic for feature flags or filtering (1 changes) | {"pr_number": 7293, "pr_title": "fix(utils): add to_state_code to router crate", "merged_at": "2025-02-17T18:21:13Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"connectors": ["crates/router/src/connector/utils.rs"]}, "change_types": {"functions_added": 4, "condi... |
If there's no connector customer present corresponding to the customer_id of hyperswitch, then it throws a missing required field error. This shouldn't happen. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/stripe/transformers.rs`
**2. Other**
- `api-reference-v2/openapi_spec.json`
**Code Patterns Applied:**
- Extend existing types wi... | {"pr_number": 8309, "pr_title": "fix(connector): [STRIPE] Throwing Missing Required Field Error if connector_customer is not present", "merged_at": "2025-06-10T15:09:01Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": [... |
<!-- Describe your changes in detail -->
- Consistently use kebab case in endpoint URLs
- Use plural form of resources in URLs, i.e. instead of `/v2/organization`, use `/v2/organizations`
Renamed (current version removed) endpoints:
`/v2/organization` -> `/v2/organizations`
`/v2/routing-algorithm` -> `/v2/routin... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/hyperswitch_vault.rs`
**2. Tests**
- `cypress-tests-v2/cypress/support/commands.js`
**3. Other**
- `api-reference/v2/openapi_s... | {"pr_number": 8630, "pr_title": "fix(router): Make v2 endpoints follow standard naming conventions", "merged_at": "2025-07-21T15:41:20Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src... |
<!-- Describe your changes in detail -->
Fix required fileds for wallet mandate payments for cybersource and bank of america. | 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": 6911, "pr_title": "fix(connector): [Cybersource] fix the required fields for wallet mandate payments", "merged_at": "2024-12-23T09:38:59Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/router/src... |
<!-- Describe your changes in detail -->
Add tenant id in dummy connector requests
## Motivation and Context
<!--
Why is this change required? What problem does it solve?
If it fixes an open issue, please link to the issue here.
If you don't have an issue, we'd recommend starting with one first so the PR
can... | 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_data.rs`
- `crates/hyperswitch_domain_models/src/router_data_v2.rs`
**2. Core Business Logic**
- `crates/router/src/core/authent... | {"pr_number": 7008, "pr_title": "fix(dummyconnector): add tenant id in dummyconnector requests", "merged_at": "2025-01-09T09:39:26Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/router_dat... |
HOTFIX PR
<!-- Describe your changes in detail -->
Update metadata gives `500` error for other connectors than stripe
Change this to `400`
- Base pr : https://github.com/juspay/hyperswitch/pull/7984 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payments/flows/update_metadata_flow.rs`
- `crates/router/src/core/payments/transformers.rs`
**Code Patterns Applied:**
- Implement new functions (1 changes)
- Exte... | {"pr_number": 7986, "pr_title": "fix(update_metadata): Update Metadata for any connectors other than stripe gives 500 error", "merged_at": "2025-05-08T11:04:03Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "order", "connector"]}, "hierarchy": {"core_business": ["crates/... |
This PR enables country Malaysia for processing APay and GPay transactions via Fiuu | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `config/deployments/integration_test.toml`
**2. Configuration Files**
- `config/deployments/production.toml`
- `config/deployments/sandbox.toml`
- `config/development.toml` | {"pr_number": 7182, "pr_title": "chore(connectors): [fiuu] update pm_filters for apple pay and google pay", "merged_at": "2025-02-06T15:20:10Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user", "transaction"]}, "hierarchy": {"tests": ["config/deployments/integration_test.toml"],... |
<!-- Describe your changes in detail -->
This PR introduces an API to list all payment attempts associated with a given intent_id. | 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/payments.rs`... | {"pr_number": 8368, "pr_title": "feat(router): Add v2 endpoint to list payment attempts by intent_id", "merged_at": "2025-06-20T06:58:02Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "order"]}, "hierarchy": {"api_models": ["crates/api_models/src/events/payme... |
<!-- Describe your changes in detail -->
Updated the readme and local setup guide to add the new script | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Other**
- `README.md`
- `docs/try_local_system.md` | {"pr_number": 7839, "pr_title": "docs: update the setup docs", "merged_at": "2025-04-24T07:56:02Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"other": ["README.md", "docs/try_local_system.md"]}, "change_types": {}, "has_identifier_data": false, "commits_matched"... |
<!-- Describe your changes in detail -->
There was a trailing whitespace in `postman/collection-dir/archipel/Flow Testcases/Happy Cases/Scenario10-Create 3DS payment without external 3ds authentication `. Because of which there was an error when attempting to clone the repo in other systems like Windows etc. Removed t... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `postman/collection-dir/archipel/Flow Testcases/Happy Cases/Scenario10-Create 3DS payment without external 3ds authentication /Payments - Confirm/event.test.js`
- `postman/collection-dir/archipel/Flow T... | {"pr_number": 9578, "pr_title": "fix(postman): [ARCHIPEL] Remove Trailing Whitespace", "merged_at": "2025-10-07T17:32:55Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user"]}, "hierarchy": {"tests": ["postman/collection-dir/archipel/Flow Testcases/Happy Cases/Scenario1... |
<!-- Describe your changes in detail -->
The merchant domain url is only required in case of samsung pay payments on web. While processing payments on app the merchant domain is not required. Hence mandate the merchant domain only if the `x-client-platform` is `web` | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/payments.rs`
**2. Core Business Logic**
- `crates/router/src/core/payments/flows/session_flow.rs`
**3. Other**
- `api-reference-v2/openapi_spec.json`
... | {"pr_number": 6362, "pr_title": "fix(router): make `x_merchant_domain` as required value only for session call done on web", "merged_at": "2024-10-19T14:22:39Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/ap... |
<!-- Describe your changes in detail -->
This PR introduces improvements to the **Customer page API**:
Added **search bar functionality** to filter customers by `customer_id`.
These changes enhance API usability and improve performance when handling large customer datasets. | 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`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/query/customers.rs`
**3. Domain Models (Business Logic Types)**
- `cr... | {"pr_number": 9619, "pr_title": "Feat(Customer): Added search Feature to the Customer Page", "merged_at": "2025-10-03T10:06:30Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "user"]}, "hierarchy": {"api_models": ["crates/api_models/src/customers.rs"], "databa... |
#### **POST** `/user/role/v2`
- Creates a role using `parent_groups` (with `name` + `scopes`) instead of granular `groups`.
- Internally maps `parent_groups` + `scopes` to existing granular permissions for DB storage. | 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_role.rs`
- `crates/api_models/src/user_role/role.rs`
**2. Core Business Logic**
- `crates/router/src/core/user_role.rs`
- `crates/router/s... | {"pr_number": 8896, "pr_title": "refactor(user_roles): implement parent group info based role APIs", "merged_at": "2025-08-22T14:03:34Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/events/user... |
ORIGINAL PR:https://github.com/juspay/hyperswitch/pull/9253 | To implement this **unknown** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/authorizedotnet/transformers.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (12 changes)
**Detailed Identifier Cha... | {"pr_number": 9276, "pr_title": "fix(connector): Revert [AUTHORIZEDOTNET] customer id population fixed in authorize flow", "merged_at": "2025-09-04T11:07:11Z", "intent": {"feature_type": "unknown", "action": "unknown", "entities": []}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors/authorize... |
bumping tonic version from 0.12 to 0.13 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Configuration Files**
- `crates/external_services/Cargo.toml`
**2. Other**
- `Cargo.lock`
- `crates/external_services/build.rs`
- `crates/external_services/src/grpc_client.rs`
**Code Patterns Applied:**
... | {"pr_number": 8461, "pr_title": "build(deps): bump tonic version from 0.12 to 0.13", "merged_at": "2025-06-26T06:26:30Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"config": ["crates/external_services/Cargo.toml"], "other": ["Cargo.lock", "crates/external_... |
<!-- Describe your changes in detail -->
Implement payments sync for v2. Using this endpoint the status of the payment can be retrieved and also synced with the connector.
## Motivation and Context
<!--
Why is this change required? What problem does it solve?
If it fixes an open issue, please link to the is... | To implement this **payment** 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/kv.rs`
- `crates/diesel_models... | {"pr_number": 6464, "pr_title": "feat(payment_v2): implement payments sync ", "merged_at": "2024-11-11T14:06:06Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/events/payment.rs", "crates/api_models/s... |
<!-- Describe your changes in detail -->
This PR contains support for db calls that are used in refunds v2 core flows for non kv config.
There are 2 ways that HS use to interact with DB, using KV and without KV.
In code we represent it by `kv_store` feature flag. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Other**
- `crates/router/src/db/refund.rs`
**Code Patterns Applied:**
- Implement new functions (4 changes)
- Extend existing types with new fields (13 changes)
**Detailed Identifier Changes:**
Commit e6482fbe:
... | {"pr_number": 7987, "pr_title": "refactor(refunds_v2): Add feature flags and db methods to non kv config", "merged_at": "2025-06-03T08:51:28Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"other": ["crates/router/src/db/refund.rs"]}, "... |
<!-- Describe your changes in detail -->
Fixed customer ID population in the Authorize flow.
- Previously, when passing customer details for normal payments, the createConnectorCustomer flow correctly created the customer.
- However, in the `Authorize` flow, we were passing the payment_id as the customer_id. If ... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/authorizedotnet/transformers.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (12 changes)
- Add conditional lo... | {"pr_number": 9079, "pr_title": "fix(connector): [AUTHORIZEDOTNET] customer id population fixed in authorize flow", "merged_at": "2025-08-29T10:41:40Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch... |
<!-- Describe your changes in detail -->
Updated the create_platform endpoint in api-reference docs
Previously the endpoint was:
```bash
/create_platform
```
Updated the endpoint now to:
```bash
/user/create_platform
``` | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Other**
- `api-reference/v1/openapi_spec_v1.json`
- `api-reference/v1/platform/platform--create.mdx`
- `crates/openapi/src/routes/platform.rs` | {"pr_number": 8782, "pr_title": "fix(openapi): update create_platform endpoint in api-reference docs", "merged_at": "2025-07-30T06:57:15Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"other": ["api-reference/v1/openapi_spec_v1.json", "api-reference/v1/platf... |
<!-- Describe your changes in detail -->
This PR implements **V2 UCS (Unified Connector Service) Integration** for authorization and synchronization flows, building upon the existing V1 UCS integration (PR#[8280](https://github.com/juspay/hyperswitch/pull/8280)), with enhanced
V2 schema support according to upd... | 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/merchant_connector_account.rs`
**2. Core Business Logic**
- `crates/router/src/core/payments.rs`
- `crates/router/src/core/paymen... | {"pr_number": 8439, "pr_title": "feat(core): Hyperswitch <|> UCS integration v2", "merged_at": "2025-07-11T14:44:46Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/merchant_connector_... |
<!-- Describe your changes in detail -->
Changed the Unified Connector Service gRPC Client config to accept the entire base url instead of host and port.
## What is Unified Connector Service?
The Unified Connector Service is a __gRPC-based microservice__ that acts as an intermediary layer between Hyperswitch ... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/external_services/src/grpc_client/unified_connector_service.rs`
**2. Configuration Files**
- `config/config.example.toml`
- `config/deployments/env_specific.toml`
... | {"pr_number": 8587, "pr_title": "feat(external_services): Fixed Url for Unified Connector Service gRPC Client", "merged_at": "2025-08-05T08:54:50Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/external_servic... |
<!-- Describe your changes in detail -->
This PR integrates the decision engine config APIs
The integration sits in the dynamic routing config flows. Based on ENV, if decision engine is enabled, we would call DE instead of Dynamo. | 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/admin.rs`
- `crates/router/src/core/payments... | {"pr_number": 8044, "pr_title": "feat(dynamic_routing): Decision engine config API integration ", "merged_at": "2025-05-22T18:43:29Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/open_router.rs... |
<!-- Describe your changes in detail -->
Previously we were pushing the Dynamic routing metrics to Prometheus, but due to high cardinality of some values(payment_id) we were not able to add that in our attributes, hence we are pushing this after creating a new table in our Database (dynamic_routing_stats).
The furt... | 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/dynamic_routing_stats.rs`
- `crates/diesel_models/src/enums.rs`
- `cr... | {"pr_number": 6723, "pr_title": "feat(dynamic_routing): analytics improvement using separate postgres table", "merged_at": "2024-12-07T09:31:44Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"api_models": ["crates/api_models/src/routin... |
<!-- Describe your changes in detail -->
Enable L2l3 config for integ
NO test needed. Just enabling config | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `config/deployments/integration_test.toml` | {"pr_number": 9538, "pr_title": "fix(l2l3): enable l2l3 for integ", "merged_at": "2025-09-25T17:55:49Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"tests": ["config/deployments/integration_test.toml"]}, "change_types": {}, "has_identifier_data": false, "commits_... |
<!-- Describe your changes in detail -->
Added Getnet, Hipay, Klarna, Moneris, Opennode in feature matrix API | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/getnet.rs`
- `crates/hyperswitch_connectors/src/connectors/hipay.rs`
- `crates/hyperswitch_connectors/src/connectors/klarna.rs`
... | {"pr_number": 7873, "pr_title": "feat(connector): [GETNET,HIPAY,KLARNA,MONERIS,OPENNODE] add in feature matrix api", "merged_at": "2025-04-25T09:54:28Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "refund"]}, "hierarchy": {"connectors": ["crates/hyperswitch_... |
<!-- Describe your changes in detail -->
Removed all the openapi references to `RefundAggregateResponse`.
1. Removed `ToSchema` trait for `RefundAggregateResponse`.
2. Removed references from `openapi` and `openapi_v2` to `RefundAggregateResponse`.
3. Generated new `openapi_spec` file based on the above changes. | 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. Other**
- `api-reference-v2/openapi_spec.json`
- `api-reference/openapi_spec.json`
- `crates/openapi/src/openapi.rs`
- ... and 1 m... | {"pr_number": 6405, "pr_title": "fix(refunds): remove to schema from refund aggregate response and exclude it from open api documentation", "merged_at": "2024-11-05T09:26:13Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user", "refund"]}, "hierarchy": {"api_models": ["crates/api_... |
Populate `shipping_cost` in payment 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. Core Business Logic**
- `crates/router/src/core/payments/transformers.rs`
**3. Tests**
- `crates/router/tests/payments.rs`
- `crate... | {"pr_number": 6351, "pr_title": "refactor(core): populate shipping_cost in payment response", "merged_at": "2024-10-18T13:44:03Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/payments.rs"], "co... |
<!-- Describe your changes in detail -->
Add configs for calculate job | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/revenue_recovery.rs`
- `crates/router/src/core/revenue_recovery/types.rs`
**2. Type Definitions**
- `crates/router/src/types/storage/revenue_recovery.rs`
**3. ... | {"pr_number": 9106, "pr_title": "refactor(revenue_recovery): Add configs for calculate job", "merged_at": "2025-08-29T15:31:36Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"core_business": ["crates/router/src/core/revenue_recovery.rs", "crates/router/src/core/re... |
<!-- Describe your changes in detail -->
This pull request refactors the `DebitRoutingOutput` structure to introduce a new `CoBadgedCardNetworksInfo` type, enhancing the representation of co-badged card networks by including additional metadata such as saving percentages. It also updates related methods and structures... | 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`
**2. Core Business Logic**
- `crates/router/src/core/debit_routing.rs`
**Code Patterns Applied:**
- Define new data structures (1 changes)
... | {"pr_number": 8388, "pr_title": "refactor(routing): add support to accept the `saving_percentage` in decision engine response", "merged_at": "2025-06-20T13:28:33Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates... |
`payment_link` currently comes as null in psync response, even if payment link exists for the particular payment id
<img width="1284" alt="Screenshot 2025-01-29 at 15 50 02" src="https://github.com/user-attachments/assets/9c4d3fad-9b02-43d8-91f8-8ef946c6dc62" /> | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payments.rs`
- `crates/router/src/core/payments/operations/payment_status.rs`
**Code Patterns Applied:**
- Implement new functions (1 changes)
- Extend existing ty... | {"pr_number": 7137, "pr_title": "fix(core): Add payment_link_data in PaymentData for Psync", "merged_at": "2025-02-05T15:08:58Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user", "connector"]}, "hierarchy": {"core_business": ["crates/router/src/core/payments.rs", "cra... |
The current description for refund - list is incorrect. Newer one looks more apt. | 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/refunds.rs` | {"pr_number": 6443, "pr_title": "fix(docs): incorrect description for refund api", "merged_at": "2024-12-10T11:02:10Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["refund"]}, "hierarchy": {"other": ["api-reference/openapi_spec.json", "crates/openapi/src/routes/refunds.rs"]}, "chan... |
<!-- Describe your changes in detail -->
For one connector alone to hard code success with a particular failure card | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/router/src/routes/dummy_connector/utils.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (2 changes)
- Add conditional logic for feature flags or fil... | {"pr_number": 8469, "pr_title": "feat(dummy_connector): allow a dummy connector to succeed a failed card", "merged_at": "2025-07-01T12:31:18Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/router/src/routes/du... |
<!-- Describe your changes in detail -->
Added Google Pay Payment Method | 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 3 more files
*... | {"pr_number": 8786, "pr_title": "feat(connector): [Barclaycard] Add Google Pay Payment Method", "merged_at": "2025-08-06T07:35:30Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/connector_configs/toml/developm... |
<!-- Describe your changes in detail -->
Fix Nuvei payments and chargeback webhooks
## 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)?
-->
Tested it by configuring payments, refunds and cha... | 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`
**Code Patterns Applied:**
- Define new data stru... | {"pr_number": 9378, "pr_title": "fix(connectors): [Nuvei] payments, refunds and chargeback webhooks", "merged_at": "2025-09-19T12:17:17Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/sr... |
Currently the API Call to the /user/auth endpoint displays only a 200::OK response code without providing a proper response body containing the authentication details for proper debugging.This PR Introduces a Response body of type CreateUserAuthenticationMethodReponse which contains members to be displayed in response ... | 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. Core Business Logic**
- `crates/router/src/core/user.rs`
**Code Patterns Applied:**
- Define new ... | {"pr_number": 9653, "pr_title": "feat: include response body for create_user_authentication_method", "merged_at": "2025-10-15T16:19:48Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"api_models": ["crates/api_models/src/events/user.rs", "crates/api_models/sr... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.