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.
As mentioned in the following post:
The card expiry date is masked when returned in the getCustomerProfileRequest. As the card number is masked, there is no PCI requirement that the expiry date of the card also be masked. Without the expiry date, it makes it impossible for us to automate the process of notifying our customer's clients that their card will be soon expiring. The reason for us going this route is to offer an ARB solution managed completely from within our application. It is imparative for us to have access to this date.
The idea is a simple one. Return the expiry date in the CIM getCustomerProfileRequest unmasked.
The ID of a duplicate customer profile is returned, but not when it is a payment profile: "A duplicate customer payment profile already exists." These requests date back to 2009, it forces us to loop through the payments and try to guess at which one is the duplicate and doesn't always work since customers can still generate duplicates anyway by updating existing profiles. It would be nice if there was a way to get the ID of the duplicate payment profile, or if there was a way to disable the duplicate verification check completely, since what some merchants really need is just a "I give you a PAN, you give me a token" level of tokenization instead of futzing with profiles. Thanks.
Authorize.Net already supports integration through Sync for Quickbooks. See more details at http://www.authorize.net/solutions/merchantsolutions/merchantservices/syncforquickbooks/
Would like to be able to customize the pop up for managing payment profiles. It would be great if the Payment Form Fields configuration checkboxes applied to this, so that for example we could turn off the shipping address. A seperate place to configure this would also be fine.
Product Idea based on previous thread: http://community.developer.authorize.net/t5/Integration-and-Testing/ARB-from-prior-tran-instead-of-c...
Currently, to avoid most PCI compliance, the hosted CIM is the suggested solution. The problem with this solution is that it is very clunky and does not integrate well with any custom interface. It uses an Iframe solution in which you have no control over the appearance of the form fields.