prompt stringlengths 6 90.9k | response stringlengths 121 18.6k | metadata stringlengths 314 42.3k |
|---|---|---|
<!-- Describe your changes in detail -->
This pull request introduces a new authentication mechanism for internal service communication using a shared API key, merchant ID, and profile ID. The changes add configuration options for this authentication method across all environment config files, update the core settings... | 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/config.example.toml`
- `config/deployments/env_specific.toml`
- `config/dep... | {"pr_number": 9547, "pr_title": "feat(auth): add new authentication to communicate between microservices", "merged_at": "2025-09-29T18:26:45Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"tests": ["config/deployments/integration_t... |
<!-- Describe your changes in detail -->
Changed the attempt status mapping of `CapturedPendingSettlement` given by AuthorizeDotNet from `ChargeInitiated` to `Charged` | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/authorizedotnet/transformers.rs` | {"pr_number": 7523, "pr_title": "fix(connector): fix incorrect mapping of attempt status in AuthorizeDotNet connector", "merged_at": "2025-03-17T14:53:38Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["connector", "transaction"]}, "hierarchy": {"connectors": ["crates/hyperswitch_co... |
This PR updates the behavior of final redirection to use top redirection when payment link's status page is present in the flow as well.
Explained in https://github.com/juspay/hyperswitch/issues/8639 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payment_link/payment_link_status/status.js` | {"pr_number": 8641, "pr_title": "refactor(payment-links): use top redirection in status page", "merged_at": "2025-07-16T10:19:33Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core/payment_link/... |
<!-- Describe your changes in detail -->
Adding support for Worldpay's XML payment processor
## 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)?
-->
```
just clippy
cargo +nightly fmt --all
... | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/configs.rs`
**2. Core Business Logic**
- `crates/router/src/core/admin.rs`
**3. External Connector Integration**
- `crates/common_enum... | {"pr_number": 7968, "pr_title": "feat(connector): Introduce connector template code for WorldpayXML ", "merged_at": "2025-05-12T14:33:38Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["payment"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/configs.rs"], "core_business... |
<!-- Describe your changes in detail -->
Template code added for blackhawknetwork. | 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": 8632, "pr_title": "feat(connector): [BLACKHAWKNETWORK] Add Template Code ", "merged_at": "2025-07-21T11:06:59Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/connector_endpoints.rs"], "connectors": ["cr... |
<!-- Describe your changes in detail -->
added **FloatMajorUnit** for amount conversion for **Fiserv**
added **FloatMajorUnit** for amount conversion for **Helcim** | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/fiserv.rs`
- `crates/hyperswitch_connectors/src/connectors/fiserv/transformers.rs`
- `crates/hyperswitch_connectors/src/connecto... | {"pr_number": 7336, "pr_title": "refactor(connector): [FISERV, HELCIM] Add amount conversion framework to Fiserv, Helcim", "merged_at": "2025-03-12T07:58:54Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hype... |
<!-- Describe your changes in detail -->
- add `vault_session_details` field to session's response for vault sdk initiation
- This is added for VGS as well as Hyperswitch Vault
- add connector customer create call for session call, this is done inside sdk session call of payment to call the payment method service's ... | 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/enums.rs`
- `crates/api_models/src/payments.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/sr... | {"pr_number": 8003, "pr_title": "feat(payment_methods): add `external_vault_details` for payments v2 sdk session call", "merged_at": "2025-06-06T12:34:21Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_mod... |
<!-- Describe your changes in detail -->
Added supported countries and currencies for Cashtocode. | 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": 8060, "pr_title": "fix(connector): [CASHTOCODE] Added supported countries and currencies", "merged_at": "2025-05-19T12:06:18Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"tests": ["config/deployments/integration_test.toml"], "config": ["config/depl... |
The PR does the following actions
- Adds endpoints to talk to ai services, particularly to n8n flow and embedded flow
- Introduces a feature flag to manage chat features across different envs | 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.rs`
- `crates/api_models/src/events/chat.rs`
- ... and 1 more files
**2. Domain Models (Business Logic Types)... | {"pr_number": 8585, "pr_title": "feat(ai): add endpoints to chat with ai service", "merged_at": "2025-07-16T20:33:11Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user"]}, "hierarchy": {"api_models": ["crates/api_models/src/chat.rs", "crates/api_models/src/events.rs", ... |
<!-- Describe your changes in detail -->
This PR implements refund flow for JPMorgan connector. Connector returns `Authorized` state (`Pending`). Post RSync call, the status gets updated to `Success`. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/jpmorgan.rs`
- `crates/hyperswitch_connectors/src/connectors/jpmorgan/transformers.rs`
**2. Tests**
- `cypress-tests/cypress/e2... | {"pr_number": 8436, "pr_title": "feat(connector): [jpmorgan] implement refund flow", "merged_at": "2025-06-25T07:01:17Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user", "refund", "connector"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors/jpmorgan... |
Described in #57 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Other**
- `.gitignore`
- `docs/try_local_system.md`
- `flake.lock`
- ... and 1 more files | {"pr_number": 6377, "pr_title": "feat(nix): add support for running external services through services-flake", "merged_at": "2024-11-05T14:07:43Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"other": [".gitignore", "docs/try_local_system.md", "flake.lock", "flake... |
<!-- Describe your changes in detail --> | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/authentication.rs`
- `crates/api_models/src/payments.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/authentication.rs`
- `crates/d... | {"pr_number": 8431, "pr_title": "feat(authentication): Added eligibility flow for modular authentication", "merged_at": "2025-07-21T13:38:52Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"api_models": ["crates/api_models/src/authentication.... |
<!-- Describe your changes in detail -->
This PR updates the usages of the `once_cell` crate and its types with their standard library equivalents. This PR replaces:
- [`once_cell::sync::OnceCell`](https://docs.rs/once_cell/latest/once_cell/sync/struct.OnceCell.html) with [`std::sync::OnceLock`](https://doc.rust-... | To implement this **connector_integration** feature, you'll need to modify these architectural layers:
**1. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/lib.rs`
**2. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/consts.rs`
- `crates/hyperswitch_domain_mode... | {"pr_number": 8030, "pr_title": "build(deps): migrate usages of `once_cell` crate to standard library equivalents", "merged_at": "2025-05-19T11:07:05Z", "intent": {"feature_type": "connector_integration", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"database": ["crates/diesel_models/src/lib.rs"], "dom... |
Fix consumer authenttication information fields
1. Renamed _consumer_authentication_information.pares_status_reason_ field to _consumer_authentication_information.signed_pares_status_reason_
2. Moved _cavv_algorithm_ from _processing_information_ to _consumer_authentication_information_
Verified with cybersouce ... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/cybersource/transformers.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (13 changes) | {"pr_number": 8927, "pr_title": "fix(connector): [CYBERSOURCE] fix incorrect consumer authentication information fields", "merged_at": "2025-08-13T12:20:13Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connector... |
<!-- Describe your changes in detail -->
- This PR will introduce theme context in user APIs and email related APIs.
- The User APIs which are affected are
1. User Info
2. Invite
3. Resend Invite
4. Reset Password
5. Connect Account
6. Signup with merchant id
- Non User flows
1... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/user.rs`
- `crates/api_models/src/user/theme.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/query/user/theme.rs`
- `crates/d... | {"pr_number": 6772, "pr_title": "feat(users): Incorporate themes in user APIs", "merged_at": "2024-12-16T09:20:21Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["merchant", "user", "token"]}, "hierarchy": {"api_models": ["crates/api_models/src/user.rs", "crates/api_models/src/user/... |
<!-- Describe your changes in detail -->
This PR adds `error_category` column to gsm table which is an enum in application. These could be used to take multiple decisions in future but currently these are required for elimination routing in which these categories will serve as bucket name.
Additionally the pr fixes t... | 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": 6648, "pr_title": "refactor(gsm): add `error_category` column to gsm table", "merged_at": "2024-12-04T11:00:45Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "connector"]}, "hierarchy": {"api_models": ["crates/api_models/src/gsm.rs"], "database": ["crates/d... |
<!-- Describe your changes in detail -->
Other changes:
1. Introduced product type column in merchant_account
2. restructure payment_methods related v2 DB queries
3. drop auto increment `id` column from all possible v1 tables.
4. introduce varchar `id` column in merchant_account in v1.
5. justfile changes to run ... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Database Layer (Queries & Schema)**
- `crates/diesel_models/drop_id.patch`
- `crates/diesel_models/src/schema.rs`
- `crates/diesel_models/remove_id.patch`
- ... and 13 more files
**2. Domain Models (Busine... | {"pr_number": 7244, "pr_title": "refactor(v1v2): refactor database queries for v1 and v2", "merged_at": "2025-02-27T07:41:43Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"database": ["crates/diesel_models/drop_id.patch", "crates/dies... |
<!-- Describe your changes in detail -->
Hotfix PR
Original PR: [https://github.com/juspay/hyperswitch/pull/7451](https://github.com/juspay/hyperswitch/pull/7451) | 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": 7453, "pr_title": "feat(analytics): add new filters, dimensions and metrics for authentication analytics", "merged_at": "2025-03-06T17:17:23Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"api_models": ["crates/api_models/src/analytics.rs", "crates/a... |
<!-- Describe your changes in detail -->
Added feature api details for Rapyd, Bamboraapac, Gocardless and Powertranz | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/bamboraapac.rs`
- `crates/hyperswitch_connectors/src/connectors/gocardless.rs`
- `crates/hyperswitch_connectors/src/connectors/p... | {"pr_number": 7136, "pr_title": "Feat(connector): Rapyd, Bamboraapac, Gocardless, Powertranz, Shift4 and Worldline added in feature matrix", "merged_at": "2025-03-11T11:46:47Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connecto... |
<!-- Describe your changes in detail -->
This PR changes the way we raise error if something goes wrong with generic filter. Currently we throw not found error which is wrong.
This feature is hard to test on hosted environments, as this requires to make some db changes so that we can get error in generic filter. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/query/generics.rs` | {"pr_number": 7935, "pr_title": "fix(diesel_models): Fix error message while using generic filter", "merged_at": "2025-05-02T12:44:50Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user", "refund"]}, "hierarchy": {"database": ["crates/diesel_models/src/query/generics.rs"]}, "chang... |
<!-- Describe your changes in detail -->
When surcharge rules where updated or deleted, the in memory cache was being invalidated using the wrong key. Fixed that issue in this PR. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/surcharge_decision_config.rs` | {"pr_number": 6907, "pr_title": "fix: invalidate surcharge cache during update", "merged_at": "2025-02-04T01:18:46Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core/surcharge_decision_config.r... |
<!-- Describe your changes in detail -->
Add support for split payments via xendit platform
Payment: Request for split
```
"split_payments": {
"xendit_split_payment": {
"multiple_splits" : {
"name": "20210908 Test",
"for_user_id":"***************", //Include in case... | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/payments.rs`
- `crates/hyperswitch_domain_models/src/payments/payment_intent.rs`
- `crates/hyperswitch_domain_models/src/router_request_... | {"pr_number": 7143, "pr_title": "feat(router): [Xendit] add support for split payments", "merged_at": "2025-02-20T15:30:54Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/payments.rs", "cra... |
<!-- Describe your changes in detail -->
For Razorpay (RZP) integration, the `connector_request_reference_id` will now be set as follows:
- If `merchant_reference_id` is available, use it directly.
- If not available, generate a UUID instead.
This ensures compliance with Razorpay’s constraint that the reference... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/razorpay.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (1 changes) | {"pr_number": 9404, "pr_title": "refactor(connector): [RAZORPAY] update generate_connector_request_reference_id to consume merchant_reference_id", "merged_at": "2025-09-18T07:18:58Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"connec... |
<!-- Describe your changes in detail -->
add authentication api for modular authentication
## Authentication Authenticate API - `POST /authentication/{authentication_id}/authenticate`
This PR adds the authenticate endpoint which is the final step in the 3DS authentication flow. | To implement this **search_filter** 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_mo... | {"pr_number": 8459, "pr_title": "feat(authentication): add authentication api for modular authentication", "merged_at": "2025-07-25T09:47:50Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"api_models": ["crates/api_models/src/authentic... |
<!-- Describe your changes in detail -->
Add a validation to check if payment method data passed in the request, if not passed decryption flow will be skipped
main branch pr: https://github.com/juspay/hyperswitch/pull/9521 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payments.rs` | {"pr_number": 9522, "pr_title": "fix(router): check payment_method_data before the decryption flow", "merged_at": "2025-09-24T08:06:03Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core/payment... |
<!-- Describe your changes in detail -->
Hotfix PR
Original PR: [https://github.com/juspay/hyperswitch/pull/7638](https://github.com/juspay/hyperswitch/pull/7638) | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/user/dashboard_metadata.rs`
**2. Core Business Logic**
- `crates/router/src/core/user.rs`
- `crates/router/src/core/user/dashboard_metadata.rs`
**3. Typ... | {"pr_number": 7787, "pr_title": "feat(users): refactor `ProdIntent` to support product-type context and merchant-scope", "merged_at": "2025-04-10T15:33:01Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"api_models": ["crates/api_models/src/user/dashboard_metadata.... |
<!-- 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. This is particular to support the refunds for the payments that was directly performed with the connector (example stripe) with out hyperswitch involve... | 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/query/relay.rs`
- `crates/diesel_models/src/relay.rs`
**3. Core Business ... | {"pr_number": 6918, "pr_title": "feat(router): add /retrieve api for relay", "merged_at": "2024-12-23T13:21:14Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "refund"]}, "hierarchy": {"api_models": ["crates/api_models/src/relay.rs"], "database": ["crates/dies... |
<!-- Describe your changes in detail -->
This PR updates the reason field in AdyenRefundRequest from Option<String> to Option<AdyenRefundRequestReason>, a strongly typed enum. This change ensures only supported values (FRAUD, CUSTOMER REQUEST, RETURN, DUPLICATE, OTHER) are used. | 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/adyen/transformers.rs`
**Code Patterns Applied:**
- Implement new functions (1 c... | {"pr_number": 8849, "pr_title": "fix(connector): Change Refund Reason Type in Adyen", "merged_at": "2025-08-08T13:06:37Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/connector_configs/toml/production.toml", ... |
<!-- Describe your changes in detail -->
As part of the subscription, a billing processor need to be configured at profile level to route the subscription creation and other related activities. | 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": 9438, "pr_title": "feat(billing): add support to configure billing processor in profile", "merged_at": "2025-09-23T19:41:29Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/admin.rs... |
<!-- Describe your changes in detail -->
This PR implements UCS(Unified Connector Service) Integration for SetupMandate and RepeatEverything (recurring payment) flows.
- Updated rust-grpc-client dependency to main branch
- Added log for Successful UCS connection | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payments/flows/authorize_flow.rs`
- `crates/router/src/core/payments/flows/setup_mandate_flow.rs`
- `crates/router/src/core/unified_connector_service.rs`
- ..... | {"pr_number": 8738, "pr_title": "feat(core): Hyperswitch <|> UCS Mandate flow integration", "merged_at": "2025-07-28T08:00:47Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core/payments/flows/a... |
<!-- Describe your changes in detail -->
Add hide card nickname field config for secure payment links. https://docs.hyperswitch.io/explore-hyperswitch/merchant-controls/integration-guide/web/customization#id-9.-hide-card-nickname-field . | 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": 6554, "pr_title": "feat(payments): [Payment links] add hide card nickname field config for secure payment links", "merged_at": "2024-11-18T12:32:16Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates... |
<!-- Describe your changes in detail -->
Removed functions that are not used in other files and removed imports that are only referenced by the unused functions.
[crates/router/src/connector/utils.rs](https://github.com/juspay/hyperswitch/blob/3cdb9e174ca384704781a4c56e826c3a5e39d295/crates/router/src/connector/utils... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/router/src/connector/utils.rs`
**Detailed Identifier Changes:**
Commit be33bc77:
Files to modify:
**crates/router/src/connector/utils.rs**
Modify existing code
Comm... | {"pr_number": 7994, "pr_title": "refactor: remove unused functions", "merged_at": "2025-05-14T10:29:02Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["connector"]}, "hierarchy": {"connectors": ["crates/router/src/connector/utils.rs"]}, "change_types": {}, "has_identifier_data": tru... |
<!-- Describe your changes in detail -->
For each countries present in Europe, their states are converted to ISO Standard
[Source for standard](https://github.com/juspay/hyperswitch-web/blob/main/src/States.json)
Note: A bugfix is present as well for address_id used to fetch billing_address for external authentic... | 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/mandates.rs`
**3. Core Business Logic**
- `crates/route... | {"pr_number": 7282, "pr_title": "feat(utils): add iso representation for each state for european countries", "merged_at": "2025-02-17T12:55:02Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment"]}, "hierarchy": {"api_models": ["crates/api_models/src/payments.rs"], "domain": ["... |
<!-- Describe your changes in detail -->
add support for partial authorization in payments flow
**Implementation**
1. Add `enable_partial_authorization` field to payments request and include it in the payment_intent table
2. When enabled in the request, it is forwarded to downstream connectors as well
3. In resp... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/payments.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/payment_attempt.rs`
- `crates/diesel_models/src/payment_intent.rs`
-... | {"pr_number": 8833, "pr_title": "feat(router): add support for partial authorization", "merged_at": "2025-08-06T14:28:24Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/payments.rs"], "database"... |
<!-- Describe your changes in detail -->
This will make the `mandate_payments` acceptable even when `setup_future_usage` is null in payments. | 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`
- `crates/router/src/core/payment_methods/utils.rs` | {"pr_number": 6812, "pr_title": "refactor(constraint_graph): revert handle for cases where setup_future_usage is null in payments is null in payments", "merged_at": "2024-12-11T17:08:34Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment"]}, "hierarchy": {"core_business": ["cra... |
<!-- Describe your changes in detail -->
- Added `split_payment_method_data` field to `confirm-intent` call to accept a `Vec` of payment methods
<img width="502" height="763" alt="image" src="https://github.com/user-attachments/assets/69ae3cc4-3d06-4980-b2d9-52b489aa98ad" /> | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/payments.rs`
**2. Other**
- `api-reference/v2/openapi_spec_v2.json`
- `crates/openapi/src/openapi_v2.rs`
**Code Patterns Applied:**
- Define new data st... | {"pr_number": 9469, "pr_title": "feat(router): Add Confirm-Intent API contract changes for split payments (v2)", "merged_at": "2025-09-25T17:56:40Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src... |
<!-- Describe your changes in detail -->
Reference https://github.com/juspay/hyperswitch/pull/7810 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/health_check.rs`
**2. Configuration Files**
- `config/config.example.toml`
- `config/deployments/env_specific.toml`
- `config/development.toml`
- ... and ... | {"pr_number": 7881, "pr_title": "chore(analytics): opensearch client creation based on config", "merged_at": "2025-04-23T14:25:19Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"core_business": ["crates/router/src/core/health_check.rs"], "config": ["config/c... |
Described in #6177 | 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_attempt.rs`
**2. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/router_response_types.rs`
**3. Core ... | {"pr_number": 6374, "pr_title": "feat(connector): add 3DS flow for Worldpay", "merged_at": "2024-10-21T14:14:20Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"database": ["crates/diesel_models/src/query/payment_attempt.rs"], "doma... |
This PR adds a payment link config for controlling the behavior or Submit button on payment links (`enable_button_only_on_form_ready`)
- If `enable_button_only_on_form_ready` is true - disallow incomplete form submission
- [DEFAULT and CURRENT] If false - allow incomplete form submission and throw validation errors | 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": 7517, "pr_title": "feat(payment-link): add config for enabling form button only when form is complete", "merged_at": "2025-03-17T15:05:30Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_model... |
This PR fixes Fiuu integration for PSync response and webhook response | 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": 7211, "pr_title": "fix(connector): [fiuu] update PSync and webhooks response", "merged_at": "2025-02-10T06:39:04Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["connector", "webhook"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors/fiuu.rs... |
<!-- Describe your changes in detail -->
Added google pay connector tokenization flow for finix connector. | 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/connector_configs/toml/development.toml`
- `crates/connector_configs/toml/production.to... | {"pr_number": 9734, "pr_title": "feat(connector): [Finix] Add Google Pay Connector Tokenization Flow", "merged_at": "2025-10-10T07:59:16Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core/conne... |
<!-- Describe your changes in detail -->
Previously the bank names were hard coded but we needed to read form `{config}.toml` files to send the supported banks inside `user_bank_options`
## Depricating bank list on top level of `ResponsePaymentMethodTypes` as we need to send it inside particular required fields... | 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. External Connector Integration**
- `crates/payment_methods/src/configs/payment_connector_required_fields.rs`
**3. Configuration Fi... | {"pr_number": 8779, "pr_title": "fix(eps_bank_name): send eps supported bank names inside the structs for sdk.", "merged_at": "2025-08-11T07:33:49Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src... |
Hotfix for - https://github.com/juspay/hyperswitch/pull/7649
- Fix dynamic fields for SepaBankTransfer
- Handle error case Status mapping
- Fix wasm Changes for SepaBankTransfer | 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": 7651, "pr_title": "refactor(connector): [TrustPay] Fix status and wasm changes ", "merged_at": "2025-03-27T08:56:21Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/connector_configs/toml/developm... |
Added template code for Dwolla.
API reference : https://developers.dwolla.com/docs/balance/api-reference/api-fundamentals | 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/configs.rs`
**2. Core Business Logic**
- `crates/router/src/core/admin.rs`
**3. External Connector Integration**
- `crates/commo... | {"pr_number": 8496, "pr_title": "feat(connector): [DWOLLA] - Add template code", "merged_at": "2025-07-01T12:34:47Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/configs.rs"], "core_business": ["crates/router/src/co... |
<!-- Describe your changes in detail -->
This PR fixes an issue where the total count of webhook events was incorrectly calculated when filtering by object ID. Previously, the total count logic was based on generic filters, which led to duplicate or incorrect counts when specific object ID filters were applied. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/webhooks/webhook_events.rs`
**Code Patterns Applied:**
- Add conditional logic for feature flags or filtering (1 changes)
**Detailed Identifier Changes:**
Commit 5... | {"pr_number": 8109, "pr_title": "fix: duplicate entries in total count when filtering by object ID", "merged_at": "2025-05-27T07:22:39Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "refund"]}, "hierarchy": {"core_business": ["crates/router/src/core/webhooks/... |
<!-- Describe your changes in detail -->
This pr contains the changes to populate `payment_method_data` in the samsung pay payment response. As part of this card_type is made a optional for wallet payment_method_data as samsung pay does not send credit or debit in the samsung pay 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`
- `crates/api_models/src/payments.rs`
- `crates/api_models/src/payments/additional_info.rs`
**2. Domain Models (Business Logic Types)... | {"pr_number": 7095, "pr_title": "fix(samsung_pay): populate `payment_method_data` in the payment response", "merged_at": "2025-02-03T21:50:07Z", "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 -->
This PR moves all payment method migration related code and functionality from the router crate to the payment_methods crate. This refactoring improves code organization and maintainability by keeping payment method related logic in a dedicated 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/cards_info.rs`
- `crates/hyperswitch_domain_models/src/ext_traits.rs`
- `crates/hyperswitch_domain_models/src/lib.rs`
**2. Core B... | {"pr_number": 7786, "pr_title": "refactor(paymentMethods): move all pm migration related changes to payment methods crate", "merged_at": "2025-05-13T08:44:52Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"domain": ["crates/hypersw... |
This PR fixes the Cypress API key validation issue, where the validation was failing for key_prefixes in API keys. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Utils**
- `cypress-tests/cypress/utils/RequestBodyUtils.js`
**Code Patterns Applied:**
- Extend existing types with new fields (1 changes) | {"pr_number": 9815, "pr_title": "ci(cypress): fix cypress api-key validation", "merged_at": "2025-10-14T08:07:47Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"utils": ["cypress-tests/cypress/utils/RequestBodyUtils.js"]}, "change_types": {"fields_added": 1}... |
<!-- Describe your changes in detail -->
changed cargo clippy command in workflow files to use default number of jobs instead of 2. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `.github/workflows/connector-sanity-tests.yml`
- `.github/workflows/connector-ui-sanity-tests.yml`
**2. Configuration Files**
- `.github/workflows/CI-pr.yml`
- `.github/w... | {"pr_number": 7088, "pr_title": "chore: run clippy with default number of jobs in github workflows", "merged_at": "2025-01-29T09:06:00Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"connectors": [".github/workflows/connector-sanity-tests.yml", ".github/workflows/... |
<!-- Describe your changes in detail -->
Merchant account creation on decision-engine is pre-requisite for making success based routing calls to it. Since toggle SR endpoint on Hyperswitch is the place where rule creation API of DE is being called, we can check whether merchant_account exists in DE, if exists, toggle ... | 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/admin.rs`
- `crates/router/src/core/routing.rs`
- `crates/router/src/core/routing/hel... | {"pr_number": 8191, "pr_title": "refactor(dynamic_routing): add logic for creating merchant account in decision engine", "merged_at": "2025-06-04T08:50:40Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_mo... |
<!-- Describe your changes in detail -->
This PR updates Hyperswitch Docker images to be prefixed by `docker.juspay.io`. I've just done a global search-replace to be honest.
## Motivation and Context
<!--
Why is this change required? What problem does it solve?
If it fixes an open issue, please link to the iss... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Configuration Files**
- `config/deployments/README.md`
- `docker-compose-development.yml`
- `docker-compose.yml`
**2. Other**
- `aws/hyperswitch_aws_setup.sh`
**Code Patterns Applied:**
- Extend existing ... | {"pr_number": 7368, "pr_title": "chore(docker): prefix Hyperswitch Docker image URIs with `docker.juspay.io`", "merged_at": "2025-03-03T15:37:11Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"config": ["config/deployments/README.md", "docker-compose-development.y... |
<!-- Describe your changes in detail -->
Added baseurl for `VGS` connector in relevant deployment TOML files | 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` | {"pr_number": 8059, "pr_title": "fix(config): Add VGS baseurl to deployments toml files", "merged_at": "2025-05-16T13:03:19Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["connector"]}, "hierarchy": {"tests": ["config/deployments/integration_test.toml"], "config": ["config/deployme... |
This PR fixes the request body order of the TSYS contract for the auth request | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/tsys/transformers.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (2 changes) | {"pr_number": 9579, "pr_title": "fix(connectors): [TSYS] change order of order_number in tsys auth request body", "merged_at": "2025-10-08T15:39:41Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_c... |
<!-- Describe your changes in detail -->
Repopulating the docker changes in the stable release | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Configuration Files**
- `docker-compose-development.yml`
- `docker-compose.yml`
**2. Other**
- `README.md`
- `scripts/docker_output.sh`
- `scripts/poststart_hook.sh`
- ... and 2 more files
**Code Pa... | {"pr_number": 7979, "pr_title": "fix: docker changes in setup script", "merged_at": "2025-05-08T09:01:27Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"config": ["docker-compose-development.yml", "docker-compose.yml"], "other": ["README.md", "scripts/docker_outpu... |
<!-- Describe your changes in detail -->
Added Default Enum Variant in RequestIncrementalAuthorization | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Other**
- `api-reference/v2/openapi_spec_v2.json`
- `crates/common_enums/src/enums.rs` | {"pr_number": 8948, "pr_title": "fix(core): Add Default Enum Variant in RequestIncrementalAuthorization", "merged_at": "2025-08-18T07:35:59Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"other": ["api-reference/v2/openapi_spec_v2.... |
Updated `organization_retrieve` api response to contain `organization_type` for v1 and v2 api | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/organization.rs`
**2. Type Definitions**
- `crates/router/src/types/api/admin.rs`
**3. Other**
- `api-reference/v1/openapi_spec_v1.json`
- `api-refer... | {"pr_number": 8660, "pr_title": "chore: update org retrieve api response to include org type", "merged_at": "2025-07-18T12:18:24Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"api_models": ["crates/api_models/src/organization.rs"], "types": ["crates/router/src/ty... |
<!-- Describe your changes in detail -->
this pr introduces feature_matrix api to 4 more connectors and in addition to that, pm filters also have been updated.
have written many scripts to verify the pm_filters and are attached in the issue | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/coinbase.rs`
- `crates/hyperswitch_connectors/src/connectors/iatapay.rs`
- `crates/hyperswitch_connectors/src/connectors/nexixpa... | {"pr_number": 7339, "pr_title": "feat(connector): introduce `feature_matrix` api to coinbase, iatapay, nexixpay and square", "merged_at": "2025-03-03T09:11:11Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "refund", "connector"]}, "hierarchy": {"connectors": ["crates/hyp... |
<!-- Describe your changes in detail -->
Add Support for Amazon Pay Redirect and Amazon Pay payment via Stripe | 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": 7056, "pr_title": "FEAT: Add Support for Amazon Pay Redirect and Amazon Pay payment via Stripe", "merged_at": "2025-02-05T15:24:59Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/p... |
Update Cypress Creds | 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": 7477, "pr_title": "ci: update wise connector cypress creds", "merged_at": "2025-03-11T08:47:32Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["connector"]}, "hierarchy": {"tests": [".github/workflows/cypress-tests-runner.yml"]}, "change_types": {"fields_added": 1}, "h... |
Implement mandate for Moneris Card | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/moneris.rs`
- `crates/hyperswitch_connectors/src/connectors/moneris/transformers.rs`
**Code Patterns Applied:**
- Define new data ... | {"pr_number": 7322, "pr_title": "feat(connector): [Moneris] Implement mandate for Moneris", "merged_at": "2025-03-05T12:25:27Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connecto... |
<!-- Describe your changes in detail -->
add correct field_type for required_fields for sepa and becs bank debits | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Configuration Files**
- `config/payment_required_fields_v2.toml` | {"pr_number": 8625, "pr_title": "fix(required_fields): add correct field_type for required_fields", "merged_at": "2025-07-13T12:02:48Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"config": ["config/payment_required_fields_v2.toml"]}, "change_types": {}, "has_ide... |
<!-- Describe your changes in detail -->
Mapping `status`, `error_code`, and `error_message` for `Stripe` Payment Processor `Sofort` Bank Transfer Payment Method as `Sofort` has been deprecated by `Stripe`. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `cypress-tests/cypress/e2e/configs/Payment/Stripe.js`
**Code Patterns Applied:**
- Extend existing types with new fields (3 changes) | {"pr_number": 7672, "pr_title": "refactor(cypress): update `Stripe` response `status`, `error_code`, and `error_message` for deprecated `Sofort`", "merged_at": "2025-04-01T08:50:24Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user"]}, "hierarchy": {"tests": ["cypress-... |
Add Aggregate API which enables merchants to retrieve summarized payment data based on a specified date range at profile or merchant level. The API aggregates key payment metrics, such as total transaction count, total processed amount, and status breakdown, helping merchants analyze their payment performance effective... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/payments/payment_intent.rs`
**2. Core Business Logic**
- `crates/router/src/core/payments.rs`
**3. Other**
- `crates/router/src/... | {"pr_number": 7196, "pr_title": "feat(router): add v2 endpoint retrieve payment aggregate based on merchant profile", "merged_at": "2025-02-14T14:02:44Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"domain": ["crates/hyperswitch_domai... |
<!-- Describe your changes in detail -->
This pr enables payout for release
Hotfix raised against: https://github.com/juspay/hyperswitch/pull/8817 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Configuration Files**
- `crates/router/Cargo.toml` | {"pr_number": 8819, "pr_title": "refactor(config): enable payout in prod release", "merged_at": "2025-08-05T07:53:31Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"config": ["crates/router/Cargo.toml"]}, "change_types": {}, "has_identifier_data": false, "commits_... |
- If Authorize.Net returns status code 1, which indicates an "`Approved`" status in the refund response, it means the refund has been created.
- But, "`Approved`" was previously marked as a "Successful Refund." We are now changing "Approved" to "Pending" because, at this stage, the connector has not yet marked the ref... | 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` | {"pr_number": 7208, "pr_title": "refactor(connector): [Authorizedotnet] fix refund status mapping", "merged_at": "2025-02-10T13:08:56Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/router/src/connector/author... |
<!-- Describe your changes in detail -->
Pass email in payment request body of Braintree as it is mandatory field for sending receipts in braintree | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/braintree/transformers.rs`
**Code Patterns Applied:**
- Define new data structures (1 changes)
- Extend existing types with new field... | {"pr_number": 7591, "pr_title": "refactor(connector): [BRAINTREE] Pass email in payment requests", "merged_at": "2025-03-21T15:18:23Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/c... |
<!-- Describe your changes in detail -->
Add setup mandate flow for cards | 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/flows/setup_mandate_flow.rs`
- `crates/rou... | {"pr_number": 9012, "pr_title": "feat(connector): [Nuvei] Implement setup mandate flow for cards", "merged_at": "2025-08-26T12:31:56Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/ro... |
<!-- Describe your changes in detail -->
- reference of payment_method_id was taken payment attempt but now it will be taken from payment_data
- payment attempt doesn't contain the context of payment_method_id before update tracker
- thus, this check was invalid | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payments/operations/external_vault_proxy_payment_intent.rs`
**Code Patterns Applied:**
- Add conditional logic for feature flags or filtering (1 changes) | {"pr_number": 9259, "pr_title": "fix(core): change condition for updating payment method status", "merged_at": "2025-09-03T14:00:30Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core/payments/o... |
<!-- Describe your changes in detail -->
Added wasm changes to collect metadata for visa_ctp
## 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)?
-->
Once this PR is merged check for `ctp_v... | To implement this **payment** 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": 7674, "pr_title": "feat(dashboard): Added wasm changes to collect metadata for visa_ctp", "merged_at": "2025-04-01T12:03:54Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["merchant", "connector", "card"]}, "hierarchy": {"connectors": ["crates/connector_configs/toml/developm... |
<!-- Describe your changes in detail -->
to_state_code method of router is not updated so the implementation from hyperswitch_connectors needs to be used and the one from router is depreciated.
Note: Contains remaning European countries for ISO conversion | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/utils.rs`
- `crates/router/src/connector/netcetera/netcetera_types.rs`
- `crates/router/src/connector/threedsecureio/transformers.rs`
- ... | {"pr_number": 7278, "pr_title": "refactor(utils): use to_state_code of hyperswitch_connectors in router", "merged_at": "2025-02-17T12:52:33Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "connector"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/utils... |
<!-- Describe your changes in detail -->
- Added `payout_method_id` to Payout API requests and responses.
- Added validations for requests with `payout_method_id`.
- Added `payout_method` to `PayoutData`.
- Added `transfer_method_id` to `PayoutsResponseData`.
- Changed `connector_manda... | 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/payouts.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/payment_method.rs`
**3. Do... | {"pr_number": 6687, "pr_title": "refactor(core): add recurring customer support for nomupay payouts.", "merged_at": "2025-02-05T14:28:03Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/payment_m... |
Hotfix for https://github.com/juspay/hyperswitch/pull/6738 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/payment_method.rs`
**2. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/router_flow_types/webhooks.rs`
**3. Core Bu... | {"pr_number": 6759, "pr_title": "feat(webhooks): adyen - consume and update connector's network_transaction_id in payment_methods", "merged_at": "2024-12-06T09:24:30Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"database": ["crates/diesel_models/src/payment_meth... |
<!-- Describe your changes in detail -->
When MCA Create is not done for Braintree, and connector creds are passed in Payment Intent Request, then Complete Authorize Flow fails. This PR is for fixing that. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payments.rs`
- `crates/router/src/core/payments/helpers.rs`
- `crates/router/src/core/payments/operations/payment_complete_authorize.rs`
- ... and 1 more file... | {"pr_number": 7501, "pr_title": "fix(connector): [BRAINTREE] Added fix for Braintree Creds Identifier", "merged_at": "2025-03-18T07:24:37Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core/paym... |
<!-- Describe your changes in detail -->
Connector code for following connectors is moved to crate hyperswitch_connectors:
1. Authorizedotnet
2. Checkout
3. Noon
4. Opayo
5. Opennode
6. Payme
7. Trustpay | 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/hyperswitch_connectors/... | {"pr_number": 7235, "pr_title": "refactor(connector): [AUTHORIZEDOTNET,CHECKOUT,NOON,OPAYO,OPENNODE,PAYME,TRUSTPAY] Move to crate hyperswitch_connectors", "merged_at": "2025-03-04T07:12:31Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarch... |
<!-- Describe your changes in detail -->
Fixed stack over flow for session call in authentication connectors
## 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 w... | To implement this **authentication** feature, you'll need to modify these architectural layers:
**1. Other**
- `crates/router/src/db/kafka_store.rs` | {"pr_number": 7983, "pr_title": "fix(router): Fixed stack over flow for session call in authentication connectors", "merged_at": "2025-05-08T10:10:33Z", "intent": {"feature_type": "authentication", "action": "add_feature", "entities": ["connector", "session"]}, "hierarchy": {"other": ["crates/router/src/db/kafka_store.... |
<!-- Describe your changes in detail -->
Currently, we have two endpoints for retrieving payment information in v2:
- GET /payments/:id
- GET /payments/:id:/get-intent
The endpoint /payments/{payment_id} is called after confirmation, at which point a payment attempt always exists. Currently, payment_attempt in P... | 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_data.rs`
**2. Core Business Logic**
- `crates/router/src/core/payment... | {"pr_number": 8126, "pr_title": "refactor: Payment Attempt as mandatory field in PaymentStatusData", "merged_at": "2025-05-29T10:25:00Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/... |
<!-- Describe your changes in detail -->
the existing amount conversion framework for certain connector is outdated. we need to migrate those connector to using the latest and greatest amount converter framework.
base - float/string major unit
minor - minor unit / string minor unit | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/bambora.rs`
- `crates/hyperswitch_connectors/src/connectors/bambora/transformers.rs`
- `crates/hyperswitch_connectors/src/connec... | {"pr_number": 8883, "pr_title": "refactor(connector): implement amount converter framework for bambora, dlocal and opennode ", "merged_at": "2025-08-18T14:41:34Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/... |
<!-- Describe your changes in detail -->
Webhook events can be filtered based on a list of event classes and event types. This PR also changes the endpoints `/events/{merchant_id}` and `/events/profile/list` to POST request. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/webhook_events.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/query/events.rs`
**3. Core Business Logic**
- `crates/router/src... | {"pr_number": 7275, "pr_title": "feat(webhook): add filter by event class and type", "merged_at": "2025-04-11T10:46:08Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "refund"]}, "hierarchy": {"api_models": ["crates/api_models/src/webhook_events.rs"], "databas... |
- Revert this [PR](https://github.com/juspay/hyperswitch/pull/6855)
- Pass `setup_future_usage = None` for ConnectorMandateId and NetworkMandateId. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payments/transformers.rs`
**2. External Connector Integration**
- `crates/router/src/connector/stripe/transformers.rs`
**Code Patterns Applied:**
- Extend existin... | {"pr_number": 6899, "pr_title": "fix(connector): [STRIPE] fix stripe mandate", "merged_at": "2024-12-20T10:59:46Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core/payments/transformers.rs"], "... |
This PR introduces -
- Core functionality to read and store raw acquirer responses for `payment` and `refund` operations.
- Read raw acquirer response from connector integration
- Store in `PaymentAttempt` and `Refund` tables
- Updates Adyen connector integration to read raw acquirer response.
- Exposes th... | 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/refunds.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/payment_attempt.rs`
- `crates/d... | {"pr_number": 7528, "pr_title": "feat: scheme error code and messages in payments api response", "merged_at": "2025-03-17T15:03:23Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "refund", "connector"]}, "hierarchy": {"api_models": ["crates/api_models/src/payments.rs", "c... |
<!-- Describe your changes in detail -->
fixes connector metadata, again. | 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": 9126, "pr_title": "fix(metadata): fix nordea metadata again", "merged_at": "2025-09-02T11:21:47Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user", "connector"]}, "hierarchy": {"connectors": ["crates/connector_configs/toml/development.toml", "crates/connector_confi... |
<!-- Describe your changes in detail -->
This PR is a part of v2 implementation of refunds. This PR contains refunds create core flow, i.e we can be able to create refunds for payments in v2.
**Important**
We are moving `refunds/transformers.rs` and `refunds/validator.rs` to a separate location because of accessib... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/Cargo.toml`
- `crates/api_models/src/events/refund.rs`
- `crates/api_models/src/refunds.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_mode... | {"pr_number": 7619, "pr_title": "feat(refunds_v2): Add refund create core flow", "merged_at": "2025-04-21T09:19:22Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/Cargo.toml", "crates/api_models/src... |
<!-- Describe your changes in detail -->
Nexixpay does not send error_code and error_message in case of failure responses. We will store NO_ERROR_CODE and nexixpay operation result as error_message in this case in our DB. This is sent in outgoing webhooks to the merchants.
Possible values of error messages:
1. Decli... | 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:**
- Implement new functions (1 changes)
- Extend existing types with new fields (8... | {"pr_number": 7713, "pr_title": "fix(connector): [Nexixpay] handle error code and message in failure response", "merged_at": "2025-04-04T13:26:49Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_con... |
<!-- Describe your changes in detail -->
This pull request updates the `docker/wasm-build.Dockerfile` to enhance the build process for WebAssembly (WASM) artifacts. The changes include adding a new dependency (`wasm-opt`) for optimizing WASM files, restructuring the build steps, and improving the overall build pipel... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Configuration Files**
- `crates/euclid_wasm/Cargo.toml`
**2. Other**
- `docker/wasm-build.Dockerfile` | {"pr_number": 8080, "pr_title": "chore: update the docker for wasm", "merged_at": "2025-05-26T07:57:18Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"config": ["crates/euclid_wasm/Cargo.toml"], "other": ["docker/wasm-build.Dockerfile"]}, "change_types": {}, "has_... |
<!-- Describe your changes in detail --> | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Other**
- `api-reference-v2/logo/dark.svg`
- `api-reference-v2/logo/light.svg`
- `api-reference/logo/dark.svg`
- ... and 3 more files | {"pr_number": 6783, "pr_title": "docs: add new logos for README and API reference", "merged_at": "2024-12-10T11:57:39Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"other": ["api-reference-v2/logo/dark.svg", "api-reference-v2/logo/light.svg", "api-reference/logo/... |
<!-- Describe your changes in detail -->
In UCS when we get None as attempt status we map it to `payments_grpc::PaymentStatus::AttemptStatusUnspecified`.
In payments via Unified Connector Service path, when for error responses it returned `attempt_status_unspecified`, it was being mapped to `AttemptStatus::Unresol... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payments/flows/authorize_flow.rs`
- `crates/router/src/core/payments/flows/external_proxy_flow.rs`
- `crates/router/src/core/payments/flows/psync_flow.rs`
- .... | {"pr_number": 9445, "pr_title": "fix: Map attempt_status_unspecified to None instead of Unresolved for HS<>UCS ErrorResponse", "merged_at": "2025-09-24T16:51:54Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crat... |
<!-- Describe your changes in detail -->
**CALCULATE WORKFLOW**
CALCULATE WORKFLOW
When we receive failed webhook and its intent retry count is more than the threshold, it will inserted into calculate job with the schedule time with 1 hour from now, before inserting it will first check the DB for existing entry for ... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/process_tracker.rs`
**2. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/payments.rs`
**3. Core Business Logic**
... | {"pr_number": 8848, "pr_title": "feat(revenue_recovery): Introducing new calculate job for card switching and invoice queueing", "merged_at": "2025-08-25T12:56:41Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"database": ["crates/... |
<!-- Describe your changes in detail -->
For each countries present in Europe, their states are converted to ISO Standard
[Source for standard](https://github.com/juspay/hyperswitch-web/blob/main/src/States.json)
Note: A bugfix is present as well for address_id used to fetch billing_address for external authentic... | 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/mandates.rs`
**3. Core Business Logic**
- `crates/route... | {"pr_number": 7273, "pr_title": "feat(utils): add iso representation for each state for european countries", "merged_at": "2025-02-15T15:54:41Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment"]}, "hierarchy": {"api_models": ["crates/api_models/src/payments.rs"], "domain": ["... |
<!-- Describe your changes in detail -->
Updated quarterly roadmap and slack invite URL's in `welcome_to_community.html` file which is sent as the email body whenever a user signs up. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Other**
- `crates/router/src/services/email/assets/welcome_to_community.html` | {"pr_number": 9341, "pr_title": "refactor(users): update url and text in welcome email", "merged_at": "2025-09-16T17:53:28Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"other": ["crates/router/src/services/email/assets/welcome_to_community.html"]}, "change... |
<!-- Describe your changes in detail -->
Hotfix PR
Original PR: [https://github.com/juspay/hyperswitch/pull/7433](https://github.com/juspay/hyperswitch/pull/7433) | 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`
**2. Database Layer (Queries & Schema)**
- `crates/analytics/src/query.rs`
**3. Core Business Logic**
- `crates/analytics/src/... | {"pr_number": 7448, "pr_title": "feat(analytics): refactor and rewrite authentication related analytics", "merged_at": "2025-03-06T13:15:49Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"api_models": ["crates/api_models/src/analytics/auth_events.rs"], "database":... |
### Implementation Details
The core of this change is the `filter_payment_methods` function, which is designed to be called iteratively for each `PaymentMethodsEnabledForConnector` object. The function's primary responsibility is to decide whether a given payment method should be included in the list of available op... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/Cargo.toml`
- `crates/api_models/src/events/payment.rs`
- `crates/api_models/src/payment_methods.rs`
- ... and 1 more files
**2. Domain Models (Business L... | {"pr_number": 8606, "pr_title": "feat(payment-methods): add filtering logic for payment method list v2", "merged_at": "2025-08-05T08:19:29Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "user"]}, "hierarchy": {"api_models": ["crates/api_models/Cargo.toml", "c... |
<!-- Describe your changes in detail -->
This PR will fix the bug where the `retry_count` was stuck at 0 and will add validation for entry in `process_tracker` only when `payment_retry_count` exceeds the `billing_connector_retry_threshold`.
Also fixed record back flow by implementing `get_amount` in `paymentAttempt` ... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/payments.rs`
**2. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/lib.rs`
- `crates/hyperswitch_domain_models/src/merchant... | {"pr_number": 7614, "pr_title": "fix(router): fix retry_count and add validation for process_tracker", "merged_at": "2025-04-09T09:56:59Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"api_models": ["crates/api_models/src/payments.rs"]... |
<!-- Describe your changes in detail -->
- Moved `CustomerAcceptance`, `AcceptanceType`, `OnlineMandate` to `common_types`
- Removed unnecessary conversions from the code
- Changed `payment_attempt` domain model and diesel model in v2 to use strict type | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/mandates.rs`
- `crates/api_models/src/payments.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/payment_attempt.rs`
**3. Domain ... | {"pr_number": 8299, "pr_title": "refactor: Move CustomerAcceptance to common_types", "merged_at": "2025-06-25T06:30:07Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/mandates.rs", "crates/api_m... |
<!-- Describe your changes in detail -->
Make bank_name field for EPS in stripe mandatore | 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. External Connector Integration**
- `crates/payment_methods/src/configs/payment_connector_required_fields.rs`
**3. Other**
- `api-referenc... | {"pr_number": 8577, "pr_title": "chore(stripe): Eps bank_name should be mandatory", "merged_at": "2025-07-14T10:44:42Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/enums.rs"], "connectors": ["... |
<!-- Describe your changes in detail -->
For generating session token for google pay, error was thrown if connector_wallet_details was not present and google pay related data won't be present in session token response thus parsing connector_wallet_details is made optional
Note: Hotfix corresponding to PR: https://... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payments/flows/session_flow.rs`
**Code Patterns Applied:**
- Add conditional logic for feature flags or filtering (1 changes) | {"pr_number": 7370, "pr_title": "fix(core): make parsing optional for connector_wallet_details in session token flow", "merged_at": "2025-02-25T13:55:35Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/route... |
The PR supports onboarding for new VSAAS merchants.
- Creating Platform Org
- Creation of Platform, and connected merchant accounts
- Change List response of merchant and organization list. | 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/organization.rs`
- `crates/api_models/src/user.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_... | {"pr_number": 7884, "pr_title": "feat(vsaas): integrate onboarding flow for vertical saas", "merged_at": "2025-05-12T15:02:09Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["merchant", "user", "token"]}, "hierarchy": {"api_models": ["crates/api_models/src/events/user.rs", "crates/a... |
<!-- Describe your changes in detail -->
<img width="539" height="305" alt="Screenshot 2025-09-18 at 22 35 30" src="https://github.com/user-attachments/assets/6ef6a861-7bb8-459e-9ac2-99791ec94c21" />
## Description
This PR introduces the **`invoice` table** along with supporting models, queries, schema definitio... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/invoice.rs`
- `crates/diesel_models/src/lib.rs`
- `crates/diesel_models/src/query.rs`
- ... and 3 more files
**2. External Connector Integrat... | {"pr_number": 9348, "pr_title": "feat: add invoice table", "merged_at": "2025-09-23T16:29:59Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"database": ["crates/diesel_models/src/invoice.rs", "crates/diesel_models/src/lib.rs", "cra... |
<!-- Describe your changes in detail -->
Add the payment method filter route to the V2 PaymentMethods implementation which list all available countries and currencies based on connector and payment method type. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Other**
- `crates/router/src/routes/app.rs`
- `crates/router/src/routes/payment_methods.rs`
**Code Patterns Applied:**
- Implement new functions (1 changes)
- Extend existing types with new fields (7 changes)
*... | {"pr_number": 8978, "pr_title": "feat(payment_methods): add payment-methods/filter endpoint to list countries and currencies for connector payment method in v2", "merged_at": "2025-08-22T13:26:14Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "connector"]}, "hierarchy": ... |
<!-- Describe your changes in detail --> | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Other**
- `api-reference/docs.json`
- `api-reference/essentials/authentication.mdx` | {"pr_number": 8719, "pr_title": "docs: add initial authentication page", "merged_at": "2025-07-28T09:57:35Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"other": ["api-reference/docs.json", "api-reference/essentials/authentication.mdx"]}, "change_types": {}, "has... |
Updates `om` CLI invocation based on this PR - https://github.com/juspay/omnix/pull/417 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Other**
- `.github/workflows/nix.yaml` | {"pr_number": 7259, "pr_title": "ci(nix): update om command invocation", "merged_at": "2025-02-14T10:53:13Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"other": [".github/workflows/nix.yaml"]}, "change_types": {}, "has_identifier_data": false, "commits_matched":... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.