PFIM

Peer-to-Peer Fundraising - In Memoriam#

Occurence: A donor has requested that their donation is to be in memory of someone.

Co-occurence: Accompanies any donation which is made 'In Memory' (the tagged field 'In Memoriam is submitted with the page'. )

Key Data: This transaction only holds the 'In Memoriam' specific data captured through related fields on a donation page. Details about the donation transaction are included, and may be used to link the in memory aspect to the specific donation. Depending on what has been included for capture on the page, the columns for 'Campaign Data 8' to 'Campaign Data 20' may be populated with data from the tagged supporter fields.

Export file columns#

Account ID#

Identifies the subaccount this item belongs to

Example: 94

Supporter ID#

The unique numerical database identifier for a supporter.

Example: 212200 Default: 0

Supporter Email#

The primary email address of a supporter, which will typically be used as the basis for identifying a unique supporter to which any transactions will be associated. <= 500 characters

Example: otto.nv@example.com

Date Created#

The date a supporter was created. [ISO 8601 format date]

Example: 2024-12-01

Date Modified#

The date a supporter was last modified. [ISO 8601 format date]

Example: 2024-12-01

Campaign Number#

The page number where this donation orginated

Occurs as either:

fundraiser page id team page id

The database identifier of a page belonging to a fundraiser. Example: 4031

The database identifier of a page belonging to a team of fundraisers. Example: 5042

Campaign Type#

PFIM

Campaign ID#

The internal reference name given to a page. <= 160 characters

Campaign Status#

The status of this transaction, as reported by the designated payment gateway.

Occurs as either:

success reject refund

success The transaction was successfully processed by the payment gateway.

reject The transaction was rejected by the payment gateway.

refund The transaction has been marked as refunded.

Example: success

Campaign Data 1#

The internal database identifier assigned to a fundraising transaction.

Example: 414664

Campaign Data 2#

The transaction identifier as provided by a payment gateway. If the current transaction is a refund, then this identifier points back to the transaction being refunded. The specific formatting of the identifier will be dependent on the gateway.

Example: ND8390T284740397745210972__cus_O20rrZCTq8iTpw__ch_3NFwqEHh8CrK50QS1uUEXjck

Campaign Data 3#

Occurs as either:

General donation site id

A donation made in general, and not attributed to a particular peer-to-peer site.

The database identifier for a Peer-to-Peer site.

Campaign Data 4#

Processing amount, presented as a decimal number without any currency symbols. The amount may be omitted for pagetypes where the amount to be processed is calculated by the page processing, for example when purchasing tickets for events or certain types of symbolic gifts. The amount will also include any additions made by any optional Fee Cover requested.

Example: 5.0

Campaign Data 5#

The ISO 4217 code of the currency used for this transaction. When processing payments, it is important to note that currency support is gateway dependent, so be sure to check with your designated payment gateway that the selected currency is supported and has been enabled for your account.

Example: GBP

Campaign Data 6#

Passed as a value or determined by a payment gateway, this describes the payment type to use for the transaction. Valid types may vary depending on the payment gateway used. Some payment types, e.g CASH, CHECK or WIRE may be used to indicate offline donation, or to process 'free' items. Such donations will not be possible to reconcile with an external payment gateway. In output, the prefix TEST: indicates a transaction carried out in a DEMO mode. These transactions should also not be considered for reconciliation purposes. The prefix digitalwallet: is added if the payment was made using a digital wallet integration. <= 50 characters

Allowed values:

Venmo cartes_bancaires Master card American Express AMEX-SSL diners Discover DI Visa electron JCB DELTA MC ECMC-SSL VI MASTERCARD Visa VISA VISA-SSL AMEX AMX unionpay discover AX CASH CHECK WIRE wire eCheck en_bank unknown Bank BANK Checking Savings EC EFT PayPal DDT ACHEFT ACH ach BACS SEPA bacs_debit sepa_debit Direct Debit DAF refund

Example: VISA

Campaign Data 7#

The frequency for this transaction, which can be a one-off payment or part of a recurring schedule.

Occurs as either:

S R

S The payment was made as a one-off (single).

R The payment was set up according to a recurring schedule.

Campaign Data 8#

Indicates if the In Memoriam Gift should be specially recognised. <= 1 characters

Allowed values:

Y N

Example: Y

Campaign Data 9#

Specific choices of tribute options for an In Memoriam Gift. <= 400 characters

Example: In memory of

Campaign Data 10#

The reason the In Memoriam Gift is being made. <= 4000 characters

Example: Tom was such a crucial member of our local community, and left such an impression on everyone he met.

Campaign Data 11#

The name of the person in whose Honor the In Memoriam Gift is made. <= 400 characters

Example: Major Tom

Campaign Data 12#

Name of the person being informed of an In Memoriam Gift. <= 400 characters

Campaign Data 13#

Email address of the person being informed of an In Memoriam Gift. <= 400 characters

Campaign Data 14#

Address line 1 of the person being informed of an In Memoriam Gift. <= 400 characters

Campaign Data 15#

Address line 2 of the person being informed of an In Memoriam Gift - floor, apartment, suite, etc. <= 400 characters

Campaign Data 16#

City of the person being informed of an In Memoriam Gift. <= 400 characters

Campaign Data 17#

Region, State/Province of the person being informed of an In Memoriam Gift. <= 400 characters

Campaign Data 18#

Postcode of the person being informed of an In Memoriam Gift. <= 400 characters

Campaign Data 19#

Country of the person being informed of an In Memoriam Gift. <= 400 characters

Campaign Data 20#

The designation of target or purpose the donor has specified for how they want their gift to be used. <= 255 characters

Campaign Data 21#

Other 1: A client defined tagged field which can be used to store any additional data that may relate to the current transaction. <= 500 characters

Example: Text containing some information that could prove useful when we handle this transaction, for example additional notes from a supporter directly relating to this particular donation.

Campaign Data 22#

Other 2: A client defined tagged field which can be used to store any additional data that may relate to the current transaction. <= 500 characters

Example: Text containing some information that could prove useful when we handle this transaction, for example additional notes from a supporter directly relating to this particular donation.

Campaign Data 23#

Other 3: A client defined tagged field which can be used to store any additional data that may relate to the current transaction. <= 500 characters

Example: Text containing some information that could prove useful when we handle this transaction, for example additional notes from a supporter directly relating to this particular donation.

Campaign Data 24#

Other 4: A client defined tagged field which can be used to store any additional data that may relate to the current transaction. <= 500 characters

Example: Text containing some information that could prove useful when we handle this transaction, for example additional notes from a supporter directly relating to this particular donation.

Campaign Data 25#

Any additional comments submitted by the user to accompany this transaction. <= 4000 characters

Example: I suffer from this illness, and would be happy to share my story if it could help.

Campaign Data 26#

Amount in USD if available - use for reporting only - converted at the time of transaction

Example: 1.3

Campaign Data 27#

Amount in GBP if available - use for reporting only - converted at the time of transaction

Example: 1.0

Campaign Data 28#

Amount in EUR if available - use for reporting only - converted at the time of transaction

Example: 1.19

Campaign Data 29#

Amount in CAD if available - use for reporting only - converted at the time of transaction

Example: 1.77

Campaign Data 30#

Amount in AUD if available - use for reporting only - converted at the time of transaction

Example: 1.91

Campaign Data 31#

The database identifier of a supporter who has been identified as the referrer for this transaction

Example: 5348788

Campaign Data 32#

Details about the user agent used when submitting the content. The string consists of key/value pairs that are separated by a ~ (tilde) character.

mobile: N or Y depending on whether the user agent identifies as a mobile device. tablet: N or Y depending on whether the user agent identifies as a type of device classed as a 'tablet'. device: The manufacturer of the type of device used by the user agent. os: The underlying operating system of a user agent. browser: The type of web-browser that was used.

Example: mobile:N~tablet:N~device:APPLE~os:Mac OS X~browser:Firefox 11

Campaign Data 33#

A URL identified as the referral origin for this transaction

Example: https://example.com/page/12272/donate/1

Campaign Data 34#

Used to note the origin of incoming page traffic, and is typically passed in links to pages using the query parameter ea.tracking.id <= 300 characters

Example: linkshare

Campaign Data 35#

An appeal code assigned to this submission.

The code can be considered transactional as it is typically submitted as part of a page submission and associated with the page transaction, however the 'latest' appeal code applied to any supporter submission is also held on the supporter's record. <= 300 characters

Example: EOY