refactor: add billing and shipping details to payment method data

[Narayanbhat166]

Feature Description

linking #347 for reference. Since the billing and shipping address used for payment should be stored in basillisk as per the discussion we had. This is to avoid

• Any PII information to be stored in db which will be used for payments.
• Avoid changes to payments if the address table undergoes any major changes ( like encryption ).

Possible Implementation

• [ ] Have a struct under payment_method_data.pay_later that will have all billing and shipping related data required for payments. All paylater payments will have the mandatory details of address taken from here.
• [ ] Save pay_later data in basillisk.
• [ ] Add payment_method_issuer and payment_experience in payment_attempt. This will be used to decide which issuer the payment has to go through and what should be the experience ( either sdk flow or redirection flow ).

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

• [X] I checked and didn't find similar issue

Have you read the Contributing Guidelines?

• [X] I have read the Contributing Guidelines

Are you willing to submit a PR?

None

[Narayanbhat166]

Let me know your thoughts on this change @bernard-eugine.

[bernard-eugine]

Let me know your thoughts on this change @bernard-eugine.

This works! Let's go ahead.

[Narayanbhat166]

One doubt that is bugging me is, the shipping address will be available with the merchant and should be sent by merchant during creating the payment, and billing address or details can be sent in the payment_method. This is why stripe has billing details in the payment method and shipping address outside payment method. Currently our implementation is also the same, should we have shipping address to in the payment method? This would mean either the merchant or client ( as in customer ) has to send both the address fields

[Narayanbhat166]

Closing this issue as these changes are included the billing_address refactoring.