Yikes. That's too bad. Bookerville's process really needs a super-lean and streamlined payment for end customers. Our vacation rental managers like to collect a down-payment of sorts for the rental, which is calculated and shown during the booking process. Right now, customers are shown a nice, simple, obvious button to click which takes them to an Auth.net hosted page where they fill out their details, enter their CC information, and pay. Very simple, very clean, very effective, most people do not get confused.
It's too bad AN can't just create a profile at that time and store it for the merchant, passing the new ids/tokens in the callback (and Silent Post), all without Bookerville having to implement this very tedious CIM process. I am at loss to understand the security issues around that? I mean, I understand if you're a Merchant-Hosted site trying to implement a (nearly) full-featured virtual terminal, but goodness that's not what we're trying to do. It would just be very nice if merchants could sign in to their accounts and be able to pull up credit card data for previous customers, without having to tell AN to do it through this convoluted api.
John