prompt stringlengths 6 90.9k | response stringlengths 121 18.6k | metadata stringlengths 314 42.3k |
|---|---|---|
This PR fixes SEPA payout routing failures by updating database configurations to use `sepa_bank_transfer` instead of `sepa` for payout flows. This was missed as part of the refactoring in https://github.com/juspay/hyperswitch/pull/7575 | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. Other**
- `crates/euclid/src/enums.rs` | {"pr_number": 8765, "pr_title": "fix(wasm): invalid variant for payout bank transfers", "merged_at": "2025-08-01T13:34:38Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"other": ["crates/euclid/src/enums.rs"]}, "change_types": {}, "has_i... |
Novalnet expects decoded wallet token for applepay. Previously encoded wallet token was being sent. | 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": 6503, "pr_title": "fix(connector): [Novalnet] Send decoded wallet token to applepay", "merged_at": "2024-11-08T13:05:27Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["token"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors/novalnet/transf... |
<!-- Describe your changes in detail -->
Moving connectors from `crates/router` to `crates/hyperswitch_connectors`
1. adyenplatform
2. ebanx
3. gpayments
4. netcetera
5. plaid
issue: https://github.com/juspay/hyperswitch/issues/7916 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/admin.rs`
- `crates/router/src/core/payments/flows.rs`
**2. External Connector Integration**
- `crates/hyperswitch_connectors/Cargo.toml`
- `crates/hyperswit... | {"pr_number": 7913, "pr_title": "Refactor(connector): Migrate [AdyenPlatform, Ebanx, GPayments, Netcetera, Plaid] from crates/router to crates/hyperswitch_connectors", "merged_at": "2025-05-06T07:38:22Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"... |
<!-- Describe your changes in detail -->
Added connector specifications for Archipel, Bankofamerica, Boku, Chargebee, Cryptopay, Cybersource, Datatrans, Nmi, Noon, Payeezy, Payme, Paypal, Plaid, Stripebilling, Trustpay. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/archipel.rs`
- `crates/hyperswitch_connectors/src/connectors/bamboraapac.rs`
- `crates/hyperswitch_connectors/src/connectors/ban... | {"pr_number": 8797, "pr_title": "feat(connector): Add Connector Specifications", "merged_at": "2025-09-01T12:44:33Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "refund"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors/archipel.r... |
<!-- Describe your changes in detail -->
This PR introduces a new endpoint that handles payments create intent v2 and confirm intent v2 steps. Note that the API contract is not finalized and is possibly subject to change.
Additionally, the endpoint can also call the setup intent flow, if the order amount is zero.... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/events/payment.rs`
- `crates/api_models/src/payments.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/payment_attempt.rs`
- `c... | {"pr_number": 7106, "pr_title": "feat(payments_v2): implement create and confirm intent flow", "merged_at": "2025-02-05T14:59:36Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/events/payment.rs... |
<!-- Describe your changes in detail -->
This add the filtering and logic for required fields in payment_mehtod list of payment's v2. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/payments.rs`
**2. Core Business Logic**
- `crates/router/src/core/payments/payment_methods.rs`
**3. Other**
- `api-reference/v2/openapi_spec_v2.json`
*... | {"pr_number": 8317, "pr_title": "feat(payments_v2): add logic to render required_fields in response of payment_method list", "merged_at": "2025-06-17T07:12:21Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "user"]}, "hierarchy": {"api_models": ["crates/api_mo... |
<!-- Describe your changes in detail -->
This pull request introduces `merchant_category_code` field in the business profile. This is the four-digit code assigned based on business type to determine processing fees and risk level. This code can be used to make various decision during a payment flow. One such use case ... | 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/open_router.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/business_profile.rs`
- `crates... | {"pr_number": 8296, "pr_title": "feat(router): add `merchant_category_code` in business profile", "merged_at": "2025-06-12T11:02:04Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/admin.rs", "cr... |
<!-- Describe your changes in detail -->
Added ThreeDs server integration template pr
## Checklist
<!-- Put an `x` in the boxes that apply -->
- [x] I formatted the code `cargo +nightly fmt --all`
- [x] I addressed lints thrown by `cargo clippy`
- [x] I reviewed the submitted code
- [ ] I added unit tests ... | To implement this **connector_integration** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/admin.rs`
- `crates/router/src/core/payments/connector_integration_v2_impls.rs`
- `crates/router/src/core/payments/flows.rs`
**2. External Connector Int... | {"pr_number": 7424, "pr_title": "feat(connector): Added ThreeDs server integration template pr", "merged_at": "2025-03-06T10:48:26Z", "intent": {"feature_type": "connector_integration", "action": "add_feature", "entities": []}, "hierarchy": {"core_business": ["crates/router/src/core/admin.rs", "crates/router/src/core/p... |
<!-- Describe your changes in detail -->
this pr addresses below mentioned nordea specific issues:
- fixes connector metadata
- fixes refunds, void and manual capture | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/connector_configs/src/connector.rs`
- `crates/connector_configs/toml/development.toml`
- `crates/connector_configs/toml/production.toml`
- ... and 3 more files
**... | {"pr_number": 9041, "pr_title": "fix(connector): [nordea] pass valid connector metadata fields and properly throw error unsupported flows", "merged_at": "2025-08-26T07:17:56Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "user"]}, "hierarchy": {"connectors": ... |
<!-- Describe your changes in detail -->
This pull request refactors how the default fallback routing configuration is updated when a merchant connector account is modified. Instead of calling the old helper function, the logic is now handled through a new `MerchantDefaultConfigUpdate` struct with methods that more ex... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/admin.rs`
- `crates/router/src/core/routing/helpers.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (6 changes)
- Add conditional logic for ... | {"pr_number": 9729, "pr_title": "fix(routing): cache redaction on updation of mca", "merged_at": "2025-10-08T08:06:23Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["merchant", "connector"]}, "hierarchy": {"core_business": ["crates/router/src/core/admin.rs", "crates/router/src/core... |
<!-- Describe your changes in detail -->
Add tokenization support for proxy and update the route for proxy to `/v2/proxy` | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/proxy.rs`
- `crates/router/src/core/proxy/utils.rs`
**2. Utils**
- `crates/common_utils/src/id_type/global_id/token.rs`
**3. Other**
- `crates/router/src/ro... | {"pr_number": 8530, "pr_title": "feat(router): Add tokenization support for proxy and update the route for proxy", "merged_at": "2025-08-08T13:19:54Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/sr... |
<!-- Describe your changes in detail -->
This PR does amount conversion changes for Riskified Connector and it accepts the 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/riskified.rs`
- `crates/router/src/connector/riskified/transformers/api.rs`
**2. Type Definitions**
- `crates/router/src/types/api/fraud_check.r... | {"pr_number": 6359, "pr_title": " refactor(connector): add amount conversion framework to Riskified ", "merged_at": "2024-11-26T09:14:52Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/router/src/connector/ris... |
<!-- Describe your changes in detail -->
* moved merchant_account, business_profile and merchant_connector_account under accounts_schema.
* added `id` as varchar in business_profile and merchant_connector_account and added logic to populate it during creation in v1 itself.
* added migration to create index for every... | 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/merchant_connector_account.rs`
- `crates/diesel_models/src/schema.rs`
- ... and 1 more files
... | {"pr_number": 7626, "pr_title": "refactor(accounts): move accounts related tables to accounts schema", "merged_at": "2025-04-03T16:25:14Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["merchant", "user", "connector"]}, "hierarchy": {"database": ["crates/diesel_models/src/business_p... |
<!-- 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 | 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": 9857, "pr_title": "feat(payouts): apple pay decrypt payout", "merged_at": "2025-10-16T08:06:22Z", "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 -->
Context:
Redsys 3DS requires full card details, including the CVC, during the complete authorize call that finalizes the payment.
Problem:
Previously, Redsys 3DS payments using saved cards were failing with a `CVC not provided` error. This happened because:
1. For saved... | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payments/helpers.rs`
**Code Patterns Applied:**
- Add conditional logic for feature flags or filtering (1 changes) | {"pr_number": 7773, "pr_title": "fix(router): conditionally store saved cards with cvc in temp locker based on config", "merged_at": "2025-04-30T12:05:16Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src... |
<!-- Describe your changes in detail -->
Add support for hyperswitch side decrypt flow for applepay in Nuvei
- Hyperswitch can decrypt applepay token without involvement of connector if it has Apple pay processing certificate and private key.
# how did i test
Payment Request
```json
{
"amount": 650... | 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": 9431, "pr_title": "feat(nuvei): applepay decrypt at hyperswitch flow", "merged_at": "2025-09-19T12:22:52Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/connector_configs/toml/development.toml", ... |
<!-- Describe your changes in detail -->
add confirm flag in kafka payment intent events
Main PR - https://github.com/juspay/hyperswitch/pull/8432 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/payments/payment_intent.rs`
**2. Core Business Logic**
- `crates/router/src/core/payments/operations/payment_confirm.rs`
- `crate... | {"pr_number": 8444, "pr_title": "feat(router): add confirm flag in kafka payment intent events", "merged_at": "2025-06-24T15:32:26Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/payments/payment_intent.rs"]... |
<!-- Describe your changes in detail -->
Adds support of consuming the incoming webhook and verifying it. | 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/common_enums/src/connector_enums.rs`
- `crates/connector_configs/src/connector.rs`
- `crates/hypers... | {"pr_number": 7439, "pr_title": "feat(connector): Recurly incoming webhook support", "merged_at": "2025-03-17T10:06:06Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user", "webhook"]}, "hierarchy": {"core_business": ["crates/router/src/core/admin.rs"], "connectors": ["... |
The current implementation of insertion of an event in `event` table does not handle the case where multiple requests with the same idempotent_event_id might be processed concurrently, leading to multiple unique constraint violation errors in the database.
This was reported by a merchant who was facing high volumes ... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/webhooks/outgoing.rs`
- `crates/router/src/core/webhooks/utils.rs`
**2. Tests**
- `config/deployments/integration_test.toml`
- `loadtest/config/development.t... | {"pr_number": 7579, "pr_title": "feat(core): add redis lock during insertion of event in event table during initial attempt of outgoing webhook delivery", "merged_at": "2025-04-28T13:45:22Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["merchant", "webhook"]}, "hierarchy": {"core_b... |
<!-- Describe your changes in detail -->
This implementation adds comprehensive V2 API testing for payment void/cancel operations across different payment states. The feature introduces a new Cypress test suite that validates three critical scenarios: successfully voiding a payment in the requires_capture state `after... | 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/cypress/e2e/configs/Payment/Commons.js`
- `cypress-tests-v2/cypress/e2e/configs/Payment/Utils.js`
- ... and 6 more files
**Code Pa... | {"pr_number": 9646, "pr_title": "test(cypress): add cypress tests for void payment in v2", "merged_at": "2025-10-07T17:28:46Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user"]}, "hierarchy": {"tests": [".github/workflows/cypress-tests-runner.yml", "cypress-tests-v2/c... |
<!-- Describe your changes in detail -->
Ref [PR](https://github.com/juspay/hyperswitch/pull/8685) | 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": 8686, "pr_title": "fix(connector): [AUTHORIZEDOTNET] Added Invoice Number Fix", "merged_at": "2025-07-18T09:31:52Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors/authorizedotnet/transformers... |
<!-- Describe your changes in detail -->
Currently in invites we don't check if user exists across entities.
This will be a problem when inviting a user with higher entity from different lineage.
This PR fixes it.
Main PR: #6677 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/user.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (5 changes)
- Add conditional logic for feature flags or filtering (1 changes) | {"pr_number": 6680, "pr_title": "fix(users): Check lineage across entities in invite", "merged_at": "2024-11-27T14:40:31Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["merchant", "user"]}, "hierarchy": {"core_business": ["crates/router/src/core/user.rs"]}, "change_types": {"fields... |
<!-- Describe your changes in detail -->
this pr adds `xof` currency to cybersource cards. | 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": 8799, "pr_title": "chore: `xof` currency to cybersource cards", "merged_at": "2025-08-01T08:08:42Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"tests": ["config/deployments/integration_test.toml", "loadtest/config/d... |
Addition details for Paze Wallet
<img width="569" alt="image" src="https://github.com/user-attachments/assets/fc751564-b9ba-464c-b094-f4bb01bb8124">
<!-- Describe your changes in detail --> | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/connector_configs/src/connector.rs`
- `crates/connector_configs/toml/development.toml`
**Code Patterns Applied:**
- Extend existing types with new fields (1 changes) | {"pr_number": 6710, "pr_title": "chore: wasm paze additional details", "merged_at": "2024-12-04T09:54:38Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"connectors": ["crates/connector_configs/src/connector.rs", "crates/connector_configs/toml/development.tom... |
Described in #6316 point `#6` | 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/api_error_response.rs`
**2. Core Business Logic**
- `crates/router/src/core/payments/operations/payment_response.rs`
**3. Ex... | {"pr_number": 6479, "pr_title": "feat(connector): [worldpay] add support for mandates", "merged_at": "2024-11-08T13:37:39Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/errors/api_er... |
<!-- Describe your changes in detail -->
This PR will enable JWT to be used for update config for success based routing route, previously it was only admin api key. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Other**
- `api-reference/openapi_spec.json`
- `crates/openapi/src/openapi.rs`
- `crates/openapi/src/routes/routing.rs`
- ... and 1 more files
**Code Patterns Applied:**
- Implement new functions (1 changes... | {"pr_number": 6785, "pr_title": "refactor(dynamic_routing): update the authentication for update config to include JWT type", "merged_at": "2024-12-18T09:24:15Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "token", "card"]}, "hierarchy": {"other": ["api-reference/openap... |
<!-- Describe your changes in detail -->
This PR adds the routing rule evaluation endpoint to Hyperswitch, which calls the decision engine
Added `evaluate_routing_rule` function, which calls `send_decision_engine_request` with `ApiKeyAuth` auth | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payments/routing/utils.rs`
**2. Type Definitions**
- `crates/router_env/src/logger/types.rs`
**3. Utils**
- `crates/router/src/routes/lock_utils.rs`
**4. Othe... | {"pr_number": 8656, "pr_title": "feat(routing): Add routing evaluation rule endpoint and related flow", "merged_at": "2025-07-18T08:48:13Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"core_business": ["crates/router/src/core/payments... |
Reverts part of juspay/hyperswitch#6510 | To implement this **unknown** feature, you'll need to modify these architectural layers:
**1. Other**
- `crates/router/src/routes/app.rs` | {"pr_number": 6712, "pr_title": "fix(openapi): Revert Standardise API naming scheme for V2 Dashboard Changes", "merged_at": "2024-12-02T09:29:35Z", "intent": {"feature_type": "unknown", "action": "unknown", "entities": []}, "hierarchy": {"other": ["crates/router/src/routes/app.rs"]}, "change_types": {}, "has_identifier... |
Described in #6316 | 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 5 more files
*... | {"pr_number": 6317, "pr_title": "refactor(connector): [WorldPay] migrate from modular to standard payment APIs", "merged_at": "2024-10-21T10:24:32Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/connector_conf... |
<!-- Describe your changes in detail -->
This pull request enhances how co-badged card information is handled, especially around identifying and propagating the card's "signature network" and whether the card issuer is regulated.
* Extended the `AdditionalCardInfo` struct to include new fields: `is_regulated` (ind... | 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`
- `crates/api_models/src/open_router.rs`
- `crates/api_models/src/payment_methods.rs`
- ... and 1 more files
**2. Domain Models... | {"pr_number": 8891, "pr_title": "refactor(router): add support to store `signature_network` and `is_regulated` in payment attempts", "merged_at": "2025-08-13T12:03:51Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["c... |
<!-- Describe your changes in detail -->
We are reverting the filtering of response for payment and payout processors.
So this works as follows:
If Payment's route is hit all the PaymentProcessors will be listed like PayoutConnectors etc. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/routing.rs`
**Code Patterns Applied:**
- Modify database queries (1 changes)
**Detailed Identifier Changes:**
Commit 66e507e0:
Files to modify:
**crates/router/s... | {"pr_number": 7556, "pr_title": "refactor(core): Revert \"filter default routing config response based on connector type\"", "merged_at": "2025-03-18T15:06:40Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "connector", "token"]}, "hierarchy": {"core_business": ["crates/r... |
<!-- Describe your changes in detail -->
This PR addresses the clippy lints occurring due to new rust version 1.89.0 | 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/user.rs`
**2. Other**
- `crates/euclid_macros/src/inner/knowledge.rs` | {"pr_number": 8873, "pr_title": "chore: address Rust 1.89.0 clippy lints", "merged_at": "2025-08-13T10:07:23Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"core_business": ["crates/router/src/core/payments.rs", "crates/router/src/core/user.rs"], "other": ["... |
- Add support where merchant can update the payment metadata after the payment has been authorized.
- Introduce a new api \payments\:id\update_metadata
- Only the metadata field can be updated, which is a key value pair.
- This api can do a connector call just using the metadata field.
- After this call is success... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/events/payment.rs`
- `crates/api_models/src/payments.rs`
**2. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/payments.rs`... | {"pr_number": 7776, "pr_title": "feat(core): Add support for updating metadata after payment has been authorized", "merged_at": "2025-04-15T07:39:02Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/s... |
<!-- Describe your changes in detail -->
- previously post capture void in nuvei was resulting in `partially_captured` response in hyperswitch, Ideally it should give `cancelled_post_capture`.
- Cause we were passing `Voided` payment instead of `VoidedPostCharge` . Ideally it should move to
payment Request
```... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/nuvei/transformers.rs`
**Code Patterns Applied:**
- Implement new functions (2 changes)
- Extend existing types with new fields (3 ch... | {"pr_number": 9292, "pr_title": "fix(Nuvei): post capture void , proper mapping for nuvei", "merged_at": "2025-09-08T16:15:31Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connecto... |
<!-- Describe your changes in detail -->
Audit trail for SR based Routing | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/analytics.rs`
- `crates/api_models/src/analytics/routing_events.rs`
- `crates/api_models/src/events.rs`
- ... and 1 more files
**2. Core Business Logi... | {"pr_number": 8188, "pr_title": "feat(routing): Add audit trail for routing", "merged_at": "2025-06-02T21:25:35Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/analytics.rs", "crates/api_models/... |
Connector Template code | 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": 9450, "pr_title": "feat(connector): [Gigadat] Connector Template code", "merged_at": "2025-09-22T18:39:33Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["connector"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/connector_endpoints.rs"], "connectors... |
Changed locale case to snakecase for `const locale` object for payment_link. Currently the object has keys in snake case but since Accept-Language is not passed in snakecase, payment_link is not able to render the translated data but shows data in english (fallback language). | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payment_link/locale.js`
**Code Patterns Applied:**
- Extend existing types with new fields (3 changes) | {"pr_number": 6789, "pr_title": "feat(payments): [Payment links] Add locale case fix", "merged_at": "2024-12-10T14:04:52Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core/payment_link/locale.j... |
<!-- Describe your changes in detail -->
/relay is a api that will be used to just forward the request sent my merchant without performing any application logic on it. In this pr the changes is particular to support the refunds for the payments that was directly performed with the connector (example stripe) with out h... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/lib.rs`
- `crates/api_models/src/relay.rs`
**2. Utils**
- `crates/common_utils/src/id_type.rs`
- `crates/common_utils/src/id_type/relay.rs`
**3. Othe... | {"pr_number": 6870, "pr_title": "feat(router): add /relay endpoint", "merged_at": "2024-12-20T14:34:47Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"api_models": ["crates/api_models/src/lib.rs", "crates/api_models/src/relay.rs"], "ut... |
Added Dynamic field Test cases for cybersource connector | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `cypress-tests/cypress/e2e/PaymentMethodListTest/00000-PaymentMethodListTests.cy.js`
- `cypress-tests/cypress/e2e/PaymentMethodListUtils/Commons.js`
- `cypress-tests/cypress/e2e/PaymentTest/00026-Dyn... | {"pr_number": 6703, "pr_title": "ci(cypress): Add Dynamic fields Test Cases", "merged_at": "2024-12-04T16:29:10Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user", "connector"]}, "hierarchy": {"tests": ["cypress-tests/cypress/e2e/PaymentMethodListTest/00000-PaymentMethodListTest... |
<!-- 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": 7647, "pr_title": "feat(docker): add webhook notifiers for installation tracking", "merged_at": "2025-04-09T09:33:33Z", "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 -->
This PR updates Cypress documentation as it was outdated that resulted in confusion among users of Cypress, we'll be stop sourcing the script. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `.github/workflows/cypress-tests-runner.yml`
- `cypress-tests/readme.md`
**Code Patterns Applied:**
- Extend existing types with new fields (3 changes)
- Add conditional logic for feature flags or filt... | {"pr_number": 6415, "pr_title": "docs(cypress): refactor cypress documentation for more clarity", "merged_at": "2024-10-24T08:59:24Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"tests": [".github/workflows/cypress-tests-runner.yml", "cypress-tests/readme.m... |
<!-- Describe your changes in detail -->
Enhancements for `archipel` Cypress Tests. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `cypress-tests/cypress/e2e/configs/Payment/Archipel.js`
- `cypress-tests/cypress/e2e/configs/Payment/Utils.js`
**Code Patterns Applied:**
- Extend existing types with new fields (104 changes) | {"pr_number": 8189, "pr_title": "ci(cypress): fix `archipel` cypress test cases", "merged_at": "2025-07-23T16:24:53Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user", "connector"]}, "hierarchy": {"tests": ["cypress-tests/cypress/e2e/configs/Payment/Archipel.js", "cypress-tests/... |
<!-- Describe your changes in detail -->
This pull request extends the analytics system to support two new payment attributes: `signature_network` and `is_issuer_regulated`, and introduces a new field, `is_debit_routed`, across the payments analytics pipeline. The changes ensure these fields are included in all releva... | 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. Core Business Logic**
- `crates/analytics/src/payments/core.rs`
**3. External Connector Integration**
- `crates/analytics/sr... | {"pr_number": 9033, "pr_title": "feat(router): add support to use signature_network and is_issuer_regulated as filters", "merged_at": "2025-08-22T14:12:31Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "connector"]}, "hierarchy": {"api_models": ["crates/api_m... |
<!-- Describe your changes in detail -->
This PR will add force 2fa environment variable. When enabled it will force users to complete 2FA to access the control center. | 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. Core Business Logic**
- `crates/router/src/core/user.rs`
**3. Tests**
- `config/deployments/integration_test.toml`
- `loadtest/config/d... | {"pr_number": 6466, "pr_title": "feat(users): Add `force_two_factor_auth` environment variable", "merged_at": "2024-11-05T14:59:29Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"api_models": ["crates/api_models/src/user.rs"], "core_business": ["crates/route... |
Hotfix pr https://github.com/juspay/hyperswitch/pull/7300
`cargo clippy` tested locally
https://github.com/user-attachments/assets/2f2ed42c-b9d4-4504-baef-00ba05b51e3c | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/utils.rs`
**2. Other**
- `crates/common_enums/src/enums.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (42 changes)
... | {"pr_number": 7311, "pr_title": "refactor(utils): match string for state with SDK's naming convention", "merged_at": "2025-02-19T13:11:40Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/utils.rs"], "other": ["... |
<!-- Describe your changes in detail -->
Authentication with Netcetera was successful, but authorization with Cybersource failed with the below error:
`Declined - The request is missing one or more fields, detailed_error_information: paymentInformation.card.typeSelectionIndicator : MISSING_FIELD`
Need to send card... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/cybersource/transformers.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (2 changes)
**Detailed Identifier Ch... | {"pr_number": 7828, "pr_title": "fix(connector): [Cybersource] send type selection indicator for co-batch cards", "merged_at": "2025-04-17T12:11:05Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_c... |
<!-- Describe your changes in detail -->
removed currencies CUC,STD,VEF from sandbox config, for SHIFT4 and WORLDLINE | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Configuration Files**
- `config/deployments/sandbox.toml` | {"pr_number": 7572, "pr_title": "fix(connector): [SHIFT4, WORLDLINE] removed currencies CUC, STD, VEF from sandbox configs", "merged_at": "2025-03-20T14:39:32Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"config": ["config/deployments/sandbox.toml"]}, "change_ty... |
This PR includes
- Use of global interface for user roles table
- Add tenant_id column in user_roles table
- Handle user_role insertions with correct value for tenant_id
- Auth Changes: Token validation, token issued in one tenancy should not be valid in other | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/schema.rs`
- `crates/diesel_models/src/schema_v2.rs`
- `crates/diesel_models/src/user_role.rs`
**2. Core Business Logic**
- `crates/router/sr... | {"pr_number": 6458, "pr_title": "feat(users): add global support in user roles", "merged_at": "2024-11-13T07:24:13Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user", "token"]}, "hierarchy": {"database": ["crates/diesel_models/src/schema.rs", "crates/diesel_models/src/schema_v2.... |
<!-- Describe your changes in detail -->
- Currently, the `limit by` clause in query_builder of `failure_reasons` metric has only `connector` hardcoded.
- Changed this behaviour to enable dynamic addition of `group` by fields to the `limit by` clause as well. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Other**
- `crates/analytics/src/payments/metrics/sessionized_metrics/failure_reasons.rs`
**Code Patterns Applied:**
- Modify database queries (1 changes) | {"pr_number": 6462, "pr_title": "fix(analytics): add dynamic limit by clause in failure reasons metric query", "merged_at": "2024-11-04T14:51:58Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"other": ["crates/analytics/src/payments/me... |
<!-- Describe your changes in detail -->
This pull request introduces a new feature for retrieving dynamic routing volume split configurations and includes related updates across multiple files. The changes primarily focus on adding a new API endpoint, defining associated data structures, and integrating the functiona... | 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/routing.rs`
**3. Tests**
- `cypress-test... | {"pr_number": 8114, "pr_title": "feat(dynamic_routing): add get api for dynamic routing volume split", "merged_at": "2025-05-27T17:51:02Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/events/routing.rs", "crates/api_... |
<!-- Describe your changes in detail -->
Update metadata gives `500` error for other connectors than stripe
Change this to `400` | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payments/flows/update_metadata_flow.rs`
- `crates/router/src/core/payments/transformers.rs`
**Code Patterns Applied:**
- Implement new functions (1 changes)
- Exte... | {"pr_number": 7984, "pr_title": "fix(update_metadata): Update Metadata for any connectors other than stripe gives 500 error", "merged_at": "2025-05-08T11:07:30Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "order", "connector"]}, "hierarchy": {"core_business": ["crates/... |
<!-- Describe your changes in detail -->
This PR:
- Adds support for webhooks to Payload connector. The connector does not support source verification.
- Address Cypress comments that was asked in #8545.
- Fixes setup mandate not throwing `501` | 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. External Connector Integration**
- `crates/connector_configs/toml/development.toml`
- `crates/connector_configs/toml/production.toml`
... | {"pr_number": 8558, "pr_title": "feat(connector): [payload] add webhook support", "merged_at": "2025-07-11T12:58:37Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/webhooks.rs"], "connectors": [... |
handle 5xx error for Volt payments webhooks
In the Volt connector for payment webhooks in production, a field is occasionally changing. The `payment` field sometimes comes as `id` instead, with the same expected value as `payment`. Since it’s coming as `id` rather than `payment`, the webhook body deserialization is ... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/volt/transformers.rs` | {"pr_number": 6576, "pr_title": "fix(connector): [Volt] handle 5xx error for Volt payments webhooks", "merged_at": "2024-11-20T12:21:57Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "user"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/co... |
<!-- Describe your changes in detail -->
Added api-key auth for routing APIs
Earlier, all routing endpoints were only JWT auth based for release build and (api-key + JWT) for local development build. Have removed the feature flag based distinction and refactored auth for all routing endpoints to be (api-key + JWT) fo... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/routing/helpers.rs`
**2. Other**
- `crates/router/src/routes/routing.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (3 changes)
**Detaile... | {"pr_number": 8083, "pr_title": "refactor: Added api-key auth for routing APIs", "merged_at": "2025-05-21T14:51:27Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["merchant", "connector", "token"]}, "hierarchy": {"core_business": ["crates/router/src/core/routing/helpers.rs"], "other... |
- Hotfix for - https://github.com/juspay/hyperswitch/pull/7776
- Add support where merchant can update the payment metadata after the payment has been authorized.
- Introduce a new api \payments\:id\update_metadata
- Only the metadata field can be updated, which is a key value pair.
- This api can do a connector c... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/events/payment.rs`
- `crates/api_models/src/payments.rs`
**2. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/payments.rs`... | {"pr_number": 7811, "pr_title": "feat(core): Add support for updating metadata after payment has been authorized", "merged_at": "2025-04-15T09:26:18Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/s... |
- 5xx error for Volt Payment Sync, for PaymentStatus. We received a new status `UNKNOWN`.
- Adding `UNKNOWN` status to Psync Payment Status and mapping it with previous status to avoid deserialization error. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/volt/transformers.rs`
**Code Patterns Applied:**
- Implement new functions (1 changes) | {"pr_number": 6846, "pr_title": "fix(connector): 5xx error for Volt Payment Sync", "merged_at": "2024-12-17T11:00:48Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors/volt/t... |
This PR contains below changes
1. Map billing's first and last name to card holder's name
2. Preserve card holder's name across different data models (API / domain / vault) | 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": 6791, "pr_title": "fix(core): payments - map billing first and last name to card holder name", "merged_at": "2024-12-10T16:42:07Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/pay... |
<!-- Describe your changes in detail -->
Updated openapi spec added labels to wallet data | 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/v1/openapi_spec_v1.json`
- `api-reference/v2/openapi_spec_v2.json`
**Detailed Identifier Changes:**
Commit ... | {"pr_number": 9287, "pr_title": "chore: Updated openapi spec added labels to wallet data", "merged_at": "2025-09-08T07:33:56Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"api_models": ["crates/api_models/src/payments.rs"], "other": ["api-reference/v1/opena... |
<!-- Describe your changes in detail -->
Currently in invites we don't check if user exists across entities.
This will be a problem when inviting a user with higher entity from different lineage.
This PR fixes it. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/user.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (5 changes)
- Add conditional logic for feature flags or filtering (1 changes) | {"pr_number": 6677, "pr_title": "fix(users): Check lineage across entities in invite", "merged_at": "2024-11-27T14:33:37Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["merchant", "user"]}, "hierarchy": {"core_business": ["crates/router/src/core/user.rs"]}, "change_types": {"fields... |
Main PR - https://github.com/juspay/hyperswitch/pull/7864 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/connector_configs/toml/production.toml`
- `crates/hyperswitch_connectors/src/connectors/noon.rs`
- `crates/hyperswitch_connectors/src/connectors/noon/transformers.rs`... | {"pr_number": 7865, "pr_title": "fix(connector): revert noon-paypal", "merged_at": "2025-04-22T10:01:20Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/connector_configs/toml/production.toml", "crates/hyperswi... |
External 3ds payments for cybersource via netcetera external authentication is not working currently. To fix it, correct ucaf_collection_indicator has to be passed which is "2" according to cybersource doc. This PR introduces this correction.
<img width="604" alt="Screenshot 2025-03-25 at 3 53 43 PM" src="https://gi... | 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": 7623, "pr_title": "fix(connector): [CYBERSOURCE] change ucaf_collection_indicator for mastercard payments via netcetera", "merged_at": "2025-03-26T12:33:55Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors":... |
<!-- Describe your changes in detail -->
This PR adds support for webhook_url in v2 PaymentsRequest. It allows merchants to pass their own webhook URL instead of creating one in Hyperswitch. This change is applicable only to v2 tunnel 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`
**2. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/payments.rs`
**3. Core Business Logic**
- `crates/route... | {"pr_number": 9625, "pr_title": "refactor(core): add webhook_url for v2 tunnel", "merged_at": "2025-10-08T15:25:10Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/payments.rs"], "domain": ["crat... |
<!-- Describe your changes in detail -->
Currently in payment link after redirection in case of non 3ds, we return to merchant url with following query params
- payment id, status
But for non 3ds we return to merchant url with following query params
- status , client secret, manual_retry_allowed
Inorder to ha... | 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` | {"pr_number": 6665, "pr_title": "fix(core): add payment_id as query param in merchant return url", "merged_at": "2024-11-26T14:43:14Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"core_business": ["crates/router/src/core/payments/help... |
1.Enhanced Dlocal Connector in cypress for Comprehensive Testing | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `cypress-tests/cypress/e2e/configs/Payment/Dlocal.js`
- `cypress-tests/cypress/e2e/configs/Payment/Utils.js`
**Code Patterns Applied:**
- Extend existing types with new fields (402 changes) | {"pr_number": 8362, "pr_title": "ci(cypress): Added Dlocal Connector Test", "merged_at": "2025-07-11T09:41:09Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user", "connector"]}, "hierarchy": {"tests": ["cypress-tests/cypress/e2e/configs/Payment/Dlocal.js", "cypress-tests/cypress/... |
<!-- Describe your changes in detail -->
Add support for Apple Pay - connector decryption flow | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/connector_configs/toml/development.toml`
- `crates/connector_configs/toml/production.toml`
- `crates/connector_configs/toml/sandbox.toml`
- ... and 3 more files
*... | {"pr_number": 9810, "pr_title": "feat(connector): [Finix] Add support for Apple Pay", "merged_at": "2025-10-16T08:13:01Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/connector_configs/toml/development.toml",... |
<!-- Describe your changes in detail -->
- Add a fallback for Redis gets with prefix
- Add a Domain type for Redis for the correctness of adding a prefix
## Motivation and Context
<!--
Why is this change required? What problem does it solve?
If it fixes an open issue, please link to the issue here.
If you do... | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/api_locking.rs`
- `crates/router/src/core/health_check.rs`
- `crates/router/src/core/payment_methods/cards.rs`
- ... and 10 more files
**2. External Connector Inte... | {"pr_number": 7043, "pr_title": "fix(multitenancy): add a fallback for get commands in redis", "merged_at": "2025-01-28T20:01:57Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["payment", "user", "card"]}, "hierarchy": {"core_business": ["crates/router/src/core/api_locking.rs", "crates/ro... |
<!-- Describe your changes in detail -->
This PR adds the info logs to log the dynamic routing grpc requests and response objects. | 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`
**2. Other**
- `crates/external_services/src/grpc_client.rs`
- `crates/external_services/src/grpc_client/dynamic_routing/elimination_rate_c... | {"pr_number": 6962, "pr_title": "refactor(dynamic_routing): add info logs to log the grpc request and response", "merged_at": "2025-01-16T11:12:32Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/... |
Fixed payout method data not being fetched from card vault when using `payout_method_id` in payouts flow.
**Changes:**
- Added `force_fetch_card_from_vault` parameter to `get_pm_list_context` to enable card vault lookup for payouts
- Added `get_card_details_from_locker` method to PaymentMethodsController trait
- ... | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payment_methods/cards.rs`
- `crates/router/src/core/payouts/validator.rs`
**2. Other**
- `crates/payment_methods/src/controller.rs`
**Code Patterns Applied:**
- Impl... | {"pr_number": 8729, "pr_title": "fix(payment-methods): fetch payment method details in payouts flow", "merged_at": "2025-07-24T15:48:58Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core/payment_meth... |
<!-- Describe your changes in detail -->
Fixed bugs and added cypress test
1. Made sensitive informations as Secret.
2. Resolved Deserialization error in Payments Response
3. Removed unnecessary structs | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/peachpayments/transformers.rs`
- `crates/payment_methods/src/configs/payment_connector_required_fields.rs`
**Code Patterns Applied... | {"pr_number": 9393, "pr_title": "fix(connector): [Peachpayments] Fix Bugs", "merged_at": "2025-09-16T18:02:31Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors/peachpayments... |
implement Skrill, interac and paysafecard Payment Method | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/connector_configs/Cargo.toml`
- `crates/connector_configs/src/common_config.rs`
- `crates/connector_configs/src/connector.rs`
- ... and 6 more files
**2. Other**
... | {"pr_number": 9396, "pr_title": "feat(connector): [Paysafe] implement Skrill, interac and paysafecard Payment Method", "merged_at": "2025-09-18T08:54:42Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/connecto... |
The Noon Connector V2 API is failing in the payment flow with the error `Missing required param: order_category.` This happens because the connector_metadata is not being extracted in the V2 confirm-intent flow, which causes the order_category field to be None. The fix involves correctly parsing connector_metadata and ... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/payments.rs`
**2. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/payments.rs`
- `crates/hyperswitch_domain_models/src/pay... | {"pr_number": 9825, "pr_title": "fix(payments): add connector metadata parsing and order category to payment router data", "merged_at": "2025-10-16T10:25:01Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_... |
MIT payment requests were previously handled only at the function level. This PR adds support for connector-level configurations.
And also includes Paybox mandates in Cypress automation. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `cypress-tests/cypress/e2e/PaymentTest/00009-RefundPayment.cy.js`
- `cypress-tests/cypress/e2e/PaymentTest/00011-CreateSingleuseMandate.cy.js`
- `cypress-tests/cypress/e2e/PaymentTest/00012-CreateMul... | {"pr_number": 6650, "pr_title": "ci(cypress): Move MIT requests to configs and add Paybox Mandates", "merged_at": "2024-11-27T18:43:05Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user", "connector"]}, "hierarchy": {"tests": ["cypress-tests/cypress/e2e/PaymentTest/000... |
This PR adds functionality for payment links to
- emit latest payment intent status before rendering status UI or payment widget
- consider `requires_customer_action` as payment link's terminal state | 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/payment_link.rs`
- `crates/router/src/core/payment_link/payment_link_initiate/payment_l... | {"pr_number": 7531, "pr_title": "feat(payment-link): emit intent status to parent before rendering payment link UI", "merged_at": "2025-03-19T11:00:08Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models... |
<!-- Describe your changes in detail -->
Use enums in payment_connector_required_fields.rs instead of string for required fields and reduce duplication | 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/payment_methods/src/configs/payment_connector_required_fields.rs`
- `crates/router/src... | {"pr_number": 7539, "pr_title": "refactor(required_fields): move pm required fields to pm crate", "merged_at": "2025-04-21T08:33:28Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user", "connector"]}, "hierarchy": {"core_business": ["crates/router/src/core/payment_metho... |
<!-- Describe your changes in detail -->
Added apikey auth for juspay threeds server in wasm file
## Checklist
<!-- Put an `x` in the boxes that apply -->
- [x] I formatted the code `cargo +nightly fmt --all`
- [x] I addressed lints thrown by `cargo clippy`
- [x] I reviewed the submitted code
- [ ] I ... | To implement this **authentication** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/connector_configs/toml/development.toml`
- `crates/connector_configs/toml/sandbox.toml` | {"pr_number": 7456, "pr_title": "fix(dashboard): added apikey auth for juspay threeds server in wasm file", "merged_at": "2025-03-07T07:15:32Z", "intent": {"feature_type": "authentication", "action": "add_feature", "entities": []}, "hierarchy": {"connectors": ["crates/connector_configs/toml/development.toml", "crates/c... |
<!-- Describe your changes in detail -->
Added Incremental Authorization flow for Paypal | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/router_request_types.rs`
**2. Core Business Logic**
- `crates/router/src/core/payments/transformers.rs`
**3. External Connector Int... | {"pr_number": 8517, "pr_title": "feat(connector): Add Incremental Authorization flow for Paypal", "merged_at": "2025-07-14T11:26:18Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/rou... |
<!-- Describe your changes in detail -->
This PR adds support for Google Pay payment method in the Tesouro connector. | 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": 9706, "pr_title": "feat(connector): [tesouro] google pay", "merged_at": "2025-10-07T15:14:55Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/connector_configs/toml/development.toml", "crates/conn... |
<!-- Describe your changes in detail --> | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/admin.rs`
- `crates/api_models/src/profile_acquirer.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/business_profile.rs`
- `crates/... | {"pr_number": 8529, "pr_title": "feat(business_profile): added merchant country code in business profile", "merged_at": "2025-07-14T12:28:40Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/admin.rs", ... |
<!-- Describe your changes in detail -->
added StringMajorUnit for amount conversion | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/router/src/connector/cybersource.rs`
- `crates/router/src/connector/cybersource/transformers.rs`
- `crates/router/tests/connectors/cybersource.rs`
**2. Type Definiti... | {"pr_number": 6335, "pr_title": "refactor(connector): add amount conversion framework to cybersource", "merged_at": "2024-12-04T11:00:45Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/router/src/connector/cyb... |
<!-- Describe your changes in detail -->
This feature allows based on deployment config , it is able to query Request Body and add as a top level fields in the Kafka events | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Configuration Files**
- `crates/router/src/configs/secrets_transformers.rs`
- `crates/router/src/configs/settings.rs`
**2. Other**
- `crates/router/src/routes/app.rs`
- `crates/router/src/services/api.rs`
... | {"pr_number": 8780, "pr_title": "chore(router): events enhancement for kafka", "merged_at": "2025-07-30T12:01:26Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"config": ["crates/router/src/configs/secrets_transformers.rs", "crates... |
<!-- Describe your changes in detail -->
This PR adds support for partial auth in proxy payments which is triggered in revenue recovery workflow.
`enable_partial_authorization` is passed in `/recovery` flow, which update payment intent with enable_partial_authorization to true. Proxy(authorize) will gets triggered b... | 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`
**3. Domain Models (Business Logic Types)**
- `crat... | {"pr_number": 9503, "pr_title": "feat(core): Add support for partial auth in proxy payments [V2]", "merged_at": "2025-09-30T07:14:23Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/payments.rs"]... |
<!-- Describe your changes in detail -->
This PR will add logging for cookies and also make signout API accessible by any SPT. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/user.rs`
**2. Tests**
- `config/deployments/integration_test.toml`
- `loadtest/config/development.toml`
**3. Configuration Files**
- `config/config.example.... | {"pr_number": 6599, "pr_title": "refactor(authn): Enable cookies in Integ", "merged_at": "2024-11-26T12:42:14Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"core_business": ["crates/router/src/core/user.rs"], "tests": ["config/deployments/integration_test.t... |
<!-- Describe your changes in detail --> | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/paysafe/transformers.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (9 changes)
**Detailed Identifier Change... | {"pr_number": 9497, "pr_title": "refactor(connector): [Paysafe] populate error code and message for 200 errors", "merged_at": "2025-09-23T19:41:28Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_co... |
<!-- Describe your changes in detail -->
Request creation changes for injector to be used `InjectorRequest` struct creation.
```rust
impl InjectorRequest {
pub fn new()
}
```
Also change the response type
```rust
pub struct InjectorResponse {
/// HTTP status code from the connector respons... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Type Definitions**
- `crates/injector/src/types.rs`
**2. Other**
- `crates/injector/src/consts.rs`
- `crates/injector/src/injector.rs`
- `crates/injector/src/lib.rs`
- ... and 1 more files
**Code Patte... | {"pr_number": 9306, "pr_title": "feat(injector): injector request formation changes", "merged_at": "2025-09-11T12:12:41Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"types": ["crates/injector/src/types.rs"], "other": ["crates/inj... |
<!-- Describe your changes in detail -->
Modified the authentication for profile and mca routes to use API Key instead of Admin API Key.
This PR has the corresponding OpenAPI spec changes. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/openapi/src/routes/merchant_connector_account.rs`
**2. Other**
- `api-reference/openapi_spec.json`
- `crates/openapi/src/routes/profile.rs` | {"pr_number": 7678, "pr_title": "refactor(openapi): update authentication for profiles and mca openapi", "merged_at": "2025-04-02T07:01:58Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"connectors": ["crates/openapi/src/routes/merchant_connector_account.rs"], "ot... |
1. Fetching email from customer email if billing.email is not present , so in HS payment request body we wont need billing.email anymore
2. Removed `customer_ip` from payments request since it is not a mandatory field for novalnet, so in HS payment request body we wont need browser_info anymore | 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": 6619, "pr_title": "fix(connector): [Novalnet] Get email from customer email if billing.email is not present ", "merged_at": "2024-11-21T21:55:07Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/h... |
<!-- Describe your changes in detail -->
We were getting a 500 in prod primarily for a `warnings` field which was incorrectly mapped type.
Also, we were sending country as alpha2, should be sent as Alpha3. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/nexixpay/transformers.rs`
**Code Patterns Applied:**
- Define new data structures (1 changes)
- Extend existing types with new fields... | {"pr_number": 9476, "pr_title": "fix(connector): [NEXIXPAY] Updated the Api Response Schema", "merged_at": "2025-09-23T08:41:29Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connec... |
<!-- Describe your changes in detail -->
This PR will add route to enable Elimination based dynamic routing for specific profiles.
```
curl --location --request POST 'http://localhost:8080/account/MERCHANT_ID/business_profile/PROFILE_ID/dynamic_routing/elimination/toggle?enable=none' \
--header 'api-key: API_KEY'
... | 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/routing.rs`
- `crates/router/src... | {"pr_number": 6568, "pr_title": "feat(routing): elimination routing switch for toggling the feature", "merged_at": "2024-12-02T15:10:20Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/events/routing.rs", "crates/api_m... |
<!-- Describe your changes in detail -->
Integrate Wallet Paze in Adyen. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/router/src/connector/adyen.rs`
- `crates/router/src/connector/adyen/transformers.rs`
**Code Patterns Applied:**
- Define new data structures (1 changes)
- Extend existi... | {"pr_number": 6545, "pr_title": "feat(connector): [ADYEN] Integrate Paze", "merged_at": "2024-11-13T10:27:07Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["card"]}, "hierarchy": {"connectors": ["crates/router/src/connector/adyen.rs", "crates/router/src/connector/adyen/transformers... |
<!-- Describe your changes in detail -->
Fix wasm bug juspay threeds
currently wasm build is not showing any error because of double bracket issue
## 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 sc... | To implement this **connector_integration** 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": 9757, "pr_title": "fix(router): Fix wasm bug juspay threeds", "merged_at": "2025-10-08T16:41:58Z", "intent": {"feature_type": "connector_integration", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"connectors": ["crates/connector_configs/toml/development.toml", "crates/connector_configs/to... |
This PR introduces a new migration API that facilitates migrating routing rules defined in Euclid (legacy engine) to the new `decision_engine`. It extracts routing algorithm definitions associated with a `profile_id`, parses them, converts them to the `Program` format used by the decision engine, and then invokes the c... | 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. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/routing_algorithm.rs`
**3. ... | {"pr_number": 8233, "pr_title": "feat: migration api for migrating routing rules to decision_engine", "merged_at": "2025-06-13T09:36:07Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"api_models": ["crates/api_models/src/events/routing... |
<!-- Describe your changes in detail -->
Hotfix for https://github.com/juspay/hyperswitch/pull/8219
Add worldpay vantiv as a payment connector. Integrated non 3ds cards flow.
> Note: Report Group for each transaction is collected from the payment's metadata. If not provided - then the default report group provide... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/configs.rs`
**2. Core Business Logic**
- `crates/router/src/core/admin.rs`
**3. External Connector Integration**
- `crates/commo... | {"pr_number": 8263, "pr_title": "feat(connectors): [Worldpayvantiv] add card support", "merged_at": "2025-06-05T11:56:14Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/configs.rs"], ... |
<!-- Describe your changes in detail -->
In this PR,
This PR integrates the Vantiv auth reversal flow as a void operation in Hyperswitch. Additionally, it handles the response status for each payment operation API call.
## How did you test it?
<!--
Did you write an integration/unit/API test to verify the code ... | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/worldpayvantiv.rs`
- `crates/hyperswitch_connectors/src/connectors/worldpayvantiv/transformers.rs`
**Code Patterns Applied:**
- Define n... | {"pr_number": 8540, "pr_title": "refactor(connector): [Worldpayvantiv] refactor void flow and handle transaction status", "merged_at": "2025-07-04T14:15:27Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch... |
<!-- 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 491334f3:
Files to modify:
**crates/rout... | {"pr_number": 6517, "pr_title": "fix(router): get apple pay certificates only from metadata during the session call", "merged_at": "2024-11-08T12:12:56Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router... |
<!-- Describe your changes in detail -->
Created callback_mapper table, added diesel, domain models and implemented interface for DB operations.
this is added for network tokenization webhooks feature. Since this is generic, any kind of data (excluding sensitive info) can be stored.
db changes -
<img width="715"... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/callback_mapper.rs`
- `crates/diesel_models/src/lib.rs`
- `crates/diesel_models/src/query.rs`
- ... and 3 more files
**2. Domain Models (Busi... | {"pr_number": 6571, "pr_title": "feat(core): diesel models, domain models and db interface changes for callback_mapper table", "merged_at": "2025-01-15T10:48:14Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["merchant", "user", "webhook"]}, "hierarchy": {"database": ["crates/diesel... |
<!-- Describe your changes in detail -->
`is_rebilling` should be sent as `1` always for `NTID` flow in Nuvei.
- Core change: For proxy/ntid flow customer details were not being passed in `router_data` from core.
- Add US as supported countries for GOOGLEPAY, Even though it doesn't list US in supported countries... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payments.rs`
**2. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/nuvei/transformers.rs`
**3. Tests**
- `config/deployments/in... | {"pr_number": 9738, "pr_title": "fix(nuvei): For NTID/proxy flow `is_rebilling` should always be sent 1 & pass customer_details in proxy flow + Add US as supported countries for GOOGLEPAY", "merged_at": "2025-10-10T12:43:31Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer",... |
<!-- Describe your changes in detail -->
Hotfix :https://github.com/juspay/hyperswitch/pull/8882 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payments.rs`
**Detailed Identifier Changes:**
Commit 7a3b4dac:
Files to modify:
**crates/router/src/core/payments.rs**
Modify existing code | {"pr_number": 8881, "pr_title": "feat(core): Fix Applepay/Gpay for Trustpay", "merged_at": "2025-08-10T19:15:51Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core/payments.rs"]}, "change_types"... |
<!-- Describe your changes in detail -->
This is the injector crate which would be used for External Vault proxy usage
<img width="2392" height="1436" alt="Screenshot 2025-07-09 at 12 03 03 PM" src="https://github.com/user-attachments/assets/3eb90264-e3eb-49c4-9804-8f840e804ceb" />
<img width="2038" height="16... | 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`
- `crates/router/Cargo.toml`
**3. Other**
- `Cargo.lock`
- `crates/injector/src/injector.rs... | {"pr_number": 8959, "pr_title": "feat(injector): add support for new crate - injector for external vault proxy", "merged_at": "2025-08-25T13:24:15Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user", "card"]}, "hierarchy": {"types": ["crates/injector/src/types.rs"], "config": ["... |
<!-- Describe your changes in detail -->
Initially, `Internal Server Error` is being propagated instead of the `IncorrectPaymentMethodConfiguration`.
Now it has been updated to `IncorrectPaymentMethodConfiguration` which has error message - No eligible connector was found for the current payment method configuration | 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": 8512, "pr_title": "fix(core): Update error for routing instead of Internal Server Error", "merged_at": "2025-07-03T09:17:13Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "connector"]}, "hierarchy": {"core_business": ["crates/router/src/core/payments.rs"]},... |
<!-- Describe your changes in detail -->
Context
https://github.com/juspay/hyperswitch/pull/7882 accidentally reverted changes made in https://github.com/juspay/hyperswitch/pull/7866, which was a merchant critical PR.
Reason:
- This might have occured due to incorrect resolution of merge conflicts in [this PR](ht... | 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`
**Code Patterns Applied:**
- Modify database queries (1 changes)
**Detailed Identifier Changes:**
Commit d5eee96f:
Files to modify:
**c... | {"pr_number": 7954, "pr_title": "fix(payment_methods): Re-revert changes done in `pr#7866` by `pr#7882`", "merged_at": "2025-05-05T12:58:42Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"core_business": ["crates/router/src/core/paymen... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.