PACR
Peer-to-Peer Registration Additional Donation - Recurring#
Occurence: The participant added a recurring donation schedule when signing up.
Co-occurence: When the additional donation is made as part of registration, a PPAY transaction will detail the fee paid for taking part - which may or may not be considered for inclusion in fundraising totals for the site.
Key Data: Details a donation made by the fundraiser themselves. The donation is associated with a page, identified by the page identifier. The transactions details the amount, currency and transaction identifiers. Note that in the case of co-occurence with other transaction types, the Registration Payment and any associated 'additional donation' are processed as part of the same transaction by the payment gateway, thus the transaction identifier will be the same for these.
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 database identifier of a page belonging to a fundraiser.
Example: 4031
Campaign Type#
PACR
Campaign ID#
A reference name given to this fundraisers's page.
<= 100 characters
Campaign Status#
Describes the status of a recurring transaction, as reported by the payment gateway (if applicable).
Occurs as either:
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 internal 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. 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 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 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:
N/A. A status is not be provided for payments that are 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:
import The transaction was imported into the system from an external source, typically for reporting or segmentation purposes.
ACI Gateway
Bank Payment Gateway Used to handle payment details securely using an Encrypted Bank Store.
Chariot Gateway Used to handle donations commited to a Donor Advised Fund.
IATS North America
IATS United Kingdom
Moneris eSelect Canada
Moneris eSelect Vault Canada
Moneris eSelect Vault US
Optimal Payments Gateway Now known simply as Paysafe.
PayPal Gateway
PayPal One Touch
Payflow Gateway
RBS Gateway This payment gateway is now known simply as WorldPay
RSM Credit Card
RSM PDD Handles Paperless Direct Debit transactions submitted to RSM2000.
Stripe Gateway
Vantiv Gateway
Vantiv ACH Gateway
OFFLINE Recorded as having occured 'offline', typically reserved for cash or check type payments. Transactions originating from fundraisers using the Amplify dashboard may be attributed to this type.
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 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#
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#
No output for this transaction type.
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:
Where (the target or purpose) the donor specified that 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.
<= 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