• Resolved wordmax

    (@wordmax)


    We enable custom field on payment form. The field name says “enter child name and age” because it’s for a camp. Great. But when we export Stripe data to see payments as a .csv file, under the column “Custom Fields (metadata)” in each row before the info submitted by user, there is the field name “enter child name and age” so it will look like “enter child name and age: bobby 9” and so on for every row.

    Is there a good reason why the field name should be included with the input data if we already have the column heading “Custom Fields (metadata)” – I think you could improve this by excluding the field name from being included with the input data which is submitted to Stripe.

    What do you think?

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter wordmax

    (@wordmax)

    Maybe useful regarding how field names vs id are treated, not sure:

    https://css-tricks.com/html-inputs-and-labels-a-love-story/

    • This reply was modified 3 months, 4 weeks ago by wordmax.
    Plugin Support mbrsolution

    (@mbrsolution)

    Thank you for reaching out to us. I personally don’t see a problem with the way the data is exported into a CSV file. However, how would you like the data to be exported? Can you provide an example of what you would like to see instead in the CSV file.

    Kind regards.

    Thread Starter wordmax

    (@wordmax)

    Just want only the customer’s input entered on custom field to be exported. The column heading already says “Custom Field” so that’s fine. We don’t need the custom field NAME be exported as well for every payment. Maybe you could put a check mark on/off to export custom field name or not. Thanks

    Plugin Support mbrsolution

    (@mbrsolution)

    Thank you for providing more information. I have submitted a message to the developers to investigate further your request.

    Kind regards.

Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.