This request updates a customer's existing Payment Profile.
General
This request updates an existing payment profile. Here's what you need to know about updating payment profiles:
- Payment profiles are always created via Secure Payments. Even when creating a payment profile in the LMS UI, you are actually creating it in Secure Payments via an iframe.
- This request updates basic payment profile information. If account number or card number information needs to be updated, a new payment profile should be created.
- A customer can have more than one associated payment profile.
- Payment profiles can either be bank accounts or credit/debit cards.
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)
{
"PaymentAccounts": {
"results": [
{
"title": "Credit Card",
"isPrimary": 0,
"isSecondary": 1,
"active": 0,
"__id": 363,
"__update": true
}
]
}
}
Try It Instructions
Our pages often provide sample payload information so that you can try requests yourself. This request is ready for you—expand the object by clicking the "+" symbol and hit the Try It button to send the request.
If you would like to try this request with your own tenant account, make sure to change the headers to match your own authentication information.