PFCR

Peer-to-Peer Credit Recurring#

Occurence: A recurring card 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.

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 organization page id site 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

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

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

Campaign Type#

PFCR

Campaign ID#

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

Campaign Status#

Describes the status of this transaction as reported by the software. If the recurring schedule has been changed, the change will be briefly described within [].

Allowed values:

success reject change []

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#

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#

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#

Transaction Frequency. This will always be 'R' for recurring transactions.R

Campaign Data 8#

For recurring payment schedules, this denotes the day of the month when a payment should be processed. If a Recurring Start Date was also provided, the processing day will be valid for the periods after the initial payment.

Example: 13

Campaign Data 9#

The schedule used for processing recurring payments.

Typical frequency for recurring charges are usually monthly, quarterly, every six months ('semi annually'), or annually.

Allowed values:

MONTHLY QUARTERLY SEMI_ANNUAL ANNUAL

Example: MONTHLY

Campaign Data 10#

The current status of the recurring schedule.

Allowed values:

ACTIVE PAUSED SUSPENDED CANCELED

Example: ACTIVE

Campaign Data 11#

Represents the gateway provided details of any parent transaction, if applicable. If the current transaction is the "parent", then this will remain blank.

Example: ND8390T284740397745210972__cus_O20rrZCTq8iTpw__ch_3NFwqEHh8CrK50QS1uUEXjck

Campaign Data 12#

The name of the payment gateway implementation used to process this payment. Payments made and recorded as the types CASH or CHECK may not hold any value here, as they do not require the involement of a payment gateway.

Occurs as either:

Example: import

Campaign Data 13#

The card expiry date. The exact format is dependent on the payment gateway used to process the transaction. <= 8 characters

Example: 10/26

Campaign Data 14#

Indicates whether this transaction should be flagged as tax deductible for reporting purposes. The status can be collected as field value when a donation is processed, or manually updated by the user. <= 1 characters

Allowed values:

Y N

Default: N

Example: Y

Campaign Data 15#

Occurs as either:

Donation made in general site id

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 when the first payment in a recurring payment schedule should be pushed [MM/DD/YYYY]. Works in conjunction with 'Recurring Day' to denote the date when the first payment in the schedule will be pushed. Recurring Day will determine the day of month when the subsequent processing events should be pushed.

Example: 13/6/2030 <= 20 characters

Campaign Data 17#

The date the schedule of recurring payments should stop.

Example: 13/6/2030 <= 20 characters

Campaign Data 18#

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

Campaign Data 19#

The name of the credit card holder, as printed on the card. To be used when processing donations. <= 500 characters

Example: MR OTTO NORMALVERBRAUCHER

Campaign Data 20#

Occurs as either:

direct gift Mandate Amount

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

Stripe: The amount offered to set up a new Direct Debit mandate.

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, passed using the tagged field Additional Comments. <= 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 value may be passed as a field present on the page, or with the url parameter supporter.appealCode. Any appeal code will be recorded on the supporter's record, and in regular page processing it will also be noted on the transactional level.

When posting data using processPage or processCardPayment, the function of this field is more flexible, and can be either part of the supporter object or of the page object, and will be stored separately in each. The page-builder behaviour can easily be replicated by passing identical values for appealCode to both the page object and the supporter object in the post request.#

<= 300 characters

Example: EOY