Tinu Hareesswar
Tinu Hareesswar
### Feature Description Currently all our recurring payments are wrapped under a mandates layer which is in turn linked to a set of payment methods. We will decouple this and...
The `/account/payment_methods` should list only the _Add Payment Method_ flow compatible PMs if invoked with the `PM Client Secret` authentication. This is to weed out PMs which cannot be saved...
### Feature Description The CIT used to set up recurring payments via MIT using the connector_mandate_id. This introduces a connector stickiness since the recurring payments can only go through the...
- Payment Method ID to be passed back in payments/confirm response to be used for recurring MIT payments - PM status to be passed back as well
### Feature Description This will be the tracking issue for all Vaulting related changes. ### Problem Statement Currently, the only way a merchant can vault a card for one of...
Collect `public_key` and `raw_card_ttl` and store it in `business_profile` table. Use update endpoint to achieve this
### Feature Description Businesses like airline ticket sales and other ticketing agencies inherently come with a requirement for splitting the payment amongst the various stakeholders. In the airline industry, the...
Adding a feature flag at business profile level to enable raw card forwarding. Feature flag to be set using /profile/:id:/extended_card_info with auth as admin api key
The issue serves as the tracking issue of version 2 of Hyperswitch Card Vault. ## What's new: - Hyperswitch aims to be a generic storage vault agnostic of payments domain...
- By default a PM added will be set to inactive - Status is updated to active based on confirmation from connector via webhook/confirm response