Back-charge	The charge made to collect a transaction that was incurred but not charged in a previous billing period. Reasons might include the recipient's non-payment, an adjustment, or the delay in billing certain expenses until a later period. This can happen in situations like charging for donations that weren't billed between the stop processing date and the migration date.
Merchant processor	The front-end (supporter-facing) stakeholder that maintains the merchant's account to initiate and authorize transactions. Merchants do not deal directly with the processor during the payment process. It is important to note that Fundraise Up is a merchant processor and not a payment processor.
Payment processor / Payment gateway	The back-end stakeholder that is only responsible for processing payments and routing the information through the card network to the customer's issuing bank for authorization. For example, Stripe is our primary payment processor, and PayPal is a secondary one.
Payment token	A unique, secure representation of sensitive card or bank account information. It's used during transactions to protect the actual data, reducing the risk of fraud or unauthorized access.
Pretty Good Privacy (PGP)	A data encryption and decryption tool that provides cryptographic privacy and authentication for data communications. It's used to secure email, files, and other data transfers to ensure privacy and secure information exchange.
Secure File Transfer Protocol (SFTP)	A network protocol used to securely transfer files over a Secure Shell (SSH) data stream, providing both encryption and secure file transfer.
Stop processing date and time	The specific date and time when recurring plans that are going to be migrated should be stop being charged by your legacy payment or merchant processor.