prompt stringlengths 6 90.9k | response stringlengths 121 18.6k | metadata stringlengths 314 42.3k |
|---|---|---|
<!-- Describe your changes in detail -->
This PR introduces the below given flows for Payload connector:
- [x] Cards (No 3DS)
- [x] PSync
- [x] Void
- [x] Refunds
- [x] AVS Checks
- [x] Cypress
Connector does not support 3DS transactions. | 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": 8545, "pr_title": "feat(connector): [payload] introduce no-3ds cards", "merged_at": "2025-07-05T15:10:04Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core/connector_validation.rs... |
<!-- Describe your changes in detail -->
Add webhooks for network tokenization
- added support to process webhooks from token service.
- verify webhooks updates the pan and network token metadata | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/payment_methods.rs`
- `crates/api_models/src/webhooks.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/callback_mapper.rs`
**3. ... | {"pr_number": 6695, "pr_title": "feat(router): Add webhooks for network tokenization ", "merged_at": "2025-06-26T09:44:47Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/payment_methods.rs", "cr... |
<!-- Describe your changes in detail -->
Currently, if the `forex_enabled` feature flag is not present as an ENV, it is leading to deserialization errors.
Modified it in such a way to assume the default value (false) if the ENV is not present. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Other**
- `crates/analytics/src/lib.rs` | {"pr_number": 7695, "pr_title": "refactor(analytics): default config for forex_enabled", "merged_at": "2025-04-03T10:44:19Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user"]}, "hierarchy": {"other": ["crates/analytics/src/lib.rs"]}, "change_types": {}, "has_identifie... |
<!-- Describe your changes in detail -->
add capability to force challenge for 3DS Payments through Netcetera and send few optional fields
1. Profile level enablement `force_3ds_challenge` which would request netcetera for challenge flow
2. Send few optional fields like trans_type, which can potentially be require... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/admin.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/business_profile.rs`
- `crates/diesel_models/src/schema.rs`
- `crates/d... | {"pr_number": 7429, "pr_title": "feat(router): add capability to force challenge for 3DS Payments through Netcetera and send few optional fields", "merged_at": "2025-03-06T13:37:46Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user", "connector"]}, "hierarchy": {"api_m... |
<!-- Describe your changes in detail -->
This PR refactors the gRPC header handling for the Unified Connector Service (UCS) by introducing a dedicated header type, `GrpcHeadersUcs`. This change enhances the specificity and robustness of header management for UCS interactions.
Key changes include:
- **New `Grpc... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payments/flows/authorize_flow.rs`
- `crates/router/src/core/payments/flows/external_proxy_flow.rs`
- `crates/router/src/core/payments/flows/psync_flow.rs`
- .... | {"pr_number": 9275, "pr_title": "refactor(ucs): introduce dedicated gRPC header type and enhance lineage ID handling", "merged_at": "2025-09-09T10:05:31Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"core_business": ["crates/router/sr... |
<!-- Describe your changes in detail -->
Add wasm field to collect merchant secret for payout webhook integration | 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": 9524, "pr_title": "feat(euclid_wasm): add wasm changes for payout webhooks", "merged_at": "2025-09-24T06:58:53Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["merchant", "webhook"]}, "hierarchy": {"connectors": ["crates/connector_configs/toml/development.toml", "crate... |
<!-- Describe your changes in detail -->
We need to make update payment methods API which can update the fields of the records in payment methods table. It will consume a CSV file which will have batch update entries. Currently it should only update connector_mandate_id, network_transaction_id and mandate_status. | 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. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/payment_method.rs`
**3. Domain Models (Business Logic Types)**
... | {"pr_number": 9075, "pr_title": "feat(core): Update payment methods api", "merged_at": "2025-09-02T12:50:03Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"api_models": ["crates/api_models/src/payment_methods.rs"], "database": ["crates... |
<!-- Describe your changes in detail -->
This pull request enhances cache management for connector creation by introducing a new mechanism to invalidate related cache entries whenever a new connector is added. The main change is the addition of the `redact_cgraph_cache` function, which ensures that outdated cgraph cac... | 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`
- `crates/router/src/core/subscription.rs`
**Code Patterns Applied:**
- Implement new functions (1 chang... | {"pr_number": 9629, "pr_title": "refactor(core): add cache redaction for cgraph", "merged_at": "2025-10-01T08:33:13Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core/admin.rs", "crates/router/... |
There was a typo while populating scheme for Archipel Applepay payments - this PR fixes it.
Impact - Due to this typo Applepay payments were failing using Mastercard, with this fix Applepay payments will work. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/archipel/transformers.rs` | {"pr_number": 8450, "pr_title": "feat(connector): [ARCHIPEL] fix Mastercard scheme string for Applepay payments", "merged_at": "2025-06-24T13:45:21Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user", "card"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connector... |
<!-- Describe your changes in detail -->
Global search has two components:
- Free flow search, wherein search takes place across all fields available to search upon
- Search on a specific field based on the field filter
In this PR, additional filters have been added for global search to search on a specific fie... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/analytics/search.rs`
**2. Configuration Files**
- `config/config.example.toml`
- `config/deployments/env_specific.toml`
- `config/development.toml`
... | {"pr_number": 6352, "pr_title": "feat(opensearch): add additional global search filters and create sessionizer indexes for local", "merged_at": "2024-10-19T14:22:39Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["cra... |
<!-- Describe your changes in detail -->
This PR fixes an edge case with GlobalPay where, upon payment decline, we get a deserialization error and that is because `currency` field is not expected to be empty but rather a valid `Currency` enum. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/globalpay/response.rs`
- `crates/hyperswitch_connectors/src/utils.rs`
**Code Patterns Applied:**
- Implement new functions (1 chan... | {"pr_number": 7812, "pr_title": "fix(connector): [globalpay] handle edge case where currency comes as empty upon payment decline", "merged_at": "2025-04-17T13:23:44Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["cra... |
<!-- Describe your changes in detail -->
Fixes routing approach updation for wallets flow | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/payment_attempt.rs`
**2. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/payments/payment_attempt.rs`
**3. Core Bus... | {"pr_number": 8490, "pr_title": "fix: Update routing_approach for session_token flow", "merged_at": "2025-07-03T07:24:26Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"database": ["crates/diesel_models/src/payment_attempt.rs"], "d... |
Added `connector_customer_id` support to batch payment method update API. When provided in CSV with `merchant_connector_ids`, stores it in customer's `connector_customer` field and returns in response.
__Key format:__
- Payout processors: `{profile_id}_{connector_name}`
- Others: `merchant_connector_id` | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/payment_methods.rs`
**2. Core Business Logic**
- `crates/router/src/core/payment_methods/migration.rs`
**Code Patterns Applied:**
- Implement new functions... | {"pr_number": 9791, "pr_title": "feat(migration): add connector_customer updation support to batch PM update API", "merged_at": "2025-10-11T13:30:20Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/s... |
Add Bambora connector to cypress test suits | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `cypress-tests/cypress/e2e/configs/Payment/Bambora.js`
- `cypress-tests/cypress/e2e/configs/Payment/Utils.js`
**Code Patterns Applied:**
- Extend existing types with new fields (464 changes) | {"pr_number": 8400, "pr_title": "ci(cypress): add bambora connector", "merged_at": "2025-06-25T09:49:13Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "connector"]}, "hierarchy": {"tests": ["cypress-tests/cypress/e2e/configs/Payment/Bambora.js", "cypress-tests/cypress/e2... |
<!-- Describe your changes in detail -->
Added GooglePay as a payment method type under wallets in config files | 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": 8832, "pr_title": "fix(wasm): [FISERV] Added GooglePay Payment Method Type", "merged_at": "2025-08-06T07:42:36Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment"]}, "hierarchy": {"connectors": ["crates/connector_configs/toml/development.toml", "crates/connector_... |
<!-- Describe your changes in detail -->
HOTFIX: https://github.com/juspay/hyperswitch/pull/7471
Changed the Attempt Status Mapping of `SubmittedForSettlement` and `SettlementPending` to `Charged` | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/braintree/transformers.rs` | {"pr_number": 7516, "pr_title": "fix(connector): [BRAINTREE] Changed Attempt Status Mapping for Braintree", "merged_at": "2025-03-13T09:29:01Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connect... |
<!-- Describe your changes in detail -->
Adds support for non threeds card mandates
> Note: Multiple mandates cannot be created with the same customer and same payment method. This is also the reason why cypress test is not added - for the same customer id and payment method CIT will fail and hence MITs cannot be ... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/paysafe.rs`
- `crates/hyperswitch_connectors/src/connectors/paysafe/transformers.rs`
- `crates/hyperswitch_connectors/src/defaul... | {"pr_number": 9560, "pr_title": "feat(connectors): [Paysafe] implement non-3DS card mandates", "merged_at": "2025-10-09T08:26:14Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/conne... |
Currently, we are not consuming amount in BankRedirectSyncResponse. Hence during a force PSync, the status is getting updated but the amount is not being updated since we arent consuming that and there's no integrity check on the PSync response. It is only there for Webhook Response. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/trustpay.rs`
- `crates/hyperswitch_connectors/src/connectors/trustpay/transformers.rs`
**Code Patterns Applied:**
- Extend existin... | {"pr_number": 8455, "pr_title": "fix(connector): [TRUSTPAY] Consuming Amount in PSync Response", "merged_at": "2025-06-26T14:38:11Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/con... |
<!-- Describe your changes in detail -->
Keeping the pr title of [pr](https://github.com/juspay/hyperswitch/pull/6918) to get the hotfix pr checked pass.
https://github.com/juspay/hyperswitch/pull/6918
/relay is a api that will be used to just forward the request sent by merchant without performing any application... | 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. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/enums.rs`
- `crates/diesel_models/src/... | {"pr_number": 6924, "pr_title": "feat(router): add /retrieve api for relay", "merged_at": "2024-12-23T17:04:46Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "refund"]}, "hierarchy": {"api_models": ["crates/api_models/src/lib.rs", "crates/api_models/src/relay... |
<!-- Describe your changes in detail -->
Updated next steps after deployment setup on Readme | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Other**
- `README.md` | {"pr_number": 7686, "pr_title": "docs: Updated next steps after deployment setup on Readme", "merged_at": "2025-04-03T03:28:38Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"other": ["README.md"]}, "change_types": {}, "has_identifier_data": false, "commits_matche... |
1. Integrated ApplePay token flow for Novalnet, decrypt flow is not supported
2. Integrated mandates for ApplePay | 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": 6409, "pr_title": "feat(connector): [Novalnet] Integrate Applepay wallet token flow", "merged_at": "2024-10-25T10:56:10Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["token"]}, "hierarchy": {"connectors": ["crates/connector_configs/toml/development.toml", "crates/con... |
- Earlier we used to support filtering of wallet payment methods for customer pml, if it has been saved by the merchant via off- session payments once , the changes were made in the following [PR](https://github.com/juspay/hyperswitch/pull/4038)
- In this PR we are reverting the logic , the decision was taken to sh... | 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. Other**
- `crates/common_enums/src/enums.rs`
**Code Patterns Applied:**
- Modify database queries (1 changes)
**Detailed Identifie... | {"pr_number": 7866, "pr_title": "refactor(payment_methods): refactor merchant payment method list for wallets", "merged_at": "2025-04-28T08:14:20Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/c... |
This PR adds a missing struct because of which the openapi v2 file that was generated was not valid. | To implement this **unknown** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/payment_methods.rs`
**2. Other**
- `api-reference-v2/openapi_spec.json`
- `api-reference/openapi_spec.json`
- `crates/masking/src/cassandra.rs`
- ... and... | {"pr_number": 7383, "pr_title": "fix(openapi_v2): add missing struct in openapi v2", "merged_at": "2025-03-07T13:57:10Z", "intent": {"feature_type": "unknown", "action": "add_feature", "entities": []}, "hierarchy": {"api_models": ["crates/api_models/src/payment_methods.rs"], "other": ["api-reference-v2/openapi_spec.jso... |
Fix type account_id for ConfigMetadata | 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 (1 changes) | {"pr_number": 9349, "pr_title": "refactor(connector): [Paysafe] fix wasm", "merged_at": "2025-09-10T17:22:46Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"connectors": ["crates/connector_configs/src/connector.rs"]}, "change_types": {"fields_added": 1}, "ha... |
<!-- Describe your changes in detail -->
- Moved both `v1` and `v2` API docs under `api-reference` directory
- Renamed `openapi_spec.json` files for v1 and v2
- Updated OpenAPI spec file paths in `openapi` crate
- Modified OpenAPI spec path in CI pipeline | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Database Layer (Queries & Schema)**
- `api-reference/api-reference/schemas/outgoing--webhook.mdx`
**2. External Connector Integration**
- `api-reference/api-reference/merchant-connector-account/merchant-connecto... | {"pr_number": 8333, "pr_title": "docs(openapi): Show API version selection dropdown in Mintlify", "merged_at": "2025-06-13T09:03:06Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"database": ["api-reference/api-reference/schemas/outgoing--webhook.mdx"], "con... |
Add template code for Loonio connector | 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": 9586, "pr_title": "feat(connector): [Loonio] Add template code", "merged_at": "2025-09-30T07:43:16Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["connector"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/connector_endpoints.rs"], "connectors": ["cr... |
<!-- 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": 6641, "pr_title": "fix(connector): [Cybersource] change commerce indicator for applepay", "merged_at": "2024-11-22T12:26:57Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "card"]}, "hierarchy": {"connectors": ["crates/router/src/connector/cybers... |
<!-- Describe your changes in detail -->
Hotfix for https://github.com/juspay/hyperswitch/pull/9372
Add acknowledgement in adyen for incoming webhooks by sending status 200. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/common_enums/src/connector_enums.rs`
- `crates/hyperswitch_connectors/src/connectors/adyenplatform/transformers/payouts.rs` | {"pr_number": 9442, "pr_title": "feat(router): Handle adyen webhook issue", "merged_at": "2025-09-18T12:33:56Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/common_enums/src/connector_enums.rs", "crates/hyper... |
<!-- Describe your changes in detail -->
Flexiti is not a traditional credit card. It's a co-branded credit card that offers installment financing.
Flexiti Payment Method Type:
Co-Branded Credit Card with Installment Financing
Flexiti issues a FlexitiCard (Mastercard network)
Functions as both a credit card AN... | 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": 8743, "pr_title": "feat(connector): [Flexiti]Add support for flexiti connector ", "merged_at": "2025-07-30T12:01:26Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/payments.rs"], "... |
Added exemption_requested and exemption_approved fields to the auth_events metrics, extended the auth-analytics API with new filters for 3DS Intelligence, and created a dedicated endpoint to serve SCA-exemption Sankey chart data. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/analytics/auth_events.rs`
**2. Core Business Logic**
- `crates/analytics/src/auth_events/core.rs`
**3. Type Definitions**
- `crates/analytics/src/auth_e... | {"pr_number": 8163, "pr_title": "feat(analytics): revamped 3ds auth analytics", "merged_at": "2025-06-02T10:08:43Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["merchant", "user", "order"]}, "hierarchy": {"api_models": ["crates/api_models/src/analytics/auth_events.rs"], "core_busi... |
<!-- Describe your changes in detail -->
Added Webhook Flow and Support for merchant_order_reference_id for Peachpayments | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/peachpayments.rs`
- `crates/hyperswitch_connectors/src/connectors/peachpayments/transformers.rs`
**Code Patterns Applied:**
- Defi... | {"pr_number": 9781, "pr_title": "feat(connector): [Peachpayments] Add Webhook Flow and Support For merchant_order_reference_id", "merged_at": "2025-10-15T16:01:29Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"connectors": ["crates/hy... |
Added below configs for payment link
1. payment_button_colour: Text for customizing message for card terms
2. custom_message_for_card_terms: Custom background colour for payment link's handle confirm button https://docs.hyperswitch.io/explore-hyperswitch/merchant-controls/integration-guide/web/customization#custom-m... | 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": 7288, "pr_title": "feat(payments): [Payment links] Add configs for payment link", "merged_at": "2025-02-18T15:29:43Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"api_models": ["crates/api_models/src/admin.rs", "crates/... |
<!-- Describe your changes in detail -->
In webhook, for specific connectors, we want to consume every webhook that arrives even if a error occurs while processing. This is done to keep the webhook channel open with the connector.
In this pr, a error wrapper is introduced to handle this logic where based on connecto... | 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/webhooks/incoming.rs`
- `crates/router/src/core/webhooks/incoming_v2.rs`
**3. E... | {"pr_number": 6636, "pr_title": "refactor(core): add error handling wrapper to wehbook", "merged_at": "2024-11-27T15:31:49Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "merchant", "connector"]}, "hierarchy": {"api_models": ["crates/api_models/src/connector_enums.rs"],... |
ach, becs and bacs in payment method data is renamed to ach_bank_debit, becs_bank_debit, bacs_bank_debit | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/router/src/configs/defaults/payment_connector_required_fields.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (12 changes) | {"pr_number": 6678, "pr_title": "refactor(dynamic_fields): rename fields like ach, bacs and becs for bank debit payment method", "merged_at": "2024-12-05T08:18:14Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crate... |
<!-- Describe your changes in detail -->
This PR fixes
1. Setup Mandate flow - Earlier Error is thrown in customer setup mandate if the payment profile is already present at the connector. Now, if `customerPaymentProfileId` is present we will map it to mandate id, if not we will return an error response.
2. For C... | 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:**
- Implement new functions (1 changes)
- Extend existing types with new fi... | {"pr_number": 9298, "pr_title": "fix(connectors): [authorizedotnet] send customerProfileId in the CIT flow and map customerPaymentProfileId in the Setup Mandate flow", "merged_at": "2025-09-09T11:09:10Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"... |
<!-- Describe your changes in detail -->
ORIGINAL PR: https://github.com/juspay/hyperswitch/pull/7525
Add mandate revoke flow to Braintree
https://developer.paypal.com/braintree/graphql/guides/payment_methods/#delete | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/braintree.rs`
- `crates/hyperswitch_connectors/src/connectors/braintree/transformers.rs`
- `crates/hyperswitch_connectors/src/de... | {"pr_number": 7530, "pr_title": "feat(connector): [BRAINTREE] Add revoke mandate flow", "merged_at": "2025-03-17T08:59:58Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors/brain... |
<!-- Describe your changes in detail -->
This PR
1. Updates Vantiv's endpoint by replacing payments with transact.
2. Extends the payment request to include billing address and customer_id.
3. It also addresses a 5xx error encountered during psync calls. The error occurred for accounts where psync is not enabled a... | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/worldpayvantiv/transformers.rs`
**2. Tests**
- `config/deployments/integration_test.toml`
- `loadtest/config/development.toml`
**3. ... | {"pr_number": 8354, "pr_title": "fix(connectors): [worldpayvantiv] change endpoint, add billing address and fix 5xx incase of psync", "merged_at": "2025-06-19T07:07:15Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates... |
This pull request introduces a new API endpoint for retrieving subscription plans and the supporting plumbing required for it. The changes include new request/response types, authentication and expiry logic, and routing updates to expose the endpoint. The main themes are new subscription plan retrieval functionality an... | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/subscription.rs`
**2. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/lib.rs`
- `crates/hyperswitch_domain_models/src/router_req... | {"pr_number": 9251, "pr_title": "feat(subscription): get plans for subscription", "merged_at": "2025-10-07T09:07:33Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/subscription.rs"], "domain": ["crate... |
<!-- Describe your changes in detail -->
removing changes for injector check of proxy and certificate | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Other**
- `crates/injector/src/vault_metadata.rs`
**Detailed Identifier Changes:**
Commit 56447525:
Files to modify:
**crates/injector/src/vault_metadata.rs**
Modify existing code | {"pr_number": 9373, "pr_title": "chore(injector): removing changes for injector check of proxy and certificate", "merged_at": "2025-09-16T10:09:16Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"other": ["crates/injector/src/vault_metadata.rs"]}, "change_types": {... |
<!-- Describe your changes in detail --> | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `postman/collection-dir/stripe/Flow Testcases/Happy Cases/Scenario17-Bank Redirect-eps/Payments - Confirm/event.test.js`
- `postman/collection-dir/stripe/Flow Testcases/Happy Cases/Scenario16-Bank Redir... | {"pr_number": 7849, "pr_title": "ci(postman): map assertions for `Sofort` using `Stripe` Payment Processor", "merged_at": "2025-04-25T14:07:23Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"tests": ["postman/collection-dir/stripe/Flow Testcases/Happy Cases/... |
<!-- Describe your changes in detail -->
Mask custom outgoing webhook headers in profile response. This changes is required to mask the custom outgoing webhook headers in the profile dashboard. This also requires control center changes, BE changes will only be merged and
deployed after dashboard changes. | 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. Type Definitions**
- `crates/router/src/types/api/admin.rs`
**Code Patterns Applied:**
- Define new data structures (1 changes)
- Implement ... | {"pr_number": 6826, "pr_title": "fix(webhooks): mask custom outgoing webhook headers in profile response", "merged_at": "2024-12-12T12:56:51Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/admin... |
<!-- Describe your changes in detail -->
Previously, in platform organization, there was support for creating v1 merchant accounts only.
This PR enables creating v2 merchant accounts of merchant_account_type `Standard` in the Platform Organization through the dashboard (using JWT authentication).
A default platfor... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/admin.rs` | {"pr_number": 8823, "pr_title": "feat(vsaas): enable creating v2 merchant accounts in platform organization", "merged_at": "2025-08-03T14:21:25Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["merchant", "user"]}, "hierarchy": {"core_business": ["crates/router/src/core/admin.rs"]}, ... |
Hotfix for https://github.com/juspay/hyperswitch/pull/7531 | 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": 7571, "pr_title": "feat(payment-link): emit intent status to parent before rendering payment link UI", "merged_at": "2025-03-19T12:57:07Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "merchant", "user"]}, "hierarchy": {"api_models": ["crates/api_models/sr... |
<!-- Describe your changes in detail -->
Create an API for Network Token Status Check.
API Doc: [doc](https://docs.google.com/document/d/1MZoq2C9NsZYBhvfqwVb3nPPTtufBlE1FE41r2MARc9Y/edit?tab=t.0)
Curl:
```
curl --location 'http://localhost:8080/v2/payment-methods/12345_pm_019959146f92737389eb6927ce1eb7dc/check-... | 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/payment_methods.rs`
**2. Core Business Logic**
- `crates/router/src/core/payment_methods.rs`
- `crates/router/src/c... | {"pr_number": 9443, "pr_title": "feat(core): [NETWORK TOKENIZATION] Check Network Token Status API", "merged_at": "2025-10-10T12:36:56Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/enums.rs", ... |
<!-- Describe your changes in detail -->
Currently, if payment method data is inserted in vault for customer c1, merchant id is being sent as entity id, this will not allow us to store same payment method data for customer c2.
Payment Method data is always tied to customer, not to merchant.
Hence updated entity id... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payment_methods.rs`
- `crates/router/src/core/payment_methods/vault.rs`
- `crates/router/src/core/proxy.rs`
- ... and 2 more files
**2. Type Definitions**
... | {"pr_number": 8380, "pr_title": "fix(payment_method): update entity id used for Vault to global customer id", "merged_at": "2025-07-08T17:49:54Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/cor... |
<!-- Describe your changes in detail -->
For generating session token for google pay, error was thrown if connector_wallet_details was not present and google pay related data won't be present in session token response thus parsing connector_wallet_details is made optional | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payments/flows/session_flow.rs`
**Code Patterns Applied:**
- Add conditional logic for feature flags or filtering (1 changes) | {"pr_number": 7365, "pr_title": "fix(core): make parsing optional for connector_wallet_details in session token flow", "merged_at": "2025-02-25T08:27:55Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/route... |
<!-- Describe your changes in detail -->
This is PR is fixing the external vault proxy URL addition to the request being sent to the PSP/Internet, which is being used in the connector-service | 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/injector.rs`
- `crates/injector/src/vault_metadata.rs`
**Code Patterns Applied:**
- Extend existing types with new fiel... | {"pr_number": 9460, "pr_title": "chore(injector): injector change for proxy", "merged_at": "2025-09-23T19:41:28Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"types": ["crates/injector/src/types.rs"], "other": ["crates/injector/sr... |
<!-- Describe your changes in detail -->
In this PR
1. Add support for moto flag : A type field called payment_channel will be accepted in the payment request optionally. This field can have one of `ecommerce`, `mail_order`, `telephone_order`. This flag is stored in the paymentIntent and sent to the connector in the... | 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.rs`
- `crates/diesel... | {"pr_number": 8800, "pr_title": "feat(router): [worldpayvantiv] add support for moto flag for v1 and extend vantiv api contract", "merged_at": "2025-08-01T11:08:29Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api... |
<!-- Describe your changes in detail -->
Improving API-Reference to include payment flows, and include better and correct description of some fields. | 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/api-reference/payments/payment--flows.mdx`
- `api-reference/api-refe... | {"pr_number": 8194, "pr_title": "docs: Improving API Reference", "merged_at": "2025-06-11T10:26:06Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment"]}, "hierarchy": {"api_models": ["crates/api_models/src/payments.rs"], "other": ["api-reference-v2/openapi_spec.json", "api-ref... |
<!-- Describe your changes in detail -->
- Added a field `payment_token` to customer PML response
- During `/confirm-intent`, in case of card, an inactive payment method method is created before `call_conector_service`
- After the payment has completed, depending on its status the payment method is marked active
- ... | 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/payment_methods.rs`
- `crates/api_models/src/payments.rs`
**2. Database Layer (Queries & Schema)**
- `crat... | {"pr_number": 8090, "pr_title": "feat(router): Save payment method on payments confirm (V2)", "merged_at": "2025-06-06T15:55:49Z", "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 -->
Currently with Postgres@18, db connection fails. Reason being space should be percent encoded as `%20`. This encoding standards are followed across all versions of Postgres as mentioned in their [docs](https://www.postgresql.org/docs/13/libpq-connect.html#LIBPQ-CONNSTRING) as w... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Utils**
- `crates/common_utils/src/lib.rs` | {"pr_number": 9685, "pr_title": "fix(database): percent-encode spaces in Postgres connection URI", "merged_at": "2025-10-06T18:21:44Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["merchant", "user"]}, "hierarchy": {"utils": ["crates/common_utils/src/lib.rs"]}, "change_types": {}, ... |
<!-- Describe your changes in detail -->
Add support for confirmation flow for click to pay
currenlty in cick to pay we do authentication with mastercard and authorisation with adyen.
But to be prod certified mastercard needs a confirmation notification from hyperswitch after authorisation stating the state... | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/router_flow_types/unified_authentication_service.rs`
- `crates/hyperswitch_domain_models/src/router_request_types.rs`
- `crates/hyperswi... | {"pr_number": 6982, "pr_title": "feat(core): add support for confirmation flow for click to pay", "merged_at": "2025-02-20T08:04:39Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/router_fl... |
<!-- Describe your changes in detail --> | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/admin.rs`
**2. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/router_data.rs`
- `crates/hyperswitch_domain_models/src/rou... | {"pr_number": 8133, "pr_title": "feat(core/connector): introduce authentication token flow and add sepa bankdebit for nordea", "merged_at": "2025-08-11T07:26:26Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/... |
Hotfix for https://github.com/juspay/hyperswitch/pull/7956 | 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` | {"pr_number": 7959, "pr_title": "fix(connector): [Novalnet] allow debit card MITs", "merged_at": "2025-05-05T12:34:09Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "card"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors/novalnet/transformers... |
Add a version column in process tracker table. This PR also includes the changes for filtering the range queries based on the versions | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/process_tracker.rs`
- `crates/diesel_models/src/query/process_tracker.rs`
- `crates/diesel_models/src/schema.rs`
- ... and 1 more files
**2. ... | {"pr_number": 7389, "pr_title": "feat(process_tracker): Add a version column in process tracker table", "merged_at": "2025-03-11T10:44:24Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"database": ["crates/diesel_models/src/process_tracker.rs", "crates/diese... |
<!-- Describe your changes in detail -->
Adding nanosecond level precision to kafka messages for sessionizer | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Other**
- `crates/router/src/services/kafka/dispute_event.rs`
- `crates/router/src/services/kafka/payment_attempt_event.rs`
- `crates/router/src/services/kafka/payment_intent_event.rs`
- ... and 1 more file... | {"pr_number": 6771, "pr_title": "refactor(kafka_message): NanoSecond precision for consolidated logs", "merged_at": "2024-12-12T10:18:40Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user", "session"]}, "hierarchy": {"other": ["crates/router/src/services/kafka/dispute_event.rs", ... |
<!-- Describe your changes in detail -->
Allow user to configure allowed auth methods for google pay | 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": 7425, "pr_title": "chore(wasm): show allowed auth methods option in google pay", "merged_at": "2025-03-11T10:11:29Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"connectors": ["crates/connector_configs/toml/development.toml", "crates/connector... |
<!-- Describe your changes in detail -->
https://github.com/juspay/hyperswitch/pull/7393 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/router/src/connector/adyen/transformers.rs` | {"pr_number": 7400, "pr_title": "fix(connector): GooglePay fixed in Ayden ", "merged_at": "2025-03-03T11:18:28Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/router/src/connector/adyen/transformers.rs"]}, "ch... |
Added Xendit Cards & Mandates Flow | 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/connector_integration_v2_impls.rs`
- `crates/router/src/core/payments/flows.rs`
**2. External Connector Integration... | {"pr_number": 6966, "pr_title": "feat(connector): [Xendit] ADD Cards & Mandates Flow ", "merged_at": "2025-01-15T10:51:54Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core/admin.rs", "crates/r... |
<!-- Describe your changes in detail -->
Added a new justfile recipe to run v2 migrations compatible with v1 schema.
Refactor v2 migration:
* move all v1 compatible migrations to a separate directory.
* refactor just commands to run the migration scripts as per the new directory structure. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Other**
- `justfile`
- `v2_migrations/2024-07-29-155137_add_v2_soft_delete_db_enum/down.sql`
- `v2_migrations/2024-07-29-155137_add_v2_soft_delete_db_enum/up.sql`
- ... and 6 more files
**Code Patterns App... | {"pr_number": 7415, "pr_title": "chore: add migrate_v2_compatible recipe in justfile", "merged_at": "2025-03-07T13:52:56Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"other": ["justfile", "v2_migrations/2024-07-29-155137_add_v2_soft_delete_db_enum/down.sql... |
<!-- Describe your changes in detail -->
send xid as none for external 3ds payments
Main PR - https://github.com/juspay/hyperswitch/pull/7577 | 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 (3 changes) | {"pr_number": 7576, "pr_title": "fix(connector): [CYBERSOURCE] send xid as none for external 3ds payments", "merged_at": "2025-03-20T05:41:50Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors/cyber... |
<!-- Describe your changes in detail -->
This Pr provides support to change `revenue_recovery_retry_algorithm_type` under the profile using ProfileUpdate API. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/admin.rs`
**2. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/business_profile.rs`
**3. Core Business Logic**
- `crates/... | {"pr_number": 8858, "pr_title": "feat(api): Adds support to change reveue_recovery_retry_algorithm_type using UpdateProfileAPI (V2)", "merged_at": "2025-08-08T09:24:32Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/a... |
- Implement InstantBankTransferFinland for Trustpay
- Implement InstantBankTransferPoland for Trustpay
- Also fixes typos in the repo | 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": 7925, "pr_title": "feat(connector): [trustpay] introduce instant bank_transfer, finland and poland", "merged_at": "2025-06-13T07:05:32Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/s... |
Created from #4674
This covers adding events for `CompleteAuthorize` operation
## How did you test it
Use `globalpay` as connector, `wallet` as payment_method and `paypal` as payment_method_type
```bash
"payment_method": "wallet",
"payment_method_types": [
{
... | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payments/operations/payment_complete_authorize.rs`
**2. Other**
- `crates/router/src/events/audit_events.rs`
**Code Patterns Applied:**
- Extend existing types with new... | {"pr_number": 6310, "pr_title": "feat(events): add audit event for CompleteAuthorize", "merged_at": "2024-12-05T07:46:26Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core/payments/operations/payment... |
This PR updates the payout MCA creation to use `sepa_bank_transfer` instead of `sepa`. | 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": 9536, "pr_title": "chore(wasm): update sepa to sepa_bank_transfer for payout MCAs", "merged_at": "2025-09-25T07:49:03Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"connectors": ["crates/connector_configs/toml/development.toml", "crates/connector_co... |
Support tenant id in user roles queries. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/query/user_role.rs`
**2. Core Business Logic**
- `crates/router/src/core/user.rs`
- `crates/router/src/core/user_role.rs`
**3. Type Definitions... | {"pr_number": 6661, "pr_title": "feat(users): add tenant id reads in user roles", "merged_at": "2024-11-29T10:54:00Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"database": ["crates/diesel_models/src/query/user_role.rs"], "core_business": ["crates/router/s... |
<!-- Describe your changes in detail -->
In One-off payments, we donot need to create the token. Just passing raw cards would be enough.
In CITs, we need to create a token and store it in `connector_mandate_id` for future MITs but while executing the CIT, raw cards need to be passed.
In MITs, we need to use that pr... | 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/payment_methods.rs`
- `crates/router/src/core/payme... | {"pr_number": 8568, "pr_title": "fix(connector): [GLOBALPAY] Added Tokenization Flow for CITs", "merged_at": "2025-07-29T12:54:12Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/route... |
<!-- Describe your changes in detail -->
For connector Datatrans add new payment status: ChallengeOngoing and ChallengeRequired
Fix Deseralization Issue on Force Sync Flow | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/datatrans/transformers.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (2 changes) | {"pr_number": 7331, "pr_title": "fix(connector): [DATATRANS] Fix Force Sync Flow", "merged_at": "2025-02-21T10:42:56Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors/datatr... |
<!-- Describe your changes in detail -->
Multiple SDK queries fixed:
1. Modified field_type text to some unique enum
2. Corrected multiple required fields
3. Voucher payments error billing.phone.number is required fixed
4. Cashapp and Swish payment_experience fixed.
5. Preprocessing to be done only for Givex in... | 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/address.rs`
**3. Core Business Logic**
- `crates/router/sr... | {"pr_number": 7380, "pr_title": "refactor(dynamic_fields): Multiple SDK queries fixed", "merged_at": "2025-03-20T10:55:17Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/enums.rs"], "domain": ["... |
Hotfix for https://github.com/juspay/hyperswitch/pull/7251 | 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`
- `crates/hyperswitch_connectors/src/utils.rs`
**Code Patterns Applied:**
- Implement new functions (4 c... | {"pr_number": 7261, "pr_title": "fix(connectors): [fiuu] zero amount mandate flow for wallets", "merged_at": "2025-02-13T12:53:38Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors/novalnet/transformers.rs",... |
Added `hyperswitch-demo` to the Docker Compose setup to provide a visual interface for the SDK.
## Motivation and Context
This addition enables merchants to preview and interact with the SDK in a demo environment, improving the overall developer experience.
## How Did You Test It?
Via running and generating... | To implement this **validation** feature, you'll need to modify these architectural layers:
**1. Configuration Files**
- `docker-compose.yml`
**Code Patterns Applied:**
- Extend existing types with new fields (14 changes) | {"pr_number": 7841, "pr_title": "chore: add hyperswitch-react-demo-app to docker-compose", "merged_at": "2025-04-24T13:44:58Z", "intent": {"feature_type": "validation", "action": "add_feature", "entities": ["merchant"]}, "hierarchy": {"config": ["docker-compose.yml"]}, "change_types": {"fields_added": 14}, "has_identif... |
1. Added **created_at** (time at which authentication completed) in Authentication Flow
2. Reused **created_at** field from AuthenticationStore, since all 3ds connectors do not send this field in authentication response
3. Used this field **created_at** for 3ds external authentication payments for Cybersource.( S... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/router_request_types.rs`
**2. Core Business Logic**
- `crates/router/src/core/payments/types.rs`
**3. External Connector Integratio... | {"pr_number": 8661, "pr_title": "feat(core): add authentication date in Authentication Flow", "merged_at": "2025-07-22T15:09:37Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/router_... |
Docker pull from latest stable tag | To implement this **validation** feature, you'll need to modify these architectural layers:
**1. Configuration Files**
- `docker-compose.yml`
**Code Patterns Applied:**
- Extend existing types with new fields (2 changes) | {"pr_number": 7701, "pr_title": "fix: web-docker pull from docker hub", "merged_at": "2025-04-02T10:24:08Z", "intent": {"feature_type": "validation", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"config": ["docker-compose.yml"]}, "change_types": {"fields_added": 2}, "has_identifier_data": false, "commi... |
Enhanced powertranz Connector in cypress for Comprehensive Testing.
## How did you test it?
PowerTranz
<img width="561" alt="Powertrans" src="https://github.com/user-attachments/assets/33f89770-1566-4503-b52e-77e809e082f7" />
Alway 3ds payments are getting failed and there is no error code and message
## Che... | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. Tests**
- `cypress-tests/cypress/e2e/configs/Payment/PowerTranz.js`
- `cypress-tests/cypress/e2e/configs/Payment/Utils.js`
**Code Patterns Applied:**
- Extend existing types with new fields (537 changes) | {"pr_number": 8452, "pr_title": "ci(cypress): Add test for powertranz connector", "merged_at": "2025-06-24T14:22:46Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["payment", "user", "connector"]}, "hierarchy": {"tests": ["cypress-tests/cypress/e2e/configs/Payment/PowerTranz.js", "cypress... |
<!-- Describe your changes in detail -->
added barclaycard 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/configs.rs`
**2. Core Business Logic**
- `crates/router/src/core/admin.rs`
**3. External Connector Integration**
- `crates/commo... | {"pr_number": 8017, "pr_title": "feat(connector): add barclaycard template code", "merged_at": "2025-05-20T12:15:42Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["card"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/configs.rs"], "core_business": ["crates/router... |
1. We are sending type twice in paymentMethod.This PR fixes it.
<img width="1728" alt="Screenshot 2024-12-11 at 14 22 04" src="https://github.com/user-attachments/assets/dc362465-48a7-4398-9f9b-5b875960110c">
2. Line 2 is not mandatory in Adyen, but we have mandated it. This PR fixes it.
3. We are sending keys whi... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/router/src/connector/adyen/transformers.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (6 changes)
- Add conditional logic for feature flags or fil... | {"pr_number": 6803, "pr_title": "feat(connector): [Adyen ] Add fixes for AdyenPaymentRequest struct", "merged_at": "2024-12-16T13:15:19Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/router/src/connector/adye... |
<!-- Describe your changes in detail -->
Previously we were generating invoice_number randomly. This PR helps to populate it from `merchant_order_reference_id` if passed in payload. | 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 (8 changes) | {"pr_number": 8635, "pr_title": "feat(connector): [AUTHORIZEDOTNET] custom invoice number populated", "merged_at": "2025-07-15T11:45:43Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/sr... |
<!-- Describe your changes in detail -->
This PR introduces **authentication validation checks** in the following APIs to prevent unauthorized access across organizations: | 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/user.rs`
**2. Type Definitions**
- `crates/router/src/types/domain/user.rs`
**3. Other**
- `crates/router/src/routes/adm... | {"pr_number": 8103, "pr_title": "fix(authentication): add Organization context validation in `Merchant Create` and `Merchant List` APIs", "merged_at": "2025-05-27T10:24:45Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"core_business":... |
<!-- Describe your changes in detail -->
Add support to run local email server in docker-compose. User can see the email we send even in local setup | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Configuration Files**
- `config/docker_compose.toml`
- `docker-compose.yml`
**Code Patterns Applied:**
- Extend existing types with new fields (4 changes) | {"pr_number": 6869, "pr_title": "feat(email): Add mailhog by default in docker-compose for local smtp server", "merged_at": "2025-01-21T10:39:56Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"config": ["config/docker_compose.toml", "docker-compose.yml"]}, "... |
<!-- Describe your changes in detail -->
- RELATED PR : https://github.com/juspay/hyperswitch/pull/9581
- Refunds via authorizedot net are getting into `pending` state where no connector call is made
- This happens when `connector_metadata` is empty in attempt table
- In usual cases `connector_metadata` is no... | 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:**
- Implement new functions (2 changes)
- Extend existing types with new fi... | {"pr_number": 9602, "pr_title": "fix(authorizedotnet): refund via ucs missing connector_metadata", "merged_at": "2025-09-30T06:40:32Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/c... |
Add NTID flow for checkout connector.
For mandate payment, changed payment type from `Recurring` to `Unscheduled`. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/checkout.rs`
- `crates/hyperswitch_connectors/src/connectors/checkout/transformers.rs`
**2. Tests**
- `config/deployments/integ... | {"pr_number": 9449, "pr_title": "feat(connector): [checkout] Add NTID flow", "merged_at": "2025-09-24T14:07:54Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors/checkout.rs"... |
Added the list mandate and revoke mandates for zero auth mandate payment
Removed the fiuu hardcoded checks which is invalid for few connectors | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `cypress-tests/cypress/e2e/PaymentTest/00013-ListAndRevokeMandate.cy.js`
- `cypress-tests/cypress/support/commands.js`
**Code Patterns Applied:**
- Add conditional logic for feature flags or filtering ... | {"pr_number": 6569, "pr_title": "ci(cypress): Add list and revoke for zero auth mandate payments", "merged_at": "2024-11-26T09:19:28Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user", "connector"]}, "hierarchy": {"tests": ["cypress-tests/cypress/e2e/PaymentTest/00013... |
- Hotfix for https://github.com/juspay/hyperswitch/pull/7815
- add AT,DE,IT country for instant_banktransfer | 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": 7816, "pr_title": "feat(configs): [Trustpay] add support for AT,DE,IT country for instant_banktransfer", "merged_at": "2025-04-15T13:56:50Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"tests": ["config/deployments/i... |
<!-- Describe your changes in detail -->
Added `no-3ds cards` flow for new connector `Getnet` | 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/router_request_types.rs`
**3. Core Business Logic**
- `cra... | {"pr_number": 7256, "pr_title": "feat(connector): [GETNET] Add cards payment flow", "merged_at": "2025-03-17T15:00:18Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/enums.rs"], "domain": ["crat... |
<!-- Describe your changes in detail -->
main pr: https://github.com/juspay/hyperswitch/pull/7556
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 ad05791f:
Files to modify:
**crates/router/s... | {"pr_number": 7557, "pr_title": "refactor(core): Revert \"filter default routing config response based on connector type\"", "merged_at": "2025-03-18T16:25:03Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "connector", "token"]}, "hierarchy": {"core_business": ["crates/r... |
<!-- Describe your changes in detail -->
Fix for this PR: [https://github.com/juspay/hyperswitch/pull/5870](https://github.com/juspay/hyperswitch/pull/5870)
- Additional filters are added to `PaymentIntentFilters` as new analytics APIs are expected to be calculated from `Sessionizer Payment Intents` table.
- Exist... | 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": 6403, "pr_title": "feat(analytics): remove additional filters from PaymentIntentFilters", "merged_at": "2024-10-23T06:51:07Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"api_models": ["crates/api_models/src/analytics/pa... |
<!-- Describe your changes in detail -->
Add support for payout webhooks in Paypal and Wise.
Wise requires MTLS Webhook Support (No algo). | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/paypal.rs`
- `crates/hyperswitch_connectors/src/connectors/paypal/transformers.rs`
- `crates/hyperswitch_connectors/src/connecto... | {"pr_number": 8888, "pr_title": "feat(payouts): add payout webhooks for Paypal and Wise", "merged_at": "2025-08-11T14:01:51Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "merchant", "order"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors/p... |
<!-- Describe your changes in detail -->
propagate network transaction id stored in payment method's table to response of 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. Core Business Logic**
- `crates/router/src/core/payments.rs`
- `crates/router/src/core/payments/transformers.rs`
**3. Tests**
- `cr... | {"pr_number": 8829, "pr_title": "refactor(core): propagate network_transaction_id in response of payment", "merged_at": "2025-08-05T16:18:02Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/payme... |
Adds the billing_connector_payment_sync config to sandbox, integ and production.toml | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `config/deployments/integration_test.toml`
- `loadtest/config/development.toml`
**2. Configuration Files**
- `config/deployments/production.toml`
- `config/deployments/sandbox.toml` | {"pr_number": 7708, "pr_title": "fix(config): add billing payment sync configs in different environments", "merged_at": "2025-04-04T10:03:04Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "connector"]}, "hierarchy": {"tests": ["config/deployments/integration_test.toml", ... |
Hotfix for [PR](https://github.com/juspay/hyperswitch/pull/7589)
`cargo clippy` output
<img width="1098" alt="Screenshot 2025-03-25 at 5 12 09 PM" src="https://github.com/user-attachments/assets/e191b508-e831-41ef-a138-1d2ca89f6a53" /> | 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`
**3. Core Busi... | {"pr_number": 7627, "pr_title": "feat(core): add three_ds_requestor_app_url in business_profile", "merged_at": "2025-03-25T13:25:01Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"api_models": ["crates/api_models/src/admin.rs", "crates/api_models/src/payment... |
<!-- Describe your changes in detail -->
This PR will allow to pass the Decrypted Payload(GooglePay) directly in the Payments Confirm call | 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`
- `crates/hyperswitch_domain_mod... | {"pr_number": 8865, "pr_title": "feat(router): add support for GooglePay pre-decrypted token in the payments confirm call ", "merged_at": "2025-08-08T11:53:22Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/ap... |
<!-- Describe your changes in detail -->
Updates creds. closes #6645 | 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": 6726, "pr_title": "ci: update cypress creds", "merged_at": "2024-12-03T17:19:14Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"tests": [".github/workflows/cypress-tests-runner.yml"]}, "change_types": {"fields_added": 1}, "has_identifier_data": false... |
<!-- Describe your changes in detail -->
Connector template code for new connector `Nordea`.
Developer Docs: https://developer.nordeaopenbanking.com/documentation
Login Dashboard: https://developer.nordeaopenbanking.com/login | 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": 8056, "pr_title": "feat(connector): [nordea] template code", "merged_at": "2025-05-21T07:49:27Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["connector"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/configs.rs"], "core_business": ["crates/router/s... |
Enhanced shift4 Connector in cypress for Comprehensive Testing.
Added ideal,eps bank redirect testcases aswell
## How did you test it?
<img width="562" alt="swift4" src="https://github.com/user-attachments/assets/7fdc1f02-83c6-48de-b076-6863c121d67f" />
Failure Reason
1.3ds payment are failing with error_mes... | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. Tests**
- `cypress-tests/cypress/e2e/configs/Payment/Shift4.js`
- `cypress-tests/cypress/e2e/configs/Payment/Utils.js`
- `cypress-tests/cypress/support/redirectionHandler.js`
**Code Patterns Applied:**
- Extend exi... | {"pr_number": 8385, "pr_title": "ci(cypress): Add shift4 connector test in cypress", "merged_at": "2025-06-20T13:55:33Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["payment", "user", "connector"]}, "hierarchy": {"tests": ["cypress-tests/cypress/e2e/configs/Payment/Shift4.js", "cypress-... |
<!-- Describe your changes in detail -->
main pr - https://github.com/juspay/hyperswitch/pull/7828 | 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": 7869, "pr_title": "fix(connector): [Cybersource] send type selection indicator for co-batch cards", "merged_at": "2025-04-22T17:32:47Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors/cybersou... |
<!-- Describe your changes in detail -->
fix connector configs for wasm build. | 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/connector.rs`
- `crates/connector_configs/toml/production.toml`
- ... and 1 more files
**2. Configur... | {"pr_number": 6832, "pr_title": "fix(wasm): fix feature dependencies in `connector_configs` crate for WASM builds ", "merged_at": "2024-12-23T14:39:31Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["connector"]}, "hierarchy": {"connectors": ["crates/connector_configs/Cargo.toml", "... |
Update creds for noon and stripe | 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": 8069, "pr_title": "chore(cypress): Update creds for stripe", "merged_at": "2025-05-19T09:26:43Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"tests": [".github/workflows/cypress-tests-runner.yml"]}, "change_types": {"fields_added": 1}, "has_identifi... |
<!-- Describe your changes in detail -->
Main PR - https://github.com/juspay/hyperswitch/pull/6308 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payment_methods.rs`
- `crates/router/src/core/payments/helpers.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (2 changes)
- Add conditional... | {"pr_number": 6320, "pr_title": "fix(router): update nick_name only if card_token.card_holder_name is non empty and populate additional card_details from payment_attempt if not present in the locker", "merged_at": "2024-10-15T11:40:54Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": [... |
Populated network_advice_code, network_decline_code and network_error_response in ErrorResponse. Also added integrity check support for Authorize, Capture, Refund, PSync and RSync flows.
What is an integrity check?
A scenario where there is a discrepancy between the amount sent in the request and the amount receiv... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/fiserv.rs`
- `crates/hyperswitch_connectors/src/connectors/fiserv/transformers.rs`
**Code Patterns Applied:**
- Define new data st... | {"pr_number": 8075, "pr_title": "feat(connector): [FISERV] Added Integrity Check support for all Payment & Refund Flows", "merged_at": "2025-06-02T07:07:31Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyper... |
<!-- Describe your changes in detail -->
use redis to store card cvc temporarily for retrieval through payment token | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payment_methods.rs`
- `crates/router/src/core/payment_methods/vault.rs`
- `crates/router/src/core/payments/operations/payment_confirm_intent.rs`
**Code Patterns... | {"pr_number": 8429, "pr_title": "feat(payment_methods): card_cvc retrieval through payment_token", "merged_at": "2025-06-22T20:20:26Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "token", "card"]}, "hierarchy": {"core_business": ["crates/router/src/core/payment_methods.... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.