On Wednesday, August 12, the American Booksellers Association hosted a webinar for IndieCommerce stores that are transitioning from ABA’s credit card processor to their own credit card processor.

A recording of this webinar, led by IndieCommerce Senior Manager Geetha Nathan, can be found on BookWeb.org [6] and includes demonstrations of new IndieCommerce site features, a walkthrough of where to find and configure information on Authorize.net, and more.

Here are some of the key points from the session:

• Most bookstores already have merchant accounts if they are accepting credit cards for in-store transactions. Those who are creating a new merchant account must be sure that it can work with Authorize.net and process all four major card types.
  • ABA has identified Gravity Payments as an option for IndieCommerce stores; this service also has a pre-negotiated rate.
• Merchant accounts will require certain information to be on a store’s website, including terms and conditions, a privacy policy, a refund/return policy, shipping and payment information, and contact information, before an account can be created.
• Merchant service providers may be able to set up an Authorize.net account for users, but if they don’t, booksellers are welcome to set one up themselves. Be sure these two features are activated: Customer Information Manager (CIM) and Advanced Fraud Detection Suite (AFDS).
  • With the Customer Information Manager, customers can save their payment profiles for future orders.
  • AFDS offers 13 configurable filters for preventing fraudulent transactions
  • An optional feature is Automated Recurring Billing (ARB), which can be used to charge customers for any recurring payments.
• Once set up, IndieCommerce users must submit their API Login ID, transaction key, and public client key through a secure form on their IndieCommerce website (Store > Configuration > Account Information and Preferences > Store Authorize.net). Do not email this information to the IndieCommerce team.
• While booksellers can change their merchant account, they cannot change their Authorize.net account, as they will lose their customer payment information.
• There are many advantages for booksellers who have their own credit card processor, including:
  • No need to wait for ABA to transfer funds for online sales.
  • The store name will appear on a customer’s credit card statement instead of “INDEPENDENT BOOKSTORE.”
  • The automated recurring billing feature can be activated.
  • Booksellers can choose fraud protection settings they’re comfortable with.
  • Booksellers will receive better credit card fees.
  • The Authorize.net Verified Merchant Seal will increase customer confidence.
  • Booksellers will have more control over online credit card transactions.
  • Booksellers can refund customers directly from their IndieCommerce website.
• To prepare for the transition, booksellers should:
  • Get a merchant account for processing online credit card transactions
  • Create and configure an Authorize.net payment gateway account
  • Contact Authorize.net support and confirm the account is ready
  • Submit the API Login ID, Transaction Key, and Public Client Key on their IndieCommerce site
  • Process open credit card orders (mark orders as “Payment Received” or “Cancelled”)
  • Stop Ingram orders a week before the switchover date (pre-orders sent to Ingram are okay)
• On the day of the switchover, booksellers should:
  • Disable the credit card payment method on the website
  • Post a message to let customers know and provide alternative payment methods
  • Be available by phone or email to coordinate with an IndieCommerce team member
  • Be ready to log in to their Authorize.net account
  • Be ready to be their first “customer” on their credit card processor
  • If there are no issues, the switch should only take 15 minutes.
• The IndieCommerce team has introduced two critical features to accompany this transition. Stores that have their own credit card processor will also be able to charge customers for additional books on orders that have already been charged. Stores can also edit “Payment Received” orders and refund customers. Both transactions can be initiated from the order page on the IndieCommerce site.
  • View a demonstration of these new features here [7].