repo stringclasses 1
value | instance_id stringlengths 22 24 | problem_statement stringlengths 30 24.1k | patch stringlengths 0 1.9M | test_patch stringclasses 1
value | created_at stringdate 2022-11-25 05:12:07 2025-06-13 10:24:29 | hints_text stringlengths 0 228k | base_commit stringlengths 40 40 | test_instructions stringlengths 0 232k | filenames listlengths 0 300 |
|---|---|---|---|---|---|---|---|---|---|
juspay/hyperswitch | juspay__hyperswitch-7020 | Bug: chore: address Rust 1.84.0 clippy lints
Address the clippy lints occurring due to new rust version 1.84.0
See https://github.com/juspay/hyperswitch/issues/3391 for more information. | diff --git a/Cargo.lock b/Cargo.lock
index e34c80bd927..2007f4f88a0 100644
--- a/Cargo.lock
+++ b/Cargo.lock
@@ -9266,9 +9266,9 @@ checksum = "b8dad83b4f25e74f184f64c43b150b91efe7647395b42289f38e50566d82855b"
[[package]]
name = "wasm-bindgen"
-version = "0.2.93"
+version = "0.2.99"
source = "registry+https://githu... | 2025-01-10T09:59:26Z |
## Description
<!-- Describe your changes in detail -->
This PR addresses the clippy lints occurring due to new rust version 1.84.0
Majorly addresses `unnecessary_map_or` clippy lint - https://rust-lang.github.io/rust-clippy/master/index.html#unnecessary_map_or
## Motivation and Context
<!--
Why is this chang... | dbe0cd4d2c368293bec22e2e83571a90b8ce3ee3 |
CI checks should pass as this PR addresses clippy lints.
1. ran `just clippy` with new rust version (1.84.0)

2. ran `just clippy_v2` with new rust version (1.84.0)
;
/// In case connector's use an identifier who... | 2025-01-09T14:03:34Z |
## Description
This PR introduces below changes around Worldpay connector
### Core changes
- add new columns (TEXT) for storing the JWE based connector transaction ID
- `payment_attempt` - `processor_transaction_data`
- `refund` - `processor_transaction_data` and `processor_refund_data`
- `captures... | bfcaf003427caf9580a2520b3f2efc8773818905 | <details>
<summary>1. Route a payment through Worldpay</summary>
cURL
curl --location --request POST 'http://localhost:8080/payments' \
--header 'Content-Type: application/json' \
--header 'Accept: application/json' \
--header 'api-key: dev_Wc9lMS2KJ6l35ehmlSsR3dwwiOvGZaWLmkk3B... | [
"crates/common_utils/src/types.rs",
"crates/diesel_models/src/capture.rs",
"crates/diesel_models/src/kv.rs",
"crates/diesel_models/src/payment_attempt.rs",
"crates/diesel_models/src/query/capture.rs",
"crates/diesel_models/src/refund.rs",
"crates/diesel_models/src/schema.rs",
"crates/diesel_models/src... | |
juspay/hyperswitch | juspay__hyperswitch-7014 | Bug: [REFACTOR] modify dynamic fields path
This PR modifies dynamic fields path of Adyen and Stripe for Klarna. Also klarnaCheckout is renamed to klarnaRedirect. | diff --git a/api-reference-v2/openapi_spec.json b/api-reference-v2/openapi_spec.json
index 892931256bc..25f0be8594a 100644
--- a/api-reference-v2/openapi_spec.json
+++ b/api-reference-v2/openapi_spec.json
@@ -12387,17 +12387,6 @@
}
}
},
- {
- "type": "object",
... | 2025-01-09T10:40:38Z |
## Description
<!-- Describe your changes in detail -->
1. Dynamic fields path for `Adyen` and `Stripe` is changed which is a frontend requirement
2. `WASM` for `klarnaCheckout` added in `Klarna` which is a dashboard requirement.
3. Removed `KlarnaCheckout` enum and using the already present `KlarnaRedirect` enum... | 3fdc41e6c946609461db6b5459e10e6351694d4c |
1. Dynamic fields path for `Adyen` and `Stripe` is changed which is a frontend requirement to show the input boxes, so no testing required.
2. `WASM` for `klarnaCheckout` added in `Klarna` which is a dashboard requirement to list out the Payment Methods for `Klarna`, so no testing required.
3. Have removed `Kla... | [
"api-reference-v2/openapi_spec.json",
"crates/api_models/src/payments.rs",
"crates/connector_configs/src/transformer.rs",
"crates/connector_configs/toml/development.toml",
"crates/connector_configs/toml/production.toml",
"crates/connector_configs/toml/sandbox.toml",
"crates/hyperswitch_connectors/src/co... | |
juspay/hyperswitch | juspay__hyperswitch-7010 | Bug: [FEATURE] [Authorizedotnet]: Add metadata information to connector request
### Feature Description
[Authorizedotnet]: Add metadata information to connector request
### Possible Implementation
[Authorizedotnet]: Add metadata information to connector request
### Have you spent some time checking if this featu... | diff --git a/crates/router/src/connector/authorizedotnet/transformers.rs b/crates/router/src/connector/authorizedotnet/transformers.rs
index d2b212e3ea0..8e0af603a3d 100644
--- a/crates/router/src/connector/authorizedotnet/transformers.rs
+++ b/crates/router/src/connector/authorizedotnet/transformers.rs
@@ -1,3 +1,5 @@... | 2025-01-08T08:42:03Z |
## Description
<!-- Describe your changes in detail -->
This PR is for code changes which sends the metadata passed in payment intent create to authorizedotnet as request payload, as per merchant requirements.
The merchant receives a receipt of the transaction through email, which contains the metadata passed... | ad5491f15bd8f61b2a918f584fe85132986176ad |
**Postman Tests**
**1. Authorize (Manual)**
- Request
```
curl --location 'http://localhost:8080/payments' \
--header 'Content-Type: application/json' \
--header 'Accept: application/json' \
--header 'api-key: dev_0vV4HvaBn68pmZTvXLzU9V7hR79lgEjiarEG2IDxveccjZ6ypKjpPaRrdeQRHhKu' \
--data-raw '{
... | [
"crates/router/src/connector/authorizedotnet/transformers.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-7009 | Bug: [fix]: dummy connector on multitenancy
| diff --git a/crates/hyperswitch_domain_models/src/router_data.rs b/crates/hyperswitch_domain_models/src/router_data.rs
index 2970ac127ed..8e4c79a965e 100644
--- a/crates/hyperswitch_domain_models/src/router_data.rs
+++ b/crates/hyperswitch_domain_models/src/router_data.rs
@@ -22,6 +22,7 @@ pub struct RouterData<Flow, R... | 2025-01-08T08:03:12Z |
## Description
<!-- Describe your changes in detail -->
Add tenant id in dummy connector requests
## 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 fir... | d594173de2aefaedce0c808f5d4903d0ad7eb447 |
1. Create `stripe_test` PaymentsConnector
```bash
curl --location 'http://localhost:8080/account/1736322673/connectors' \
--header 'cache-control: no-cache' \
--header 'content-type: application/json' \
--header 'x-tenant-id: public' \
--header 'api-key: test_admin' \
--data '{
"connector_type": "payment_... | [
"crates/hyperswitch_domain_models/src/router_data.rs",
"crates/hyperswitch_domain_models/src/router_data_v2.rs",
"crates/router/src/connector/dummyconnector.rs",
"crates/router/src/core/authentication.rs",
"crates/router/src/core/authentication/transformers.rs",
"crates/router/src/core/fraud_check/flows/c... | |
juspay/hyperswitch | juspay__hyperswitch-7005 | Bug: feat(analytics): Add currency as dimension and filter for disputes
Should add currency as dimension and filter for disputes, required for Analytics V2 Dashboard.
| diff --git a/crates/analytics/src/disputes/core.rs b/crates/analytics/src/disputes/core.rs
index 540a14104c1..c1dcbaf2b2f 100644
--- a/crates/analytics/src/disputes/core.rs
+++ b/crates/analytics/src/disputes/core.rs
@@ -204,6 +204,7 @@ pub async fn get_filters(
.filter_map(|fil: DisputeFilterRow| match dim {
... | 2025-01-08T05:53:25Z |
## Description
<!-- Describe your changes in detail -->
Added currency as dimension and filter for disputes, required for Analytics V2 Dashboard.
## 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 ha... | ed8ef2466b7f059ed0f534aa1f3fca9b5ecbeefd |
Hit the curl:
```bash
curl --location 'http://localhost:8080/analytics/v1/org/metrics/disputes' \
--header 'Accept: */*' \
--header 'Accept-Language: en-US,en;q=0.9' \
--header 'Connection: keep-alive' \
--header 'Content-Type: application/json' \
--header 'Origin: http://localhost:9000' \
--header 'QueryType... | [
"crates/analytics/src/disputes/core.rs",
"crates/analytics/src/disputes/filters.rs",
"crates/analytics/src/disputes/metrics.rs",
"crates/analytics/src/disputes/metrics/dispute_status_metric.rs",
"crates/analytics/src/disputes/metrics/sessionized_metrics/dispute_status_metric.rs",
"crates/analytics/src/dis... | |
juspay/hyperswitch | juspay__hyperswitch-7003 | Bug: [FIX] consider status of payment method before filtering wallets in list pm
| diff --git a/crates/router/src/core/payment_methods/cards.rs b/crates/router/src/core/payment_methods/cards.rs
index 164c0e9557a..deae78b5540 100644
--- a/crates/router/src/core/payment_methods/cards.rs
+++ b/crates/router/src/core/payment_methods/cards.rs
@@ -3470,12 +3470,14 @@ pub async fn list_payment_methods(
... | 2025-01-07T13:44:49Z |
## Description
<!-- Describe your changes in detail -->
https://github.com/juspay/hyperswitch/pull/3953
We were not considering the status of payment method in above filtering logic
## Motivation and Context
<!--
Why is this change required? What problem does it solve?
If it fixes an open issue, please lin... | c4d36b506e159f39acff17e13f72b5c53edec184 |
1. Create merchant_account, api_key, mca (with any wallet)
2. Create a payment with wallet as payment method with authentication_type as three_ds. Retain the status of payment as processing
```
curl --location 'http://localhost:8080/payments' \
--header 'Content-Type: application/json' \
--header 'Accept: appl... | [
"crates/router/src/core/payment_methods/cards.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-6993 | Bug: [REFACTOR] reduce duplicate code in config in cypress
- too much chaos and confusion
- boiler plate and duplicate code
- move memory cache test out of payments and make it a separate service | 2025-01-06T09:12:46Z |
## Description
<!-- Describe your changes in detail -->
This PR aims at refactoring:
- `cypress-tests` folder structure to reduce confusion and chaos in within `e2e` directory
- previous:
```sh
.
└── cypress
├── e2e
│ ├── PaymentMethodListTest
│ ├── PaymentMethodListUtils
... | cf82861e855bbd055fcbfc2367b23eaa58d8f842 |
```sh
| [] | ||
juspay/hyperswitch | juspay__hyperswitch-6999 | Bug: feat(roles): edge cases for multi-tenancy - I
Add tenant_id in custom roles
Add generic query to search across all tenants
Close https://github.com/juspay/hyperswitch-cloud/issues/7998
Close https://github.com/juspay/hyperswitch-cloud/issues/7998
Close https://github.com/juspay/hyperswitch-cloud/issues/8026 | diff --git a/crates/diesel_models/src/query/role.rs b/crates/diesel_models/src/query/role.rs
index 6f6a1404ee2..2ab58ec2382 100644
--- a/crates/diesel_models/src/query/role.rs
+++ b/crates/diesel_models/src/query/role.rs
@@ -32,14 +32,18 @@ impl Role {
role_id: &str,
merchant_id: &id_type::MerchantId,... | 2025-01-05T20:12:09Z |
## Description
This PR
- add tenant_id in roles table
- add support for genenric query to serach user across all tenancies
- Fixes custom roles creates by tenant_level user
- List view for tenant level user
- Fix bug to search across envs for tenant admin
## Motivation and Context
Closes [#6999](https://git... | 79013024ff371efc6062310564b8b56e9bb22701 | Tenant admin able to create custom org level role
```
curl --location 'http://localhost:8080/user/role' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer JWT' \
--data '{
"role_name": "custom_role_7",
"groups": ["users_view"],
"role_scope": "organization"
}'
```
Response
``... | [
"crates/diesel_models/src/query/role.rs",
"crates/diesel_models/src/query/user_role.rs",
"crates/diesel_models/src/role.rs",
"crates/diesel_models/src/schema.rs",
"crates/diesel_models/src/schema_v2.rs",
"crates/router/src/analytics.rs",
"crates/router/src/core/user.rs",
"crates/router/src/core/user_r... | |
juspay/hyperswitch | juspay__hyperswitch-6983 | Bug: [CHORE] remove redundant variants from PermissionGroup
### Feature Description
Few variants in `PermissionGroup` enum were kept in the application code for backwards compatibility. These variants are directly stored as TEXT in DB which forces the application to ensure backwards compatibility during staggered r... | diff --git a/crates/common_enums/src/enums.rs b/crates/common_enums/src/enums.rs
index 0234fbea6d5..1faa3b90aa8 100644
--- a/crates/common_enums/src/enums.rs
+++ b/crates/common_enums/src/enums.rs
@@ -2936,8 +2936,6 @@ pub enum PermissionGroup {
ReconReportsManage,
ReconOpsView,
ReconOpsManage,
- // T... | 2025-01-03T10:45:05Z |
## Description
This removes the redundant `ReconOps` variant from `PermissionGroup` enum which is stored in DB. This was kept back in application for backwards compatibility. Migrations are added for this and this will not be needed anymore.
## Motivation and Context
Helps in keeping a clean permission view on H... | 22072fd750940ac7fec6ea971737409518600891 | Locally by running migrations and viewing permission view in dashboard.
| [
"crates/common_enums/src/enums.rs",
"crates/router/src/services/authorization/info.rs",
"crates/router/src/services/authorization/permission_groups.rs",
"migrations/2025-01-03-104019_migrate_permission_group_for_recon/down.sql",
"migrations/2025-01-03-104019_migrate_permission_group_for_recon/up.sql"
] | |
juspay/hyperswitch | juspay__hyperswitch-6979 | Bug: [CHORE] extend Currency TYPE in DB with more variants
### Feature Description
Below currencies to be added to the Currency type in DB
AFN
BTN
CDF
ERN
IRR
ISK
KPW
SDG
SYP
TJS
TMT
ZMW
ZWL
### Possible Implementation
Add diesel migrations
### Have you spent some time checking if this feature req... | diff --git a/migrations/2025-01-03-084904_add_currencies/down.sql b/migrations/2025-01-03-084904_add_currencies/down.sql
new file mode 100644
index 00000000000..e0ac49d1ecf
--- /dev/null
+++ b/migrations/2025-01-03-084904_add_currencies/down.sql
@@ -0,0 +1 @@
+SELECT 1;
diff --git a/migrations/2025-01-03-084904_add_cur... | 2025-01-03T08:54:40Z |
## Description
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
```
## Motivation and Context
<!--
Why is this change required? What problem does it solve?
If it fixes an open issue, please link to... | 2aa14e7fec19b31d84745b524cbf835ff16b8ce8 | Ran migrations locally.
| [
"migrations/2025-01-03-084904_add_currencies/down.sql",
"migrations/2025-01-03-084904_add_currencies/up.sql"
] | |
juspay/hyperswitch | juspay__hyperswitch-6977 | Bug: [BUG - Cypress] Cookie not passed in user APIs
we need to pass cookies in user apis | 2025-01-02T15:58:49Z |
## Description
<!-- Describe your changes in detail -->
this pr fixes the issue where cookies are not being set when hitting user apis.
- we need to set cookies. but cypress does not directly support that
- `cy.setCookie()` method does not persist outside of the `it()` block
- in order to make it persist, we... | 7d00583a8076ef2f996345549b5e81c7f90361dc |
<img width="540" alt="image" src="https://github.com/user-attachments/assets/5d1f0463-e9a2-4ee7-9597-65151c85539e" />
every failure here is related to assertion and `globalState` where `connectorId` and `mcaId` not getting updated. This can be picked up a separate PR since the fix done in this PR is `P0`
| [] | ||
juspay/hyperswitch | juspay__hyperswitch-6975 | Bug: add support for relay refund incoming webhooks
Some connectors, like Adyen, do not support a refund sync API, so we need to rely on refund webhooks for the status. To address this, support for relay refund webhooks needs to be added.
To support this use case, a new webhook endpoint needs to be introduced for... | diff --git a/crates/api_models/src/webhooks.rs b/crates/api_models/src/webhooks.rs
index e6f4065eb7a..f99e3a450b2 100644
--- a/crates/api_models/src/webhooks.rs
+++ b/crates/api_models/src/webhooks.rs
@@ -120,6 +120,10 @@ pub enum WebhookResponseTracker {
status: common_enums::MandateStatus,
},
NoEff... | 2025-01-02T13:49:11Z |
## Description
<!-- Describe your changes in detail -->
Some connectors, like Adyen, do not support a refund sync API, so we need to rely on refund webhooks for the status. To address this, support for relay refund webhooks is being added.
To support this use case, a new webhook endpoint needs to be introduced fo... | c4d36b506e159f39acff17e13f72b5c53edec184 |
-> Create a merchant connector account for stripe
-> Setup the webhook url in the stripe dashboard
-> Relay webhook testing
-> Make payment through stripe connector. As this relay webhooks can only handle relay refunds webhooks, we need to return 200 OK for the payments webhooks that we received.
```
curl --loca... | [
"crates/api_models/src/webhooks.rs",
"crates/common_utils/src/id_type/relay.rs",
"crates/diesel_models/src/query/relay.rs",
"crates/hyperswitch_domain_models/src/relay.rs",
"crates/router/src/core/webhooks/incoming.rs",
"crates/router/src/core/webhooks/incoming_v2.rs",
"crates/router/src/db/relay.rs",
... | |
juspay/hyperswitch | juspay__hyperswitch-6972 | Bug: [feat] add multitenancy support to keymanager
| diff --git a/config/config.example.toml b/config/config.example.toml
index 99926632114..eb30435d5f8 100644
--- a/config/config.example.toml
+++ b/config/config.example.toml
@@ -762,7 +762,7 @@ sdk_eligible_payment_methods = "card"
[multitenancy]
enabled = false
-global_tenant = { schema = "public", redis_key_prefix... | 2025-01-02T09:46:41Z |
## Description
<!-- 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 o... | 7d00583a8076ef2f996345549b5e81c7f90361dc |
- Create Merchant Account with x-tenant-id as `public`
```bash
curl --location 'http://localhost:8080/accounts' \
--header 'Content-Type: application/json' \
--header 'Accept: application/json' \
--header 'x-feature: integ-custom' \
--header 'x-tenant-id: public' \
--header 'api-key: test_admin' \
--data-raw ... | [
"config/config.example.toml",
"config/deployments/env_specific.toml",
"config/development.toml",
"config/docker_compose.toml",
"crates/common_utils/src/consts.rs",
"crates/common_utils/src/id_type/tenant.rs",
"crates/common_utils/src/keymanager.rs",
"crates/common_utils/src/types/keymanager.rs",
"cr... | |
juspay/hyperswitch | juspay__hyperswitch-6973 | Bug: refactor(redis_interface): make the redis command for using scripts to write into redis Generic
make the redis command for using scripts to write into redis as Generic | diff --git a/crates/redis_interface/src/commands.rs b/crates/redis_interface/src/commands.rs
index 3c7ffa16ada..56e9ab98104 100644
--- a/crates/redis_interface/src/commands.rs
+++ b/crates/redis_interface/src/commands.rs
@@ -849,20 +849,23 @@ impl super::RedisConnectionPool {
}
#[instrument(level = "DEBUG",... | 2025-01-02T08:33:31Z |
## Description
make the redis command for using scripts to write into redis Generic, for allowing the flexibility to update the redis
## 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 issu... | 638e1f230a543a1ff2b7712d04b937a9a9db1969 | wrote a unit test for it
| [
"crates/redis_interface/src/commands.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-6960 | Bug: [REFACTOR] add info logs to log the grpc request and response
| diff --git a/crates/external_services/src/grpc_client.rs b/crates/external_services/src/grpc_client.rs
index 404685025ed..7a627d3ab27 100644
--- a/crates/external_services/src/grpc_client.rs
+++ b/crates/external_services/src/grpc_client.rs
@@ -128,3 +128,13 @@ impl<T> AddHeaders for tonic::Request<T> {
});
... | 2024-12-30T16:03:02Z |
## Description
<!-- Describe your changes in detail -->
This PR adds the info logs to log the dynamic routing grpc requests and response objects.
## 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 ha... | 4664d4bc4b7e685ab6dfb9176a3309026d3032e9 |
1. Create merchant_account, api_key and mca (any connector)
2. Toggle dynamic routing
```
curl --location --request POST 'http://localhost:8080/account/merchant_1734609410/business_profile/pro_gPTjn9jLm0CxI8ZD1omL/dynamic_routing/success_based/toggle?enable=metrics' \
--header 'Content-Type: application/json'... | [
"crates/external_services/src/grpc_client.rs",
"crates/external_services/src/grpc_client/dynamic_routing/elimination_rate_client.rs",
"crates/external_services/src/grpc_client/dynamic_routing/success_rate_client.rs",
"crates/router/src/core/payments/routing.rs",
"proto/success_rate.proto"
] | |
juspay/hyperswitch | juspay__hyperswitch-7000 | Bug: test(cypress): add a test for in memory cache
| 2024-12-30T11:36:48Z |
## Description
<!-- Describe your changes in detail -->
Add Test Cases for testing In Memory Cache
## 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 f... | c4d36b506e159f39acff17e13f72b5c53edec184 |
<img width="1025" alt="Screenshot 2024-12-30 at 3 28 02 PM" src="https://github.com/user-attachments/assets/8059ee3c-f695-452f-ac74-3909849559d3" />
<img width="1028" alt="Screenshot 2024-12-30 at 3 28 10 PM" src="https://github.com/user-attachments/assets/d6d12ca8-3802-4a3a-94d8-0382bf8e1fb2" />
| [] | ||
juspay/hyperswitch | juspay__hyperswitch-1039 | Bug: [FEATURE] Use proxy exclusion instead of a separate proxied client
### Feature Description
Currently we provide the option for proxying all external requests made to Connectors. We also use reqwest clients to make API calls to basilisk/locker or other utilities.
Recently we started reusing the `reqwest::Cli... | diff --git a/config/config.example.toml b/config/config.example.toml
index eb30435d5f8..821e854c9fa 100644
--- a/config/config.example.toml
+++ b/config/config.example.toml
@@ -23,11 +23,10 @@ certificate = "/path/to/certificate.pem"
# Proxy server configuration for connecting to payment gateways.
# Don't define the ... | 2024-12-29T12:26:39Z |
## Description
<!-- Describe your changes in detail -->
This PR refactors the logic for excluding specific HTTP / HTTPS traffic from being proxied via the outgoing proxy. Specifically, the changes included are:
1. We no longer need two clients (a proxied client and a non-proxied client), we can have the same cl... | dbe0cd4d2c368293bec22e2e83571a90b8ce3ee3 |
Locally, by setting up [`mitmproxy`](https://mitmproxy.org) as a proxy for outgoing HTTP and HTTPS traffic. I also set up our card vault locally to simulate an internal service running close to the application.
I ran `mitmproxy` using the command:
```shell
mitmweb --listen-port 8090 --web-port 8091
```
A... | [
"config/config.example.toml",
"config/deployments/env_specific.toml",
"crates/common_enums/src/enums.rs",
"crates/router/src/bin/scheduler.rs",
"crates/router/src/configs/defaults.rs",
"crates/router/src/configs/settings.rs",
"crates/router/src/lib.rs",
"crates/router/src/services/api.rs",
"crates/r... | |
juspay/hyperswitch | juspay__hyperswitch-6955 | Bug: [DOC] update cypress docs
current docs are pretty much outdated | 2024-12-28T17:24:37Z |
## Description
<!-- Describe your changes in detail -->
Existing [docs](https://github.com/juspay/hyperswitch/tree/main/cypress-tests) are outdated to an extent and miss many feature updates.
closes https://github.com/juspay/hyperswitch/issues/6955
## Motivation and Context
<!--
Why is this change require... | e393a036fbde109d367e488807a53e919a12db90 |
Nah!
| [] | ||
juspay/hyperswitch | juspay__hyperswitch-6987 | Bug: [FEATURE] Integrate global SR
### Feature Description
In dynamic routing, we need to keep track of global success rates as well. We need to support the integration for tracking global SR
### Possible Implementation
The dynamic routing modules and corresponding proto file would need to be changed
### Have y... | diff --git a/crates/api_models/src/routing.rs b/crates/api_models/src/routing.rs
index 2e570816ab4..8e502767575 100644
--- a/crates/api_models/src/routing.rs
+++ b/crates/api_models/src/routing.rs
@@ -779,6 +779,7 @@ impl Default for SuccessBasedRoutingConfig {
duration_in_mins: Some(5),
... | 2024-12-26T13:46:40Z |
## Description
<!-- Describe your changes in detail -->
Integrate global Success rates for dynamic routing
## 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 ... | 72904842ed0092e16e2d9980e1d4968df03cafb6 |
1. toggle success based routing with dynamic connector selection enabled
```
curl --location --request POST 'http://localhost:8080/account/sarthak2/business_profile/pro_F5mC1GGXHPLTtfcBnZEP/dynamic_routing/success_based/toggle?enable=dynamic_connector_selection' \
--header 'api-key: dev_RQxKf8JqHb5tTfTp13JMnI7TyWg... | [
"crates/api_models/src/routing.rs",
"crates/diesel_models/src/dynamic_routing_stats.rs",
"crates/diesel_models/src/schema.rs",
"crates/diesel_models/src/schema_v2.rs",
"crates/external_services/src/grpc_client/dynamic_routing/success_rate_client.rs",
"crates/openapi/src/openapi.rs",
"crates/router/src/c... | |
juspay/hyperswitch | juspay__hyperswitch-6944 | Bug: [REFACTOR] remove `tenant_id` prefix from `id` field in dynamic routing grpc requests
| diff --git a/crates/router/src/core/payments/routing.rs b/crates/router/src/core/payments/routing.rs
index 0a57819816f..8f3f40edf06 100644
--- a/crates/router/src/core/payments/routing.rs
+++ b/crates/router/src/core/payments/routing.rs
@@ -1347,14 +1347,9 @@ pub async fn perform_success_based_routing(
... | 2024-12-26T12:53:24Z |
## Description
<!-- Describe your changes in detail -->
Since hyperswitch started sending tenant-id in headers of dynamic routing grpc requests, we can safely remove the tenant-id prefixed in `id` field
## Motivation and Context
<!--
Why is this change required? What problem does it solve?
If it fixes an open... | 295d3dde7749e7576dbdee4675528bb6dd6ffb70 |
1. Create merchant_account, api_key and mca (any connector)
2. Toggle dynamic routing
```
curl --location --request POST 'http://localhost:8080/account/merchant_1734609410/business_profile/pro_gPTjn9jLm0CxI8ZD1omL/dynamic_routing/success_based/toggle?enable=metrics' \
--header 'Content-Type: application/json' \... | [
"crates/router/src/core/payments/routing.rs",
"crates/router/src/core/routing.rs",
"crates/router/src/core/routing/helpers.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-6941 | Bug: [FEATURE] integrate NTI flow for Worldpay and Novalnet
### Feature Description
Processing card payments using Network Transaction ID is required for below payment processors -
- Fiuu
- Novalnet
- Worldpay
This helps make card payments agnostic to the acquirer.
### Possible Implementation
Fiuu - c... | diff --git a/config/config.example.toml b/config/config.example.toml
index 821e854c9fa..c860420da38 100644
--- a/config/config.example.toml
+++ b/config/config.example.toml
@@ -802,7 +802,7 @@ check_token_status_url= "" # base url to check token status from token servic
connector_list = "cybersource" # Supported co... | 2024-12-26T11:38:07Z |
## Description
Described in #6941
This PR adds NTI flow integrations for below connectors
- Fiuu - store NTI ID in `payment_methods` from connector's PSync response
- Novalnet - use NTI ID for card payments
- Worldpay - store and use NTI ID for card payments
## Motivation and Context
<!--
Why is this c... | d01172a613b8e74564eef792b8a6915c647854fc |
<details>
<summary>1. CIT for cards through Adyen</summary>
cURL
curl --location --request POST 'http://localhost:8080/payments' \
--header 'Content-Type: application/json' \
--header 'Accept: application/json' \
--header 'api-key: dev_rh7Gdbe4bpB4Vxz9A7SQge8NwmI48LHgckedcW... | [
"config/config.example.toml",
"config/deployments/integration_test.toml",
"config/deployments/sandbox.toml",
"config/development.toml",
"config/docker_compose.toml",
"crates/hyperswitch_connectors/src/connectors/fiuu.rs",
"crates/hyperswitch_connectors/src/connectors/fiuu/transformers.rs",
"crates/hyp... | |
juspay/hyperswitch | juspay__hyperswitch-6948 | Bug: rename `management_url` to `management_u_r_l` in the apple pay session response
Parent issue describing the feature (https://github.com/juspay/hyperswitch/issues/6841)
We need to rename `management_url` to `management_u_r_l` in the apple pay session response as our sdk converts the apple pay session request ... | diff --git a/api-reference-v2/openapi_spec.json b/api-reference-v2/openapi_spec.json
index 636723d808a..f1caede89cc 100644
--- a/api-reference-v2/openapi_spec.json
+++ b/api-reference-v2/openapi_spec.json
@@ -3438,7 +3438,7 @@
"required": [
"payment_description",
"regular_billing",
- ... | 2024-12-26T10:17:29Z |
## Description
<!-- Describe your changes in detail -->
Parent issue describing the feature (https://github.com/juspay/hyperswitch/issues/6841)
We need to rename `management_url` to `management_u_r_l` in the apple pay session response as our sdk converts the apple pay session request to camelCase before sending... | b6249f226116a7cc96e602a8910e8b186eecda5b |
-> create a merchant connector account with apple pay enabled
-> create a payment with recurring details passed in the `feature_metadata`
```
{
"amount": 6500,
"currency": "USD",
"confirm": false,
"amount_to_capture": 6500,
"customer_id": "test_fb",
"capture_method": "automatic",
... | [
"api-reference-v2/openapi_spec.json",
"crates/api_models/src/payments.rs",
"crates/router/src/core/payments/transformers.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-6943 | Bug: Update open-api spec of /relay request to make the data untagged enum
Update open-api spec of /relay request to make the data untagged enum | diff --git a/crates/openapi/src/routes/relay.rs b/crates/openapi/src/routes/relay.rs
index 9100bf47f75..180fed66492 100644
--- a/crates/openapi/src/routes/relay.rs
+++ b/crates/openapi/src/routes/relay.rs
@@ -13,8 +13,10 @@
"connector_id": "mca_5apGeP94tMts6rg3U3kR",
"type": "r... | 2024-12-26T08:18:28Z |
## Description
<!-- Describe your changes in detail -->
Update open-api spec of /relay request to make the data untagged enum.
## 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 r... | b6249f226116a7cc96e602a8910e8b186eecda5b |
<img width="1616" alt="image" src="https://github.com/user-attachments/assets/4ba7d3d6-9fcd-4a29-a7ff-62f0a5abda22" />
| [
"crates/openapi/src/routes/relay.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-6939 | Bug: feat(users): Add email domain based restriction for dashboard entry APIs
Currently Zurich uses okta and they use a specific `auth_id` to see the okta login method.
If any user doesn't use `auth_id`, then the user will see the default auth methods that Hyperswitch has and they will be use them to login, which w... | diff --git a/crates/api_models/src/user.rs b/crates/api_models/src/user.rs
index 7b5911cf1a8..ea979bfe735 100644
--- a/crates/api_models/src/user.rs
+++ b/crates/api_models/src/user.rs
@@ -305,18 +305,26 @@ pub struct CreateUserAuthenticationMethodRequest {
pub owner_type: common_enums::Owner,
pub auth_method... | 2024-12-26T07:59:40Z |
## Description
<!-- Describe your changes in detail -->
There will be a mapping of email domain and auth methods.
This PR will restrict users to enter into the dashboard based on the email domain.
## Motivation and Context
<!--
Why is this change required? What problem does it solve?
If it fixes an open is... | b6249f226116a7cc96e602a8910e8b186eecda5b |
1. Create user auth method with email domain
```bash
curl --location 'http://localhost:8080/user/auth' \
--header 'Authorization: Bearer eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJ1c2VyX2lkIjoiMjAxYTJlZWQtNGE0ZC00MjZlLTg1N2ItMjNhM2ZjZTk5NTMzIiwibWVyY2hhbnRfaWQiOiJtZXJjaGFudF8xNjk3NjIzMjI0Iiwicm9sZV9pZCI6I... | [
"crates/api_models/src/user.rs",
"crates/diesel_models/src/query/user_authentication_method.rs",
"crates/diesel_models/src/schema.rs",
"crates/diesel_models/src/schema_v2.rs",
"crates/diesel_models/src/user_authentication_method.rs",
"crates/router/src/core/errors/user.rs",
"crates/router/src/core/user.... | |
juspay/hyperswitch | juspay__hyperswitch-6937 | Bug: populate `profile_id` in for the HeaderAuth of v1
populate `profile_id` in for the HeaderAuth of v1 | diff --git a/config/deployments/integration_test.toml b/config/deployments/integration_test.toml
index dd4938d8d6f..6283382258a 100644
--- a/config/deployments/integration_test.toml
+++ b/config/deployments/integration_test.toml
@@ -419,7 +419,7 @@ outgoing_enabled = true
connectors_with_webhook_source_verification_ca... | 2024-12-24T12:56:35Z |
## Description
<!-- Describe your changes in detail -->
populate `profile_id` in for the HeaderAuth of v1
And also this pr involves the changes to unmask the profile id that is sent in the headers.
## Motivation and Context
<!--
Why is this change required? What problem does it solve?
If it fixes an open iss... | b6249f226116a7cc96e602a8910e8b186eecda5b | [
"config/deployments/integration_test.toml",
"config/deployments/production.toml",
"config/deployments/sandbox.toml",
"config/development.toml",
"config/docker_compose.toml",
"crates/router/src/services/authentication.rs",
"loadtest/config/development.toml"
] | ||
juspay/hyperswitch | juspay__hyperswitch-6947 | Bug: [BUG] Connector Required Fields for Mandates not present
### Bug Description
Connector Required Fields for Mandates not present
### Expected Behavior
Connector Required Fields for Mandates present
### Actual Behavior
Connector Required Fields for Mandates not present
### Steps To Reproduce
Provide an una... | diff --git a/crates/router/src/configs/defaults/payment_connector_required_fields.rs b/crates/router/src/configs/defaults/payment_connector_required_fields.rs
index 3eda9c2a91f..0a4d58c8ded 100644
--- a/crates/router/src/configs/defaults/payment_connector_required_fields.rs
+++ b/crates/router/src/configs/defaults/paym... | 2024-12-24T08:58:02Z |
## Description
The required fields were not added for mandates for some connectors. Those fields have been configured as `required` in this PR.
Connectors I have checked for : Aci, Adyen, Authorizeddotnet, Globalpay, Multisafepay, Worldpay, Nexinets, Noon, Novalnet, Payme, Stripe, Bankofamerica, Cybersource, We... | 2b70c945406b1cf80831452b75e0c488eb60c86c |
**1. Worldpay**
- **A) Create Payment**
- Request
```
curl --location 'http://localhost:8080/payments' \
--header 'Content-Type: application/json' \
--header 'Accept: application/json' \
--header 'api-key: dev_MA7DHjl9k4izCsQ42Vh7VJEKQeNy78RkGjIISOOrAbu78sRnpwuuuJmmipITEyae' \
--data-raw '{
"amou... | [
"crates/router/src/configs/defaults/payment_connector_required_fields.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-6929 | Bug: disable partial auth feature for relay
disable partial auth feature for relay | diff --git a/config/deployments/integration_test.toml b/config/deployments/integration_test.toml
index a74ababdd26..f10ffac3e2e 100644
--- a/config/deployments/integration_test.toml
+++ b/config/deployments/integration_test.toml
@@ -411,7 +411,7 @@ outgoing_enabled = true
connectors_with_webhook_source_verification_ca... | 2024-12-24T08:23:40Z |
## Description
<!-- Describe your changes in detail -->
disable partial auth feature for relay
## 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... | 912091976859628ac9fbfe86475814bf8cca3edf | [
"config/deployments/integration_test.toml",
"config/deployments/production.toml",
"config/deployments/sandbox.toml",
"crates/router/src/routes/relay.rs"
] | ||
juspay/hyperswitch | juspay__hyperswitch-6919 | Bug: add retrieve api support for relay
/relay is a api that will be used to just forward the request sent by merchant without performing any application logic on it. This is particular to support the refunds for the payments that was directly performed with the connector (example stripe) with out hyperswitch involv... | diff --git a/crates/api_models/src/relay.rs b/crates/api_models/src/relay.rs
index e4bc607fc0d..f54e1471632 100644
--- a/crates/api_models/src/relay.rs
+++ b/crates/api_models/src/relay.rs
@@ -84,9 +84,20 @@ pub struct RelayRetrieveRequest {
#[serde(default)]
pub force_sync: bool,
/// The unique identifi... | 2024-12-23T09:40:12Z |
## Description
<!-- Describe your changes in detail -->
/relay is a api that will be used to just forward the request sent by merchant without performing any application logic on it. This is particular to support the refunds for the payments that was directly performed with the connector (example stripe) with out hy... | 1fc941056fb8759435f41bba004a602c176eb802 |
-> Create a merchant connector account
-> Make a refund request with invalid connector_resource_id
```
curl --location 'http://localhost:8080/relay' \
--header 'Content-Type: application/json' \
--header 'X-Profile-Id: pro_rIikb0gPrzd0vEY8hIiP' \
--header 'api-key: dev_qqMQAuMWCclJSk4uMBeNNSpqAPlsKlBA3blQOwOoq5... | [
"crates/api_models/src/relay.rs",
"crates/diesel_models/src/query/relay.rs",
"crates/diesel_models/src/relay.rs",
"crates/router/src/core/relay.rs",
"crates/router/src/db/relay.rs",
"crates/router/src/routes/app.rs",
"crates/router/src/routes/lock_utils.rs",
"crates/router/src/routes/relay.rs",
"cra... | |
juspay/hyperswitch | juspay__hyperswitch-6916 | Bug: fix(payments_list): handle same payment/attempt IDs for different merchants
The query planner was applying the merchant_id filter before the join operation, which caused incorrect results when different merchants had the same payment_id or attempt_id. This prematurely filtered out valid rows from the payment_at... | diff --git a/crates/storage_impl/src/payments/payment_intent.rs b/crates/storage_impl/src/payments/payment_intent.rs
index fe64136b743..786cbe75a43 100644
--- a/crates/storage_impl/src/payments/payment_intent.rs
+++ b/crates/storage_impl/src/payments/payment_intent.rs
@@ -831,10 +831,11 @@ impl<T: DatabaseStore> Paymen... | 2024-12-23T09:39:07Z |
## Description
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.
## Motivation and Context
Closes [#6916](https://github.com/juspay/hyp... | a423ff53d3523508ba6c584134e32f3f1bb4f0c0 | Tried to have to merchant id that have same payment/atttempt id. And tested for the logic:
<img width="1078" alt="Screenshot 2024-12-23 at 7 31 50 PM" src="https://github.com/user-attachments/assets/0cc062fd-e10a-45f2-adbb-549dc9eb34c1" />
<img width="1056" alt="Screenshot 2024-12-23 at 4 32 48 PM" src="https://githu... | [
"crates/storage_impl/src/payments/payment_intent.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-6914 | Bug: [feat] show error code and message in cypress reports
show error code and message in cypress reports.
this is helpful to debug failures in ci | 2024-12-21T07:48:52Z |
## Description
<!-- Describe your changes in detail -->
This PR introduces error code and error message validations.
This nullifies the need to re-run the ci check manually in local every the check just to see the reason for the failure.
With that, `error_code` and `error_message` will now be printed in the ui... | d4b3dbc155906e8bc0fa1b14e73f45227395a32f |
when a ci check fail, especially from the connectors' end, ci takes a screenshot of the ui, as usual, but that will now contain the error code and message.
since adyen yet again got into some issues with save card flow, it is possible to test my changes directly without the need to make any modifications to the ... | [] | ||
juspay/hyperswitch | juspay__hyperswitch-6585 | Bug: [REFACTOR] Move cybersource, bankofamerica, wellsfargo to crate hyperswitch_connectors
### Feature Description
Move cybersource, bankofamerica, wellsfargo code to crate hyperswitch_connectors.
### Possible Implementation
Move cybersource, bankofamerica, wellsfargo code to crate hyperswitch_connectors.
### H... | diff --git a/Cargo.lock b/Cargo.lock
index 2007f4f88a0..7583fb2eeee 100644
--- a/Cargo.lock
+++ b/Cargo.lock
@@ -4003,6 +4003,7 @@ dependencies = [
"hyperswitch_domain_models",
"hyperswitch_interfaces",
"image",
+ "josekit",
"lazy_static",
"masking",
"mime",
diff --git a/crates/hyperswitch_connectors/Cargo.... | 2024-12-20T10:56:16Z |
## Description
<!-- Describe your changes in detail -->
Move cybersource, bankofamerica, wellsfargo code to crate hyperswitch_connectors.
## Motivation and Context
https://github.com/juspay/hyperswitch/issues/6585
<!--
Why is this change required? What problem does it solve?
If it fixes an open issue, pl... | 9c1ebd219fcaeefb6bd06c21c2358bf19a332891 | Moved the connector tot he hyperswitch crate (No logical Changes)
| [
"Cargo.lock",
"crates/hyperswitch_connectors/Cargo.toml",
"crates/hyperswitch_connectors/src/connectors.rs",
"crates/router/src/connector/bankofamerica.rs",
"crates/router/src/connector/bankofamerica/transformers.rs",
"crates/router/src/connector/cybersource.rs",
"crates/router/src/connector/cybersource... | |
juspay/hyperswitch | juspay__hyperswitch-7067 | Bug: [BUG] previous rules are being considered for surcharge calculation even after updating surcharge rules in database
### Bug Description
When I updated surcharge rules using the `PUT /routing/decision/surcharge` endpoint, the surcharge rules are being updated in DB but when I do merchant payment method list(PML... | diff --git a/crates/router/src/core/surcharge_decision_config.rs b/crates/router/src/core/surcharge_decision_config.rs
index 0ff5f3fb373..2d817fd1afe 100644
--- a/crates/router/src/core/surcharge_decision_config.rs
+++ b/crates/router/src/core/surcharge_decision_config.rs
@@ -56,7 +56,7 @@ pub async fn upsert_surcharge... | 2024-12-20T09:07:57Z |
## Description
<!-- Describe your changes in detail -->
When surcharge rules where updated or deleted, the in memory cache was being invalidated using the wrong key. Fixed that issue in this PR.
## Motivation and Context
<!--
Why is this change required? What problem does it solve?
If it fixes an open issue... | 3fdc41e6c946609461db6b5459e10e6351694d4c |
1. upsert surcharge rules. If amount >500 and <1000 add a surcharge of 40%.
```
curl --location --request PUT 'http://localhost:8080/routing/decision/surcharge' \
--header 'Content-Type: application/json' \
--header 'api-key: dev_bLGFEtyJtHdvJqXtbnwOcnxpBuNk9lcGIHewiAgCcQQKXYdyoHw8SyAz5JcfikMl' \
--data '{
... | [
"crates/router/src/core/surcharge_decision_config.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-6986 | Bug: refactor(currency_conversion): re-frame the crate to make api calls on background thread
| diff --git a/config/config.example.toml b/config/config.example.toml
index c860420da38..ecc2d2127ce 100644
--- a/config/config.example.toml
+++ b/config/config.example.toml
@@ -74,13 +74,10 @@ max_feed_count = 200 # The maximum number of frames that will be fe
# This section provides configs for currenc... | 2024-12-20T06:29:50Z |
## Description
<!-- Describe your changes in detail -->
Due to redis lock being held for a long time, which made the forex api-calls synchronous, we had to re-frame the way how things were being operated for forex rates fetch, The changes includes:
1. Acquiring redis lock, just before api-call and releasing it once... | 3fdc41e6c946609461db6b5459e10e6351694d4c |
1. Testing for first call when there is no data present in cache as well as redis:

```
curl --location 'http://127.0.0.1:8080/forex/rates' \
--header 'api-key: xxxxxxx' \
--data ''
```
<img w... | [
"config/config.example.toml",
"config/deployments/env_specific.toml",
"config/development.toml",
"config/docker_compose.toml",
"crates/analytics/docs/README.md",
"crates/router/src/configs/settings.rs",
"crates/router/src/core/currency.rs",
"crates/router/src/utils/currency.rs",
"loadtest/config/dev... | |
juspay/hyperswitch | juspay__hyperswitch-6925 | Bug: [FEATURE] Add support for retries with clear pan and network token payment method data
Add support for payment retries with clear pan and network token payment method data and also reduced calls to locker when data is already fetch once. | diff --git a/api-reference-v2/openapi_spec.json b/api-reference-v2/openapi_spec.json
index 2e0d57d977e..cd8b8458364 100644
--- a/api-reference-v2/openapi_spec.json
+++ b/api-reference-v2/openapi_spec.json
@@ -10615,7 +10615,8 @@
"message",
"status",
"decision",
- "step_up_possi... | 2024-12-19T21:16:38Z |
## Description
<!-- Describe your changes in detail -->
Add support to retry a transaction with clear PAN or Network Token
- added support for clear pan retry with same connector when previous attempt failed with payment method data - network token.
- refactored `make_pm_data` which does fetch payment method data ... | b71571d16ca4553e1c7eca17f00df24945479638 |
test cases -
1 - enable network tokenization, auto retries for profile
2 - make a setup future usage= on_session payment.
3 - make saved card payment (with payment token) (payment will happen with network token + cryptogram) with adyen, if it fails, a retry will happen with card data fetched from locker with same... | [
"api-reference-v2/openapi_spec.json",
"crates/api_models/src/admin.rs",
"crates/api_models/src/gsm.rs",
"crates/diesel_models/src/business_profile.rs",
"crates/diesel_models/src/gsm.rs",
"crates/diesel_models/src/schema.rs",
"crates/diesel_models/src/schema_v2.rs",
"crates/hyperswitch_domain_models/sr... | |
juspay/hyperswitch | juspay__hyperswitch-6902 | Bug: [REFACTOR] send `tenant-id` and `request-id` in grpc headers
| diff --git a/crates/common_utils/src/consts.rs b/crates/common_utils/src/consts.rs
index 39e5483700a..3b437b703be 100644
--- a/crates/common_utils/src/consts.rs
+++ b/crates/common_utils/src/consts.rs
@@ -146,3 +146,6 @@ pub const CONNECTOR_TRANSACTION_ID_HASH_BYTES: usize = 25;
/// Apple Pay validation url
pub const... | 2024-12-19T16:09:44Z |
## Description
<!-- Describe your changes in detail -->
This PR adds support for sending the `x-tenant-id` and `x-request-id` in the grpc headers
## 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 ha... | dcd51a7fb8df673cc74130ee732542b55783602f |
1. Create merchant_account, api_key and mca (any connector)
2. Toggle dynamic routing
```
curl --location --request POST 'http://localhost:8080/account/merchant_1734609410/business_profile/pro_gPTjn9jLm0CxI8ZD1omL/dynamic_routing/success_based/toggle?enable=metrics' \
--header 'Content-Type: application/json' \... | [
"crates/common_utils/src/consts.rs",
"crates/external_services/src/grpc_client.rs",
"crates/external_services/src/grpc_client/dynamic_routing/elimination_rate_client.rs",
"crates/external_services/src/grpc_client/dynamic_routing/success_rate_client.rs",
"crates/router/src/core/payments/routing.rs",
"crate... | |
juspay/hyperswitch | juspay__hyperswitch-6901 | Bug: refactor(dynamic_routing): perform db operations only when payments are in terminal state
| diff --git a/crates/common_enums/src/enums.rs b/crates/common_enums/src/enums.rs
index 193998c3fd1..c3faa5c6f93 100644
--- a/crates/common_enums/src/enums.rs
+++ b/crates/common_enums/src/enums.rs
@@ -1304,6 +1304,20 @@ pub enum IntentStatus {
}
impl IntentStatus {
+ /// Indicates whether the payment intent is i... | 2024-12-19T14:48:25Z |
## Description
<!-- Describe your changes in detail -->
Previously due to the DB insertion code being in `post_update_tracker` was being called several times as our payment's status keeps on changing, due to this our DB broke as we had a unique constraint on `attempt_id` in the `dynamic_routing_stats` table.
To fix... | 04787313941ec39b179490d0196258f09e2e51dd |
1. Toggle Success Based routing for the merchant.
```
curl --location --request POST 'http://localhost:8080/account/xxxxxx/business_profile/xxxxxxx/dynamic_routing/success_based/toggle?enable=metrics' \
--header 'api-key: xxxxxxx'
```
2. Create a payment that goes in processing state or any non terminal state. (... | [
"crates/common_enums/src/enums.rs",
"crates/router/src/core/payments/operations/payment_response.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-6893 | Bug: [bug] reports are being generated in cypress upon failures
that is because recently, i moved cypress.config.js from being a commonjs module to esmodule and this resulted in inconsistencies which went unaddressed or unnotified.
| 2024-12-19T10:16:04Z |
## Description
<!-- Describe your changes in detail -->
closes https://github.com/juspay/hyperswitch/issues/6893
this pr also bumps cypress dependencies
## 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 ... | c525c9f4c9d23802989bc594a4acd26c7d7cd27d |
the changes in this pr has been cherry picked from #6735. reports for failed tests were generated there.
an example of reports being generated: https://github.com/juspay/hyperswitch/actions/runs/12409713710?pr=6735
| [] | ||
juspay/hyperswitch | juspay__hyperswitch-6889 | Bug: [FEATURE] Implement Payment Method Samsung Pay for Connector BankOfAmerica
### Feature Description
Implement Payment Method Samsung Pay for Connector BankOfAmerica.
### Possible Implementation
Samsung Pay should be implemented for BankOfAmerica
### Have you spent some time checking if this feature request h... | diff --git a/crates/hyperswitch_connectors/src/connectors/bankofamerica/transformers.rs b/crates/hyperswitch_connectors/src/connectors/bankofamerica/transformers.rs
index 4b40e36a7a6..7690b6ed3d0 100644
--- a/crates/hyperswitch_connectors/src/connectors/bankofamerica/transformers.rs
+++ b/crates/hyperswitch_connectors/... | 2024-12-19T08:24:33Z |
## Description
<!-- Describe your changes in detail -->
Implemented Payment Method Samsung Pay for connector Bankofamerica
## 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 rec... | 10371af561ecc7536bb1db191af90a3cac2ab515 |
1. Connector configuration with merhcant account
```
curl --location 'http://localhost:8080/account/merchant_1734596148/connectors' \
--header 'Content-Type: application/json' \
--header 'Accept: application/json' \
--header 'api-key: test_admin' \
--data '{
"connector_type": "payment_processor",
"con... | [
"crates/hyperswitch_connectors/src/connectors/bankofamerica/transformers.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-6886 | Bug: [BUG] fix cypress test cases for adyenplatform
### Bug Description
Cypress test cases for adyenplatform (Payout specific test cases) are failing.
### Expected Behavior
They should be successfully executed.
### Actual Behavior
They're failing while doing a status check in the expected response and... | 2024-12-19T07:03:39Z |
## Description
This PR fixes the cypress payout test cases for AdyenPlatform connector.
## Motivation and Context
Helps in enabling the Adyenplatform connector for payout cypress test cases as a part of Github CI checks.
# | 4bc88a71903bbb06cc757569b4c20d2d63f9d245 | Locally.
<img width="845" alt="Screenshot 2024-12-19 at 12 33 27 PM" src="https://github.com/user-attachments/assets/e9cd904d-c9a7-4b1e-93e9-5c78ae705a4e" />
| [] | ||
juspay/hyperswitch | juspay__hyperswitch-1593 | Bug: feat(CI/CD):Implement Code Cov for CI checks
Tracked in #1587
Implement Code coverage for PR's via CI
Objectives
- run tests as part of CI
- generate codeCov for these tests & auto-publish the report as part of PR Comment...
- [Optionally] be able to specify that atleast x% of new code should be test-co... | diff --git a/.gitignore b/.gitignore
index dcbeddf7ada..d53145b33ee 100644
--- a/.gitignore
+++ b/.gitignore
@@ -241,6 +241,7 @@ $RECYCLE.BIN/
# hyperswitch Project specific excludes
# code coverage report
*.profraw
+lcov.info
html/
coverage.json
# other
diff --git a/README.md b/README.md
index c09176b172a..5b551... | 2024-12-19T06:36:46Z |
## Description
<!-- Describe your changes in detail -->
Added a CI pipeline that will run cypress tests and generate code coverage reports for v2
## 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 ha... | 90c932a6d798453f7e828c55a7668c5c64c933a5 |
Manually confirmed the pipeline works.
This PR contains only CI testing related changes. There is no need of adding test cases.
| [
".gitignore",
"README.md",
"cypress-tests-v2/package-lock.json",
"justfile",
"scripts/execute_cypress.sh"
] | |
juspay/hyperswitch | juspay__hyperswitch-1587 | Bug: [FEATURE]: setup code coverage for local tests & CI
#### Context
As any other codebase, unit tests are vital to maintain stability & correctness of code..
Currently while the project has some amount of tests, We still don't have a code coverage tracking in place which robs people of some of the incentives f... | diff --git a/.gitignore b/.gitignore
index dcbeddf7ada..d53145b33ee 100644
--- a/.gitignore
+++ b/.gitignore
@@ -241,6 +241,7 @@ $RECYCLE.BIN/
# hyperswitch Project specific excludes
# code coverage report
*.profraw
+lcov.info
html/
coverage.json
# other
diff --git a/README.md b/README.md
index c09176b172a..5b551... | 2024-12-19T06:36:46Z |
## Description
<!-- Describe your changes in detail -->
Added a CI pipeline that will run cypress tests and generate code coverage reports for v2
## 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 ha... | 90c932a6d798453f7e828c55a7668c5c64c933a5 |
Manually confirmed the pipeline works.
This PR contains only CI testing related changes. There is no need of adding test cases.
| [
".gitignore",
"README.md",
"cypress-tests-v2/package-lock.json",
"justfile",
"scripts/execute_cypress.sh"
] | |
juspay/hyperswitch | juspay__hyperswitch-6883 | Bug: feat(core): setup platform merchant account
- Setup platform merchant account.
Platform merchant account is a special type of merchant account which can do operations on behalf of other merchant account present in the same organisation.
- Add APIs to create a platform merchant account / convert a merchant accou... | diff --git a/config/deployments/integration_test.toml b/config/deployments/integration_test.toml
index 7fdc0c6d5e8..65ce1fdbc0a 100644
--- a/config/deployments/integration_test.toml
+++ b/config/deployments/integration_test.toml
@@ -428,3 +428,6 @@ card_networks = "Visa, AmericanExpress, Mastercard"
[network_tokeniz... | 2024-12-18T18:20:15Z |
## Description
#### About the feature
- This the first PR for the Platform Account feature.
- Feature is under development and behind the feature flag.
- Feature is supposed to be disabled for sandbox and production environments.
#### Enabling the platform account.
- New API has been created to enable platform ... | 1fc941056fb8759435f41bba004a602c176eb802 | 1. Create a merchant account(m1).
2. Use below api to convert it into platform account.
```sh
curl --location --request POST '<BASE URL>/accounts/{merchant_id}/platform' \
--header 'api-key:<ADMIN API KEY>'
```
3. Create another merchant account in the same organisation(m2).
4. Do a payment using platform's(m1) ... | [
"config/deployments/integration_test.toml",
"config/deployments/production.toml",
"config/deployments/sandbox.toml",
"config/development.toml",
"config/docker_compose.toml",
"crates/diesel_models/src/merchant_account.rs",
"crates/diesel_models/src/payment_intent.rs",
"crates/diesel_models/src/schema.r... | |
juspay/hyperswitch | juspay__hyperswitch-6958 | Bug: refactor(dynamic_routing): add non_deterministic value in SuccessBasedRoutingConclusiveState type
## Description
<!-- Describe your changes in detail -->
This will add a value `non_deterministic` in `SuccessBasedRoutingConclusiveState` type. | diff --git a/migrations/2024-12-18-124527_add_new_value_in_success_based_routing_conclusive_state/down.sql b/migrations/2024-12-18-124527_add_new_value_in_success_based_routing_conclusive_state/down.sql
new file mode 100644
index 00000000000..2a3866c86d4
--- /dev/null
+++ b/migrations/2024-12-18-124527_add_new_value_in... | 2024-12-18T13:01:15Z |
## Description
<!-- Describe your changes in detail -->
This will add a value `non_deterministic` in `SuccessBasedRoutingConclusiveState` type.
## 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... | db51ec43bc629dc20ceaa2bb57ede888d2d2fc2c |
1. Toggle Success Based routing for the merchant.
```
curl --location --request POST 'http://localhost:8080/account/xxxxxx/business_profile/xxxxxxx/dynamic_routing/success_based/toggle?enable=metrics' \
--header 'api-key: xxxxxxx'
```
2. Create a payment that goes in processing state or any non terminal state.... | [
"migrations/2024-12-18-124527_add_new_value_in_success_based_routing_conclusive_state/down.sql",
"migrations/2024-12-18-124527_add_new_value_in_success_based_routing_conclusive_state/up.sql"
] | |
juspay/hyperswitch | juspay__hyperswitch-6872 | Bug: [FEATURE] [Network Tokenization]: Tokenize before payment
### Feature Description
Tokenize the card before payment based on profile level config.
### Possible Implementation
Tokenize the card before payment based on profile level config.
### Have you spent some time checking if this feature request has been... | diff --git a/crates/api_models/src/admin.rs b/crates/api_models/src/admin.rs
index a7b57b7433c..60eca62b618 100644
--- a/crates/api_models/src/admin.rs
+++ b/crates/api_models/src/admin.rs
@@ -2002,6 +2002,9 @@ pub struct ProfileCreate {
/// Indicates if the redirection has to open in the iframe
pub is_ifra... | 2024-12-18T06:19:09Z |
## Description
<!-- 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.
... | 1192bd5247dc099f647963a90ccc85a356b9f742 |
1. Enable is_network_tokenization_enabled and is_pre_network_tokenization_enabled in business_profile
2. Create a card payment with a network tokenization supported connector. (Customer acceptance should be there)
Connector Create(Cybersource):
```
curl --location 'http://localhost:8080/account/merchant_1747299... | [
"crates/api_models/src/admin.rs",
"crates/diesel_models/src/business_profile.rs",
"crates/diesel_models/src/schema.rs",
"crates/hyperswitch_domain_models/src/business_profile.rs",
"crates/hyperswitch_domain_models/src/payment_method_data.rs",
"crates/hyperswitch_domain_models/src/payments.rs",
"crates/r... | |
juspay/hyperswitch | juspay__hyperswitch-6898 | Bug: add api model changes for /relay endpoint
/relay is a api that will be used to just forward the request sent by merchant without performing any application logic on it. In this pr the changes is particular to support the refunds for the payments that was directly performed with the connector (example stripe) wi... | diff --git a/crates/api_models/src/lib.rs b/crates/api_models/src/lib.rs
index a28332e7fea..2d1e87ebf01 100644
--- a/crates/api_models/src/lib.rs
+++ b/crates/api_models/src/lib.rs
@@ -31,6 +31,7 @@ pub mod poll;
#[cfg(feature = "recon")]
pub mod recon;
pub mod refunds;
+pub mod relay;
pub mod routing;
pub mod sur... | 2024-12-18T06:00:50Z |
## Description
<!-- Describe your changes in detail -->
/relay is a api that will be used to just forward the request sent my merchant without performing any application logic on it. In this pr the changes is particular to support the refunds for the payments that was directly performed with the connector (example s... | dcd51a7fb8df673cc74130ee732542b55783602f |
<img width="1675" alt="image" src="https://github.com/user-attachments/assets/246da847-274c-4d1e-b441-07326e4a6d00" />
<img width="1721" alt="image" src="https://github.com/user-attachments/assets/0cb733ee-562d-4994-b57c-289296fff720" />
| [
"crates/api_models/src/lib.rs",
"crates/api_models/src/relay.rs",
"crates/common_utils/src/id_type.rs",
"crates/common_utils/src/id_type/relay.rs",
"crates/openapi/src/openapi.rs",
"crates/openapi/src/routes.rs",
"crates/openapi/src/routes/relay.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-6892 | Bug: feat(email): Local SMTP server
Add mailhog by default in docker-compose for local smtp server. | diff --git a/config/docker_compose.toml b/config/docker_compose.toml
index cfdf4b0e0c2..4296a5931dc 100644
--- a/config/docker_compose.toml
+++ b/config/docker_compose.toml
@@ -55,9 +55,9 @@ master_enc_key = "73ad7bbbbc640c845a150f67d058b279849370cd2c1f3c67c4dd6c869213e1
password_validity_in_days = 90
two_factor_auth... | 2024-12-18T04:38:10Z |
## Description
<!-- Describe your changes in detail -->
Add support to run local email server in docker-compose. User can see the email we send even in local setup
## 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.
... | e35f7079e3fc9ada76d0602739053bdd5d595008 | [
"config/docker_compose.toml",
"docker-compose.yml"
] | ||
juspay/hyperswitch | juspay__hyperswitch-6861 | Bug: refactor(users): move roles schema to global storeage interface
- We need to have roles schema in global schema. It should be global along with user, user_roles and user_key_store
- We need to remove themes from global schema, since themes are not global and can depend on tenant, organization, merchant or profi... | diff --git a/crates/router/src/core/user/theme.rs b/crates/router/src/core/user/theme.rs
index 27b342d9053..2a896b7158f 100644
--- a/crates/router/src/core/user/theme.rs
+++ b/crates/router/src/core/user/theme.rs
@@ -21,7 +21,7 @@ pub async fn get_theme_using_lineage(
lineage: ThemeLineage,
) -> UserResponse<them... | 2024-12-17T12:04:20Z |
## Description
Refactor:
- move roles to global schema
- remove themes from global schema
## Motivation and Context
Closes [#6861](https://github.com/juspay/hyperswitch/issues/6861)
# | e8bfd0e2270300fff3f051143f34ebb782da5366 | Refactoring changes, currently in config global schema points to public, so no change in behaviour.
Changes will be reflected after we turn on feature flag for multi-tenancy and update the configs. Global interface will point to global (shared resources) schema.
When interacting with roles and themes storeage fucnt... | [
"crates/router/src/core/user/theme.rs",
"crates/router/src/core/user_role/role.rs",
"crates/router/src/db.rs",
"crates/router/src/services/authorization.rs",
"crates/router/src/services/authorization/roles.rs",
"crates/router/src/utils/user/theme.rs",
"crates/router/src/utils/user_role.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-6854 | Bug: refactor(dynamic_routing): add col payment_method_type in dynamic_routing_stats
| diff --git a/crates/diesel_models/src/dynamic_routing_stats.rs b/crates/diesel_models/src/dynamic_routing_stats.rs
index 168699d7f56..c055359d8b0 100644
--- a/crates/diesel_models/src/dynamic_routing_stats.rs
+++ b/crates/diesel_models/src/dynamic_routing_stats.rs
@@ -19,6 +19,7 @@ pub struct DynamicRoutingStatsNew {
... | 2024-12-16T12:13:56Z |
## Description
<!-- Describe your changes in detail -->
This change will add `payment_method_type` in dynamic_routing_stats.
## 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 rec... | ae00a103de5bd283695969270a421c7609a699e8 |
Testing can be done in following way:
1. Enable Success based routing for a profile with feature as metrics.
2. Make a payment.
3. Search the `dynamic_routing_stats` table for the new col. `payment_method_type` for that payment.
<img width="441" alt="Screenshot 2024-12-16 at 5 38 33 PM" src="https://github.co... | [
"crates/diesel_models/src/dynamic_routing_stats.rs",
"crates/diesel_models/src/schema.rs",
"crates/diesel_models/src/schema_v2.rs",
"crates/router/src/core/routing/helpers.rs",
"migrations/2024-12-16-111228_add_new_col_payment_method_type_in_dynamic_routing_stats/down.sql",
"migrations/2024-12-16-111228_a... | |
juspay/hyperswitch | juspay__hyperswitch-6850 | Bug: [bug] adyen mit transactions in ntid flow fail due mis matched expiry conversion
```txt
"The provided Expiry Date is not valid.: Expiry year should be a 4 digit number greater than 2000: 30"
```
above error is being thrown during ntid transaction resulting in payment to fail:
<img width="441" alt="image... | diff --git a/crates/router/src/connector/adyen/transformers.rs b/crates/router/src/connector/adyen/transformers.rs
index 16cab2fda47..3e84dffcfaf 100644
--- a/crates/router/src/connector/adyen/transformers.rs
+++ b/crates/router/src/connector/adyen/transformers.rs
@@ -2650,7 +2650,7 @@ impl
... | 2024-12-16T11:55:03Z |
## Description
<!-- Describe your changes in detail -->
This PR fixes MIT payments failing especially during NTID flow.
We previously used to get below error message during MIT Confirm call:
```log
"The provided Expiry Date is not valid.: Expiry year should be a 4 digit number greater than 2000: 30"
```
c... | 986de77b4868e48d00161c9d30071d809360e9a6 |
xecuted below commands:
```sh
| [
"crates/router/src/connector/adyen/transformers.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-6951 | Bug: refactor(payment_methods): update connector_mandate_details for card metadata changes
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 | diff --git a/crates/router/src/core/payments/operations/payment_response.rs b/crates/router/src/core/payments/operations/payment_response.rs
index 01a4e086091..e7101742676 100644
--- a/crates/router/src/core/payments/operations/payment_response.rs
+++ b/crates/router/src/core/payments/operations/payment_response.rs
@@ ... | 2024-12-16T10:09:23Z |
## Description
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
## Motivation and Context
<!--
Why is this change required? What problem does it so... | ed276ecc0017f7f98b6f8fa3841e6b8971f609f1 | - Nothreeds
> - Create a MA and a MCA
> - Make a off_Session save card payment
> - Make a off_Session payment again with the same card just and changes expiry
> - After a successful payment the Connector Mandate Details would be overriden
<img width="1725" alt="Screenshot 2024-12-16 at 4 21 51 PM" src="https://... | [
"crates/router/src/core/payments/operations/payment_response.rs",
"crates/router/src/core/payments/tokenization.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-6840 | Bug: [FEATURE] [Deutschebank] : Implement 3ds Card Flow
### Feature Description
Implement 3ds Card Flow for Deutschebank
### Possible Implementation
Implement 3ds Card Flow for Deutschebank
### Have you spent some time checking if this feature request has been raised before?
- [X] I checked and didn't find a si... | diff --git a/crates/diesel_models/src/payment_attempt.rs b/crates/diesel_models/src/payment_attempt.rs
index 03facc2ebab..a450a30fa76 100644
--- a/crates/diesel_models/src/payment_attempt.rs
+++ b/crates/diesel_models/src/payment_attempt.rs
@@ -3426,6 +3426,10 @@ pub enum RedirectForm {
access_token: String,
... | 2024-12-16T08:25:48Z |
## Description
<!-- Describe your changes in detail -->
Implement Card 3ds for Deutschebank
## 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... | 3eb2eb1cf5b9855432b49994b433e6f7fa404212 |
**Cypress Tests**
**1. No3DSManualCapture**

**2. 3DSAutoCapture**

**3. 3DSManualCapture**
 integration
Klarna provides two payment methods:
1. Klarna Payments (for US)
2. Klarna Kustom Checkout (for EU)
Any one of the methods can be used at a time and switching between Klarna Payments and Klarna Checkout is been done. Based on the PML got, there will be a... | 886e2aacd7dcd8a04a33884ceafb1562aa7c365f | I tested it using postman by hitting the required endpoints. Curl to the postman setup:
1. Configure Klarna Checkout for merchant account
```
curl --location 'http://localhost:8080/account/merchant_1734083062/connectors' \
--header 'Content-Type: application/json' \
--header 'Accept: application/json' \
--heade... | [
"api-reference-v2/openapi_spec.json",
"crates/api_models/src/payments.rs",
"crates/diesel_models/src/types.rs",
"crates/hyperswitch_connectors/src/connectors/multisafepay/transformers.rs",
"crates/hyperswitch_connectors/src/connectors/square/transformers.rs",
"crates/hyperswitch_connectors/src/connectors/... | |
juspay/hyperswitch | juspay__hyperswitch-6835 | Bug: feat(redis-interface): add redis interface command to set multiple the keys in redis and increment if the key already exists
add redis interface command to set multiple the keys in redis and increment if the key already exists | diff --git a/crates/redis_interface/src/commands.rs b/crates/redis_interface/src/commands.rs
index 746b424abc8..19497d6fbb8 100644
--- a/crates/redis_interface/src/commands.rs
+++ b/crates/redis_interface/src/commands.rs
@@ -14,7 +14,7 @@ use common_utils::{
use error_stack::{report, ResultExt};
use fred::{
inte... | 2024-12-12T11:51:49Z |
## Description
add redis interface command to set multiple the keys in redis and increment if the key already exists
## 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 ... | 573fc2ce0ff306d15ec97e7c8d5b8a03528165f4 | - Wrote a unit test to insert the keys
<img width="1725" alt="Screenshot 2024-12-13 at 1 05 33 PM" src="https://github.com/user-attachments/assets/5165c747-6e53-4db2-9dce-6aa338c33517" />
| [
"crates/redis_interface/src/commands.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-6563 | Bug: Integration of ER in core flow
| diff --git a/config/development.toml b/config/development.toml
index 3a041db3574..c83713e2a07 100644
--- a/config/development.toml
+++ b/config/development.toml
@@ -991,7 +991,7 @@ connector_list = "cybersource"
[grpc_client.dynamic_routing_client]
host = "localhost"
-port = 7000
+port = 8000
service = "dynamo"
... | 2024-12-12T04:52:49Z |
## Description
<!-- 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.
# | 2a4670537a5c0e40e70d2afec0a2ba6124f03927 |
Testing performed in same way as SR routing.
1. Enable ER for merchant
```
curl --location --request POST 'http://localhost:8080/account/merchant_1744368166/business_profile/pro_GrzjTHd5Pn5hAhwTZPRn/dynamic_routing/elimination/toggle?enable=dynamic_connector_selection' \
--header 'api-key: dev_a4XMpNXd3Yriz5DPsiw... | [
"config/development.toml",
"crates/api_models/src/routing.rs",
"crates/common_enums/src/enums.rs",
"crates/router/src/core/errors.rs",
"crates/router/src/core/payments/operations/payment_response.rs",
"crates/router/src/core/payments/routing.rs",
"crates/router/src/core/routing/helpers.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-6814 | Bug: [FEATURE] Ephemeral Auth for v2
### Feature Description
We need to support ephemeral auth in v2.
This would replace the current client secret auth being used in Payment methods
### Possible Implementation
Need to add implementation for ephemeral auth
### Have you spent some time checking if this feature r... | diff --git a/api-reference-v2/openapi_spec.json b/api-reference-v2/openapi_spec.json
index 58a81caeed3..7a9448a4fd4 100644
--- a/api-reference-v2/openapi_spec.json
+++ b/api-reference-v2/openapi_spec.json
@@ -13696,16 +13696,11 @@
"PaymentMethodIntentConfirm": {
"type": "object",
"required": [
... | 2024-12-11T18:52:11Z |
## Description
<!-- 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
## Motivation and Context
<!--
Why is this change ... | e8bfd0e2270300fff3f051143f34ebb782da5366 |
1. Create Payment Method Intent
```
curl --location --request POST 'http://localhost:8080/v2/payment-methods/create-intent' \
--header 'Content-Type: application/json' \
--header 'Accept: application/json' \
--header 'X-Profile-Id: pro_DMmRBLpkNczeVDPd2EKd' \
--header 'api-key: dev_HVwdf7yWqJ9GGfw1CLDbAgjOFYHr... | [
"api-reference-v2/openapi_spec.json",
"crates/api_models/src/ephemeral_key.rs",
"crates/api_models/src/payment_methods.rs",
"crates/common_utils/src/events.rs",
"crates/common_utils/src/id_type.rs",
"crates/common_utils/src/id_type/ephemeral_key.rs",
"crates/diesel_models/src/ephemeral_key.rs",
"crate... | |
juspay/hyperswitch | juspay__hyperswitch-6787 | Bug: refactor(constraint_graph): add cypress test cases for 'mandate_details'
| diff --git a/crates/router/src/core/payment_methods/cards.rs b/crates/router/src/core/payment_methods/cards.rs
index 13575961108..0ca77f3a5ee 100644
--- a/crates/router/src/core/payment_methods/cards.rs
+++ b/crates/router/src/core/payment_methods/cards.rs
@@ -4589,7 +4589,7 @@ pub async fn filter_payment_methods(
... | 2024-12-11T12:50:44Z |
## Description
<!-- Describe your changes in detail -->
This will handel the cases for constraint_graph for PML where setup_future_usage is not passed in payments.
## 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.
... | 9466ced89407f31963bb0eb7c762749e3713591a |
This can be tested in the following way:
1. Connector create (Fiuu)
```
curl --location 'http://127.0.0.1:8080/account/merchant_1733312955/connectors' \
--header 'Content-Type: application/json' \
--header 'Accept: application/json' \
--header 'api-key: test_admin' \
--data '{
"connector_type": "payment_p... | [
"crates/router/src/core/payment_methods/cards.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-6808 | Bug: feat(users): handle email URLs for users in different tenancies
We will be sending emails to users in different tenancies, on clicking the email they should land on that particular tenant URL.
For that we need tenant level user configs. And 'll be using it to generate emails.
| diff --git a/config/config.example.toml b/config/config.example.toml
index 0fe6b8caa2c..8d7c926c3e2 100644
--- a/config/config.example.toml
+++ b/config/config.example.toml
@@ -758,8 +758,15 @@ sdk_eligible_payment_methods = "card"
enabled = false
global_tenant = { schema = "public", redis_key_prefix = "", clickhouse... | 2024-12-11T12:20:07Z |
## Description
- Add support for user in tenants configs.
- Handle email URLs for different tenancies
## Motivation and Context
Closes [#6808](https://github.com/juspay/hyperswitch/issues/6808)
# | ed276ecc0017f7f98b6f8fa3841e6b8971f609f1 | Tested locally with email feature flag on, for different tenancies the emails we were getting, we were landing onto to the URL specified in the tenant's config.
We specified the following in the local configs.
```
[multitenancy]
enabled = true
global_tenant = { schema = "public", redis_key_prefix = "", clickhouse_... | [
"config/config.example.toml",
"config/deployments/env_specific.toml",
"config/development.toml",
"config/docker_compose.toml",
"crates/external_services/src/email.rs",
"crates/router/src/configs/settings.rs",
"crates/router/src/core/recon.rs",
"crates/router/src/core/user.rs",
"crates/router/src/cor... | |
juspay/hyperswitch | juspay__hyperswitch-6807 | Bug: [FEATURE] [AIRWALLEX] Add refferer data to whitelist hyperswitch
### Feature Description
Referrer data needs to be added in Airwallex's Create Payment Intent request in order to whitelist Hyperswitch for processing raw card details.
### Possible Implementation
Referrer data needs to be added in Airwallex's C... | diff --git a/crates/hyperswitch_connectors/src/connectors/airwallex/transformers.rs b/crates/hyperswitch_connectors/src/connectors/airwallex/transformers.rs
index 97c9ed4d36a..e8ab479c978 100644
--- a/crates/hyperswitch_connectors/src/connectors/airwallex/transformers.rs
+++ b/crates/hyperswitch_connectors/src/connecto... | 2024-12-11T11:54:10Z |
## Description
<!-- Describe your changes in detail -->
Add referrer data in Airwallex's Create Payment Intent request in order to whitelist Hyperswitch for processing raw card details.
## Motivation and Context
<!--
Why is this change required? What problem does it solve?
If it fixes an open issue, please li... | cd205378c035780586f6b94e5c9e03466165a33b |
Testing can be done by verifying payment logs for Airwallex payments
<img width="1276" alt="Screenshot 2024-12-11 at 5 28 08 PM" src="https://github.com/user-attachments/assets/55f4ce53-6e38-46be-9055-d0ea50dd7b0c">
Payments Request:
```
curl --location 'http://localhost:8080/payments' \
--header 'Content-Type: ... | [
"crates/hyperswitch_connectors/src/connectors/airwallex/transformers.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-6800 | Bug: [deps] update scylla driver
| diff --git a/Cargo.lock b/Cargo.lock
index e8315e8049a..4284539c5e5 100644
--- a/Cargo.lock
+++ b/Cargo.lock
@@ -7153,9 +7153,8 @@ dependencies = [
[[package]]
name = "scylla"
-version = "0.14.0"
-source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "8139623d3fb0c8205b15e84fa587f3aa0ba61f876... | 2024-12-11T06:19:00Z |
## Description
<!-- Describe your changes in detail -->
Update scylla driver on masking crate
## 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 s... | 400d9a42de4cb99e3e2d7dc69510f503661700e4 |
Compiler guided. Testing not needed in environments
| [
"Cargo.lock",
"crates/masking/Cargo.toml",
"crates/masking/src/cassandra.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-6788 | Bug: refactor(permissions): Give access to connector view group in operation groups
Currently `connector_label` is not visible in payments page of control-center. This is because, the payment retrieve API doesn't send the `connector_label`. As it is a big change in the payments flow, we are providing access to conne... | diff --git a/crates/router/src/routes/admin.rs b/crates/router/src/routes/admin.rs
index 80d22ad22bf..a57fd56e6c8 100644
--- a/crates/router/src/routes/admin.rs
+++ b/crates/router/src/routes/admin.rs
@@ -431,7 +431,10 @@ pub async fn connector_retrieve(
&auth::AdminApiAuthWithMerchantIdFromHeader,
... | 2024-12-10T13:06:55Z |
## Description
<!-- Describe your changes in detail -->
This PR will make connector_view group accessible by operation groups.
This PR will also change the permission of connector_retrieve API from connector_read to connector_write as it contains sensitive data.
## Motivation and Context
<!--
Why is thi... | 08ab3ad7a2e60bc35332be606941793bc6a8a32f |
```
curl 'http://localhost:8080/account/merchant_1733829021/profile/connectors' \
-H 'Content-Type: application/json' \
-H 'Cookie: login_token=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJ1c2VyX2lkIjoiMzgyMWViZTktNGVkZS00Y2Y5LTlkNDQtNDgzZGFjMTM2ODEzIiwibWVyY2hhbnRfaWQiOiJtZXJjaGFudF8xNzMzODI5MDIxIiwicm9sZV9pZCI6In... | [
"crates/router/src/routes/admin.rs",
"crates/router/src/services/authorization/permission_groups.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-6786 | Bug: refactor(dynamic_routing): update the authentication for update config to include JWT type
Enable JWT to be used for update config for success based routing route, previously it was only admin api key.
| diff --git a/crates/openapi/src/openapi.rs b/crates/openapi/src/openapi.rs
index 7ad5645e75a..fc8668905ca 100644
--- a/crates/openapi/src/openapi.rs
+++ b/crates/openapi/src/openapi.rs
@@ -159,7 +159,9 @@ Never share your secret api keys. Keep them guarded and secure.
routes::routing::routing_retrieve_linked_c... | 2024-12-10T09:10:55Z |
## Description
<!-- Describe your changes in detail -->
This PR will enable JWT to be used for update config for success based routing route, previously it was only admin api key.
## Motivation and Context
<!--
Why is this change required? What problem does it solve?
If it fixes an open issue, please link to ... | 886e2aacd7dcd8a04a33884ceafb1562aa7c365f |
This will be checked with JWT token.
```
curl --location --request PATCH '{base_url}/account/:account_id/business_profile/:profile_id/dynamic_routing/success_based/config/:routing_config_id' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer token' \
--data '{
"params": [
"Curr... | [
"crates/openapi/src/openapi.rs",
"crates/openapi/src/routes/routing.rs",
"crates/router/src/routes/routing.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-6782 | Bug: Adding new logo in API ref and Readme
| diff --git a/api-reference-v2/logo/dark.svg b/api-reference-v2/logo/dark.svg
index fbf0d89d410..f07be0cea14 100644
--- a/api-reference-v2/logo/dark.svg
+++ b/api-reference-v2/logo/dark.svg
@@ -1,29 +1,21 @@
-<svg width="766" height="100" viewBox="0 0 766 100" fill="none" xmlns="http://www.w3.org/2000/svg">
-<g clip-pat... | 2024-12-09T21:10:32Z |
## Description
<!-- Describe your changes in detail -->
## 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 PR
can focus on the implement... | 05f737309f7fac9f0985fac2948a57398c286317 | [
"api-reference-v2/logo/dark.svg",
"api-reference-v2/logo/light.svg"
] | ||
juspay/hyperswitch | juspay__hyperswitch-6778 | Bug: Adding support for Tenant ID in Kafka events apart from Transactional events ( API , Connector, Outgoing )
Need to add tenant-id for kafka events for the domains API events, Connector events and Outgoing Webhook Events | diff --git a/crates/hyperswitch_interfaces/src/events/connector_api_logs.rs b/crates/hyperswitch_interfaces/src/events/connector_api_logs.rs
index 5edd8d68c32..bf9eafe5aaf 100644
--- a/crates/hyperswitch_interfaces/src/events/connector_api_logs.rs
+++ b/crates/hyperswitch_interfaces/src/events/connector_api_logs.rs
@@ ... | 2024-12-09T09:51:37Z |
## Description
<!-- Describe your changes in detail -->
The changes are required for pushing tenant ID for API events, Connector events and Outgoing Webhook events
## 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.
... | 05f737309f7fac9f0985fac2948a57398c286317 |
Attaching screenshots
<img width="917" alt="Screenshot 2024-12-09 at 3 20 34 PM" src="https://github.com/user-attachments/assets/b8918318-68b5-426c-aad3-9eed76cd5150">
<img width="925" alt="Screenshot 2024-12-09 at 3 20 08 PM" src="https://github.com/user-attachments/assets/b21c5b4b-359b-4d35-a875-c33154c06e... | [
"crates/hyperswitch_interfaces/src/events/connector_api_logs.rs",
"crates/router/src/core/webhooks/incoming.rs",
"crates/router/src/core/webhooks/incoming_v2.rs",
"crates/router/src/core/webhooks/outgoing.rs",
"crates/router/src/events/api_logs.rs",
"crates/router/src/events/outgoing_webhook_logs.rs",
"... | |
juspay/hyperswitch | juspay__hyperswitch-6775 | Bug: feat(analytics): add support for multiple emails as input to forward reports
Currently, while generating reports on the dashboard, the current setup only supports forwarding reports to the email of the account signed in.
Should add support to have custom emails in the input text box on the dashboard while gener... | diff --git a/crates/api_models/src/analytics.rs b/crates/api_models/src/analytics.rs
index 806eb4b6e0e..7f58c6b00d7 100644
--- a/crates/api_models/src/analytics.rs
+++ b/crates/api_models/src/analytics.rs
@@ -114,6 +114,7 @@ pub struct RefundDistributionBody {
#[serde(rename_all = "camelCase")]
pub struct ReportReque... | 2024-12-09T07:26:15Z |
## Description
<!-- Describe your changes in detail -->
Currently, while generating reports on the dashboard, the current setup only supports forwarding reports to the email of the account signed in.
This PR adds support to have custom emails in the input text box on the dashboard while generating and forwarding th... | 079379e7290df47ac2410be50e066d84728a85ad |
Hit the curl:
```bash
curl --location 'http://localhost:8080/analytics/v1/org/report/payments' \
--header 'Accept: */*' \
--header 'Accept-Language: en-US,en;q=0.9' \
--header 'Connection: keep-alive' \
--header 'Content-Type: application/json' \
--header 'Origin: http://localhost:9000' \
--header 'Referer: h... | [
"crates/api_models/src/analytics.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-6780 | Bug: feat(users): Introduce themes in user APIs
Currently there is no themes context in the user and email related APIs where the themes should be reflected.
We should change the APIs which would have the theme context.
| diff --git a/config/config.example.toml b/config/config.example.toml
index 5aa9e543fb2..0fe6b8caa2c 100644
--- a/config/config.example.toml
+++ b/config/config.example.toml
@@ -797,5 +797,12 @@ host = "localhost" # Client Host
port = 7000 # Client Port
service = "dynamo" # Service name
-[theme_storage]
+[the... | 2024-12-06T14:42:13Z |
## Description
<!-- Describe your changes in detail -->
- This PR will introduce theme context in user APIs and email related APIs.
- The User APIs which are affected are
1. User Info
2. Invite
3. Resend Invite
4. Reset Password
5. Connect Account
6. Signup with merchant id
- Non ... | 08ab3ad7a2e60bc35332be606941793bc6a8a32f |
1. User Info API will send `theme_id` in the response if a theme exists in your lineage.
```
curl --location 'http://localhost:8080/user' \
--header 'Cookie: login_token=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJ1c2VyX2lkIjoiMzAwMjAwN2UtZWE3NC00NzVlLWJmNWQtMzYxNzIwNTk4YzA3IiwibWVyY2hhbnRfaWQiOiJtZXJjaGFu... | [
"config/config.example.toml",
"config/deployments/env_specific.toml",
"config/development.toml",
"config/docker_compose.toml",
"crates/api_models/src/user.rs",
"crates/api_models/src/user/theme.rs",
"crates/common_utils/src/types/theme.rs",
"crates/diesel_models/src/query/user/theme.rs",
"crates/die... | |
juspay/hyperswitch | juspay__hyperswitch-6773 | Bug: refactor(kafka_message): NanoSecond precision for consolidated logs
Due to millisecond level precision earlier , sessionizer was getting updates in same millisecond due to which updates were not getting picked up. Need to change this behaviour to NanoSecond precision | diff --git a/crates/router/src/services/kafka/dispute_event.rs b/crates/router/src/services/kafka/dispute_event.rs
index 92327c044d7..45e7ff2c798 100644
--- a/crates/router/src/services/kafka/dispute_event.rs
+++ b/crates/router/src/services/kafka/dispute_event.rs
@@ -20,15 +20,15 @@ pub struct KafkaDisputeEvent<'a> {
... | 2024-12-06T13:16:47Z |
## Description
<!-- Describe your changes in detail -->
Adding nanosecond level precision to kafka messages for sessionizer
## 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... | b5d3d49ceaa2f89284ae5976afec0ff5663a24b0 |
Via Kafka UI
| [
"crates/router/src/services/kafka/dispute_event.rs",
"crates/router/src/services/kafka/payment_attempt_event.rs",
"crates/router/src/services/kafka/payment_intent_event.rs",
"crates/router/src/services/kafka/refund_event.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-6841 | Bug: Add support to pass apple pay recurring details in the payment request
Whenever a customer makes an Applepay payment a unique network token called a DPAN (Device Primary Account Number) is created and stored securely on the customer’s Apple device. This token acts as the payment information for all purchases an... | diff --git a/api-reference-v2/openapi_spec.json b/api-reference-v2/openapi_spec.json
index ee5654cfb6b..17849948516 100644
--- a/api-reference-v2/openapi_spec.json
+++ b/api-reference-v2/openapi_spec.json
@@ -3288,12 +3288,169 @@
}
],
"nullable": true
+ },
+ "r... | 2024-12-06T12:20:54Z |
## Description
<!-- Describe your changes in detail -->
Whenever a customer makes an Applepay payment a unique network token called a DPAN (Device Primary Account Number) is created and stored securely on the customer’s Apple device. This token acts as the payment information for all purchases and keeps the raw card... | da4642761495fba88e76ae7cbb567afdac28dce0 |
-> Create a merchant connector account with applepay metadata to decrypt the apple pay token at hyperswitch
-> Create a payment by passing `apple_pay_recurring_details`
```
curl --location 'http://localhost:8080/payments' \
--header 'Content-Type: application/json' \
--header 'Accept: application/json' \
--head... | [
"api-reference-v2/openapi_spec.json",
"crates/api_models/src/payments.rs",
"crates/diesel_models/src/types.rs",
"crates/hyperswitch_connectors/src/connectors/bluesnap/transformers.rs",
"crates/hyperswitch_domain_models/src/lib.rs",
"crates/hyperswitch_domain_models/src/router_request_types.rs",
"crates/... | |
juspay/hyperswitch | juspay__hyperswitch-6828 | Bug: [FEATURE] Contract Routing Integration
### Feature Description
Integration of Contract based routing in Router
### Possible Implementation
Need to build interface, perform core integration and populate metrics for contract routing
### Have you spent some time checking if this feature request has been raised... | diff --git a/crates/api_models/src/events/routing.rs b/crates/api_models/src/events/routing.rs
index f3e169336bf..122d1f8d3c8 100644
--- a/crates/api_models/src/events/routing.rs
+++ b/crates/api_models/src/events/routing.rs
@@ -1,12 +1,13 @@
use common_utils::events::{ApiEventMetric, ApiEventsType};
use crate::rou... | 2024-12-05T20:19:52Z |
## Description
<!-- Describe your changes in detail -->
- Built an interface for Contract based routing
- Integrated Contract based routing with hyperswitch
- Built new APIs for contract routing config setup
- Refactored some existing dynamic routing code
## Motivation and Context
<!--
Why is this change ... | 22072fd750940ac7fec6ea971737409518600891 |
1. Enable Contract routing config
```
curl --location --request POST 'http://localhost:8080/account/sarthak2/business_profile/pro_YozTgS8HebvBlk0UaeWW/dynamic_routing/contracts/toggle?enable=dynamic_connector_selection' \
--header 'api-key: dev_1aD8YuFd6Ovanf3oOtAYobqI6qw4ZBRSfw6BgYbifWHpaopkisBtm8obNXkFbVJn' \
-... | [
"crates/api_models/src/events/routing.rs",
"crates/api_models/src/routing.rs",
"crates/external_services/build.rs",
"crates/external_services/src/grpc_client/dynamic_routing.rs",
"crates/external_services/src/grpc_client/dynamic_routing/contract_routing_client.rs",
"crates/external_services/src/grpc_clien... | |
juspay/hyperswitch | juspay__hyperswitch-6754 | Bug: [FEATURE] [INESPAY] Implement Sepa Bank Debit Flow
### Feature Description
Implement Sepa Bank Debit Flow
### Possible Implementation
Implement Sepa Bank Debit Flow
### Have you spent some time checking if this feature request has been raised before?
- [X] I checked and didn't find a similar issue
### Hav... | diff --git a/api-reference-v2/openapi_spec.json b/api-reference-v2/openapi_spec.json
index 41b2c0f80e4..330e504c272 100644
--- a/api-reference-v2/openapi_spec.json
+++ b/api-reference-v2/openapi_spec.json
@@ -6622,6 +6622,7 @@
"gocardless",
"gpayments",
"helcim",
+ "inespay",
... | 2024-12-05T08:14:02Z |
## Description
<!-- Describe your changes in detail -->
Added payment flows (Auth, PSync, Refund, RSync, and Webhooks) for Inespay Sepa Bank Debit.
## 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'... | 062e1d1757ab894d3d7d88534372f8a85e77a8b6 |
1. Merchant Account Create
2. API Key Create
3.Inespay Connector Create:
```
curl --location 'http://localhost:8080/account/merchant_1736331946/connectors' \
--header 'Content-Type: application/json' \
--header 'Accept: application/json' \
--header 'api-key: test_admin' \
--data '{
"connector_type": "pay... | [
"api-reference-v2/openapi_spec.json",
"config/development.toml",
"crates/common_enums/src/connector_enums.rs",
"crates/connector_configs/src/connector.rs",
"crates/hyperswitch_connectors/src/connectors/inespay.rs",
"crates/hyperswitch_connectors/src/connectors/inespay/transformers.rs",
"crates/router/sr... | |
juspay/hyperswitch | juspay__hyperswitch-6750 | Bug: [BUG] Network token data is being fetched in CIT repeat irrespective of connector
Currently, Network token data is being fetched in CIT repeat irrespective of connector decided by routing. this would to lead to failure of payments with "payment method not implemented".
New Implementation -
connector decide... | diff --git a/crates/router/src/core/payment_methods.rs b/crates/router/src/core/payment_methods.rs
index 599d696ec06..39889bf7577 100644
--- a/crates/router/src/core/payment_methods.rs
+++ b/crates/router/src/core/payment_methods.rs
@@ -588,6 +588,7 @@ pub async fn retrieve_payment_method_with_token(
m... | 2024-12-04T22:09:10Z |
## Description
<!-- Describe your changes in detail -->
Currently we always fetch network token for the connector that does not support network tokenization.
Fix: we ll only fetch network token if the connector supports network tokenization else fetch card details to make CIT repeat.
## Motivation and Context... | 086115f47379b06185a1753979fc6dd9dc945afd |
test cases -
Create two MCA ex - Cybersource(network tokenization supported conn), Adyen
enable network tokenization for business profile
Make saved card flow transaction.
when routable connector list - [Cybersource, Adyen] -> payment should happen with Network token + cryptogram
when routable connector list -... | [
"crates/router/src/core/payment_methods.rs",
"crates/router/src/core/payments/helpers.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-6748 | Bug: fix(api_models): `wasm` build problems caused by `actix-multipart`
`wasm` build is failing because of adding `actix-multipart` dependency in `api-models`.
As we cannot change any dependencies in `wasm`, we will have to make changes to `api_models` to fix this. | diff --git a/crates/api_models/Cargo.toml b/crates/api_models/Cargo.toml
index eb706dc913c..e5bf74c20c6 100644
--- a/crates/api_models/Cargo.toml
+++ b/crates/api_models/Cargo.toml
@@ -8,7 +8,7 @@ readme = "README.md"
license.workspace = true
[features]
-errors = ["dep:reqwest"]
+errors = ["dep:actix-web", "dep:req... | 2024-12-04T13:49:31Z |
## Description
<!-- Describe your changes in detail -->
Wasm build is failing because of adding `actix-multipart` dependency in `api-models`.
## 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 a... | 3a3e93cb3be3fc3ffabef2a708b49defabf338a5 |
Checked by building `wasm` locally. It worked.

No need to run any other tests as this is an internal change.
| [
"crates/api_models/Cargo.toml",
"crates/api_models/src/events/user.rs",
"crates/api_models/src/user.rs",
"crates/router/Cargo.toml"
] | |
juspay/hyperswitch | juspay__hyperswitch-6742 | Bug: Updating logo in API ref
| 2024-12-04T12:36:25Z |
## Description
<!-- Describe your changes in detail -->
## 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 PR
can focus on the implement... | dc26317e9bc1aa82666e978c5e824ccb9b016d31 | [] | |||
juspay/hyperswitch | juspay__hyperswitch-6731 | Bug: feat(analytics): Analytics Request Validator and config driven forex feature
## Current behaviour
- Forex api calls are occuring on every analytics api call
- There is no analytics request validator.
## Proposed Changes
- Enable/Disable forex functionality based on a config flag.
- `request_validator()` to v... | diff --git a/config/config.example.toml b/config/config.example.toml
index 54a3ab3827b..fbeea44774b 100644
--- a/config/config.example.toml
+++ b/config/config.example.toml
@@ -660,6 +660,7 @@ pm_auth_key = "Some_pm_auth_key"
# Analytics configuration.
[analytics]
source = "sqlx" # The Analytics source/strategy to b... | 2024-12-03T13:03:26Z |
## Fixes #6731
## Description
<!-- Describe your changes in detail -->
### Config driven forex functionality
- Created a `forex_enabled` flag in config settings under analytics config.
- Instead of passing `ExchangeRates` data structure now we are passing `Option<ExchangeRates>`
- In amount related fields of ... | d75625f11d4611c688593d5730efc8c6f2c59afd |
### Prerequisites
```toml
[analytics]
source = "sqlx"
forex_enabled = false # update this to enable or disable
```
### Testing config driven forex api call
```bash
curl --location 'http://localhost:8080/analytics/v1/org/metrics/payments' \
--header 'Accept: */*' \
--header 'Accept-Language: en-GB,en-US;q=0.... | [
"config/config.example.toml",
"config/deployments/env_specific.toml",
"config/development.toml",
"crates/analytics/docs/README.md",
"crates/analytics/src/lib.rs",
"crates/analytics/src/payment_intents/core.rs",
"crates/analytics/src/payments/core.rs",
"crates/analytics/src/refunds/core.rs",
"crates/... | |
juspay/hyperswitch | juspay__hyperswitch-6625 | Bug: Feature(routing): Stats table for dynamic_routing
## Description
Creation of new table for storing required fields for dynamic_routing for list and point queries. | diff --git a/crates/api_models/src/routing.rs b/crates/api_models/src/routing.rs
index c4c2f072b1e..eeb67d679ee 100644
--- a/crates/api_models/src/routing.rs
+++ b/crates/api_models/src/routing.rs
@@ -740,7 +740,6 @@ pub struct ToggleDynamicRoutingPath {
#[derive(serde::Serialize, serde::Deserialize, Debug, Clone, ToS... | 2024-12-02T17:06:01Z |
## Description
<!-- Describe your changes in detail -->
Previously we were pushing the Dynamic routing metrics to Prometheus, but due to high cardinality of some values(payment_id) we were not able to add that in our attributes, hence we are pushing this after creating a new table in our Database (dynamic_routing_st... | 03b936a117ae0931fab800cb82038ba45aa6f9a3 |
Can be tested in the following ways:
1. enable success_based_routing(feature = metrics) for merchant.
```
curl --location --request POST 'http://localhost:8080/account/m_id/business_profile/pro_id/dynamic_routing/success_based/toggle?enable=metrics' \
--header 'api-key:api_key'
```
2. Make a payment afterwards.... | [
"crates/api_models/src/routing.rs",
"crates/common_enums/src/enums.rs",
"crates/diesel_models/src/dynamic_routing_stats.rs",
"crates/diesel_models/src/enums.rs",
"crates/diesel_models/src/lib.rs",
"crates/diesel_models/src/query.rs",
"crates/diesel_models/src/query/dynamic_routing_stats.rs",
"crates/d... | |
juspay/hyperswitch | juspay__hyperswitch-6715 | Bug: fix(opensearch): fix empty filter array query addition in globalsearch query
Fix the opensearch query building, when free-text query is empty, no case-sensitive filters are passed and time-range is also not mentioned | diff --git a/crates/analytics/src/opensearch.rs b/crates/analytics/src/opensearch.rs
index e8726840a2e..246a0f4e8bb 100644
--- a/crates/analytics/src/opensearch.rs
+++ b/crates/analytics/src/opensearch.rs
@@ -705,9 +705,7 @@ impl OpenSearchQueryBuilder {
let should_array = self.build_auth_array();
- ... | 2024-12-02T09:29:40Z |
## Description
<!-- Describe your changes in detail -->
The opensearch query should be built manually in the code, based on the request body.
There is a component called `filter_array` which comprises of the free-text search query, addition of case sensitive filters and also the time_range (if provided).
When all ... | 797a0db7733c5b387564fb1bbc106d054c8dffa6 |
Should test the case when free-text query is empty, case-sensitive filters are not provided, and time-range filter is also not applied.
Hit the curl:
```bash
curl --location 'http://localhost:8080/analytics/v1/search' \
--header 'sec-ch-ua-platform: "macOS"' \
--header 'authorization: Bearer eyJ0eXAiOiJKV1QiLCJh... | [
"crates/analytics/src/opensearch.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-6713 | Bug: ci: update expiry year to a later date
ntid checks are failing because of expired cards | 2024-12-02T09:21:32Z |
## Description
<!-- Describe your changes in detail -->
this pr increments expiry year to a later date
closes https://github.com/juspay/hyperswitch/issues/6713
## 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.... | 22b5a93e02156cd92adf5e24a3fd8d0e39e8d429 |
ci should pass
| [] | ||
juspay/hyperswitch | juspay__hyperswitch-6707 | Bug: feat(users): support tenant level users
- Add api to create tenant_admin
- Create org by tenant level user
- Support tenant entity: tenant level roles/permission | diff --git a/crates/api_models/src/events/user.rs b/crates/api_models/src/events/user.rs
index 15146e304af..a244f69f543 100644
--- a/crates/api_models/src/events/user.rs
+++ b/crates/api_models/src/events/user.rs
@@ -9,15 +9,15 @@ use crate::user::{
theme::{CreateThemeRequest, GetThemeResponse, UpdateThemeRequest,... | 2024-12-01T21:16:10Z |
## Description
- Add api to create tenant users
- Add api to create orgs
- Support tenant level entity for the user hierarchy
A tenant level user should see dashboard as seen by the org admin. He will be pinned to one org, merchant and profile. And he can switch between any org in the given tenancy.
## Motiv... | 3a3e93cb3be3fc3ffabef2a708b49defabf338a5 | Api for create tenant:
```
curl --location 'http://localhost:8080/user/tenant_signup' \
--header 'api-key: test_admin' \
--header 'Content-Type: application/json' \
--header 'x-tenant-id: test' \
--header 'Cookie: login_token=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJ1c2VyX2lkIjoiNTJhMmViYzItOWZiZS00MDI0LThjODEtOWY... | [
"crates/api_models/src/events/user.rs",
"crates/api_models/src/user.rs",
"crates/common_enums/src/enums.rs",
"crates/common_utils/src/consts.rs",
"crates/diesel_models/src/query/merchant_account.rs",
"crates/router/src/analytics.rs",
"crates/router/src/consts/user.rs",
"crates/router/src/core/user.rs"... | |
juspay/hyperswitch | juspay__hyperswitch-6704 | Bug: chore: address Rust 1.83.0 clippy lints
### Description
Address the clippy lints stabilized / enabled in Rust version 1.83.0.
See #3391 for more information. | diff --git a/.clippy.toml b/.clippy.toml
new file mode 100644
index 00000000000..4296655a040
--- /dev/null
+++ b/.clippy.toml
@@ -0,0 +1 @@
+allow-dbg-in-tests = true
diff --git a/Cargo.toml b/Cargo.toml
index 90eb996b82b..38d895d767a 100644
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -18,12 +18,16 @@ unused_qualifications = ... | 2024-12-01T18:55:46Z |
## Description
<!-- Describe your changes in detail -->
This PR addresses clippy lints stabilized / enabled in Rust 1.83.0. The major warnings being thrown due to the version bump were [`empty_line_after_doc_comments`](https://rust-lang.github.io/rust-clippy/master/index.html#empty_line_after_doc_comments) and [`e... | 982b26a8c2851266b6e8615699479a05ab62e519 |
From what I'd expect, none of the existing behavior should be affected due to these changes. Our Postman and Cypress tests running on CI should pass, as before.
| [
".clippy.toml",
"Cargo.toml",
"api-reference-v2/openapi_spec.json",
"crates/analytics/src/disputes/metrics/sessionized_metrics/mod.rs",
"crates/analytics/src/payment_intents/metrics/sessionized_metrics/mod.rs",
"crates/analytics/src/payments/metrics/sessionized_metrics/mod.rs",
"crates/analytics/src/ref... | |
juspay/hyperswitch | juspay__hyperswitch-6702 | Bug: refactor(users): remove lineage checks in roles get operations
refactor find_by_role_id_in_merchant_scope query to support profile level custom roles | diff --git a/crates/diesel_models/src/query/role.rs b/crates/diesel_models/src/query/role.rs
index 065a5b6e114..6f6a1404ee2 100644
--- a/crates/diesel_models/src/query/role.rs
+++ b/crates/diesel_models/src/query/role.rs
@@ -26,6 +26,7 @@ impl Role {
.await
}
+ // TODO: Remove once find_by_role_id_in... | 2024-11-29T06:19:36Z |
## Description
<!-- Describe your changes in detail -->
- Refactor the find_by_role_id_in_merchant_scope query to make it a generic query that uses only org_id and role_id as parameters.
- This PR also includes backfilling user_roles entity_type column based on user_role
## Motivation and Context
<!--
Why ... | 6eb7cc14613d94f4711e39e16dc015a30b02cf0e |
Using dashboard . All the below should work as before
Cases to test :
- Create a custom role from dashboard
- Invite someone for that custom role
- signin via that custom-role-user
- List roles and list roles at entity level
- List users
| [
"crates/diesel_models/src/query/role.rs",
"crates/diesel_models/src/user_role.rs",
"crates/router/src/analytics.rs",
"crates/router/src/core/user.rs",
"crates/router/src/core/user_role.rs",
"crates/router/src/core/user_role/role.rs",
"crates/router/src/db/kafka_store.rs",
"crates/router/src/db/role.rs... | |
juspay/hyperswitch | juspay__hyperswitch-6698 | Bug: refactor(users): Use domain email type in DB functions
Currently lowercase email check is there in `UserEmail` type. But DB is using `pii::Email` type, which might cause unexpected behaviour in some cases.
| diff --git a/crates/hyperswitch_domain_models/src/errors/api_error_response.rs b/crates/hyperswitch_domain_models/src/errors/api_error_response.rs
index b02da396075..850cc470316 100644
--- a/crates/hyperswitch_domain_models/src/errors/api_error_response.rs
+++ b/crates/hyperswitch_domain_models/src/errors/api_error_res... | 2024-11-28T13:49:22Z |
## Description
<!-- Describe your changes in detail -->
This PR does 3 things.
1. Throw 401 if cookies are not found in request or if JWT is not found in cookies.
2. Cache role info only if the ttl is greater than or equal to 0.
3. Use `UserEmail` type in DB functions.
## Motivation and Context
<!--
Why is ... | 707f48ceda789185187d23e35f483e117c67b81b |
todo!()
| [
"crates/hyperswitch_domain_models/src/errors/api_error_response.rs",
"crates/router/src/compatibility/stripe/errors.rs",
"crates/router/src/core/user.rs",
"crates/router/src/core/user_role.rs",
"crates/router/src/db/kafka_store.rs",
"crates/router/src/db/user.rs",
"crates/router/src/services/authenticat... | |
juspay/hyperswitch | juspay__hyperswitch-6697 | Bug: bug(authz): cache `role_info` only if ttl >= 0
There is a race condition in BE, where application is putting role info into cache when the ttl is negative.
Redis is throwing error when this happens. | diff --git a/crates/hyperswitch_domain_models/src/errors/api_error_response.rs b/crates/hyperswitch_domain_models/src/errors/api_error_response.rs
index b02da396075..850cc470316 100644
--- a/crates/hyperswitch_domain_models/src/errors/api_error_response.rs
+++ b/crates/hyperswitch_domain_models/src/errors/api_error_res... | 2024-11-28T13:49:22Z |
## Description
<!-- Describe your changes in detail -->
This PR does 3 things.
1. Throw 401 if cookies are not found in request or if JWT is not found in cookies.
2. Cache role info only if the ttl is greater than or equal to 0.
3. Use `UserEmail` type in DB functions.
## Motivation and Context
<!--
Why is ... | 707f48ceda789185187d23e35f483e117c67b81b |
todo!()
| [
"crates/hyperswitch_domain_models/src/errors/api_error_response.rs",
"crates/router/src/compatibility/stripe/errors.rs",
"crates/router/src/core/user.rs",
"crates/router/src/core/user_role.rs",
"crates/router/src/db/kafka_store.rs",
"crates/router/src/db/user.rs",
"crates/router/src/services/authenticat... | |
juspay/hyperswitch | juspay__hyperswitch-6696 | Bug: bug(authn): Throw 401 if cookies are not found
Currently BE is throwing 400 if cookies are not found and this is breaking FE if token is present in local storage but not in cookies.
If 401 is thrown, FE will remove the token from the local storage automatically. | diff --git a/crates/hyperswitch_domain_models/src/errors/api_error_response.rs b/crates/hyperswitch_domain_models/src/errors/api_error_response.rs
index b02da396075..850cc470316 100644
--- a/crates/hyperswitch_domain_models/src/errors/api_error_response.rs
+++ b/crates/hyperswitch_domain_models/src/errors/api_error_res... | 2024-11-28T13:49:22Z |
## Description
<!-- Describe your changes in detail -->
This PR does 3 things.
1. Throw 401 if cookies are not found in request or if JWT is not found in cookies.
2. Cache role info only if the ttl is greater than or equal to 0.
3. Use `UserEmail` type in DB functions.
## Motivation and Context
<!--
Why is ... | 707f48ceda789185187d23e35f483e117c67b81b |
todo!()
| [
"crates/hyperswitch_domain_models/src/errors/api_error_response.rs",
"crates/router/src/compatibility/stripe/errors.rs",
"crates/router/src/core/user.rs",
"crates/router/src/core/user_role.rs",
"crates/router/src/db/kafka_store.rs",
"crates/router/src/db/user.rs",
"crates/router/src/services/authenticat... | |
juspay/hyperswitch | juspay__hyperswitch-6709 | Bug: [FEATURE] Add webhook support for network tokenization
### Feature Description
Add webhook support to consume the webhooks from network token requestor.
### Possible Implementation
New webhook wrapper should be introduced, since current implementation are specific to payments, but payment methods.
### Have ... | diff --git a/crates/api_models/src/payment_methods.rs b/crates/api_models/src/payment_methods.rs
index 25b583f5dc4..c681cf7edd0 100644
--- a/crates/api_models/src/payment_methods.rs
+++ b/crates/api_models/src/payment_methods.rs
@@ -1065,6 +1065,23 @@ pub struct Card {
pub nick_name: Option<String>,
}
+#[cfg(fe... | 2024-11-28T13:10:26Z |
## Description
<!-- Describe your changes in detail -->
Add webhooks for network tokenization
- added support to process webhooks from token service.
- verify webhooks updates the pan and network token metadata
## Motivation and Context
<!--
Why is this change required? What problem does it solve?
If it fix... | 46709ae3695eb1a6601c356397545f86de9f0f64 |
This cannot be tested unless we get real-time webhooks from CardNetwork.
| [
"crates/api_models/src/payment_methods.rs",
"crates/api_models/src/webhooks.rs",
"crates/common_enums/src/enums.rs",
"crates/common_types/src/callback_mapper.rs",
"crates/common_types/src/lib.rs",
"crates/common_utils/src/events.rs",
"crates/diesel_models/src/callback_mapper.rs",
"crates/hyperswitch_d... | |
juspay/hyperswitch | juspay__hyperswitch-6693 | Bug: bug(users): Mark users as verified if user comes from SSO
- Currently we are not marking users as verified if they use SSO to login.
- But if there is only SSO to login, then they won't be able to verify their email unless they come from the accept invite email.
- Instead, we will mark users coming from SSO as ... | diff --git a/crates/router/src/core/user.rs b/crates/router/src/core/user.rs
index aad2537c3d9..5595d72850c 100644
--- a/crates/router/src/core/user.rs
+++ b/crates/router/src/core/user.rs
@@ -2318,13 +2318,24 @@ pub async fn sso_sign(
.await?;
// TODO: Use config to handle not found error
- let user_fro... | 2024-11-28T10:33:46Z |
## Description
<!-- Describe your changes in detail -->
Currently we are not marking users as verified if the user comes from SSO and there is no other way to verify if SSO is the only login method that is available.
## Motivation and Context
<!--
Why is this change required? What problem does it solve?
If it... | 707f48ceda789185187d23e35f483e117c67b81b |
```
curl 'http://localhost:9000/api/user/oidc' \
-H 'Content-Type: application/json' \
--data-raw '{"code":"okta oidc code","state":"okta oidc state"}'
```
- The above curl when hit correctly should verify the user if the user was unverified.
| [
"crates/router/src/core/user.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-6691 | Bug: populate card network in the network transaction id based MIT flow
In the PG agnostic MIT flow (card details with network transaction id) the card network is being passed a null in the response. As the card network fetched form the card info lookup is not being used.
Additionally add changes to include the `... | diff --git a/config/config.example.toml b/config/config.example.toml
index ba14ed881cf..76a38192909 100644
--- a/config/config.example.toml
+++ b/config/config.example.toml
@@ -787,6 +787,9 @@ check_token_status_url= "" # base url to check token status from token servic
[network_tokenization_supported_connectors]
... | 2024-11-28T08:03:58Z |
## Description
<!-- Describe your changes in detail -->
In the PG agnostic MIT flow (card details with network transaction id) the card network is being passed a null in the response. As the card network fetched form the card info lookup is not being used.
Additionally this pr also contains the changes to include... | 9be012826abe87ffa2d0cea5423aed3e50449de2 |
-> Create merchant account and merchant connector account
-> enable `is_connector_agnostic_mit_enabled` flag
```
curl --location 'http://localhost:8080/account/merchant_1732783890/business_profile/pro_lNl3x8up5RJTzGLgq0cC' \
--header 'Content-Type: application/json' \
--header 'Accept: application/json' \
--hea... | [
"config/config.example.toml",
"config/deployments/production.toml",
"crates/router/src/connector/cybersource/transformers.rs",
"crates/router/src/core/payments/helpers.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-6692 | Bug: Refactor(router): [ZSL] remove partially capture status
### Feature Description
Currently, in case of underpayment we are mapping the payment status as partially captured.
### Possible Implementation
We will map the underpayment status as succeeded and provide information about the amount actually captured... | diff --git a/crates/hyperswitch_connectors/src/connectors/zsl/transformers.rs b/crates/hyperswitch_connectors/src/connectors/zsl/transformers.rs
index 81019325113..b2ba05b7cde 100644
--- a/crates/hyperswitch_connectors/src/connectors/zsl/transformers.rs
+++ b/crates/hyperswitch_connectors/src/connectors/zsl/transformer... | 2024-11-28T07:54:15Z |
## Description
<!-- Describe your changes in detail -->
Currently, in case of underpayment we are mapping the payment status as `partially captured` with the changes of this PR. We will map the underpayment status as `succeeded` and provide information about the amount actually captured
# | 9be012826abe87ffa2d0cea5423aed3e50449de2 |
Webhooks cannot be tested in ZSL sandbox.
| [
"crates/hyperswitch_connectors/src/connectors/zsl/transformers.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-6684 | Bug: fix(opensearch): handle empty free-text query search in global search
Previously, there was no support to add filters in global-search, hence only free-search queries were supported.
Because of this, the following query object was being mandatorily added.
```bash
{
"multi_match": {
"ty... | diff --git a/crates/analytics/src/opensearch.rs b/crates/analytics/src/opensearch.rs
index 84a2b9db3d4..e8726840a2e 100644
--- a/crates/analytics/src/opensearch.rs
+++ b/crates/analytics/src/opensearch.rs
@@ -510,14 +510,15 @@ impl OpenSearchQueryBuilder {
case_sensitive_filters: Vec<&(String, Vec<String>)>,
... | 2024-11-27T14:28:36Z |
## Description
<!-- Describe your changes in detail -->
Previously, there was no support to add filters in global-search, hence only free-text search queries were supported.
Because of this, the following query object was being mandatorily added.
```bash
{
"multi_match": {
"type": "phr... | d4b482c21cf57b022c7bbadc1a3a9c9d9e5d4f03 |
Hit the curl:
```bash
curl --location 'http://localhost:8080/analytics/v1/search' \
--header 'sec-ch-ua-platform: "macOS"' \
--header 'authorization: Bearer eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJ1c2VyX2lkIjoiNTQ5ZTNkMmItMTY5Yi00NzUzLWJmNTQtZDcxMTM2YjRiN2JkIiwibWVyY2hhbnRfaWQiOiJtZXJjaGFudF8xNzI2MDQ2MzI4Iiwicm... | [
"crates/analytics/src/opensearch.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-6688 | Bug: refactor(dynamic_fields): rename fields like ach, bacs and becs for bank debit payment method
## Type of Change
- Refactoring
## Description
- The fields ach, becs, and bacs in the payment method data (particularly in bank_debit) should be renamed to improve clarity.
## Changes to be made:
- Rename... | diff --git a/crates/router/src/configs/defaults/payment_connector_required_fields.rs b/crates/router/src/configs/defaults/payment_connector_required_fields.rs
index 4e80ccf027e..1cb41827be3 100644
--- a/crates/router/src/configs/defaults/payment_connector_required_fields.rs
+++ b/crates/router/src/configs/defaults/paym... | 2024-11-27T13:05:18Z |
## Description
ach, becs and bacs in payment method data is renamed to ach_bank_debit, becs_bank_debit, bacs_bank_debit
## 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 recomme... | d4b482c21cf57b022c7bbadc1a3a9c9d9e5d4f03 | Tested it through Postman.
- Create Connector (Stripe):
```
{
"connector_type": "payment_processor",
"connector_name": "stripe",
"business_country": "US",
"business_label": "default",
"connector_account_details": {
"auth_type": "HeaderKey",
"api_key": "some key here"
... | [
"crates/router/src/configs/defaults/payment_connector_required_fields.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-6679 | Bug: bug(users): Check lineage across entities in invite
Currently in invites we don't check if user exists across entities.
This will be a problem when inviting a user with higher entity from different lineage.
We should check if user exists across lineage before allowing invite in this case.
| diff --git a/crates/router/src/core/user.rs b/crates/router/src/core/user.rs
index c6501dac3bd..2087d01dbb4 100644
--- a/crates/router/src/core/user.rs
+++ b/crates/router/src/core/user.rs
@@ -642,6 +642,38 @@ async fn handle_existing_user_invitation(
return Err(UserErrors::UserExists.into());
}
+ le... | 2024-11-27T13:02:47Z |
## Description
<!-- Describe your changes in detail -->
Currently in invites we don't check if user exists across entities.
This will be a problem when inviting a user with higher entity from different lineage.
This PR fixes it.
## Motivation and Context
<!--
Why is this change required? What problem does it... | d4b482c21cf57b022c7bbadc1a3a9c9d9e5d4f03 |
1. Invite a user in a specific (org, merchant, profile) combination.
2. Create a new profile in the same merchant account and switch to it.
3. Invite the same user as merchant level user. This should be stopped by API.
| [
"crates/router/src/core/user.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-6565 | Bug: Elimination routing integration
| diff --git a/crates/api_models/src/routing.rs b/crates/api_models/src/routing.rs
index c4c2f072b1e..2e570816ab4 100644
--- a/crates/api_models/src/routing.rs
+++ b/crates/api_models/src/routing.rs
@@ -740,14 +740,13 @@ pub struct ToggleDynamicRoutingPath {
#[derive(serde::Serialize, serde::Deserialize, Debug, Clone, T... | 2024-11-27T07:23:28Z |
## Description
build the gRPC interface for communicating with the external service to perform elimination routing
## 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 ... | d75625f11d4611c688593d5730efc8c6f2c59afd | - Communication is being established with dynamo
<img width="1705" alt="Screenshot 2024-12-05 at 6 03 54 PM" src="https://github.com/user-attachments/assets/09c62052-6c86-47a2-b03f-da0c2835df55">
| [
"crates/api_models/src/routing.rs",
"crates/external_services/build.rs",
"crates/external_services/src/grpc_client/dynamic_routing.rs",
"crates/external_services/src/grpc_client/dynamic_routing/elimination_rate_client.rs",
"crates/external_services/src/grpc_client/dynamic_routing/success_rate_client.rs",
... | |
juspay/hyperswitch | juspay__hyperswitch-6681 | Bug: refactor(currency_conversion): release redis lock if api call fails
### Description
Refactor currency conversion:
-> For Better error propagation
-> For Redis lock realease, if data isn't fetched from api, so that the other subsequent calls donot fail. | diff --git a/crates/router/src/utils/currency.rs b/crates/router/src/utils/currency.rs
index 2173478ab67..9ab2780da73 100644
--- a/crates/router/src/utils/currency.rs
+++ b/crates/router/src/utils/currency.rs
@@ -7,6 +7,7 @@ use error_stack::ResultExt;
use masking::PeekInterface;
use once_cell::sync::Lazy;
use redis... | 2024-11-27T07:12:48Z |
## Description
<!-- Describe your changes in detail -->
Refactors for currency conversion which invlolves:
-> Better error propagation
-> Redis lock realease, if data isn't fetched from api, so that the other subsequent calls donot fail.
## Motivation and Context
<!--
Why is this change required? What proble... | d4b482c21cf57b022c7bbadc1a3a9c9d9e5d4f03 |
Scenarios tested:
1. No api_keys provided: call returned error and redis key was deleted after being set.
2. fallback api_key provided: call returned forex rates and lock was also released.
3. primary api_key provided: call returned forex rates and lock was also released.
| [
"crates/router/src/utils/currency.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-6666 | Bug: fix(analytics): fix first_attempt filter value parsing for Payments
- `first_attempt` filter takes in `true` or `false` as variants.
- But while it is getting applied in the query, it is being converted into a string:
`'true'` or `'false'`
This works on latest clickhouse versions, but fails on the older clickh... | diff --git a/crates/analytics/src/query.rs b/crates/analytics/src/query.rs
index e80f762c41b..caa112ec175 100644
--- a/crates/analytics/src/query.rs
+++ b/crates/analytics/src/query.rs
@@ -459,7 +459,8 @@ impl<T: AnalyticsDataSource> ToSql<T> for common_utils::id_type::CustomerId {
impl<T: AnalyticsDataSource> ToSql... | 2024-11-26T13:05:27Z |
## Description
<!-- Describe your changes in detail -->
Fixes this issue: [https://github.com/juspay/hyperswitch-cloud/issues/7580](https://github.com/juspay/hyperswitch-cloud/issues/7580)
- `first_attempt` filter takes in `true` or `false` as variants.
- But while it is getting applied in the query, it is being c... | d4b482c21cf57b022c7bbadc1a3a9c9d9e5d4f03 |
Hit the curl with first_attempt filter containing either `true` or `false`:
```bash
curl --location 'http://localhost:8080/analytics/v1/org/metrics/payments' \
--header 'Accept: */*' \
--header 'Accept-Language: en-US,en;q=0.9' \
--header 'Connection: keep-alive' \
--header 'Content-Type: application/json' \
... | [
"crates/analytics/src/query.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-6564 | Bug: Volume Split for Intelligent Routing
Hyperswitch currently supports both static and dynamic routing. Develop a feature to provide a volume split between these routing types itself. Example - 20% of the payments, make decisions based on dynamic routing and 80% of the payments, based on static routing. | diff --git a/config/development.toml b/config/development.toml
index eef44648c6c..4e3a9b09993 100644
--- a/config/development.toml
+++ b/config/development.toml
@@ -790,9 +790,10 @@ card_networks = "Visa, AmericanExpress, Mastercard"
[network_tokenization_supported_connectors]
connector_list = "cybersource"
-[grpc_... | 2024-11-26T10:16:33Z |
## Description
<!-- Describe your changes in detail -->
Have added a new API for enabling volume split for dynamic routing service
## 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... | 3a3e93cb3be3fc3ffabef2a708b49defabf338a5 |
```
curl --location --request POST 'http://localhost:8080/account/sarthak1/business_profile/pro_WlO7KCOeDRB8kWk7MSy1/dynamic_routing/set_volume_split?split=20' \
--header 'api-key: dev_iricUDSeFis6RzTGCcYkOt4wmuBcRfjbVbWXbOUO5996boAgztmtfTKN6HNqerjM'
```
Status in DB -
<img width="1511" alt="image" src="https:/... | [
"config/development.toml",
"crates/api_models/src/events/routing.rs",
"crates/api_models/src/routing.rs",
"crates/router/src/consts.rs",
"crates/router/src/core/payments.rs",
"crates/router/src/core/payments/routing.rs",
"crates/router/src/core/routing.rs",
"crates/router/src/core/routing/helpers.rs",... | |
juspay/hyperswitch | juspay__hyperswitch-6660 | Bug: feat(user_roles): support tenant_id reads
For tenancy support tenant_id in user roles queries
- Adding tenant id to reads, deletes and updates queries. | diff --git a/crates/diesel_models/src/query/user_role.rs b/crates/diesel_models/src/query/user_role.rs
index ed018cc2381..bb07f671824 100644
--- a/crates/diesel_models/src/query/user_role.rs
+++ b/crates/diesel_models/src/query/user_role.rs
@@ -1,7 +1,11 @@
use async_bb8_diesel::AsyncRunQueryDsl;
use common_utils::id... | 2024-11-26T09:27:22Z |
## Description
Support tenant id in user roles queries.
## Motivation and Context
Closes [#6660](https://github.com/juspay/hyperswitch/issues/6660)
# | b1c4e30e929fb8d31d854765d5f1ddad5e77f065 | With tenancy feature flag enabled these changes will be tested when upcoming tenant related PRs from dashboard gets merged.
The current behaviour of user apis should not change. Since hyperswitch has its own tenant id and we don't have tenant_id feature flag enabled for now.
Tested the sanity flows for users. Worki... | [
"crates/diesel_models/src/query/user_role.rs",
"crates/router/src/analytics.rs",
"crates/router/src/core/user.rs",
"crates/router/src/core/user_role.rs",
"crates/router/src/db/kafka_store.rs",
"crates/router/src/db/user_role.rs",
"crates/router/src/services/authentication.rs",
"crates/router/src/types... | |
juspay/hyperswitch | juspay__hyperswitch-6673 | Bug: [FEATURE] [REDSYS] add Connector Template Code
### Feature Description
Add Connector Template Code for Redsys
### Possible Implementation
Add Connector Template Code for Redsys
### Have you spent some time checking if this feature request has been raised before?
- [X] I checked and didn't find a similar is... | diff --git a/config/config.example.toml b/config/config.example.toml
index 191f2ba7f8b..c0a7f8ad8d1 100644
--- a/config/config.example.toml
+++ b/config/config.example.toml
@@ -252,6 +252,7 @@ powertranz.base_url = "https://staging.ptranz.com/api/"
prophetpay.base_url = "https://ccm-thirdparty.cps.golf/"
rapyd.base_u... | 2024-11-26T09:11:29Z |
## Description
<!-- Describe your changes in detail -->
Template code added for new connector Inespay
This PR is related to issue: https://github.com/juspay/hyperswitch-cloud/issues/7572
## Motivation and Context
<!--
Why is this change required? What problem does it solve?
If it fixes an open issue, pleas... | 108b1603fa44b2a56c278196edb5a1f76f5d3d03 |
Only template PR, hence no testing required.
| [
"config/config.example.toml",
"config/deployments/integration_test.toml",
"config/deployments/production.toml",
"config/deployments/sandbox.toml",
"config/development.toml",
"config/docker_compose.toml",
"crates/api_models/src/connector_enums.rs",
"crates/common_enums/src/connector_enums.rs",
"crate... | |
juspay/hyperswitch | juspay__hyperswitch-6553 | Bug: feat(themes): APIs for theme management
Backend needs to provide APIs to create and manage themes. Four APIs are planned
1. Create theme
2. Update theme data
3. Delete theme
4. Upload an asset to theme

| diff --git a/Cargo.lock b/Cargo.lock
index 4118ea29c2d..9b0263f99dc 100644
--- a/Cargo.lock
+++ b/Cargo.lock
@@ -455,6 +455,7 @@ checksum = "b3d1d046238990b9cf5bcde22a3fb3584ee5cf65fb2765f454ed428c7a0063da"
name = "api_models"
version = "0.1.0"
dependencies = [
+ "actix-multipart",
"actix-web",
"cards",
"commo... | 2024-11-25T14:04:47Z |
## Description
<!-- Describe your changes in detail -->
This PR adds APIs to manage themes.
These are the following APIs
1. Create Theme
2. Delete Theme
3. Update Theme
4. Upload Asset
5. Find Theme by Theme ID
6. Find Theme by Lineage
## Motivation and Context
<!--
Why is this change required? What pro... | 64383915bda5693df1cecf6cc5683e8b9aaef99b |
1. Create Theme
```
curl --location 'http://localhost:8080/user/theme' \
--header 'Content-Type: application/json' \
--header 'api-key: ••••••' \
--data '{
"lineage": {
"entity_type": "profile",
"tenant_id": "t1",
"org_id": "o1",
"m... | [
"Cargo.lock",
"config/config.example.toml",
"config/deployments/env_specific.toml",
"config/development.toml",
"config/docker_compose.toml",
"crates/api_models/Cargo.toml",
"crates/api_models/src/events/user.rs",
"crates/api_models/src/user.rs",
"crates/api_models/src/user/theme.rs",
"crates/commo... | |
juspay/hyperswitch | juspay__hyperswitch-6656 | Bug: ci: use ubuntu runner
| 2024-11-25T11:34:38Z |
## Description
<!-- Describe your changes in detail -->
Use ubuntu runners instead.
closes https://github.com/juspay/hyperswitch/issues/6656
## 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... | 83e8bc0775c20e9d055e65bd13a2e8b1148092e1 |
See if CI checks pass.
| [] | ||
juspay/hyperswitch | juspay__hyperswitch-6653 | Bug: fix(analytics): fix bugs in payments page metrics in Analytics V2 dashboard
Fix bugs in metrics calculations for Payments page - Analytics V2 dashboard:
- `Successful Payments Distribution` and `Failure Payments Distribution`: Exclude the dropoffs from the denominator while calculating the rates
- `Failure ... | diff --git a/crates/analytics/src/payment_intents/accumulator.rs b/crates/analytics/src/payment_intents/accumulator.rs
index ef3cd3129c4..d8f27501b56 100644
--- a/crates/analytics/src/payment_intents/accumulator.rs
+++ b/crates/analytics/src/payment_intents/accumulator.rs
@@ -273,8 +273,14 @@ impl PaymentIntentMetricAc... | 2024-11-25T08:40:46Z |
## Description
<!-- Describe your changes in detail -->
Fixing some bugs in metrics calculations for Payments page - Analytics V2 dashboard:
- `Successful Payments Distribution` and `Failure Payments Distribution`: Excluded the following dropoffs from the denominator while calculating the rates
- Without smart... | 31204941ee24fe7b23344ba9b4a2615c46f33bb0 |
Sankey:
```bash
curl --location 'http://localhost:8080/analytics/v1/org/metrics/sankey' \
--header 'Accept: */*' \
--header 'Accept-Language: en-US,en;q=0.9' \
--header 'Connection: keep-alive' \
--header 'Content-Type: application/json' \
--header 'Origin: http://localhost:9000' \
--header 'Referer: http://l... | [
"crates/analytics/src/payment_intents/accumulator.rs",
"crates/analytics/src/payment_intents/core.rs",
"crates/analytics/src/payment_intents/sankey.rs",
"crates/analytics/src/payments/accumulator.rs",
"crates/analytics/src/payments/metrics/sessionized_metrics/failure_reasons.rs",
"crates/api_models/src/an... | |
juspay/hyperswitch | juspay__hyperswitch-6647 | Bug: [REFACTOR] add `error_category` column to gsm table
Add `error_category` column to gsm table which is an enum in application. These could be used to take multiple decisions but currently these are required for elimination routing in which these categories will serve as bucket name. | diff --git a/api-reference-v2/openapi_spec.json b/api-reference-v2/openapi_spec.json
index e3f54813a43..ae9265aa41d 100644
--- a/api-reference-v2/openapi_spec.json
+++ b/api-reference-v2/openapi_spec.json
@@ -7776,6 +7776,16 @@
}
}
},
+ "ErrorCategory": {
+ "type": "string",
+ ... | 2024-11-24T12:45:50Z |
## Description
<!-- Describe your changes in detail -->
This PR adds `error_category` column to gsm table which is an enum in application. These could be used to take multiple decisions in future but currently these are required for elimination routing in which these categories will serve as bucket name.
Additional... | 797a0db7733c5b387564fb1bbc106d054c8dffa6 |
Added new column to GSM table. (`error_category`)
```
curl --location 'http://localhost:8080/gsm' \
--header 'Content-Type: application/json' \
--header 'Accept: application/json' \
--header 'api-key: test_admin' \
--data '{
"connector": "stripe",
"flow" : "flow1",
"sub_flow": "sub_flow",
"code": ... | [
"api-reference-v2/openapi_spec.json",
"crates/api_models/src/gsm.rs",
"crates/common_enums/src/enums.rs",
"crates/diesel_models/src/gsm.rs",
"crates/diesel_models/src/schema.rs",
"crates/diesel_models/src/schema_v2.rs",
"crates/openapi/src/openapi.rs",
"crates/openapi/src/openapi_v2.rs",
"crates/rou... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.