Stripe Meta Data should post in Subscription Renewal Payments
under review
Angela Blake
M
Matthew Lewis
We use hidden custom fields to include vital metadata for our Zapier integration. Without this feature, we have had to set up multiple donation forms for different metadata values, and then split it out in Zapier based on the form id. Not ideal.
R
Ryan Smith
We have something like 80% of our donations coming through as recurring and when you are manually pulling reports from Stripe to place into your accounting software, it is extremely difficult to know what payments are associated to what designations or even what subscriptions.
I think it would be good to allow Metadata to be added to every payment from a subscription as well as passing along or being able to update the Payment Description as you can with individual payment subscriptions as shown here https://github.com/impress-org/givewp-snippet-library/blob/master/gateway-customizations/stripe-pass-custom-meta-for-payments.php or using $charge_args['description'].
Relatedly as other people have mentioned this change should also effect first payments on a subscription which is shown in this post: https://feedback.givewp.com/feature-requests/p/add-description-to-stripe-recurring-payments
A
Alan Owen
suggest merging these two posts - https://feedback.givewp.com/feature-requests/p/stripe-meta-data-should-post-in-new-subscriptions
J
James Taylor
Agreed - we receive a high volume of donations from multiple platforms, so the ability to view full metadata on subscriptions in Stripe for these is almost essential to our Financial department to cut down on manual manipulation between reports and ensure subscriptions are being attributed to the correct donor in our data management system.
May Workman
I have another comment related to Stripe Meta Data for Subscription Renewal Payments after a very long discussion with Stripe. I understand this much better now since my previous post on April 15th.
There are 3 transactions that could have better descriptions and metadata that correspond to Subscriptions. Below are the descriptions we see on Payouts for the 3 types.
Subscription Creations : Subscription creation
Transaction line at a renewal : Invoice 767FC042-0004
Billing Fee : Billing (2021-07-26): Subscriptions
Could there be the donor name, or email or donation ID added?
I have learned that the Billing Fee is an extra fee charged because Stripe creates an Invoice at the time of the renewal. An invoice is created from a Subscription but no metadata or description is copied from the Subscription so putting more information in the Subscription will not help the Billing Fee line. See the video https://youtu.be/fPYi0y2LSDQ
A potential workaround to this would be to set up a webhook to listen in on invoice.payment_succeeded events (https://stripe.com/docs/api/events/types#event_types-invoice.payment_succeeded) and a webhook response to update the associated invoice with the metadata (https://stripe.com/docs/api/invoices/update#update_invoice-metadata).
Any help for our financial dept would be greatly welcomed. I had Stripe explain to me how to connect "Billing (2021-07-26): Subscriptions" to a line so we can figure out who the donor is. It takes a lot of effort and I have a page of documentation for our finance team to be able to follow. :/
May Workman
The initial subscription description in Stripe is "Subscription creation". It is very difficult for the finance dept to connect this to a donation. In addition, each renewal is an invoice number which is not connected to anything in GiveWP. It is very cumbersome not only for the finance dept but also for me training the finance dept. I would like to see not only the meta data improve but also the description.
D
David Hahn
Extremely important that this upgrade happen. We work with churches and non profits and a big percentage of their giving is for various "funds" that the donor can select and this becomes part of the meta data. The churches and non profits encourage recurring giving so as they get started with GiveWP // Stripe a great percentage of their monthly donations are recurring. The payout reconciliation and other reports from Stripe are helpful, but it is VERY CUMBERSOME for the accounting when they don't have the meta data on recurring donations. PLEASE. It will increase sales of GiveWP for us. Thank you.
Ben Meredith
under review
We're monitoring this post for further votes and comments.
Up to this point in the history of GiveWP, we've assumed that the initial donation on a subscription was sufficient to be able to track things like fund and other meta. If enough folks disagree, we could be persuaded to look more deeply into this. Vote and comment here!
Jim Mackenzie
This is especially important for Indian donors as they need to have their PAN (https://en.wikipedia.org/wiki/Permanent_account_number) displayed on all receipts.
Ben Meredith
Jim Mackenzie: Hey Jim, I'd be very wary of storing PAN on the WordPress server: https://www.pcicomplianceguide.org/pan-storage-and-the-pci-dss/
Jim Mackenzie
Ben Meredith: Hi Ben. It's not the same PAN that we're looking to store. If you check the link I posted you'll see the difference.
Ben Meredith
Jim Mackenzie: Thanks for the clarification. I still don't know how PAN from India affects PCI compliance, but I do see now that it appears to be addressing a different PAN.
Load More
→