Skip to main content

What Meta Data Does RaiseDonors Send To Stripe?

Chris Mechsner
  • Updated

With each transaction, RaiseDonors sends contextual information about the donation to Stripe's meta data feature. Meta data is located in several different areas of Stripe. Here is how and what RaiseDonors sends to Stripe's meta data.

ONE-TIME DONATION

When a new one-time donation is placed, a payment intent will be created in Stripe with several meta data keys on the payment object. 

  • RaiseDonors_CampaignId
    • This is the unique ID of the page in RaiseDonors that the donor is donating from. 
  • RaiseDonors_LandingUrl
    • This is the full URL including all parameters, which the donor landed on to give this donation. 
  • RaiseDonors_CampaignUrl
    • This is the unique URL of the page in RaiseDonors that the donor is donating from. 
  • RaiseDonors_ProjectShoppingCart
    • Optional
    • If the donation page has enabled multiple Projects and the donor is giving to multiple Projects, this will display a JSON payload of the Project shopping cart.
    • Ex: [{"CartId":1,"Amount":25,"ProjectId":"2215","Comment":"test"}]
  • RaiseDonors_SelectedProductId
    • Optional
    • If the donation page has products/sku's enabled, this will display the selected product Id.

Due to the security aspects, only these 3-5 meta data keys are created at the time of the payment intent creation. After the successful charge takes place, Stripe notifies RaiseDonors of the new charge, and RaiseDonors will add additional meta data keys to the payment object. This whole process is usually completed within seconds of a charge taking place. 

  • RaiseDonors_OrgId
    • The unique ID of your organization in RaiseDonors.
  • RaiseDonors_ProjectId
    • Every donation is associated with at least one Project. This information explains the Project Id, the amount, and the Project name, pipe delimited.
    • Ex: 2215|25|Sending More Workers into His Harvest Field
  • RaiseDonors_ProjectNames
    • Every donation is associated with at least one Project. This information displays the name(s) of the Project(s) the donation is associated with.
    • Ex: Sending More Workers into His Harvest Field
  • First Name
    • Donors first name
  • Last Name
    • Donors last name
  • Email
    • Donors email address
  • RaiseDonors_DonorId
    • The unique ID of the donor in RaiseDonors. You can use this ID to look up donors via the API. 
  • Amount
    • The amount of the donation. 
  • Phone
    • Donors phone number
  • Billing Address
    • The donation's billing address.
    • Ex: PO Box 123, Austin, Texas, 78737 USA
  • Source URL
    • The URL the donor came from to place this donation. 
  • Billing.Address
    • The billing address's address.
  • Billing.City
    • The billing address's city.
  • Billing.State
    • The billing address's state.
  • Billing.Postal
    • The billing address's postal code.
  • Billing.Country
    • The billing address's country.

Additionally, the following meta data key is added to the customer object in stripe. 

  • RaiseDonors_DonorId
    • The unique ID of the donor in RaiseDonors. 

RECURRING DONATION

A subscription with a price and product will be created in Stripe. The subscription will contain various meta data values from RaiseDonors. These meta data values are created and set up with the creation of the subscription. If a subscription is adjusted, these meta data values will also be adjusted. 

  • RaiseDonors_OrgId
    • The unique ID of your organization in RaiseDonors.
  • RaiseDonors_CampaignId
    • This is the unique ID of the page in RaiseDonors that the donor is donating from. 
  • RaiseDonors_ProjectId
    • Every donation is associated with at least one Project. This information is stored with the subscription so that future charges inherit these Project allocations.
    • Ex: 2215|25|Sending More Workers into His Harvest Field
  • RaiseDonors_ProjectNames
    • This information displays the name(s) of the Project(s) the donation is associated with.
    • Ex: Sending More Workers into His Harvest Field
  • First Name
    • Donors first name
  • Last Name
    • Donors last name
  • Email
    • Donors email address
When a transaction is created from the schedule, RaiseDonors will populate the same meta data elements described above on the "one-time donation". 
 

CUSTOM META DATA OPTIONS

In addition to these standard meta data values, you can provide custom meta data key/values to Stripe. Doing so requires a bit of Javascript knowledge. We have a full guide to read and follow here. Any custom key/value pair added to the donation will be sent to Stripe and included as meta data. 

For instance, if you create the following key/value pair and store it with the donation,

custom_birthday=1/1/2000|custom_gender=female|custom_age=21|
 
You will see the following key/values in Stripe as meta data.
  • birthday = 1/1/2000
  • gender = female
  • age = 21

Note, the custom key/values will be added in addition to the standard key/values already added by RaiseDonors. Stripe also has limitations on the amount and number of key/value pairs provided. 

You can specify up to 50 keys, with key names up to 40 characters long and values up to 500 characters long.