Skip to content

PFCA

Peer-to-Peer Fundraising - Cash#

Occurence: A cash donation has been made to the campaign.

Key Data: The donation should be credited to the page from where it was requested, which may be that of the site, an organization, a team or an individual.

Donations made as cash are limited to single payments, so will include basic payment details such as amount, currency, date and time of the transaction, and transaction identifier, but can not be associated with a recurring schedule.

As this is an offline payment, the payment status will always be reported as 'success'.

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:

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

The database identifier of a page belonging to an organization. Example: 5144

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

Campaign Type#

PFCA

Campaign ID#

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

Campaign Status#

The payment status of the offline donation.

Occurs as either:

success The donation has been marked as received.

refund The donation has been marked as refunded.

change A change has been made to this donation. May include details of the change, for example which part of the record was modified.

Example: success

Campaign Data 1#

The internal database identifier assigned to a fundraising transaction.

Example: 4913255

Campaign Data 2#

An identifier assigned to this transaction by the software.

Example: ND87711264501200329633

Campaign Data 3#

Any message, including error codes provided by a payment gateway if a transaction is rejected. Refer to the documentation provided by the relevant payment gateway for details.

Example: The card type provided is not supported for this transaction

Campaign Data 4#

An amount presented as a decimal number without any currency symbols. This amount may be omitted for pagetypes where the amount to be processed by a payment gateway needs to be calculated, for example when purchasing tickets for events or certain types of symbolic gifts.

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#

Offline payments made using 'cash' or 'wire' transfer. <= 50 characters

Example: cash

Allowed values:

cash wire

Campaign Data 7#

No output for this transaction type.

Campaign Data 8#

No output for this transaction type.

Campaign Data 9#

No output for this transaction type.

Campaign Data 10#

No output for this transaction type.

Campaign Data 11#

No output for this transaction type.

Campaign Data 12#

No output for this transaction type.

Campaign Data 13#

No output for this transaction type.

Campaign Data 14#

Indicates the tax deductible status of this transaction. <= 1 characters

Occurs as either:

N The transaction is flagged as not being tax deductible. When importing transactions, leaving this blank will still result in an 'N' being recorded to indicate that the transaction should not be considered tax deductible.

Y Indicates the that this payment should be flagged as tax deductible for reporting purposes.

Default: N

Example: N

Campaign Data 15#

Occurs as either:

A donation made was made in general, meaning it should not be attributed to a particular page.

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

Campaign Data 16#

The date a gift was processed - as provided by the user or administrator [YYYY-MM-DD]. If the date was unknown at the time of processing, the day the gift was added to the system will be used instead.

Campaign Data 17#

No output for this transaction type.

Campaign Data 18#

Occurs as either:

The numerical identifier of the generated receipt for this transaction.

If no receipt was generated, this will refer back to the internal database identifier of the transaction. Example: 414664

The internal database identifier assigned to a fundraising transaction. Example: 4913255

Campaign Data 19#

No output for this transaction type.

Campaign Data 20#

Where (the target or purpose) the donor specified that 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

External Reference 1#

No output for this transaction type.

External Reference 2#

No output for this transaction type.

External Reference 3#

No output for this transaction type.

External Reference 4#

No output for this transaction type.

External Reference 5#

No output for this transaction type.

External Reference 6#

No output for this transaction type.

External Reference 7#

No output for this transaction type.

External Reference 8#

No output for this transaction type.

External Reference 9#

No output for this transaction type.

External Reference 10#

No output for this transaction type.

Email Address#

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

Title#

A supporter's title to be used in salutations <= 50 characters

Example: Dr

First Name#

A supporter's first name <= 500 characters

Example: Otto

Middle Name#

A supporter's middle name <= 500 characters

Example: Niemand

Last Name#

A supporter's last name <= 500 characters

Example: Normalverbraucher

Address 1#

The first line of the supporter's address <= 1000 characters

Address 2#

The second line of the supporter's address <= 1000 characters

Address 3#

The third line of the supporter's address <= 1000 characters

City#

The city in a supporter's address <= 500 characters

Example: Musterstadt

Region#

The supporter's region, state, county, province or similar <= 500 characters

Example: Musterregion

Country#

The supporter's country <= 500 characters

Example: DE

Phone Number#

The primary phone number for a supporter <= 200 characters

Example: +49 4066969123