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-4674 | Bug: Add audit events for CompleteAuthorize update
Created from #4525
This covers adding events for Complete Authorize operation
This event should include the payment data similar to [PaymentCancel](https://github.com/juspay/hyperswitch/pull/4166)
It should also include any metadata for the event
e.g re... | diff --git a/crates/router/src/core/payments/operations/payment_complete_authorize.rs b/crates/router/src/core/payments/operations/payment_complete_authorize.rs
index 850fa738cd8..8c003f54adf 100644
--- a/crates/router/src/core/payments/operations/payment_complete_authorize.rs
+++ b/crates/router/src/core/payments/oper... | 2024-10-14T13:49:41Z |
## Description
Created from #4674
This covers adding events for `CompleteAuthorize` operation
## How did you test it
Use `globalpay` as connector, `wallet` as payment_method and `paypal` as payment_method_type
```bash
"payment_method": "wallet",
"payment_method_types": [
... | 535c8d4e6fc8226a66ba2c45bb8102625454306c | [
"crates/router/src/core/payments/operations/payment_complete_authorize.rs",
"crates/router/src/events/audit_events.rs"
] | ||
juspay/hyperswitch | juspay__hyperswitch-6307 | Bug: [FEATURE] Set header consumption as optional in Open banking flows
### Feature Description
Set header consumption as optional in Open banking flows
### Possible Implementation
Set header consumption as optional in Open banking flows
### Have you spent some time checking if this feature request has been rais... | diff --git a/crates/api_models/src/pm_auth.rs b/crates/api_models/src/pm_auth.rs
index 443a4c30394..8ed52907da8 100644
--- a/crates/api_models/src/pm_auth.rs
+++ b/crates/api_models/src/pm_auth.rs
@@ -4,8 +4,6 @@ use common_utils::{
id_type, impl_api_event_type,
};
-use crate::enums as api_enums;
-
#[derive(De... | 2024-10-14T09:59:58Z |
## Description
<!-- Describe your changes in detail -->
Make header data to consume in open banking flows as optional.
## 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... | a7c6f57668683132ac3b59a0398742ea9d12bdca |
Test all open banking flows (PM auth and Payment initiation)
Refer to this PR - https://github.com/juspay/hyperswitch/pull/3952
| [
"crates/api_models/src/pm_auth.rs",
"crates/pm_auth/src/connector/plaid/transformers.rs",
"crates/pm_auth/src/types.rs",
"crates/router/src/connector/plaid/transformers.rs",
"crates/router/src/core/pm_auth.rs",
"crates/router/src/routes/pm_auth.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-6303 | Bug: [FEATURE] Enable Paze Wallet for Cybersource on Dashboard
### Feature Description
Enable Paze Wallet for Cybersource on Dashboard
### Possible Implementation
Enable Paze Wallet for Cybersource on Dashboard
### Have you spent some time checking if this feature request has been raised before?
- [X]... | diff --git a/crates/connector_configs/toml/development.toml b/crates/connector_configs/toml/development.toml
index 3e81062b91e..f4523cf6171 100644
--- a/crates/connector_configs/toml/development.toml
+++ b/crates/connector_configs/toml/development.toml
@@ -1213,6 +1213,8 @@ merchant_secret="Source verification key"
... | 2024-10-14T07:32:52Z |
## Description
<!-- Describe your changes in detail -->
Enable Paze Wallet for Cubersource on 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 have an issue, we'd recommend starting with ... | 19a8474d8731ed7149b541f02ad237e30c4c9f24 |
Only config changes hence no testing required.
| [
"crates/connector_configs/toml/development.toml",
"crates/connector_configs/toml/sandbox.toml"
] | |
juspay/hyperswitch | juspay__hyperswitch-2346 | Bug: [FEATURE]: [Rapyd] Use `connector_response_reference_id` as reference to merchant
### :memo: Feature Description
- Reference id are used to map transactions in the connector’s dashboard.
- Hyperswitch manages several reference ids, such as `payment_id`, `attempt_id`, and `connector_transaction_id` for a single... | diff --git a/crates/router/src/connector/rapyd/transformers.rs b/crates/router/src/connector/rapyd/transformers.rs
index 044a64b413c..6689c5b46f4 100644
--- a/crates/router/src/connector/rapyd/transformers.rs
+++ b/crates/router/src/connector/rapyd/transformers.rs
@@ -274,6 +274,7 @@ pub struct ResponseData {
pub ... | 2024-10-14T06:50:16Z |
## Description
Add connector_response_reference_id support for Rapyd
- Used `merchant_reference_id` as the reference id, while implementing this!
Resolves #2346
## Motivation and Context
<!--
Why is this change required? What problem does it solve?
If it fixes an open issue, please link to the issue her... | 9597215a66e38b0021bd804ffe4d9d040e30f8f9 | [
"crates/router/src/connector/rapyd/transformers.rs"
] | ||
juspay/hyperswitch | juspay__hyperswitch-6473 | Bug: [FEATURE] Add support for network token migration
Currently, the migration api only supports card raw details migration.
Feature description -
Add support to migrate raw network token details along with the network token requestor ref id. | diff --git a/crates/api_models/src/events/payment.rs b/crates/api_models/src/events/payment.rs
index b1f15188dcb..6fdb7d59b0f 100644
--- a/crates/api_models/src/events/payment.rs
+++ b/crates/api_models/src/events/payment.rs
@@ -18,7 +18,7 @@ use crate::{
ListCountriesCurrenciesResponse, PaymentMethodCollectLi... | 2024-10-13T21:59:05Z |
## Description
<!-- Describe your changes in detail -->
Add support for network token migration.
## 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... | 43d87913ab3d177a6d193b3e475c96609cc09a28 |
test migration api.
req -
```
curl --location 'http://localhost:8080/payment_methods/migrate' \
--header 'Content-Type: application/json' \
--header 'Accept: application/json' \
--header 'api-key: api-key' \
--data '{
"merchant_id": "merchant_id",
"card": {
"card_number": "card_number",
... | [
"crates/api_models/src/events/payment.rs",
"crates/api_models/src/payment_methods.rs",
"crates/diesel_models/src/payment_method.rs",
"crates/router/src/core/payment_methods/cards.rs",
"crates/router/src/core/payment_methods/migration.rs",
"crates/router/src/core/payments/tokenization.rs",
"crates/router... | |
juspay/hyperswitch | juspay__hyperswitch-6024 | Bug: [REFACTOR]: [WELLSFARGO] Add amount conversion framework to Wellsfargo
### :memo: Feature Description
Currently, amounts are represented as `i64` values throughout the application. We want to introduce a `Unit` struct that explicitly states the denomination. A new type, `MinorUnit`, has been added to standar... | diff --git a/crates/common_utils/src/types.rs b/crates/common_utils/src/types.rs
index 0cad88bfd4f..1c0ca722f29 100644
--- a/crates/common_utils/src/types.rs
+++ b/crates/common_utils/src/types.rs
@@ -580,6 +580,10 @@ impl StringMajorUnit {
.ok_or(ParsingError::DecimalToI64ConversionFailure)?;
Ok(... | 2024-10-13T18:46:13Z |
## Description
<!-- Describe your changes in detail -->
This PR do amount conversion changes for Wellsfargo Connector and it accepts the amount in StringMajorUnit
## 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.
... | 19a8474d8731ed7149b541f02ad237e30c4c9f24 | [
"crates/common_utils/src/types.rs",
"crates/router/src/connector/wellsfargo.rs",
"crates/router/src/connector/wellsfargo/transformers.rs",
"crates/router/src/types/api.rs",
"crates/router/tests/connectors/wellsfargo.rs"
] | ||
juspay/hyperswitch | juspay__hyperswitch-6294 | Bug: [BUG] Broken link to FAQs
### Bug Description
The link in this line:
https://github.com/juspay/hyperswitch/blob/19a8474d8731ed7149b541f02ad237e30c4c9f24/README.md?plain=1#L317
is broken.
### Expected Behavior
When I click the link I should be taken to some FAQ page.
### Actual Behavior
When I click that ... | diff --git a/README.md b/README.md
index f5c27411b51..3814ac925ad 100644
--- a/README.md
+++ b/README.md
@@ -21,7 +21,6 @@ The single API to access payment ecosystems across 130+ countries</div>
<a href="#community">Community</a> •
<a href="#bugs-and-feature-requests">Bugs and feature requests</a> •
<a href="#... | 2024-10-13T15:06: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... | 2a53f52f994ca98a31509f05e31b3874b88d15bf |
Manual check of the README.md file.
| [
"README.md"
] | |
juspay/hyperswitch | juspay__hyperswitch-2315 | Bug: [FEATURE]: [Rapyd] Use `connector_request_reference_id` as reference to the connector
### :memo: Feature Description
- We transmit our reference id from Hyperswitch to the connector, enabling merchants to subsequently locate the payment within the connector dashboard.
- Presently, there is a lack of uniformit... | diff --git a/crates/router/src/connector/rapyd/transformers.rs b/crates/router/src/connector/rapyd/transformers.rs
index 044a64b413c..939004f8ea9 100644
--- a/crates/router/src/connector/rapyd/transformers.rs
+++ b/crates/router/src/connector/rapyd/transformers.rs
@@ -37,6 +37,7 @@ pub struct RapydPaymentsRequest {
... | 2024-10-12T13:47:08Z |
## Description
Add connector_request_reference_id support for Rapyd
- Used `merchant_reference_id` as the reference id, while implementing this!
Resolves #2315
## 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... | 9597215a66e38b0021bd804ffe4d9d040e30f8f9 | [
"crates/router/src/connector/rapyd/transformers.rs"
] | ||
juspay/hyperswitch | juspay__hyperswitch-6111 | Bug: [FEATURE] Extend the BatchSampleDataInterface Trait for Disputes
### Feature Description
The issue is sub part of issue: #5991
We currently have a feature for generating sample data, which includes batch insertion of payments and refunds. The feature inserts payments and refunds in batches using the Batc... | diff --git a/crates/diesel_models/src/query/user/sample_data.rs b/crates/diesel_models/src/query/user/sample_data.rs
index b5400f570a3..27e674f7d7b 100644
--- a/crates/diesel_models/src/query/user/sample_data.rs
+++ b/crates/diesel_models/src/query/user/sample_data.rs
@@ -12,9 +12,11 @@ use crate::schema_v2::{
pay... | 2024-10-11T13:39:20Z |
## Description
<!-- Describe your changes in detail -->
I've extended the interface for `BatchSampleDataInterface` to with `insert_disputes_batch_for_sample_data` and `delete_disputes_for_sample_data`, and added implementation to all structs implementing this trait. I've also modified `generate_sample_data` function... | 53e82c3faef3ee629a38180e3882a2920332a9a8 |
Manual test is done, screenshots are provided in the comment section of this issue: https://github.com/juspay/hyperswitch/issues/6111
| [
"crates/diesel_models/src/query/user/sample_data.rs",
"crates/router/src/db/kafka_store.rs",
"crates/router/src/db/user/sample_data.rs",
"crates/router/src/services/kafka.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-6290 | Bug: [DOCS]: Add `X-Merchant-Id` to headers in Profile endpoints for v2
### Description
We require `X-Merchant-Id` in the headers for the following endpoints in Profile:
- Profile - Create
- Profile - Update
- Profile - Retrieve
- Merchant Connector - List
We need to update the v2 API documentation. | diff --git a/api-reference-v2/openapi_spec.json b/api-reference-v2/openapi_spec.json
index 3f57faaf1d7..46c4868e4bd 100644
--- a/api-reference-v2/openapi_spec.json
+++ b/api-reference-v2/openapi_spec.json
@@ -711,6 +711,20 @@
"summary": "Profile - Create",
"description": "Creates a new *profile* for a... | 2024-10-11T09:36:55Z |
## Description
<!-- Describe your changes in detail -->
Add X-Merchant-Id to headers in Profile endpoints 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 have an issue, we'd recommend start... | 19a8474d8731ed7149b541f02ad237e30c4c9f24 | [
"api-reference-v2/openapi_spec.json",
"crates/openapi/src/routes/profile.rs"
] | ||
juspay/hyperswitch | juspay__hyperswitch-2438 | Bug: [FEATURE] Implement `MerchantAccountInterface` for `MockDb`
Spin off from #172. Refer to the parent issue for more information | diff --git a/crates/diesel_models/src/merchant_account.rs b/crates/diesel_models/src/merchant_account.rs
index b1dcc1d3476..12d51311e87 100644
--- a/crates/diesel_models/src/merchant_account.rs
+++ b/crates/diesel_models/src/merchant_account.rs
@@ -260,6 +260,36 @@ pub struct MerchantAccountUpdateInternal {
pub re... | 2024-10-10T01:07:03Z |
## Description
<!-- Describe your changes in detail -->
Mockdb is a stub to avoid costly interactions with db during testing. This PR powers mockdb to have [MerchantAccountInterface](https://github.com/juspay/hyperswitch/blob/3d70b1a31703c5316183adaa9312a38e598fce01/crates/router/src/db/merchant_account.rs#L26) for ... | 33bc83fce47c579457f1b9be0a91bb4fa13585ff | [
"crates/diesel_models/src/merchant_account.rs",
"crates/hyperswitch_domain_models/src/merchant_account.rs",
"crates/router/src/db/merchant_account.rs",
"docker-compose-development.yml"
] | ||
juspay/hyperswitch | juspay__hyperswitch-6097 | Bug: [REFACTOR]: [TSYS] Add amount conversion framework to Tsys
### :memo: Feature Description
Currently, amounts are represented as `i64` values throughout the application. We want to introduce a `Unit` struct that explicitly states the denomination. A new type, `MinorUnit`, has been added to standardize the flo... | diff --git a/crates/hyperswitch_connectors/src/connectors/tsys.rs b/crates/hyperswitch_connectors/src/connectors/tsys.rs
index ec53a99316f..25b47981def 100644
--- a/crates/hyperswitch_connectors/src/connectors/tsys.rs
+++ b/crates/hyperswitch_connectors/src/connectors/tsys.rs
@@ -1,12 +1,11 @@
pub mod transformers;
... | 2024-10-09T22:18:50Z |
## Description
added `StringMajorUnit` for amount conversion
## 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 implem... | 3d1a3cdc8f942a3dca2e6a200bf9200366bd62f1 | [
"crates/hyperswitch_connectors/src/connectors/tsys.rs",
"crates/hyperswitch_connectors/src/connectors/tsys/transformers.rs",
"crates/router/src/types/api.rs",
"crates/router/tests/connectors/tsys.rs"
] | ||
juspay/hyperswitch | juspay__hyperswitch-6092 | Bug: [REFACTOR]: [MOLLIE] Add amount conversion framework to Mollie
### :memo: Feature Description
Currently, amounts are represented as `i64` values throughout the application. We want to introduce a `Unit` struct that explicitly states the denomination. A new type, `MinorUnit`, has been added to standardize the... | diff --git a/crates/hyperswitch_connectors/src/connectors/mollie.rs b/crates/hyperswitch_connectors/src/connectors/mollie.rs
index 5066fb422fa..010ae90c56f 100644
--- a/crates/hyperswitch_connectors/src/connectors/mollie.rs
+++ b/crates/hyperswitch_connectors/src/connectors/mollie.rs
@@ -1,12 +1,11 @@
pub mod transfor... | 2024-10-09T18:52:03Z |
## Description
<!-- Describe your changes in detail -->
This PR do amount conversion changes for Mollie Connector and it accepts the amount in StringMajorUnit
## 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.
... | edd099886da9c46800a646fe809796a08eb78c99 | [
"crates/hyperswitch_connectors/src/connectors/mollie.rs",
"crates/hyperswitch_connectors/src/connectors/mollie/transformers.rs",
"crates/router/src/types/api.rs",
"crates/router/tests/connectors/mollie.rs"
] | ||
juspay/hyperswitch | juspay__hyperswitch-6237 | Bug: [REFACTOR]: (merchant_account_v2) move `organization_id` from request body to `headers`
When creating the merchant account, the request body is
```json
{
"merchant_name": "cloth_seller",
"organization_id": "org_tdhdTbv3z85XtxXGgVHS"
}
```
Here `organization_id` is the hierarchy_id / lineage id... | diff --git a/api-reference-v2/openapi_spec.json b/api-reference-v2/openapi_spec.json
index bd9de3a2962..9a406e9c733 100644
--- a/api-reference-v2/openapi_spec.json
+++ b/api-reference-v2/openapi_spec.json
@@ -453,6 +453,20 @@
"summary": "Merchant Account - Create",
"description": "Create a new account... | 2024-10-09T13:08:17Z |
## Description
<!-- Describe your changes in detail -->
For create_merchant request organization_id is currently being passed in request body. Moved it to request header
## Motivation and Context
<!--
Why is this change required? What problem does it solve?
If it fixes an open issue, please link to the issue ... | c3b0f7c1d6ad95034535048aa50ff6abe9ed6aa0 |
1a. Correct Request
```
curl --location 'http://localhost:8080/v2/merchant_accounts' \
--header 'X-Organization-Id: org_55QZkS5H9AR8deTk9mRs' \
--header 'Content-Type: application/json' \
--header 'api-key: test_admin' \
--data '{
"merchant_name": "Cloth Seller Person"
}'
```
1b. Response
```... | [
"api-reference-v2/openapi_spec.json",
"crates/api_models/src/admin.rs",
"crates/common_utils/src/id_type/organization.rs",
"crates/openapi/src/openapi_v2.rs",
"crates/openapi/src/routes/merchant_account.rs",
"crates/router/src/lib.rs",
"crates/router/src/routes/admin.rs",
"crates/router/src/services/a... | |
juspay/hyperswitch | juspay__hyperswitch-6248 | Bug: [FEATURE]:[BILLWERK] Move connector code to hyperswitch_connectors
Connector code for Billwerk needs to be moved from crate router to new crate hyperswitch_connectors | diff --git a/crates/hyperswitch_connectors/src/connectors.rs b/crates/hyperswitch_connectors/src/connectors.rs
index e5eaa22795a..ddd9fa861a6 100644
--- a/crates/hyperswitch_connectors/src/connectors.rs
+++ b/crates/hyperswitch_connectors/src/connectors.rs
@@ -1,4 +1,5 @@
pub mod bambora;
+pub mod billwerk;
pub mod b... | 2024-10-08T09:30:53Z |
## Description
<!-- Describe your changes in detail -->
Moved connector Billwerk from Router to HyperswitchConnector Trait
## 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 recom... | 962afbd084458e9afb11a0278a8210edd9226a3d | 1. Create Merchant Account
```
curl --location 'http://localhost:8080/payments/pay_hY1WhQcAhKsQZehh2piy' \
--header 'Accept: application/json' \
--header 'api-key: ___'
```
2. Create API Key
```
curl --location 'http://localhost:8080/api_keys/merchant_1728387984' \
--header 'Content-Type: application/json' \
... | [
"crates/hyperswitch_connectors/src/connectors.rs",
"crates/router/src/connector/billwerk.rs",
"crates/router/src/connector/billwerk/transformers.rs",
"crates/hyperswitch_connectors/src/default_implementations.rs",
"crates/hyperswitch_connectors/src/default_implementations_v2.rs",
"crates/router/src/connec... | |
juspay/hyperswitch | juspay__hyperswitch-6421 | Bug: feat(routing): add invalidate window as a service for SR based routing
add invalidate window as a service for SR based routing | diff --git a/config/development.toml b/config/development.toml
index 8f3ffdbcbb5..5a6a1250637 100644
--- a/config/development.toml
+++ b/config/development.toml
@@ -775,3 +775,7 @@ card_networks = "Visa, AmericanExpress, Mastercard"
[network_tokenization_supported_connectors]
connector_list = "cybersource"
+
+[grpc... | 2024-10-08T09:02:03Z |
## Description
add invalidate window as a service for SR based 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 with one first so the PR
can focus o... | f56d76ffec7ef6c27417a5df1999af7ccc3f1545 | - Hit the route, to update the config
```
curl --location --request PATCH 'http://localhost:8080/account/merchant_1730123706/business_profile/pro_TtvgDfAdgudrReoeeUJb/dynamic_routing/success_based/config/routing_lmPpwoTevEaYMVogesHs' \
--header 'Content-Type: application/json' \
--header 'api-key: test_admin' \
... | [
"config/development.toml",
"crates/external_services/src/grpc_client/dynamic_routing.rs",
"crates/router/src/core/routing.rs",
"crates/router/src/routes/app.rs",
"crates/router/src/routes/routing.rs",
"proto/success_rate.proto"
] | |
juspay/hyperswitch | juspay__hyperswitch-6265 | Bug: [FEATURE]: [FORTE, NEXINETS, PAYEEZY, PAYU, ZEN] Move connector code to crate hyperswitch_connectors
### Feature Description
Connector code for forte, nexinets, payeexy, payu and zen needs to be moved from crate router to new crate hyperswitch_connectors
### Possible Implementation
Connector code for f... | diff --git a/Cargo.lock b/Cargo.lock
index 347d4e58797..9ccedba3c39 100644
--- a/Cargo.lock
+++ b/Cargo.lock
@@ -3997,6 +3997,7 @@ dependencies = [
"hyperswitch_interfaces",
"image",
"masking",
+ "mime",
"once_cell",
"qrcode",
"rand",
diff --git a/crates/common_utils/src/consts.rs b/crates/common_utils/src/... | 2024-10-08T08:03:24Z |
## Description
<!-- Describe your changes in detail -->
Moved connectors Forte, Nexinets, Payeezy, Payu and Zen from Router to HyperswitchConnector Trait
## 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 ... | f3a869ea9a430f3b5177852fb74d0910dc8fbe17 | Forte :
1. Create Merchant Account
```
curl --location 'http://localhost:8080/accounts' \
--header 'Content-Type: application/json' \
--header 'Accept: application/json' \
--header 'api-key: {}' \
--data-raw '{
"merchant_id": "merchant_1728385434",
"locker_id": "m0010",
"merchant_name": "NewAge R... | [
"Cargo.lock",
"crates/common_utils/src/consts.rs",
"crates/hyperswitch_connectors/Cargo.toml",
"crates/hyperswitch_connectors/src/connectors.rs",
"crates/router/src/connector/forte.rs",
"crates/router/src/connector/forte/transformers.rs",
"crates/router/src/connector/nexinets.rs",
"crates/router/src/c... | |
juspay/hyperswitch | juspay__hyperswitch-6258 | Bug: Add support for Samsung pay app token flow
Samsung pay provide token in different format for web and app. Hence both of the formates needs to be handled in confirm call. | diff --git a/api-reference-v2/openapi_spec.json b/api-reference-v2/openapi_spec.json
index 44ac1d3e08d..13d0cc87ccf 100644
--- a/api-reference-v2/openapi_spec.json
+++ b/api-reference-v2/openapi_spec.json
@@ -18929,6 +18929,61 @@
"FORMAT_TOTAL_ESTIMATED_AMOUNT"
]
},
+ "SamsungPayAppWalle... | 2024-10-08T04:15:32Z |
## Description
<!-- Describe your changes in detail -->
Samsung pay provide token in different format for web and app. Hence both of the formates needs to be handled in confirm call.
## Motivation and Context
<!--
Why is this change required? What problem does it solve?
If it fixes an open issue, please link ... | edd099886da9c46800a646fe809796a08eb78c99 |
-> Create merchant connector account with samsung pay enabled
-> Create a payment
```
curl --location 'http://localhost:8080/payments' \
--header 'Content-Type: application/json' \
--header 'Accept: application/json' \
--header 'api-key:' \
--data '{
"amount": 100000,
"currency": "USD",
"capture_metho... | [
"api-reference-v2/openapi_spec.json",
"crates/api_models/src/payments.rs",
"crates/common_enums/src/enums.rs",
"crates/hyperswitch_domain_models/src/payment_method_data.rs",
"crates/openapi/src/openapi.rs",
"crates/openapi/src/openapi_v2.rs",
"crates/router/src/connector/cybersource/transformers.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-6254 | Bug: fix(users): Accepting invite for org_admins
Currently, when email feature flag is enabled and invite a org_admin, it throws error saying `InvalidRoleId`.
When we try to accept invite for `org_admin`s, it again throws `InvalidRoleId`.
This should not be the case, error should not be throws and invite should be... | diff --git a/crates/diesel_models/src/query/user_role.rs b/crates/diesel_models/src/query/user_role.rs
index f4142842e21..5ef09715211 100644
--- a/crates/diesel_models/src/query/user_role.rs
+++ b/crates/diesel_models/src/query/user_role.rs
@@ -119,7 +119,7 @@ impl UserRole {
conn: &PgPooledConn,
user... | 2024-10-07T15:00:50Z |
## Description
<!-- Describe your changes in detail -->
Currently accepting invites for org_admin will not work. This PR fixes it.
## 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... | b79f75a7ab9ed63a75defa2b3c5f9c170fca493e |
```
curl 'http://localhost:8080/user/accept_invite_from_email' \
-H 'authorization: Bearer SPT with accept_invite_from_email' \
--data-raw '{"token":"email token"}'
```
Response:
```json
{
"token": "JWT",
"token_type": "user_info"
}
```
| [
"crates/diesel_models/src/query/user_role.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/utils/user_role.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-6122 | Bug: [REFACTOR]: [SHIFT4] Add amount conversion framework to Shift4
### :memo: Feature Description
Currently, amounts are represented as `i64` values throughout the application. We want to introduce a `Unit` struct that explicitly states the denomination. A new type, `MinorUnit`, has been added to standardize the... | diff --git a/crates/router/src/connector/shift4.rs b/crates/router/src/connector/shift4.rs
index 895487db3ba..08c23bc5710 100644
--- a/crates/router/src/connector/shift4.rs
+++ b/crates/router/src/connector/shift4.rs
@@ -1,8 +1,10 @@
pub mod transformers;
-use std::fmt::Debug;
-
-use common_utils::{ext_traits::ByteS... | 2024-10-07T11:52:12Z |
## Description
This PR adds amount conversion framework to Shift4, for sending to connector.
Resolves #6122
## 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 ... | 3d1a3cdc8f942a3dca2e6a200bf9200366bd62f1 | [
"crates/router/src/connector/shift4.rs",
"crates/router/src/connector/shift4/transformers.rs",
"crates/router/src/types/api.rs",
"crates/router/tests/connectors/shift4.rs"
] | ||
juspay/hyperswitch | juspay__hyperswitch-6249 | Bug: fix(users): max attempts for two-fa
- Previously, there was no limit on the number of failed attempts for TOTP and recovery code. With this PR, a maximum of 4 wrong attempts is introduced for both TOTP and recovery code. After 4 failed attempts, a cooldown period of 5 minutes applies for TOTP, and 10 minutes fo... | diff --git a/crates/api_models/src/events/user.rs b/crates/api_models/src/events/user.rs
index bb61a025180..4dc2a1a301a 100644
--- a/crates/api_models/src/events/user.rs
+++ b/crates/api_models/src/events/user.rs
@@ -18,8 +18,9 @@ use crate::user::{
ResetPasswordRequest, RotatePasswordRequest, SendVerifyEmailReque... | 2024-10-07T10:19:31Z |
## Description
<!-- Describe your changes in detail -->
- Previously, there was no limit on the number of failed attempts for TOTP and recovery code. With this PR, a maximum of 4 wrong attempts is introduced for both TOTP and recovery code. After 4 failed attempts, a cooldown period of 5 minutes applies for TOTP, an... | 55a97cc952aedd67451ed3785792e00d74f357ff |
Request :
```
curl --location 'http://localhost:8080/user/2fa/v2' \
--header 'Authorization: Bearer JWT'
```
Response:
- If the user has not set twofa
```
{
"status": null
}
```
- If the user has twofa set and no attempts is remaining for both recovery code and totp
```
{
"status": {
... | [
"crates/api_models/src/events/user.rs",
"crates/api_models/src/user.rs",
"crates/router/src/consts/user.rs",
"crates/router/src/core/errors/user.rs",
"crates/router/src/core/user.rs",
"crates/router/src/routes/app.rs",
"crates/router/src/routes/user.rs",
"crates/router/src/utils/user/two_factor_auth.r... | |
juspay/hyperswitch | juspay__hyperswitch-6260 | Bug: Add support for network transaction id and card details based MIT
Support needs to be added in order to accept the card details and network transaction id in `recurring_details` for an MIT. This will be only in the Sever-to-Server call where the customer is off_session and merchant is initiating the transaction... | diff --git a/api-reference-v2/openapi_spec.json b/api-reference-v2/openapi_spec.json
index 44ac1d3e08d..99055a2c6b5 100644
--- a/api-reference-v2/openapi_spec.json
+++ b/api-reference-v2/openapi_spec.json
@@ -10093,6 +10093,77 @@
}
}
},
+ "NetworkTransactionIdAndCardDetails": {
+ ... | 2024-10-07T04:35:39Z |
## Description
<!-- Describe your changes in detail -->
Support needs to be added in order to accept the card details and network transaction id in `recurring_details` for an MIT. This will be only in the Sever-to-Server call where the customer is off_session and merchant is initiating the transaction who is a PCI... | e911ea4615294d136210bcf9a8bd4b3ab39ca85f |
-> Create the cybersource connector
-> Make a payment
```
curl --location 'http://localhost:8080/payments' \
--header 'Content-Type: application/json' \
--header 'Accept: application/json' \
--header 'api-key: dev_tsD2yHJdXXW6s9EMzxgsDgJiJbQEzCLt0l0ysqlOc0tV9F1CACTCTWdHOdtJcoYs' \
--data-raw '{
"amount": ... | [
"api-reference-v2/openapi_spec.json",
"crates/api_models/src/mandates.rs",
"crates/api_models/src/payments.rs",
"crates/hyperswitch_connectors/src/connectors/bambora/transformers.rs",
"crates/hyperswitch_connectors/src/connectors/cryptopay/transformers.rs",
"crates/hyperswitch_connectors/src/connectors/dl... | |
juspay/hyperswitch | juspay__hyperswitch-6242 | Bug: [BUG] Broken links to Running additional services
### Bug Description
These lines:
- https://github.com/juspay/hyperswitch/blob/b7139483bb4735b7dfaf7e659ab33a16a90af1db/README.md?plain=1#L137,
- https://github.com/juspay/hyperswitch/blob/b7139483bb4735b7dfaf7e659ab33a16a90af1db/docs/try_local_system.md?pla... | diff --git a/README.md b/README.md
index 0428ff38694..f5c27411b51 100644
--- a/README.md
+++ b/README.md
@@ -134,7 +134,7 @@ setup, which includes the [scheduler and monitoring services][docker-compose-sch
[website-link]: https://hyperswitch.io/
[learning-resources]: https://docs.hyperswitch.io/learn-more/payment-flo... | 2024-10-06T11:24:54Z |
## Description
<!-- Describe your changes in detail -->
Changed the links to point to:
https://github.com/juspay/hyperswitch/blob/main/docs/try_local_system.md#running-additional-services
## Motivation and Context
<!--
Why is this change required? What problem does it solve?
If it fixes an open issue, please... | b7139483bb4735b7dfaf7e659ab33a16a90af1db |
Manually checked the links.
| [
"README.md"
] | |
juspay/hyperswitch | juspay__hyperswitch-5914 | Bug: [CYPRESS_FRAMEWORK] Run Cypress tests in parallel
**Description:**
Cypress tests are resource intensive and consume a lot of memory and power. But that should not stop us from running them in parallel even if they consume a lot of resources.
At present, Cypress tests here at Hyperswitch is run in sequential... | diff --git a/scripts/execute_cypress.sh b/scripts/execute_cypress.sh
new file mode 100755
index 00000000000..1f1219ee717
--- /dev/null
+++ b/scripts/execute_cypress.sh
@@ -0,0 +1,188 @@
+#! /usr/bin/env bash
+
+set -euo pipefail
+
+# Initialize tmp_file globally
+tmp_file=""
+
+# Define arrays for services, etc.
+# Rea... | 2024-10-04T09:33:14Z |
## Description
<!-- Describe your changes in detail -->
This PR makes it possible for us to run Cypress tests in parallel by leveraging `gnu-parallel`.
At present, we'll only be running against 5 connectors namely,
- payments: bluesnap, cybersource, stripe
- payouts: adyen and wise
w.r.t pml and other connec... | d06d19fc96e1a74d20e2fe3613f86d541947e0ae |
Tested locally:
These are known failures.
<img width="576" alt="image" src="https://github.com/user-attachments/assets/12788d3f-f816-4395-9799-316546595823">
The ones that passed is `Stripe` and hence it is not in `failed_connector` list.
https://github.com/juspay/hyperswitch/actions/runs/11177572035/jo... | [
"scripts/execute_cypress.sh"
] | |
juspay/hyperswitch | juspay__hyperswitch-6222 | Bug: bug(user_roles): Restrict updating user_roles to the same entity level
Currently update user role API allows updating a merchant level user role to profile level, which should not be possible.
This comes under upgrade/downgrade functionality, which is not available yet.
| diff --git a/crates/router/src/core/user_role.rs b/crates/router/src/core/user_role.rs
index e10fa0eb81c..f2e9f758158 100644
--- a/crates/router/src/core/user_role.rs
+++ b/crates/router/src/core/user_role.rs
@@ -151,6 +151,14 @@ pub async fn update_user_role(
));
}
+ if role_info.get_ent... | 2024-10-04T08:16:42Z |
## Description
<!-- Describe your changes in detail -->
- Currently update user role API allows updating a merchant level user role to profile level, which should not be possible.
## Motivation and Context
<!--
Why is this change required? What problem does it solve?
If it fixes an open issue, please link to ... | a3c2694943a985d27b5bc8b0371884d17a6ca34d |
```curl
curl --location 'http://localhost:8080/user/user/update_role' \
--header 'Authorization: JWT' \
--data-raw '{
"email": "merchant level user email",
"role_id": "profile_admin"
}'
```
This call should throw the following error.
```json
{
"error": {
"type": "invalid_request",
... | [
"crates/router/src/core/user_role.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-6216 | Bug: [BUG] Docker Compose dev environment fails to setup hyperswitch-server
### Bug Description
`hyperswitch-hyperswitch-server-1` container stops abruptly without spinning up the server. Container can't find `protobuf-compiler` debian package and fails. Below are the logs of the container
```shell
➜ hyperswitc... | diff --git a/docker-compose-development.yml b/docker-compose-development.yml
index cf12982a9bd..3878f880b06 100644
--- a/docker-compose-development.yml
+++ b/docker-compose-development.yml
@@ -59,10 +59,12 @@ services:
### Application services
hyperswitch-server:
- image: rust:latest
- command: |
- a... | 2024-10-04T02:40:48Z |
## Description
<!-- Describe your changes in detail -->
Fixes: https://github.com/juspay/hyperswitch/issues/6216
Builds a docker image with protobuf for hyperswitch-server.
## Motivation and Context
<!--
Why is this change required? What problem does it solve?
If it fixes an open issue, please link to the ... | a3c2694943a985d27b5bc8b0371884d17a6ca34d |
docker compose --file docker-compose-development.yml up -d
| [
"docker-compose-development.yml"
] | |
juspay/hyperswitch | juspay__hyperswitch-6014 | Bug: [BUG] Add reference to Sepa Bank Transfer Next Customer Actions Responses
### Bug Description
Sepa bank transfer payment responses don't contain reference for the payment.
A reference is very important unique id for the payment reconciliation by the connectors. e.g. Stripe does create a payment reference ... | diff --git a/api-reference-v2/openapi_spec.json b/api-reference-v2/openapi_spec.json
index fb679970f3d..c554245b936 100644
--- a/api-reference-v2/openapi_spec.json
+++ b/api-reference-v2/openapi_spec.json
@@ -18325,7 +18325,8 @@
"account_holder_name",
"bic",
"country",
- "iban"... | 2024-10-03T13:51:09Z |
## Description
<!-- Describe your changes in detail -->
'reference' added in sepa_bank_instructions, for Stripe Sepa Bank Transfer
## 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, ... | a3c2694943a985d27b5bc8b0371884d17a6ca34d |
Request
~~~
curl --location 'http://localhost:8080/payments' \
--header 'Content-Type: application/json' \
--header 'Accept: application/json' \
--header 'api-key: <apiKey>' \
--data-raw '{
"amount": 60,
"authentication_type": "no_three_ds",
"confirm": true,
"currency": "EUR",
"customer_id": "S... | [
"api-reference-v2/openapi_spec.json",
"crates/api_models/src/payments.rs",
"crates/router/src/connector/stripe/transformers.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-6213 | Bug: Payment method delete API for v2
| diff --git a/crates/hyperswitch_domain_models/src/payment_methods.rs b/crates/hyperswitch_domain_models/src/payment_methods.rs
index af3c657c34a..445ad5ab800 100644
--- a/crates/hyperswitch_domain_models/src/payment_methods.rs
+++ b/crates/hyperswitch_domain_models/src/payment_methods.rs
@@ -14,6 +14,20 @@ use time::Pr... | 2024-10-03T11:11:50Z |
## Description
<!-- Describe your changes in detail -->
- Payment method delete API 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 have an issue, we'd recommend starting with one first s... | edd099886da9c46800a646fe809796a08eb78c99 |
Cannot be tested as vault dev is incomplete.
| [
"crates/hyperswitch_domain_models/src/payment_methods.rs",
"crates/router/src/consts.rs",
"crates/router/src/core/payment_methods.rs",
"crates/router/src/core/payment_methods/cards.rs",
"crates/router/src/core/payment_methods/vault.rs",
"crates/router/src/routes/app.rs",
"crates/router/src/routes/paymen... | |
juspay/hyperswitch | juspay__hyperswitch-6205 | Bug: [FIX] batch encrypt decrypt for mca fetch/insert/update
This adds batch encryption/decryption support for fetch/insert/update of the Merchant Connector Account. | diff --git a/crates/hyperswitch_domain_models/src/merchant_connector_account.rs b/crates/hyperswitch_domain_models/src/merchant_connector_account.rs
index a281c553a13..66b98389818 100644
--- a/crates/hyperswitch_domain_models/src/merchant_connector_account.rs
+++ b/crates/hyperswitch_domain_models/src/merchant_connecto... | 2024-10-03T07:30:06Z |
## Description
<!-- Describe your changes in detail -->
This adds batch encrypt/decrypt support for Merchant Connector account create/fetch/update
## 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... | a3c2694943a985d27b5bc8b0371884d17a6ca34d |
1. Create MerchantConnector Account
```bash
{
"connector_type": "fiz_operations",
"connector_name": "checkout_test",
"connector_label": "checkout_test_US_default",
"merchant_connector_id": "mca_1nx2lpMSrHoJZ0Xiw3CM",
"profile_id": "pro_1tS3symGpqUT5zGglYyI",
"connector_account_details"... | [
"crates/hyperswitch_domain_models/src/merchant_connector_account.rs",
"crates/router/src/core/admin.rs",
"crates/router/src/core/payments/helpers.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-5961 | Bug: [REFACTOR]: [PAYU] Add amount conversion framework to Payu
### :memo: Feature Description
Currently, amounts are represented as `i64` values throughout the application. We want to introduce a `Unit` struct that explicitly states the denomination. A new type, `MinorUnit`, has been added to standardize the flo... | diff --git a/crates/hyperswitch_connectors/src/connectors/payu.rs b/crates/hyperswitch_connectors/src/connectors/payu.rs
index 05f983b8fbb..ad2479f19e4 100644
--- a/crates/hyperswitch_connectors/src/connectors/payu.rs
+++ b/crates/hyperswitch_connectors/src/connectors/payu.rs
@@ -6,6 +6,7 @@ use common_utils::{
er... | 2024-10-02T14:12:09Z |
## Description
This PR adds amount conversion framework to payu, for sending to connector.
fixes #5961
## 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 wi... | a3ea62f88524a360b666cacfbc1cf239f6be8797 | [
"crates/hyperswitch_connectors/src/connectors/payu.rs",
"crates/hyperswitch_connectors/src/connectors/payu/transformers.rs",
"crates/router/src/types/api.rs",
"crates/router/tests/connectors/payu.rs"
] | ||
juspay/hyperswitch | juspay__hyperswitch-5913 | Bug: [CYPRESS_FRAMEWORK] Re-use config update commands
**Description:**
Cypress is the testing framework that Hyperswitch uses to run automated tests. Having good grip on Javascript to work on Cypress is a must.
Cypress makes use of custom [commands](https://github.com/juspay/hyperswitch/blob/main/cypress-te... | 2024-10-02T12:55:09Z |
## Description
This PR refactors the existing Cypress commands used for configuration updates (autoRetryConfig, setMaxAutoRetries, and stepUp) into a single unified command cy.updateConfig. The refactor helps reduce redundancy in the codebase by consolidating multiple similar implementations into one versatile comman... | 19a8474d8731ed7149b541f02ad237e30c4c9f24 | Tested manually and with cypress command.
| [] | ||
juspay/hyperswitch | juspay__hyperswitch-5917 | Bug: [FIX] Add Limit Parameter to User Role List for Org Function
### Feature Description
Description: The function [generic_user_roles_list_for_org_and_extra](https://github.com/juspay/hyperswitch/blob/a94cf25bb6eb40fafc5327aceffac8292b47b001/crates/diesel_models/src/query/user_role.rs#L270) currently fetches al... | diff --git a/crates/diesel_models/src/query/user_role.rs b/crates/diesel_models/src/query/user_role.rs
index 5ef09715211..2496d22447e 100644
--- a/crates/diesel_models/src/query/user_role.rs
+++ b/crates/diesel_models/src/query/user_role.rs
@@ -258,6 +258,7 @@ impl UserRole {
merchant_id: Option<id_type::Merch... | 2024-10-01T16:00:18Z |
## Description
<!-- Describe your changes in detail -->
This PR adds the `limit` parameter to the `generic_user_roles_list_for_org_and_extra` function.
## Motivation and Context
<!--
Why is this change required? What problem does it solve?
If it fixes an open issue, please link to the issue here.
If you do... | 19a8474d8731ed7149b541f02ad237e30c4c9f24 |
When having 5a1d2b3633e4fc8862f61bed9b5810eac2a313cb in:
```shell
curl 'http://localhost:8080/user/user/v2/list' \
-H 'authorization: Bearer JWT' \
```
yields
```
[{"email":"email1@gmail.com","roles":[{"role_id":"org_admin","role_name":"organization_admin"}]}]
```
**Outdated** by 5a1d2b3633e4fc8862f61b... | [
"crates/diesel_models/src/query/user_role.rs",
"crates/router/src/core/user_role.rs",
"crates/router/src/db/user_role.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-5915 | Bug: [CYPRESS_FRAMEWORK] Verify URL after redirection
**Description:**
Cypress is the testing framework that Hyperswitch uses to run automated tests as it helps test both backend as well as frontend in a single shot that includes redirection flows like `3ds` and `bank redirect`.
Redirection tests in Cypress ... | 2024-10-01T10:33:37Z |
## Description
This PR refactors the verifyReturnUrl function to validate the redirection_url and ensure that the payment status is either succeeded or processing. If the status is invalid, the test will now fail, preventing false positives in redirection tests like 3DS or bank redirects.
###Key Changes:
- Pars... | d8d8c400bbda49b9a0cd5edbe37e929ae6d38eb4 | Ran against Integ environment for Stripe:
<img width="555" alt="image" src="https://github.com/user-attachments/assets/0dc3fb11-4f2c-4731-9f23-8a3a0dc9ab94" />
when the validation fails, below is the kind of error we get:
<img width="551" alt="image" src="https://github.com/user-attachments/assets/e15418f2-ad9... | [] | ||
juspay/hyperswitch | juspay__hyperswitch-6186 | Bug: feat(users): Allow multiple org_admins in single org
Currently, there can only be a single org_admin in a org, and that is the person who signed up.
All the other users will be either merchant level or profile level.
Since, there can be a usecase where a org needs multiple org admins, we should allow multiple... | diff --git a/crates/diesel_models/src/query/user_role.rs b/crates/diesel_models/src/query/user_role.rs
index 1cd25e54cb3..f4142842e21 100644
--- a/crates/diesel_models/src/query/user_role.rs
+++ b/crates/diesel_models/src/query/user_role.rs
@@ -5,7 +5,6 @@ use diesel::{
BoolExpressionMethods, ExpressionMethods, Qu... | 2024-10-01T10:27:33Z |
## Description
<!-- Describe your changes in detail -->
Currently we are inserting user_roles in v1 version and v2 version. Since we have completely moved the APIs to support v2, we don't have to insert v1 anymore.
Allow inviting, updating and deleting org_admins.
## Motivation and Context
<!--
Why is this ... | 4dae29221f2d24a0f4299e641cfe22ab705fae25 |
All the following APIs will insert only v2 user_roles from now on.
```curl
curl --location 'https://integ-api.hyperswitch.io/user/signup' \
--header 'Content-Type: application/json' \
--data-raw '{
"email": "new email",
"password": "password"
}'
```
```
curl --location 'https://integ-api.hyperswit... | [
"crates/diesel_models/src/query/user_role.rs",
"crates/router/src/core/user.rs",
"crates/router/src/db/kafka_store.rs",
"crates/router/src/db/user_role.rs",
"crates/router/src/services/authorization/roles/predefined_roles.rs",
"crates/router/src/types/domain/user.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-6184 | Bug: refactor(users): Remove v1 insertions for user_roles
Currently, we are inserting user_roles in v1 version and v2 version.
Since we moved all the APIs to work with v2 data, we can stop inserting v1 data.
This will also help in migrating v1 data to v2. | diff --git a/crates/diesel_models/src/query/user_role.rs b/crates/diesel_models/src/query/user_role.rs
index 1cd25e54cb3..f4142842e21 100644
--- a/crates/diesel_models/src/query/user_role.rs
+++ b/crates/diesel_models/src/query/user_role.rs
@@ -5,7 +5,6 @@ use diesel::{
BoolExpressionMethods, ExpressionMethods, Qu... | 2024-10-01T10:27:33Z |
## Description
<!-- Describe your changes in detail -->
Currently we are inserting user_roles in v1 version and v2 version. Since we have completely moved the APIs to support v2, we don't have to insert v1 anymore.
Allow inviting, updating and deleting org_admins.
## Motivation and Context
<!--
Why is this ... | 4dae29221f2d24a0f4299e641cfe22ab705fae25 |
All the following APIs will insert only v2 user_roles from now on.
```curl
curl --location 'https://integ-api.hyperswitch.io/user/signup' \
--header 'Content-Type: application/json' \
--data-raw '{
"email": "new email",
"password": "password"
}'
```
```
curl --location 'https://integ-api.hyperswit... | [
"crates/diesel_models/src/query/user_role.rs",
"crates/router/src/core/user.rs",
"crates/router/src/db/kafka_store.rs",
"crates/router/src/db/user_role.rs",
"crates/router/src/services/authorization/roles/predefined_roles.rs",
"crates/router/src/types/domain/user.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-5965 | Bug: [REFACTOR] Update Database Connection Functions for Read Operations
### Feature Description
Currently, in our codebase, we are using `pg_connection_write` for database operations even when performing read operations, which is inefficient. The `pg_connection_write` function should only be used when we need to... | diff --git a/crates/router/src/db/dashboard_metadata.rs b/crates/router/src/db/dashboard_metadata.rs
index f8aee34c49c..742c03dde4a 100644
--- a/crates/router/src/db/dashboard_metadata.rs
+++ b/crates/router/src/db/dashboard_metadata.rs
@@ -99,7 +99,7 @@ impl DashboardMetadataInterface for Store {
org_id: &id_... | 2024-09-30T19:50:45Z |
## Description
This PR refactors the database connection logic by changing the function from `pg_connection_write()` to `pg_connection_read()` for functions that only perform read operations from the database. This is an internal change aimed at optimizing resource usage. All user-facing APIs should continue to funct... | edd099886da9c46800a646fe809796a08eb78c99 | - Verified that all user-related APIs are working without any issues.
- All existing test cases for database read and write operations passed successfully.
- Confirmed that this internal change does not affect the functionality of user-facing APIs.
| [
"crates/router/src/db/dashboard_metadata.rs",
"crates/router/src/db/role.rs",
"crates/router/src/db/user.rs",
"crates/router/src/db/user_role.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-6165 | Bug: [FIX] use batch encryption/decryption for payment intent table
| diff --git a/crates/hyperswitch_domain_models/src/payments/payment_intent.rs b/crates/hyperswitch_domain_models/src/payments/payment_intent.rs
index bd4707243ce..562e5d205c0 100644
--- a/crates/hyperswitch_domain_models/src/payments/payment_intent.rs
+++ b/crates/hyperswitch_domain_models/src/payments/payment_intent.rs... | 2024-09-30T16:08:45Z |
## Description
<!-- Describe your changes in detail -->
Batch Encrypt/Decrypt fields in Payment Intent table
## 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 w... | 6b0f7e4870886997ca300935e727283c739be486 |
### How to test it in deployed environments
Basic sanity testing of `PaymentsCreate` and `PaymentsList`.
### How did I test it locally
1. Call /payments from postman
```bash
curl --location 'http://localhost:8080/payments' \
--header 'Content-Type: application/json' \
--header 'Accept: application/json' \
... | [
"crates/hyperswitch_domain_models/src/payments/payment_intent.rs",
"crates/router/Cargo.toml",
"crates/router/src/core/admin.rs",
"crates/router/src/core/payments/operations/payment_create.rs",
"crates/router/src/services/api.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-6163 | Bug: fix(payments): remove time range filter from payment attempt hotfix
Corresponding issue: https://github.com/juspay/hyperswitch/issues/6160 | diff --git a/crates/diesel_models/src/query/payment_attempt.rs b/crates/diesel_models/src/query/payment_attempt.rs
index 48941330ec6..fa80b0990d1 100644
--- a/crates/diesel_models/src/query/payment_attempt.rs
+++ b/crates/diesel_models/src/query/payment_attempt.rs
@@ -351,7 +351,6 @@ impl PaymentAttempt {
paym... | 2024-09-30T14:44:08Z |
## Description
Corresponding main branch PR: #6159
Currently created_at is not indexed in payment attempt table, when applying filtering with active attempt ids. We are adding extra overhead of checking time_range, though we need not to as we will be already getting filtered attempt ids from intent table.
## M... | 387f02ee273e1bbf50e7b3882f5e9468d59f2c5b | [
"crates/diesel_models/src/query/payment_attempt.rs",
"crates/hyperswitch_domain_models/src/payments/payment_attempt.rs",
"crates/router/src/core/payments.rs",
"crates/router/src/db/kafka_store.rs",
"crates/storage_impl/src/mock_db/payment_attempt.rs",
"crates/storage_impl/src/payments/payment_attempt.rs"
... | ||
juspay/hyperswitch | juspay__hyperswitch-6160 | Bug: fix(payments): remove time range filter from payment attempt
We don't need time range filters since created at is not indexed in payments attempts, we are already getting filtered payments intents and using its active attempt ids. It is further slowing down 'IN' query performance. | diff --git a/crates/diesel_models/src/query/payment_attempt.rs b/crates/diesel_models/src/query/payment_attempt.rs
index e07d716fb6c..ad056aef6d0 100644
--- a/crates/diesel_models/src/query/payment_attempt.rs
+++ b/crates/diesel_models/src/query/payment_attempt.rs
@@ -369,7 +369,6 @@ impl PaymentAttempt {
paym... | 2024-09-30T13:32:34Z |
## Description
Currently `created_at` is not indexed in payment attempt table, when applying filtering with active attempt ids. We are adding extra overhead of checking time_range, though we need not to as we will be already getting filtered attempt ids from intent table.
## Motivation and Context
Closes [#6160]... | e4a35d366b7db151378d6c1f61e4d01d1c7ed37f | We can hit test api
```
curl --location 'http://localhost:8080/payments/list' \
--header 'Content-Type: application/json' \
--header 'Accept: application/json' \
--header 'Authorization: Bearer JWT' \
--data '{
"limit": 50,
}'
```
| [
"crates/diesel_models/src/query/payment_attempt.rs",
"crates/hyperswitch_domain_models/src/payments/payment_attempt.rs",
"crates/router/src/core/payments.rs",
"crates/router/src/db/kafka_store.rs",
"crates/storage_impl/src/mock_db/payment_attempt.rs",
"crates/storage_impl/src/payments/payment_attempt.rs"
... | |
juspay/hyperswitch | juspay__hyperswitch-6157 | Bug: [FEATURE] [DLOCAL, SQUARE] Move connector code to crate hyperswitch_connectors
### Feature Description
Connector code for `dlocal` and `square` needs to be moved from crate `router` to new crate `hyperswitch_connectors`
### Possible Implementation
Connector code for `dlocal` and `square` needs to be mo... | diff --git a/crates/hyperswitch_connectors/src/connectors.rs b/crates/hyperswitch_connectors/src/connectors.rs
index f057b7d4a33..9406353a1ee 100644
--- a/crates/hyperswitch_connectors/src/connectors.rs
+++ b/crates/hyperswitch_connectors/src/connectors.rs
@@ -4,6 +4,7 @@ pub mod cashtocode;
pub mod coinbase;
pub mod... | 2024-09-30T08:36:17Z |
## Description
Move conector Dlocal and Square from router to hyperswitch_connector 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 so th... | dcec2a2bff082b606cc3376e9451d53ed6ecdf04 | 1. Create Merchant Account
```
curl --location 'http://localhost:8080/accounts' \
--header 'Content-Type: application/json' \
--header 'Accept: application/json' \
--header 'api-key: test_admin' \
--data-raw '{
"merchant_id": "merchant_1727684785",
"locker_id": "m0010",
"merchant_name": "NewAge Retailer"... | [
"crates/hyperswitch_connectors/src/connectors.rs",
"crates/router/src/connector/dlocal.rs",
"crates/router/src/connector/dlocal/transformers.rs",
"crates/router/src/connector/square.rs",
"crates/router/src/connector/square/transformers.rs",
"crates/hyperswitch_connectors/src/constants.rs",
"crates/hyper... | |
juspay/hyperswitch | juspay__hyperswitch-6146 | Bug: fix(user_roles): Send only same and below Entity Level Users in List Users API
Currently in user list api, for merchants we show org admin.
This is happening because in V1 data, we have merchant_id in org level users as well, because of why the filtering is not correct. | diff --git a/crates/router/src/core/user_role.rs b/crates/router/src/core/user_role.rs
index b841f88eca1..e10fa0eb81c 100644
--- a/crates/router/src/core/user_role.rs
+++ b/crates/router/src/core/user_role.rs
@@ -736,6 +736,16 @@ pub async fn list_users_in_lineage(
}
};
+ // This filtering is needed ... | 2024-09-27T11:56:42Z |
## Description
<!-- Describe your changes in detail -->
- Send only same and below Entity Level Users in List Users API.
## 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... | 67d6d2247bb53dc25831d65305269ba6889c99de |
```
curl 'http://localhost:8080/user/user/v2/list' \
-H 'authorization: Bearer JWT' \
```
This API when called with merchant level users, it should not send org level users in response. Can be tested via control center.
| [
"crates/router/src/core/user_role.rs",
"crates/router/src/utils/user_role.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-6141 | Bug: fix(admin): jwt added for organization update and retrieve
Previously, updating and retrieving organization details required authentication using the admin API key. With the recent change, the dashboard JWT can now be used to update the org_name directly through the dashboard. | diff --git a/crates/router/src/routes/admin.rs b/crates/router/src/routes/admin.rs
index e5a18fba536..78238d3af07 100644
--- a/crates/router/src/routes/admin.rs
+++ b/crates/router/src/routes/admin.rs
@@ -39,14 +39,24 @@ pub async fn organization_update(
) -> HttpResponse {
let flow = Flow::OrganizationUpdate;
... | 2024-09-27T07:14:54Z |
## Description
<!-- Describe your changes in detail -->
Previously, updating and retrieving organization details required authentication using the admin API key. With the recent change, the dashboard JWT can now be used to update the org_name directly through the dashboard.
## Motivation and Context
<!--
Why i... | 67d6d2247bb53dc25831d65305269ba6889c99de |
Request :
```
curl --location --request PUT 'http://localhost:8080/organization/${org_id}' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer JWT' \
--data '{
"organization_name":"RiddhiTest3"
}'
```
Response:
```
{
"organization_id": "org_id",
"organization_name... | [
"crates/router/src/routes/admin.rs",
"crates/router/src/services/authentication.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-8556 | Bug: [FEATURE] Add auto retries configs in profile CRUD apis
### Feature Description
Add auto retries configs in profile CRUD apis
1. is_auto_retries_enabled - Boolean (denotes whether auto retries should be performed for a profile)
2. max_auto_retries_enabled - Int (i16) (maximum auto retries to be performed)
##... | diff --git a/crates/api_models/src/admin.rs b/crates/api_models/src/admin.rs
index 6f656339569..6e7f4f29d03 100644
--- a/crates/api_models/src/admin.rs
+++ b/crates/api_models/src/admin.rs
@@ -1971,6 +1971,12 @@ pub struct ProfileCreate {
/// If set to `true` is_network_tokenization_enabled will be checked.
#... | 2024-09-26T17:43:50Z |
## Description
<!-- Describe your changes in detail -->
add auto retries configs in profile CRUD apis
1. is_auto_retries_enabled - Boolean (denotes whether auto retries should be performed for a profile)
2. max_auto_retries_enabled - Int (maximum auto retries to be performed)
closes - https://github.com/juspay/... | 5912936f9f2178f002c96e25636b25f532b1ecb2 |
Tested Manually
1. Profile Create
```
curl --location '{{BASE_URL}}/account/{{MERCHANT_ID}}/business_profile' \
--header 'Content-Type: application/json' \
--header 'api-key: {{ADMIN_API_KEY}}' \
--data '{
"is_auto_retries_enabled": true,
"max_auto_retries_enabled": 1
}'
```
Response
`{
"... | [
"crates/api_models/src/admin.rs",
"crates/diesel_models/src/business_profile.rs",
"crates/diesel_models/src/schema.rs",
"crates/diesel_models/src/schema_v2.rs",
"crates/hyperswitch_domain_models/src/business_profile.rs",
"crates/router/src/core/admin.rs",
"crates/router/src/types/api/admin.rs",
"migra... | |
juspay/hyperswitch | juspay__hyperswitch-6112 | Bug: refactor(users): Deprecate non-profile level user APIs
- Currently there are few APIs in Backend which are not at profile level. For example - Switch merchant.
- We have to remove those APIs.
- If there is any v2 counter part for those APIs, v1 APIs should be modified so that they will work the same way as v1. | diff --git a/crates/api_models/src/events/user.rs b/crates/api_models/src/events/user.rs
index 9b100a7321e..bb61a025180 100644
--- a/crates/api_models/src/events/user.rs
+++ b/crates/api_models/src/events/user.rs
@@ -12,25 +12,16 @@ use crate::user::{
},
AcceptInviteFromEmailRequest, AuthSelectRequest, Author... | 2024-09-26T12:17:17Z |
## Description
<!-- Describe your changes in detail -->
Deletions
- `/user/switch_merchant`
- `/user/switch/list`
- `/user/merchants/list`
- `/user/merchant_select/list`
Modifications
- `/user/user` will work same as `/user/user/v2`
- `/user/user/list` will work same as `/user/user/v2/list`
... | 67d6d2247bb53dc25831d65305269ba6889c99de |
All the below APIs with throw 404.
- `/user/switch_merchant`
- `/user/switch/list`
- `/user/merchants/list`
- `/user/merchant_select/list`
All the below APIs with behave differently.
- `/user/user` will work same as `/user/user/v2`
- `/user/user/list` will work same as `/user/user/v2/list`
- ... | [
"crates/api_models/src/events/user.rs",
"crates/api_models/src/events/user_role.rs",
"crates/api_models/src/user.rs",
"crates/api_models/src/user_role.rs",
"crates/api_models/src/user_role/role.rs",
"crates/router/src/core/user.rs",
"crates/router/src/core/user_role.rs",
"crates/router/src/core/user_r... | |
juspay/hyperswitch | juspay__hyperswitch-6115 | Bug: fix: env added for hyperswitch-web
Added env for hyperswitch-web | diff --git a/docker-compose.yml b/docker-compose.yml
index ef6ff17b5e9..f766ff91053 100644
--- a/docker-compose.yml
+++ b/docker-compose.yml
@@ -162,6 +162,7 @@ services:
- SELF_SERVER_URL=http://localhost:5252
- SDK_ENV=local
- ENV_LOGGING_URL=http://localhost:3103
+ - ENV_BACKEND_URL=http://... | 2024-09-26T12:12:55Z |
## Description
In docker for hyperswitch-web we were facing that it's always pointing to beta.hyperswitch.io as `ENV_BACKEND_URL` was not getting passed.
## 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... | 8049993320e0c103d72dcae0497928ba622d7b59 | Via checking HyperLoader.js file at 9050 port.
| [
"docker-compose.yml"
] | |
juspay/hyperswitch | juspay__hyperswitch-5940 | Bug: [REFACTOR] Move Hardcoded Email Subjects to Constants Across the User Related Files
### Feature Description
In the current implementation, email subjects are hardcoded at multiple places across the codebase when constructing email content. To improve maintainability and avoid magic strings, each unique subje... | diff --git a/crates/router/src/consts.rs b/crates/router/src/consts.rs
index 9e70cb2b96b..728933a4614 100644
--- a/crates/router/src/consts.rs
+++ b/crates/router/src/consts.rs
@@ -86,6 +86,11 @@ pub const EMAIL_TOKEN_TIME_IN_SECS: u64 = 60 * 60 * 24; // 1 day
#[cfg(feature = "email")]
pub const EMAIL_TOKEN_BLACKLIST... | 2024-09-26T11:47:50Z |
## Description
Change the hardcoded email subject to constants
## Motivation and Context
refactor based on this issue - #5940
[link](https://github.com/juspay/hyperswitch/issues/5940)
Closes #5940.
# | 05080259132fb12cdef40a999bd02b6fe2beeeaa | This is an internal change for email subjects.
There should be no affect. All email subjects like magic link, invite should be properly sent as before.
[change_apply_before.txt](https://github.com/user-attachments/files/17147768/change_apply_before.txt)
[change_apply_after.txt](https://github.com/user-attachment... | [
"crates/router/src/consts.rs",
"crates/router/src/consts/user.rs",
"crates/router/src/core/recon.rs",
"crates/router/src/core/user.rs",
"crates/router/src/services/email/types.rs",
"crates/router/src/workflows/api_key_expiry.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-6116 | Bug: [FEATURE] Update worldpay connector's integration
# Storing long connector transaction IDs (\>128 characters)
## Aim
This issue describes the approach for efficiently storing long connector transaction IDs in HyperSwitch application.
## Context
HyperSwitch is integrated with multiple connectors, the... | diff --git a/api-reference-v2/openapi_spec.json b/api-reference-v2/openapi_spec.json
index e16a206b118..5d6d4049dea 100644
--- a/api-reference-v2/openapi_spec.json
+++ b/api-reference-v2/openapi_spec.json
@@ -6018,6 +6018,7 @@
"description": "The three letter ISO currency code in uppercase. Eg: 'USD' for the U... | 2024-09-26T10:48:20Z |
## Description
Described in #6116
## Motivation and Context
Strengthens worldpay connector's integration.
# | 39d89f23b6ae85c4f91a52bb0d970277b43237d8 | Things to test
1. No 3DS payment using auto capture
2. No 3DS payment using manual capture (full amount captures)
3. Refunds
4. Payments Sync
5. Backwards compatibility
Notes
- Refunds cannot be tested as WP relies only on webhooks to update the status to settled (succeeded in HS). Webhook URLs are configure... | [
"api-reference-v2/openapi_spec.json",
"config/deployments/integration_test.toml",
"config/deployments/production.toml",
"config/deployments/sandbox.toml",
"config/development.toml",
"config/docker_compose.toml",
"crates/common_enums/src/enums.rs",
"crates/common_utils/src/consts.rs",
"crates/common_... | |
juspay/hyperswitch | juspay__hyperswitch-6094 | Bug: [FIX] keymanager config if disabled
| diff --git a/config/development.toml b/config/development.toml
index 6e56d5bb14d..a607dd94a16 100644
--- a/config/development.toml
+++ b/config/development.toml
@@ -13,7 +13,7 @@ use_xray_generator = false
bg_metrics_collection_interval_in_secs = 15
[key_manager]
-url = "http://localhost:5000"
+enabled = false
#... | 2024-09-26T07:16:23Z |
## Description
<!-- Describe your changes in detail -->
This fixes unnecessary failure when url and cert for the keymanager is not provided in the config but keymanager is disabled.
## Motivation and Context
<!--
Why is this change required? What problem does it solve?
If it fixes an open issue, please link to... | 962b9978d651e3cc9185b2f6f849c7f255868077 |
This cannot be tested on any environment
| [
"config/development.toml",
"crates/common_utils/src/types/keymanager.rs",
"crates/hyperswitch_domain_models/src/type_encryption.rs",
"crates/router/src/configs/defaults.rs",
"crates/router/src/configs/secrets_transformers.rs",
"crates/router/src/configs/settings.rs",
"crates/router/src/configs/validatio... | |
juspay/hyperswitch | juspay__hyperswitch-6090 | Bug: restructure `Samsung Pay` connector wallet details
We need to restructure the Samsung Pay session token data stored in the connector wallet details as going forward we will add support for samsung pay payments with hyperswitch credentials. Then the samsung pay payment can be done using either merchant's credent... | diff --git a/crates/api_models/src/payments.rs b/crates/api_models/src/payments.rs
index 456bb8e43a3..9d606dacb9f 100644
--- a/crates/api_models/src/payments.rs
+++ b/crates/api_models/src/payments.rs
@@ -4908,20 +4908,37 @@ pub struct GpaySessionTokenData {
pub data: GpayMetaData,
}
+#[derive(Debug, Clone, ser... | 2024-09-26T06:27:47Z |
## Description
<!-- Describe your changes in detail -->
We need to restructure the Samsung Pay session token data stored in the connector wallet details as going forward we will add support for samsung pay payments with hyperswitch credentials. Then the samsung pay payment can be done using either merchant's credent... | 962b9978d651e3cc9185b2f6f849c7f255868077 |
```
{
"connector_type": "payment_processor",
"connector_name": "cybersource",
"connector_account_details": {
"auth_type": "SignatureKey",
"api_secret": "api_secret",
"key1": "key1",
"api_key": "api_key"
},
"test_mode": true,
"disabled": false,
"p... | [
"crates/api_models/src/payments.rs",
"crates/router/src/core/payments/flows/session_flow.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-6086 | Bug: feat(analytics): add card network feature
Add a filter in payment analytics for the card network column | diff --git a/crates/analytics/src/opensearch.rs b/crates/analytics/src/opensearch.rs
index e0235c67bed..149c77212a0 100644
--- a/crates/analytics/src/opensearch.rs
+++ b/crates/analytics/src/opensearch.rs
@@ -280,7 +280,10 @@ impl HealthCheck for OpenSearchClient {
if health.status != OpenSearchHealthStatus::R... | 2024-09-25T20:51:06Z |
## Description
<!-- Describe your changes in detail -->
- Add card network analytics filter in payment analytics
## 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 start... | 9a605afe372a0602127090da59e35ac9ca7396e1 |
<img width="431" alt="image" src="https://github.com/user-attachments/assets/d209f786-a967-4245-a780-e9539a5c7469">
| [
"crates/analytics/src/opensearch.rs",
"crates/analytics/src/payments/core.rs",
"crates/analytics/src/payments/filters.rs",
"crates/analytics/src/payments/types.rs",
"crates/analytics/src/sqlx.rs",
"crates/api_models/src/analytics/payments.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-6028 | Bug: [FEATURE] Implement Paze Wallet
### Feature Description
Integrate paze wallet
https://www.paze.com/
### Possible Implementation
Integrate paze wallet
https://www.paze.com/
### Have you spent some time checking if this feature request has been raised before?
- [X] I checked and didn't find a similar issue... | diff --git a/api-reference-v2/openapi_spec.json b/api-reference-v2/openapi_spec.json
index 388ccb79a66..44ac1d3e08d 100644
--- a/api-reference-v2/openapi_spec.json
+++ b/api-reference-v2/openapi_spec.json
@@ -5592,6 +5592,11 @@
"type": "object",
"description": "This field contains the Samsung ... | 2024-09-25T13:09:27Z |
## Description
<!-- Describe your changes in detail -->
New wallet Paze is integrated in Hyperswitch with Cybserource as the supported payment processor.
## 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 ... | 2bc21cfc5e3e6d8403bec82fde14cfd01536f406 |
Paze Payments need to be tested via Cybersource:
1. Payments Connector - Create:
Request:
```
curl --location 'http://localhost:8080/account/merchant_1727784802/connectors' \
--header 'Content-Type: application/json' \
--header 'Accept: application/json' \
--header 'api-key: test_admin' \
--data '{
"conn... | [
"api-reference-v2/openapi_spec.json",
"config/config.example.toml",
"config/deployments/env_specific.toml",
"config/deployments/integration_test.toml",
"config/deployments/production.toml",
"config/deployments/sandbox.toml",
"config/development.toml",
"config/docker_compose.toml",
"crates/api_models... | |
juspay/hyperswitch | juspay__hyperswitch-6018 | Bug: pass Samsung Pay `public_key_hash` in the confirm call
The token received form Samsung Pay will be int the JWT format. The header of that will contain the `kid` which is the `public_key_hash`. This is needs to be passed to Cybersource in the confirm call. | diff --git a/crates/router/src/connector/adyen.rs b/crates/router/src/connector/adyen.rs
index f0b84fc93c1..810551e0cb7 100644
--- a/crates/router/src/connector/adyen.rs
+++ b/crates/router/src/connector/adyen.rs
@@ -130,6 +130,7 @@ impl ConnectorValidation for Adyen {
}
},
... | 2024-09-25T05:31:12Z |
## Description
<!-- Describe your changes in detail -->
The token received form Samsung Pay will be int the JWT format. The header of that will contain the `kid` which is the `public_key_hash`. This is needs to be passed to Cybersource in the confirm call.
## Motivation and Context
<!--
Why is this change requ... | 2a10b09a2f7c6bcf0b9b7c23b5b88066e1d0f029 |
Test Samsung Pay flow
-> Enable Samsung Pay payment method for the connector (Cybersource)
```
{
"connector_type": "payment_processor",
"connector_name": "cybersource",
"connector_account_details": {
"auth_type": "SignatureKey",
"api_secret": "api_secret",
"key1": "key1",
... | [
"crates/router/src/connector/adyen.rs",
"crates/router/src/connector/cybersource/transformers.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-6012 | Bug: fix: remove internal entity type
We can remove type internal.
TODO:
- Being internal is the property of role and does not depend on entity type
- We can remove logic for internal entity type and transfer it use role.is_internal() wherever it is being used in the code.
- The mini logics like get entity type ... | diff --git a/crates/common_enums/src/enums.rs b/crates/common_enums/src/enums.rs
index a9ece7e9c02..d6f452a5a01 100644
--- a/crates/common_enums/src/enums.rs
+++ b/crates/common_enums/src/enums.rs
@@ -3144,7 +3144,6 @@ pub enum ApiVersion {
#[strum(serialize_all = "snake_case")]
#[serde(rename_all = "snake_case")]
p... | 2024-09-24T11:18:33Z |
## Description
Remove internal from entity type. Being internal is the property of role and does not depend on entity type. Even internal role can have the entity types as 'Merchant', 'Org' or 'Profile'
## Motivation and Context
Closes [#6012](https://github.com/juspay/hyperswitch/issues/6012)
# | 3ddfe53838c6b039dc5f669ccd23d3035521d691 | Switch should work fine for users
For internal users also switch merchant should work as expected.
```
curl --location 'http://localhost:8080/user/switch/merchant' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer JWT' \
--data '{
"merchant_id": "some_merchant_id"
}'
```
The ... | [
"crates/common_enums/src/enums.rs",
"crates/diesel_models/src/user_role.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/services/authorization/roles/predefined_roles.rs",
"crates/router/src/types/domain/user.rs"... | |
juspay/hyperswitch | juspay__hyperswitch-6004 | Bug: [BUG] [CORE] Payment method details are being none in Psync Response.
### Bug Description
Payment method details are being none in Psync Response.
### Expected Behavior
Payment method data should be populated in Psync response for all the payment methods, except for network token.
### Actual Behavior
Payme... | diff --git a/crates/router/src/core/payments/transformers.rs b/crates/router/src/core/payments/transformers.rs
index 37e178dc7f3..d8c5f88dde9 100644
--- a/crates/router/src/core/payments/transformers.rs
+++ b/crates/router/src/core/payments/transformers.rs
@@ -784,36 +784,16 @@ where
.map(ToString::to_string)
... | 2024-09-24T08:35:45Z |
## Description
<!-- Describe your changes in detail -->
Currently, in Psync response, payment_method_data is being none. Updated the Psync response with pm data.
For network token pm data will be none, since we are not storing additional pm data in attempt.
For other payment methods, it will continue to function ... | 8a9fed36fc7f01f54d9a2e725abf459fac857222 |
payment curl -
```{
"amount": 6540,
"currency": "USD",
"confirm": true,
"capture_method": "automatic",
"capture_on": "2022-09-10T10:11:12Z",
"amount_to_capture": 6540,
"customer_id": "StripeCustomer",
"email": "guest@example.com",
"name": "John Doe",
"phone": "99999... | [
"crates/router/src/core/payments/transformers.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-5966 | Bug: [BUG] Bug in merchant connector account create - delete flows
### Bug Description
There is a problem with how the `configs` table is updated. The problem arises when a user deletes a connector and then adds the same one, the config isn't cleaned from the connector when it's deleted, and the new connector (with... | diff --git a/crates/common_enums/src/enums.rs b/crates/common_enums/src/enums.rs
index 781b5e3710a..f0adf49c1e8 100644
--- a/crates/common_enums/src/enums.rs
+++ b/crates/common_enums/src/enums.rs
@@ -3327,6 +3327,16 @@ pub enum PresenceOfCustomerDuringPayment {
Absent,
}
+impl From<ConnectorType> for Transacti... | 2024-09-23T13:34:14Z |
## Description
Fixes #5966 (in both v1 and v2). Now the router cleans up the configs table (or business_profile in v2) when a connector is deleted.
## 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... | 64383915bda5693df1cecf6cc5683e8b9aaef99b | Added a payment and payout processor, checked if values are present in config, deleted and rechecked.
v1:
v2:
| [
"crates/common_enums/src/enums.rs",
"crates/router/src/core/admin.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-5996 | Bug: feat(users): Add entity type filter in list users and list roles API
Currently list users and list roles API is sending all the users and roles respectively for those who are same entity level and less.
We need to add filters in these APIs to send users and roles who are only at particular entity level. | diff --git a/crates/api_models/src/events/user_role.rs b/crates/api_models/src/events/user_role.rs
index 81b38198cfc..eb09abd471c 100644
--- a/crates/api_models/src/events/user_role.rs
+++ b/crates/api_models/src/events/user_role.rs
@@ -2,12 +2,12 @@ use common_utils::events::{ApiEventMetric, ApiEventsType};
use cra... | 2024-09-23T13:30:11Z |
## Description
<!-- Describe your changes in detail -->
- Adds entity_type filter in list users and list roles API.
## 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 st... | 035906e9b1b1a1e52fe970db5d7e028556fa82b4 |
1. List Users
```
curl 'http://localhost:8080/user/user/v2/list' \
-H 'authorization: Bearer JWT' \
```
This should respond with all the users who are at the same level and lower.
```
curl 'http://localhost:8080/user/user/v2/list?entity_type=organization' \
-H 'authorization: Bearer JWT' \
```
This ... | [
"crates/api_models/src/events/user_role.rs",
"crates/api_models/src/user_role.rs",
"crates/api_models/src/user_role/role.rs",
"crates/router/src/core/user_role.rs",
"crates/router/src/core/user_role/role.rs",
"crates/router/src/routes/user_role.rs",
"crates/router/src/utils/user_role.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-5995 | Bug: feat(payments): support for card_network filter in payments list
- Support for card_network as filters in payments list
- Card network values in payments filter values | diff --git a/crates/api_models/src/payments.rs b/crates/api_models/src/payments.rs
index 584f81992bd..4034b8cd58e 100644
--- a/crates/api_models/src/payments.rs
+++ b/crates/api_models/src/payments.rs
@@ -4361,6 +4361,8 @@ pub struct PaymentListFilterConstraints {
/// The order in which payments list should be sor... | 2024-09-23T09:15:45Z |
## Description
<!-- Describe your changes in detail -->
- Support for card_network as filters in payments list
- Card network values in payments filter values
## 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.
... | b7139483bb4735b7dfaf7e659ab33a16a90af1db |
1. Payments filter list
Request
```
curl --location 'http://localhost:8080/payments/v2/filter' \
--header 'Authorization: Bearer JWT' \
--data ''
```
Response
```
{
"connector": {
"connector_name": [
{
"connector_label": "connector_label",
"mer... | [
"crates/api_models/src/payments.rs",
"crates/hyperswitch_domain_models/src/payments/payment_intent.rs",
"crates/router/src/core/payments.rs",
"crates/storage_impl/src/payments/payment_intent.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-6002 | Bug: [FEATURE] [CRYPTOPAY] Move connector code to crate hyperswitch_connectors
### Feature Description
Connector code for `cryptopay` needs to be moved from crate `router` to new crate `hyperswitch_connectors`
### Possible Implementation
Connector code for `cryptopay` needs to be moved from crate `router` to new ... | diff --git a/crates/hyperswitch_connectors/src/connectors.rs b/crates/hyperswitch_connectors/src/connectors.rs
index 48c50936d60..f057b7d4a33 100644
--- a/crates/hyperswitch_connectors/src/connectors.rs
+++ b/crates/hyperswitch_connectors/src/connectors.rs
@@ -1,5 +1,8 @@
pub mod bambora;
pub mod bitpay;
+pub mod cas... | 2024-09-20T18:00:15Z |
## 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... | d9270ace8ddde16eca8c45ceb79af3e4d815d7cd |
Cryptopay:
Request:
```
curl --location 'http://localhost:8080/payments' \
--header 'Content-Type: application/json' \
--header 'Accept: application/json' \
--header 'api-key: dev_23PxPwqBujt8VbpD0hwiNIqNHY5HNa82ZKPJEfN2Ex2y9CE2RcPNiNCeBMIMBifB' \
--data-raw '{
"amount": 300,
"currency": "USD",
... | [
"crates/hyperswitch_connectors/src/connectors.rs",
"crates/router/src/connector/cashtocode.rs",
"crates/router/src/connector/cashtocode/transformers.rs",
"crates/router/src/connector/coinbase.rs",
"crates/router/src/connector/coinbase/transformers.rs",
"crates/router/src/connector/cryptopay.rs",
"crates... | |
juspay/hyperswitch | juspay__hyperswitch-6001 | Bug: [FEATURE] [CASHTOCODE] Move connector code to crate hyperswitch_connectors
### Feature Description
Connector code for `cashtocode` needs to be moved from crate `router` to new crate `hyperswitch_connectors`
### Possible Implementation
Connector code for `cashtocode` needs to be moved from crate `router` to n... | diff --git a/crates/hyperswitch_connectors/src/connectors.rs b/crates/hyperswitch_connectors/src/connectors.rs
index 48c50936d60..f057b7d4a33 100644
--- a/crates/hyperswitch_connectors/src/connectors.rs
+++ b/crates/hyperswitch_connectors/src/connectors.rs
@@ -1,5 +1,8 @@
pub mod bambora;
pub mod bitpay;
+pub mod cas... | 2024-09-20T18:00:15Z |
## 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... | d9270ace8ddde16eca8c45ceb79af3e4d815d7cd |
Cryptopay:
Request:
```
curl --location 'http://localhost:8080/payments' \
--header 'Content-Type: application/json' \
--header 'Accept: application/json' \
--header 'api-key: dev_23PxPwqBujt8VbpD0hwiNIqNHY5HNa82ZKPJEfN2Ex2y9CE2RcPNiNCeBMIMBifB' \
--data-raw '{
"amount": 300,
"currency": "USD",
... | [
"crates/hyperswitch_connectors/src/connectors.rs",
"crates/router/src/connector/cashtocode.rs",
"crates/router/src/connector/cashtocode/transformers.rs",
"crates/router/src/connector/coinbase.rs",
"crates/router/src/connector/coinbase/transformers.rs",
"crates/router/src/connector/cryptopay.rs",
"crates... | |
juspay/hyperswitch | juspay__hyperswitch-5629 | Bug: [FEATURE] [COINBASE] Move connector code to crate hyperswitch_connectors
### Feature Description
Connector code for `coinbase` needs to be moved from crate `router` to new crate `hyperswitch_connectors`
### Possible Implementation
Connector code for `coinbase` needs to be moved from crate `router` to n... | diff --git a/crates/hyperswitch_connectors/src/connectors.rs b/crates/hyperswitch_connectors/src/connectors.rs
index 48c50936d60..f057b7d4a33 100644
--- a/crates/hyperswitch_connectors/src/connectors.rs
+++ b/crates/hyperswitch_connectors/src/connectors.rs
@@ -1,5 +1,8 @@
pub mod bambora;
pub mod bitpay;
+pub mod cas... | 2024-09-20T18:00:15Z |
## 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... | d9270ace8ddde16eca8c45ceb79af3e4d815d7cd |
Cryptopay:
Request:
```
curl --location 'http://localhost:8080/payments' \
--header 'Content-Type: application/json' \
--header 'Accept: application/json' \
--header 'api-key: dev_23PxPwqBujt8VbpD0hwiNIqNHY5HNa82ZKPJEfN2Ex2y9CE2RcPNiNCeBMIMBifB' \
--data-raw '{
"amount": 300,
"currency": "USD",
... | [
"crates/hyperswitch_connectors/src/connectors.rs",
"crates/router/src/connector/cashtocode.rs",
"crates/router/src/connector/cashtocode/transformers.rs",
"crates/router/src/connector/coinbase.rs",
"crates/router/src/connector/coinbase/transformers.rs",
"crates/router/src/connector/cryptopay.rs",
"crates... | |
juspay/hyperswitch | juspay__hyperswitch-5982 | Bug: add `email` in `billing` and `shipping` address of merchant payment method list
This is to extend the feature of [collect address details](https://github.com/juspay/hyperswitch/pull/5418) to collect `billing.email` and `shipping.email`.
As per this when `"always_collect_shipping_details_from_wallet_connector... | diff --git a/crates/router/src/configs/defaults.rs b/crates/router/src/configs/defaults.rs
index 41efc6e4c38..5719e111759 100644
--- a/crates/router/src/configs/defaults.rs
+++ b/crates/router/src/configs/defaults.rs
@@ -12353,6 +12353,15 @@ pub fn get_billing_required_fields() -> HashMap<String, RequiredFieldInfo> {
... | 2024-09-20T13:48:34Z |
## Description
<!-- Describe your changes in detail -->
This is to extend the feature of [collect address details](https://github.com/juspay/hyperswitch/pull/5418) to collect `billing.email` and `shipping.email`.
## Motivation and Context
<!--
Why is this change required? What problem does it solve?
If it fix... | c0cac8d9135b14945ce5763327ec16b1578ca2a2 |
-> Create a merchant account
-> Set the below config in the business profile
```
curl --location 'http://localhost:8080/account/merchant_1726839405/business_profile/pro_TwNiv0vtGBct5t1SLyhm' \
--header 'Content-Type: application/json' \
--header 'Accept: application/json' \
--header 'api-key: *' \
--data '{
... | [
"crates/router/src/configs/defaults.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-5979 | Bug: [REFACTOR] API Key List and Update endpoints in Hyperswitch V2
Update API Key endpoint in V2, the URLs are registered in the `app.rs` but the necessary changes to it has not been made in `api_keys.rs`.
In addition to that, List API Key endpoint for V2 does not work as no such thing exist in `api_keys.rs`.
... | diff --git a/api-reference-v2/api-reference/api-key/api-key--list.mdx b/api-reference-v2/api-reference/api-key/api-key--list.mdx
new file mode 100644
index 00000000000..5975e9bd6ca
--- /dev/null
+++ b/api-reference-v2/api-reference/api-key/api-key--list.mdx
@@ -0,0 +1,3 @@
+---
+openapi: get /v2/api_keys/list
+---
diff... | 2024-09-20T13:18:13Z |
## Description
<!-- Describe your changes in detail -->
This PR fixes `404` errors thrown by API Key List and Update endpoints.
Previously:
Update end point:
```curl
curl --location --request PUT '{{baseUrl}}/v2/api_keys/{{api_key_id}}' \
--header 'Content-Type: application/json' \
--header 'Accept: ap... | 5fec99b58b0062dbc02fc8fdc1bd8d949d76c51e |
tested it by running locally.
Create Api Key endpoint:
```curl
curl --location 'http://Localhost:8080/v2/api_keys' \
--header 'x-merchant-id: cloth_seller_o6pEetqmlQjhp0kfR7ae' \
--header 'Content-Type: application/json' \
--header 'api-key: test_admin' \
--data '{
"name": "My Api Key",
"expira... | [
"api-reference-v2/api-reference/api-key/api-key--list.mdx",
"api-reference-v2/mint.json",
"api-reference-v2/openapi_spec.json",
"crates/api_models/src/api_keys.rs",
"crates/api_models/src/events.rs",
"crates/openapi/src/openapi.rs",
"crates/openapi/src/openapi_v2.rs",
"crates/openapi/src/routes/api_ke... | |
juspay/hyperswitch | juspay__hyperswitch-5976 | Bug: [BUG] [DEUTSCHEBANK] Trim the spaces in IBAN
### Bug Description
Trim the spaces in IBAN before sending it in SEPA Mandate Post and Direct Debit requests for Deutsche Bank.
### Expected Behavior
No spaces in IBAN in SEPA Mandate Post and Direct Debit requests.
### Actual Behavior
Spaces in IBAN in SEPA Man... | diff --git a/crates/hyperswitch_connectors/src/connectors/deutschebank/transformers.rs b/crates/hyperswitch_connectors/src/connectors/deutschebank/transformers.rs
index 8b3837edd63..30b1d65134a 100644
--- a/crates/hyperswitch_connectors/src/connectors/deutschebank/transformers.rs
+++ b/crates/hyperswitch_connectors/src... | 2024-09-20T11:49:40Z |
## Description
<!-- Describe your changes in detail -->
Trim the spaces in IBAN before sending it in SEPA Mandate Post and Direct Debit requests for Deutsche Bank.
## 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.
... | 5335f2d21ce6f0c11dc84fd56b3cd2c80e8b064f |
Request:
```
curl --location 'http://localhost:8080/payments' \
--header 'Content-Type: application/json' \
--header 'Accept: application/json' \
--header 'api-key: dev_2QpEeK0ByPRkb2DPBxHfad4i1WxQO3hZSuVzlFcg9mTrLFUHRpGfE0SCuQwZjGEb' \
--data '{
"amount": 9000,
"currency": "EUR",
"confirm": true... | [
"crates/hyperswitch_connectors/src/connectors/deutschebank/transformers.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-5974 | Bug: Missing terms and conditions for the contests.
The team should add terms and conditions for the contests like Hacktoberfest. | diff --git a/api-reference-v2/openapi_spec.json b/api-reference-v2/openapi_spec.json
index 926af8c162c..577fe4ae1b7 100644
--- a/api-reference-v2/openapi_spec.json
+++ b/api-reference-v2/openapi_spec.json
@@ -7293,7 +7293,7 @@
},
"FutureUsage": {
"type": "string",
- "description": "Indicat... | 2024-09-20T10:51:26Z |
## 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... | dccb8d4e629d615a69f6922a96e72f10d3410bfc | [
"api-reference-v2/openapi_spec.json",
"crates/common_enums/src/enums.rs"
] | ||
juspay/hyperswitch | juspay__hyperswitch-5970 | Bug: add `phone` and `country_code` in dynamic fields
This is to extend the feature of [collecting address details](https://github.com/juspay/hyperswitch/pull/5418) from wallets to paylater.
Additionally also include phone and country_code in the dynamic fields. | diff --git a/crates/router/src/configs/defaults.rs b/crates/router/src/configs/defaults.rs
index 4fcb0785ea1..41efc6e4c38 100644
--- a/crates/router/src/configs/defaults.rs
+++ b/crates/router/src/configs/defaults.rs
@@ -12335,6 +12335,24 @@ pub fn get_billing_required_fields() -> HashMap<String, RequiredFieldInfo> {
... | 2024-09-19T14:51:31Z |
## Description
<!-- Describe your changes in detail -->
This is to extend the feature of [collecting address details](https://github.com/juspay/hyperswitch/pull/5418) from wallets to paylater.
Additionally also include phone and country_code in the dynamic fields.
## Motivation and Context
<!--
Why is this ... | 5942e059e9efa3fa71a13cacc896509515e2f976 |
-> Create a merchant connector of Klarna with klarna payment method enabled.
-> Set the below business profile config
```
curl --location 'http://localhost:8080/account/merchant_1726764490/business_profile/pro_XOWZOwYWMAmTV4wEyGgh' \
--header 'Content-Type: application/json' \
--header 'Accept: application/json'... | [
"crates/router/src/configs/defaults.rs",
"crates/router/src/core/payment_methods/cards.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-5963 | Bug: fix(dashboard_metadata): Fix prod intent emails
Currently prod intent emails are not going to biz email. Email are working on custom integ, integ main pod and custom sandbox pod with some code changes. Need to check if sandbox main pod is also able to send emails. | diff --git a/config/config.example.toml b/config/config.example.toml
index be0532622bb..a6af984b01f 100644
--- a/config/config.example.toml
+++ b/config/config.example.toml
@@ -375,10 +375,12 @@ wildcard_origin = false # If true, allows any origin to make req
# EmailClient configuration. Only applica... | 2024-09-19T12:17:46Z |
## Description
<!-- Describe your changes in detail -->
- This PR add recipient emails for recon and prod_intent under email config.
## 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, ... | 82574c0e8e7eb69e9f21eedc765145c724960cd5 |
```
curl --location 'http://localhost:8080/user/data' \
--header 'Content-Type: application/json' \
--header 'Authorization: ••••••' \
--data '
{
"ProdIntent": {
"is_completed": true,
"legal_business_name": "test",
"business_label": "test",
"business_location": "US",
... | [
"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/secrets_transformers.rs",
"crates/router/src/configs/settings.rs",
"crates/router/src/consts/user.rs",
"c... | |
juspay/hyperswitch | juspay__hyperswitch-5958 | Bug: fix: add time_range constraint to retrieve payment attempt list
Currently, to retrieve the total count for payments, we use a query that gets the total count of attempts based on the last active attempt ID. To enhance performance, we need to add a time_range to the query. This will ensure that the query is exec... | diff --git a/api-reference-v2/openapi_spec.json b/api-reference-v2/openapi_spec.json
index 5465d902388..3690bcf24db 100644
--- a/api-reference-v2/openapi_spec.json
+++ b/api-reference-v2/openapi_spec.json
@@ -18569,6 +18569,7 @@
},
"TimeRange": {
"type": "object",
+ "description": "A type ... | 2024-09-19T11:00:46Z |
## Description
- Add time range to filter total count for payment attempt list.
- Move `TimeRange` type to common utils so that it can be used in diesel models and across all the other api models
## Motivation and Context
Closes #5958
# | 6a6ce17506932e0843140ef5b02ed201d0524d5d | The expected behaviour is same, the query that is getting printed, is now also considering time range.
```
SELECT COUNT(*) FROM "payment_attempt" WHERE ((("payment_attempt"."merchant_id" = $1)
AND ("payment_attempt"."attempt_id" = ANY($2))) AND ("payment_attempt"."created_at" >= $3))
-- binds: [MerchantId("mercha... | [
"api-reference-v2/openapi_spec.json",
"crates/analytics/src/disputes/metrics.rs",
"crates/analytics/src/opensearch.rs",
"crates/api_models/src/analytics.rs",
"crates/api_models/src/analytics/search.rs",
"crates/api_models/src/events.rs",
"crates/api_models/src/payments.rs",
"crates/api_models/src/payo... | |
juspay/hyperswitch | juspay__hyperswitch-5956 | Bug: [BUG] using FRM with Signifyd throws 5xx
### Bug Description
Enabling Signifyd FRM connector for payments, and using this for a payment throws 5xx. This is due to Signifyd sending 303 which is not handled in HyperSwitch. Signifyd throws 303 as the URL is malformed.
https://api.signifyd.com//v3/orders/even... | diff --git a/crates/router/src/connector/signifyd.rs b/crates/router/src/connector/signifyd.rs
index 6ba2dce9861..4ee36d8966b 100644
--- a/crates/router/src/connector/signifyd.rs
+++ b/crates/router/src/connector/signifyd.rs
@@ -237,7 +237,7 @@ impl
Ok(format!(
"{}{}",
self.base_url(c... | 2024-09-19T09:26:00Z |
## Description
Described in #5956
## Motivation and Context
Fixes 5xx thrown by payments API when FRM flows are consumed.
# | 7076ae9244e26c08c61fdca328237963b3797a5a | Locally - using an increased stack size.
| [
"crates/router/src/connector/signifyd.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-5969 | Bug: Add support for Samsung Pay payment method
This is to support for Samsung pay as a payment method.
This also needs to add a new field in merchant connector account create `connector_wallet_details` which is required to collect the required credentials for Samsung Pay. As this column in the data base stores the... | diff --git a/api-reference-v2/openapi_spec.json b/api-reference-v2/openapi_spec.json
index 5465d902388..a250a8a9c37 100644
--- a/api-reference-v2/openapi_spec.json
+++ b/api-reference-v2/openapi_spec.json
@@ -5521,6 +5521,27 @@
}
}
},
+ "ConnectorWalletDetails": {
+ "type": "objec... | 2024-09-19T08:10:50Z |
## Description
<!-- Describe your changes in detail -->
This pr is to support for Samsung pay as a payment method.
This pr also adds a new field in merchant connector account create `connector_wallet_details` which is required to collect the required credentials for Samsung Pay. As this column in the data base stor... | 5942e059e9efa3fa71a13cacc896509515e2f976 |
Test Samsung Pay flow
-> Enable Samsung Pay payment method for the connector
```
{
"connector_type": "payment_processor",
"connector_name": "cybersource",
"connector_account_details": {
"auth_type": "SignatureKey",
"api_secret": "api_secret",
"key1": "key1",
"api_... | [
"api-reference-v2/openapi_spec.json",
"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/admin.rs",
"crates/api_models/src/p... | |
juspay/hyperswitch | juspay__hyperswitch-5952 | Bug: [CHORE]: update docker compose toml
### Feature Description
remove the network_tokenization_service config
### Possible Implementation
remove the network_tokenization_service config
### Have you spent some time checking if this feature request has been raised before?
- [X] I checked and didn't find a simi... | diff --git a/config/docker_compose.toml b/config/docker_compose.toml
index 698800f082d..f0d44db4d5e 100644
--- a/config/docker_compose.toml
+++ b/config/docker_compose.toml
@@ -597,15 +597,5 @@ recon = "recon@example.com"
[network_tokenization_supported_card_networks]
card_networks = "Visa, AmericanExpress, Mastercar... | 2024-09-19T06:58:00Z |
## Description
<!-- Describe your changes in detail -->
remove the network_tokenization_service from the config
## Motivation and Context
<!--
Why is this change required? What problem does it solve?
If it fixes an op... | 769111c20b0f745a5e4fc3ed6c9a705f277c3d5b |
Test is not required
| [
"config/docker_compose.toml"
] | |
juspay/hyperswitch | juspay__hyperswitch-5946 | Bug: fix(external_services): add proto compilation under a feature flag
add proto compilation under a feature flag | diff --git a/config/config.example.toml b/config/config.example.toml
index a6af984b01f..8345185238d 100644
--- a/config/config.example.toml
+++ b/config/config.example.toml
@@ -748,3 +748,7 @@ check_token_status_url= "" # base url to check token status from token servic
[network_tokenization_supported_connectors]... | 2024-09-18T10:38:19Z |
## Description
add proto build under the dynamic_routing feature flag. Now the application would run without having to install protoc
## 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... | c8f7232a3001be1fc5d8b0fedfd703030df83789 | Cannot be tested as it is for compiling the application without having to mandatorily install proton
| [
"config/config.example.toml",
"config/deployments/env_specific.toml",
"crates/external_services/Cargo.toml",
"crates/external_services/build.rs",
"crates/external_services/src/grpc_client/dynamic_routing.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-5941 | Bug: Update and Retrieve PM APIs
### Feature Description
- Update Payment methods API
- Retrieve Payment Method API | diff --git a/crates/api_models/src/payment_methods.rs b/crates/api_models/src/payment_methods.rs
index 6c93b0bb5bd..1a82dc0e26b 100644
--- a/crates/api_models/src/payment_methods.rs
+++ b/crates/api_models/src/payment_methods.rs
@@ -374,7 +374,7 @@ pub struct PaymentMethodUpdate {
#[serde(deny_unknown_fields)]
pub st... | 2024-09-18T08:09:47Z |
## Description
<!-- Describe your changes in detail -->
- Update PM API for v2
- Retrieve PM API 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 have an issue, we'd recommend starting wi... | 4eec6ca4b05202dea1f5400007c5f143142b65e4 |
Vault dev is incomplete so cannot be tested.
| [
"crates/api_models/src/payment_methods.rs",
"crates/router/src/consts.rs",
"crates/router/src/core/payment_methods.rs",
"crates/router/src/core/payment_methods/cards.rs",
"crates/router/src/core/payment_methods/transformers.rs",
"crates/router/src/core/payments/helpers.rs",
"crates/router/src/routes/app... | |
juspay/hyperswitch | juspay__hyperswitch-5934 | Bug: feat(opensearch): restrict search view access based on user roles and permissions
To fix the issue raised here: [https://github.com/juspay/hyperswitch-cloud/issues/6759](https://github.com/juspay/hyperswitch-cloud/issues/6759)
- Currently, a profile level user is able to see the other profile payments list whe... | diff --git a/config/dashboard.toml b/config/dashboard.toml
index 4cafdd49ab3..87c00721736 100644
--- a/config/dashboard.toml
+++ b/config/dashboard.toml
@@ -35,5 +35,6 @@ global_search=true
dispute_analytics=true
configure_pmts=false
branding=false
+user_management_revamp=true
totp=true
live_users_counter=false
\ ... | 2024-09-18T06:53:54Z |
## Description
<!-- Describe your changes in detail -->
Fixes the issue raised here: [https://github.com/juspay/hyperswitch-cloud/issues/6759](https://github.com/juspay/hyperswitch-cloud/issues/6759)
- Currently, a profile level user is able to see the other profile payments list when using global-search, irrespe... | e7da0474ec63c9953098ee808543e22e114291cf |
Try to search payments of a profile from another profile which doesn't have access to the profile where the payments are present. Results should not show up while using global search.
| [
"config/dashboard.toml",
"crates/analytics/src/opensearch.rs",
"crates/router/src/analytics.rs",
"crates/router/src/consts/opensearch.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-5944 | Bug: feat(refunds) : profile level refunds aggregate
Support for disputes aggregate at profile level | diff --git a/crates/router/src/core/refunds.rs b/crates/router/src/core/refunds.rs
index 118f4b81766..0f3dfa44c10 100644
--- a/crates/router/src/core/refunds.rs
+++ b/crates/router/src/core/refunds.rs
@@ -1098,11 +1098,17 @@ pub async fn get_filters_for_refunds(
pub async fn get_aggregates_for_refunds(
state: Ses... | 2024-09-18T06:32:36Z |
## Description
<!-- Describe your changes in detail -->
- Add support for profile level refunds aggregate
- For now it will have list of intent status along with the their count for a given time range.
## Motivation and Context
<!--
Why is this change required? What problem does it solve?
If it fixes an op... | dccb8d4e629d615a69f6922a96e72f10d3410bfc |
Request :
```
curl --location 'http://localhost:8080/refunds/profile/aggregate?start_time=2022-08-10T18%3A30%3A00Z' \
--header 'Authorization: Bearer JWT' \
--data ''
```
Response
```
{
"status_with_count": {
"success": 3,
"pending": 0,
"failure": 0,
"manual_review... | [
"crates/router/src/core/refunds.rs",
"crates/router/src/db/kafka_store.rs",
"crates/router/src/db/refund.rs",
"crates/router/src/routes/app.rs",
"crates/router/src/routes/refunds.rs",
"crates/router/src/types/storage/refund.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-5924 | Bug: [FEATURE] [DEUTSCHEBANK] Implement subsequent mandate payments via SEPA
### Feature Description
Implement SEPA mandate payments for Deutschebank.
### Possible Implementation
Implement SEPA mandate payments for Deutschebank.
### Have you spent some time checking if this feature request has been raised before... | diff --git a/crates/api_models/src/payments.rs b/crates/api_models/src/payments.rs
index b0866cfb265..535a5abffce 100644
--- a/crates/api_models/src/payments.rs
+++ b/crates/api_models/src/payments.rs
@@ -1042,6 +1042,7 @@ pub struct ConnectorMandateReferenceId {
pub connector_mandate_id: Option<String>,
pub ... | 2024-09-17T11:42:58Z |
## Description
<!-- Describe your changes in detail -->
Implement SEPA mandate payments for Deutschebank.
These mandate details will be stored in the payment_methods table in the connector_mandate_details.
## Motivation and Context
<!--
Why is this change required? What problem does it solve?
If it fixes a... | a94cf25bb6eb40fafc5327aceffac8292b47b001 |
1. Payments Intent Create:
Request:
```
curl --location 'http://localhost:8080/payments' \
--header 'Content-Type: application/json' \
--header 'Accept: application/json' \
--header 'api-key: dev_2QpEeK0ByPRkb2DPBxHfad4i1WxQO3hZSuVzlFcg9mTrLFUHRpGfE0SCuQwZjGEb' \
--data '{
"amount": 1650,
"currenc... | [
"crates/api_models/src/payments.rs",
"crates/hyperswitch_connectors/src/connectors/deutschebank.rs",
"crates/hyperswitch_connectors/src/connectors/deutschebank/transformers.rs",
"crates/hyperswitch_connectors/src/connectors/fiservemea/transformers.rs",
"crates/hyperswitch_connectors/src/connectors/novalnet/... | |
juspay/hyperswitch | juspay__hyperswitch-5906 | Bug: fix(user_roles): Profile level user_roles are not being updated
Currently, updating a profile level user role causes update user role API to break and throw error. This is because profile_id from the token is not being populated in the DB calls.
This makes the API unable to find the user role to be updated. | diff --git a/crates/router/src/core/user_role.rs b/crates/router/src/core/user_role.rs
index 868d2e65a24..d42f71695a5 100644
--- a/crates/router/src/core/user_role.rs
+++ b/crates/router/src/core/user_role.rs
@@ -119,7 +119,7 @@ pub async fn update_user_role(
user_to_be_updated.get_user_id(),
... | 2024-09-16T11:36:31Z |
## Description
<!-- Describe your changes in detail -->
Currently, profile level user_roles are not being updated. This PR fixes it.
## 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, ... | 90ebd54ec9dfabf03ee85c0d0e7d96755a135083 |
```
curl 'http://localhost:8080/user/user/update_role' \
-H 'authorization: Bearer JWT' \
--data-raw '{"email":"email","role_id":"profile_iam_admin"}'
```
Response: 200 OK.
| [
"crates/router/src/core/user_role.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-5898 | Bug: feat(disputes): add support for disputes aggregate
1. Support for disputes aggregate
2. Support for disputes aggregate in profile level | diff --git a/crates/api_models/src/disputes.rs b/crates/api_models/src/disputes.rs
index 5c2a2cc03d2..a1340b5aa5a 100644
--- a/crates/api_models/src/disputes.rs
+++ b/crates/api_models/src/disputes.rs
@@ -1,3 +1,5 @@
+use std::collections::HashMap;
+
use masking::{Deserialize, Serialize};
use time::PrimitiveDateTime;... | 2024-09-16T09:50:34Z |
## Description
<!-- Describe your changes in detail -->
- Add support for disputes aggregate
- Add support for profile level disputes aggregate
- For now it will have list of intent status along with the their count for a given time range.
## Motivation and Context
<!--
Why is this change required? What ... | 90ebd54ec9dfabf03ee85c0d0e7d96755a135083 |
**Dispute Aggregate**
Request:
```
curl --location 'http://localhost:8080/disputes/aggregate?start_time=2022-08-10T18%3A30%3A00Z' \
--header 'Authorization: Bearer JWT' \
--data ''
```
Response :
```
{
"status_with_count": {
"dispute_cancelled": 0,
"dispute_expired": 3,
"d... | [
"crates/api_models/src/disputes.rs",
"crates/api_models/src/events/dispute.rs",
"crates/common_enums/src/enums.rs",
"crates/router/src/core/disputes.rs",
"crates/router/src/db/dispute.rs",
"crates/router/src/db/kafka_store.rs",
"crates/router/src/routes/app.rs",
"crates/router/src/routes/disputes.rs",... | |
juspay/hyperswitch | juspay__hyperswitch-5888 | Bug: [BUG] remove redundant DB calls when FRM feature is not enabled
### Bug Description
FRM is a payment feature which is integrated in HyperSwitch behind `frm` feature flag. There are some DB queries (which are generally not behind a feature flag) which are being executed even when `frm` feature is disabled.
###... | diff --git a/crates/router/src/core/payments/operations/payment_approve.rs b/crates/router/src/core/payments/operations/payment_approve.rs
index 38cf72a3e2f..9c5b632eff0 100644
--- a/crates/router/src/core/payments/operations/payment_approve.rs
+++ b/crates/router/src/core/payments/operations/payment_approve.rs
@@ -136... | 2024-09-16T04:11:58Z |
## Description
Described in #5888
## Motivation and Context
Ensures FRM DB queries are not executed if `frm` feature flag is not enabled. There are a couple of features disabled in HS production, and the DB migrations for such features have not been executed. This leads to unnecessary missing column logs in pro... | 2aa215440e0531e315e61ee30bbbc5a5685481b3 | <details>
<summary>1. Create a txn</summary>
cURL
curl --location 'http://localhost:8080/payments' \
--header 'Content-Type: application/json' \
--header 'Accept: application/json' \
--header 'api-key: dev_4cUeectovRvg0seB0AhDXZ04342m045JeKncgz5XfwkkhJujY4gy7TzfTS9uvdiP' \
--data-raw ... | [
"crates/router/src/core/payments/operations/payment_approve.rs",
"crates/router/src/core/payments/operations/payment_reject.rs",
"crates/router/src/core/payments/operations/payment_status.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-5886 | Bug: [FEATURE] Add Cell ID in config
### Feature Description
Add global cell id information in config for v2
### Possible Implementation
Will need to add in settings
### Have you spent some time checking if this feature request has been raised before?
- [X] I checked and didn't find a similar issue
### Have yo... | diff --git a/config/config.example.toml b/config/config.example.toml
index 1f32481fec7..cf6703f43d4 100644
--- a/config/config.example.toml
+++ b/config/config.example.toml
@@ -734,6 +734,9 @@ connector_list = ""
[recipient_emails]
recon = "test@example.com"
+[cell_information]
+id = "12345" # Default CellID for Gl... | 2024-09-13T15:00:31Z |
## Description
<!-- Describe your changes in detail -->
Added Cell Id in SessionState config
The strategy is use check the value of Cell id at application start and panic if it equals the default value.
## Motivation and Context
<!--
Why is this change required? What problem does it solve?
If it fixes an ope... | c0cac8d9135b14945ce5763327ec16b1578ca2a2 |
Cannot be tested, as setting the cell id as default in config will cause the application to panic.
| [
"config/config.example.toml",
"config/deployments/env_specific.toml",
"config/development.toml",
"config/docker_compose.toml",
"crates/common_utils/src/id_type/global_id.rs",
"crates/common_utils/src/id_type/global_id/payment_methods.rs",
"crates/router/Cargo.toml",
"crates/router/src/configs/secrets_... | |
juspay/hyperswitch | juspay__hyperswitch-5891 | Bug: [FEATURE] Open banking SDK fixes
### Feature Description
SDK would send headers in order to identify the client platform, we need to consume in the backend and process accordingly.
### Possible Implementation
Need to consume headers in specific flows.
### Have you spent some time checking if this feature r... | diff --git a/crates/api_models/src/payments.rs b/crates/api_models/src/payments.rs
index 20f1205e14b..c50b1fb1d05 100644
--- a/crates/api_models/src/payments.rs
+++ b/crates/api_models/src/payments.rs
@@ -793,6 +793,8 @@ pub struct HeaderPayload {
pub x_client_platform: Option<api_enums::ClientPlatform>,
pub ... | 2024-09-13T13:40:37Z |
## Description
<!-- Describe your changes in detail -->
- Refactored RouterData to use HeaderPayload for Android/IOS Platform specific flows.
- Refactored Open banking flows to consume and process the header information to take decisions based on client platform.
## Motivation and Context
<!--
Why is this c... | fbd2cda763f0d8d2757d734578babd73a8613cb8 |
1. Payments create -
```
curl --location --request POST 'http://localhost:8080/payments' \
--header 'Content-Type: application/json' \
--header 'Accept: application/json' \
--header 'api-key: dev_uFcNSTN14N27NiyGdgkK8eN2fBmPWHHhbPZh6RMkBUxoByMfAdPlBItplwGctI6P' \
--data-raw '{
"amount": 6500,
"curren... | [
"crates/api_models/src/payments.rs",
"crates/api_models/src/pm_auth.rs",
"crates/common_enums/src/enums.rs",
"crates/hyperswitch_domain_models/src/router_data.rs",
"crates/hyperswitch_domain_models/src/router_request_types.rs",
"crates/pm_auth/src/connector/plaid/transformers.rs",
"crates/pm_auth/src/ty... | |
juspay/hyperswitch | juspay__hyperswitch-5871 | Bug: feat(analytics): Add metrics, filters and APIs for Analytics v2 Dashboard - Payments Page
Add metrics, filters and APIs for Analytics v2 Dashboard - Payments page
The following filters should be added:
Payment Attempts:
- Merchant_id
- Card last 4
- Error Reason
- Card Issuer
Payment Intents:
... | diff --git a/crates/analytics/src/clickhouse.rs b/crates/analytics/src/clickhouse.rs
index 37a011c9a5a..546b57f99af 100644
--- a/crates/analytics/src/clickhouse.rs
+++ b/crates/analytics/src/clickhouse.rs
@@ -130,9 +130,12 @@ impl AnalyticsDataSource for ClickhouseClient {
fn get_table_engine(table: AnalyticsColle... | 2024-09-12T08:10:00Z |
## Description
<!-- Describe your changes in detail -->
Adding metrics, filters and APIs for Analytics v2 Dashboard - Payments page
The new Analytics Dashboard will now have the following metrics:
- Sessionizer Payment Intents based Metrics:
- Total Payments Savings - Amount saved via Smart Retries
- Payment... | b7139483bb4735b7dfaf7e659ab33a16a90af1db |
Curls for different metrics (which are newly created or modified):
Payment Attempts based metrics:
- sessionized_payment_processed_amount
```bash
curl --location 'http://localhost:8080/analytics/v1/org/metrics/payments' \
--header 'Accept: */*' \
--header 'Accept-Language: en-US,en;q=0.9' \
--header 'Connectio... | [
"crates/analytics/src/clickhouse.rs",
"crates/analytics/src/lib.rs",
"crates/analytics/src/payment_intents.rs",
"crates/analytics/src/payment_intents/accumulator.rs",
"crates/analytics/src/payment_intents/core.rs",
"crates/analytics/src/payment_intents/filters.rs",
"crates/analytics/src/payment_intents/... | |
juspay/hyperswitch | juspay__hyperswitch-5876 | Bug: [BUG] Nix build is broken
### Bug Description
`nix build` is broken as you can see from the CI failure of https://github.com/juspay/hyperswitch/pull/5017
### Expected Behavior
All outputs of `flake.nix` should build.
### Actual Behavior
Some outputs (eg: router) do not build
### Steps To Reproduce
`nix -... | diff --git a/Cargo.nix b/Cargo.nix
deleted file mode 100644
index 1c3c3a086f5..00000000000
--- a/Cargo.nix
+++ /dev/null
@@ -1,5948 +0,0 @@
-# This file was @generated by cargo2nix 0.11.0.
-# It is not intended to be manually edited.
-
-args@{
- release ? true,
- rootFeatures ? [
- "api_models/default"
- "commo... | 2024-09-11T19:50:00Z | Resolves #5876
This PR makes sure that `flake.nix` builds, and checks it in CI (uses self-hosted runners) going forward. It removes no longer used Nix code (they don't build).
- [x] Add github workflow action to build flake outputs
- [x] Remove packages that no longer build (see #5017) | 3ddfe53838c6b039dc5f669ccd23d3035521d691 | [
"Cargo.nix",
"flake.lock",
"flake.nix"
] | ||
juspay/hyperswitch | juspay__hyperswitch-5862 | Bug: [REFACTOR] unify locker api function call
Create a single method using which locker api can be called and deserialised to the given type. Also send tenant-id in headers | diff --git a/crates/router/src/core/admin.rs b/crates/router/src/core/admin.rs
index 996224d7bea..e2c2dbb48ce 100644
--- a/crates/router/src/core/admin.rs
+++ b/crates/router/src/core/admin.rs
@@ -4486,7 +4486,7 @@ async fn locker_recipient_create_call(
ttl: state.conf.locker.ttl_for_storage_in_secs,
});
... | 2024-09-11T14:08:08Z |
## Description
<!-- Describe your changes in detail -->
This PR performs below changes -
* Creates a single method using which locker api can be called and deserialised to the given type.
* Currently, if locker returns an Err, the error response is not JWE+JWS decrypted. Instead its logged directly. This new met... | 10ac08944986a1fd101f8f05263e92ed7ebbba94 |
To test, I failed the locker on purpose and received below error report in Hyperswitch which also includes JWE+JWS decrypted error message.
Sandbox testing - Basic sanity tests which also involves saving card in locker wou... | [
"crates/router/src/core/admin.rs",
"crates/router/src/core/errors.rs",
"crates/router/src/core/payment_methods/cards.rs",
"crates/router/src/core/payment_methods/transformers.rs",
"crates/router/src/core/payouts/helpers.rs",
"crates/router/src/lib.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-5860 | Bug: refactor(users): Populate optional fields in the user APIs
Currently
- list users in lineage
- get user role details
- list invitations
APIs send `null` for role_name, entity_name etc...
These fields should be populated with proper data. | diff --git a/crates/api_models/src/user.rs b/crates/api_models/src/user.rs
index 7bb8409993d..7b22387b3c3 100644
--- a/crates/api_models/src/user.rs
+++ b/crates/api_models/src/user.rs
@@ -188,6 +188,7 @@ pub struct GetUserRoleDetailsResponseV2 {
pub profile: Option<NameIdUnit<String, id_type::ProfileId>>,
pu... | 2024-09-11T12:21:48Z |
## Description
<!-- Describe your changes in detail -->
- Populate entity name in list invitations API.
- Add role name in the response of get user role details API.
- Populate role name in list users in lineage API.
## Motivation and Context
<!--
Why is this change required? What problem does it solve?
If ... | 246fdc84064367885596b33f5e0e66af78a97a3c |
1. List invitations
```
curl 'http://localhost:8080/user/list/invitation' \
-H 'authorization: Bearer SPT with accept invite purpose' \
```
```json
[
{
"entity_id": "merchant_1726053750",
"entity_type": "merchant",
"entity_name": "First M... | [
"crates/api_models/src/user.rs",
"crates/api_models/src/user_role/role.rs",
"crates/diesel_models/src/query/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... | |
juspay/hyperswitch | juspay__hyperswitch-5855 | Bug: fix merchant payment method list
1. `collect_billing_details_from_wallets` field should be made true if either of `always_collect_billing_details_from_wallet_connector` ` collect_billing_details_from_wallet_connector`
2. `collect_shipping_details_from_wallets` field should be made true if either of `always_co... | diff --git a/crates/router/src/core/payment_methods/cards.rs b/crates/router/src/core/payment_methods/cards.rs
index c553840347d..8ab3bf50147 100644
--- a/crates/router/src/core/payment_methods/cards.rs
+++ b/crates/router/src/core/payment_methods/cards.rs
@@ -3656,23 +3656,29 @@ pub async fn list_payment_methods(
... | 2024-09-11T08:13:26Z |
## Description
<!-- Describe your changes in detail -->
1. `collect_billing_details_from_wallets` field should be made true if either of `always_collect_billing_details_from_wallet_connector` ` collect_billing_details_from_wallet_connector` is true
2. `collect_shipping_details_from_wallets` field should be made tru... | be346e5d963925ecbe1bbb77aa024f7eed66019e |
-> Create a merchant account and mca
-> Set the below config in the business profile
```
curl --location 'http://localhost:8080/account/merchant_1726040867/business_profile/pro_a6nz5AzJNeeczSAq4bjx' \
--header 'Content-Type: application/json' \
--header 'Accept: application/json' \
--header 'api-key: test_admin... | [
"crates/router/src/core/payment_methods/cards.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-5852 | Bug: Adding information about decimal and non decimal currencies
There is lack of information about decimal and non decimal currencies in the documentation. | diff --git a/api-reference-v2/openapi_spec.json b/api-reference-v2/openapi_spec.json
index ac4f3fe7b46..ac7f5dfd2cc 100644
--- a/api-reference-v2/openapi_spec.json
+++ b/api-reference-v2/openapi_spec.json
@@ -11596,7 +11596,7 @@
"amount": {
"type": "integer",
"format": "int64",
- ... | 2024-09-11T06:20:15Z |
## 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... | 034f736ea6e25ae2c75e74dedc12ac54f5979d68 | [
"api-reference-v2/openapi_spec.json",
"crates/api_models/src/payments.rs"
] | ||
juspay/hyperswitch | juspay__hyperswitch-5846 | Bug: feat(payments): add support for profile aggregates
Show count of aggregate payments status in the given time range for a particular profile | diff --git a/crates/hyperswitch_domain_models/src/payments/payment_intent.rs b/crates/hyperswitch_domain_models/src/payments/payment_intent.rs
index e5b0e8b9120..62fb06fd522 100644
--- a/crates/hyperswitch_domain_models/src/payments/payment_intent.rs
+++ b/crates/hyperswitch_domain_models/src/payments/payment_intent.rs... | 2024-09-10T07:40:31Z |
## Description
<!-- Describe your changes in detail -->
- Add support for profile level aggregates in payments.
- For now it will have list of intent status along with the their count for a given time range.
## Motivation and Context
<!--
Why is this change required? What problem does it solve?
If it fixes a... | 296ca311c96cc032aaa9ad846299db24bacaeb56 |
Request :
```
curl --location 'http://localhost:8080/payments/profile/aggregate?start_time=2022-08-10T18%3A30%3A00Z' \
--header 'Authorization: Bearer JWT token' \
--data ''
```
Response :
```
{
"status_with_count": {
"failed": 5,
"cancelled": 0,
"processing": 0,
"... | [
"crates/hyperswitch_domain_models/src/payments/payment_intent.rs",
"crates/router/src/core/payments.rs",
"crates/router/src/db/kafka_store.rs",
"crates/router/src/routes/app.rs",
"crates/router/src/routes/payments.rs",
"crates/storage_impl/src/mock_db/payment_intent.rs",
"crates/storage_impl/src/payment... | |
juspay/hyperswitch | juspay__hyperswitch-5842 | Bug: feat(roles): New roles for profile level
Create new roles for profile level roles.
- profile_admin
- profile_view_only
- profile_operator
- profile_developer
- profile_iam | diff --git a/crates/router/src/analytics.rs b/crates/router/src/analytics.rs
index 879db9a5a67..1fcfbdb5df9 100644
--- a/crates/router/src/analytics.rs
+++ b/crates/router/src/analytics.rs
@@ -419,7 +419,7 @@ pub mod routes {
},
&auth::JWTAuth {
permission: Permission::Analyti... | 2024-09-09T13:52:12Z |
## Description
<!-- Describe your changes in detail -->
- Make merchant account create profile level.
- Create new roles for profile users.
## 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... | bf1797fe7cf769eb6e89f75b132a35a6cd9003df |
Invite user at any of the following roles:
- profile_admin
- profile_view_only
- profile_iam_admin
- profile_developer
- profile_operator
Dashboard features should work without 401s.
| [
"crates/router/src/analytics.rs",
"crates/router/src/consts/user_role.rs",
"crates/router/src/core/admin.rs",
"crates/router/src/routes/admin.rs",
"crates/router/src/routes/payment_methods.rs",
"crates/router/src/routes/routing.rs",
"crates/router/src/routes/user.rs",
"crates/router/src/routes/user_ro... | |
juspay/hyperswitch | juspay__hyperswitch-5756 | Bug: Interfacing of client and gRPC communications to Dynamo
Building a gRPC Client for communicating with the Dynamo server, once the dynamic routing feature has been enabled.
The dynamic routing feature would be a compile time as well as runtime feature flag ,
for providing the flexibility to enable and dis... | diff --git a/Cargo.lock b/Cargo.lock
index 11036b42dc4..d90c577152d 100644
--- a/Cargo.lock
+++ b/Cargo.lock
@@ -1433,7 +1433,7 @@ source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3b829e4e32b91e643de6eafe82b1d90675f5874230191a4ffbc1b336dec4d6bf"
dependencies = [
"async-trait",
- "axum-co... | 2024-09-09T05:27:48Z |
## Description
Feature Description:
Building a Grpc Client for communicating with the Dynamo server, once the dynamic routing feature has been enabled.
The dynamic routing feature would be a compile time as well as runtime feature flag ,
for providing the flexibility to enable and disable the dynamic ... | be902ffa5328d32efe70c40c36f86d8fbfa01c79 | - This cannot be tested on sbx, yet
I have tested it locally
- Started the gRPC Server
- Established the connection with the Client <-> Server
- Sent Request the gRPC Server
<img width="1711" alt="Screenshot 2024-09-17 at 7 29 17 PM" src="https://github.com/user-attachments/assets/60fb8ccf-2c4d-48d5-bcfe-f7f3018... | [
"Cargo.lock",
"Dockerfile",
"crates/api_models/src/routing.rs",
"crates/external_services/Cargo.toml",
"crates/external_services/build.rs",
"crates/external_services/src/grpc_client.rs",
"crates/external_services/src/grpc_client/dynamic_routing.rs",
"crates/external_services/src/lib.rs",
"crates/hyp... | |
juspay/hyperswitch | juspay__hyperswitch-5831 | Bug: chore: address Rust 1.81.0 clippy lints
Address the clippy lints occurring due to new rust version 1.81.0
See https://github.com/juspay/hyperswitch/issues/3391 for more information. | diff --git a/crates/drainer/src/health_check.rs b/crates/drainer/src/health_check.rs
index 10514108991..946489513b4 100644
--- a/crates/drainer/src/health_check.rs
+++ b/crates/drainer/src/health_check.rs
@@ -170,7 +170,7 @@ impl HealthCheckInterface for Store {
logger::debug!("Redis set_key was successful");
... | 2024-09-07T05:19:45Z |
## Description
<!-- Describe your changes in detail -->
This PR addresses the clippy lints occurring due to new rust version 1.81.0
## 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, w... | d9485a5f360f78f308f4e70c361f33873c63b686 |
This PR addresses clippy lint due to new rust version. So basic sanity testing should suffice.
| [
"crates/drainer/src/health_check.rs",
"crates/router/src/connector/globalpay.rs",
"crates/router/src/core/health_check.rs",
"crates/router/src/core/payment_methods/surcharge_decision_configs.rs",
"crates/router/src/core/payments.rs",
"crates/router_env/tests/env.rs",
"crates/storage_impl/src/redis/kv_st... | |
juspay/hyperswitch | juspay__hyperswitch-5755 | Bug: Creation of Toggle and Configs for DynamicRouting & DynamicRoutingMetrics
### Toggle for Dynamic Routing:
There should be a 2 way toggle of the switch:
1. For Success-Based routing(whole integration in core that will affect payments).
2. For only enabling metrics of Success-Based routing (This can be used ... | diff --git a/api-reference-v2/openapi_spec.json b/api-reference-v2/openapi_spec.json
index 3c2c811766b..8e6e58865fc 100644
--- a/api-reference-v2/openapi_spec.json
+++ b/api-reference-v2/openapi_spec.json
@@ -17247,7 +17247,8 @@
"single",
"priority",
"volume_split",
- "advanced... | 2024-09-06T15:35:56Z |
## Description
<!-- Describe your changes in detail -->
### Toggle Success based dynamic routing
This PR will toggle success based dynamic routing for a profile, and the flow looks something like this:
1. A default config will be created for the profile, which will look something like this.
```
api_model... | 246fdc84064367885596b33f5e0e66af78a97a3c | 1. Request:
```
curl --location --request POST 'http://localhost:8080/account/merchant_1726160910/business_profile/pro_7Oo0CzTQoOwE5HfwKf6v/dynamic_routing/success_based/toggle?status=false' \
--header 'api-key:xxxxx'
```
Response:
```
{
"id": "routing_sSePmUaucfVIcaSeZPK4",
"profile_id": "pro_ejL5TRsd... | [
"api-reference-v2/openapi_spec.json",
"crates/api_models/src/admin.rs",
"crates/api_models/src/events/routing.rs",
"crates/api_models/src/routing.rs",
"crates/diesel_models/src/business_profile.rs",
"crates/diesel_models/src/enums.rs",
"crates/diesel_models/src/schema.rs",
"crates/diesel_models/src/sc... | |
juspay/hyperswitch | juspay__hyperswitch-5838 | Bug: [REFACTOR] update auth data for recon APIs
### Refactor Description
Refactor the code to
- pass only the required authentication data to recon APIs (remove UserFromToken which contains different resource IDs)
- remove existing impls for fetching user from DB
### Have you spent some time checking if this... | diff --git a/crates/router/src/core/recon.rs b/crates/router/src/core/recon.rs
index fa9944ee8ee..2c2dfc9c9f0 100644
--- a/crates/router/src/core/recon.rs
+++ b/crates/router/src/core/recon.rs
@@ -17,11 +17,10 @@ use crate::{
pub async fn send_recon_request(
state: SessionState,
- user_with_auth_data: authen... | 2024-09-06T13:53:29Z |
## Description
Described in #5838
## Motivation and Context
Helps removing redundant code.
# | aa2f5d147561f6e996228d269e6a54c5d1f53a60 | <details>
<summary>1. Request a new JWT token for recon dashboard</summary>
cURL Request
curl --location 'http://localhost:8080/recon/token' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJ1c2VyX2lkIjoiOWZmNzcxNmItNzB... | [
"crates/router/src/core/recon.rs",
"crates/router/src/core/user.rs",
"crates/router/src/routes/user.rs",
"crates/router/src/services/authentication.rs"
] | |
juspay/hyperswitch | juspay__hyperswitch-5858 | Bug: [FEATURE] [DEUTSCHEBANK] Integrate SEPA Payments
### Feature Description
Integrate SEPA Payments for connector Deutsche Bank
### Possible Implementation
https://testmerch.directpos.de/rest-api/apidoc/v2.1/index.html#chap_sdd
### Have you spent some time checking if this feature request has been raised befor... | diff --git a/api-reference-v2/openapi_spec.json b/api-reference-v2/openapi_spec.json
index bda5fab29c0..acff517e107 100644
--- a/api-reference-v2/openapi_spec.json
+++ b/api-reference-v2/openapi_spec.json
@@ -4979,6 +4979,7 @@
"cryptopay",
"cybersource",
"datatrans",
+ "deutsch... | 2024-09-06T10:29:05Z |
## Description
<!-- Describe your changes in detail -->
Integrate SEPA Payments for connector Deutsche Bank
https://testmerch.directpos.de/rest-api/apidoc/v2.1/index.html#chap_sdd
## Motivation and Context
<!--
Why is this change required? What problem does it solve?
If it fixes an open issue, please link to... | 10ac08944986a1fd101f8f05263e92ed7ebbba94 |
1. Authorize:
Request:
```
curl --location 'http://localhost:8080/payments' \
--header 'Content-Type: application/json' \
--header 'Accept: application/json' \
--header 'api-key: dev_2QpEeK0ByPRkb2DPBxHfad4i1WxQO3hZSuVzlFcg9mTrLFUHRpGfE0SCuQwZjGEb' \
--data '{
"amount": 9000,
"currency": "EUR",
... | [
"api-reference-v2/openapi_spec.json",
"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/enums.rs",
"crates/common_enums/src... | |
juspay/hyperswitch | juspay__hyperswitch-5822 | Bug: feat(analytics): Revert api_event metrics and filters back to merchant_id authentication
`api_event_metrics` and `api_event_filters` APIs were modified to authenticate through AuthInfo where there are MerchantLevel, ProfileLevel and OrgLevel authentication. (https://github.com/juspay/hyperswitch/pull/5729)
But... | diff --git a/crates/analytics/src/api_event/core.rs b/crates/analytics/src/api_event/core.rs
index f3a7b154b90..305de7e69c8 100644
--- a/crates/analytics/src/api_event/core.rs
+++ b/crates/analytics/src/api_event/core.rs
@@ -21,7 +21,6 @@ use super::{
metrics::ApiEventMetricRow,
};
use crate::{
- enums::AuthI... | 2024-09-06T05:59:52Z |
## Description
<!-- Describe your changes in detail -->
Previously modified api_event_metrics and api_event_filters to authenticate through AuthInfo where there are MerchantLevel, ProfileLevel and OrgLevel authentication. ([https://github.com/juspay/hyperswitch/pull/5729](https://github.com/juspay/hyperswitch/pull/5... | d3a1703bf59afc06e87e94433bc10a01e413259b |
Spoke with dashboard team and removed the following api endpoints:
- /analytics/v1/profile/metrics/api_events
- /analytics/v1/profile/filters/api_events
- /analytics/v1/org/metrics/api_events
- /analytics/v1/org/filters/api_events
| [
"crates/analytics/src/api_event/core.rs",
"crates/analytics/src/api_event/filters.rs",
"crates/analytics/src/api_event/metrics.rs",
"crates/analytics/src/api_event/metrics/api_count.rs",
"crates/analytics/src/api_event/metrics/latency.rs",
"crates/analytics/src/api_event/metrics/status_code_count.rs",
"... | |
juspay/hyperswitch | juspay__hyperswitch-5820 | Bug: feat(users): Add profile level role and profile level authz
- Create profile level users.
- Create authorization checks for entity level in apis. default to merchant | diff --git a/crates/router/src/analytics.rs b/crates/router/src/analytics.rs
index a6e94ed294a..7c4d1acc6bf 100644
--- a/crates/router/src/analytics.rs
+++ b/crates/router/src/analytics.rs
@@ -20,6 +20,7 @@ pub mod routes {
GetRefundFilterRequest, GetRefundMetricRequest, GetSdkEventFiltersRequest,
Get... | 2024-09-05T13:54:50Z |
## Description
- Created a profile level user.
- Added entity level authorization in routes.
<!-- Describe your changes in detail -->
## Motivation and Context
Dashboards users to be restricted at profile level.
<!--
Why is this change required? What problem does it solve?
If it fixes an open issue, pleas... | 4d499038c03986a6f3ecee742c5add1c55789b01 | Dashboard UI.
1. Login to dashboard.
2. Invite a user at profile level.
3. Login using profile level user.
4. Check if APIs are working.
| [
"crates/router/src/analytics.rs",
"crates/router/src/consts.rs",
"crates/router/src/consts/user_role.rs",
"crates/router/src/routes/admin.rs",
"crates/router/src/routes/api_keys.rs",
"crates/router/src/routes/blocklist.rs",
"crates/router/src/routes/connector_onboarding.rs",
"crates/router/src/routes/... | |
juspay/hyperswitch | juspay__hyperswitch-5816 | Bug: feat(users): Add profile id in JWT and user_info
Currently tokens doesn't have profile id. Backend should start sending it or else dashboard will not work at profile level. | diff --git a/crates/api_models/src/user.rs b/crates/api_models/src/user.rs
index 4674abf3976..7bb8409993d 100644
--- a/crates/api_models/src/user.rs
+++ b/crates/api_models/src/user.rs
@@ -1,6 +1,6 @@
use std::fmt::Debug;
-use common_enums::{PermissionGroup, RoleScope, TokenPurpose};
+use common_enums::{EntityType, ... | 2024-09-05T11:52:56Z |
## Description
<!-- Describe your changes in detail -->
1. This PR changes list users in lineage API so that it don't do any db call to get the role info which leads us to send null in role name in the response.
2. This PR will add profile_id in JWT and user info API.
## Motivation and Context
<!--
Why is thi... | dfebc29c2b1398ac8934bd350eefcd4fa4f10d84 |
```
curl --location 'http://localhost:8080/user/v2/signin' \
--header 'Content-Type: application/json' \
--data-raw '{
"email": "email",
"password": "name"
}
'
```
```
{
"token": "eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJ1c2VyX2lkIjoiZTY2NjM4OGYtMzE3OC00YmRiLTlhYTYtNjQwNjJkOTIyZTRlIiwicHVycG9zZS... | [
"crates/api_models/src/user.rs",
"crates/api_models/src/user_role/role.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/types/domain/user.rs",
"crates/router/src/types/domain/user/decision_manager.rs",
"crates/... | |
juspay/hyperswitch | juspay__hyperswitch-5815 | Bug: fix(user_roles): List users in lineage API failing
List users in lineage API sends response like following:
```json
[
{
"email": "e1",
"roles": [
{
"role_id": "r1",
"role_name": "name",
}
]
}
]
```
To get the role name, this API does a db call to get the role info in the JWT merchant scop... | diff --git a/crates/api_models/src/user.rs b/crates/api_models/src/user.rs
index 4674abf3976..7bb8409993d 100644
--- a/crates/api_models/src/user.rs
+++ b/crates/api_models/src/user.rs
@@ -1,6 +1,6 @@
use std::fmt::Debug;
-use common_enums::{PermissionGroup, RoleScope, TokenPurpose};
+use common_enums::{EntityType, ... | 2024-09-05T11:52:56Z |
## Description
<!-- Describe your changes in detail -->
1. This PR changes list users in lineage API so that it don't do any db call to get the role info which leads us to send null in role name in the response.
2. This PR will add profile_id in JWT and user info API.
## Motivation and Context
<!--
Why is thi... | dfebc29c2b1398ac8934bd350eefcd4fa4f10d84 |
```
curl --location 'http://localhost:8080/user/v2/signin' \
--header 'Content-Type: application/json' \
--data-raw '{
"email": "email",
"password": "name"
}
'
```
```
{
"token": "eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJ1c2VyX2lkIjoiZTY2NjM4OGYtMzE3OC00YmRiLTlhYTYtNjQwNjJkOTIyZTRlIiwicHVycG9zZS... | [
"crates/api_models/src/user.rs",
"crates/api_models/src/user_role/role.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/types/domain/user.rs",
"crates/router/src/types/domain/user/decision_manager.rs",
"crates/... | |
juspay/hyperswitch | juspay__hyperswitch-4933 | Bug: Refactor `/payment_methods` to support a unified interface for vaulting use-cases
### Feature Description
We want a unified interface to `/payment_methods` create APIs for vaulting a payment method. Request/Response types and their behavior should be same across the vaulting APIs.
Involved APIs would be PM cr... | diff --git a/crates/api_models/Cargo.toml b/crates/api_models/Cargo.toml
index 00c12b9255b..c16b1d9a418 100644
--- a/crates/api_models/Cargo.toml
+++ b/crates/api_models/Cargo.toml
@@ -20,7 +20,7 @@ v1 = ["common_utils/v1"]
v2 = ["common_utils/v2", "customer_v2"]
customer_v2 = ["common_utils/customer_v2"]
payment_v2... | 2024-09-05T09:53:05Z |
## Description
<!-- Describe your changes in detail -->
- Core logic for Payment method create API for v2
- Does not contain global_id (will raise separate PR for that)
## Motivation and Context
<!--
Why is this change required? What problem does it solve?
If it fixes an open issue, please link to the issue ... | 97c8e98a48f514b0ba36b109971dd479ae84861e |
Vault dev is incomplete as of now so cannot test.
| [
"crates/api_models/Cargo.toml",
"crates/api_models/src/events.rs",
"crates/api_models/src/payment_methods.rs",
"crates/common_utils/Cargo.toml",
"crates/common_utils/src/events.rs",
"crates/common_utils/src/id_type.rs",
"crates/common_utils/src/id_type/global_id.rs",
"crates/common_utils/src/id_type/p... | |
juspay/hyperswitch | juspay__hyperswitch-5847 | Bug: [FEATURE] add translation to unified error messages in API response and payout link
### Feature Description
Connector can fail due to numerous reasons and usually returns an error code along with an error message. These error messages are specific to the underlying connectors. However, these errors can be logi... | diff --git a/api-reference-v2/openapi_spec.json b/api-reference-v2/openapi_spec.json
index acff517e107..e7dbbcdabe6 100644
--- a/api-reference-v2/openapi_spec.json
+++ b/api-reference-v2/openapi_spec.json
@@ -15207,13 +15207,17 @@
},
"unified_code": {
"type": "string",
- "d... | 2024-09-05T09:45:42Z |
## Description
This adds `unified_code` and `unified_message` in the payout's API response. These values are looked up in the DB and populated in the API response.
`unified_code` and `unified_message` are then used to fetch the translated message string from DB (if present). This is finally returned in the payouts... | 2aa215440e0531e315e61ee30bbbc5a5685481b3 | **Pre-requisites**
1. Ensure payout unified code and messages are inserted in `gateway_status_map` table
2. Ensure the translated messages for these unified code <> messages are inserted in `unified_translations` table
<details>
<summary>1. Create an invalid payout txn</summary>
cURL
curl --locati... | [
"api-reference-v2/openapi_spec.json",
"crates/api_models/src/payouts.rs",
"crates/common_utils/src/consts.rs",
"crates/common_utils/src/types.rs",
"crates/diesel_models/src/payout_attempt.rs",
"crates/diesel_models/src/schema.rs",
"crates/diesel_models/src/schema_v2.rs",
"crates/hyperswitch_domain_mod... | |
juspay/hyperswitch | juspay__hyperswitch-5805 | Bug: feat(payouts): Add profile level get filters API for payouts
Currently payout get filter API gives filters whole merchant. Since dashboard is being moved to profile level, filter API at profile level should be needed. | diff --git a/crates/router/src/core/payouts.rs b/crates/router/src/core/payouts.rs
index 515a7be959a..65490e2d270 100644
--- a/crates/router/src/core/payouts.rs
+++ b/crates/router/src/core/payouts.rs
@@ -947,10 +947,11 @@ pub async fn payouts_filtered_list_core(
pub async fn payouts_list_available_filters_core(
... | 2024-09-05T08:25:23Z |
## Description
<!-- Describe your changes in detail -->
- This PR adds a profile level get filters api for payouts.
## 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 st... | db04ded4a460abfb073167d59b3c51a4e7972c54 |
```
curl --location 'http://localhost:8080/payouts/profile/filter' \
--header 'Content-Type: application/json' \
--header 'authorization: Bearer JWT with profile_id' \
--data '{"start_time":"2024-08-05T18:30:00Z","end_time":"2024-09-05T08:19:00Z"}'
```
Response will look like this
```json
{
"connector": ... | [
"crates/router/src/core/payouts.rs",
"crates/router/src/routes/app.rs",
"crates/router/src/routes/payouts.rs"
] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.