[FEATURE] Vaulting a payment method

[tinu-hareesswar]

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 his customers is through processing a payment for that customer with a setup_future_usage preference given. We want to enable the merchant to be able to vault a card for a customer through the SDK without having to process a payment.

Although there are APIs for this very purpose, it is not compatible with the SDK since it operates only with a payment client secret.

Use Cases

Sequence Diagrams

Link

Possible Implementation

Task Distribution

Payment Method changes - without authentication

• [x] #4099
• [x] #4100
• [x] #4098
• [x] #4097

Adding Auth Support

1. Via Payment Processors

   • [ ] Add PM core to handle Connector requests which support dedicated vault APIs to store cards
   • [ ] Handling redirection flow for 3DS verification

2. Via external 3DS provider

   • [ ] Authenticate with 3dsecure.io

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 Contributing Guidelines?

• [X] I have read the Contributing Guidelines

Are you willing to submit a PR?

None

[shubham-chhimpa]

not able to open both these links. Only people having access can open it.

https://juspay.atlassian.net/wiki/spaces/JR/pages/2260566162/Vaulting+and+Tokenization+with+Hyperswitch

https://docs.google.com/document/d/1Ox0JaOCtmhSLLxSc-OT7AdqRovzpXSxdaoODJ4LH7O4/edit?usp=sharing

[tinu-hareesswar]

@shubham-chhimpa - sorry these were internal docs that were linked for dev assistance, I've removed it now. Will add relevant details here.

[luizaraujobliver]

@tinu-hareesswar This internal developer assistance document would help us a lot, without a doubt. Can't share?