[FEATURE] Extend storage of additional payment method details to wallets

[kashif-m]

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 access to the raw payment method data details. However, these wallets also has some metadata for identification and display purposes. These details are to be stored and propagated in payments response.

Possible Implementation

HyperSwitch supports loads of wallet integrations today. As a first cut, add additional payment method details to below wallets

• ApplePay
• GooglePay

Have you spent some time checking if this feature request has been raised before?

• I checked and didn't find a similar issue

Have you read the Contributing Guidelines?

• I have read the Contributing Guidelines

Are you willing to submit a PR?

Yes, I am willing to submit a PR!

[kashif-m]

# 2

• Extend propagation of additional payment method details in payments API response and webhooks response during wallet MIT transactions

Context

• MIT transactions in HS work using a payment_method_id during payments call
• Additional payment method data for wallets is expected during payments creation - which is not available during MIT payments

Possible solution

• Additional payment method data for wallets to be stored in DB
• Same to be retrieved from the DB during MIT payments