FCR

Fundraising Card Recurring#

Occurence: Represents either the setup of a new recurring payment schedule as submitted through a donation page, or details about the subsequent transaction processing which happens according to the specified schedule. This type of transaction will also be produced for any changes made to such payment, such as a new expiry date, amount, status, or the day of charge.

Key Data: The transactional data summarises the key features of the agreed schedule. If this transaction is not setting up the schedule, it will be a recurring event and there will be a parent Id listed, which links back to the transaction that initiated the payment sequence. When Campaign Status has noted a change, more details about the change can be found in the columns Campaign Data 21 and Campaign Data 22.

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#

A unique database identifier used to refer to a page, particularly in transactional data. Where records in transactional data originate outside of a page structure, for example as a result of dashboard actions or imports, this will hold a value of 0. Default: 0

Example: 10122

Campaign Type#

FCR

Campaign ID#

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

Campaign Status#

Describes the status of a recurring transaction, as reported by the payment gateway (if applicable).

Occurs as either:

success reject change []

success The payment was accepted by the processing payment gateway.

reject The payment was rejected by the processing payment gateway.

change [] The recurring schedule has been changed. The change may be briefly described within [].

Example: success

Campaign Data 1#

The database identifier assigned to a fundraising transaction.

Example: 4913255

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#

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. Currency support is gateway dependent, so be sure to check with your designated payment gateway that the selected currency is supported.

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, this day will be valid for the periods after the initial payment.

Example: 13

Campaign Data 9#

The schedule used for processing if the payment is recurring. Typical frequency for recurring charges are usually monthly, quarterly, every six months ('semi annually') or annually.

Occurs as either:

MONTHLY QUARTERLY SEMI_ANNUAL ANNUAL

MONTHLY The recurring schedule is processed every month.

QUARTERLY The recurring schedule is processed every three months.

SEMI_ANNUAL The recurring schedule is processed every 6 months.

ANNUAL The recurring schedule is processed every 12 months.

Example: MONTHLY

Campaign Data 10#

The current status of the recurring schedule.

Occurs as either:

blank ACTIVE PAUSED SUSPENDED CANCELED

A status will not be provided if a payment is not recurring.

ACTIVE The schedule is running as defined.

PAUSED The schedule has been temporarily halted

SUSPENDED The schedule has been suspended by the software, as it has failed to process after being rejected by the gateway over 3 attempts.

CANCELED The schedule has been cancelled.

Example: ACTIVE

Campaign Data 11#

Represent the gateway provided details of any parent transaction. 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 the tax deductible status of this transaction. <= 1 characters

Occurs as either:

N Y

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#

Apply this donation to a given pledge. Default: 0

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 database identifier of the transaction.

Example: 414664

Campaign Data 19#

The name of the credit card holder, as printed on the card. <= 500 characters

Example: MR OTTO NORMALVERBRAUCHER

Campaign Data 20#

Occurs as either:

direct gift

Where (the target or purpose) the donor specified that they want their gift to be used.

<= 255 characters

Mandate Amount

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

Campaign Data 21#

Occurs as either:

change TXN_MOVE other1

Describes a change that has been made to this transaction. Example: change [tax deductible: true]

TXN_MOVE Indicates that a transaction has been moved from one supporter to another. The supporter id of the previous owner of this transaction will be noted in the following column. Example: TXN_MOVE

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#

Occurs as either:

changed or moved other2

Notes a source for the update to this transaction. The format of the output will depend on the type of source identified as the origin of the update.

More information

Supporter Hub MANAGESUPP TXN_MOVE ENS

The update originated from a supporter hub page. Points back to the supporter id of the supporter logged in to the hub where the change originated. Example: hub-2077811

The transaction was modified by a dashboard user. Example: MANAGESUPP

For transactions moved between records, the supporter id of the source record will be reflected here. Example: 2077811

The transaction was modified using a REST service call from an external application. As calls are made by API Users, the source is the username. Example: mobileapp@example.com

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#

When used outside of API page processing, this field may be populated using the URL parameters utm_source or by the generic parameter en_txn1. Content will be automatically truncated if the maximum length is exceeded, and the three last characters replaced by '...' to indicate that a string has been truncated <= 100 characters

External Reference 2#

When used outside of API page processing, this field may be populated using the URL parameters utm_medium or by the generic parameter en_txn2. Content will be automatically truncated if the maximum length is exceeded, and the three last characters replaced by '...' to indicate that a string has been truncated <= 100 characters

External Reference 3#

When used outside of API page processing, this field may be populated using the URL parameters utm_campaign or by the generic parameter en_txn3. Note: Content will be automatically truncated if the maximum length is exceeded, and the three last characters replaced by '...' to indicate that a string has been truncated <= 100 characters

External Reference 4#

When used outside of API page processing, this field may be populated using the URL parameters utm_content or by the generic parameter en_txn4. Note: Content will be automatically truncated if the maximum length is exceeded, and the three last characters replaced by '...' to indicate that a string has been truncated <= 100 characters

External Reference 5#

When used outside of API page processing, this field may be populated using the URL parameters utm_term or by the generic parameter en_txn5. Note: Content will be automatically truncated if the maximum length is exceeded, and the three last characters replaced by '...' to indicate that a string has been truncated <= 100 characters

External Reference 6#

When used outside of API page processing, this field may also be populated by a user-defined page property [Page > Admin > Campaign References], or by the url query parameter en_txn6. When added as a page parameter, the field is referred to as Campaign Reference 1 in the dashboard settings. If a value is presented in both places, the url query parameter will take precedence. Note: Content will be automatically truncated if the maximum length is exceeded, and the three last characters replaced by '...' to indicate that a string has been truncated <= 100 characters

External Reference 7#

When used outside of API page processing, this field may also be populated by a user-defined page property [Page > Admin > Campaign References], or by the url query parameter en_txn7. When added as a page parameter, the field is referred to as Campaign Reference 2 in the dashboard settings. If a value is presented in both places, the url query parameter will take precedence. Note: Content will be automatically truncated if the maximum length is exceeded, and the three last characters replaced by '...' to indicate that a string has been truncated <= 100 characters

External Reference 8#

When used outside of API page processing, this field may also be populated by a user-defined page property [Page > Admin > Campaign References], or by the url query parameter en_txn8. When added as a page parameter, the field is referred to as Campaign Reference 3 in the dashboard settings. If a value is presented in both places, the url query parameter will take precedence. Note: Content will be automatically truncated if the maximum length is exceeded, and the three last characters replaced by '...' to indicate that a string has been truncated <= 100 characters

External Reference 9#

When used outside of API page processing, this field may also be populated by a user-defined page property [Page > Admin > Campaign References], or by the url query parameter en_txn9. When added as a page parameter, the field is referred to as Campaign Reference 4 in the dashboard settings. If a value is presented in both places, the url query parameter will take precedence. Note: Content will be automatically truncated if the maximum length is exceeded, and the three last characters replaced by '...' to indicate that a string has been truncated <= 100 characters

External Reference 10#

When used outside of API page processing, this field may also be populated by a user-defined page property [Page > Admin > Campaign References], or by the url query parameter en_txn10. When added as a page parameter, the field is referred to as Campaign Reference 5 in the dashboard settings. If a value is presented in both places, the url query parameter will take precedence. Note: Content will be automatically truncated if the maximum length is exceeded, and the three last characters replaced by '...' to indicate that a string has been truncated <= 100 characters

Origin Source#

The name of this origin source as specified by the user. The available Origin Sources can be managed through the Pages > Components > Origin Source section in the dashboard.

Example: ECF

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

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