Our client does not want to support bank accounts. They want all Payment Profiles created to be linked to Credit Cards. They do not want to deal with any PCI consequences so they asked us to develop the application in such a way that all Payment Profiles are created directly in the Authorize.Net web application, using the Hosted Pages feature. Since that is the case, we (the developers) have no way of controlling what type of Payment Profile is the customer creating. Is there a way to set a flag in the client's Merchant Account Settings, to tell Authorize.Net that it shouldn't allow the client's customers to create Payment Profiles linked to bank accounts?
Solved! Go to Solution.