Glossary-Payments

Australian Bankers Association (ABA) 

ABA stands for Australian Bankers Association and is used in reference to a specific, standardized file format used in the payment transactions of direct debits, especially in batch use. 

Closed Lost 

One of several opportunity stage combinations, Closed Lost refers to an opportunity which was unsuccessfully processed, including after the maximum number of configured retries was met. A successfully processed opportunity is said to be Closed Won. 

Closed Won 

One of several opportunity stage combinations, Closed Won refers to an opportunity which is successfully processed. An unsuccessfully processed opportunity is said to be Closed Lost. 

Comms Log 

Log, current or historic, of what fulfilment will happen or has happened. Coms Log processing will see that there is a log what needs to be sent or…after fulfillment, a record is retained in log…Coms Log is a custom object. 

Customer Registration Number (CRN) 

A form of identification used by banks to ensure a customer’s identity has been verified 

Fulfilment Channel 

Email, mail, etc. 

General Ledger Code (GL Code) 

GL or General ledger code is a code for an entry in the Accounting Systems General Ledger. GL codes are associated with both GAUs and Bank Accounts to facilitate the transfer of general ledger data to the Accounting Platform. 

Lightning Web Component (LWC) 

A Salesforce feature which enables organisations to build custom user interfaces, web and mobile apps on the Salesforce platform.  

Payment Card Industry Data Security Standard  (PCI DSS) 

Payment Card Industry Data Security Standard is actually a group of standards designed to ensure the protection of credit card data from misuse or theft. The PCI DSS standards provide guidelines for credit card detail communications, storage, use and destruction. Many banks will require that an organization complies with PCI DSS requirements before they will provide credit card merchant status. 

Payment Component 

Inside Pronto Payments, it is a piece of flow you can call from – FLOW, APEX, LWC (Salesforce codes) 

Payment Gateway 

A Payment Gateway is a platform which facilitates the clearance of payment transactions normally through credit card and/or direct debit transactions. It is necessary to have at least one payment gateway in order to facilitate the clearance of these types of transactions although some organizations use multiple payment gateways. For a list of Payment Gateways supported by the AlphaSys Fund raising Accelerator please Contact the AlphaSys support team. 

Pronto Checkout 

Inside Pronto Payments, it is a flow that uses the Payment Component. 

ProntoPayments (PPayment) 

The name of the Posimente product for payment processing. 

Retry 

A Retry is a system automation which attempts to process a payment when previous attempts failed. You configure the number of retries to attempt in your setup. 

Salesforce Nonprofit Service Platform (SNSP) 

Refers to base installation type of a Salesforce org. 

Soft Decline 

A soft decline is a standard payment processing function with a related transaction code which records a payment which has not cleared due to a likely remediable issue, such as insufficient funds. 

Tokenisation 

Tokenisation is a security facility provided by the Fundraising Accelerator and your Payment Gateway to eliminate the need to store credit card numbers and other details in your Fundraising data base where there can be a security risk. When the Fundraising Accelerator is used with a payment gateway that supports tokenization, any time an operator enters a credit card number and other details into your Salesforce Platform it is quickly transferred to your Payment Gateway which returns a token, which is what is stored in the Salesforce database. The credit card details themselves are then discarded without storage except for the first 6 and last 4 digits of the card number to facilitate the identification of the token. Tokens are then used to complete the credit clearance process, and in some cases, the token can be reused for future transactions eliminating the need for operators to rekey credit card details when a supporter wishes to use a card they have used previously. Tokenisation is an important part of the PCIDSS process. 

The process of taking a customer’s credit card number, storing it in a highly secure encryption appliance and then replacing it with a surrogate value known as a “token”. The payment system can then use this token value when processing payments to retrieve the customer’s credit card number. The token itself is not a sensitive piece of data and can be stored in an external system and used in future transactions instead of the credit card number.‏