-
Notifications
You must be signed in to change notification settings - Fork 4.6k
Closed
Labels
A-connector-compatibilityArea: Connector compatibilityArea: Connector compatibilityC-refactorCategory: RefactorCategory: RefactorC-tracking-issueCategory: Tracking issue for a proposal or a category of bugsCategory: Tracking issue for a proposal or a category of bugs
Description
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_laterthat 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_issuerandpayment_experienceinpayment_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?
- I checked and didn't find similar issue
Have you read the Contributing Guidelines?
- I have read the Contributing Guidelines
Are you willing to submit a PR?
None
Metadata
Metadata
Assignees
Labels
A-connector-compatibilityArea: Connector compatibilityArea: Connector compatibilityC-refactorCategory: RefactorCategory: RefactorC-tracking-issueCategory: Tracking issue for a proposal or a category of bugsCategory: Tracking issue for a proposal or a category of bugs