prompt stringlengths 6 90.9k | response stringlengths 121 18.6k | metadata stringlengths 314 42.3k |
|---|---|---|
Adds the following fields to the api and diesel models Feature meta data
retry_count: Total number of billing connector + recovery retries for a payment intent.
payment_connector_transmission: It's supposed to tell if the payment_connector has been called or not.
billing_connector_id: To update the invoice at... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/payments.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/types.rs`
**3. Domain Models (Business Logic Types)**
- `crates/hypers... | {"pr_number": 7176, "pr_title": "refactor(router): add revenue_recovery_metadata to payment intent in diesel and api model for v2 flow", "merged_at": "2025-02-14T11:41:35Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models"... |
Add wasm changes for , interac , skrill and paysafe card | 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": 9455, "pr_title": "feat(connector): [Paysafe] add wasm changes", "merged_at": "2025-09-19T14:25:22Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["card"]}, "hierarchy": {"connectors": ["crates/connector_configs/toml/development.toml", "crates/connector_configs/toml/pr... |
<!-- Describe your changes in detail -->
Closes #5305 | 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.json`
- `api-reference/openapi_spec.json` | {"pr_number": 6452, "pr_title": "docs: Added desc. for wallets other than AP, GP", "merged_at": "2024-10-29T07:56:09Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"api_models": ["crates/api_models/src/payments.rs"], "other": ["api-reference-v2/openapi_spec.json",... |
<!-- Describe your changes in detail -->
Updated dashboard.toml to reflect the latest dashboard changes for open-source users.
 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Configuration Files**
- `config/dashboard.toml` | {"pr_number": 7707, "pr_title": "chore(dashboard): update dashboard toml", "merged_at": "2025-04-03T07:10:34Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"config": ["config/dashboard.toml"]}, "change_types": {}, "has_identifier_data": false, "commits_match... |
<!-- Describe your changes in detail -->
When adding the injector as a crate in connector-service, getting following
```bash
Compiling injector v0.1.0 (/Users/shivansh.mathur/Desktop/VS_Code/hyperswitch/crates/injector)
error[E0433]: failed to resolve: could not find `tracing` in the list of imported crates
... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Type Definitions**
- `crates/injector/src/types.rs`
**2. Configuration Files**
- `crates/injector/Cargo.toml`
**3. Other**
- `Cargo.lock`
- `crates/injector/src/injector.rs`
**Code Patterns Applied:**
- ... | {"pr_number": 9124, "pr_title": "feat(injector): adding tracing to injector for dependency issues", "merged_at": "2025-09-01T09:29:32Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user", "order"]}, "hierarchy": {"types": ["crates/injector/src/types.rs"], "config": ["cr... |
<!-- Describe your changes in detail -->
Template code added for new connector Inespay
This PR is related to issue: https://github.com/juspay/hyperswitch-cloud/issues/7514 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/connector_enums.rs`
**2. Core Business Logic**
- `crates/router/src/core/admin.rs`
- `crates/router/src/core/payments/connector_integration_v2_impls.rs`
... | {"pr_number": 6614, "pr_title": "feat(connector): [INESPAY] add Connector Template Code", "merged_at": "2024-11-26T07:40:31Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["connector"]}, "hierarchy": {"api_models": ["crates/api_models/src/connector_enums.rs"], "core_business": ["cra... |
<!-- Describe your changes in detail -->
Use $(...) notation instead of legacy `...` in the shell files.
Removes the use of deprecated backticks notation (cf. [SC2006](https://www.shellcheck.net/wiki/SC2006)). | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `scripts/add_connector.sh`
**2. Other**
- `INSTALL_dependencies.sh`
- `aws/hyperswitch_aws_setup.sh`
- `aws/hyperswitch_cleanup_setup.sh`
**Code Patterns Applied:**
- Ad... | {"pr_number": 6337, "pr_title": "fix: replace deprecated backticks with $(...) for command substitution", "merged_at": "2024-11-05T08:29:48Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"connectors": ["scripts/add_connector.sh"], "other": ["INSTALL_dependencies.s... |
<!-- Describe your changes in detail -->
Change the commerce indicator for cybersource applepay payment which was failing payment in production
Hotfix correspond to PR - [#6634](https://github.com/juspay/hyperswitch/pull/6634)
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": 6675, "pr_title": "fix(connector): [Cybersource] change commerce indicator for applepay", "merged_at": "2024-11-27T11:30:18Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "card"]}, "hierarchy": {"connectors": ["crates/router/src/connector/cybers... |
This PR adds support for Adyen tokenized card payouts in the AdyenPlatform connector. This enables processing payouts using stored PSP tokens
- Restructured `AdyenCardIdentification` as an enum supporting both raw card data and stored payment method IDs
- Added `StoredPaymentCounterparty` and `RawPaymentCounterpart... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payments/routing.rs`
- `crates/router/src/core/payouts.rs`
- `crates/router/src/core/payouts/helpers.rs`
- ... and 1 more files
**2. External Connector Integ... | {"pr_number": 9040, "pr_title": "feat(connector): [Adyenplatform] process payouts using PSP tokens", "merged_at": "2025-08-25T13:10:04Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core/payment... |
This PR removes the `vault_private_key` from the configs. | To implement this **unknown** feature, you'll need to modify these architectural layers:
**1. Configuration Files**
- `config/development.toml` | {"pr_number": 7825, "pr_title": "ci(configs): remove vault private key from configs", "merged_at": "2025-04-16T08:26:05Z", "intent": {"feature_type": "unknown", "action": "unknown", "entities": []}, "hierarchy": {"config": ["config/development.toml"]}, "change_types": {}, "has_identifier_data": false, "commits_matched"... |
This PR fixes an issue where internal user roles were being displayed in the dashboard.
With this change, all internal roles are filtered out, ensuring only relevant user-facing roles are visible. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/user_role/role.rs`
**Code Patterns Applied:**
- Modify database queries (1 changes) | {"pr_number": 9402, "pr_title": "fix(user_role): Filter out internal roles in list roles API", "merged_at": "2025-09-22T18:36:13Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core/user_role/rol... |
<!-- Describe your changes in detail -->
- A new field in introduced in payment_intent table called extended_return_url
- This deprecate the existing return_url field since it can take string only upto length 255
- extended_return_url can now take length upto 2048 size
- write is done into the new field (extended_r... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/payments.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/payment_intent.rs`
- `crates/diesel_models/src/schema.rs`
**3. Domain ... | {"pr_number": 8322, "pr_title": "refactor(core): introduce new field in payment_intent to handle longer return_url", "merged_at": "2025-06-12T10:07:57Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "user"]}, "hierarchy": {"api_models": ["crates/api_models/src... |
<!-- Describe your changes in detail -->
Alpha Integ Added Gift Card Payments 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/payments/additional_info.rs`
**2. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/pa... | {"pr_number": 8701, "pr_title": "feat(connector): [BHN] Add BHN GiftCard Flow( Alpha)", "merged_at": "2025-08-22T16:43:32Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "connector", "card"]}, "hierarchy": {"api_models": ["crates/api_models/src/payments.rs", "crates/api_m... |
<!-- Describe your changes in detail -->
This pull request adds debit routing support for Apple Pay. In the Apple Pay decryption flow, if debit routing is enabled by the merchant and the card type is debit, a call will be made to the decision engine to retrieve the supported card networks and the potential debit routi... | 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/payment_method_data.rs`
**2. Core Business Logic**
- `crates/router/src/core/debit_routing.rs`
- `crates/router/src/core/payments... | {"pr_number": 8673, "pr_title": "feat(debit_routing): add debit routing support for apple pay", "merged_at": "2025-07-18T14:54:09Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/payme... |
<!-- Describe your changes in detail -->
Apple pay payments for noon were failing due to PR#7921. Adding AED to the currency list for apple pay is a temporary fix for this failure. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Configuration Files**
- `config/deployments/production.toml` | {"pr_number": 8217, "pr_title": "chore: Update apple pay currency filter configs", "merged_at": "2025-06-09T07:57:15Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment"]}, "hierarchy": {"config": ["config/deployments/production.toml"]}, "change_types": {}, "has_identifier_data... |
<!-- Describe your changes in detail -->
`Boleto`, `Trustly`, `Alipay`, `Wechatpay` PMs added in connector `shift4` | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/shift4.rs`
- `crates/hyperswitch_connectors/src/connectors/shift4/transformers.rs`
**2. Tests**
- `config/deployments/integrati... | {"pr_number": 8476, "pr_title": "feat(connector): [shift4] Boleto, Trustly, Alipay, Wechatpay PMs added", "merged_at": "2025-07-03T09:21:36Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connector... |
<!-- Describe your changes in detail -->
refactor ctp flow to fetch mca_id and get the connector creds instead of connector_name
https://github.com/juspay/hyperswitch/pull/6859 | 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`
**3. Domain Models (Business Logic Types)**
- `crate... | {"pr_number": 7087, "pr_title": "refactor(router): refactor ctp flow to fetch mca_id and get the connector creds instead of connector_name", "merged_at": "2025-01-22T09:16:07Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["connector"]}, "hierarchy": {"api_models": ["crates/api_mode... |
<!-- Describe your changes in detail -->
Earlier, the `additional_payment_method_data` was not being updated in the psync call because the check was applied on `payment_data.payment_method_data`, which at the time of the psync call was not populated.
In this PR, we have updated the logic to apply the check on the `pa... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payments/operations/payment_response.rs`
**Detailed Identifier Changes:**
Commit 407be56e:
Files to modify:
**crates/router/src/core/payments/operations/payment_r... | {"pr_number": 9519, "pr_title": "feat(core): update additional payment method data in psync response", "merged_at": "2025-09-26T08:26:11Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core/payme... |
<!-- Describe your changes in detail -->
Implementation of
Payment,Refund,void , customer create , tokenization for non3ds cards for finix
## Test cases
<details>
<summary> Payment : Automatic </summary>
## Request
```json
{
"amount": 689,
"customer_id":"hello_world",
"currency": "U... | 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": 9680, "pr_title": "feat(connector): Card non3ds | FINIX", "merged_at": "2025-10-09T13:19:07Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core/connector_validation.rs"], "connecto... |
<!-- Describe your changes in detail -->
This PR includes:
- Implementation of ```Nomupay payout flows```.
- The connector utilizes ```payout_method_id``` for subsequent payouts.
- ```Cypress tests``` for payout using ```payout_method_id```.
- modified josekit, for empty payload, "{}" changed to "".
commit: ht... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/enums.rs`
**2. Core Business Logic**
- `crates/router/src/core/admin.rs`
**3. External Connector Integration**
- `crates/common_enums/src/connector_enum... | {"pr_number": 6511, "pr_title": "feat(connector): [Nomupay] Implement nomupay payouts flows", "merged_at": "2025-02-25T20:23:58Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "user", "connector"]}, "hierarchy": {"api_models": ["crates/api_models/src/enums.rs"], "core_bu... |
Update connector creds for Novalnet | 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": 7035, "pr_title": "ci: update cypress creds for Novalnet", "merged_at": "2025-01-15T08:41:29Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["connector"]}, "hierarchy": {"tests": [".github/workflows/cypress-tests-runner.yml"]}, "change_types": {"fields_added": 1}, "has... |
<!-- Describe your changes in detail -->
Added PayPal Redirect Payment Flow. First we Create an Order and then in the return_url, customer gets redirected. After that we Capture the funds.
Note: We are getting a missing fields error from the connector, possibly because this particular payment method hasn't been ena... | 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": 8669, "pr_title": "feat(connector): [FISERV] Added PayPal Redirect Payment Method", "merged_at": "2025-08-08T09:29:32Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/connector_configs/toml/develo... |
Hotfix for https://github.com/juspay/hyperswitch/pull/7623 | 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` | {"pr_number": 7675, "pr_title": "fix(connector): [CYBERSOURCE] change ucaf_collection_indicator for mastercard payments via netcetera", "merged_at": "2025-04-01T13:21:26Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/... |
<!-- Describe your changes in detail -->
- Fixed spell checks
- Added `routing_approach` field in routing events API response | 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/payments/routing.rs`
- `crates/router/src/core/routing/helpers.rs`
**3. Other**
- `c... | {"pr_number": 8227, "pr_title": "fix: Fixed spell check", "merged_at": "2025-06-06T11:47:33Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "connector"]}, "hierarchy": {"api_models": ["crates/api_models/src/routing.rs"], "core_business": ["crates/router/src/co... |
<!-- Describe your changes in detail -->
`Blik`, `Klarna`, `Bitpay` PMs added for connector `shift4`. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/shift4.rs`
- `crates/hyperswitch_connectors/src/connectors/shift4/transformers.rs`
**2. Tests**
- `config/deployments/integrati... | {"pr_number": 8478, "pr_title": "feat(connector): [shift4] Blik, Klarna, Bitpay PMs added", "merged_at": "2025-07-03T14:19:13Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connecto... |
<!-- Describe your changes in detail -->
Template PR | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payments/flows.rs`
**2. External Connector Integration**
- `crates/common_enums/src/connector_enums.rs`
- `crates/hyperswitch_connectors/src/connectors.rs`
-... | {"pr_number": 7052, "pr_title": "feat(connector): [COINGATE] Add Template PR ", "merged_at": "2025-02-06T14:33:44Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"core_business": ["crates/router/src/core/payments/flows.rs"], "connectors": ["crates/common_enums/src/... |
Transaction Monitoring means to record all the transaction that are happening in the billing connectors and storing them in our database. So that we can use those to train our model and get insights from that data in revenue recovery flow.
To support monitor the transaction happening in the billing connectors and to g... | 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`
- `crates/hyperswitch_domain_models/src/revenue_recovery.rs`
- `crates/hyperswitch_domain_models/src/router_request_ty... | {"pr_number": 7867, "pr_title": "feat(connector): [Recurly] add invoice sync support along with transaction monitoring ", "merged_at": "2025-05-02T12:12:23Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user", "connector"]}, "hierarchy": {"domain": ["crates/hyperswitch_... |
Described in #6508 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payments/flows.rs`
**2. External Connector Integration**
- `crates/hyperswitch_connectors/src/default_implementations.rs`
**3. Type Definitions**
- `crates/rou... | {"pr_number": 6481, "pr_title": "refactor: move Payout traits to hyperswitch_interfaces for connectors crate", "merged_at": "2024-11-12T11:24:53Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["connector"]}, "hierarchy": {"core_business": ["crates/router/src/core/payments/flows.rs"]... |
<!-- Describe your changes in detail -->
Network error code, network advice code and network error message should be consumed across connectors.
**Stripe** - Stripe shares network adivice code and network decline code. [source](https://docs.stripe.com/api/errors#errors-network_advice_code)
Network advice code... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/bankofamerica/transformers.rs`
- `crates/hyperswitch_connectors/src/connectors/cybersource/transformers.rs`
- `crates/hyperswitc... | {"pr_number": 7760, "pr_title": "fix(connector): Add network error message support for payment connectors", "merged_at": "2025-04-11T10:49:15Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connect... |
<!-- Describe your changes in detail -->
https://github.com/juspay/hyperswitch/pull/7978 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/authentication.rs`
**2. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/router_request_types/authentication.rs`
-... | {"pr_number": 8005, "pr_title": "refactor(authentication): moved cavv storing from table to temp locker", "merged_at": "2025-05-12T13:55:06Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"database": ["crates/diesel_models/src/authentication.rs"], "domain": ["crate... |
ArchiPEL requires one-way TLS in their UAT environment to verify incoming requests. To support this:
A CA certificate must be provided and included with each request to enable proper server verification.
NOTE: The PEM certificate must be converted to a JSON-safe string format (i.e., escaped \n as \\r\\n or \\n). ... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payment_methods/cards.rs`
**2. External Connector Integration**
- `crates/connector_configs/toml/development.toml`
- `crates/connector_configs/toml/production.t... | {"pr_number": 8128, "pr_title": "feat(core): add one-way TLS support with CA certificate for ArchiPEL UAT environment", "merged_at": "2025-05-25T15:58:06Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"core_business": ["crates/router/s... |
<!-- Describe your changes in detail -->
This PR creates a new table named `themes` in the DB. This will be used to store the `theme_id` for any lineage of `tenant_id`, `org_id`, `merchant_id` and `profile_id`. | 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.rs`
- `crates/diesel_models/src/query/user/theme.rs`
- `crates/diesel_models/src/schema.rs`
- ... and 3 more files
**2. Type Defin... | {"pr_number": 6533, "pr_title": "feat(themes): Setup themes table", "merged_at": "2024-11-14T09:16:40Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["merchant"]}, "hierarchy": {"database": ["crates/diesel_models/src/query/user.rs", "crates/diesel_models/src/query/user/theme.rs", "c... |
<!-- Describe your changes in detail -->
This PR adds payment methods list endpoint for payment methods endpoint for payment methods. This will be used to display the list of payment methods that are enabled by the merchant.
<img width="1720" alt="Screenshot 2025-01-03 at 11 59 48 PM" src="https://github.com/user-a... | 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/connector_enums.rs`
- `crates/api_models/src/events.rs`
- ... and 3 more files
**2. Database Layer (Queries & Schem... | {"pr_number": 6938, "pr_title": "feat(payment_methods_v2): add payment methods list endpoint", "merged_at": "2025-01-13T10:05:07Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/admin.rs", "crate... |
<!-- Describe your changes in detail -->
Deleting API Key needs Merchant ID. So, deleting it after deleting the merchant itself yields a error message in the response which goes like `"API key not provided or invalid API key used"`, but, its solely because the Merchant ID used is not authenticated because the Merchant... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Other**
- `postman/collection-dir/stripe/PaymentConnectors/.meta.json` | {"pr_number": 8339, "pr_title": "fix(postman): fix `stripe` test cases failures", "merged_at": "2025-06-13T08:20:44Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["merchant", "user"]}, "hierarchy": {"other": ["postman/collection-dir/stripe/PaymentConnectors/.meta.json"]}, "change_t... |
<!-- Describe your changes in detail -->
Add create and update, bulk update APIs for cards_info table. These APIs will be used to update card bin details stored in cards_info table. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/cards_info.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/cards_info.rs`
- `crates/diesel_models/src/query/cards_info.rs`
**3.... | {"pr_number": 7194, "pr_title": "feat(core): Add support for cards bin update", "merged_at": "2025-03-04T09:24:59Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user", "card"]}, "hierarchy": {"api_models": ["crates/api_models/src/cards_info.rs"], "database": ["crates/diesel_models... |
<!-- Describe your changes in detail -->
In the CIT call, we store the stripe split payment details inside Mandate Metadata and during the MIT calls we retrieve the split payments data from there and use it in the MIT calls. And if the merchant sends split payment details again in the MIT call, we match it. If its t... | 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. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/errors/api_error_response.rs`
**3. Core Business Logic... | {"pr_number": 8326, "pr_title": "fix(connector): [STRIPE] Retrieving Connect Account Id from Mandate Metadata in MITs", "merged_at": "2025-06-18T12:23:52Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_mod... |
<!-- Describe your changes in detail --> | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/admin.rs`
- `crates/api_models/src/lib.rs`
- `crates/api_models/src/payments.rs`
- ... and 1 more files
**2. Database Layer (Queries & Schema)**
- ... | {"pr_number": 6607, "pr_title": "feat(core): api ,domain and diesel model changes for extended authorization", "merged_at": "2025-02-18T16:54:28Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/a... |
<!-- Describe your changes in detail -->
Renamed Connector Name from Bluecode to Calida. Payment Method Type Bluecode remains the same. | 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. Core Business Logic**
- `crates/router/src/core/connector_validation.rs`
**3. External Connector Integ... | {"pr_number": 9712, "pr_title": "fix(connector): [CALIDA] Changed Connector Name From Bluecode to Calida", "merged_at": "2025-10-07T16:39:34Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_model... |
<!-- Describe your changes in detail -->
Currently we are creating the interfaces for CRUD operations for each resource in hyperswitch_domain_models which returns a result of Result<Resource, hyperswitch_domain_models::errors::StorageError> and we are implementing them in storage_impl which is expected to return hyper... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/errors.rs`
- `crates/hyperswitch_domain_models/src/payment_methods.rs`
- `crates/hyperswitch_domain_models/src/payments/payment_at... | {"pr_number": 7537, "pr_title": "refactor(router): make error_type generic in domain_models inorder to avoid conversion of errors in storage_impl", "merged_at": "2025-03-21T14:08:47Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"domain": ["crates/hyperswitch_doma... |
<!-- Describe your changes in detail -->
This PR addresses the clippy lints occurring due to new rust version 1.88.0 | 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/payment_methods.rs`
- ... and 1 more files
**2. Database Layer (Queries & Schema... | {"pr_number": 8498, "pr_title": "chore: address Rust 1.88.0 clippy lints", "merged_at": "2025-07-02T07:17:47Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"api_models": ["crates/api_models/src/admin.rs", "crates/api_models/src/enums.rs", "crates/api_models/... |
<!-- Describe your changes in detail -->
The Sources API for Stripe Bank Transfer (Ach, Multibanco) got deprecated. They are supporting `/v1/payment_intents` now. Removed the pre processing implementations. Added new flow for Stripe Ach, and Multibanco bank transfer through payment_intents api. | 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/flows.rs`
**2. External Connector Integration**
- `crates/router/src/connector/stripe.rs`
- `crates/router/sr... | {"pr_number": 7599, "pr_title": "refactor(connector): [STRIPE] Bank Transfer Api Refactor", "merged_at": "2025-03-27T12:05:05Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core/payments.rs", "c... |
<!-- Describe your changes in detail -->
Previously, there was no support to add filters in global-search, hence only free-text search queries were supported.
Because of this, the following query object was being mandatorily added.
```bash
{
"multi_match": {
"type": "phrase",
... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Other**
- `crates/analytics/src/opensearch.rs`
**Code Patterns Applied:**
- Add conditional logic for feature flags or filtering (1 changes) | {"pr_number": 6685, "pr_title": "fix(opensearch): handle empty free-text query search in global search", "merged_at": "2024-11-29T10:12:34Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"other": ["crates/analytics/src/opensearch.rs"]},... |
<!-- Describe your changes in detail -->
This PR includes
- HubSpot proxy integration for `prod_intent` triggered from the dashboard
- New CRM interface with two implementations: NoCrm and HubspotProxy.
- Includes refactoring to move `http_client send_request` and `client` from the `router` module to `external... | 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/admin.rs`
- `crates/router/src/core/connector_onboarding/paypal.rs`
-... | {"pr_number": 7798, "pr_title": "chore(users): add hubspot tracking to prod intent", "merged_at": "2025-05-13T12:33:04Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/user/dashboard_metadata.rs"], "core_business": ["c... |
This new Kafka Event consume the revenue recovery related events which will be constructed from both `RecoveryPaymentIntent` and `RecoveryPaymentAttempt` in revenue recovery flow. The events form Kafka will be picked up by vector and this be eventually batched and pushed to s3 based on the set config. They file path wi... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/payments.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/types.rs`
**3. Domain Models (Business Logic Types)**
- `crates/hypers... | {"pr_number": 8285, "pr_title": "feat(recovery-events): add revenue recovery topic and vector config to push these events to s3", "merged_at": "2025-07-25T12:00:14Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"api_models": ["crates/a... |
<!-- Describe your changes in detail -->
add merchant_configuration_id in netcetera metadata and make other merchant configurations optional
Main PR - https://github.com/juspay/hyperswitch/pull/7347
Clippy Successful Locally
<img width="906" alt="image" src="https://github.com/user-attachments/assets/85ba726c-d... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payments/helpers.rs`
- `crates/router/src/core/payments/operations/payment_confirm.rs`
**2. External Connector Integration**
- `crates/connector_configs/src/com... | {"pr_number": 7348, "pr_title": "feat(router): add merchant_configuration_id in netcetera metadata and make other merchant configurations optional", "merged_at": "2025-02-21T17:32:29Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["merchant", "user"]}, "hierarchy": {"core_business":... |
<!-- Describe your changes in detail -->
Introduced` /v2/configs` and `/v2/health` endpoints and for v2 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/health_check.rs`
**2. Core Business Logic**
- `crates/router/src/core/health_check.rs`
**3. Configuration Files**
- `crates/router/src/routes/configs.rs... | {"pr_number": 8835, "pr_title": "feat(v2): introduce configs and health endpoints for v2", "merged_at": "2025-08-08T12:56:47Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["connector"]}, "hierarchy": {"api_models": ["crates/api_models/src/health_check.rs"], "core_business": ["crate... |
<!-- Describe your changes in detail -->
In the case of debit routing flow, the routing output (`CallConnectorType`) will include both the connector and its associated card network. In our current implementation, we simply iterate over the connector list and pass the connector. With the updated requirement, we will al... | 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/retry.rs`
- `crates/router/src/core/routing/helpers.rs`
**Code Patterns Applied:**
- Extend existing types with ... | {"pr_number": 8220, "pr_title": "feat(router): add retry support for debit routing", "merged_at": "2025-06-16T11:50:20Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core/payments.rs", "crates/r... |
Cybersource throws error if state length exceeds 20 characters, to fix this this PR addes truncation of state at Hyperswitch end | 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`
**2. Utils**
- `crates/scheduler/src/utils.rs`
**Code Patterns Applied:**
- Implement new functions ... | {"pr_number": 7343, "pr_title": "fix(cybersource): Add truncation logic for administrative area", "merged_at": "2025-02-25T06:44:26Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user", "card"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors... |
This PR introduces below changes around Worldpay connector | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/capture.rs`
- `crates/diesel_models/src/kv.rs`
- `crates/diesel_models/src/payment_attempt.rs`
- ... and 5 more files
**2. Domain Models (Business ... | {"pr_number": 7017, "pr_title": "refactor(schema): add a new column for storing large connector transaction IDs", "merged_at": "2025-02-12T08:49:11Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"database": ["crates/diesel_models/src/cap... |
This PR contains the docker compose file changes for stable release. The PRs included in this file are | To implement this **unknown** feature, you'll need to modify these architectural layers:
**1. Configuration Files**
- `docker-compose.yml`
**2. Other**
- `README.md`
- `docs/one_click_setup.md`
- `docs/try_local_system.md`
- ... and 4 more files
**Code Patterns Applied:**
- Extend existing types with... | {"pr_number": 7894, "pr_title": "chore(docker): docker compose changes for stable release", "merged_at": "2025-04-29T08:00:26Z", "intent": {"feature_type": "unknown", "action": "unknown", "entities": []}, "hierarchy": {"config": ["docker-compose.yml"], "other": ["README.md", "docs/one_click_setup.md", "docs/try_local_s... |
Add new field_type `UserBsbNumber`, `UserBankSortCode` and `UserBankRoutingNumber` for `payment_connector_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/enums.rs`
**2. External Connector Integration**
- `crates/router/src/configs/defaults/payment_connector_required_fields.rs`
**3. Other**
- `api-referenc... | {"pr_number": 6758, "pr_title": "refactor(payment_methods): Add new field_type UserBsbNumber, UserBankSortCode and UserBankRoutingNumber for payment_connector_required_fields", "merged_at": "2024-12-10T11:54:21Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "... |
Adds fix for stopping multiple event locking idempotent logs
Fix on top of previous PR - https://github.com/juspay/hyperswitch/pull/7579
What got missed in the previous PR?
- We should be searching by merchant ID and idempotent event ID instead of searching by merchant ID and event ID
[outgoing.rs](https://github.c... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/query/events.rs`
**2. Core Business Logic**
- `crates/router/src/core/webhooks/outgoing.rs`
**3. Other**
- `crates/router/src/db/events.rs`
... | {"pr_number": 8034, "pr_title": "fix(core): add fix for stopping multiple event locking idempotent logs", "merged_at": "2025-08-05T14:04:00Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["merchant", "user", "webhook"]}, "hierarchy": {"database": ["crates/diesel_models/src/query/eve... |
<!-- Describe your changes in detail -->
So previously we were only inserting in dynamic_routing_stats table, after this change we will be doing an Upsert operation instead of directly performing an insert operation. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/dynamic_routing_stats.rs`
- `crates/diesel_models/src/query/dynamic_routing_stats.rs`
**2. Core Business Logic**
- `crates/router/src/core/routi... | {"pr_number": 7398, "pr_title": "refactor(dynamic_routing): change insert operation to upsert for dynamic_routing_stats", "merged_at": "2025-03-21T12:28:00Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"database": ["crates/diesel_mode... |
<!-- Describe your changes in detail -->
this pr reverts wasm changes for the payload connector that was introduced in https://github.com/juspay/hyperswitch/pull/8597 | 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": 8818, "pr_title": "chore(env): revert wasm changes for payload connector", "merged_at": "2025-08-01T10:36:57Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user", "connector"]}, "hierarchy": {"connectors": ["crates/connector_configs/toml/development.toml", "crates/co... |
<!-- Describe your changes in detail -->
Reverts [https://github.com/juspay/hyperswitch/pull/6403](https://github.com/juspay/hyperswitch/pull/6403)
When global filters are applied on the dashboard, these filters are being sent to both Payment Attempt and Payment Intent related metrics.
Initially backend support wa... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/analytics/payment_intents.rs`
**2. Core Business Logic**
- `crates/analytics/src/payment_intents/core.rs`
**3. Type Definitions**
- `crates/analytics/sr... | {"pr_number": 6492, "pr_title": "feat(analytics): revert remove additional filters from PaymentIntentFilters", "merged_at": "2024-11-08T16:07:08Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"api_models": ["crates/api_models/src/analy... |
<!-- Describe your changes in detail -->
This PR bumps the Minimum Supported Rust Version (MSRV) from Rust 1.80 to 1.85.
Clippy Warning Fixes:
1. Replace repeat().take() with repeat_n() - More concise iterator creation
2. Replace map_or(true, ...) with is_none_or(...) - Modern idiomatic Option handling | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/merchant_connector_account.rs`
**2. Core Business Logic**
- `crates/router/src/core/payment_methods/cards.rs`
- `crates/router/sr... | {"pr_number": 9390, "pr_title": "build: bump MSRV to 1.85.0", "merged_at": "2025-09-16T07:03:28Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/merchant_connector_account.rs"], "core_business": ["crates/router/src/co... |
<!-- Describe your changes in detail -->
Added cypress for ACI.
Following bugs were detected while adding cypress, this PR includes the fix for those as well:
1. `card_network` is required field only for network_token and not for normal card_payment, so made the field optional and populated missing error only fo... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/aci/aci_result_codes.rs`
- `crates/hyperswitch_connectors/src/connectors/aci/transformers.rs`
**2. Tests**
- `cypress-tests/cyp... | {"pr_number": 9502, "pr_title": "feat(connector): [ACI] cypress added", "merged_at": "2025-09-29T09:09:41Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user", "token"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors/aci/aci_result_codes.rs"... |
<!-- Describe your changes in detail -->
Previously we were using payment get to find whether attempt is present in db or not, but for the first invoice webhook there won't be any attempt present in db and recently we added a validation to use payment get only in case of attempt is present.
This PR solves this issue ... | 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`
**3. Domain Models (Business Logic Types)**
- `cra... | {"pr_number": 8393, "pr_title": "feat(revenue_recovery): Invoke attempt list instead of payment get in recovery webhooks flow", "merged_at": "2025-06-20T09:01:12Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "connector"]}, "hierarchy": {"api_models": ["crate... |
add add metadata keys for coingate in ConfigMetadata struct | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/connector_configs/src/connector.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (3 changes) | {"pr_number": 7655, "pr_title": "refactor(connector): [Coingate] add add metadata keys for coingate in ConfigMetadata struct ", "merged_at": "2025-03-28T11:12:41Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "connector"]}, "hierarchy": {"connectors": ["crate... |
<!-- Describe your changes in detail -->
Some connectors, like Adyen, do not support a refund sync API, so we need to rely on refund webhooks for the status. To address this, support for relay refund webhooks is being added.
To support this use case, a new webhook endpoint needs to be introduced for relay webhooks:... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/webhooks.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/query/relay.rs`
**3. Domain Models (Business Logic Types)**
- `crates/... | {"pr_number": 6974, "pr_title": "feat(router): add support for relay refund incoming webhooks", "merged_at": "2025-01-10T08:07:42Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/webhooks.rs"], "... |
<!-- Describe your changes in detail -->
Currently manual retry is enabled through request.
We need to make it profile configurable such that the merchant/SDK doesn't need to send it for each request
- `is_manual_retry` is enabled through profile with this pr
- if it is enabled, it lets merchant do multiple confirm... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/enums.rs`
**2. Core Business Logic**
- `crates/router/src/core/payments.rs`
- `crates/router/src/core/payments/helpers.rs`
- `crates/router/src/core/p... | {"pr_number": 9302, "pr_title": "refactor(core): accept manual retry from profile ", "merged_at": "2025-09-11T14:32:09Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/enums.rs"], "core_business"... |
<!-- Describe your changes in detail -->
Add mandates support for fiuu | 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_create.rs`
**2. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/fiuu.rs`
- `crates/hyperswitch_conn... | {"pr_number": 6361, "pr_title": "feat(connector): [Fiuu] Add support for cards recurring payments", "merged_at": "2024-10-25T13:24:25Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core/payments... |
<!-- Describe your changes in detail -->
Passing shopperReference as "Moto" if paymentChannel is being sent as Moto | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/adyen/transformers.rs` | {"pr_number": 9134, "pr_title": "feat(connector): [ADYEN] Add Support for MOTO Payments", "merged_at": "2025-09-03T13:23:03Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors... |
<!-- Describe your changes in detail -->
- Built an interface for Contract based routing
- Integrated Contract based routing with hyperswitch
- Built new APIs for contract routing config setup
- Refactored some existing dynamic routing code | 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/errors.rs`
- `crates/router/src/core/metr... | {"pr_number": 6761, "pr_title": "feat(routing): Contract based routing integration ", "merged_at": "2025-02-06T14:35:08Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user", "connector"]}, "hierarchy": {"api_models": ["crates/api_models/src/events/routing.rs", "crates/a... |
Add Payu Connector to the cypress test suits
- PayU doesn't support mandates so tests are skipped accordingly
- PayU doesn't support three_ds | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `cypress-tests/cypress/e2e/configs/Payment/Payu.js`
- `cypress-tests/cypress/e2e/configs/Payment/Utils.js`
**Code Patterns Applied:**
- Extend existing types with new fields (565 changes) | {"pr_number": 8567, "pr_title": "ci(cypress): add payu connector", "merged_at": "2025-07-08T12:28:51Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user", "refund"]}, "hierarchy": {"tests": ["cypress-tests/cypress/e2e/configs/Payment/Payu.js", "cypress-tests/cypress/e2e... |
<!-- Describe your changes in detail -->
this pr addresses an issue where hyperswitch sdk did not return required fields resulting in transactions to not happen. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/payment_methods/src/configs/payment_connector_required_fields.rs` | {"pr_number": 8941, "pr_title": "fix(connector): update required fields for xendit", "merged_at": "2025-08-13T15:17:43Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/payment_methods/src/configs/payment_connec... |
1. Added config `skip_status_screen` in payment links to decide whether to skip status screen after payment completion
- If config is true user will be redirected to return url directly
- If config is false,or not passed redirect user to status screen and then to return url `(default flow)`
2. Added config `bac... | 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": 7340, "pr_title": "feat(payments): [Payment links] add configs for payment link", "merged_at": "2025-02-27T13:32:06Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/admin.rs", "crat... |
<!-- Describe your changes in detail -->
Fixes this issue: [https://github.com/juspay/hyperswitch-cloud/issues/7580](https://github.com/juspay/hyperswitch-cloud/issues/7580)
- `first_attempt` filter takes in `true` or `false` as variants.
- But while it is getting applied in the query, it is being converted into a s... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Database Layer (Queries & Schema)**
- `crates/analytics/src/query.rs` | {"pr_number": 6667, "pr_title": "fix(analytics): fix first_attempt filter value parsing for Payments", "merged_at": "2024-11-29T10:11:16Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"database": ["crates/analytics/src/query.rs"]}, "ch... |
<!-- Describe your changes in detail -->
This PR addresses the clippy lints occurring due to new rust version 1.85.0
https://rust-lang.github.io/rust-clippy/master/index.html#useless_conversion | To implement this **validation** feature, you'll need to modify these architectural layers:
**1. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/customer.rs`
- `crates/hyperswitch_domain_models/src/errors/api_error_response.rs`
**2. Core Business Logic**
- `crates/router/src/c... | {"pr_number": 7376, "pr_title": "chore: address Rust 1.85.0 clippy lints", "merged_at": "2025-03-05T11:22:58Z", "intent": {"feature_type": "validation", "action": "add_feature", "entities": []}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/customer.rs", "crates/hyperswitch_domain_models/src/errors/api... |
<!-- Describe your changes in detail -->
Updated open-api spec for Intelligent routing | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `api-reference/intelligent-router-api-reference/contract-routing/fetch-contract-scores-for-an-entity.mdx`
**2. Configuration Files**
- `api-reference/hyperswitch_intelligent_router_open_a... | {"pr_number": 7777, "pr_title": "docs: Updated open-api spec for Intelligent routing", "merged_at": "2025-04-23T14:01:26Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"core_business": ["api-reference/intelligent-router-api-reference/contract-routing/fetch-c... |
Hotfix for https://github.com/juspay/hyperswitch/pull/7072 | 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_initiator.js`
- `crates/router/src/core/payment_link/payment_link_initiate/secure_payment_link_initiator.js`
**Code... | {"pr_number": 7086, "pr_title": "refactor(payment-link): use shouldRemoveBeforeUnloadEvents flag for handling removal of beforeunload events through SDK", "merged_at": "2025-01-22T07:30:59Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"core_business": ["crates/ro... |
<!-- Describe your changes in detail -->
refactor ctp flow to fetch mca_id and get the connector creds instead of connector_name
## 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)?
-->
A... | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/admin.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/business_profile.rs`
**3. Domain Models (Business Logic Types)**
- `crates/hype... | {"pr_number": 6859, "pr_title": "refactor(router): refactor ctp flow to fetch mca_id and get the connector creds instead of connector_name", "merged_at": "2025-01-20T12:02:06Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": [... |
<!-- Describe your changes in detail -->
Template new connection integration `celero` | 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/connector_validation.rs`
**3. External Connector Integration**
... | {"pr_number": 8489, "pr_title": "feat(connector): [Celero] add Connector Template Code", "merged_at": "2025-07-07T11:57:07Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/configs.rs"], "core_business": ["crates/route... |
<!-- Describe your changes in detail -->
This PR resolves the v2 warnings generated in crates common_utils, api_models, hyperswitch_domain_models, diesel_models, kgraph_utils, storage_impl, hyperswitch_connectors, payment_methods. | 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/refunds.rs`
- `crates/api_models/src/tokenization.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_mod... | {"pr_number": 8373, "pr_title": "chore: resolve warnings in v2", "merged_at": "2025-06-22T11:59:35Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "connector"]}, "hierarchy": {"api_models": ["crates/api_models/src/admin.rs", "crates/api_models/src/refunds.rs", "crates/api... |
<!-- Describe your changes in detail -->
This pull request updates the API endpoint configuration in the `dashboard.toml` file. The only change is the `api_url` value, which now points to port 8080 instead of 9000.
Earlier PR for reference : https://github.com/juspay/hyperswitch/pull/9243 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Configuration Files**
- `config/dashboard.toml` | {"pr_number": 9334, "pr_title": "fix: fix api url in dashboard configuration", "merged_at": "2025-09-10T10:38:50Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"config": ["config/dashboard.toml"]}, "change_types": {}, "has_identifier_data": false, "commits_matched... |
<!-- Describe your changes in detail -->
This PR involves the following changes in payment methods v2 code:
- Renames the `payment_method` field to `payment_method_type`, and `payment_method_type` to `payment_method_subtype`. This change affect the database columns itself, the diesel models, the domain models and... | 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/events/payment.rs`
- `crates/api_models/src/payment_methods.rs`
- ... and 1 more files
**2. Database Layer (Querie... | {"pr_number": 6555, "pr_title": "refactor(payment_methods_v2): rename `payment_method` and `payment_method_type` fields and use concrete type for `payment_method_data`", "merged_at": "2024-11-19T16:05:19Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment"]}, "hiera... |
<!-- Describe your changes in detail -->
Currently, `subscription/create`, `/subscription`, and `/subscription/:id/update` accept amount and currency as input parameters(this pr removes that).
Retrieved the amount and currency from the `get_subscription_estimate` from item_price_id. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/subscription.rs`
**2. Core Business Logic**
- `crates/router/src/core/subscription.rs`
- `crates/router/src/core/subscription/invoice_handler.rs`
**Code... | {"pr_number": 9835, "pr_title": "feat(subscription): Add estimate to subscriptions flow and remove amount and currency", "merged_at": "2025-10-16T10:36:29Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_mo... |
Logging x-request-id for failed requests | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `cypress-tests/cypress/e2e/configs/Payment/Stripe.js`
- `cypress-tests/cypress/support/commands.js`
**2. Other**
- `.github/data/cards_info.csv`
- `postman/collection-dir/stripe/Flow Testcases/Ha... | {"pr_number": 7118, "pr_title": "ci(cypress): log `x-request-id` for failed requests", "merged_at": "2025-01-30T18:37:25Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user"]}, "hierarchy": {"tests": ["cypress-tests/cypress/e2e/configs/Payment/Stripe.js", "cypress-tests... |
<!-- Describe your changes in detail -->
add wasm changes for ctp_mastercard connector | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/connector_configs/src/common_config.rs`
- `crates/connector_configs/src/connector.rs`
- `crates/connector_configs/toml/development.toml`
- ... and 1 more files
**... | {"pr_number": 6838, "pr_title": "chore(wasm): add wasm changes for ctp_mastercard connector", "merged_at": "2024-12-17T12:22:34Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["connector", "card"]}, "hierarchy": {"connectors": ["crates/connector_configs/src/common_config.rs", "crate... |
This PR introduces a new variant - `ReconOps` in the `PermissionGroup` enum for deserializing the custom recon related roles in the existing DB.
**Why?**
In `PermissionGroup` enum, `ReconOps` was recently renamed to `ReconOpsManage`. These values are serialized and stored in DB in case custom roles are created. For... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Other**
- `crates/common_enums/src/enums.rs`
- `crates/router/src/services/authorization/info.rs`
- `crates/router/src/services/authorization/permission_groups.rs` | {"pr_number": 6767, "pr_title": "refactor(enums): recon - include ReconOps variant in PermissionsGroup for backwards compatibility with data in DB", "merged_at": "2024-12-10T12:03:38Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"other": ["crates/common_enu... |
added the assertion for connector_mandate_id in mandates and zero auth mandates test cases | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `cypress-tests/cypress/e2e/spec/Payment/00019-MandatesUsingPMID.cy.js`
- `cypress-tests/cypress/support/commands.js`
**Code Patterns Applied:**
- Add conditional logic for feature flags or filtering (4... | {"pr_number": 7474, "pr_title": "ci(cypress): add assertion for `connector_mandate_id`", "merged_at": "2025-03-12T10:01:36Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user", "connector"]}, "hierarchy": {"tests": ["cypress-tests/cypress/e2e/spec/Payment/00019-MandatesUsingPMID.c... |
<!-- Describe your changes in detail -->
- Added `Vault` as a connector type
- Added connector template code for VGS vault | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/enums.rs`
**2. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/configs.rs`
**3. Core Business Logic**
- `crates/router/sr... | {"pr_number": 7814, "pr_title": "feat(router): Add support for Vault in connector_accounts endpoint", "merged_at": "2025-05-15T11:57:04Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "connector"]}, "hierarchy": {"api_models": ["crates/api_models/src/enums.rs"... |
<!-- Describe your changes in detail -->
Currently we have apple pay certificates being stored in the `metadata` as well as `connector_wallet_details` when a merchant connector account is created. During the session call we try to get the certificates from the `connector_wallet_details` if it fails we try to get it fr... | 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`
- `crates/router/src/core/payments/helpers.rs`
**Detailed Identifier Changes:**
Commit 51b6cdfa:
Files to modify:
**crates/rout... | {"pr_number": 6514, "pr_title": "fix(router): get apple pay certificates only from metadata during the session call", "merged_at": "2024-11-08T11:59:23Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router... |
<!-- Describe your changes in detail -->
This PR updates our Rust dependencies to compatible versions (not major version bumps). Additionally, this PR addresses a couple of deprecation warnings in the `time` crate that were arising in our `cards` crate.
## Motivation and Context
<!--
Why is this change required... | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/Cargo.toml`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/Cargo.toml`
**3. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_... | {"pr_number": 8164, "pr_title": "build(deps): bump dependencies to compatible versions", "merged_at": "2025-05-31T21:43:26Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["user", "card"]}, "hierarchy": {"api_models": ["crates/api_models/Cargo.toml"], "database": ["crates/diesel_models/Car... |
<!-- Describe your changes in detail -->
Add UPI Collect support to dummy_connector
1. To simulate a failure case, use: failure@upi
2. To test a successful case, use success@upi. You will be redirected to a screen that simulates the waiting screen.
3. Any other vpa data will result in an invalid VPA data err... | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/router/src/connector/dummyconnector.rs`
- `crates/router/src/connector/dummyconnector/transformers.rs`
- `crates/router/src/routes/dummy_connector/consts.rs`
- ... and 2... | {"pr_number": 8014, "pr_title": "feat(router): [dummy_connector] add upi collect ", "merged_at": "2025-05-15T11:52:15Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/router/src/connector/dummyconnector.rs", "crates/... |
<!-- Describe your changes in detail -->
Refactor network tokenization flow for v2 payment method.
1. moved the network tokenization req, response types from domain to router types, since the types are not generic for Hyperswitch but req and response types of token service.
2. replaced hanging functions to ... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/payment_methods.rs`
**2. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/lib.rs`
- `crates/hyperswitch_domain_models/src/n... | {"pr_number": 7309, "pr_title": "refactor(payment_methods_v2): refactor network tokenization flow for v2", "merged_at": "2025-03-12T22:03:23Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "token"]}, "hierarchy": {"api_models": ["crates/api_models/src/payment_... |
<!-- Describe your changes in detail -->
On successful redirection on CARDS3ds Friction , eps bank redirect, even when fully captured the status is `partially_captured` | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/stripe/transformers.rs`
- `crates/hyperswitch_connectors/src/utils.rs`
**Code Patterns Applied:**
- Implement new functions (1 changes)
... | {"pr_number": 8956, "pr_title": "fix(stripe): partial capture issue when fully captured on redirection flow like card3ds , eps bank redirect", "merged_at": "2025-08-14T11:44:01Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors":... |
Exposed endpoints for auth analytics under profile, merchant and org access levels. | To implement this **authentication** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/analytics/src/auth_events/core.rs`
**2. Other**
- `crates/analytics/src/auth_events/filters.rs`
- `crates/analytics/src/auth_events/metrics.rs`
- `crates/analytics/src/auth... | {"pr_number": 8335, "pr_title": "refactor: exposed auth analytics at merchant,org and profile levels", "merged_at": "2025-07-01T12:31:34Z", "intent": {"feature_type": "authentication", "action": "add_feature", "entities": ["merchant", "user", "order"]}, "hierarchy": {"core_business": ["crates/analytics/src/auth_events/... |
This PR enables processing payment transactions via Adyen using network tokens and NTI | 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/config.example.toml`
- `config/deployments/sandbox.toml`
- `config/development.toml`
- ... and 1 more files | {"pr_number": 8082, "pr_title": "chore: add adyen to network_tokenization_supported_connectors list across different environments", "merged_at": "2025-05-30T14:10:07Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "token"]}, "hierarchy": {"tests": ["config/dep... |
add client_secret auth auth type for list_blocked_payment_methods | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/blocklist.rs`
**2. Other**
- `api-reference/v1/openapi_spec_v1.json`
- `api-reference/v2/openapi_spec_v2.json`
- `crates/router/src/routes/blocklist.r... | {"pr_number": 9475, "pr_title": "feat(core): add client_auth auth type for list_blocked_payment_methods", "merged_at": "2025-09-22T18:44:08Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "card"]}, "hierarchy": {"api_models": ["crates/api_models/src/blocklist.rs"], "other... |
1. This commit changes how the client secret is generated
2. Change how client secret is made in Create Payment Intent
Old
`{Payment_id}_secret_{Secret}` `eg : pay_U42c409qyHwOkWo3vK60_secret_el9ksDkiB8hi6j9N78yo`
New
`cs_{Secret}` `eg: cs_0195d2be95ba7ef1a05066e163295562`
3. Client secret ... | 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_intent.rs`
- `crates/diesel_models/src/schema_v2.rs`
**3. Domain Mod... | {"pr_number": 7648, "pr_title": "feat: remove client_secret from payment_intent and update related code", "merged_at": "2025-04-10T13:34:30Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/payments.rs"... |
<!-- Describe your changes in detail -->
disable sprite.
closes #7184 | 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 (2 changes) | {"pr_number": 7183, "pr_title": "ci: disable stripe in cypress", "merged_at": "2025-02-04T10:41:55Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"tests": [".github/workflows/cypress-tests-runner.yml"]}, "change_types": {"fields_added": 2}, "has_identifier_data": ... |
<!-- Describe your changes in detail -->
In customer payment method list api, card scheme and card network are showing different value for co-branded card it they are saved with both the network, to fix this issue, both these fields are now fetching the data from the card locker
Note: This PR is hotfix against [#68... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/payment_method.rs`
**2. Core Business Logic**
- `crates/router/src/core/payment_methods/cards.rs`
- `crates/router/src/core/payments/tokenizatio... | {"pr_number": 6867, "pr_title": "fix(payment_methods): card_network and card_scheme should be consistent", "merged_at": "2024-12-18T07:42:26Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "user"]}, "hierarchy": {"database": ["crates/diesel_models/src/payment_... |
<!-- Describe your changes in detail -->
Added GooglePay Payment Method in Fiserv Connector. Added the Connector Level Decryption Flow. The Hyperswitch end decryption flow of Fiserv still remains undone. | 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": 8658, "pr_title": "feat(connector): [FISERV] Added GooglePay Payment Method - Connector Decryption Flow", "merged_at": "2025-07-29T08:13:32Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/connect... |
# Migrate Nix Configuration to rust-flake | To implement this **connector_integration** feature, you'll need to modify these architectural layers:
**1. Other**
- `.gitignore`
- `flake.lock`
- `flake.nix`
- ... and 4 more files | {"pr_number": 8503, "pr_title": "refactor(nix): Migrate from cargo2nix to rust-flake", "merged_at": "2025-07-15T08:20:23Z", "intent": {"feature_type": "connector_integration", "action": "add_feature", "entities": []}, "hierarchy": {"other": [".gitignore", "flake.lock", "flake.nix", "nix/modules/flake/devshell.nix", "ni... |
- Integrate proxy_payments api to process tracker passive_churn workflow, to initiate a MIT payment via PT.
- This PR also includes another api integration to the same workflow , the update_payments api to update the `payment_transmission` and the active_attempt_id, when the payment is a retryable payment | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/payments.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/types.rs`
**3. Domain Models (Business Logic Types)**
- `crates/hypers... | {"pr_number": 7480, "pr_title": "refactor(process_tracker): Integrate proxy_payments api to process tracker workflow", "merged_at": "2025-03-17T05:23:14Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user"]}, "hierarchy": {"api_models": ["crates/api_models/src/payments.... |
Implement 3ds decision manager flow for V2 and use it in payments flows. | 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`
**3. Domain Models (Business Logic Types)**
- `cra... | {"pr_number": 7089, "pr_title": "feat(core): 3ds decision manager for v2", "merged_at": "2025-02-12T14:07:35Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/payments.rs"], "database": ["crates/d... |
Add newer payment methods for `multisafepay` connector
- Trustly
- WeChatPay
- Alipay | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/multisafepay.rs`
- `crates/hyperswitch_connectors/src/connectors/multisafepay/transformers.rs`
**2. Tests**
- `config/deployments/int... | {"pr_number": 8465, "pr_title": "feat(connector): `multisafepay` added payment methods | TRUSTLY | WeChatpay | Alipay", "merged_at": "2025-07-02T07:12:31Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_c... |
<!-- Describe your changes in detail -->
Fixed ideal giropay country currency config | 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/production.toml`
- `config/deplo... | {"pr_number": 9552, "pr_title": "Fix: Ideal Giropay Country Currency Config", "merged_at": "2025-09-29T09:09:41Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"tests": ["config/deployments/integration_test.toml", "loadtest/config/development.toml"], "config": ["co... |
<!-- Describe your changes in detail -->
This PR
1. Adds workflows to sync dispute with the connector to add new records
2. Introduce force_sync in the current dispute-sync API to update the dispute status from connector
3. Integrate dispute list, dispute sync, accept liability, submit evidence, file upload and fi... | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/admin.rs`
- `crates/api_models/src/disputes.rs`
- `crates/api_models/src/events/dispute.rs`
- ... and 2 more files
**2. Database Layer (Queries & Schema)**
... | {"pr_number": 8830, "pr_title": "feat(router): [worldpayvantiv] add dispute list sync and implement dispute", "merged_at": "2025-08-06T10:14:56Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"api_models": ["crates/api_models/src/admin.rs", "... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.