Get Payment Profile Information

A Payment Profile allows a customer to make payments on their accounts:

• The PaymentAccounts object holds payment profile information, and it's nested within the Customers entity.
• Payment profiles are always created via Adaptive Wallet (formerly Secure Payments). Even when creating a payment profile in the LMS UI, it is actually creating it in Adaptive Wallet via an iframe.
• Payment profiles are tokenized when they're created for enhanced security. The token that is generated is used in LMS to reference the profile created in Adaptive Wallet. Tokens are never saved in Adaptive Wallet, so it's important to capture them until linking the payment profile to a customer in LMS.
• Payment profiles can either be bank accounts or credit/debit cards.
• Multiple payment profiles can be associated to a customer.

For an example of how payment profiles are linked to customers within the UI, take a look at our Add a Payment Profile article.

Database

For information regarding payment profile database tables, see the following articles:

• Database – Customer Payment Profile Information (payment_account_entity)
• Database – Customer Main Table (customer_entity)