Integrations
Card payments (Authorize.net)
How MoveBoard charges cards through your Authorize.net account — the keys, what's kept, refunds and voids, and how to check it's working.
- 2 min read
- Checked against MoveBoard
- For owners & admins
On this page
MoveBoard charges cards through Authorize.net, using your own merchant account. The money goes straight to your account; MoveBoard never holds it.
Before you start
You need an Authorize.net merchant account. Each branch can have its own.
Connect your account
- In Authorize.net, create an API Login ID and a Transaction Key (step by step: Payment processing).
- In MoveBoard, open Settings › Payments & billing › Payment processing.
- Type the API Login ID and the Transaction Key in the Authorize.net card and press Save.
A saved key shows as dots and is never shown again. Typing over it replaces it — do this when you make a new Transaction Key in Authorize.net, or the old one stops working and so do your charges.
What goes through Authorize.net
- Deposits — charged in the office, from the deposit link, or when the customer books online.
- Card payments on an order or an invoice, in the office, the customer portal or on the bill of lading.
- Cards on file — kept at Authorize.net; MoveBoard keeps only a reference, the last four digits and the expiry. A card is checked with the bank before it's kept.
- Refunds — go back to the card through Authorize.net.
- Voids — a charge that hasn't settled yet (usually the same day) is voided instead of refunded, so it never reaches the customer's statement.
- Storage recurring charges.
The card number never touches MoveBoard: the browser hands it to Authorize.net's secure form, and MoveBoard receives only a one-time token. See Card security.
Card fees and the cash discount
What you add for paying by card, or take off for cash, is set separately on Settings › Payments & billing › Payment & processing fees — see Card fees and the cash discount.
Is it working?
There's no test mode in your company: every charge is real. To check a new connection, charge a small amount to your own card on a test order, then void it the same day from the order's Payments window.
If something goes wrong
- A charge declined by the bank shows the bank's reason — see When a card is declined.
- Every charge fails right after you changed keys in Authorize.net — the Transaction Key in MoveBoard is the old one. Make a new one and save it here.
- That could not be saved on the settings page — check both keys and try again.
Related guides
- SettingsPayment processingConnect your card processor — your Authorize.net API Login ID and Transaction Key — so deposits and card payments go through.
- Booking & paymentsHow card data is keptWhere a customer's card number goes when it's typed into MoveBoard — and what MoveBoard keeps.
- Booking & paymentsCards on fileSave a customer's card, charge it later, pick the default card and take a card off the file.
- Booking & paymentsRefund or void a paymentGive money back on a card, cash, check or other payment — or void a card charge that hasn't settled yet.
- Booking & paymentsWhen a card is declinedWhat happens when a card charge is declined or the card processor doesn't answer — and what to do next.
Still stuck? A person will help.
Open a ticket from Support inside MoveBoard, or email us — we usually reply within one business day.