prompt stringlengths 6 90.9k | response stringlengths 121 18.6k | metadata stringlengths 314 42.3k |
|---|---|---|
<!-- Describe your changes in detail -->
Added Support for Domestic Card Network
Added Mandatory Fields for 3ds -transactions | 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_data.rs`
**2. Core Business Logic**
- `crates/router/src/core/payments/flows.rs`
- `crates/router/src/core/payments/flows/... | {"pr_number": 7603, "pr_title": "fix(connectors): [Hipay] Fix 3DS Mandatory Fields", "merged_at": "2025-04-01T18:13:59Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user", "card", "transaction"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/router_data.rs"], "c... |
<!-- Describe your changes in detail -->
This PR fixes two critical issues in Adyen Platform connector and payout core flow error handling:
1. **Enhanced error message construction**: Modified `build_error_response` in `crates/hyperswitch_connectors/src/connectors/adyenplatform.rs` to include the `detail` field w... | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payouts.rs`
**2. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/adyenplatform.rs`
- `crates/hyperswitch_connectors/src/connectors/ad... | {"pr_number": 9384, "pr_title": "fix(connector): [adyenplatform] update error mapping", "merged_at": "2025-09-18T14:31:52Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["customer", "merchant", "user"]}, "hierarchy": {"core_business": ["crates/router/src/core/payouts.rs"], "connectors": [... |
<!-- Describe your changes in detail -->
add proxy card as a valid payment method subtype for cards | 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` | {"pr_number": 9136, "pr_title": "fix(payment_method): add validation for proxy card details", "merged_at": "2025-09-01T15:28:44Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "card"]}, "hierarchy": {"api_models": ["crates/api_models/src/payment_methods.rs"]}, "change_typ... |
<!-- Describe your changes in detail -->
This PR forces users to use 2FA in production. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Configuration Files**
- `config/deployments/production.toml` | {"pr_number": 6596, "pr_title": "refactor(users): Force 2FA in production environment", "merged_at": "2024-11-19T13:18:51Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"config": ["config/deployments/production.toml"]}, "change_types": {}, "has_identifier_da... |
<!-- Describe your changes in detail -->
This PR marks refunds as supported by JPMorgan connector. Although this does not affect refund flow, the feature matrix marking is wrong. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/jpmorgan.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (2 changes) | {"pr_number": 8699, "pr_title": "fix(feature_matrix): refunds are supported by jpmorgan", "merged_at": "2025-07-24T13:32:53Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "refund", "connector"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors/... |
This PR contains changes to
- update status mapping for Worldpay - payments and refunds
- add required fields for Worldpay
- fix refund retrieve bug for Worldpay
Described in detail - #6316 point # 5 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/query/payment_attempt.rs`
**2. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/payments/payment_attempt.rs`
**3. Co... | {"pr_number": 6468, "pr_title": "feat(connector): worldpay - add dynamic fields and update terminal status mapping", "merged_at": "2024-11-28T14:50:09Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user", "refund"]}, "hierarchy": {"database": ["crates/diesel_models/src/... |
This PR adds a diesel migration for including below variants in Currency ENUM in database
```AFN
BTN
CDF
ERN
IRR
ISK
KPW
SDG
SYP
TJS
TMT
ZMW
ZWL
``` | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Other**
- `migrations/2025-01-03-084904_add_currencies/down.sql`
- `migrations/2025-01-03-084904_add_currencies/up.sql`
**Code Patterns Applied:**
- Modify database queries (4 changes) | {"pr_number": 6980, "pr_title": "chore: add migrations for Currency type in DB", "merged_at": "2025-01-03T11:24:28Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"other": ["migrations/2025-01-03-084904_add_currencies/down.sql", "migrations/2025-01-03-084904_add_cu... |
<!-- Describe your changes in detail -->
https://github.com/juspay/hyperswitch/pull/6911
Fix required fileds for wallet mandate payments for cybersource and bank of america. | 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 (8 changes) | {"pr_number": 6921, "pr_title": "fix(connector): [Cybersource] fix the required fields for wallet mandate payments", "merged_at": "2024-12-23T14:13:00Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/router/src... |
<!-- 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. 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/connec... | {"pr_number": 8246, "pr_title": "feat(connectors): [Worldpayvantiv] add card support", "merged_at": "2025-06-05T06:25:48Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core/admin.rs"], "connecto... |
<!-- Describe your changes in detail -->
change amount conversion from MInorUnit to FloatMajorUnit
hotfix raised against https://github.com/juspay/hyperswitch/pull/8991 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/wise.rs`
- `crates/hyperswitch_connectors/src/connectors/wise/transformers.rs`
**Code Patterns Applied:**
- Implement new function... | {"pr_number": 8995, "pr_title": "fix(connector): [Wise] change amount conversion unit", "merged_at": "2025-08-19T15:29:21Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors/w... |
<!-- Describe your changes in detail -->
This PR is about adding ApplePay Payment Method in Hyperswitch. This has both the Hyperswitch level Decryption Flow as well as the Connector Level Decryption Flow.
NOTE: The connector returns an error as missing fields probably because this particular payment method is not e... | 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": 8670, "pr_title": "feat(connector): [FISERV] Added ApplePay Wallet", "merged_at": "2025-08-12T07:25:47Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/connector_configs/toml/development.toml", "c... |
Added Cards flow for Elavon (ThreeDs not implemented)
Added Mandates Flow
Void Flow is not available for Elavon | 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. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/router_request_types.rs`
**3. Core Business Logic**... | {"pr_number": 6485, "pr_title": "feat(connector): [Elavon] Implement cards Flow", "merged_at": "2024-11-25T14:38:04Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/connector_enums.rs"], "domain"... |
- 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": 7815, "pr_title": "feat(configs): [Trustpay] add support for AT,DE,IT country for instant_banktransfer", "merged_at": "2025-04-15T13:48:28Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"tests": ["config/deployments/i... |
<!-- Describe your changes in detail -->
We are filtering the response for payment and payout processors.
So this works as follows:
If Payment's route is hit only PaymentProcessors will be listed and nothing else like PayoutConnectors etc.
Payment :
```
curl --location 'http://localhost:8080/routing/default/pro... | 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:**
- Extend existing types with new fields (1 changes)
- Modify database queries (1 changes)
**Detailed Identifier Changes:**
C... | {"pr_number": 7199, "pr_title": "refactor(core): filter default routing config response based on connector type", "merged_at": "2025-03-11T15:00:03Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user", "connector"]}, "hierarchy": {"core_business": ["crates/router/src/co... |
<!-- Describe your changes in detail -->
Postman Tests for `nmi` were failing on SBX (but not on Integ) because `Flow Testcases/Variation Cases/Scenario9-Create a mandate payment` responded an error message as `debit mandate payment is not supported by nmi` on SBX and `credit mandate payment is not supported by nmi` o... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `postman/collection-dir/nmi/Flow Testcases/Variation Cases/Scenario9-Create a mandate payment/Payments - Create/event.test.js`
**2. Other**
- `postman/collection-dir/nmi/Flow Testcases/Variation Cases/... | {"pr_number": 7765, "pr_title": "ci(postman): update assertion error message for nmi collection", "merged_at": "2025-04-17T07:51:28Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user", "card"]}, "hierarchy": {"tests": ["postman/collection-dir/nmi/Flow Testcases/Variati... |
<!-- Describe your changes in detail -->
This PR adds a new NetworkDetails struct containing network_advice_code to capture network-level response information from payment processors.
Key Changes:
1)Added network_details JSONB column to payment_attempt table
2)Extended PaymentsResponse API to include optional n... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/payments.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/payment_attempt.rs`
- `crates/diesel_models/src/schema.rs`
- `crates... | {"pr_number": 9273, "pr_title": "feat(core): Add Network Details in Payments Response", "merged_at": "2025-09-09T14:10:52Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/payments.rs"], "database... |
<!-- Describe your changes in detail -->
Connector Feature Matrix Bugfix:
1. Removed Dispute webhook from stax
2. Capture methods added in Inespay
3. Card Authentication type corrected in Fiserv and Bluesnap
4. Added Refund webhook in shift4.
<img width="1728" alt="Screenshot 2025-05-16 at 5 45 57 PM" src="http... | 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": 8047, "pr_title": "fix(connector): Connector Feature Matrix Bugfix", "merged_at": "2025-05-22T10:40:05Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/connector_configs/toml/development.toml", "c... |
<!-- Describe your changes in detail -->
- Accept merchant_connector_credentials in the Request Body of Refunds create and retrieve
- Add a new POST endpoint refunds_retrieve_with_gateway_creds | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/payments.rs`
- `crates/api_models/src/refunds.rs`
**2. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/merchant_connector_... | {"pr_number": 8441, "pr_title": "feat(core): accept merchant_connector_details in Refunds create and retrieve flow", "merged_at": "2025-06-26T14:23:16Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models... |
<!-- Describe your changes in detail -->
Enhanced the script to pre-configure a user and a dummy connector in the control center for the local setup. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Other**
- `README.md`
- `scripts/setup.sh`
**Code Patterns Applied:**
- Add conditional logic for feature flags or filtering (18 changes) | {"pr_number": 8093, "pr_title": "fix: updated the docker setup", "merged_at": "2025-05-21T09:51:53Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user", "connector"]}, "hierarchy": {"other": ["README.md", "scripts/setup.sh"]}, "change_types": {"conditionals_added": 18}, "has_ident... |
<!-- Describe your changes in detail -->
A recent change in [this PR](https://github.com/juspay/hyperswitch/pull/7537) removed the usage of DomainStorageError in all the places and started using StorageError everywhere.
Previously, DataStorage and RedisError were manually converted into StorageError based on few c... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Other**
- `crates/storage_impl/src/errors.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (2 changes) | {"pr_number": 7712, "pr_title": "fix(errors): Entry not found error as 4xx instead of 5xx", "merged_at": "2025-04-03T12:18:30Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"other": ["crates/storage_impl/src/errors.rs"]}, "change_t... |
Cards Non-3DS payments added for silverflow (Alpha Integration).
Ref: https://www.silverflow.com/ | 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": 8591, "pr_title": "feat(connector): [SILVERFLOW] Integrate cards non 3ds payments", "merged_at": "2025-07-24T06:43:09Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "card"]}, "hierarchy": {"connectors": ["crates/connector_configs/toml/development.toml", "cr... |
<!-- Describe your changes in detail -->
Adyen now uses `connector_customer_id` to form `shopper_reference` if the field is present, else falls to previous implementation. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/adyen/transformers.rs`
**2. Tests**
- `config/deployments/integration_test.toml`
- `loadtest/config/development.toml`
**3. Con... | {"pr_number": 8447, "pr_title": "fix(connector): adyen connector creates connector's customer reference on the fly fixed", "merged_at": "2025-06-24T17:23:39Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "user", "connector"]}, "hierarchy": {"connectors": ["crates/hypers... |
Changed the query to apply the merchant_id filter after the join. This ensures valid rows aren’t excluded too early and fixes an issue where **payments with the same IDs but different merchants** were being handled incorrectly. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Other**
- `crates/storage_impl/src/payments/payment_intent.rs`
**Code Patterns Applied:**
- Modify database queries (7 changes) | {"pr_number": 6917, "pr_title": "fix(payments_list): handle same payment/attempt ids for different merchants", "merged_at": "2024-12-24T13:29:37Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"other": ["crates/storage_impl/src/paym... |
Context: In case of some billing connectors we dont get the enough data in the webhook itself to support creation of payment intent and payment attempt in our system. So previously we derived a flow named "AdditionalRevenuerecoveryDetails" in this PR:#7402 which name is now changed to "BillingConnectorPaymentSync". Th... | 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. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/revenue_recovery.rs`
- `crates/hyperswitch_domain_models... | {"pr_number": 7461, "pr_title": "feat(connector): Add recovery support for stripebilling", "merged_at": "2025-04-02T07:49:57Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"api_models": ["crates/api_models/src/webhooks.rs"], "domain": ... |
<!-- Describe your changes in detail -->
This pull request adds support pass the decryted apple pay token directly in the confirm call.
This pull also request introduces significant changes to the handling of Apple Pay payment data across multiple modules, improving the structure, validation, and usage of encrypted... | 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": 8815, "pr_title": "feat(router): add support for apple pay pre-decrypted token in the payments confirm call", "merged_at": "2025-08-05T08:19:29Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api... |
<!-- Describe your changes in detail -->
During the MIT if the decided connector is same as the connector with which the mandate is created then the MIT should be processed with the connector mandate _id. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payments.rs`
**Code Patterns Applied:**
- Add conditional logic for feature flags or filtering (1 changes) | {"pr_number": 7081, "pr_title": "refactor(router): prioritise `connector_mandate_id` over `network_transaction_id` during MITs", "merged_at": "2025-01-28T21:02:35Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["cr... |
<!-- Describe your changes in detail -->
Wasm fix for xendit connector
## Checklist
<!-- Put an `x` in the boxes that apply -->
- [ ] I formatted the code `cargo +nightly fmt --all`
- [ ] I addressed lints thrown by `cargo clippy`
- [ ] I reviewed the submitted code
- [ ] I added unit tests for my changes ... | 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": 7459, "pr_title": "fix(dashboard): Wasm fix for xendit connector", "merged_at": "2025-03-07T10:24:04Z", "intent": {"feature_type": "connector_integration", "action": "add_feature", "entities": ["connector"]}, "hierarchy": {"connectors": ["crates/connector_configs/toml/development.toml", "crates/connector_... |
<!-- Describe your changes in detail -->
hotfix PR for https://github.com/juspay/hyperswitch/pull/6519 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payments/operations/payment_confirm.rs`
- `crates/router/src/core/payments/operations/payment_create.rs`
- `crates/router/src/core/payments/transformers.rs`
**C... | {"pr_number": 6557, "pr_title": "fix(payments): populate payment_method_type in payment_attempt for cards", "merged_at": "2024-11-13T13:42:37Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"core_business": ["crates/router/src/core/payments/operations/payment_confi... |
This PR removes billing details as required fields for Worldpay connector. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/payment_methods/src/configs/payment_connector_required_fields.rs` | {"pr_number": 7853, "pr_title": "chore(dynamic-fields): remove billing details as required fields for Worldpay connector", "merged_at": "2025-04-22T08:46:45Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"connectors": ["crates/payment_... |
Added `type_selection_indicator` as 1 for all cards
Reason for this change - Without this field Mastercard card payments are currently failing for a france-based merchant acquirer CMCIC in prod for cybersource, it expects type_selection_indicator as 1.
Please note, this change is a fix on top of this [PR](https:/... | 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 (6 changes)
**Detailed Identifier Ch... | {"pr_number": 8663, "pr_title": "fix(connector): [Cybersource] Add type_selection_indicator as 1 for all cards ", "merged_at": "2025-07-21T14:21:53Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_c... |
Added dispute support for novalnet. Novalnet supports 2 webhook events for disputes
1. Chargeback
2. Representment (dispute won)
Novalnet does not support emails/webhooks for Arbitration and Pre-Arbitration stages. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/novalnet.rs`
- `crates/hyperswitch_connectors/src/connectors/novalnet/transformers.rs`
**Code Patterns Applied:**
- Implement new ... | {"pr_number": 6560, "pr_title": "feat(connector): [Novalnet] Add support for disputes ", "merged_at": "2024-11-18T14:22:01Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user", "webhook"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors/noval... |
<!-- Describe your changes in detail -->
Updated to check if the payment method is Wallet before proceeding with the wallet decryption operation.
main branch pr https://github.com/juspay/hyperswitch/pull/8744 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payments.rs`
**Code Patterns Applied:**
- Add conditional logic for feature flags or filtering (1 changes) | {"pr_number": 8747, "pr_title": "fix(router): add payment method Wallet check for decrypted wallet payment method token logic", "merged_at": "2025-07-24T11:44:58Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["cra... |
<!-- Describe your changes in detail -->
This pull request introduces support for fetching subscription estimates from Chargebee, alongside the existing subscription plans functionality. It adds new data structures, request/response types, and integration logic to handle the "Get Subscription Estimate" flow end-to-end... | 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_data_v2/flow_common_types.rs`
- `crates/hyperswitch_domain_models/src/router_flow_types/subscriptions.rs`
- `crates/hypersw... | {"pr_number": 9336, "pr_title": "feat(subscription): Add support to estimate for a subscription in chargebee", "merged_at": "2025-09-24T16:58:56Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["connector"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/router_data_... |
<!-- Describe your changes in detail -->
This PR updates Hyperswitch Docker images to be prefixed by `docker.juspay.io`. This includes the same changes as #7368, I've cherry picked the same commit.
## Motivation and Context
<!--
Why is this change required? What problem does it solve?
If it fixes an open issue... | To implement this **connector_integration** feature, you'll need to modify these architectural layers:
**1. Configuration Files**
- `config/deployments/README.md`
- `docker-compose-development.yml`
- `docker-compose.yml`
**2. Other**
- `aws/hyperswitch_aws_setup.sh`
**Code Patterns Applied:**
- Extend e... | {"pr_number": 7592, "pr_title": "chore(docker): prefix Hyperswitch Docker image URIs with `docker.juspay.io`", "merged_at": "2025-03-21T11:37:07Z", "intent": {"feature_type": "connector_integration", "action": "add_feature", "entities": []}, "hierarchy": {"config": ["config/deployments/README.md", "docker-compose-devel... |
<!-- Describe your changes in detail --> | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Other**
- `README.md`
- `docs/one_click_setup.md`
- `docs/try_local_system.md`
- ... and 1 more files
**Code Patterns Applied:**
- Add conditional logic for feature flags or filtering (15 changes) | {"pr_number": 7804, "pr_title": "feat(deploy): Add one-click Docker setup script", "merged_at": "2025-05-02T12:35:09Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"other": ["README.md", "docs/one_click_setup.md", "docs/try_local_system.md", "scripts/setup.s... |
Allow update of `connector_mandate_details` for card in case of metadata changes(in case of expiry changes). First the value is set as inactive and if a successful payment has been made then set it back to active | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payments/operations/payment_response.rs`
- `crates/router/src/core/payments/tokenization.rs`
**Code Patterns Applied:**
- Implement new functions (1 changes)
- Ext... | {"pr_number": 6848, "pr_title": "refactor(payment_methods): update `connector_mandate_details` for card metadata changes", "merged_at": "2024-12-27T06:21:58Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user", "connector"]}, "hierarchy": {"core_business": ["crates/rout... |
<!-- Describe your changes in detail -->
When customer_id with length greater than 20 is passed in payload along with email, customer will be created only with email and not id (because length validation will fail). Now when we again use some other customer_id with length greater than 20 with the same email, createCon... | 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 (2 changes) | {"pr_number": 8866, "pr_title": "fix(connector): [AUTHORIZEDOTNET] error for customer already exists refactored", "merged_at": "2025-08-07T12:03:49Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_c... |
<!-- Describe your changes in detail -->
- Developed the proxy-confirm-intent API, specifically designed for Merchant-Initiated Transactions (MIT) payments. This is a generic and reusable API that facilitates MIT payment confirmations.
- Its working is similar to confirm-intent api but in proxy flow we will be not ... | 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`
- `crates/api_models/src/payments.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel... | {"pr_number": 7215, "pr_title": "feat(router): add proxy-confirm-intent api for payments in v2 flow", "merged_at": "2025-03-05T09:02:52Z", "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 -->
Introduced a new field in business_profile (is_pre_network_tokenization_enabled).
Based on that field the card will be tokenized before first payment.
If the payment get succeeded the card and network token data will be stored in the locker afterwards. | 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`
**3. Domain M... | {"pr_number": 6873, "pr_title": "feat(core): [Network Tokenization] pre network tokenization", "merged_at": "2025-05-19T11:07:05Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/admin.rs"], "data... |
<!-- Describe your changes in detail -->
Added `FRM` data in payment request for connector `Adyen` | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/adyen/transformers.rs`
**Code Patterns Applied:**
- Define new data structures (1 changes)
- Implement new functions (4 changes)
- Ex... | {"pr_number": 7615, "pr_title": "refactor(request_body): Added FRM data in payment request", "merged_at": "2025-03-28T12:12:51Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connect... |
To support the transaction monitoring feature for charge bee we need to consume the following fields :
Billing Address details for invoices such as city, state, country, zip and invoices next billing time and retry count.
Since all these details are in invoice level we should be storing them in payment intent. Bill... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/payments.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/types.rs`
**3. Domain Models (Business Logic Types)**
- `crates/hypers... | {"pr_number": 7774, "pr_title": "feat(connector): [chargebee] consumes required fields to support transaction monitoring", "merged_at": "2025-04-16T08:29:29Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_... |
This PR contains the following
- Opened an endpoint to dashboard for process tracker's revenue_recovery workflow to retrieve the schedule time , to display the time the next retry has been scheduled
- Also it includes the naming changes, for consistent naming , we have changed the file names to revenue_recovery inst... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/events.rs`
- `crates/api_models/src/events/revenue_recovery.rs`
- `crates/api_models/src/lib.rs`
- ... and 2 more files
**2. Database Layer (Queries &... | {"pr_number": 7602, "pr_title": "feat(core): Add support for process tracker retrieve api in v2", "merged_at": "2025-03-27T12:12:57Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user"]}, "hierarchy": {"api_models": ["crates/api_models/src/events.rs", "crates/api_models... |
<!-- Describe your changes in detail -->
We need to update traditional chinese locale for payment link expired. | 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 (2 changes) | {"pr_number": 8935, "pr_title": "feat(payment-link): update traditional chinese local", "merged_at": "2025-08-13T10:06:47Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"core_business": ["crates/router/src/core/payment_link/locale.js"]... |
Described in #6609 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Utils**
- `crates/router/src/utils.rs`
**2. Tests**
- `cypress-tests-v2/cypress/e2e/configs/Payment/Commons.js`
- `cypress-tests-v2/cypress/e2e/configs/Payment/Utils.js`
- `cypress-tests/cypress/e2e/Paymen... | {"pr_number": 6610, "pr_title": "refactor: update API response for JSON deserialization errors", "merged_at": "2024-11-21T22:26:21Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"utils": ["crates/router/src/utils.rs"], "tests": ["cypress-tests-v2/cypress/e2e/confi... |
<!-- Describe your changes in detail -->
Adds tenant-id for every requests to keymanager
## Motivation and Context
<!--
Why is this change required? What problem does it solve?
If it fixes an open issue, please link to the issue here.
If you don't have an issue, we'd recommend starting with one first so the P... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Type Definitions**
- `crates/common_utils/src/types/keymanager.rs`
- `crates/router/src/types/domain/types.rs`
**2. Utils**
- `crates/common_utils/src/consts.rs`
- `crates/common_utils/src/id_type/tenant.r... | {"pr_number": 6968, "pr_title": "chore(keymanager): add tenant-id to keymanager requests", "merged_at": "2025-01-06T15:34:01Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"types": ["crates/common_utils/src/types/keymanager.rs", "crate... |
<!-- Describe your changes in detail -->
In the MIT flow when the recurring details is of type "type": "network_transaction_id_and_card_details" the eligible connector needs to be set in the payment attempt. | 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": 6347, "pr_title": "fix(router): set the eligible connector in the payment attempt for nti based mit flow", "merged_at": "2024-10-17T13:55:22Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/rou... |
<!-- Describe your changes in detail -->
Added all_keys_required in confirm and psync payload. If all_keys_required is passed as true, we will send the whole connector response. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/payments.rs`
**2. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/router_data.rs`
**3. Core Business Logic**
- `crates/ro... | {"pr_number": 7998, "pr_title": "feat(core): add all_keys_required in confirm and psync payload", "merged_at": "2025-05-19T14:00:36Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/payments.rs"],... |
- set Instant as the default RefundType | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/analytics/refunds.rs`
- `crates/api_models/src/refunds.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/enums.rs` | {"pr_number": 7824, "pr_title": "refactor(refunds): set Instant as the default RefundType", "merged_at": "2025-04-28T11:50:25Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/analytics/refunds.rs... |
<!-- Describe your changes in detail -->
Added template code for [Checkbook](https://docs.checkbook.io/reference/) | 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": 8494, "pr_title": "feat(connector): [CHECKBOOK] Add Template Code", "merged_at": "2025-07-02T10:27:27Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/configs.rs"], "core_business": ["crates/router/src/c... |
<!-- Describe your changes in detail -->
This pr adds api refs for routing
```
"v1/routing/routing--evaluate",
"v1/routing/routing--feedback",
"v1/routing/routing--rule-evaluate"
```
Moved `RoutingEvaluateRequest`, `RoutingEvaluateResponse`, `DeRoutableConnectorChoice`, `ValueType`, `MetadataValue`, `NumberComp... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/open_router.rs`
- `crates/api_models/src/routing.rs`
**2. Core Business Logic**
- `crates/router/src/core/payments/routing/utils.rs`
**3. Other**
- `... | {"pr_number": 8709, "pr_title": "feat(routing): Add api-refs for new decision engine endpoints", "merged_at": "2025-07-29T11:33:19Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user", "connector"]}, "hierarchy": {"api_models": ["crates/api_models/src/open_router.rs", "crates/api_... |
Add Payment connector template for Worldpayvantiv.
Worldpay Vantiv, also known as the Worldpay CNP API, is a robust XML-based interface used to process online (card-not-present) transactions such as e-commerce purchases, subscription billing, and digital payments
Doc Reference - http://support.worldpay.com/support... | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/configs.rs`
**2. Core Business Logic**
- `crates/router/src/core/admin.rs`
**3. External Connector Integration**
- `crates/common_enum... | {"pr_number": 8226, "pr_title": "feat(connectors): [Template] add Worldpayvantiv ", "merged_at": "2025-06-04T10:31:32Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["payment", "connector", "card"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/configs.rs"], "core_busine... |
<!-- Describe your changes in detail -->
This pull request introduces several improvements to the subscription flow, primarily focused on more robust handling and propagation of billing address information, as well as better error handling for missing required fields. The changes ensure that billing address is consist... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/subscription.rs`
**2. Core Business Logic**
- `crates/router/src/core/subscription.rs`
- `crates/router/src/core/subscription/invoice_handler.rs`
- `c... | {"pr_number": 9788, "pr_title": "refactor: Refactored Response types for subscription APIs", "merged_at": "2025-10-13T11:00:21Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/subscription.rs"], ... |
<!-- Describe your changes in detail -->
This PR resolves the v2 warnings generated in common_utils. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Utils**
- `crates/common_utils/src/id_type/global_id.rs`
- `crates/common_utils/src/id_type/global_id/customer.rs`
- `crates/common_utils/src/id_type/global_id/payment.rs`
- ... and 1 more files
**Code Pat... | {"pr_number": 7358, "pr_title": "chore: resolve v2 warnings in common_utils", "merged_at": "2025-05-13T06:56:09Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"utils": ["crates/common_utils/src/id_type/global_id.rs", "crates/common_utils/src/id_type/global_id/cust... |
Fixed payment failures caused by changes in the Iatapay redirection page by triggering the Simulate button during the redirection flow.
## Motivation and Context
Iatapay UPI is failing due to new element added in the redirection page
## How did you test it?
Ran locally
<img width="1295" height="670" alt="Scr... | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. Tests**
- `cypress-tests/cypress/support/redirectionHandler.js` | {"pr_number": 9811, "pr_title": "ci(cypress): Fix Iatapay UPI redirection", "merged_at": "2025-10-13T11:49:13Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["payment", "user"]}, "hierarchy": {"tests": ["cypress-tests/cypress/support/redirectionHandler.js"]}, "change_types": {}, "has_iden... |
<!-- Describe your changes in detail -->
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": 7525, "pr_title": "feat(connector): [BRAINTREE] Add revoke mandate flow", "merged_at": "2025-03-15T11:52:36Z", "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 fixes the following
1.Maps cnp_txn_id to connector_transaction_id in error responses when cnp_txn_id is present.
2.Enforces maximum length validation for customer_id and connector_request_reference_id.
3.Maps merchant_order_reference to customer_reference. Since we c... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/Cargo.toml`
- `crates/hyperswitch_connectors/src/connectors/worldpayvantiv.rs`
- `crates/hyperswitch_connectors/src/connectors/worldpayvantiv/t... | {"pr_number": 9031, "pr_title": "fix(connectors): [worldpayvantiv] map cnp_txn_id to connector_txn_id and enforce max length for customer_id and connector_request_reference_id", "merged_at": "2025-08-22T13:07:55Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", ... |
<!-- Describe your changes in detail -->
Added Feature Matrix supported payment methods, countries and currencies for Multisafepay, Cashtocode, Worldpay and Wellsfargo. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/cashtocode.rs`
- `crates/hyperswitch_connectors/src/connectors/deutschebank.rs`
- `crates/hyperswitch_connectors/src/connectors/... | {"pr_number": 7149, "pr_title": "feat(connector): [MULTISAFEPAY, CASHTOCODE, WORLDPAY, WELLSFARGO] Supported features for feature matrix", "merged_at": "2025-04-30T09:31:43Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors... |
<!-- Describe your changes in detail -->
Added flag to the CyberSource capture call to indicate the final capture in cases of manual capture.
This flag has been incorporated into the CyberSource capture request body to ensure the issuer bank is informed appropriately.
## How did you test it?
<!--
Did you writ... | To implement this **payment** 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 (1 changes) | {"pr_number": 7085, "pr_title": "fix(router): [Cybersource] add flag to indicate final capture ", "merged_at": "2025-02-04T01:21:48Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connecto... |
<!-- Describe your changes in detail -->
Implemented payment method: Card no-3ds
Implemented Flows
1. Authorization
2. Capture
3. Void
4. Refund
5. Psync
6. Rsync
## 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 (pro... | 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": 9632, "pr_title": "feat(connectors): [Tesouro] Integrate no-threeds cards", "merged_at": "2025-10-01T13:05:07Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core/connector_validati... |
<!-- Describe your changes in detail -->
In this PR
1. A new next action is added
```json
"next_action": {
"type": "invoke_hidden_iframe",
"iframe_data": {
"method_key": "threeDSMethodData",
"three_ds_method_url": "https://sis-d.redsys.es/sis-simulador-web/threeDsMethod... | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/payments.rs`
**2. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/router_request_types.rs`
**3. Core Business Logic**
- `crates... | {"pr_number": 7508, "pr_title": "feat(connectors): [Redsys] add 3D secure card payment support, including transaction capture, cancellation, and refunds", "merged_at": "2025-03-21T10:12:17Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"... |
https://github.com/juspay/hyperswitch/pull/9659
This pull request introduces a new helper function to update the default fallback connector configuration whenever a merchant connector account (MCA) is updated. This ensures that changes to connector status (such as disabling or enabling) are accurately reflected in bot... | 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.rs`
- `crates/router/src/core/routing/helpers.rs`
**Code Patterns Applied:**
- Implement new functions (1 changes)
-... | {"pr_number": 9690, "pr_title": "refactor(routing): update configs on updation of mca", "merged_at": "2025-10-08T08:05:17Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["merchant", "connector"]}, "hierarchy": {"core_business": ["crates/router/src/core/admin.rs", "crates/router/src/... |
- Adyen sofort was failing in cypress automation as sofort payment method is deprecated from adyen, hence handled the error message
- Fixed Variation case for iatapay | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `cypress-tests/cypress/e2e/PaymentUtils/Adyen.js`
- `cypress-tests/cypress/e2e/PaymentUtils/Iatapay.js`
**Code Patterns Applied:**
- Extend existing types with new fields (17 changes) | {"pr_number": 6984, "pr_title": "ci(cypress): fix adyen sofort in cypress", "merged_at": "2025-01-03T19:57:49Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user"]}, "hierarchy": {"tests": ["cypress-tests/cypress/e2e/PaymentUtils/Adyen.js", "cypress-tests/cypress/e2e/Pa... |
<!-- Describe your changes in detail -->
Moving connectors (NMI,Riskified,and payone) from `router` crate to `hyperswitch_connector` crate | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payments/flows.rs`
**2. External Connector Integration**
- `crates/hyperswitch_connectors/Cargo.toml`
- `crates/hyperswitch_connectors/src/connectors.rs`
- `... | {"pr_number": 7666, "pr_title": "refactor(connector): [NMI,PAYONE,RISKIFIED] moved to hyperswitch_connectors", "merged_at": "2025-04-24T10:35:43Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/co... |
- Add support for user in tenants configs.
- Handle email URLs for different tenancies | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/recon.rs`
- `crates/router/src/core/user.rs`
- `crates/router/src/core/user/dashboard_metadata.rs`
**2. Type Definitions**
- `crates/router/src/services/emai... | {"pr_number": 6809, "pr_title": "feat(users): handle email url for users in different tenancies", "merged_at": "2024-12-19T08:50:07Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user", "token"]}, "hierarchy": {"core_business": ["crates/router/src/core/recon.rs", "crates/router/sr... |
<!-- Describe your changes in detail -->
I have implemented a gRPC client that facilitates communication with the recovery-decider gRPC service. The client should be capable of initializing and managing the connection to the service, sending requests, and handling responses in accordance with the defined service contr... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payments/operations/proxy_payments_intent.rs`
- `crates/router/src/core/revenue_recovery/types.rs`
**2. Type Definitions**
- `crates/router/src/types/storage/re... | {"pr_number": 8178, "pr_title": "feat(gRPC): build gRPC client interface to initiate communication with recovery-decider service", "merged_at": "2025-08-06T13:44:24Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user"]}, "hierarchy": {"core_business": ["crates/router/sr... |
<!-- Describe your changes in detail -->
Error message from cashtocode is now populated in error reason along with error message as well. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/cashtocode.rs`
- `crates/hyperswitch_connectors/src/connectors/cashtocode/transformers.rs`
**Code Patterns Applied:**
- Extend exi... | {"pr_number": 7154, "pr_title": "fix(connector): [CASHTOCODE] Populate error reason", "merged_at": "2025-03-03T16:30:03Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors/cashtocode.rs", "crates/hyperswitch_... |
<!-- Describe your changes in detail -->
This PR adds the elimination routing integration support with open router. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/open_router.rs`
- `crates/api_models/src/routing.rs`
**2. Core Business Logic**
- `crates/router/src/core/payments/routing.rs`
- `crates/router/src/co... | {"pr_number": 7896, "pr_title": "feat(dynamic_routing): add open router integration for elimination routing", "merged_at": "2025-04-29T09:51:50Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"api_models": ["crates/api_models/src/open_r... |
<!-- Describe your changes in detail -->
Template connector code for Nomupay payout | 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/payments/connector_integration_v2_impls.rs`
- `crates/router/src/core/payments/f... | {"pr_number": 6382, "pr_title": "feat(connector): [NOMUPAY] Add template code", "merged_at": "2024-11-12T07:30:05Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["connector"]}, "hierarchy": {"api_models": ["crates/api_models/src/connector_enums.rs"], "core_business": ["crates/router... |
Payment via CartesBancaires were failing via Cybersource, since the card_type passed was wrong. It was previously "006" ,but should be "036" - this PR introduces this fix.
source
https://developer.cybersource.com/library/documentation/dev_guides/Retail_SO_API/html/Topics/app_card_types.htm | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/adyen/transformers.rs`
- `crates/hyperswitch_connectors/src/connectors/cybersource/transformers.rs`
- `crates/hyperswitch_connec... | {"pr_number": 8031, "pr_title": "fix(connector): [CYBERSOURCE] fix CartesBancaires card_type for Cybersource", "merged_at": "2025-05-15T12:54:57Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "user"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connecto... |
Hotfix for [PR](https://github.com/juspay/hyperswitch/pull/8455) | 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": 8480, "pr_title": "fix(connector): [TRUSTPAY] Consuming Amount in PSync Response", "merged_at": "2025-06-27T11:19:06Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors/trustpay.rs", "crates/hyp... |
Increased outgoing webhook timeout from 5 seconds to 30 seconds by replacing hardcoded `OUTGOING_WEBHOOK_TIMEOUT_SECS` with existing `REQUEST_TIME_OUT` constant for consistency. | To implement this **payment** 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/outgoing_v2.rs`
- `crates/router/src/core/webhooks/types.rs` | {"pr_number": 8725, "pr_title": "refactor(core): remove hardcoded timeout limit of 5s for outgoing webhook requests", "merged_at": "2025-07-24T15:36:25Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/c... |
<!-- Describe your changes in detail -->
This will integrate elimination routing in our core flows for connectors to be filtered on basis of error codes received. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/routing.rs`
**2. Core Business Logic**
- `crates/router/src/core/errors.rs`
- `crates/router/src/core/payments/operations/payment_response.rs`
- `crat... | {"pr_number": 6816, "pr_title": "feat(dynamic_routing): integration of elimination routing for core flows", "merged_at": "2025-04-22T07:38:05Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/rout... |
<!-- Describe your changes in detail -->
customer_id length validated and server-too-busy error fixed | 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": 8696, "pr_title": "feat(connector): [AUTHORIZEDOTNET] customer_id length validated and server-too-busy error handled", "merged_at": "2025-07-22T17:21:45Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["c... |
Added CIT and MIT flows examples for API Reference for Stripe Split Payments | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Other**
- `api-reference/v1/openapi_spec_v1.json`
- `crates/openapi/src/routes/payments.rs`
**Detailed Identifier Changes:**
Commit 0851c6ec:
Files to modify:
**crates/openapi/src/routes/payments.rs**
Modi... | {"pr_number": 8311, "pr_title": "docs(connector): [STRIPE] Added CIT & MIT Examples for API Reference in Stripe Split Payments", "merged_at": "2025-06-20T14:01:48Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"other": ["api-refere... |
<!-- Describe your changes in detail -->
This PR addresses panics and some bugs in customers v2 endpoints. This PR includes the following changes:
- Fixes the customers v2 update and retrieve endpoints to use the correct HTTP methods (`PUT` and `GET` respectively).
- Adds the `#[serde(deny_unknown_fields)]` to c... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/customers.rs`
- `crates/api_models/src/ephemeral_key.rs`
- `crates/api_models/src/events/customer.rs`
- ... and 2 more files
**2. Database Layer (Quer... | {"pr_number": 6836, "pr_title": "refactor(customers_v2): address panics and some bugs in customers v2 endpoints", "merged_at": "2024-12-17T11:26:05Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/sr... |
<!-- Describe your changes in detail -->
As part of the modularity effort, we are introducing user support to enable dashboard interactions with v2 merchant accounts. This allows users to create, list, and switch between merchant accounts within their organization. This also allows users to list profiles and switch ... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/events/user.rs`
- `crates/api_models/src/user.rs`
**2. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/merchant_account.rs... | {"pr_number": 7386, "pr_title": "feat(users): Add V2 User APIs to Support Modularity for Merchant Accounts", "merged_at": "2025-03-12T14:36:50Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"api_models": ["crates/api_models/src/events/... |
<!-- Describe your changes in detail -->
ORIGINAL PR: https://github.com/juspay/hyperswitch/pull/7591
Pass email in payment request body of Braintree as it is mandatory field for sending receipts in braintree | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/braintree/transformers.rs`
**Code Patterns Applied:**
- Define new data structures (1 changes)
- Extend existing types with new field... | {"pr_number": 7597, "pr_title": "refactor(connector): [BRAINTREE] Pass email in payment requests", "merged_at": "2025-03-21T16:28:45Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/c... |
<!-- Describe your changes in detail -->
Return Network transaction if from connector Response
- NOTE: we need to ask nuvei to return `external_scheme_transaction_id` during integration.
<details>
<summary> See returned NTID in the connector payment response</summary> | 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:**
- Extend existing types with new fields (1 changes) | {"pr_number": 9261, "pr_title": "feat(nuvei): Map NTID for nuvei payment responses", "merged_at": "2025-09-07T14:40:37Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors/nuve... |
<!-- Describe your changes in detail -->
Move stripe connector code form `router` crate to `hyperswitch_connectors` crate
- issue : https://github.com/juspay/hyperswitch/issues/8008 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payments.rs`
- `crates/router/src/core/payments/flows.rs`
**2. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors.rs`
- `crates... | {"pr_number": 8007, "pr_title": "refactor(connector): stripe migration from router to hyperswitch_connectors", "merged_at": "2025-05-16T14:21:48Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/co... |
Added Integrity Checks for PSync and RSync flows in Trustpay.
Why not for other flows as well?
The reason being, Trustpay doesnt send `amount` field in their response. Without getting to know the `amount`, we cannot perform integrity check. But they do send an `amount` field in Webhooks, so it will be checked upon r... | 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_data.rs`
**2. Core Business Logic**
- `crates/router/src/core/payments.rs`
- `crates/router/src/core/payments/helpers.rs`
... | {"pr_number": 8096, "pr_title": "feat(connector): [TRUSTPAY] Added Integrity Checks for PSync & RSync flows & Added New Variants in AttemptStatus & IntentStatus", "merged_at": "2025-06-10T17:03:40Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "... |
fix deserialization error for Paypal while canceling payment for Authorizedotnet | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/router/src/connector/authorizedotnet/transformers.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (2 changes) | {"pr_number": 7141, "pr_title": "fix(connector): [Authorizedotnet] fix deserialization error for Paypal while canceling payment ", "merged_at": "2025-02-05T15:03:54Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["cra... |
<!-- Describe your changes in detail -->
Added `Payments - List` endpoint for v2 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/events/payment.rs`
- `crates/api_models/src/payments.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/query/payment_attempt.rs`
... | {"pr_number": 7191, "pr_title": "feat(router): Add Payments - List endpoint for v2", "merged_at": "2025-02-20T12:28:49Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/events/payment.rs", "crates... |
<!-- Describe your changes in detail -->
This PR integrates the get plan prices endpoint for chargebee, required to be called in the respective API handler for the same (not yet implemented) | 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_data_v2/flow_common_types.rs`
- `crates/hyperswitch_domain_models/src/router_flow_types.rs`
- `crates/hyperswitch_domain_mo... | {"pr_number": 9300, "pr_title": "feat(connector): Add support for get plan prices for Chargebee", "merged_at": "2025-09-19T08:20:28Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user", "connector"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/router_data_v2/fl... |
<!-- Describe your changes in detail -->
Adding `connector_customer_id` for proxy flow | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payments/operations/external_vault_proxy_payment_intent.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (4 changes) | {"pr_number": 9263, "pr_title": "fix(router): adding connector_customer_id for external vault proxy", "merged_at": "2025-09-11T12:38:28Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core/paymen... |
<!-- Describe your changes in detail -->
Template code added for new connector Amazon Pay
https://developer.amazon.com/docs/amazon-pay-api-v2/introduction.html | 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/payments/connector_integration_v2_impls.rs`
- `crates/router/src/core/payments/f... | {"pr_number": 6486, "pr_title": "Feat(connector): [AMAZON PAY] Added Template code", "merged_at": "2024-11-08T10:52:01Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["connector"]}, "hierarchy": {"api_models": ["crates/api_models/src/connector_enums.rs"], "core_business": ["crates/r... |
<!-- Describe your changes in detail -->
- Add sessionized metrics module and implement backwards compatibility.
- Add the `sessionizer_dispute` table support for Sessionized metrics. | 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/disputes.rs`
- `crates/api_models/src/events.rs`
**2. Core Business Logic**
- `crates/analytics/src/d... | {"pr_number": 6573, "pr_title": "feat(analytics): add `sessionized_metrics` for disputes analytics", "merged_at": "2024-11-26T13:58:33Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user", "order"]}, "hierarchy": {"api_models": ["crates/api_models/src/analytics.rs", "cr... |
Add payments flows for connector Moneris
- Payments (Cards)
- Payment Sync
- Capture
- Void
- Refund
- Refund Sync
- Add cypress test
- Add wasm changes | 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/connec... | {"pr_number": 7249, "pr_title": "feat(connector): [Moneris] Add payments flow", "merged_at": "2025-02-18T18:00:11Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core/admin.rs"], "connectors": ["... |
<!-- 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": 6822, "pr_title": "fix(webhooks): mask custom outgoing webhook headers in profile response", "merged_at": "2024-12-12T08:42:48Z", "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 -->
add `challenge_request_key` in authentication response and add support for cardinal authentication processor | 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/authentication.rs`
- `crates/diesel_models/src/schema.rs`
- `crates/... | {"pr_number": 9429, "pr_title": "feat(router): add `challenge_request_key` in authentication response and add support for cardinal authentication processor", "merged_at": "2025-09-18T15:40:57Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "card"]}, "hierarchy": {"api_mod... |
<!-- Describe your changes in detail -->
In revenue recovery flow, when process tracker picks task , it records internal attempt first and then triggers proxy payments. Previously only customer id and psp token is required to make payment. Since recovery ml model needs all othe parameter, This PR adds support for popu... | 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": 9061, "pr_title": "fix(revenue_recovery): Populate payment method data in record attempt flow for V2", "merged_at": "2025-08-28T17:25:22Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models... |
<!-- Describe your changes in detail -->
This PR addresses 5xx that currently is being thrown when a user tries to cancel the PayPal transactions from the redirected page:
<img width="372" alt="image" src="https://github.com/user-attachments/assets/4f920b8b-6ab4-4bcb-9705-dc4d15635c2d" />
This is addressed by ... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/globalpay/requests.rs`
- `crates/hyperswitch_connectors/src/connectors/globalpay/response.rs`
- `crates/hyperswitch_connectors/s... | {"pr_number": 7605, "pr_title": "fix(connector): [GlobalPay] Address `5xx` when cancelling a paypal transaction", "merged_at": "2025-03-26T10:26:02Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_c... |
<!-- Describe your changes in detail -->
Add `peek_mut` function to PeekInterface to get mutable reference for the inner data.
## Motivation and Context
<!--
Why is this change required? What problem does it solve?
If it fixes an open issue, please link to the issue here.
If you don't have an issue, we'd reco... | To implement this **connector_integration** feature, you'll need to modify these architectural layers:
**1. Other**
- `crates/masking/src/abs.rs`
- `crates/masking/src/bytes.rs`
- `crates/masking/src/secret.rs`
- ... and 1 more files
**Code Patterns Applied:**
- Implement new functions (4 changes) | {"pr_number": 7281, "pr_title": "chore(masking): add peek_mut to PeekInterface", "merged_at": "2025-02-22T08:40:07Z", "intent": {"feature_type": "connector_integration", "action": "add_feature", "entities": []}, "hierarchy": {"other": ["crates/masking/src/abs.rs", "crates/masking/src/bytes.rs", "crates/masking/src/secr... |
<!-- Describe your changes in detail -->
If the business profile does not have a country set, we cannot perform debit routing, because the merchant_business_country will be treated as the acquirer_country, which is used to determine whether a transaction is local or global in the open router. For now, since debit rout... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/debit_routing.rs`
**Code Patterns Applied:**
- Add conditional logic for feature flags or filtering (2 changes) | {"pr_number": 8141, "pr_title": "refactor(debit_routing): Handle missing merchant_business_country by defaulting to US", "merged_at": "2025-05-28T06:51:44Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/rou... |
<!-- Describe your changes in detail -->
Add authorized_amount in payment_attempt to support partial authorization for manual_multiple capture.
Add partial authorization support for Checkout connector | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/payment_attempt.rs`
- `crates/diesel_models/src/schema.rs`
- `crates/diesel_models/src/schema_v2.rs`
- ... and 1 more files
**2. Domain Model... | {"pr_number": 9594, "pr_title": "feat(core): Add authorized_amount in payment_attempt to support partial authorization for manual_multiple capture", "merged_at": "2025-10-01T10:16:39Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"... |
A new struct, UpdateScoreResponse, was introduced in the API models to represent responses from the Open Router. The payment routing logic was updated to parse responses directly into this struct, replacing the previous manual string conversion and error handling with structured deserialization. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/open_router.rs`
**2. Core Business Logic**
- `crates/router/src/core/payments/routing.rs`
**3. Other**
- `api-reference-v2/openapi_spec.json`
**Code Pa... | {"pr_number": 8308, "pr_title": "refactor(dynamic_routing): change the response type of update gateway score api in open router", "merged_at": "2025-06-11T10:07:49Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user"]}, "hierarchy": {"api_models": ["crates/api_models/sr... |
<!-- Describe your changes in detail -->
Corrected the content of the tip. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Other**
- `api-reference/api-reference/payments/Introduction--to--payments.mdx` | {"pr_number": 7387, "pr_title": "docs(api-reference): fix the content of the tip", "merged_at": "2025-02-27T13:47:08Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"other": ["api-reference/api-reference/payments/Introduction--to--payments.mdx"]}, "change_types": {... |
<!-- Describe your changes in detail -->
For each countries present in Europe, their states are converted to ISO Standard
[Source for standard](https://github.com/juspay/hyperswitch-web/blob/main/src/States.json)
Note: A bugfix is present as well for address_id used to fetch billing_address for external authentic... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/payments.rs`
**2. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/mandates.rs`
**3. Core Business Logic**
- `crates/route... | {"pr_number": 7302, "pr_title": "feat(utils): add iso representation for each state for european countries", "merged_at": "2025-02-18T17:45:24Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment"]}, "hierarchy": {"api_models": ["crates/api_models/src/payments.rs"], "domain": ["... |
<!-- Describe your changes in detail -->
Make new APIs to replace
- `/user/role/{{role_id}}` -> `/user/role/{{role_id}}/v2`
- `/user/role` -> `/user/role/v2`
- `/user/module/list` -> `/user/parent/list`
The new APIs will have proper description and parent info which has entity level context unlike the previous A... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/events/user_role.rs`
- `crates/api_models/src/user_role/role.rs`
**2. Core Business Logic**
- `crates/router/src/core/user_role.rs`
- `crates/router/s... | {"pr_number": 6440, "pr_title": "feat(authz): Make info APIs support `ParentGroup`", "merged_at": "2024-10-30T10:42:37Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/events/user_role.rs", "crat... |
<!-- Describe your changes in detail -->
After passive churn recovery retries the payment, we will have to record back and update the invoice in billing process. This PR adds support for this by adding connector integration flow. | 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_data_v2/flow_common_types.rs`
- `crates/hyperswitch_domain_models/src/router_flow_types/revenue_recovery.rs`
- `crates/hype... | {"pr_number": 7416, "pr_title": "feat(connector): Add record back connector integration flow ", "merged_at": "2025-03-12T12:38:36Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "connector"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/router_data_v2/f... |
<!-- Describe your changes in detail -->
Integrate celero commerce connector
Doc : https://sandbox.gotnpgateway.com/docs/api/transactions
[x] Cards
[x] Avs | 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": 8574, "pr_title": "feat(connector): [CELERO] Integrate Card Payments (Alpha)", "merged_at": "2025-08-20T12:33:18Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user", "connector", "card"]}, "hierarchy": {"connectors": ["crates/connector_configs/toml/development.toml"... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.