Set Payment Profile as Primary

General

This request allows you to set a payment profile as primary or secondary. Here's what you need to know about this request:

• The current primary payment profile must be listed in the payload first. The system begins by updating the primary payment profile and then updates the subsequent payment profiles.
• Only one payment profile can be listed as primary.
• Payment profiles are always edited via Secure Payments. Even when editing a payment profile in the LMS UI, you are actually editing it in Secure Payments via an iframe.

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

Database

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

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

{    
    "PaymentAccounts":{        
        "results":[          
        {              
            "id":307,            
            "isPrimary": 0,            
            "isSecondary": 0,            
            "__id":307,            
            "__update":true        
        },        
        {              
            "id":320,            
            "isPrimary": 1,            
            "isSecondary": 0,            
            "__id":320,            
            "__update":true        
        }      
        ]  
    }
}

📘

Try It Instructions

Our requests often provide sample payload information so that you can receive a 200 response from simply hitting the Try It button. This request is ready for you—expand the PaymentAccounts object and hit Try It to send the request.

However, 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.