Stripe Metadata

Created by Emilie Macke, Modified on Wed, 29 May at 7:10 AM by Emilie Macke

On your Stripe Dashboard, your Organization has access to several additional levels of information. 


To provide some context, here is a potential list of fields I'm thinking through (with ServiceReef data in parentheses):
  • Type (ServiceReef type, which could be: payment, donation, application fee, task payment, etc)
  • Origin (Opportunity Name, Track Name, Task Name, etc - similar to Trip Name currently, but SR has multiple ways of generating payments)
  • Origin ID (e.g. Trip ID, Track ID, etc)
  • App ("ServiceReef")
  • Accounting Code (what is on each opportunity - likely currently the "purpose code")
  • Donor Name
  • Donor Address
  • Donor Email
  • Donor ID (ServiceReef ID)
  • Recipient Name
  • Recipient Address
  • Recipient Email
  • Recipient ID (ServiceReef ID)


Customizing Your Reports : Stripe: Help & Support 


  • Exporting from Stripe
    • Pros:
      • As of our last release on 2/29, ServiceReef is now sending metadata with each transaction that can be reported on (Stripe Custom Reports - more details here)
      • This can be manipulated in an export from Stripe directly, so it only includes the data you need 
      • ServiceReef data that is included with each transaction is included below
      • Easily exported data leveraging Stripe's interface
    • Cons:
      • Requires Stripe Login for user who is pulling the report
      • Lack of SR Knowledge... just being transparent, I personally have not spent a lot of time on Stripe Reports, but I know other churches that leverage this extensively
      • Still requires an export and potentially data/column manipulation
      • Recurring donations don't have ServiceReef metadata yet (Stripe stores these separately and ServiceReef is planning on adding metadata in March/April 2024 for recurring payments)

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article