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

Add further payment metadata for classification #5669

Closed
dechov opened this issue Mar 3, 2023 · 4 comments · Fixed by #7091
Closed

Add further payment metadata for classification #5669

dechov opened this issue Mar 3, 2023 · 4 comments · Fixed by #7091
Assignees
Labels
category: core WC Payments core related issues, where it’s obvious. category: engineering For product engineering, architecture work, tech debt and so on. component: checkout Issues related to Checkout type: enhancement The issue is a request for an enhancement.

Comments

@dechov
Copy link
Contributor

dechov commented Mar 3, 2023

Add more information to payment metadata, either in a single field or multiple, about how the payment originates: initial vs. renewal, UPE vs. non-UPE, shortcode vs. block, etc.

We already have payment_type but its value is "recurring" for all subscription-related payments, not just renewals. (There is also payment_context for WCPay subscriptions – see #3715 (comment)).

@htdat htdat added category: core WC Payments core related issues, where it’s obvious. category: engineering For product engineering, architecture work, tech debt and so on. needs prioritisation Triage finished and issues are ready for the following processing. type: enhancement The issue is a request for an enhancement. labels Mar 6, 2023
@RadoslavGeorgiev RadoslavGeorgiev added the component: checkout Issues related to Checkout label Mar 7, 2023
@jessy-p
Copy link
Contributor

jessy-p commented Mar 7, 2023

To come up with the list of fields, and after checking with architects, implement it.

@souravdebnath1986
Copy link

What are the use cases (+customers i.e. merchants, internal) for enhancing the payment meta eg: enhanced reporting.

@naman03malhotra
Copy link
Contributor

Moving it back to "RFP" queue to discuss it during the prioritization call.

@naman03malhotra naman03malhotra removed the needs prioritisation Triage finished and issues are ready for the following processing. label Jul 13, 2023
@aheckler
Copy link
Member

Can we also add a bit of metadata to indicate the current version of WooPayments on the merchant site? This could be helpful for support during troubleshooting.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category: core WC Payments core related issues, where it’s obvious. category: engineering For product engineering, architecture work, tech debt and so on. component: checkout Issues related to Checkout type: enhancement The issue is a request for an enhancement.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

8 participants