Good morning Andy! I passed the questions along to our ecommerce team and they provided the following:
I’m assuming the endpoint they are referring is
/v1/contacts/{contactId}/creditCards
When adding a credit card, is it authorizing it in a merchant account as a part of the process?
Yes, the information is being sent to the processor(s) to perform their own authorization of the card information.
How does it know which merchant account to choose? In the case of the API, it seems to be choosing the very first one it comes across - in our case, it’s this Test Account.
If there exists multiple AuthNet accounts connected, then the card will be authorized through through each of them
How do we get it to not use certain merchant accounts?
There isn’t a way in the v1 to select/ignore a merchant. If they use the v2 method of adding payment method via the JS package, then the payment method added will be based on the default merchant,
Outside of API usage, we actually went into the Keap interface to try and edit the Test Account, and it keeps presenting us with an error. This makes me think this Merchant Account is somehow bugged, and it won’t let us do anything about it. What recourse can we take regarding this? I’ve already chatted with support regarding this, but there was nothing they could do.
Sounds like an issue we could investigate, but it would have to go through the Keap Support process for us to receive a ticket in order to resolve.