ACC
Peer-to-Peer Cash or Check Offline Gift#
Occurence: A gift has been registered as an offline gift (e.g someone donated via cash or check) by a Peer-to-Peer fundraiser.
Key Data: The amount and currency donated, as well as the type of donation (e.g cash or check). As this is considered an offline payment method, the payment status will be reported as 'success' for payments made. Note that a donation may also be marked as refunded, which will be reflected by the payment type of 'refund'. Regardless of whether the transaction is a donation or a refund, the amount will occur as a positive decimal number, so the payment type should be considered for reconciliation purposes when dealing with refunds.
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 used to refer to a campaign
Example: 3883
Campaign Type#
ACC
Campaign ID#
Peer-to-Peer Campaign Reference Name
<= 160 characters
Example: Runaround Challenge
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 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#
No output for this transaction type.
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#
Occurs as either:
The payment type recorded for this donation ('cash' or 'check').
Indicates that this payment transaction was marked as a refund for reporting purposes. The actionable part of the refund would be carried out outside of the platform. Note that a refund transaction does not include any data submitted with the donation to the tagged fields Other 1 to 4.refund
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#
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#
The unique numerical database identifier for the supporter record of a fundraiser.
Example: 212200
Default: 0
Campaign Data 15#
The email address of a fundraiser, who is also a supporter.
<= 500 characters
Example: otto.nv@example.com
Campaign Data 16#
Peer-to-Peer Site Identifier
Example: 3543
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 database identifier of the transaction. Example: 414664
The 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#
Occurs as either:
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.
Indicates that this payment transaction was marked as a refund for reporting purposes. The actionable part of the refund would be carried out outside of the platform. Note that a refund transaction does not include any data submitted with the donation to the tagged fields Other 1 to 4.refund
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#
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