prompt stringlengths 24 63.1k | response stringlengths 180 101k | metadata stringlengths 143 152 |
|---|---|---|
refactor(core): filter default routing config response based on connector type
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [ ] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
<!-- Describe your change... | <think>
PR Context:
- Title: refactor(core): Revert "filter default routing config response based on connector type"
- Merged: 2025-03-18T15:06:40Z
- Files changed: 1 files
- Commits: 1 commits
Implementation approach:
Reverts juspay/hyperswitch#7199
## Description
<!-- Describe your changes in detail -->
We are... | {"issue_number": 7199, "pr_number": 7556, "commits_count": 1, "files_changed": 1, "response_length": 995, "file_count": 3, "needs_breakdown": false} |
chore(openapi): reformat and fix typos
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [x] Bugfix
- [ ] New feature
- [ ] Enhancement
- [x] Refactoring
- [ ] Dependency updates
## Description
<!-- Describe your changes in detail -->
(If you're reviewing, it's better to follow changes in ... | <think>
PR Context:
- Title: docs(openapi): introduce a `QuickStart` tag
- Merged: 2023-01-03T12:32:42Z
- Files changed: 2 files
- Commits: 5 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
This PR builds on top of changes made in #263 and includes a `QuickStart` tag and fol... | {"issue_number": 263, "pr_number": 264, "commits_count": 0, "files_changed": 2, "response_length": 773, "file_count": 0, "needs_breakdown": false} |
[FEATURE] allow payout_id to be configurable
### Feature Description
`payout_id` is an unique identifier for payout resource which is auto generated during payout creation. This field needs to be configurable during payout creation by accepting in the API.
Along with this, a `merchant_order_reference_id` needs to be... | <think>
PR Context:
- Title: feat(payouts): add domain type for PayoutId
- Merged: 2025-07-01T14:45:02Z
- Files changed: 30 files
- Commits: 16 commits
Implementation approach:
feat(payouts): allow payout_id to be configurable in API request
feat(payouts): add merchant_order_reference_id for referencing payouts
#... | {"issue_number": 8392, "pr_number": 8395, "commits_count": 1, "files_changed": 30, "response_length": 5301, "file_count": 56, "needs_breakdown": true} |
chore(codeowners): add codeowners data for PR reviews
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [ ] New feature
- [x] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
## Description
Adding a CODEOWNERS file for facilitating PR reviews for teams
### Additional... | <think>
PR Context:
- Title: refactor: explicitly specify top redirections for secure payment and payout links
- Merged: 2024-11-11T08:07:30Z
- Files changed: 2 files
- Commits: 2 commits
Implementation approach:
## Description
Described in https://github.com/juspay/hyperswitch-web/issues/773
### Additional Cha... | {"issue_number": 1, "pr_number": 6494, "commits_count": 0, "files_changed": 2, "response_length": 811, "file_count": 0, "needs_breakdown": false} |
Payment Intent and MCA changes for split payments
- Add split_txns_enabled field in PaymentIntent
- Add split_enabled field to MCA payment_method
- Code changes to modify split_enabled for a payment method when creating or updating an MCA (similar to recurring_enabled)
- PML changes to filter payment methods based on ... | <think>
PR Context:
- Title: feat(router): Payment Intent and MCA changes for split payments
- Merged: 2025-09-01T13:47:28Z
- Files changed: 20 files
- Commits: 5 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
- Add split_txns_enabled field to business_profile DB, create+up... | {"issue_number": 9047, "pr_number": 9049, "commits_count": 1, "files_changed": 20, "response_length": 1976, "file_count": 17, "needs_breakdown": true} |
feat(users): add support to check 2FA status
Add support to check whether the 2FA has been done recently or not. ( For now it will check for last five minutes)
Use case: The api will help to check for when was last TOTP done, if user has recently done sign in and trying to do some operation that asks for TOTP again ... | <think>
PR Context:
- Title: feat(users): add endpoint to check 2fa status
- Merged: 2024-05-29T13:45:12Z
- Files changed: 7 files
- Commits: 6 commits
Implementation approach:
## Description
The api checks whether the 2FA has been done recently or not.
It just checks the status in Redis and gives the response.
... | {"issue_number": 4809, "pr_number": 4810, "commits_count": 1, "files_changed": 7, "response_length": 1384, "file_count": 9, "needs_breakdown": false} |
[FEATURE] Recon APIs
### Feature Description
Add recon related APIs in HyperSwitch for managing recon module for the consumers. Recon dashboard is a separate application hosted at https://sandbox.hyperswitch.io/recon-dashboard/
Recon module in HyperSwitch should be able to perform below tasks
- Toggle recon modul... | <think>
PR Context:
- Title: feat(recon): add recon APIs
- Merged: 2024-01-16T11:22:00Z
- Files changed: 22 files
- Commits: 7 commits
Implementation approach:
## Description
This PR adds recon APIs for activating recon as a feature on HyperSwitch dashboard and generating tokens for Recon dashboard.
Issue - #3359... | {"issue_number": 3359, "pr_number": 3345, "commits_count": 1, "files_changed": 22, "response_length": 3691, "file_count": 21, "needs_breakdown": true} |
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. | <think>
PR Context:
- Title: refactor(users): Deprecate unused user APIs and stabilize v1 APIs
- Merged: 2024-10-04T11:53:51Z
- Files changed: 18 files
- Commits: 5 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
Deletions
- `/user/switch_merchant`
- `/user/switch/list... | {"issue_number": 6112, "pr_number": 6114, "commits_count": 1, "files_changed": 18, "response_length": 4341, "file_count": 20, "needs_breakdown": true} |
[FEATURE]: [Multisafepay] 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... | <think>
PR Context:
- Title: feat(connector): [Multisafepay] Use transaction_id as reference to transaction
- Merged: 2023-10-07T18:03:37Z
- Files changed: 1 files
- Commits: 12 commits
Implementation approach:
## Description
Updated the `connector_response_reference_id` value from the response.
closes #2336
... | {"issue_number": 2336, "pr_number": 2451, "commits_count": 1, "files_changed": 1, "response_length": 1001, "file_count": 3, "needs_breakdown": false} |
fix(core): Update pm details in Psync response
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [x] Bugfix
- [ ] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
<!-- Describe your changes in detail -->
Currently, in P... | <think>
PR Context:
- Title: fix(core): Update pm details in Psync response
- Merged: 2024-09-24T12:36:15Z
- Files changed: 1 files
- Commits: 1 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
pr on oss main - [#6003](https://github.com/juspay/hyperswitch/pull/6003)
Current... | {"issue_number": 6003, "pr_number": 6011, "commits_count": 1, "files_changed": 1, "response_length": 927, "file_count": 3, "needs_breakdown": false} |
Add Worldline for card payments | <think>
PR Context:
- Title: feature(connector): add support for worldline connector
- Merged: 2023-01-16T12:53:44Z
- Files changed: 15 files
- Commits: 12 commits
Implementation approach:
## Description
Adding support for [worldline](https://epayments-api.developer-ingenico.com/?paymentPlatform=GLOBALCOLLECT) payme... | {"issue_number": 233, "pr_number": 374, "commits_count": 1, "files_changed": 15, "response_length": 8149, "file_count": 13, "needs_breakdown": true} |
Eliminate Lack of Diagnostics Information because of macro panicking
Proc macro should not panic. When proc macro panics, it will be the only error message returned by the rust compiler. Instead, in case of errors, proc macro should emit compile_error!() to communicate error to the user. This will allow other errors ... | <think>
PR Context:
- Title: fix(router_derive): use compile_error instead of panic
- Merged: 2023-01-11T10:20:01Z
- Files changed: 3 files
- Commits: 7 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
Use compile_error in proc macros instead of panic.
### Additional Chang... | {"issue_number": 115, "pr_number": 332, "commits_count": 1, "files_changed": 3, "response_length": 1085, "file_count": 5, "needs_breakdown": false} |
docs:correction of content in the api-ref | <think>
PR Context:
- Title: docs(api-reference): fix the content of the tip
- Merged: 2025-02-27T13:47:08Z
- Files changed: 1 files
- Commits: 1 commits
Implementation approach:
Corrected the tip content.
## Description
<!-- Describe your changes in detail -->
Corrected the content of the tip.
### Additional... | {"issue_number": 7391, "pr_number": 7387, "commits_count": 0, "files_changed": 1, "response_length": 777, "file_count": 0, "needs_breakdown": false} |
docs(CONTRIBUTING): update contributing guidelines based on Tokio
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [ ] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [x] Documentation
## Description
Updates [`CONTRIBUTING.md`](https://github.com/jusp... | <think>
PR Context:
- Title: ci(workflows): skip CI checks for ignored files
- Merged: 2022-11-23T13:35:25Z
- Files changed: 2 files
- Commits: 2 commits
Implementation approach:
## Description
This PR allows skipping CI checks for [ignored files](https://github.com/juspay/orca/blob/5593a97c91e347a36b21bf78cf1f91d... | {"issue_number": 9, "pr_number": 10, "commits_count": 0, "files_changed": 2, "response_length": 777, "file_count": 0, "needs_breakdown": false} |
[FEATURE]: Save Payment Method on Payments Confirm (V2)
Add functionality to save a payment method after a successful payment | <think>
PR Context:
- Title: feat(router): Save payment method on payments confirm (V2)
- Merged: 2025-06-06T15:55:49Z
- Files changed: 26 files
- Commits: 30 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
- Added a field `payment_token` to customer PML response
- During `... | {"issue_number": 8089, "pr_number": 8090, "commits_count": 1, "files_changed": 26, "response_length": 3921, "file_count": 27, "needs_breakdown": true} |
feat: populate payment method details in payments response
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [ ] New feature
- [x] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
Described in #5652
### Additional Chang... | <think>
PR Context:
- Title: feat: populate payment method details in payments response
- Merged: 2024-09-04T15:26:16Z
- Files changed: 10 files
- Commits: 1 commits
Implementation approach:
(cherry picked from commit c84af20ec1d9c5aba3ab0e290760a40328b9bf8e)
## Description
Reverts the changes in merge commit of ... | {"issue_number": 5661, "pr_number": 5790, "commits_count": 1, "files_changed": 10, "response_length": 4669, "file_count": 10, "needs_breakdown": true} |
[Analytics/Payouts] - add kafka events and clickhouse schema for payout analytics
add kafka events and clickhouse schema for payout analytics | <think>
PR Context:
- Title: feat(payout-events): add kafka events for payout analytics
- Merged: 2024-04-04T07:39:29Z
- Files changed: 9 files
- Commits: 15 commits
Implementation approach:
## Description
add kafka events and clickhouse schema for payout analytics
### Additional Changes
- [ ] This PR modifies... | {"issue_number": 4210, "pr_number": 4211, "commits_count": 1, "files_changed": 9, "response_length": 1495, "file_count": 6, "needs_breakdown": false} |
fix(diesel_models, api_models): mask `poc_email` and `data_value` for DashboardMetadata
## Current behaviour
- `poc_email` isn't masked for `DashboardMetadata` which leads to it being logged both at API and diesel query level.
Example:
<img width="1114" alt="Image" src="https://github.com/user-attachments/assets/8aa... | <think>
PR Context:
- Title: fix(dashboard_metadata): mask `poc_email` and `data_value` for DashboardMetadata
- Merged: 2025-02-06T15:16:20Z
- Files changed: 5 files
- Commits: 8 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
- (api_models): change the `poc_email` type to `... | {"issue_number": 7128, "pr_number": 7130, "commits_count": 1, "files_changed": 5, "response_length": 1303, "file_count": 7, "needs_breakdown": false} |
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 | <think>
PR Context:
- Title: feat(users): New profile level roles
- Merged: 2024-09-10T12:49:59Z
- Files changed: 9 files
- Commits: 7 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
- Make merchant account create profile level.
- Create new roles for profile users.
### ... | {"issue_number": 5842, "pr_number": 5843, "commits_count": 1, "files_changed": 9, "response_length": 1492, "file_count": 11, "needs_breakdown": false} |
feat(connector): [Adyen] Add pix support for adyen
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [x] New feature
## Description
<!-- Describe your changes in detail -->
Add support for `Pix` bank transfer through adyen
Api contract for `Pix`:
```
"payment_method": "bank_transfer",
... | <think>
PR Context:
- Title: revert: feat(connector): [Adyen] Add pix support for adyen
- Merged: 2023-07-26T15:53:33Z
- Files changed: 10 files
- Commits: 1 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
This reverts commit 33a1368e8a0961610d652f5a6834ba37b995582a. (PR #17... | {"issue_number": 1703, "pr_number": 1795, "commits_count": 1, "files_changed": 10, "response_length": 2250, "file_count": 11, "needs_breakdown": false} |
[BUG - Cypress] Cookie not passed in user APIs
we need to pass cookies in user apis | <think>
PR Context:
- Title: fix(cypress): backup and restore sessions when using user apis
- Merged: 2025-01-08T11:43:26Z
- Files changed: 5 files
- Commits: 4 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
this pr fixes the issue where cookies are not being set when hit... | {"issue_number": 6977, "pr_number": 6978, "commits_count": 0, "files_changed": 5, "response_length": 792, "file_count": 0, "needs_breakdown": false} |
fix(list): remove enabled payment methods from list customer payment …
…method
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [ ] New feature
- [x] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
## Description
Removes the enabled payment method field from list_custo... | <think>
PR Context:
- Title: feat(list): global filter mapping for payment methods via card network
- Merged: 2023-03-01T11:31:41Z
- Files changed: 4 files
- Commits: 4 commits
Implementation approach:
## Description
In an earlier PR #689, we added a global filter mapping for `<connector>.<payment_method_type>`, but... | {"issue_number": 689, "pr_number": 694, "commits_count": 1, "files_changed": 4, "response_length": 1154, "file_count": 4, "needs_breakdown": false} |
chore(masking): add peek_mut to PeekInterface
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [x] Enhancement
## Description
<!-- Describe your changes in detail -->
Add `peek_mut` function to PeekInterface to get mutable reference for the inner data.
## Motivation and Context
<!--
Why is t... | <think>
PR Context:
- Title: Feat(connector): [JP MORGAN] Added Template code for cards integration
- Merged: 2024-11-05T15:51:59Z
- Files changed: 25 files
- Commits: 2 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
Template code added for new connector JP Morgan
https:... | {"issue_number": 7281, "pr_number": 6467, "commits_count": 1, "files_changed": 25, "response_length": 8958, "file_count": 18, "needs_breakdown": true} |
bug(events): api events with event_type `user` aren't parsed correctly in clickhouse
The api events with events type user aren't parsed correctly in the user table,
this happens due to there being duplicate keys in the json representation which is treated as invalid json by clickhouse
```json
{
"key_a": "abc... | <think>
PR Context:
- Title: fix(events): Correct parsing of API events with user event_type for Clickhouse
- Merged: 2024-06-19T11:15:06Z
- Files changed: 3 files
- Commits: 2 commits
Implementation approach:
## Description
fix(events): Correct parsing of API events with user event_type for ClickHouse (#4987)
- ... | {"issue_number": 4987, "pr_number": 5022, "commits_count": 1, "files_changed": 3, "response_length": 1042, "file_count": 4, "needs_breakdown": false} |
feat(users): Force users to reset password on first login for non-email flow
Currently in non-email flow, users who are invited are not forced to change their password.
This is being forced in email flow, this should also be present in non-email flow as well. | <think>
PR Context:
- Title: fix(users): Add force rotate password on first login for non-email flow
- Merged: 2024-11-07T10:37:29Z
- Files changed: 1 files
- Commits: 3 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
Currently in non-email flow, users who are invited are no... | {"issue_number": 6482, "pr_number": 6483, "commits_count": 1, "files_changed": 1, "response_length": 1061, "file_count": 3, "needs_breakdown": false} |
feat(mandates): recurring payment support for bank redirect and bank debit payment method for stripe
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [X] New feature
- [ ] Enhancement
- [x] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
<!-... | <think>
PR Context:
- Title: fix(connector): stripe mandate failure and other ui tests failures
- Merged: 2023-07-19T14:57:33Z
- Files changed: 7 files
- Commits: 17 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
1. Fix existing failures in UI tests of existing connectors
... | {"issue_number": 1119, "pr_number": 1742, "commits_count": 1, "files_changed": 7, "response_length": 1317, "file_count": 7, "needs_breakdown": false} |
feat(router): add support for co-badged cards
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [x] New feature
- [x] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
<!-- Describe your changes in detail -->
In this PR, we e... | <think>
PR Context:
- Title: feat(router): revert support for co-badged cards
- Merged: 2024-09-27T12:33:10Z
- Files changed: 12 files
- Commits: 1 commits
Implementation approach:
Reverts juspay/hyperswitch#5801
</think>
To implement this, you'll need to modify:
**Detailed Implementation:**
**Commit 1:** feat(rout... | {"issue_number": 5801, "pr_number": 6142, "commits_count": 1, "files_changed": 12, "response_length": 1333, "file_count": 12, "needs_breakdown": false} |
feat(router): Add support for network token migration
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [ ] New feature
- [x] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
<!-- Describe your changes in detail -->
Add supp... | <think>
PR Context:
- Title: fix(router): validate each field for migration request body
- Merged: 2024-12-06T11:44:36Z
- Files changed: 1 files
- Commits: 15 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
#6300 has inconsistent response due to no validations for each field... | {"issue_number": 6300, "pr_number": 6525, "commits_count": 1, "files_changed": 1, "response_length": 987, "file_count": 3, "needs_breakdown": false} |
doc: documentation for payment method routes
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [x] Enhancement
## Description
<!-- Describe your changes in detail -->
Written documentation for Payment Method routes
## Motivation and Context
<!--
Why is this change required? What problem doe... | <think>
PR Context:
- Title: build(deps): use utoipa crate upstream URL as git dependency
- Merged: 2023-01-16T09:12:32Z
- Files changed: 5 files
- Commits: 4 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
This PR updates the repository URL for the `utoipa` crate to use the... | {"issue_number": 436, "pr_number": 378, "commits_count": 1, "files_changed": 5, "response_length": 937, "file_count": 3, "needs_breakdown": false} |
[REFACTOR] : [Stax] Error Message For Connector Implementation
### :memo: Feature Description
- In terms of errors, we are currently throwing a 'not supported' message, which shouldn't be the case as we are yet to decide on the implementation.
### :hammer: Possible Implementation
- In order to manage paymen... | <think>
PR Context:
- Title: refactor(connector): [Stax] change error message from NotSupported to NotImplemented
- Merged: 2023-11-29T18:27:28Z
- Files changed: 1 files
- Commits: 2 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
### Additional Changes
- [ ] This PR ... | {"issue_number": 2862, "pr_number": 2879, "commits_count": 1, "files_changed": 1, "response_length": 1004, "file_count": 3, "needs_breakdown": false} |
[FEATURE] statement_descriptor_suffix and statement_descriptor_name not being sent to Adyen. Please implement.
### Feature Description
It is important to be able to have custom statements (and also it is available feature on Stripe), so it should be on Adyen as well.
### Possible Implementation
It should propagate ... | <think>
PR Context:
- Title: refactor(connector): [adyen] add more fields in the payments request
- Merged: 2024-03-11T10:13:22Z
- Files changed: 3 files
- Commits: 6 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
- Add shopper statement and metadata in payments request
... | {"issue_number": 3914, "pr_number": 4010, "commits_count": 2, "files_changed": 3, "response_length": 2537, "file_count": 5, "needs_breakdown": false} |
feat(connector): Add recovery support for stripebilling
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [x] New feature
- [x] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
Context: In case of some billing connectors we d... | <think>
PR Context:
- Title: feat(recovery-events): add revenue recovery topic and vector config to push these events to s3
- Merged: 2025-07-25T12:00:14Z
- Files changed: 22 files
- Commits: 30 commits
Implementation approach:
## Description
This new Kafka Event consume the revenue recovery related events which wil... | {"issue_number": 7461, "pr_number": 8285, "commits_count": 1, "files_changed": 22, "response_length": 2621, "file_count": 18, "needs_breakdown": true} |
refactor(users): Force 2FA in prod env
Currently 2FA is not forced on prod, users have ability to skip it.
For the PCI compliance, we have to force users to setup and use 2FA. | <think>
PR Context:
- Title: refactor(users): Force 2FA in production environment
- Merged: 2024-11-19T13:18:51Z
- Files changed: 1 files
- Commits: 2 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
This PR forces users to use 2FA in production.
### Additional Changes
... | {"issue_number": 6592, "pr_number": 6596, "commits_count": 0, "files_changed": 1, "response_length": 782, "file_count": 0, "needs_breakdown": false} |
feat(auth): Support profile level authentication
- After the dashboard is changed to profile level, there will be 3 types of APIs based on the level
1. Merchant Level only
- API Keys
- Merchant Account
- Business profile
2. Profile Level only
- Connectors
- Routing
- Operations (Payment, refund, dispute... | <think>
PR Context:
- Title: refactor(auth): Pass `profile_id` from the auth to core functions
- Merged: 2024-08-05T11:37:32Z
- Files changed: 5 files
- Commits: 2 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
Use the profile_id from the authentication data and pass it to ... | {"issue_number": 5491, "pr_number": 5520, "commits_count": 1, "files_changed": 5, "response_length": 1452, "file_count": 7, "needs_breakdown": false} |
feat(analytics): Analytics Request Validator and config driven forex feature
## Current behaviour
- Forex api calls are occuring on every analytics api call
- There is no analytics request validator.
## Proposed Changes
- Enable/Disable forex functionality based on a config flag.
- `request_validator()` to validate... | <think>
PR Context:
- Title: feat(analytics): Analytics Request Validator and config driven forex feature
- Merged: 2024-12-17T10:50:36Z
- Files changed: 16 files
- Commits: 16 commits
Implementation approach:
## Fixes #6731
## Description
<!-- Describe your changes in detail -->
### Config driven forex functio... | {"issue_number": 6731, "pr_number": 6733, "commits_count": 1, "files_changed": 16, "response_length": 2201, "file_count": 14, "needs_breakdown": false} |
[FEATURE] add domain type for client secret
### Feature Description
Create domain type for client secret
### Possible Implementation
Make type `ClietSecret(String)` and use it wherever applicable
### Have you spent some time to check if this feature request has been raised before?
- [X] I checked and didn't find... | <think>
PR Context:
- Title: feat(api_models): add client_secret type to payments
- Merged: 2024-02-15T06:49:24Z
- Files changed: 1 files
- Commits: 6 commits
Implementation approach:
## Description
Implement `ClientSecret` type for payments.
Closes #1357
### Additional Changes
- [ ] This PR modifies th... | {"issue_number": 1357, "pr_number": 3557, "commits_count": 1, "files_changed": 1, "response_length": 1465, "file_count": 3, "needs_breakdown": false} |
Add tenant_id as a field for data pipeline
1. Add `Tenant_id` as a field for all logs
2. Add `Tenant_id` action for Kafka messages as well , headers to be a combination of ( tenant_id, merchant_id, payment_id )
3. Make logical databases and physical tables in clickhouse for different tenants | <think>
PR Context:
- Title: fix(multitenancy): remove tenant id from redis stream key of kafkaStore
- Merged: 2024-06-10T13:57:26Z
- Files changed: 1 files
- Commits: 1 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
As part of multitenancy feature, we added tenant prefix i... | {"issue_number": 4475, "pr_number": 4916, "commits_count": 1, "files_changed": 1, "response_length": 965, "file_count": 3, "needs_breakdown": false} |
[FEATURE] Use newtype pattern for email addresses
### Feature Description
This issue covers one of the problems mentioned in #119, about using [the newtype pattern](https://rust-unofficial.github.io/patterns/patterns/behavioural/newtype.html) for email addresses. The requirement is that email addresses must be vali... | <think>
PR Context:
- Title: refactor: use newtype pattern for email addresses
- Merged: 2023-05-04T14:24:44Z
- Files changed: 30 files
- Commits: 26 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
- This fixes #608
- Added testcases
### Additional Changes
- [ ] This... | {"issue_number": 608, "pr_number": 819, "commits_count": 1, "files_changed": 30, "response_length": 3491, "file_count": 30, "needs_breakdown": true} |
fix(authz): Proper descriptions for parents
Currently descriptions for parent groups in invite page of control center are not entity specific. That means, customers in description will be visible for profile level users when it shouldn't. | <think>
PR Context:
- Title: feat(authz): Make info APIs support `ParentGroup`
- Merged: 2024-10-30T10:42:37Z
- Files changed: 13 files
- Commits: 8 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
Make new APIs to replace
- `/user/role/{{role_id}}` -> `/user/role/{{role_id}... | {"issue_number": 6439, "pr_number": 6440, "commits_count": 1, "files_changed": 13, "response_length": 2316, "file_count": 15, "needs_breakdown": false} |
[BUG] connector_request_reference_id not updated in payment_tokenization confirm_intent flow
### Bug Description
In the payment tokenization confirm intent flow, the field `connector_request_reference_id` is not being updated in payment_attempt. Because of this missing update, flows such as PaymentsCancel and Payment... | <think>
PR Context:
- Title: fix(payment): add connector_request_reference_id to PaymentAttemptUpdate in ConfirmIntentTokenized flow
- Merged: 2025-10-01T13:42:36Z
- Files changed: 2 files
- Commits: 1 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
In the payment tokeniza... | {"issue_number": 9596, "pr_number": 9597, "commits_count": 1, "files_changed": 2, "response_length": 1144, "file_count": 4, "needs_breakdown": false} |
make `ApplepayPaymentMethod` in payment_method_data column of `payment_attempt` table as json
make `ApplepayPaymentMethod` in payment_method_data column of `payment_attempt` table as json because retrieve payment fails for the old payments for which the `payment_method_data` in the `payment_attempt` table was stored ... | <think>
PR Context:
- Title: fix(payment_methods): make ApplepayPaymentMethod in payment_method_data column of payment_attempt table as json
- Merged: 2024-03-20T13:42:02Z
- Files changed: 2 files
- Commits: 1 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
make ApplepayPaym... | {"issue_number": 4153, "pr_number": 4154, "commits_count": 1, "files_changed": 2, "response_length": 1107, "file_count": 4, "needs_breakdown": false} |
feat(payments_v2): implement create and confirm intent flow
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [x] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
<!-- Describe your changes in detail -->
... | <think>
PR Context:
- Title: feat(router): [V2] Return connector customer reference IDs in `CustomerResponse`
- Merged: 2025-03-21T13:58:53Z
- Files changed: 8 files
- Commits: 8 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
Add a field `connector_customer` to `CustomerRes... | {"issue_number": 7106, "pr_number": 7319, "commits_count": 1, "files_changed": 8, "response_length": 1761, "file_count": 8, "needs_breakdown": false} |
fix(router): connecconnector name not saved in payment_attempt & connector_response tables
## Type of Change
- [x] Bugfix
## Description
The connector name was not being saved in
1. Payment Attempt table in both error and success cases.
2. Connector Response table in error cases.
Fixed this by including `c... | <think>
PR Context:
- Title: feat(payout_link): secure payout links using server side validations and client side headers
- Merged: 2024-07-17T13:18:28Z
- Files changed: 23 files
- Commits: 23 commits
Implementation approach:
## Description
This PR includes below changes -
- adding `allowed_domains` field in payout... | {"issue_number": 143, "pr_number": 5219, "commits_count": 1, "files_changed": 23, "response_length": 2564, "file_count": 18, "needs_breakdown": true} |
[FEAT] Multiple credential support for a connector in Cypress
## Requirement
Execute cypress tests for a connector having **multiple credentials** which can be used for different scenarios (one api key for `cards`, another for `bank redirects` and etc.,).
## Implementation
### Introduce new format for `creds.... | <think>
PR Context:
- Title: ci: update cypress creds
- Merged: 2024-12-03T17:19:14Z
- Files changed: 1 files
- Commits: 2 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
Updates creds. closes #6645
### Additional Changes
- [ ] This PR modifies the API contract
- [ ... | {"issue_number": 6645, "pr_number": 6726, "commits_count": 0, "files_changed": 1, "response_length": 754, "file_count": 0, "needs_breakdown": false} |
chore(codeowners): add codeowners data for PR reviews
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [ ] New feature
- [x] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
## Description
Adding a CODEOWNERS file for facilitating PR reviews for teams
### Additional... | <think>
PR Context:
- Title: feat(core): Add click to pay support in hyperswitch
- Merged: 2024-12-16T14:25:44Z
- Files changed: 30 files
- Commits: 30 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
Add click to pay and unified authentication service integration in core
... | {"issue_number": 1, "pr_number": 6769, "commits_count": 1, "files_changed": 30, "response_length": 11983, "file_count": 42, "needs_breakdown": true} |
[REFACTOR] : [Multisafepay] Error Message For Connector Implementation
### :memo: Feature Description
- In terms of errors, we are currently throwing a 'not supported' message, which shouldn't be the case as we are yet to decide on the implementation.
### :hammer: Possible Implementation
- In order to manag... | <think>
PR Context:
- Title: refactor(connector): [Multisafe Pay] change error message from not supported to not implemented
- Merged: 2023-11-30T19:06:32Z
- Files changed: 1 files
- Commits: 3 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
### Additional Changes
- [... | {"issue_number": 2842, "pr_number": 2851, "commits_count": 1, "files_changed": 1, "response_length": 1031, "file_count": 3, "needs_breakdown": false} |
[FEATURE]: [Dlocal] 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 trans... | <think>
PR Context:
- Title: feat(connector): [Dlocal] Use connector_response_reference_id as reference to merchant
- Merged: 2023-10-15T09:15:45Z
- Files changed: 1 files
- Commits: 9 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
I have populated the 'id' which is pr... | {"issue_number": 2328, "pr_number": 2446, "commits_count": 1, "files_changed": 1, "response_length": 1010, "file_count": 3, "needs_breakdown": false} |
Vault connector changes
Need to implement Vault Retrieve for VGS | <think>
PR Context:
- Title: feat(connector): Add VGS connector impls
- Merged: 2025-08-25T09:52:19Z
- Files changed: 14 files
- Commits: 13 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
- Added Connector changes for VGS
- Implemented `ExternalVaultInsertFlow` and `Extern... | {"issue_number": 9023, "pr_number": 7942, "commits_count": 1, "files_changed": 14, "response_length": 3938, "file_count": 9, "needs_breakdown": false} |
fix: revert mget use authorization
In the hosted environment, where we have multiple redis clusters `mget` is not working as expected and throwing the following error: `Unknown Error: CROSSSLOT Keys in request don't hash to the same slot`.
Temporary fix is to revert the PR which is using `mget` | <think>
PR Context:
- Title: fix(users): revert using mget in authorization
- Merged: 2024-03-07T08:22:10Z
- Files changed: 1 files
- Commits: 1 commits
Implementation approach:
## Description
`mget` is not working in the hosted version. So, this PR will revert the #3945 which uses `mget``.
### Additional Changes... | {"issue_number": 4000, "pr_number": 3999, "commits_count": 1, "files_changed": 1, "response_length": 934, "file_count": 3, "needs_breakdown": false} |
[BUG] payout routing for Sepa transactions result in a 4xx error
### Bug Description
Creating payout transactions for SEPA are resulting in a 4xx error with below message.
```
{
"error": {
"type": "invalid_request",
"message": "No eligible connector was found for the current payment method config... | <think>
PR Context:
- Title: chore(wasm): update sepa to sepa_bank_transfer for payout MCAs
- Merged: 2025-09-25T07:49:03Z
- Files changed: 3 files
- Commits: 1 commits
Implementation approach:
## Description
This PR updates the payout MCA creation to use `sepa_bank_transfer` instead of `sepa`.
### Additional Cha... | {"issue_number": 8168, "pr_number": 9536, "commits_count": 0, "files_changed": 3, "response_length": 792, "file_count": 0, "needs_breakdown": false} |
feat(connector): [Square] Use connector_request_reference_id as reference to connector.
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [x] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
Using connector_... | <think>
PR Context:
- Title: feat(connector): [RISKIFIED] Add support for riskified frm connector
- Merged: 2023-12-12T13:23:22Z
- Files changed: 30 files
- Commits: 30 commits
Implementation approach:
## Description
Add support for Riskified FRM Connector.
This PR resolves the problem mentioned in issue [#2453](ht... | {"issue_number": 2453, "pr_number": 2533, "commits_count": 1, "files_changed": 30, "response_length": 13334, "file_count": 54, "needs_breakdown": true} |
[REFACTOR] provide an identifier for the api key in the expiry reminder email
### Issue Description:
Currently, our system sends out reminder emails to merchants when their API key is about to expire. However, since merchants can create multiple API keys, the email lacks clarity on which specific API key is expirin... | <think>
PR Context:
- Title: refactor(api_keys): provide identifier for api key in the expiry reminder email
- Merged: 2024-03-04T14:19:34Z
- Files changed: 5 files
- Commits: 4 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
Refactored the api key expiry reminder workflow t... | {"issue_number": 3801, "pr_number": 3888, "commits_count": 1, "files_changed": 5, "response_length": 1202, "file_count": 6, "needs_breakdown": false} |
[FEATURE]: Add `Payment Method - Delete` endpoint to payment methods session for V2
Required for Payment Methods Service | <think>
PR Context:
- Title: feat(router): Add payment_methods_session_delete_payment_method endpoint [V2]
- Merged: 2025-03-27T12:05:05Z
- Files changed: 11 files
- Commits: 12 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
This endpoint allows deleting saved payment met... | {"issue_number": 7407, "pr_number": 7409, "commits_count": 1, "files_changed": 11, "response_length": 1678, "file_count": 10, "needs_breakdown": false} |
Adding new logo in API ref and Readme | <think>
PR Context:
- Title: docs: add new logos for README and API reference
- Merged: 2024-12-10T11:57:39Z
- Files changed: 6 files
- Commits: 15 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
### Additional Changes
- [ ] This PR modifies the API contract
- [ ] Th... | {"issue_number": 6782, "pr_number": 6783, "commits_count": 0, "files_changed": 6, "response_length": 779, "file_count": 0, "needs_breakdown": false} |
[FEATURE] Extend storage of additional payment method details to wallets
### Feature Description
Wallet integrations like ApplePay and GooglePay makes use of a tokenized network token which is collected on client's device and sent to underlying PSPs for completing the txns. The intermediary parties do not have any ac... | <think>
PR Context:
- Title: feat(payments): store and propagate additional wallet pm details in payments response
- Merged: 2024-09-19T13:50:57Z
- Files changed: 7 files
- Commits: 6 commits
Implementation approach:
## Description
Described in #5868
### Additional Changes
- [x] This PR modifies the API contr... | {"issue_number": 5868, "pr_number": 5869, "commits_count": 1, "files_changed": 7, "response_length": 1297, "file_count": 7, "needs_breakdown": false} |
[REFACTOR] Update KafkaStore to hold variables for tenant ID
Update the [`KafkaStore`](https://github.com/juspay/hyperswitch/blob/c20ecb855aa3c4b3ce1798dcc19910fb38345b46/crates/router/src/db/kafka_store.rs#L75-L79) to hold a variable for tenant-ID.
This can be achieved by simply adding a new field in the `KafkaSto... | <think>
PR Context:
- Title: refactor(db): Add TenantId field to the KafkaStore struct
- Merged: 2024-05-08T13:19:57Z
- Files changed: 3 files
- Commits: 7 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
- Add TenantId field to the KafkaStore struct
- Add the tenant_id para... | {"issue_number": 4496, "pr_number": 4512, "commits_count": 1, "files_changed": 3, "response_length": 1115, "file_count": 5, "needs_breakdown": false} |
bug(users): Mark users as verified if user comes from SSO
- Currently we are not marking users as verified if they use SSO to login.
- But if there is only SSO to login, then they won't be able to verify their email unless they come from the accept invite email.
- Instead, we will mark users coming from SSO as verifie... | <think>
PR Context:
- Title: fix(users): Mark user as verified if user logins from SSO
- Merged: 2024-11-29T10:52:38Z
- Files changed: 1 files
- Commits: 1 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
Currently we are not marking users as verified if the user comes from S... | {"issue_number": 6693, "pr_number": 6694, "commits_count": 1, "files_changed": 1, "response_length": 932, "file_count": 3, "needs_breakdown": false} |
[FEATURE] Allow rotating and revoking API keys
### Feature Description
As of now, the `merchant_account` table has an `api_key` field which restricts a merchant account to only have one API key. Furthermore, there are no mechanisms in place to revoke and regenerate API keys. To improve the convenience of rotating and... | <think>
PR Context:
- Title: feat(router): implement API endpoints for managing API keys
- Merged: 2023-02-10T09:06:18Z
- Files changed: 30 files
- Commits: 21 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
This PR implements the endpoints to create, retrieve, update, revok... | {"issue_number": 501, "pr_number": 511, "commits_count": 1, "files_changed": 30, "response_length": 6696, "file_count": 31, "needs_breakdown": true} |
feat(invite): Send email to user if user already exist | <think>
PR Context:
- Title: feat(pm_list): add required fields for google pay
- Merged: 2024-01-31T09:45:43Z
- Files changed: 1 files
- Commits: 9 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
Resolves [#3706](https://github.com/juspay/hyperswitch-cloud/issues/3706)
##... | {"issue_number": 3706, "pr_number": 3196, "commits_count": 1, "files_changed": 1, "response_length": 966, "file_count": 3, "needs_breakdown": false} |
refactor: change create and update role apis to respond with role info | <think>
PR Context:
- Title: refactor(roles): Add more checks in create, update role APIs and change the response type
- Merged: 2024-02-29T14:11:09Z
- Files changed: 4 files
- Commits: 5 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
This PR modifies create and update role... | {"issue_number": 3895, "pr_number": 3896, "commits_count": 1, "files_changed": 4, "response_length": 1262, "file_count": 6, "needs_breakdown": false} |
feat(single_use): add extra fields in `Mandate` table and `MandateData` [Blocked on #61]
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [x] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
## Description
This PR adds single use mandate support and a 2 n... | <think>
PR Context:
- Title: feat: add test_mode for quickly testing payout links
- Merged: 2024-08-27T08:31:54Z
- Files changed: 11 files
- Commits: 8 commits
Implementation approach:
## Description
Described in #5668
### Additional Changes
- [x] This PR modifies the API contract
- [ ] This PR modifies the ... | {"issue_number": 66, "pr_number": 5669, "commits_count": 1, "files_changed": 11, "response_length": 1431, "file_count": 10, "needs_breakdown": false} |
[FEATURE] Validate card numbers when accepting payment method information
### Feature Description
As of now, we just pass the card information to the payment processor without performing any form of validation on the provided card number. It'd be great if the card number could have been validated on our end wheneve... | <think>
PR Context:
- Title: feat(cards): add credit card number validation
- Merged: 2023-05-09T15:06:39Z
- Files changed: 30 files
- Commits: 6 commits
Implementation approach:
Fixes #606
## Description
<!-- Describe your changes in detail -->
The PR adds a new crate called `cards`. Which currently just has a ... | {"issue_number": 606, "pr_number": 889, "commits_count": 1, "files_changed": 30, "response_length": 8780, "file_count": 77, "needs_breakdown": true} |
[BUG]: [Adyen] Webhook Psync response Handler
### Bug Description
Currently the Psync response handler for webhook tightly coupled to payments response which is creating a lot of bugs in status and transaction id updates
- Update Psync response handler to consume the incoming webhook response
- Handle Webhook Sta... | <think>
PR Context:
- Title: fix(connector): [adyen] handle Webhook reference and object
- Merged: 2024-03-06T14:43:23Z
- Files changed: 2 files
- Commits: 5 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
- Update Psync response handler to consume the incoming webhook respo... | {"issue_number": 3977, "pr_number": 3976, "commits_count": 1, "files_changed": 2, "response_length": 1651, "file_count": 4, "needs_breakdown": false} |
[FEATURE]: [Cybersource] Add 3DS flow for cards
### Feature Description
Add 3DS flow for cards
### Possible Implementation
Add 3DS flow for cards
### 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 you read the Contribut... | <think>
PR Context:
- Title: feat(connector): [cybersource] Implement 3DS flow for cards
- Merged: 2024-01-11T15:20:46Z
- Files changed: 13 files
- Commits: 29 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
Implement 3DS flow for cards
```
Legend:
UB: User Browser
M:... | {"issue_number": 3296, "pr_number": 3290, "commits_count": 1, "files_changed": 13, "response_length": 3043, "file_count": 12, "needs_breakdown": false} |
feat(core): Added integrity framework for Authorize and Sync flow with connector as Stripe
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [x] New feature
## Description
<!-- Describe your changes in detail -->
With this PR, we are implementing connector integrity checks for the authorize and ... | <think>
PR Context:
- Title: Revert "feat(core): Added integrity framework for Authorize and Sync flow with connector as Stripe"
- Merged: 2024-06-24T14:30:07Z
- Files changed: 30 files
- Commits: 1 commits
Implementation approach:
Reverts juspay/hyperswitch#5057
</think>
To implement this, you'll need to modify:
(N... | {"issue_number": 5057, "pr_number": 5108, "commits_count": 0, "files_changed": 30, "response_length": 361, "file_count": 0, "needs_breakdown": false} |
[FEATURE] Create a dummy connector for internal and external testing of payments and refunds flows
### Feature Description
A dummy test connector needs to be created with the ability to process all the payment methods available on Hyperswitch. This dummy connector will be useful for internal and external testing an... | <think>
PR Context:
- Title: feat(connector): add multiple dummy connectors and enable them
- Merged: 2023-05-13T11:12:49Z
- Files changed: 6 files
- Commits: 2 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
Add multiple dummy connectors and enable dummy connector by defaul... | {"issue_number": 726, "pr_number": 1147, "commits_count": 1, "files_changed": 6, "response_length": 7521, "file_count": 7, "needs_breakdown": true} |
feat(connector): [Peach Payments] add network token support for connector
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [ ] New feature
- [x] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
<!-- Describe your changes in ... | <think>
PR Context:
- Title: feat(connector): [Peach Payments] add network token support for connector
- Merged: 2025-10-13T14:00:59Z
- Files changed: 8 files
- Commits: 1 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
add network token support for peach payments connector
... | {"issue_number": 9754, "pr_number": 9814, "commits_count": 1, "files_changed": 8, "response_length": 1940, "file_count": 4, "needs_breakdown": false} |
Fix: populating the docker related changes from main to stable release
Replicating
https://github.com/juspay/hyperswitch/issues/8091
https://github.com/juspay/hyperswitch/pull/8092
to stable release | <think>
PR Context:
- Title: fix: updated the docker setup
- Merged: 2025-05-22T09:46:58Z
- Files changed: 2 files
- Commits: 2 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
Enhanced the script to pre-configure a user and a dummy connector in the control center for the loc... | {"issue_number": 8094, "pr_number": 8092, "commits_count": 0, "files_changed": 2, "response_length": 759, "file_count": 0, "needs_breakdown": false} |
[BUG] : Noon Api Contract Changes
### Bug Description
Noon API contract has changed. Therefore subscription payments is failing in Noon sandbox.
### Expected Behavior
Noon subscriptions work in sandbox
### Actual Behavior
Throwing Missing Field error
### Steps To Reproduce
Provide an unambiguous set of steps to... | <think>
PR Context:
- Title: refactor: [Noon] add new field max_amount to mandate request
- Merged: 2024-02-07T09:32:34Z
- Files changed: 2 files
- Commits: 18 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
Resolves #3445
_Note
1.While connector create ensure `test_mode... | {"issue_number": 3445, "pr_number": 3481, "commits_count": 1, "files_changed": 2, "response_length": 1081, "file_count": 4, "needs_breakdown": false} |
[FEATURE] : [Billwerk] Add Payment and Refund Flows
### Feature Description
Add all the payment flows for non-3ds cards:
Authorise, Capture, Void, Psync
And the refund flows:
Refund and Rsync
### Possible Implementation
Add all the payment flows for non-3ds cards:
Authorise, Capture, Void, Psync
And the refun... | <think>
PR Context:
- Title: feat(connector): [billwerk] implement payment and refund flows
- Merged: 2024-04-01T14:31:48Z
- Files changed: 20 files
- Commits: 25 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
implement all the basic flows for Billwerk (Reepay):
- [Autho... | {"issue_number": 4246, "pr_number": 4245, "commits_count": 1, "files_changed": 20, "response_length": 3540, "file_count": 11, "needs_breakdown": false} |
[FEATURE] : [Cybersource] Add Card holder name in dynamic field
### Feature Description
Add Card holder name as required field in dynamic field
### Possible Implementation
Add Card holder name as required field in dynamic field in `default.rs`
### Have you spent some time checking if this feature request has been ... | <think>
PR Context:
- Title: feat(connector): [cybersource] add card holder name in dynamic fields
- Merged: 2024-03-14T07:45:28Z
- Files changed: 1 files
- Commits: 1 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
add card holder name as a required field in dynamic fields ... | {"issue_number": 4083, "pr_number": 4082, "commits_count": 1, "files_changed": 1, "response_length": 963, "file_count": 3, "needs_breakdown": false} |
[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 the sa... | <think>
PR Context:
- Title: fix(connector): add config cleanup on payment connector deletion
- Merged: 2024-12-06T08:36:24Z
- Files changed: 2 files
- Commits: 7 commits
Implementation approach:
## Description
Fixes #5966 (in both v1 and v2). Now the router cleans up the configs table (or business_profile in v2) wh... | {"issue_number": 5966, "pr_number": 5998, "commits_count": 1, "files_changed": 2, "response_length": 1291, "file_count": 4, "needs_breakdown": false} |
Pre-configuring an account in the local setup using docker
Pre-configuring an account in the local setup using docker | <think>
PR Context:
- Title: fix: updated the docker setup
- Merged: 2025-05-21T09:51:53Z
- Files changed: 2 files
- Commits: 3 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
Enhanced the script to pre-configure a user and a dummy connector in the control center for the loc... | {"issue_number": 8091, "pr_number": 8093, "commits_count": 0, "files_changed": 2, "response_length": 759, "file_count": 0, "needs_breakdown": false} |
Implement `EphemeralKeyInterface` for `MockDb`
Spin out from https://github.com/juspay/hyperswitch/issues/172. Please refer to that issue for more information. | <think>
PR Context:
- Title: feat(db): implement `EphemeralKeyInterface` for `MockDb`
- Merged: 2023-06-25T05:52:25Z
- Files changed: 3 files
- Commits: 6 commits
Implementation approach:
## Description
Implemented Mock db for ephemeral key
### Additional Changes
- [ ] This PR modifies the API contract
- [ ... | {"issue_number": 1191, "pr_number": 1285, "commits_count": 1, "files_changed": 3, "response_length": 1052, "file_count": 5, "needs_breakdown": false} |
feat: add cache for MCA and API key tables.
Add support for in memory and redis cache for Merchant Connector Account and API keys tables to the functions that are frequently called for less latency during payments. | <think>
PR Context:
- Title: feat: add cache for api_key and mca tables
- Merged: 2023-07-07T07:08:21Z
- Files changed: 3 files
- Commits: 10 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
This PR adds in memory and redis cache for Merchant Connector Account and API keys. T... | {"issue_number": 1211, "pr_number": 1212, "commits_count": 1, "files_changed": 3, "response_length": 1174, "file_count": 5, "needs_breakdown": false} |
fix(mandate): add mandate_id column in payment_attempt table
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [ ] New feature
- [x] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
## Description
This change includes
- Adding a new column `mandate_id` in the table `paymen... | <think>
PR Context:
- Title: fix(router): fixed integrity check failures in case of 3ds flow in sync flow
- Merged: 2024-07-12T00:04:26Z
- Files changed: 12 files
- Commits: 5 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
we have implemented integrity checks for stripe, we... | {"issue_number": 3, "pr_number": 5279, "commits_count": 1, "files_changed": 12, "response_length": 1800, "file_count": 14, "needs_breakdown": false} |
Updating the API reference documentation - payments
We have had feedback related to the API doc being outdated, and lacking proper visibility of the latest spec of the API collection. | <think>
PR Context:
- Title: Docs: Updated API - ref for payments
- Merged: 2024-07-04T13:33:48Z
- Files changed: 4 files
- Commits: 13 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
### Additional Changes
- [ ] This PR modifies the API contract
- [ ] This PR modifi... | {"issue_number": 5174, "pr_number": 5172, "commits_count": 1, "files_changed": 4, "response_length": 1077, "file_count": 5, "needs_breakdown": false} |
[CI] Add workflow to ensure a pull request contains at least one linked issue
### Description
Add a CI workflow to ensure that each pull request contains at least one linked issue. We wish to introduce this requirement for improved project tracking. The workflow should do nothing else: just succeed/fail the check b... | <think>
PR Context:
- Title: ci(pr-convention-checks): add job to check for linked issues for pull requests
- Merged: 2024-01-19T06:54:05Z
- Files changed: 2 files
- Commits: 10 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
This PR adds a new pull request CI check to ensur... | {"issue_number": 3375, "pr_number": 3376, "commits_count": 0, "files_changed": 2, "response_length": 809, "file_count": 0, "needs_breakdown": false} |
Connector changes for 3ds in v2
In v2, the `PreProcessing` and `CompleteAuthorize` flows will not be present.
We will introduce new flows `PreAuthenticate`, `Authenticate` and `PostAuthenticate` to better represent the domain. | <think>
PR Context:
- Title: feat(router): Add Connector changes for 3ds (v2)
- Merged: 2025-09-11T14:33:57Z
- Files changed: 8 files
- Commits: 1 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
- Add `PreAuthenticate`, `Authenticate` and `PostAuthenticate` connector integ... | {"issue_number": 9116, "pr_number": 9117, "commits_count": 1, "files_changed": 8, "response_length": 5050, "file_count": 10, "needs_breakdown": true} |
fix(payments): populate merchant order reference id in payments list response
In payment list response populate merchant order reference id | <think>
PR Context:
- Title: fix(payments): populate merchant order ref id in list
- Merged: 2024-07-12T11:51:05Z
- Files changed: 1 files
- Commits: 1 commits
Implementation approach:
## Description
Populate merchant order reference id in payments list response
### Additional Changes
- [ ] This PR modifies th... | {"issue_number": 5309, "pr_number": 5310, "commits_count": 2, "files_changed": 1, "response_length": 1112, "file_count": 5, "needs_breakdown": false} |
feat(payments): show aggregate count of payment status
Show count of aggregate payments status in the given time range:
This can be part of filter Api. | <think>
PR Context:
- Title: feat(payments): add support for aggregates in payments
- Merged: 2024-08-21T13:01:59Z
- Files changed: 12 files
- Commits: 2 commits
Implementation approach:
## Description
- The endpoint `/aggrega... | {"issue_number": 5627, "pr_number": 5654, "commits_count": 1, "files_changed": 12, "response_length": 2049, "file_count": 14, "needs_breakdown": false} |
[FEATURE]: [Bambora] 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 uniformity in ... | <think>
PR Context:
- Title: feat(connector): [Bambora] use connector_request_reference_id
- Merged: 2023-10-18T10:45:39Z
- Files changed: 1 files
- Commits: 17 commits
Implementation approach:
Addresses #2293
## Description
<!-- Describe your changes in detail -->
This PR updates the use of `RequestData.request... | {"issue_number": 2293, "pr_number": 2518, "commits_count": 1, "files_changed": 1, "response_length": 962, "file_count": 3, "needs_breakdown": false} |
feat: Create new versions of BE pre-login APIs
Currently we've made SPT and decision starter APIs. Now we have to integrate SPT into email specific, signin and signup APIs.
For backwards compatibility, old version should also need to be kept. So we can do these new APIs accessible with a query param. | <think>
PR Context:
- Title: feat(users): Create Token only support for pre-login user flow APIs
- Merged: 2024-05-07T09:41:39Z
- Files changed: 8 files
- Commits: 11 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
This PR will add new core functions for the following APIs w... | {"issue_number": 4556, "pr_number": 4558, "commits_count": 1, "files_changed": 8, "response_length": 1796, "file_count": 10, "needs_breakdown": false} |
refactor: Separate out recovery codes from TOTP
Even though recovery codes is dependent entity on TOTP. But the new findings suggest that TOTP is a part of entity called 2FA and TOTP is depended on the 2FA entity not the TOTP entity.
This will be more clear when we add multiple 2FAs like SMS OTP.
So, we want to sepa... | <think>
PR Context:
- Title: feat(users): Create generate recovery codes API
- Merged: 2024-05-22T08:42:47Z
- Files changed: 11 files
- Commits: 3 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
Currently recovery code are being generated in `begin_totp` API. We want to make... | {"issue_number": 4707, "pr_number": 4708, "commits_count": 1, "files_changed": 11, "response_length": 1811, "file_count": 13, "needs_breakdown": false} |
[FEATURE]: [Cybersource] Currency Unit Conversion
### :memo: Feature Description
- Each currency can be described in terms of base or minor units.
- For instance, when dealing with USD currency, the Cent is considered as the minor unit, while the Dollar is considered the base unit.
- In Hyperswitch, the amount valu... | <think>
PR Context:
- Title: refactor(connector): [CyberSource] Enhance currency Mapping with ConnectorCurrencyCommon Trait
- Merged: 2023-10-25T09:38:44Z
- Files changed: 3 files
- Commits: 10 commits
Implementation approach:
## Description
This PR implements `get_currency_unit` for cybersource to convert payments ... | {"issue_number": 2222, "pr_number": 2626, "commits_count": 1, "files_changed": 3, "response_length": 1415, "file_count": 5, "needs_breakdown": false} |
[FEATURE]: [Rapyd] Currency Unit Conversion
### :memo: Feature Description
- Each currency can be described in terms of base or minor units.
- For instance, when dealing with USD currency, the Cent is considered as the minor unit, while the Dollar is considered the base unit.
- In Hyperswitch, the amount value is e... | <think>
PR Context:
- Title: refactor(connector): [Rapyd] add and implement the get_currency_unit function
- Merged: 2023-10-27T13:17:37Z
- Files changed: 2 files
- Commits: 18 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
This PR solves issue number #2244 for currency uni... | {"issue_number": 2244, "pr_number": 2664, "commits_count": 2, "files_changed": 2, "response_length": 1823, "file_count": 7, "needs_breakdown": false} |
fix(connector): [Cybersource] change commerce indicator for applepay
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [x] Bugfix
- [ ] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
<!-- Describe your changes in detai... | <think>
PR Context:
- Title: fix(connector): [Cybersource] change commerce indicator for applepay
- Merged: 2024-11-27T11:30:18Z
- Files changed: 1 files
- Commits: 1 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
Change the commerce indicator for cybersource applepay payme... | {"issue_number": 6634, "pr_number": 6675, "commits_count": 1, "files_changed": 1, "response_length": 979, "file_count": 3, "needs_breakdown": false} |
feat(webhooks): allow manually retrying delivery of outgoing webhooks
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [x] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
<!-- Describe your changes in deta... | <think>
PR Context:
- Title: refactor(webhook_events): allow listing unique webhook events based on profile ID
- Merged: 2024-08-14T09:51:26Z
- Files changed: 15 files
- Commits: 3 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
This PR adds back a feature that was removed... | {"issue_number": 4176, "pr_number": 5598, "commits_count": 1, "files_changed": 15, "response_length": 2107, "file_count": 13, "needs_breakdown": false} |
[REFACTOR]: [Dlocal] Remove Default Case Handling
### :memo: Feature Description
- We utilize match statements to make pivotal decisions, such as generating requests based on the payment method type and managing responses received from the connector.
- These conditions generally go hand in hand with enum variants.
... | <think>
PR Context:
- Title: refactor(connector): [Dlocal] remove default case handling
- Merged: 2023-10-19T14:26:05Z
- Files changed: 1 files
- Commits: 4 commits
Implementation approach:
## Description
removed all the default case in dlocal and handle all the missing cases
closes #2269
### Additional Changes... | {"issue_number": 2269, "pr_number": 2624, "commits_count": 1, "files_changed": 1, "response_length": 954, "file_count": 3, "needs_breakdown": false} |
Updating the API reference documentation
We have had feedback related to the API doc being outdated, and lacking proper visibility of the latest spec of the API collection. | <think>
PR Context:
- Title: Docs: Api reference docs update for Payments - Create
- Merged: 2024-06-28T11:47:58Z
- Files changed: 9 files
- Commits: 25 commits
Implementation approach:
## Description
This is regarding the API Reference Doc changes using OpenAPI.
This PR just the doc changes for Payments - Create (... | {"issue_number": 5014, "pr_number": 4955, "commits_count": 1, "files_changed": 9, "response_length": 1399, "file_count": 10, "needs_breakdown": false} |
Force password reset
- Force user to change the password after certain amount of time.
- Force user to set password after user lands to dashboard without setting his/her password (invite flow). | <think>
PR Context:
- Title: feat(users): implement force set and force change password
- Merged: 2024-05-07T14:25:34Z
- Files changed: 25 files
- Commits: 12 commits
Implementation approach:
## Description
- Allow users to set password when newly signing in
- Allow users to force change password after specified du... | {"issue_number": 4411, "pr_number": 4564, "commits_count": 1, "files_changed": 25, "response_length": 2049, "file_count": 18, "needs_breakdown": true} |
feat(connector): Add recovery support for stripebilling
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [x] New feature
- [x] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
Context: In case of some billing connectors we d... | <think>
PR Context:
- Title: feat(core): consume card details from billing connectors and first error codes and store them in payment intent table
- Merged: 2025-06-16T11:39:32Z
- Files changed: 16 files
- Commits: 30 commits
Implementation approach:
## Description
The following details are needed to be stored in th... | {"issue_number": 7461, "pr_number": 8250, "commits_count": 1, "files_changed": 16, "response_length": 3062, "file_count": 17, "needs_breakdown": true} |
[BUG] : Bank Transfer status mapping is wrong for stripe
### Bug Description
While making the payment for bank transfer its going to "processing" state instead of "requires_customer_action".
Even after payment sync also its in processing state.
### Expected Behavior
It should be in "requires_customer_action" state... | <think>
PR Context:
- Title: fix(update_trackers): handle preprocessing steps status update
- Merged: 2023-06-22T04:20:03Z
- Files changed: 9 files
- Commits: 8 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
The status of `router_data` was being updated after update tracker... | {"issue_number": 1495, "pr_number": 1496, "commits_count": 1, "files_changed": 9, "response_length": 1627, "file_count": 11, "needs_breakdown": false} |
ci(connector-sanity-tests): fix invalid YAML syntax
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [ ] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [x] CI/CD
## Description
<!-- Describe your changes in detail -->
This PR fi... | <think>
PR Context:
- Title: ci(connector-sanity-tests): fix no tests being run
- Merged: 2023-05-10T12:55:23Z
- Files changed: 3 files
- Commits: 5 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
This PR fixes no tests being run after my derp in #1099.
## Motivation and ... | {"issue_number": 1099, "pr_number": 1106, "commits_count": 1, "files_changed": 3, "response_length": 1038, "file_count": 4, "needs_breakdown": false} |
fix(docker): currency enum fix for docker config
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [x] Bugfix
- [ ] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD
## Description
<!-- Describe your changes in detail -->
This PR fixes... | <think>
PR Context:
- Title: fix(docker): currency enum fix for docker config
- Merged: 2024-08-09T08:44:39Z
- Files changed: 1 files
- Commits: 1 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
This PR fixes the following bug
```
2024-08-08 21:08:07 thread 'main' panicke... | {"issue_number": 5577, "pr_number": 5578, "commits_count": 0, "files_changed": 1, "response_length": 778, "file_count": 0, "needs_breakdown": false} |
[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 at pres... | <think>
PR Context:
- Title: refactor(cypress): verify payment status after payment redirection
- Merged: 2025-01-13T08:18:18Z
- Files changed: 1 files
- Commits: 26 commits
Implementation approach:
## Description
This PR refactors the verifyReturnUrl function to validate the redirection_url and ensure that the paym... | {"issue_number": 5915, "pr_number": 6187, "commits_count": 0, "files_changed": 1, "response_length": 797, "file_count": 0, "needs_breakdown": false} |
fix: verify email in decision manger
Currently decision manager is giving verify email flow for users who are already verified but not for users who are not verified. This should be other way around. | <think>
PR Context:
- Title: fix(users): Correct the condition for `verify_email` flow in decision manger
- Merged: 2024-05-08T08:31:55Z
- Files changed: 1 files
- Commits: 2 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
- Currently decision manager is giving verify email ... | {"issue_number": 4579, "pr_number": 4580, "commits_count": 1, "files_changed": 1, "response_length": 995, "file_count": 3, "needs_breakdown": false} |
[REFACTOR] facilitapay destination bank account number should be merchant facing
destination bank account number should be added by merchant, not customer. this is a design flaw that needs to be fixed. | <think>
PR Context:
- Title: refactor(connector): [facilitapay] move destination bank account number to connector metadata
- Merged: 2025-07-25T12:44:09Z
- Files changed: 11 files
- Commits: 7 commits
Implementation approach:
## Description
<!-- Describe your changes in detail -->
Destination bank account id shou... | {"issue_number": 8703, "pr_number": 8704, "commits_count": 1, "files_changed": 11, "response_length": 2205, "file_count": 7, "needs_breakdown": false} |
refactor: Basilisk hs integration
## Type of Change
<!-- Put an `x` in the boxes that apply -->
- [ ] Bugfix
- [ ] New feature
- [ ] Enhancement
- [x] Refactoring
- [ ] Dependency updates
## Description
Legacy locker will be depreciated as it doesn't have the key rotation feature,
We will be using basilis... | <think>
PR Context:
- Title: feat: Integrate basilisk-hs for card storage alongside legacy locker
- Merged: 2023-03-13T13:52:55Z
- Files changed: 9 files
- Commits: 6 commits
Implementation approach:
## Description
This PR is an extension for #704 . Earlier @manoj-juspay added the support for `basilisk_hs` permane... | {"issue_number": 704, "pr_number": 718, "commits_count": 0, "files_changed": 9, "response_length": 798, "file_count": 0, "needs_breakdown": false} |
[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 featur... | <think>
PR Context:
- Title: refactor(recon): use AuthDataWithUser and use JWTAuth for token verif…
- Merged: 2024-09-19T13:54:06Z
- Files changed: 4 files
- Commits: 27 commits
Implementation approach:
## Description
Described in #5838
### Additional Changes
- [ ] This PR modifies the API contract
- [ ] Thi... | {"issue_number": 5838, "pr_number": 5829, "commits_count": 1, "files_changed": 4, "response_length": 1399, "file_count": 6, "needs_breakdown": false} |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.