ACS
Peer-to-Peer Credit Single#
Occurence: A supporter has made a single gift to a fundraiser's Peer-to-Peer page.
Key Data: Details about the supporter and the donation, including amount and currency.
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#
ACSThe Campaign Type is used to determine the layout of the data columns in the output stream.
Campaign ID#
Peer-to-Peer Campaign Reference Name
<= 160 characters
Example: Runaround Challenge
Campaign Date#
The recorded date [YYYY-MM-DD] of this transaction. If left blank during transactional import, the service will apply the import date. The reference timezone for this service is US/Eastern.
Example: 2024-12-01
Campaign Time#
The recorded time [HH:MM:SS] of this transaction. The reference timezone for this service is US/Eastern.
Example: 13:53:02
Default: 00:00:00
Campaign Status#
Describes the status of a transaction, as reported by a payment gateway (if applicable).
Allowed values:
success
reject
refund
change
Example: change [ tax deductible: Y ]
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#
Occurs as either:
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 donations, 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
Example: VISA
refund 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 transaction marked as a refund will not include any data submitted with the donation to the tagged fields Other 1 to 4.
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#
Y if this transaction describes a refund.
Allowed values:
Y
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 involvement of a payment gateway, and are output as separate transaction types.
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 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#
Apply this donation to a given pledge. Default: 0
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 internal database identifier of the transaction. Example:
414664
The internal database identifier assigned to a fundraising 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#
The amount to be considered as a donation and not part of purchase.
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.
If the Campaign Status is reported as change, this entry describes the change that has been made to the transaction.
Example: change [tax deductible: true]
refund 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 transaction marked as a refund will not include any data submitted with the donation to the tagged fields Other 1 to 4.
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 note relating to the transaction.
Example: Self-Donation at Registration
Campaign Data 26#
Amount in USD if available - use for reporting only - converted at the time of a successful transaction.
Example: 1.3
Default: 0
Campaign Data 27#
Amount in GBP if available - use for reporting only - converted at the time of a successful transaction.
Example: 1.0
Default: 0
Campaign Data 28#
Amount in EUR if available - use for reporting only - converted at the time of a successful transaction.
Example: 1.19
Default: 0
Campaign Data 29#
Amount in CAD if available - use for reporting only - converted at the time of a successful transaction.
Example: 1.77
Default: 0
Campaign Data 30#
Amount in AUD if available - use for reporting only - converted at the time of a successful transaction.
Example: 1.91
Default: 0
Campaign Data 31#
No output for this transaction type.
Campaign Data 32#
No output for this transaction type.
Campaign Data 33#
No output for this transaction type.
Campaign Data 34#
No output for this transaction type.
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.
Using appealCode with ENS
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
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