prompt stringlengths 6 90.9k | response stringlengths 121 18.6k | metadata stringlengths 314 42.3k |
|---|---|---|
<!-- Describe your changes in detail -->
- In list payment method for merchant, list both mandate and non-mandate payment methods unless it is zero mandate flow
- If the `setup_future_usage` is `off_session` for a payment method, downgrade it to `on_session` for that payment method
- Add config for the zero mandates... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/payment_attempt.rs`
- `crates/diesel_models/src/schema.rs`
- `crates/diesel_models/src/user/sample_data.rs`
**2. Domain Models (Business Logic T... | {"pr_number": 7775, "pr_title": "feat(payment_method): add logic for setup_future_usage downgrade and add filter based on zero mandate config", "merged_at": "2025-04-17T12:09:52Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"datab... |
<!-- Describe your changes in detail -->
Currently normal 3ds payments are failing if we enable a merchant for UAS. This pr fixes that
https://github.com/juspay/hyperswitch/pull/9545 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payments.rs`
- `crates/router/src/core/unified_authentication_service.rs`
**2. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/... | {"pr_number": 9546, "pr_title": "fix(core): fixed ctp bug for confirmation and added multi profile support for modular auth", "merged_at": "2025-09-25T07:45:31Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src... |
<!-- Describe your changes in detail -->
- Add `payment_type` to Payments Get Intent 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. Other**
- `api-reference/v2/openapi_spec_v2.json`
**Co... | {"pr_number": 9066, "pr_title": "feat(router): Add payment_type to Get Intent response (v2)", "merged_at": "2025-08-28T06:22:39Z", "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 -->
Refactored the feature matrix PR by using `LazyLock` instead of `lazy_static!` | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/billwerk.rs`
- `crates/hyperswitch_connectors/src/connectors/fiservemea.rs`
- `crates/hyperswitch_connectors/src/connectors/tsys... | {"pr_number": 7494, "pr_title": "refactor(connector): [BILLWERK, FISERVEMEA, TSYS] use LazyLock instead of lazy_static", "merged_at": "2025-04-24T10:35:43Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "refund"]}, "hierarchy": {"connectors": ["crates/hyperswi... |
<!-- Describe your changes in detail -->
Added is_debit_routing_enabled in profile Create req types and update Profile table | 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": 7470, "pr_title": "feat(core): add profile level config for debit routing feature", "merged_at": "2025-03-26T14:19:46Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/admin.rs"], "d... |
Just modified the error logging on change of password for getting better error details and description. This helps in knowing about error in more detail. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/user.rs` | {"pr_number": 9667, "pr_title": "feat: Add attach_printable() for better error logging", "merged_at": "2025-10-15T16:19:48Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"core_business": ["crates/router/src/core/user.rs"]}, "change_types": {}, "has_identifie... |
<!-- Describe your changes in detail --> | 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": 6903, "pr_title": "fix(connector): Update mandate PMT configs for Mandate Supported Connectors", "merged_at": "2024-12-20T11:06:57Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"tests": ["config/deployments/integration_test.toml", "loadtest/config/d... |
<!-- Describe your changes in detail -->
This PR enables **authenticated access for platform merchants** via their API key to perform the following operations: | 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`
**3. Type Definitions**
- `crates/rou... | {"pr_number": 8156, "pr_title": "feat(vsaas): enable platform merchant API Key authentication for org-level operations", "merged_at": "2025-05-30T14:04:26Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"api_models": ["crates/api_models... |
<!-- Describe your changes in detail -->
This PR disables the `cargo-hack` step for PRs opened against hotfix branches, and in such cases `cargo check --features release` would be run instead. This is done to (hopefully) reduce the time required to get the hotfixes merged, and thus, deployed to our hosted environmen... | To implement this **connector_integration** feature, you'll need to modify these architectural layers:
**1. Configuration Files**
- `.github/workflows/CI-pr.yml`
**Code Patterns Applied:**
- Extend existing types with new fields (6 changes) | {"pr_number": 7334, "pr_title": "ci(CI-pr): disable `cargo-hack` step for hotfix PRs", "merged_at": "2025-02-24T20:56:28Z", "intent": {"feature_type": "connector_integration", "action": "add_feature", "entities": []}, "hierarchy": {"config": [".github/workflows/CI-pr.yml"]}, "change_types": {"fields_added": 6}, "has_id... |
<!-- Describe your changes in detail -->
This PR fixes NTID for PayPal by disabling it from running.
closes #7172 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `.github/workflows/cypress-tests-runner.yml`
- `cypress-tests/cypress/e2e/configs/Payment/Utils.js`
- `cypress-tests/cypress/e2e/spec/Payment/00020-MandatesUsingNTIDProxy.cy.js`
- ... and 2 more f... | {"pr_number": 7173, "pr_title": "ci(cypress): fix nmi and paypal", "merged_at": "2025-02-06T10:39:20Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"tests": [".github/workflows/cypress-tests-runner.yml", "cypress-tests/cypress/e2e/configs/Payment/Utils.js", ... |
<!-- Describe your changes in detail -->
`Trustly` and `Ideal` Bank Redirect payments were failing for `Ayden`.
`Trustly` error message: `Required object 'paymentMethod' is not provided.`
`Ideal` error message: `Could not find issuer for issuerId`
For `Trustly`, populated the `paymentMethod` to fix the issue.
`... | 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`
**2. Tests**
- `cypress-tests/cypress/e2e/configs/Payment/Adyen.js`
- `cypress-tests/cypress/support/redirectionHandler.j... | {"pr_number": 7139, "pr_title": "fix(connector): Ideal and multiple other failing PMs fixed in Ayden", "merged_at": "2025-02-25T20:27:57Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/router/src/connector/ady... |
<!-- Describe your changes in detail -->
This PR adds support for configuring revenue recovery retry algorithms at the business level. When a new billing connector is created, the columns are updated with Monitoring as the default algorithm type and the current timestamp. It introduces two new columns in the `busine... | 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/enums.rs`
- `crates/diesel_models/src/schema_v2.rs`
**2. Domain Models (Business Logic Types)**... | {"pr_number": 7772, "pr_title": "feat(router): Add revenue recovery retry algorithm type and data columns to business_profile table", "merged_at": "2025-04-24T10:03:20Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"database": ["crates... |
<!-- Describe your changes in detail --> | 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`
- `crates/diesel_models/src/schema_v2.rs`
**2. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src... | {"pr_number": 7917, "pr_title": "feat(payment_methods): add external vault connector service", "merged_at": "2025-05-21T12:16:40Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"database": ["crates/diesel_models/src/payment_method.rs", "crates/diesel_models/src/sch... |
<!-- Describe your changes in detail -->
disable partial auth feature for relay | 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`
**3. Other**
- `crates/router/src/routes/relay.rs... | {"pr_number": 6928, "pr_title": "fix(router): disable partial auth feature for relay", "merged_at": "2024-12-24T08:40:13Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"tests": ["config/deployments/integration_test.toml"], "config": ["config/deployments/production... |
<!-- Describe your changes in detail -->
- add accept-language from request headers into browser-info
- propagate the value to netcetera | 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. External Connector Integration**
- `crates/router/src/connector/netcetera/netcetera_types.rs`
- `cr... | {"pr_number": 7074, "pr_title": "feat(router): add accept-language from request headers into browser-info", "merged_at": "2025-01-29T08:33:30Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user", "connector"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/... |
This PR implements payment expiration handling for QR code-based payments through Adyen's OFFER_CLOSED webhook and fixes next_action display for terminal payment states. | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/webhooks.rs`
**2. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/revenue_recovery.rs`
- `crates/hyperswitch_domain_models/src/r... | {"pr_number": 8720, "pr_title": "feat(connector): [Adyen] receive incoming webhooks for pix expiry", "merged_at": "2025-07-29T08:47:11Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/webhooks.rs"], "d... |
<!-- Describe your changes in detail -->
Change the commerce indicator for cybersource applepay payment which was failing payment in production
Note: This pr is crucial for flowbird | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/router/src/connector/cybersource/transformers.rs` | {"pr_number": 6634, "pr_title": "fix(connector): [Cybersource] change commerce indicator for applepay", "merged_at": "2024-11-22T11:45:06Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "card"]}, "hierarchy": {"connectors": ["crates/router/src/connector/cybers... |
<!-- Describe your changes in detail -->
added new endpoint to delete tokenization record from tokenization table | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/events.rs`
- `crates/api_models/src/tokenization.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/query/tokenization.rs`
- `cr... | {"pr_number": 8361, "pr_title": "feat(router): Add new api for delete tokenization record", "merged_at": "2025-08-11T10:44:32Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "session", "token"]}, "hierarchy": {"api_models": ["crates/api_models/src/events.rs", "crates/api... |
<!-- Describe your changes in detail -->
the return url i.e., `hyperswitch.io` is throwing uncaught exceptions. the issue has been escalated to the team managing the website. and for now, we're ignoring any uncaught exceptions thrown by it.
additionally, have bumped the package versions except for cypress since i... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `cypress-tests/cypress/support/e2e.js`
- `cypress-tests/cypress/support/redirectionHandler.js`
- `cypress-tests/package-lock.json`
- ... and 1 more files
**Code Patterns Applied:**
- Extend exist... | {"pr_number": 7092, "pr_title": "fix(cypress): uncaught exceptions thrown by `hyperswitch.io`", "merged_at": "2025-01-24T07:22:53Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user"]}, "hierarchy": {"tests": ["cypress-tests/cypress/support/e2e.js", "cypress-tests/cypre... |
<!-- Describe your changes in detail -->
Added support for calculating new metrics based on smart retries for Analytics v2 dashboard.
The 2 metrics are:
- Payment Processed Amount and Count for smart retries
- Payments Success Rate and Failure Rate distribution for Smart Retries
`Payment Processed Amount and Cou... | 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. Other**
- `crates/analytics/src/payments/accumulator.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (5 ... | {"pr_number": 6575, "pr_title": "feat(analytics): add `smart_retries` only metrics for analytics v2 dashboard", "merged_at": "2024-11-19T19:21:45Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"api_models": ["crates/api_models/src/anal... |
<!-- Describe your changes in detail -->
Added a CI pipeline that will run cypress tests and generate code coverage reports for v2 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `.github/workflows/cypress-tests-runner.yml`
- `cypress-tests-v2/package-lock.json`
**2. Other**
- `.gitignore`
- `README.md`
- `docs/CONTRIBUTING.md`
- ... and 2 more files
**Code Pattern... | {"pr_number": 6884, "pr_title": "ci(workflows): Add code coverage reporting for v2", "merged_at": "2025-01-24T07:21:44Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"tests": [".github/workflows/cypress-tests-runner.yml", "cypress-tests-v2/package-lock.json"], "ot... |
- generated open api spec for create platform api
<img width="3182" height="2040" alt="image" src="https://github.com/user-attachments/assets/1373cff4-640d-4a4f-8b21-2fdb50a340e4" /> | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/user.rs`
**2. Other**
- `api-reference/README.md`
- `api-reference/docs.json`
- `api-reference/v1/openapi_spec_v1.json`
- ... and 4 more files
**C... | {"pr_number": 8692, "pr_title": "chore: updated open api spec documentation for create platform account", "merged_at": "2025-07-28T09:50:55Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"api_models": ["crates/api_models/src/user.rs"], "other": ["api-referen... |
This PR assigns the code owner to relevant modules for `hyperswitch-payouts`.
## Motivation and Context
- Helps offload PR review tasks for payout related modules to the respective team.
## How did you test it?
Not needed | To implement this **unknown** feature, you'll need to modify these architectural layers:
**1. Other**
- `.github/CODEOWNERS` | {"pr_number": 9411, "pr_title": "chore(git): add code owner for payout modules", "merged_at": "2025-09-17T17:59:19Z", "intent": {"feature_type": "unknown", "action": "add_feature", "entities": []}, "hierarchy": {"other": [".github/CODEOWNERS"]}, "change_types": {}, "has_identifier_data": false, "commits_matched": 0, "m... |
<!-- Describe your changes in detail -->
<details>
<summary>Changes</summary>
- Changed the Authorization in the `commands.js` because Authorization changes had been made recently.
- Changed field names in `payment_methods_enabled` accordingly as accepted by v2 endpoints.
</details> | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `cypress-tests-v2/cypress/e2e/configs/Payment/Commons.js`
- `cypress-tests-v2/cypress/support/commands.js`
**Code Patterns Applied:**
- Extend existing types with new fields (38 changes) | {"pr_number": 7805, "pr_title": "refactor(cypress-v2): change `Authorization` and `payment_methods_enabled` for v2 cypress tests", "merged_at": "2025-04-17T13:17:01Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user"]}, "hierarchy": {"tests": ["cypress-tests-v2/cypress... |
<!-- Describe your changes in detail -->
Added Invoice Number Fix | 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 (4 changes)
- Add conditional log... | {"pr_number": 8685, "pr_title": "fix(connector): [AUTHORIZEDOTNET] Added Invoice Number Fix", "merged_at": "2025-07-18T07:47:38Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connec... |
<!-- Describe your changes in detail -->
Add acknowledgement in adyen for incoming webhooks by sending status 200. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/common_enums/src/connector_enums.rs`
- `crates/hyperswitch_connectors/src/connectors/adyenplatform/transformers/payouts.rs` | {"pr_number": 9372, "pr_title": "feat(router): Handle incoming webhooks adyen", "merged_at": "2025-09-17T18:54:57Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/common_enums/src/connector_enums.rs", "crates/h... |
<!-- Describe your changes in detail -->
Affirm template code added | 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/toml/development.toml`
- `crates/connec... | {"pr_number": 8650, "pr_title": "feat(connector): [AFFIRM] add Connector Template Code", "merged_at": "2025-07-16T10:45:18Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/connector_endpoints.rs"], "connectors": ["cra... |
<!-- Describe your changes in detail -->
Have added a new API for enabling volume split for dynamic routing service | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/events/routing.rs`
- `crates/api_models/src/routing.rs`
**2. Core Business Logic**
- `crates/router/src/core/payments.rs`
- `crates/router/src/core/pa... | {"pr_number": 6662, "pr_title": "feat(routing): Enable volume split for dynamic routing", "merged_at": "2024-12-05T09:45:49Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"api_models": ["crates/api_models/src/events/routing.rs", "crates/api_models/src/routin... |
<!-- Describe your changes in detail -->
This PR adds amount conversion framework to rapyd.
rapyd accepts amount in MinorUnit | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/router/src/connector/rapyd.rs`
- `crates/router/src/connector/rapyd/transformers.rs`
- `crates/router/tests/connectors/rapyd.rs`
**2. Type Definitions**
- `crates... | {"pr_number": 6414, "pr_title": "refactor(connector): add amount conversion framework to rapyd", "merged_at": "2024-10-30T14:47:44Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"connectors": ["crates/router/src/connector/rapyd.rs", "crates/router/src/connector/ra... |
<!-- Describe your changes in detail -->
1. Add support to create a subscription with trial plans.
When this type of subscription is created, a payment of $0 will be made to validate the payment method and save it for future use. The incoming webhook for invoice-generated event should work similarly to the MIT flow.
... | 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/subscription.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/invoice.rs`
- `crates/dies... | {"pr_number": 9721, "pr_title": "feat(subscription): add support to create subscription with trial plans", "merged_at": "2025-10-10T14:44:11Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/payme... |
<!-- Describe your changes in detail --> | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/payments.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/payment_attempt.rs`
- `crates/diesel_models/src/payment_intent.rs`
-... | {"pr_number": 8485, "pr_title": "feat(connector): [Redsys] Use merchant payment_id for ds_merchant_order with length check", "merged_at": "2025-07-03T16:58:18Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/ap... |
<!-- Describe your changes in detail -->
1. add `organization_id` in authentication table of postgres
2. add `organization_id` in kafka queue and authentications table of clickhouse
3. send `organization_id` while logging events to clickhouse | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/authentication.rs`
- `crates/diesel_models/src/schema.rs`
- `crates/diesel_models/src/schema_v2.rs`
**2. Core Business Logic**
- `crates/rout... | {"pr_number": 7168, "pr_title": "feat(router): add `organization_id` in authentication table and add it in authentication events", "merged_at": "2025-02-06T15:19:15Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user"]}, "hierarchy": {"database": ["crates/diesel_models/... |
<!-- Describe your changes in detail -->
Added click to pay feature for Trustpay. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/trustpay/transformers.rs`
- `crates/hyperswitch_connectors/src/utils.rs`
**Code Patterns Applied:**
- Define new data structures (... | {"pr_number": 8304, "pr_title": "feat(connector): add click to pay feature for trustpay", "merged_at": "2025-06-25T06:31:44Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors... |
<!-- Describe your changes in detail -->
This PR introduces template code for new connector named `Facilitapay`.
Docs: https://sandbox-portal.facilitapay.com/#/docs | 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`
- `crates/router/src/core/payments/flows.rs`
**3. Ext... | {"pr_number": 7631, "pr_title": "feat(connector): Introduce connector template code for Facilitapay", "merged_at": "2025-03-27T13:33:42Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["connector"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/configs.rs"], "core_b... |
<!-- Describe your changes in detail -->
- Whenever `Refund Status` filter is applied on the analytics section on dashboard, errors are being generated.
- The wrong `RefundStatus` enum has been imported for the `RefundStatus` filter in `RefundFilters` struct in this PR: [https://github.com/juspay/hyperswitch/pull/298... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/analytics/refunds.rs`
**Code Patterns Applied:** | {"pr_number": 6431, "pr_title": "fix(analytics): fix refund status filter on dashboard", "merged_at": "2024-10-25T13:30:37Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user", "order", "refund"]}, "hierarchy": {"api_models": ["crates/api_models/src/analytics/refunds.rs"]}, "chang... |
<!-- Describe your changes in detail -->
GooglePay fixed in Ayden | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/router/src/connector/adyen/transformers.rs` | {"pr_number": 7393, "pr_title": "fix(connector): GooglePay fixed in Ayden ", "merged_at": "2025-03-03T07:51:16Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/router/src/connector/adyen/transformers.rs"]}, "ch... |
<!-- Describe your changes in detail -->
This PR will add a new variant in Dashboard Metadata for storing the recon state. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/user/dashboard_metadata.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/enums.rs`
**3. Core Business Logic**
- `crates/router/s... | {"pr_number": 7595, "pr_title": "feat(dashboard_metadata): Add `ReconStatus` in `dashboard_metadata`", "merged_at": "2025-03-26T10:26:02Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user", "order"]}, "hierarchy": {"api_models": ["crates/api_models/src/user/dashboard_metadata.rs"... |
<!-- Describe your changes in detail -->
- Currently `profile_id` in the JWT is optional, this PR makes it non-optional. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/query/user_role.rs`
**2. Core Business Logic**
- `crates/router/src/core/user.rs`
- `crates/router/src/core/user_role.rs`
**3. Type Definitions... | {"pr_number": 6537, "pr_title": "refactor(users): Make `profile_id` in the JWT non-optional", "merged_at": "2024-11-18T07:57:18Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"database": ["crates/diesel_models/src/query/user_role.rs"], "core_business": ["crates/ro... |
<!-- Describe your changes in detail -->
api contract change for confirm with hs vault token | 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": 8624, "pr_title": "feat(payment-method): api contract change for confirm with hs vault token", "merged_at": "2025-07-13T11:06:02Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["token"]}, "hierarchy": {"api_models": ["crates/api_models/src/payments.rs"], "domain": ["cr... |
<!-- Describe your changes in detail -->
Add support for payment and refund webhooks
note: Needs dashboard wasm deployment to test in sandbox. | 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": 6315, "pr_title": "feat(connector): [fiuu] Add support for payment and refund webhooks", "merged_at": "2024-10-16T14:17:04Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/connector_configs/toml/d... |
<!-- Describe your changes in detail -->
BNPL flow added for affirm connector.
Only added mock server for affirm and not cypress because BNPL is currently not supported in cypress. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/connector_validation.rs`
**2. External Connector Integration**
- `crates/common_enums/src/connector_enums.rs`
- `crates/connector_configs/src/connector.rs`
-... | {"pr_number": 8795, "pr_title": "feat(connector): [AFFIRM] BNPL flow added (Alpha)", "merged_at": "2025-08-24T20:12:21Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["connector"]}, "hierarchy": {"core_business": ["crates/router/src/core/connector_validation.rs"], "connectors": ["cr... |
<!-- Describe your changes in detail -->
Add error details when payment void is failed at connector level and update the status accordingly. | 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_data.rs`
- `crates/hyperswitch_domain_models/src/... | {"pr_number": 9595, "pr_title": "fix(payments): update error handling for payment void v2", "merged_at": "2025-10-07T08:22:58Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/payments.rs"], "doma... |
<!-- Describe your changes in detail -->
Moved customer saved PML route to OLAP in v2 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Other**
- `crates/router/src/routes/app.rs` | {"pr_number": 8303, "pr_title": "fix(router): Move Customer PML endpoint to OLAP (v2)", "merged_at": "2025-06-18T08:23:04Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer"]}, "hierarchy": {"other": ["crates/router/src/routes/app.rs"]}, "change_types": {}, "has_identifier_da... |
<!-- Describe your changes in detail -->
Database Changes:
Added network_transaction_id column (VARCHAR(255), nullable) to the payment_attempt table via migration 2025-08-20-095434_add_ntid_in_attempt_table.
Added get_network_transaction_id method to PaymentsResponseData in crates/hyperswitch_domain_models/src... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/payment_attempt.rs`
- `crates/diesel_models/src/schema.rs`
- `crates/diesel_models/src/schema_v2.rs`
- ... and 1 more files
**2. Domain Model... | {"pr_number": 9032, "pr_title": "feat(core): Add network_transaction_id in payments Response ", "merged_at": "2025-08-24T17:00:41Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"database": ["crates/diesel_models/src/payment_attempt... |
<!-- Describe your changes in detail -->
Added dpa_client_id, , provider to click to pay session response
## 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)?
-->
setup visa_ctp
Create mer... | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/payments.rs`
**2. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/payments.rs`
**3. Core Business Logic**
- `crates/router/src/... | {"pr_number": 7683, "pr_title": "feat(session): Added dpa_client_id, provider to click to pay session response", "merged_at": "2025-04-04T09:41:14Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"api_models": ["crates/api_models/src/payments.... |
<!-- Describe your changes in detail -->
This feature add connector-level tokenization to Hyperswitch V2, allowing secure storage of card data as tokens at payment connectors like Braintree.
Additionally Tokenization in router is not implemented, because of temp locker mechanism which is still pending.
For conne... | 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.rs`
- `crates/router/src/core/payments/operations/payment_confirm_intent.rs`
**Code Patterns Applied:... | {"pr_number": 9506, "pr_title": "feat(payments): add tokenization action handling to payment flow for braintree", "merged_at": "2025-09-30T08:07:13Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src... |
<!-- Describe your changes in detail -->
Currently if we cancel the transaction after initiating with netcetera we are trying hard fetch cavv stored in temp locker, which is causing 5xx.
with this PR we will be ignoring the cavv fetch error since it will be fetched in authorisation flow if authorisation need to be ... | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/authentication.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (1 changes) | {"pr_number": 8035, "pr_title": "fix(router): fixed netcetera flow for backward flow cavv fetching", "merged_at": "2025-05-15T12:44:04Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["user", "transaction"]}, "hierarchy": {"core_business": ["crates/router/src/core/authentication.rs"]}, "ch... |
<!-- Describe your changes in detail -->
Revert this PR:
https://github.com/juspay/hyperswitch/pull/8887 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/api_locking.rs`
**2. Type Definitions**
- `crates/redis_interface/src/types.rs`
**3. Other**
- `crates/redis_interface/src/commands.rs`
- `crates/redis_inte... | {"pr_number": 9001, "pr_title": "revert: feat(core): add support for api locking with multiple keys for a single api (#8887)", "merged_at": "2025-08-20T11:53:35Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"core_business": ["crates/router/src/core/api_locking.rs... |
<!-- Describe your changes in detail -->
This PR updates all the typos in the repository. For reference, check: https://github.com/juspay/hyperswitch/actions/runs/15082629873/job/42401247676?pr=8056 | 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/unified_authentication_service.rs`
**... | {"pr_number": 8063, "pr_title": "chore: fix typos in the repo", "merged_at": "2025-05-23T07:52:09Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"api_models": ["crates/api_models/src/payments.rs"], "domain": ["crates/hyperswitch_domain_models/src/router_request_ty... |
Hotfix for https://github.com/juspay/hyperswitch/pull/7874 | 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": 7898, "pr_title": "feat(payments): add support for connector testing (Adyen)", "merged_at": "2025-04-25T07:55:19Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["merchant", "connector", "card"]}, "hierarchy": {"api_models": ["crates/api_models/src/payments.rs"], "domai... |
<!-- Describe your changes in detail -->
Improved OpenAPI documentation for V2 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `api-reference-v2/api-reference/merchant-connector-account/merchant-connector--create.mdx`
- `api-reference-v2/api-reference/merchant-connector-account/merchant-connector--delet... | {"pr_number": 6496, "pr_title": "docs(openapi): Fixed API documentation for V2", "merged_at": "2024-11-12T07:16:32Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["merchant", "connector"]}, "hierarchy": {"connectors": ["api-reference-v2/api-reference/merchant-connector-account/merch... |
<!-- Describe your changes in detail -->
this pr fixes bug in paysafe where skrill wallet payment method was throwing `501`. the reason being, we've added a check in preprocessing call that applied to all wallet payment methods for paysafe instead of having it applied to apple pay specifically.
this pr fixes 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` | {"pr_number": 9687, "pr_title": "fix(connector): restrict preprocessing to only apple pay for paysafe", "merged_at": "2025-10-07T11:04:41Z", "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 -->
Add `encoded_data` from `PaymentsRetrieveRequest` in `payment_attempt` inside `get_trackers` for PSync | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payments/operations/payment_get.rs` | {"pr_number": 8177, "pr_title": "fix(router): Handle encoded_data in PSync [V2]", "merged_at": "2025-06-02T10:26:16Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment"]}, "hierarchy": {"core_business": ["crates/router/src/core/payments/operations/payment_get.rs"]}, "change_typ... |
This PR adds user APIs to manage themes. Earlier themes was being managed using Admin apis.
These are the following APIs
1. Create Theme
2. Delete Theme
3. Update Theme
4. Upload Asset
5. Find Theme by Theme ID
6. List themes by entity level
7. Get Theme by lineage
- Added Theme resource and ThemeManage p... | 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/theme.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/query/user/theme.rs`
**3. C... | {"pr_number": 8387, "pr_title": "feat(themes): Create user APIs for managing themes", "merged_at": "2025-07-28T07:46:16Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["merchant", "user", "order"]}, "hierarchy": {"api_models": ["crates/api_models/src/events/user.rs", "crates/api_mod... |
<!-- Describe your changes in detail -->
Hotfix PR
Original PR: [https://github.com/juspay/hyperswitch/pull/7483](https://github.com/juspay/hyperswitch/pull/7483) | 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": 7499, "pr_title": "feat(analytics): modified authentication queries and added generate report for authentications", "merged_at": "2025-03-12T12:31:20Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"api_models": ["crates/api_models/src/analytics/auth_... |
<!-- Describe your changes in detail -->
This PR addresses two issues : | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/revenue_recovery/types.rs`
**2. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/stripebilling.rs`
- `crates/hyperswitch_connect... | {"pr_number": 8548, "pr_title": "fix(RevenueRecovery): Skip record-back for failed invoices on auto-voiding billing connectors", "merged_at": "2025-08-01T10:58:15Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["cr... |
<!-- Describe your changes in detail -->
- Payout is done via Decrypted Token data of Apple pay.
- The decrypted data is directly collected in the request to initiate payout.
- Integration is done via Worldpay for the following flow
Note: this is a hotfix raised against https://github.com/juspay/hyperswitch/pull/... | 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/payouts.rs`
**2. Core Business Logic**
- `crates/router/src/core/payment_methods/vault.rs`
**3. External Connector In... | {"pr_number": 9875, "pr_title": "feat(payouts): apple pay decrypt payout", "merged_at": "2025-10-16T08:47:47Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "merchant", "order"]}, "hierarchy": {"api_models": ["crates/api_models/src/enums.rs", "crates/api_models/src/payou... |
<!-- Describe your changes in detail -->
this pr updates the `adyen` payouts credentials and it also replaces wise from running in github ci | 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": 7756, "pr_title": "ci(cypress-ci): remove wise payout from running in github ci", "merged_at": "2025-04-08T08:31:18Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"tests": [".github/workflows/cypress-tests-runner.yml"]}, "change_types": {"fields_adde... |
Added the missed feature matrix supported PM , paypal for authorizedotnet.
Changes we added to authorizedotnet.rs file only, .toml files already have the desired changes in original PR.
Original PR : #7854 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/authorizedotnet.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (4 changes) | {"pr_number": 8072, "pr_title": "fix(connector): Added Paypal in feature matrix for authorizedotnet", "merged_at": "2025-05-21T10:23:21Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/sr... |
<!-- Describe your changes in detail -->
ORIGINAL PR: https://github.com/juspay/hyperswitch/pull/7525
Add mandate revoke flow to Braintree
https://developer.paypal.com/braintree/graphql/guides/payment_methods/#delete | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/braintree.rs`
- `crates/hyperswitch_connectors/src/connectors/braintree/transformers.rs`
- `crates/hyperswitch_connectors/src/de... | {"pr_number": 7527, "pr_title": "feat(connector): [BRAINTREE] Add revoke mandate flow", "merged_at": "2025-03-15T12:12:25Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors/brain... |
We're passing base64 encoded data in SetupMandate flow for apple pay token, but Novalnet expects apple pay token as decoded raw string. This PR fixes this. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/novalnet/transformers.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (1 changes) | {"pr_number": 7973, "pr_title": "fix(connector): [Novalnet] send decoded token for apple pay payment", "merged_at": "2025-05-12T15:06:33Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["token"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors/novalnet/tra... |
<!-- 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": 7440, "pr_title": "feat(connector): [PAYSTACK] Electronic Fund Transfer(EFT) Payment Flows", "merged_at": "2025-03-17T07:21:35Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/connector_configs/to... |
Added below config related testcases in cypress
"collect_shipping_details_from_wallet_connector"
"collect_billing_details_from_wallet_connector"
"always_collect_billing_details_from_wallet_connector"
"always_collect_shipping_details_from_wallet_connector" | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `cypress-tests/cypress/e2e/PaymentTest/00024-ConnectorAgnostic.cy.js`
- `cypress-tests/cypress/e2e/PaymentTest/00025-ConfigTest.cy.js`
- `cypress-tests/cypress/fixtures/business-profile.json`
- ..... | {"pr_number": 6622, "pr_title": "ci(cypress): Added Config Testcases", "merged_at": "2024-11-28T09:34:54Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user", "connector"]}, "hierarchy": {"tests": ["cypress-tests/cypress/e2e/PaymentTest/00024-ConnectorAgnostic.cy.js", "cypress-tes... |
<!-- Describe your changes in detail -->
This PR adds support for sending the `x-tenant-id` and `x-request-id` in the grpc headers | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payments/routing.rs`
- `crates/router/src/core/routing.rs`
- `crates/router/src/core/routing/helpers.rs`
**2. Utils**
- `crates/common_utils/src/consts.rs`
... | {"pr_number": 6904, "pr_title": "refactor(grpc): send `x-tenant-id` and `x-request-id` in grpc headers", "merged_at": "2024-12-22T18:11:45Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core/pay... |
<!-- Describe your changes in detail -->
This pr will enable profile level custom creation from API and also enable org level custom role read | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/role.rs`
- `crates/diesel_models/src/schema.rs`
- `crates/diesel_models/src/schema_v2.rs`
**2. Core Business Logic**
- `crates/router/src/cor... | {"pr_number": 7877, "pr_title": "feat(users): profile level custom role write", "merged_at": "2025-04-24T10:35:43Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["merchant", "user", "token"]}, "hierarchy": {"database": ["crates/diesel_models/src/role.rs", "crates/diesel_models/src/s... |
<!-- Describe your changes in detail -->
Added a webhook notifier for pre- and post-installation of `hyperswitch` using docker compose. This webhook sends the following API call to `https://hyperswitch.gateway.scarf.sh`:
- **initiated** (when a user tries to install hyperswitch)
- **success** (when all the compone... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Configuration Files**
- `docker-compose.yml`
**2. Other**
- `scripts/poststart_hook.sh`
- `scripts/prestart_hook.sh`
**Code Patterns Applied:**
- Extend existing types with new fields (13 changes)
- Add cond... | {"pr_number": 7653, "pr_title": "feat(docker): add webhook notifiers for installation tracking", "merged_at": "2025-04-15T08:08:13Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user", "webhook"]}, "hierarchy": {"config": ["docker-compose.yml"], "other": ["scripts/poststart_hook.s... |
<!-- Describe your changes in detail -->
Currently, while generating reports on the dashboard, the current setup only supports forwarding reports to the email of the account signed in.
This PR adds support to have custom emails in the input text box on the dashboard while generating and forwarding the report, to make... | 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`
**Code Patterns Applied:**
- Extend existing types with new fields (1 changes) | {"pr_number": 6776, "pr_title": "feat(analytics): add support for multiple emails as input to forward reports", "merged_at": "2024-12-10T12:20:39Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"api_models": ["crates/api_models/src/anal... |
<!-- Describe your changes in detail -->
During the recurring payout transaction, if confirm false is being explicitly sent in the request - throw a Bad Request Error. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payouts/validator.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (1 changes)
- Add conditional logic for feature flags or filtering (1 changes... | {"pr_number": 9424, "pr_title": "feat(core): Confirm true mandatory when using stored payment method id in payouts", "merged_at": "2025-09-25T07:15:42Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "merchant", "order"]}, "hierarchy": {"core_business": ["crates/router/sr... |
<!-- Describe your changes in detail -->
Added Amazon Pay connector using Amazon Pay Wallet for the US region.
Flow:
1. In the Hyperswitch dashboard, when configuring the Amazon Pay connector, merchants are required to provide their API keys, Merchant ID, and Store ID. The Merchant ID and Store ID are specifical... | 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. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/payment_method_data.r... | {"pr_number": 7062, "pr_title": "feat(connector): [AMAZONPAY] add Payment flows for Amazon Pay Wallet", "merged_at": "2025-08-29T08:49:23Z", "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 involves adding WASM changes for Google Pay for Finix Connector.
Previously `Merchant Identity ID` was being retrieved from the metadata in MCA call. This field is now moved to Authentication field `MultiAuthKey`. | 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": 9845, "pr_title": "fix(connector): Add WASM Changes for Finix Google Pay", "merged_at": "2025-10-15T16:19:48Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core/connector_validatio... |
<!-- Describe your changes in detail -->
Refactors for currency conversion which invlolves:
-> Better error propagation
-> Redis lock realease, if data isn't fetched from api, so that the other subsequent calls donot fail. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Utils**
- `crates/router/src/utils/currency.rs`
**Code Patterns Applied:** | {"pr_number": 6671, "pr_title": "refactor(currency_conversion): release redis lock if api call fails", "merged_at": "2024-11-29T10:37:43Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"utils": ["crates/router/src/utils/currency.rs"]}, "change_types": {"imports_add... |
<!-- Describe your changes in detail -->
Currently schemas weren't there for Error Response structs. Added them for status code 400 in payments and refunds APIs. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/errors/types.rs`
**2. Configuration Files**
- `crates/openapi/Cargo.toml`
**3. Other**
- `api-reference/v1/openapi_spec_v1.json`
- `api-reference/v2/... | {"pr_number": 8684, "pr_title": "fix(openapi): Added Error Response Schema for Status Code 400", "merged_at": "2025-07-22T09:00:55Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user", "refund"]}, "hierarchy": {"api_models": ["crates/api_models/src/errors/types.rs"], "c... |
<!-- Describe your changes in detail -->
Added Peachpayments Cypress Test. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/peachpayments.rs`
- `crates/hyperswitch_connectors/src/connectors/peachpayments/transformers.rs`
**2. Tests**
- `cypress-tests/... | {"pr_number": 9573, "pr_title": "feat(connector): Add Peachpayments Cypress", "merged_at": "2025-09-29T09:06:41Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user", "refund"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors/peachpayments.rs"... |
This PR hides the visible scrollbars on payment link's checkout widget. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payment_link/payment_link_initiate/payment_link.css`
**Code Patterns Applied:**
- Extend existing types with new fields (1 changes) | {"pr_number": 9541, "pr_title": "fix(ui): hide visible scrollbar from checkout widget for windows", "merged_at": "2025-10-01T13:15:54Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "order"]}, "hierarchy": {"core_business": ["crates/router/src/core/payment_link/payment_li... |
<!-- Describe your changes in detail -->
- We were required to populate connector_customer_id after merchant migrates the data (data having connector_customer_id) in shopper_reference_id (customer_id for Adyen).
- But connector_customer_id gets populated in router_data only for connectors listed under:
```
[con... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payments/customers.rs`
**2. Tests**
- `config/deployments/integration_test.toml`
- `loadtest/config/development.toml`
**3. Configuration Files**
- `config/c... | {"pr_number": 8937, "pr_title": "fix(core): connector customer id population dependency removed from config", "merged_at": "2025-08-18T08:01:02Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/cor... |
<!-- Describe your changes in detail -->
Moved connectors Bamboraapac, Boku, Ebanx, Gocardless, Prophetpay and Rapyd from router crate to hyperswitch_connectors crate | 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": 6652, "pr_title": "refactor(connector): Move connectors Bamboraapac, Boku, Gocardless, Prophetpay, Rapyd", "merged_at": "2024-12-05T08:14:44Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/ro... |
<!-- Describe your changes in detail -->
**Enhanced Payment Listing API with Multi-Value Filtering**
This feature adds support for retrieving a filtered list of payments via a `GET /v2/payments/list` endpoint where multiple values can be provided for a single filter key (e.g. `status`, `currency`, `connector`, etc.... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/payments.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/query/payment_attempt.rs`
**3. Domain Models (Business Logic Types)**
... | {"pr_number": 8794, "pr_title": "feat(payments): add PaymentListFilterConstraints and payments_list_by_filter endpoint for v2", "merged_at": "2025-08-21T14:04:23Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates... |
This pull request introduces two main features for payouts:
1. **Configurable `payout_id` in API Requests**:
* The `payout_id` field in payout creation API requests can now be optionally provided by the merchant. If provided, this ID will be used for the payout. If not provided, the system will generate one.... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/events/payouts.rs`
- `crates/api_models/src/payouts.rs`
- `crates/api_models/src/webhooks.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diese... | {"pr_number": 8395, "pr_title": "feat(payouts): add domain type for PayoutId", "merged_at": "2025-07-01T14:45:02Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "merchant", "user"]}, "hierarchy": {"api_models": ["crates/api_models/src/events/payouts.rs", "crates/api_mode... |
This PR removes validation on `max_length` for the `return_url` in PaymentsRequest. | 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. Tests**
- `cypress-tests/cypress/e2e/spec/Payment/00022-Variations.cy.js`
**3. Other**
- `api-reference/openapi_spec.json` | {"pr_number": 8125, "pr_title": "refactor(api): remove max_length validation for return_url in PaymentsRequest", "merged_at": "2025-05-24T08:47:38Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment"]}, "hierarchy": {"api_models": ["crates/api_models/src/payments.rs"], "tests":... |
<!-- Describe your changes in detail --> | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/connector_endpoints.rs`
**2. External Connector Integration**
- `crates/connector_configs/src/connector.rs`
- `crates/connector_c... | {"pr_number": 8488, "pr_title": "feat(connector): [SIFT] add Connector Template Code ", "merged_at": "2025-08-08T13:23:45Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/connector_endpoints.rs"], "connectors": ["crat... |
<!-- Describe your changes in detail -->
**Recovery Incoming Webhooks service :**
Consume incoming webhooks of billing platforms to schedule revenue recovery retries in hs.
**Endpoint :**
v2/webhooks/revenue_recovery/{{profile_id}}/{{merchant_connector_account_id}}
**Authentication :**
Source verification.... | 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/payments.rs`
- `crates/api_models/src/webhooks.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/s... | {"pr_number": 7109, "pr_title": "feat(connector): Add support for passive churn recovery webhooks", "merged_at": "2025-02-22T21:44:08Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "connector"]}, "hierarchy": {"api_models": ["crates/api_models/Cargo.toml", "c... |
<!-- Describe your changes in detail -->
add infra-values in intent kafka events | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Type Definitions**
- `crates/common_utils/src/types/keymanager.rs`
- `crates/router/src/types/domain/types.rs`
**2. Other**
- `crates/router/src/db/kafka_store.rs`
- `crates/router/src/services/kafka.rs`
... | {"pr_number": 8264, "pr_title": "refactor: add infra-values in intent kafka events", "merged_at": "2025-06-05T13:46:55Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user"]}, "hierarchy": {"types": ["crates/common_utils/src/types/keymanager.rs", "crates/router/src/types... |
<!-- Describe your changes in detail -->
1. Error type changed from `InternalServerError` to `InvalidRequestData`
2. The `attach_printable` method was removed
3. Instead, the error message is now included directly in the `InvalidRequestData` variant with a `message` field
## How did you test it?
<!--
Di... | To implement this **connector_integration** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/admin.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (2 changes) | {"pr_number": 8665, "pr_title": "fix(core): fixed invalid merchant country code error object", "merged_at": "2025-07-24T09:08:53Z", "intent": {"feature_type": "connector_integration", "action": "add_feature", "entities": ["merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core/admin.rs"]}, "change_types":... |
<!-- Describe your changes in detail -->
Changed `async-bb8-diesel crate from custom [fork](https://github.com/jarnura/async-bb8-diesel) to crates.io [version](https://github.com/oxidecomputer/async-bb8-diesel) | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Database Layer (Queries & Schema)**
- `crates/diesel_models/Cargo.toml`
**2. Configuration Files**
- `crates/drainer/Cargo.toml`
- `crates/router/Cargo.toml`
- `crates/storage_impl/Cargo.toml`
**3. Other*... | {"pr_number": 8028, "pr_title": "chore: Move async-bb8-diesel crate to crates.io version", "merged_at": "2025-05-15T12:05:55Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"database": ["crates/diesel_models/Cargo.toml"], "config": ["crates/drainer/Cargo.toml", "cr... |
<!-- Describe your changes in detail -->
Implement card payment with Worldpay xml
Hotfix for https://github.com/juspay/hyperswitch/pull/8076
> Note: Status updation takes 5-10 mins at the connector
## How did you test it?
<!--
Did you write an integration/unit/API test to verify the code changes?
Or did yo... | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/admin.rs`
**2. External Connector Integration**
- `crates/common_enums/src/connector_enums.rs`
- `crates/connector_configs/src/connector.rs`
- `crates/connector_co... | {"pr_number": 8139, "pr_title": "feat(connector): [Worldpayxml] add card payment", "merged_at": "2025-05-26T11:52:53Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core/admin.rs"], "connectors": ["cra... |
<!-- Describe your changes in detail -->
This pr adds the functionality to read custom role at profile level | 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/role.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/query/role.rs`
- `crates/diesel_models/src/role.rs`
- `crates/... | {"pr_number": 6875, "pr_title": "feat(users): custom role at profile read", "merged_at": "2025-02-05T14:28:03Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["merchant", "user", "connector"]}, "hierarchy": {"api_models": ["crates/api_models/src/user_role/role.rs"], "database": ["cra... |
<!-- Describe your changes in detail -->
Add visa click to pay support | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/payments.rs`
**2. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/configs.rs`
- `crates/hyperswitch_domain_models/src/router_req... | {"pr_number": 7562, "pr_title": "feat(core): Add visa click to pay support", "merged_at": "2025-03-28T08:31:11Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/payments.rs"], "domain": ["crates/hypersw... |
<!-- Describe your changes in detail -->
Added `first_attempt` as a filter in `PaymentFilters`.
This is required for the new Analytics v2 `Smart Retries` Metrics, specifically `Smart Retries Successful Distribution` and `Smart Retries Failure Distribution`, for calculations only involving smart retries (ignoring fi... | 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`
**3. Type Definitions**
- `crates/analytics/src/paymen... | {"pr_number": 6604, "pr_title": "feat(analytics): add `first_attempt` as a filter for PaymentFilters", "merged_at": "2024-11-24T13:39:07Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"api_models": ["crates/api_models/src/analytics/pay... |
- remove merchant return url from `router_data`
- We are not using merchant return url at the connectors, we should always send our return url to the connectors | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/payment_intent.rs`
**2. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/payments/payment_intent.rs`
- `crates/hyp... | {"pr_number": 6895, "pr_title": "refactor(core): remove merchant return url from `router_data`", "merged_at": "2024-12-24T11:53:52Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"database": ["crates/diesel_models/src/payment_intent... |
<!-- Describe your changes in detail -->
Currently payment_intent stores platform_merchant_id. This can be used to identify if the payment was created by platform merchant.
If the payment was initialized by platform merchant, the merchant who is the owner of the payment should not be able to do any operations on th... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payments/operations/payment_approve.rs`
- `crates/router/src/core/payments/operations/payment_cancel.rs`
- `crates/router/src/core/payments/operations/payment_ca... | {"pr_number": 7204, "pr_title": "refactor(payments): Add platform merchant account checks for payment intent", "merged_at": "2025-02-14T10:05:46Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/co... |
<!-- Describe your changes in detail -->
add card_discovery filter to payment list and 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. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/query/payment_attempt.rs`
**3. Domain Models (Business Logic Types)**
... | {"pr_number": 7230, "pr_title": "feat(core): add card_discovery filter to payment list and payments Response", "merged_at": "2025-02-14T10:05:46Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/p... |
<!-- Describe your changes in detail -->
Add globalpay, globepay, itaubank, nexinets, nuvei, prophetpay, zen connectors in feature matrix | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/globalpay.rs`
- `crates/hyperswitch_connectors/src/connectors/globepay.rs`
- `crates/hyperswitch_connectors/src/connectors/itaub... | {"pr_number": 7258, "pr_title": "feat(connector): [globalpay, globepay, itaubank, nexinets, nuvei, prophetpay, zen] add in feature matrix", "merged_at": "2025-05-06T07:34:05Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "order"]}, "hierarchy": {"connectors":... |
<!-- Describe your changes in detail -->
This pull request refactors and fixes the Postman test suite for the archipel payment connector in the Hyperswitch payments platform . The PR addresses several issues with the existing test cases and makes them compatible with the `archipel` connector's actual capabilities. | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `postman/collection-dir/archipel/Flow Testcases/Happy Cases/Scenario5b-Create a zero auth mandate and recurring payment (using connector agnostic)/.meta.json`
- `postman/collection-di... | {"pr_number": 8360, "pr_title": "ci(postman): fix `archipel` configs and test cases", "merged_at": "2025-06-25T12:17:36Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["payment", "user", "refund"]}, "hierarchy": {"connectors": ["postman/collection-dir/archipel/Flow Testcases/Happy Cases/S... |
<!-- Describe your changes in detail -->
Irrespective of what is sent in the connector field - be it `bluecode` or `calida`, it will be treated as `calida` at Hyperswitch's end. We would be sending back connector as `calida` in the response and the db it would also be saved as `calida`. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/common_enums/src/connector_enums.rs`
- `crates/hyperswitch_connectors/src/connectors/calida.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (1 ch... | {"pr_number": 9817, "pr_title": "fix(connector): [CALIDA] Treat Bluecode as an alias for Calida", "merged_at": "2025-10-15T16:45:31Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/common_enums/src/connector_en... |
<!-- Describe your changes in detail -->
This PR address the 5xx that occurs with GlobalPay connector when the required field `account_name` is not passed during MCA creation.
Below migration needs to be run on hosted environments:
```sql
UPDATE merchant_connector_account
SET metadata = jsonb_set(
metad... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/admin.rs`
**2. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/globalpay/transformers.rs`
**Code Patterns Applied:**
- Implement ... | {"pr_number": 7540, "pr_title": "fix(connector): [globalpay] address 5xx due to deserialization issue when `account_name` is not passed", "merged_at": "2025-03-24T08:23:52Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_busine... |
<!-- Describe your changes in detail --> | 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": 6910, "pr_title": "fix(connector): Update mandate PMT configs for Mandate Supported Connectors", "merged_at": "2024-12-20T12:09:28Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"tests": ["config/deployments/integration_test.toml", "loadtest/config/d... |
<!-- Describe your changes in detail -->
This PR adds, adyen split payment support.
Changes taken up in this PR
1. Add adyen split request to PaymentRequest
```
"split_payments": {
"adyen_split_payment": {
"store": "4935y84385736",
"split_items": [{
"split_typ... | 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/payment_attempt.rs`
- `crates/diesel_models/src/schema.rs`
- `crates/diese... | {"pr_number": 6952, "pr_title": "feat(router): add adyen split payments support", "merged_at": "2025-02-10T07:12:05Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/payments.rs"], "database": ["crates/... |
Enhanced Stax Connector in cypress for Comprehensive Testing.
## How did you test it?
**STAX**
<img width="561" alt="stax" src="https://github.com/user-attachments/assets/5a1dddb0-3e72-4112-a37f-aeb5387ad785" />
Note: 3ds payments silently falling back to no-3ds(Should throw validation)
## Checklist
<... | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. Tests**
- `cypress-tests/cypress/e2e/configs/Payment/Modifiers.js`
- `cypress-tests/cypress/e2e/configs/Payment/Stax.js`
- `cypress-tests/cypress/e2e/configs/Payment/Utils.js`
**Code Patterns Applied:**
- Extend ex... | {"pr_number": 8404, "pr_title": "ci(cypress): Add Stax connector test in cypress", "merged_at": "2025-06-24T14:43:55Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["payment", "user", "connector"]}, "hierarchy": {"tests": ["cypress-tests/cypress/e2e/configs/Payment/Modifiers.js", "cypress... |
<!-- Describe your changes in detail -->
Fixed Typos in the codebase (master branch) | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payment_methods/vault.rs`
- `crates/router/src/core/payments.rs`
**2. Type Definitions**
- `crates/router/src/types/transformers.rs`
**Code Patterns Applied:**... | {"pr_number": 8857, "pr_title": "fix(ci): Fix Spell Check For CI Pull Request", "merged_at": "2025-08-08T13:19:54Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"core_business": ["crates/router/src/core/payment_methods/vault.rs", "crates/router/src/core/payments.r... |
Some connectors like Novalnet do not have a separate list of refund errors, they only have a single list for all the possible connector error codes.
In such cases, the error codes and messages are stored under "Authorize" flow in GSM table.
During refund related error when we fetch GSM in code, we will have to fet... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/refunds.rs`
**2. Other**
- `crates/router/src/consts.rs` | {"pr_number": 7129, "pr_title": "feat(core): Add Authorize flow as fallback flow while fetching GSM for refund errors", "merged_at": "2025-02-05T15:29:42Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "user"]}, "hierarchy": {"core_business": ["crates/router/s... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.