prompt stringlengths 6 90.9k | response stringlengths 121 18.6k | metadata stringlengths 314 42.3k |
|---|---|---|
<!-- Describe your changes in detail -->
Nomupay is not added in `connector_customer` for `payout_connector_list` for different environments, that's why payouts cypress test is failing for nomupay in integ.
Nomupay added in `payout_connector_list` for all environment | 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": 7521, "pr_title": "fix(connector): add Nomupay in payout_connector_list for all environment", "merged_at": "2025-03-25T07:19:52Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "user", "connector"]}, "hierarchy": {"tests": ["config/deployments/integration_t... |
Earlier we used to store the connector mandate id irrespective of the payments status being charged or not for 3DS flows, now we would handle the connector_mandate_id updation in payment_method once and only if the payment has a status as charged. | 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": 6327, "pr_title": "fix(mandates): handle the connector_mandate creation once and only if the payment is charged", "merged_at": "2024-10-17T13:59:13Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"database": ["crates/d... |
<!-- Describe your changes in detail -->
The metadata fields should have currency_id and platform_id as numbers, not strings for coingate | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/connector_configs/src/common_config.rs`
- `crates/connector_configs/toml/development.toml`
- `crates/connector_configs/toml/production.toml`
- ... and 1 more files | {"pr_number": 7716, "pr_title": "fix(connector): [Coingate] Fix Wasm Changes ", "merged_at": "2025-04-04T10:34:59Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"connectors": ["crates/connector_configs/src/common_config.rs", "crates/connector_configs/toml/developm... |
<!-- Describe your changes in detail -->
This PR adds a check to verify if the `payment_status` is not any of `succeeded`, `partially_captured` or `requires_capture` and if so, then the `connector_mandate_id` should be `null`. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `cypress-tests/cypress/e2e/spec/Payment/00024-ConnectorAgnosticNTID.cy.js`
- `cypress-tests/cypress/support/commands.js`
**Code Patterns Applied:**
- Add conditional logic for feature flags or filterin... | {"pr_number": 7749, "pr_title": "ci(cypress): verify mandate id to be `null` if payment id not `succeeded`", "merged_at": "2025-04-16T10:47:24Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user", "connector"]}, "hierarchy": {"tests": ["cypress-tests/cypress/e2e/spec/Pa... |
Added details feature api details for Jpmorgan, Payu, Digital Virgo. | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/bitpay.rs`
- `crates/hyperswitch_connectors/src/connectors/digitalvirgo.rs`
- `crates/hyperswitch_connectors/src/connectors/helcim.rs`... | {"pr_number": 7148, "pr_title": "feat(connector): [JPMORGAN, PAYU, DIGITALVIRGO, PAYBOX, BITPAY, HELCIM] added in feature matrix api", "merged_at": "2025-02-25T19:48:48Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["payment", "merchant", "refund"]}, "hierarchy": {"connectors": ["crates/... |
<!-- Describe your changes in detail -->
This PR contains -
- Ephemeral auth support for v2 (including resource type product identifier)
- Minor Fixes for Payment methods v2 CRUD APIs
- Removed Client secret auth from PaymentMethod CRUD APIs | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/ephemeral_key.rs`
- `crates/api_models/src/payment_methods.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/ephemeral_key.rs`
... | {"pr_number": 6813, "pr_title": "feat(payment_methods_v2): Added Ephemeral auth for v2", "merged_at": "2024-12-22T18:04:10Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/ephemeral_key.rs", "cra... |
<!-- Describe your changes in detail -->
Added `payment_experience` in Payment Method List for Payments Response | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/payments.rs`
**2. Core Business Logic**
- `crates/router/src/core/payments/payment_methods.rs`
**3. Other**
- `api-reference-v2/openapi_spec.json`
**Co... | {"pr_number": 8255, "pr_title": "feat(router): Return payment_experience in PML for payment (v2)", "merged_at": "2025-06-05T16:40:31Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "card"]}, "hierarchy": {"api_models": ["crates/api_models/src/payments.rs"], "c... |
<!-- Describe your changes in detail -->
#6300 has inconsistent response due to no validations for each field in migration api request body. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payment_methods/cards.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (2 changes)
- Add conditional logic for feature flags or filtering (1 cha... | {"pr_number": 6525, "pr_title": "fix(router): validate each field for migration request body", "merged_at": "2024-12-06T11:44:36Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core/payment_metho... |
<!-- Describe your changes in detail -->
Fixed broken API reference for the following endpoints:
- `API Key - Create`
- `API Key - Revoke`
- `Routing - Retrieve`
- `Routing - Activate Config` | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Configuration Files**
- `api-reference/api-reference/routing/routing--activate-config.mdx`
**2. Other**
- `api-reference/api-reference/api-key/api-key--create.mdx`
- `api-reference/api-reference/api-key/api-k... | {"pr_number": 6507, "pr_title": "fix(docs): Fix broken pages in API reference", "merged_at": "2024-11-08T13:05:27Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"config": ["api-reference/api-reference/routing/routing--activate-config.mdx"], "other": ["api-referenc... |
<!-- Describe your changes in detail -->
For adyen incase of reponse update with webhooks, we are hardcoding error code and message to none and while propagating checking whether error code & message is some, This pr fixes this bug . | 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": 6602, "pr_title": "fix(connector): [Adyen]fix error code and message for webhooks response", "merged_at": "2024-11-19T19:36:03Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/router/src/connector... |
<!-- Describe your changes in detail -->
This will remove payment_id from being pushed to dynamic_routing metrics | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/routing/helpers.rs` | {"pr_number": 6535, "pr_title": "refactor(routing): remove payment_id from dynamic_routing metrics", "merged_at": "2024-11-12T15:03:43Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core/routing/helpers.rs"... |
<!-- Describe your changes in detail -->
template for unified_authentication_service | 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": 6732, "pr_title": "feat(connector): [Unifiedauthenticationservice] add Connector Template Code", "merged_at": "2024-12-10T11:03:06Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"api_models": ["crates/api_models/src/connector_enums.rs"], "core_busine... |
Added Skrill and iDeal payment methods in `Airwallex` | 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": 8535, "pr_title": "feat(connector): [AIRWALLEX] Added Ideal & Skrill payment methods ", "merged_at": "2025-07-24T08:11:05Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/payments.r... |
<!-- Describe your changes in detail -->
Added EFT as a payment method in Bank Redirect.
Active Issue linked to this PR: https://github.com/juspay/hyperswitch/issues/7313
but still PR convention checks are failing | 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": 7304, "pr_title": "feat(connector): [EFT] Add EFT as a payment method", "merged_at": "2025-03-05T14:51:22Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "connector"]}, "hierarchy": {"api_models": ["crates/api_models/src/payments.rs"], "domain": ["crates/hyp... |
<!-- Describe your changes in detail -->
Add required wasm changes for samsung pay integration. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/connector_configs/src/common_config.rs`
- `crates/connector_configs/src/connector.rs`
- `crates/connector_configs/toml/development.toml`
**Code Patterns Applied:**
-... | {"pr_number": 6424, "pr_title": "chore: Add samsung pay payment method support for cybersource", "merged_at": "2024-10-24T15:05:18Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"connectors": ["crates/connector_configs/src/common_config.rs", "crates/connecto... |
- Add l2l3 data for checkout
- Note : checkout recommends some checks like line_items should sum up proper total and discount amount. But it doesn't throw any errors for this. Hence in this pr we are not adding any such validations .
## Request
```json
{
"amount": 30000,
"capture_method": "automatic",... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/checkout/transformers.rs`
**Code Patterns Applied:**
- Define new data structures (5 changes)
- Extend existing types with new fields... | {"pr_number": 9446, "pr_title": "feat(Connector): [checkout] l2l3 data ", "merged_at": "2025-09-19T12:29:00Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors/checkout/transf... |
Enhanced Forte Connector in cypress for Comprehensive Testing.
## How did you test it?
**Forte**
<img width="552" alt="Forte" src="https://github.com/user-attachments/assets/21082635-e104-41d4-9d09-997939825c2d" />
## Checklist
<!-- Put an `x` in the boxes that apply -->
- [ ] I formatted the code `cargo +n... | To implement this **connector_integration** feature, you'll need to modify these architectural layers:
**1. Tests**
- `cypress-tests/cypress/e2e/configs/Payment/Forte.js`
- `cypress-tests/cypress/e2e/configs/Payment/Utils.js`
- `cypress-tests/cypress/support/commands.js`
**Code Patterns Applied:**
- Extend ... | {"pr_number": 8402, "pr_title": "ci(cypress): Add Forte connector test in cypress", "merged_at": "2025-06-24T12:58:24Z", "intent": {"feature_type": "connector_integration", "action": "add_feature", "entities": ["user", "connector"]}, "hierarchy": {"tests": ["cypress-tests/cypress/e2e/configs/Payment/Forte.js", "cypress... |
<!-- Describe your changes in detail -->
This will make the `mandate_payments` acceptable even when `setup_future_usage` is null in payments. | 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`
- `crates/router/src/core/payment_methods/utils.rs` | {"pr_number": 6845, "pr_title": "refactor(constraint_graph): revert handle for cases where setup_future_usage is null in payments", "merged_at": "2024-12-16T13:24:35Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment"]}, "hierarchy": {"core_business": ["crates/router/src/core/... |
<!-- Describe your changes in detail -->
This PR removes the redundant (and outdated) webhooks documentation page in our API reference (both v1 and v2) in favor of the one on `docs.hyperswitch.io`.
## 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. Other**
- `api-reference-v2/essentials/webhooks.mdx`
- `api-reference-v2/mint.json`
- `api-reference/essentials/webhooks.mdx`
- ... and 1 more files | {"pr_number": 6538, "pr_title": "docs(api-reference): remove redundant webhooks page", "merged_at": "2024-11-12T15:02:42Z", "intent": {"feature_type": "connector_integration", "action": "add_feature", "entities": ["webhook"]}, "hierarchy": {"other": ["api-reference-v2/essentials/webhooks.mdx", "api-reference-v2/mint.js... |
ORIGINAL PR: https://github.com/juspay/hyperswitch/pull/8042 | To implement this **unknown** 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/trustpay.rs`
**2. Tests**
- `config/deployments/integration_test.toml`
... | {"pr_number": 8046, "pr_title": "feat(connector): revert [paypal, trustpay] add in feature matrix", "merged_at": "2025-05-15T14:22:25Z", "intent": {"feature_type": "unknown", "action": "unknown", "entities": []}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors/paypal.rs", "crates/hyperswitch_... |
<!-- Describe your changes in detail -->
This PR introduces profile-level configuration for enabling/disabling L2/L3 transaction data, providing merchants with granular control over enhanced payment data collection at the business profile level.
# 🧩 Additional Changes
## 🗄️ Database & Schema
- Added new colum... | 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": 9683, "pr_title": "feat(core): Add profile-level configuration for L2/L3 data enablement", "merged_at": "2025-10-16T08:22:12Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/admin.r... |
<!-- Describe your changes in detail -->
Destination bank account id should be merchant facing, not customer. This PR removes any references to destination bank account id and moves it to connector metadata instead. | 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. Core Business Logic**
- `crates/router/src/core/connector_validation.rs`
**3. Ex... | {"pr_number": 8704, "pr_title": "refactor(connector): [facilitapay] move destination bank account number to connector metadata", "merged_at": "2025-07-25T12:44:09Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crate... |
<!-- Describe your changes in detail -->
the reason behind this pr is that there are a few connectors like adyen that expects the user to pass specific card expiry year and having it hard coded like we had until now results in unintended issues resulting the tests to fail. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `cypress-tests/cypress/e2e/spec/Payment/00014-SaveCardFlow.cy.js` | {"pr_number": 7834, "pr_title": "refactor(cypress): do not update `card_expiry` while updating card info", "merged_at": "2025-04-22T09:31:33Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user", "connector", "card"]}, "hierarchy": {"tests": ["cypress-tests/cypress/e2e/spec/Payment... |
<!-- Describe your changes in detail -->
This PR updates the BIN lookup override logic in payment transformers.rs to ensure payment_method_type is overridden only for Card payment methods. | 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": 9241, "pr_title": "fix(payments): override payment_method_type only for cards", "merged_at": "2025-09-03T13:10:45Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core/payments/opera... |
<!-- Describe your changes in detail -->
connector_transaction_id of wise only support UUID format.
reference_id wont be required as value since we store the wise's transaction id.
We only send UUID to make the transaction without any error. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/wise/transformers.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (1 changes) | {"pr_number": 8836, "pr_title": "fix(connector): [Wise] send uuid as connector_transaction_id", "merged_at": "2025-08-05T09:41:49Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "merchant", "order"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connec... |
<!-- Describe your changes in detail -->
This PR introduces payments capture endpoint for the v2 version.
This PR also changes the `GenerateResponse` trait to be implemented on the payment data. The new trait looks like this
```rust
pub trait GenerateResponse<Response>
where
Self: Sized,
{
#[cfg(fe... | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/events/payment.rs`
- `crates/api_models/src/payments.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/payment_attempt.rs`
- `crates/... | {"pr_number": 6722, "pr_title": "feat(payments_v2): implement payments capture v2", "merged_at": "2024-12-20T15:53:01Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/events/payment.rs", "crates/api_mo... |
<!-- Describe your changes in detail -->
- `diesel_cli` version `2.3.0` expects to call `rustfmt` to format its output. If `rustfmt` is not installed on the system it will give an error.
- Added a step to install `rustfmt` to fix the workflow | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Other**
- `.github/workflows/migration-check.yaml`
**Code Patterns Applied:**
- Extend existing types with new fields (1 changes) | {"pr_number": 9386, "pr_title": "ci(migration-check): install rustfmt to address migration run failures", "merged_at": "2025-09-15T12:52:03Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"other": [".github/workflows/migration-check.yaml"]}, "change_types": {"field... |
<!-- Describe your changes in detail -->
Added support for `client_secret` authentication in `Payments - Get Intent` | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Other**
- `crates/router/src/routes/payments.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (2 changes) | {"pr_number": 8119, "pr_title": "feat(router): Enable client_secret auth for payments_get_intent [v2]", "merged_at": "2025-05-27T10:56:27Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"other": ["crates/router/src/routes/payments.r... |
This PR enables card payouts through AdyenPlatform connector. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/adyenplatform/transformers/payouts.rs`
**2. Configuration Files**
- `crates/router/src/configs/defaults/payout_required_fields.rs`... | {"pr_number": 8504, "pr_title": "feat(connector): [ADYENPLATFORM] add card payouts", "merged_at": "2025-07-01T11:43:42Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "merchant", "user"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors/adyenpl... |
Add multisafepay connector to cypress test suite
Connector doesn't support no_three_ds payments hence mapped accordingly | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `cypress-tests/cypress/e2e/configs/Payment/Multisafepay.js`
- `cypress-tests/cypress/e2e/configs/Payment/Utils.js`
**Code Patterns Applied:**
- Extend existing types with new fields (561 changes) | {"pr_number": 8479, "pr_title": "ci(cypress): add multisafepay connector", "merged_at": "2025-07-01T08:13:19Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user", "connector"]}, "hierarchy": {"tests": ["cypress-tests/cypress/e2e/configs/Payment/Multisafepay.js", "cypres... |
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 AND installment loan provider
- Cu... | 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": 8714, "pr_title": "feat(connector): [Flexiti]template code for flexiti connector", "merged_at": "2025-07-25T07:20:56Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/conn... |
Added config for changing text of confirm button for payment links | 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": 6860, "pr_title": "feat(payments): [Payment links] Add config for changing button text for payment links", "merged_at": "2024-12-19T13:28:25Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_mo... |
- Fix dynamic fields for SepaBankTransfer
- Handle error case Status mapping
- Fix wasm Changes for SepaBankTransfer | 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": 7649, "pr_title": "refactor(connector): [TrustPay] Fix status and wasm changes ", "merged_at": "2025-03-26T18:06:21Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/connector_configs/toml/developm... |
This PR introduces the following fix:
HS should pass `paymentInformation.tokenizedCard.transactionType` for only wallet MITs. Presently `paymentInformation.tokenizedCard.transactionType` is being passed for card MITs as well, which is incorrect according to cybersource docs. | 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) | {"pr_number": 9444, "pr_title": "fix(connector): [CYBERSOURCE] Pass transaction type for only wallet MITs", "merged_at": "2025-09-19T13:08:08Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user", "connector"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors... |
<!-- Describe your changes in detail -->
Moving Datatrans, Paybox, Placetopay, Bluesnap 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/connector_integration_v2_impls.rs`
- `crates/router/src/core/payments/flows.rs`
**2. External Connector Integration**
- `crates/hyperswitch_connectors/... | {"pr_number": 6730, "pr_title": "refactor(connector): Move connectors Datatrans, Paybox, Placetopay, Bluesnap from router crate to hyperswitch_connector crate", "merged_at": "2024-12-12T07:45:33Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "h... |
<!-- Describe your changes in detail -->
This pull request introduces a new field, `routing_result_source`, across various structs and enums in the codebase to specify the source of routing decision results. This field allows for flexibility in choosing between Hyperswitch's inbuilt routing engine and an external de... | 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. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/business_profile... | {"pr_number": 8350, "pr_title": "feat(routing): add profile config to switch between HS routing and DE routing result", "merged_at": "2025-06-20T13:20:57Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_mod... |
<!-- Describe your changes in detail -->
Some connector requires connector metadata in the refund flow.
Example adyen requires `endpoint_prefix`. Hence this change is to populate the connector metadata in the relay refunds flow. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/relay/utils.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (1 changes) | {"pr_number": 7045, "pr_title": "fix(relay): populate connector metadata in the refunds flow", "merged_at": "2025-01-19T14:14:43Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core/relay/utils.r... |
<!-- Describe your changes in detail -->
Previously we were not sending some customer's details (email, shipping details) in the payload while creating the customer and thus merchant was not able to see the details in connector dashboard, this PR passes the fields and thus visible in the dashboard as well.
Populate... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/router_request_types.rs`
**2. Core Business Logic**
- `crates/router/src/core/payments/transformers.rs`
**3. External Connector Int... | {"pr_number": 8618, "pr_title": "feat(connector): [AUTHORIZEDOTNET] Populated merchant required fields in setupmandate flow", "merged_at": "2025-07-14T07:33:35Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"domain": ["crates/hyper... |
Hotfix for https://github.com/juspay/hyperswitch/pull/7211 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/fiuu.rs`
- `crates/hyperswitch_connectors/src/connectors/fiuu/transformers.rs`
**Code Patterns Applied:**
- Extend existing types ... | {"pr_number": 7242, "pr_title": "fix(connector): [fiuu] update PSync and webhooks response", "merged_at": "2025-02-11T11:32:38Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["connector"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors/fiuu.rs", "crates/... |
<!-- Describe your changes in detail -->
This PR modifies the `Dockerfile` to specify the user at runner stage. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Other**
- `Dockerfile` | {"pr_number": 7641, "pr_title": "build(docker): specify user for runner stage", "merged_at": "2025-03-27T09:20:47Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"other": ["Dockerfile"]}, "change_types": {}, "has_identifier_data": false, "commits_matched": 0,... |
<!-- Describe your changes in detail -->
Cashtocode does not support PSync.
When a PSync call is processed via Hyperswitch, the RouterData remains unchanged (payment status is not modified).
However, when the same PSync call goes via UCS, UCS returns an error response.
This causes inconsistent behavior betwee... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payments/flows/psync_flow.rs`
**2. External Connector Integration**
- `crates/external_services/src/grpc_client/unified_connector_service.rs`
**3. Tests**
- `c... | {"pr_number": 9093, "pr_title": "fix: Disable UCS PSync call for Cashtocode", "merged_at": "2025-09-02T14:46:21Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core/payments/flows/psync_flow.rs"]... |
build the gRPC interface for communicating with the external service to perform elimination routing | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/routing.rs`
**2. Core Business Logic**
- `crates/router/src/core/payments/routing.rs`
- `crates/router/src/core/routing.rs`
- `crates/router/src/core/... | {"pr_number": 6672, "pr_title": "feat(routing): build the gRPC interface for communicating with the external service to perform elimination routing", "merged_at": "2024-12-13T05:41:41Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"api_models": ["crates/api_... |
<!-- Describe your changes in detail -->
Payment links will have `Add Payment Method` as button text in case merchant send is_setup_mandate_flow as `true` in payment_link_config, `Authorize Payment` in case of manual capture payments and `Pay Now` in automatic captures.
is_setup_mandate_flow field is only used to alt... | 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": 7574, "pr_title": "feat(payment-link): alternate text for manual captures", "merged_at": "2025-04-25T12:16:40Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/admin.rs", "crates/api... |
<!-- Describe your changes in detail -->
Earlier Limitation:
1. Adding connector to customer create config will trigger customer create for all types of payments where mostly, connectors would require customer create for a specific payment method or customer initiated payment method.
2. This config will not change ... | 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/customers.rs`
- `crates/router/src/core/payments/vault_session.rs`
**2. External Connector Integration**
- `c... | {"pr_number": 9569, "pr_title": "fix(core): add should_call_connector_customer function to connector specification", "merged_at": "2025-09-30T07:42:14Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/... |
- implement session update flow for Paypal
- implement post_update_tracker for SessionUpdate Flow
hotfix for [PR](https://github.com/juspay/hyperswitch/pull/6299) | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/payments.rs`
**2. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/router_request_types.rs`
- `crates/hyperswitch_domain_mo... | {"pr_number": 6350, "pr_title": "feat(router): implement post_update_tracker for SessionUpdate Flow and add support for session_update_flow for Paypal", "merged_at": "2024-10-17T10:22:37Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy"... |
<!-- Describe your changes in detail -->
- google pay details can be collected from connector_wallets_details field in MCA. Both for decrypt and tokenized flow
- session token response can be generated from both connector_wallets_details and metadata. (connector_wallets_details is given the priority in case both are ... | 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/errors.rs`
- `crates/router/src/core/payments.rs`
- `crates/router/src/core/payments... | {"pr_number": 7140, "pr_title": "feat(core): add support to generate session token response from both `connector_wallets_details` and `metadata`", "merged_at": "2025-02-13T08:26:17Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "connector"]}, "hierarchy": {"a... |
Add Shipping Cost test case for cypress automation | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `cypress-tests/cypress/e2e/PaymentTest/00004-NoThreeDSAutoCapture.cy.js`
- `cypress-tests/cypress/e2e/PaymentUtils/Adyen.js`
- `cypress-tests/cypress/e2e/PaymentUtils/BankOfAmerica.js`
- ... and 1... | {"pr_number": 6779, "pr_title": "ci(cypress): Add shipping cost test case", "merged_at": "2024-12-10T12:53:48Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"tests": ["cypress-tests/cypress/e2e/PaymentTest/00004-NoThreeDSAutoCapture.cy.js", "cypress-tests/cy... |
This PR integrates the Euclid-based decision engine with Hyperswitch’s dynamic routing infrastructure. It enables dual routing logic: legacy DSL-based evaluation and decision-engine-backed configurations. The integration ensures routing algorithms can be authored, activated, and evaluated via Euclid and linked seamless... | 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. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/routing_algorithm.rs`
- `crates/diesel_models/src/schema.rs`
**3. Core ... | {"pr_number": 7930, "pr_title": "feat(euclid): integration with decision engine", "merged_at": "2025-05-14T18:40:13Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/routing.rs"], "database": ["crates/diesel_... |
<!-- Describe your changes in detail -->
Corrected the docker setup, for demo app, control-center, and removed mailhog. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Configuration Files**
- `docker-compose-development.yml`
- `docker-compose.yml`
**2. Other**
- `README.md`
- `scripts/docker_output.sh`
- `scripts/poststart_hook.sh`
- ... and 1 more files
**Code Pa... | {"pr_number": 7963, "pr_title": "fix: fixes the docker setup to clean up the scarf data", "merged_at": "2025-05-12T16:21:53Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"config": ["docker-compose-development.yml", "docker-compose.yml"], "other": ["README.md", "s... |
<!-- Describe your changes in detail -->
- Moved required fields for `givex` gift card for `Adyen` from `non-mandate` to `common` | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Configuration Files**
- `config/payment_required_fields_v2.toml` | {"pr_number": 9414, "pr_title": "fix(config): Set common required fields for Givex (v2)", "merged_at": "2025-09-18T08:51:00Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "user"]}, "hierarchy": {"config": ["config/payment_required_fields_v2.toml"]}, "change_t... |
<!-- Describe your changes in detail -->
Added WASM build check as part of pipeline
 | {"pr_number": 6842, "pr_title": "ci: add workflow to check wasm-pack build", "merged_at": "2024-12-17T10:58:16Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"config": [".github/workflows/wasm-bulild-check.yml"]}, "change_types": {"fields_added": 16}, "has_i... |
Fix deserlization error for Nuvei card 3ds | 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/authentication.rs`
**2. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/nuvei/... | {"pr_number": 8913, "pr_title": "refactor(connector): [Nuvei] Fix card 3ds", "merged_at": "2025-08-19T11:00:18Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/router_request_types/aut... |
<!-- Describe your changes in detail -->
This PR adds payment methods session confirm endpoint. This endpoint can be used to create multi use tokens for the given payment method data.
Payment method session confirm endpoint creates a payment method based on the `payment_method_session` data. If tokenization paramet... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/events.rs`
- `crates/api_models/src/events/payment.rs`
- `crates/api_models/src/payment_methods.rs`
- ... and 2 more files
**2. Database Layer (Querie... | {"pr_number": 7248, "pr_title": "feat(payment_method_session): implement payment methods session confirm", "merged_at": "2025-02-26T18:13:18Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/event... |
<!-- Describe your changes in detail -->
This PR fixes Cypress tests for Itaubank, Paybox and Datatrans.
Datatrans still fail. Datatrans fails because `ResponseCustom` needs a refactor while Paybox requires us to pass `FR` as country and upon fixing it, it started to say wrong creds.
Facilitapay has no issues.... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `cypress-tests/cypress/e2e/configs/Payment/Datatrans.js`
- `cypress-tests/cypress/e2e/configs/Payment/ItauBank.js`
- `cypress-tests/cypress/e2e/configs/Payment/Modifiers.js`
- ... and 1 more files... | {"pr_number": 8229, "pr_title": "fix(cypress): fix itaubank, datatrans and facilitapay", "merged_at": "2025-06-10T10:26:47Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user", "connector"]}, "hierarchy": {"tests": ["cypress-tests/cypress/e2e/configs/Payment/Datatrans.j... |
Deprecated groups include:
1. organizationManage
2. merchantDetailsView
3. merchantDetailsManage
These permissions are equivalent to
organizationManage == accountManage
merchantDetailsManage == accountManage
merchantDetailsView == accountView
Also earlier validation blocks organizationManage when creatin... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Utils**
- `crates/router/src/utils/user_role.rs`
**2. Other**
- `crates/common_enums/src/enums.rs`
- `crates/router/src/services/authorization/info.rs`
- `crates/router/src/services/authorization/permissio... | {"pr_number": 9604, "pr_title": "refactor(users): remove deprecated permission groups", "merged_at": "2025-10-16T07:26:55Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["merchant"]}, "hierarchy": {"utils": ["crates/router/src/utils/user_role.rs"], "other": ["crates/common_enums/src... |
Hotfix for https://github.com/juspay/hyperswitch/pull/6725 | 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": 6831, "pr_title": "feat(core): payment links - add support for custom background image and layout in details section", "merged_at": "2024-12-12T17:58:15Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"api_models": ["crates/api_models/src/admin.rs", "... |
<!-- Describe your changes in detail -->
Closes - #5175 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Other**
- `README.md`
- `docs/imgs/hyperswitch-logo-dark.svg`
- `docs/imgs/hyperswitch-logo-light.svg`
- ... and 2 more files | {"pr_number": 6368, "pr_title": "docs: upload new logos", "merged_at": "2024-10-18T14:34:22Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"other": ["README.md", "docs/imgs/hyperswitch-logo-dark.svg", "docs/imgs/hyperswitch-logo-light.svg", "docs/imgs/hyperswitch-... |
Ref [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": 8508, "pr_title": "fix(connector): [TRUSTPAY] Consuming Amount in PSync Response", "merged_at": "2025-07-01T09:56:26Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors/trustpay.rs", "crates/hyp... |
<!-- 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/api_keys.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/api_keys.rs`
- `crates/diesel_models/src/query/api_keys.rs`
**3. Core ... | {"pr_number": 6324, "pr_title": "refactor(router): Introduce ApiKeyId id type", "merged_at": "2024-10-21T14:14:20Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/api_keys.rs"], "database": ["crates/diesel_models/src/a... |
<!-- Describe your changes in detail -->
This PR updates the lineage context Redis caching logic to use a dedicated global Redis key prefix (`global`) instead of the default tenant-scoped prefixes (`public_`, `public_v2_`), causing inconsistencies between deployments (i.e., v1 and v2).
Introduced a new helper: `get... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Utils**
- `crates/router/src/utils/user.rs`
**Code Patterns Applied:**
- Implement new functions (1 changes)
- Extend existing types with new fields (7 changes) | {"pr_number": 7892, "pr_title": "feat(user): use global redis key prefix for user lineage context", "merged_at": "2025-04-24T17:38:33Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["merchant", "user"]}, "hierarchy": {"utils": ["crates/router/src/utils/user.rs"]}, "change_types": {"... |
<!-- Describe your changes in detail -->
template for hyperwallet integration | 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/common_enums/src/connector_enums.rs`
- `crates/connector_... | {"pr_number": 8926, "pr_title": "feat(connector): [Hyperwallet] template code", "merged_at": "2025-08-14T08:29:02Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/connector_endpoints.rs"], "connectors": ["crates/commo... |
<!-- Describe your changes in detail -->
- card network fetch from db was not being populated in payment call resulting in sending the default value which failed the payment
- util function have been added to collect the card network from additional_payment_method_data
- ucaf_indicator is being populated for masterc... | 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/business_profile.rs`
**2. Core Business Logic**
- `crates/router/src/core/admin.rs`
- `crates/router/src/core/payments/transforme... | {"pr_number": 7481, "pr_title": "fix(router): pass card network for external 3DS from additional_payment_method_data", "merged_at": "2025-03-11T15:42:49Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"domain": ["crates/hyperswitch_... |
<!-- Describe your changes in detail -->
add `sdk-type` and `default-sdk-type` in netcetera authentication request
add `sdk-type` in SDK Information of PaymentsExternalAuthenticationRequest | 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. External Connector Integration**
- `crates/router/src/connector/netcetera/netcetera_types.rs`
**3. Other**
- `api-reference-v2/openapi... | {"pr_number": 7156, "pr_title": "fix(connector): [NETCETERA] add `sdk-type` and `default-sdk-type` in netcetera authentication request", "merged_at": "2025-02-03T19:31:57Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment"]}, "hierarchy": {"api_models": ["crates/api_models/src... |
<!-- Describe your changes in detail -->
Hotfix for [PR](https://github.com/juspay/hyperswitch/pull/8518) | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/payments.rs`
**2. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/payment_attempt.rs`
- `crates/diesel_models/src/payment_intent.rs`
-... | {"pr_number": 8578, "pr_title": "fix(connector): [CYBERSOURCE] Passing pares_status for MasterCard & Visa and transaction_type field", "merged_at": "2025-07-08T18:57:17Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"api_models": ["crates/api_models/src/payments.r... |
<!-- Describe your changes in detail -->
Clippy screenshot
 | 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": 8108, "pr_title": "fix(connector): [CYBERSOURCE] fix CartesBancaires card_type for Cybersource", "merged_at": "2025-05-22T09:47:47Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors/adyen... |
<!-- Describe your changes in detail -->
Nanosecond level precision for time based fields | 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/fraud_check_event.rs`
- `crates/router/src/services/kafka/payment_attempt_event.rs`
- ... and 2 more files | {"pr_number": 8759, "pr_title": "chore(events): making events nanosecond level precision", "merged_at": "2025-08-06T12:20:15Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"other": ["crates/router/src/services/kafka/dispute_event.rs", "crates/router/src/serv... |
<!-- Describe your changes in detail -->
Template PR for Hipay | 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": 7360, "pr_title": "feat(hipay): Add Template PR", "merged_at": "2025-03-07T07:57:40Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": []}, "hierarchy": {"core_business": ["crates/router/src/core/admin.rs", "crates/router/src/core/payments/connector_integration_v2_impls.rs... |
<!-- Describe your changes in detail -->
This PR adds necessary payment method configs to the GlobalPay connector.
For wallets (Paypal, Apple Pay and Google Pay), their developer docs does not mention about them being support while their main page says it to be supported. Have got in touch with the team asking fo... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Type Definitions**
- `crates/currency_conversion/src/types.rs`
**2. Utils**
- `crates/kgraph_utils/src/transformers.rs`
**3. Tests**
- `config/deployments/integration_test.toml`
- `cypress-tests/cypress/e... | {"pr_number": 7512, "pr_title": "chore: update payment method configs for globalpay", "merged_at": "2025-03-20T07:39:28Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "connector"]}, "hierarchy": {"types": ["crates/currency_conversion/src/types.rs"], "utils": ... |
<!-- Describe your changes in detail -->
This PR extends the connector feature matrix response to include threeds and non_threeds support flags along with card network details in case of cards
> This PR won't affect Payments | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. API Request/Response Models**
- `crates/api_models/src/feature_matrix.rs`
**2. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/router_response_types.rs`
**3. External Connector Integrat... | {"pr_number": 6963, "pr_title": "feat(router): add payment method-specific features to connector feature list", "merged_at": "2025-01-21T09:36:09Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["payment", "refund", "connector"]}, "hierarchy": {"api_models": ["crates/api_models/src/feature... |
<!-- Describe your changes in detail -->
Removed deprecated PMTs from Ayden: https://www.adyen.com/payment-methods | 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": 7100, "pr_title": "refactor(connector): [Adyen] Removed deprecated PMTs from Ayden (Giropay, Sofort)", "merged_at": "2025-02-12T08:48:54Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user"]}, "hierarchy": {"connectors": ["crates/connector_configs/toml/dev... |
<!-- Describe your changes in detail --> | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/checkout/transformers.rs`
**2. Tests**
- `config/deployments/integration_test.toml`
**3. Configuration Files**
- `config/deplo... | {"pr_number": 9356, "pr_title": "fix(connector): [checkout] Add US Support for Apple Pay and Google Pay + Enhanced Checkout Response Data", "merged_at": "2025-09-11T13:22:02Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connector... |
<!-- Describe your changes in detail -->
this pr makes the amount for refund and capture configurable within connector configs.
standardizes the amount to be 6000 while making partial amount to be 2000.
while doing so, a lot of config clean up has been done. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `cypress-tests/cypress/e2e/configs/Payment/Adyen.js`
- `cypress-tests/cypress/e2e/configs/Payment/BankOfAmerica.js`
- `cypress-tests/cypress/e2e/configs/Payment/Bluesnap.js`
- ... and 43 more file... | {"pr_number": 7219, "pr_title": "refactor(cypress): make amount configurable", "merged_at": "2025-02-12T08:23:26Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user", "refund", "connector"]}, "hierarchy": {"tests": ["cypress-tests/cypress/e2e/configs/Payment/Adyen.js", "cypress-te... |
<!-- Describe your changes in detail -->
Integrated CIT/MIT and setup mandate flow.
Added `setup_future_usage` to `PaymentsSyncData` to support mandate payments.
For mandate flows, the source_id (connector mandate ID) must be stored in the MandateReference. To identify whether a payment is mandate-based, we need t... | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/router_request_types.rs`
**2. Core Business Logic**
- `crates/router/src/core/payments/transformers.rs`
**3. External Connector Int... | {"pr_number": 9248, "pr_title": "feat(connector): [checkout] Add mandate flow", "merged_at": "2025-09-10T08:51:15Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"domain": ["crates/hyperswitch_domain_models/src/router_request_types.... |
Implement Banktransfer PaymentMethod
- SepabankTransfer
- InstantBankTransfer | 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": 7575, "pr_title": "feat(connector): [TRUSTPAY] implement Banktransfer PaymentMethod", "merged_at": "2025-03-25T14:58:25Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/payments.rs... |
This PR adds SEK currency for cybersource | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `config/deployments/integration_test.toml`
**2. Configuration Files**
- `config/config.example.toml`
- `config/deployments/production.toml`
- `config/deployments/sandbox.toml`
- ... and 2 more... | {"pr_number": 8048, "pr_title": "feat(connector): [CYBERSOURCE] add SEK currency for cybersource", "merged_at": "2025-05-19T11:08:01Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "user"]}, "hierarchy": {"tests": ["config/deployments/integration_test.toml"], ... |
<!-- Describe your changes in detail -->
Removed bank_name field from ideal request and language field from klarna request as it is optional. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/airwallex/transformers.rs`
- `crates/payment_methods/src/configs/payment_connector_required_fields.rs`
**Code Patterns Applied:**
... | {"pr_number": 9060, "pr_title": "fix(connector): [Airwallex] Remove optional fields for Ideal and Klarna pm", "merged_at": "2025-08-28T11:52:06Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_conne... |
<!-- Describe your changes in detail -->
Implement card payment with Worldpay xml
Hotfix for https://github.com/juspay/hyperswitch/pull/8076
> Note: Status updation takes 5-10 mins at the connector
## How did you test it?
<!--
Did you write an integration/unit/API test to verify the code changes?
Or did yo... | To implement this **payment** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/admin.rs`
**2. External Connector Integration**
- `crates/common_enums/src/connector_enums.rs`
- `crates/connector_configs/src/connector.rs`
- `crates/connector_co... | {"pr_number": 8154, "pr_title": "feat(connector): [Worldpayxml] add card payment", "merged_at": "2025-05-27T11:45:17Z", "intent": {"feature_type": "payment", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core/admin.rs"], "connectors": ["cra... |
<!-- Describe your changes in detail -->
This PR populates UCS status_code (connector HTTP code) in response headers.
It also introduces proxy_connector_http_status_code which when enabled, configures Hyperswitch to mirror (proxy) the connector’s HTTP status code in its own response. | 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/authorize_flow.rs`
- `crates/router/src/core/payments/flows/psync_flow.rs`
- ... and 4 more files
**2. ... | {"pr_number": 8788, "pr_title": "feat(core): populate UCS status_code in response headers", "merged_at": "2025-08-05T09:02:48Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core/payments.rs", "c... |
<!-- Describe your changes in detail -->
This pull request introduces a comprehensive set of changes to add invoice management capabilities to the codebase. The changes include new data models and enums for invoices, database schema and query support, and integration with connectors and APIs for invoice-related workfl... | 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. Domain Models (Business Logic Types)**
- `crates/hyperswitch_domain_models/src/router_data_v2/flow_common_types.rs`
**3. Core Busines... | {"pr_number": 9529, "pr_title": "feat(subscriptions): Invoice record back workflow", "merged_at": "2025-10-03T19:49:18Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/subscription.rs"], "domain"... |
To consume transaction id for some error cases , where currently its not consumed for Adyen, Worldpay. This PR addresses this issue. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/router/src/connector/adyen.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (1 changes) | {"pr_number": 7061, "pr_title": "feat(connector): [ADYEN ] Consume transaction id for PaymentsPreProcessing error", "merged_at": "2025-01-22T07:01:32Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["transaction"]}, "hierarchy": {"connectors": ["crates/router/src/connector/adyen.rs"]... |
Described in #6316 (point # 2) | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/router/src/connector/worldpay.rs`
- `crates/router/src/connector/worldpay/response.rs`
- `crates/router/src/connector/worldpay/transformers.rs`
**Code Patterns Appli... | {"pr_number": 6392, "pr_title": "refactor(connector): [WorldPay] propagate refusal codes as error code and messages", "merged_at": "2024-10-22T13:03:52Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/router/sr... |
<!-- Describe your changes in detail -->
Bumped up the UCS Client dependency in order to bring in the latest changes of having first_name and last_name as SecretString types. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/unified_connector_service/transformers.rs`
**2. Configuration Files**
- `crates/external_services/Cargo.toml`
- `crates/router/Cargo.toml`
**3. Other**
- `C... | {"pr_number": 9326, "pr_title": "feat(core): Add first_name and last_name as Secret<String> Types. ", "merged_at": "2025-09-11T12:14:35Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core/unifie... |
<!-- 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/connector_enums.rs`
**2. Core Business Logic**
- `crates/router/src/core/admin.rs`
**3. External Connector Integration**
- `crates/common_enums/src/conn... | {"pr_number": 6668, "pr_title": "feat(connector): [JPMORGAN] add Payment flows for cards", "merged_at": "2024-12-22T18:18:07Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"api_models": ["crates/api_models/src/connector_enums.rs"],... |
<!-- Describe your changes in detail -->
We can update card expiry in payments method data of payment methods table using batch pm update API>
Added support to pass multiple mca ids for updating payment methods entry. | 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. Core Business Logic**
- `crates/payment... | {"pr_number": 9688, "pr_title": "feat(core): Add support to update card exp in update payment methods api", "merged_at": "2025-10-07T12:54:46Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "merchant", "user"]}, "hierarchy": {"api_models": ["crates/api_models/src/payment_... |
<!-- Describe your changes in detail -->
Previously the `mandate_details` were enough to identify the payment as mandate payment but now it is optional so a payment can be mandate even if there is no `mandate_details` but the payment's `setup_future_usage` is `off-session`. | 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`
- `crates/router/src/core/payment_methods/utils.rs`
**Code Patterns Applied:**
- Add conditional logic for feature flags or filtering (1 ... | {"pr_number": 6744, "pr_title": "refactor(constraint_graph): add setup_future_usage for mandate check in payments", "merged_at": "2024-12-10T12:12:50Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/s... |
Handled zero auth mandates for Iatapay connector in cypress automation | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Tests**
- `cypress-tests/cypress/e2e/PaymentUtils/Iatapay.js`
**Code Patterns Applied:**
- Extend existing types with new fields (29 changes) | {"pr_number": 6552, "pr_title": "ci(cypress): Fix Iatapay Zero Auth Mandates Flow", "merged_at": "2024-11-14T08:07:59Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user", "connector"]}, "hierarchy": {"tests": ["cypress-tests/cypress/e2e/PaymentUtils/Iatapay.js"]}, "cha... |
- This PR consists of the process tracker flow for Psync and Review Tasks
- **Psync Task** is created if a payment’s status is Processing with an active attempt_id
> Action: match attempt status and update the process tracker status based on that.
> Finish the current task
- This PR also includes changes in th... | 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/process_tracker.rs`
**3. Domain Models (Business Logic Types)**
- `cra... | {"pr_number": 7178, "pr_title": "feat(process_tracker): Task implementation for psync payments", "merged_at": "2025-04-30T08:25:32Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user", "connector"]}, "hierarchy": {"api_models": ["crates/api_models/src/payments.rs"], "da... |
<!-- Describe your changes in detail -->
add support for hide card nickname field for open payment links | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payment_link/payment_link_initiate/payment_link_initiator.js`
**Code Patterns Applied:**
- Extend existing types with new fields (1 changes) | {"pr_number": 6700, "pr_title": "fix(payment_link): add support for hide card nickname field for open payment links", "merged_at": "2024-12-02T14:59:17Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router... |
<!-- Describe your changes in detail -->
This PR adds support for running tests against mock server for alpha connectors. | 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": 8742, "pr_title": "feat: add ci support for mock server", "merged_at": "2025-08-01T12:56:53Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["connector"]}, "hierarchy": {"core_business": ["crates/router/src/core/connector_validation.rs"], "connectors": ["crates/common_e... |
<!-- Describe your changes in detail -->
1) Pass 3 Digit Numeric Code in CountryCode instead of the country alphaCode for Paybox 3DS Request | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/paybox/transformers.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (2 changes)
- Add conditional logic for fe... | {"pr_number": 7153, "pr_title": "fix(connector): Fix Paybox 3DS failing issue", "merged_at": "2025-02-04T19:25:06Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connectors/paybox/tr... |
<!-- 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.
replica of https://github.com/juspay/hyperswitch/pull/8093 on the main | 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": 8092, "pr_title": "fix: updated the docker setup", "merged_at": "2025-05-22T09:46:58Z", "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 -->
Integrate global Success rates for dynamic routing | 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. Database Layer (Queries & Schema)**
- `crates/diesel_models/src/dynamic_routing_stats.rs`
- `crates/diesel_models/src/schema.rs`
- `c... | {"pr_number": 6950, "pr_title": "feat(routing): Integrate global success rates", "merged_at": "2025-01-21T12:16:06Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["payment", "user", "connector"]}, "hierarchy": {"api_models": ["crates/api_models/src/routing.rs"], "database": ["crates... |
<!-- Describe your changes in detail -->
Added Apple Pay Flow for Barclaycard | 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": 8885, "pr_title": "feat(connector): [Barclaycard] Add Apple Pay Flow", "merged_at": "2025-09-09T09:45:21Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/connector_configs/toml/development.toml", ... |
<!-- Describe your changes in detail -->
The error status was previously being accepted as i32, which was causing Hyperswitch to throw an error because the connector returns the status as a String. The status has been changed to type String in this PR. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/router/src/connector/wise/transformers.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (1 changes) | {"pr_number": 7468, "pr_title": "fix(connector): [WISE] Changed error status to string", "merged_at": "2025-04-02T06:41:10Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "merchant", "connector"]}, "hierarchy": {"connectors": ["crates/router/src/connector/wise/transforme... |
<!-- Describe your changes in detail -->
Connectors which accept FormData type request, their `raw_connector_request` weren't being logged. Added masking support and logging form-data type requests. | 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`
**2. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/checkout.rs`
- `crates/hyperswitch_connectors/src/conn... | {"pr_number": 9496, "pr_title": "feat(core): Add masking support for form-data types request", "merged_at": "2025-10-07T17:32:55Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/src/core/payment_metho... |
<!-- Describe your changes in detail -->
Implemented capture and webhook flow, fix some issues in ACI | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/aci.rs`
- `crates/hyperswitch_connectors/src/connectors/aci/transformers.rs`
**2. Utils**
- `crates/common_utils/src/errors.rs`... | {"pr_number": 8349, "pr_title": "feat(connector): Implement capture and webhook flow, fix some issues in ACI", "merged_at": "2025-07-01T09:53:19Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates/hyperswitch_conn... |
<!-- Describe your changes in detail -->
connector_transaction_id of wise only support UUID format.
reference_id wont be required as value since we store the wise's transaction id.
We only send UUID to make the transaction without any error.
Hotfix raised against: https://github.com/juspay/hyperswitch/pull/8836 | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/wise/transformers.rs`
**Code Patterns Applied:**
- Extend existing types with new fields (1 changes) | {"pr_number": 8837, "pr_title": "fix(connector): [Wise] send uuid as connector_transaction_id", "merged_at": "2025-08-05T10:18:31Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "merchant", "order"]}, "hierarchy": {"connectors": ["crates/hyperswitch_connectors/src/connec... |
<!-- Describe your changes in detail -->
Script for one click docker setup, to minimise issues faced by users.
>Run the whole setup with simple command
>Show output with localhost links for different setups | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Other**
- `README.md`
- `scripts/docker_output.sh`
**Code Patterns Applied:**
- Add conditional logic for feature flags or filtering (1 changes) | {"pr_number": 7762, "pr_title": "fix: script for one click docker setup", "merged_at": "2025-04-13T21:08:39Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["user"]}, "hierarchy": {"other": ["README.md", "scripts/docker_output.sh"]}, "change_types": {"conditionals_added": 1}, "has_id... |
<!-- Describe your changes in detail -->
Populated Error Message in Incremental Authorization Flow. Added check for same amount in incremental authorization requests. | To implement this **search_filter** feature, you'll need to modify these architectural layers:
**1. Core Business Logic**
- `crates/router/src/core/payments/operations/payments_incremental_authorization.rs`
**2. External Connector Integration**
- `crates/hyperswitch_connectors/src/connectors/stripe.rs`
**Code... | {"pr_number": 9006, "pr_title": "fix(connector): [STRIPE] Populate Error Message in Incremental Authorization Flow", "merged_at": "2025-08-21T14:20:35Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"core_business": ["crates/router/... |
For acquirer CMCIC, Cybersource MIT payments needs the following field
`paymentInformation.card.typeSelectionIndicator`
This PR addresses the same | 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:**
- Define new data structures (1 changes)
- Extend existing types with new fie... | {"pr_number": 9265, "pr_title": "fix(connector): [CYBERSOURCE] Add extra field for Cybersource MIT payment for acquirer CMCIC", "merged_at": "2025-09-07T14:39:12Z", "intent": {"feature_type": "search_filter", "action": "add_feature", "entities": ["customer", "payment", "merchant"]}, "hierarchy": {"connectors": ["crates... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.