The Payment Profile object contains payment information for a contact or account. A separate payment profile record is stored as needed, for different credit cards, IBANs, bank account and sort code combinations, etc. The payment profiles are then linked to the installments to indicate what card or bank account should be used when processing this payment.
FinDock does not store the card primary account number (PAN), rather only tokenized information on the payment profile.
When dealing with changes to the account number or card information, we recommend creating a new payment profile record rather than updating the existing record. This preserves the history of existing payments and installments related to the original profile information.
Different types of information in the payment profile object are separated by using Record Types. These record types allow you to configure different page-layouts for each type of payment profile such as Credit card, IBAN, bank account, etc. For more information about working with Record Types and page-layouts, see Assign Page Layouts to Profiles or Record Types.
Identification and uniqueness
The Payment Profile object includes two fields for identification and enforcing uniqueness: Primary Identifier and Unique Identifier.
The Primary Identifier field is an indexed identification field that can be queried by processes like Guided Matching. The field value is determined by Record Type (account, credit card, etc.).
The Unique Identifier field is an indexed field with an enforceable, unique value that is upserted during Guided Matching processing. When uniqueness is enforced (FinDock Core general setting - disabled by default), this field ensures duplicate records are not created because of parallel processing. The Unique Identifier value is composed of the following elements:
Record Type Name + Primary Identifier + Wallet Type + 18 char Contact Id (or Account Id).
All elements are separated by an underscore.