There are few key restrictions regarding how the Authorize.net gateway works within the BookingCenter MyPMS system, as compared to the other MyCard solutions offered. 

Authorize.net operates within the following within MyPMS.

  1. Authorize.net can't provide lodging accounts - meaning card swipe/present; EMV 'dip/tap', auth management, incremental auths, void auths (all events a Lodging PMS does daily) cannot be accessed with an Authorize.net account.  Only Vital/TSYS/VisaNet/VersioPay/Global/Stripe accounts (together, what we call MyCard) can provide these services for a Lodging merchant. 
  2. All transactions are 'authorize and capture'.   There is no 'authorization' management, so every payment and credit on a folio occurs automatically, there is no 'net' resolution of payments and credits on a given day between, so each transaction on the folio will appear on a card holder's statement.
  3. Authorize.Net is an 'auto batch' system.  This means your account will batch at the time it's set each day in Authorize.Net (usually midnight), there are no controls via the Night Audit tools to settle batches.
  4. You are not able to issue just an 'authorization', as all transactions are both authorize and capture.
    1. The Auth feature is not available in the 'Manage Credit Cards' screen.
  5. If you wish to 'Void' a transaction, this must be done within the Authorize.net portal.
    1. By void, we mean either a full refund or partial refund of a transaction that has not yet settled
  6. Refunds can be issued. 
    1. They can only be issued on a settled transaction, and/or
    2. Can only refund the original amount or a value less than the original amount. For example, if the original payment was for $100.00, you can only refund the $100.00 or less; not anything over $100.00.
    3. As refunds can only be issued against an existing transaction, you cannot refund a new card that does not have an existing payment.
  7. For any deposits that you wish to charge for booking engine reservations (i.e. first night's deposit), please let our support department know and we can have this enabled for you.
  8. The functionality under 'Authorization' (described in SETUP  | PMS | SETUP) does not apply to Authorize.net within MyPMS. 

Onboarding requirements for Authorize.net

We require the 'API Transaction Key' credentials to connect to the your Authorize.Net account.  It's usually best to also send a Parameter Form/VAR Sheet from the merchant banker in case we have troubles, but we should only need your 'API Transaction Key' credentials to connect.