Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE] Inclusion of customer details in payment_intent column #5008

Closed
2 tasks done
prajjwalkumar17 opened this issue Jun 14, 2024 · 0 comments · Fixed by #5007
Closed
2 tasks done

[FEATURE] Inclusion of customer details in payment_intent column #5008

prajjwalkumar17 opened this issue Jun 14, 2024 · 0 comments · Fixed by #5007
Assignees
Labels
A-core Area: Core flows C-feature Category: Feature request or enhancement M-database-changes Metadata: This PR involves database schema changes

Comments

@prajjwalkumar17
Copy link
Contributor

Feature Description

This change will insure storage of customer_details in our payment_intent table.
Which will help us to derive the customer_details directly in one db call.

Possible Implementation

if customer_id alone is passed -> Derive customer_details from customer_table and put it in guest_customer_details,
if customer_id is not present -> Put the details in guest_customer_details.
if both are present -> we are ignoring the email, phone etc and deriving them from customer_table and adding to the guest_customer_details field.

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?

Are you willing to submit a PR?

Yes, I am willing to submit a PR!

@prajjwalkumar17 prajjwalkumar17 added A-core Area: Core flows C-feature Category: Feature request or enhancement M-database-changes Metadata: This PR involves database schema changes labels Jun 14, 2024
@prajjwalkumar17 prajjwalkumar17 added this to the May 2024 Release milestone Jun 14, 2024
@prajjwalkumar17 prajjwalkumar17 self-assigned this Jun 14, 2024
@prajjwalkumar17 prajjwalkumar17 linked a pull request Jun 14, 2024 that will close this issue
14 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-core Area: Core flows C-feature Category: Feature request or enhancement M-database-changes Metadata: This PR involves database schema changes
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants