Have your own great idea for a new API feature?
or maybe a suggested improvement to an existing one? Share it and become a god of the developer world.
We are a software developer with an interface to Authorize.net's API for storing card data using Customer Information Manager and issuing transactions based on the saved payment profiles.
A number of our clients separate credit card transactions by card type. To do this we need to know the card type for a payment profile saved in CIM. This information does not appear to be in your CIM documentation. Are there any plans for returning this data?
I don't think it's fair to put the status to delivered, (as @cggamer alluded to) as the request was specifically for getCustomerProfileRequest. It's nice that it was delivered for getCustomerPaymentProfileRequest but this means that you have to do multiple requests to show a customer's full profile, which I'm guessing most systems (including mine) would rather not.
It is unclear whether or not Authorize.net supports readers where the manufacturer is able to perform key injection of an encryption key provided by Authorize.net. This seems like a straight-forward concept that should be documented on the mobile reader support page. Forum posts (other than mine) indicate confusion about this issue. Unfortunately, the support reps don't really understand the question and can only answer based on what they read from the site, so calling support does not help.
Product Idea based on previous thread: http://community.developer.authorize.net/t5/Integration-and-Testing/ARB-from-prior-tran-instead-of-c...
A way to email a simple checkout link would be great. I give custom quotes and it is very difficult to create a simple checkout button, then create a new page on my website then email the link to my customer, have the customer browse to my website, click the checkout button and enter their information.
It would be much easier if I could email them the simple checkout link, then have them click the link from directly in their email and checkout.
I suggest its good if we can send parameters and enable/disable payment options (credit card/bank account) in "Get an Accept Payment Page" API request. Adding to that it would be nice if we can control credit card types (VISA/MASTER/AMEX/etc.) as well. Then user can only pay using allowed credit card type if it is a credit card payment.
I need to be able to create new payment profiles on existing customer profiles at the same time as a transaction is being done, so I can skip the test transaction step. Currently, I can create new payment profiles with an authCaptureTransaction only if I also want a new customer profile. I am getting lots of complaints about the test transactions, and this would solve the problem.
Our store uses WooCommerce (WordPress) and we use Google Analytics to track our transactions. Because users leave our site to make their payment via Authorize.net, Google Analytics is unable to correctly attribute the subsequent conversions (showing as referrals from authorize.net).
We've setup Analytics in Tag Manager and have enabled third party cookies (auto link domains), but without actually adding the code to the authorize.net pages, this is useless. I've seen many places where your customers ask this exact question and yet I've not seen a single workable response. Please create a way customers (or their developers) can enable and implement this tracking continuity.