How to Prepare a Gravity Payments Account for Sales

By Jordan Lee, merchant-onboarding documentation editor (editorial persona)
Last reviewed: July 12, 2026

Gravity Payments says account approval normally takes one to two business days, followed by two to three business days for equipment shipping. That does not necessarily mean a business will be processing within five days, because software integration, network preparation, device activation and staff testing may extend the launch.

This independent guide is not operated by Gravity Payments and cannot approve, activate or change a merchant account.

What Gravity Payments onboarding includes

Gravity Payments provides merchant accounts, payment terminals, online tools and software-connected processing for independent businesses. The setup path depends on whether payments will be accepted through a standalone terminal, a point-of-sale integration, Gravity Dashboard or an industry-specific platform.

A typical launch has several separate milestones:

  1. Merchant-account review and approval
  2. Equipment selection and shipment
  3. Internet and physical installation
  4. Terminal or software activation
  5. Test transactions and reporting checks
  6. Staff access and PCI-related work

Treat approval as the start. Skip plans based solely on the shipping estimate, particularly when a point-of-sale vendor or software developer must also configure the payment connection.

Approval and shipping time

Gravity’s published timeline is brief: approval takes one to two business days, and approved equipment ships in another two to three business days. The company does not promise a universal delivery date or total implementation time on that support page.

Choose the payment method before the device

Gravity’s current hardware catalog separates devices by operating model. Some are marked as standalone terminals, while others are described as integration-only equipment intended to work with compatible software. Buying the cheapest reader before checking the business workflow is the wrong priority.

Device listed by GravityPublished priceListed use
Swipe Simple B350$120Standalone
PAX A80$250Standalone, surcharge-capable
FD150$300Standalone
Clover Flex Gen 4From $750Integration-capable, surcharge-capable
MagTek iDynamo$199Integration-only
PAX A35$425Integration-only

Prices and device labels were displayed on Gravity’s U.S. hardware page when reviewed on July 12, 2026. Gravity also tells merchants to ask about available rental options. Equipment selection and quoted costs may vary by account or required configuration.

A countertop business that only needs card acceptance may be served by a standalone device. A restaurant, clinic or retailer expecting payments to appear automatically inside business software needs confirmation that the terminal and processor connection are supported by that specific platform.

Do this first.

Ask which system creates the sale, which system records the payment, and whether refunds can be initiated from the same interface. A device marked integration-only may be unusable without the matching software connection, while a standalone terminal may require manual entry into the business’s accounting or order system.

Prepare the network before delivery

Payment equipment should not be tested for the first time during a busy opening shift.

Gravity’s Clover Flex instructions require a working internet connection and describe Wi-Fi or mobile-network activation. For Wi-Fi, the company says the router should use WPA or WPA2 security and operate as a closed, protected network. Businesses offering public Wi-Fi are told to place customers on a different network from the one used for payment processing.

That separation is a practical security control, not merely a performance preference. Customer devices can consume bandwidth, introduce unnecessary exposure and complicate troubleshooting. The payment terminal should have stable coverage where transactions are actually taken, including patios, treatment rooms, service counters or mobile checkout areas.

PAX A80 instructions add several details that are easily missed. Wi-Fi network names and connection details are case-sensitive. When the terminal cannot connect, Gravity recommends powering down both the access point and terminal for approximately three minutes, restoring power, then waiting roughly two minutes before checking again. Moving the terminal closer to the access point can reveal whether the problem is weak coverage rather than account activation.

Intermittent failures deserve a different check. Gravity says nearby access points using the same Wi-Fi channel can contribute to dropped connections. Its guide also identifies microwave ovens and curling irons as equipment that may affect coverage.

Odd, but useful.

Activate a Clover Flex correctly

The Clover Flex setup begins with an activation code delivered through Clover’s activation email. The device is powered on, connected through Wi-Fi or its mobile network, and activated on the device screen before account applications are installed.

Keep the activation message available to the person performing the installation, but do not forward the code to an unsolicited caller or unverified installer.

Clover’s setup screen asks the merchant to select a language and network connection. After a successful network connection is confirmed, the activation code is entered and the device downloads the applications assigned to that account. A device that turns on but lacks the expected applications may not have completed activation or may be attached to the wrong configuration.

The Flex accepts chip cards, magnetic-stripe cards without chips and contactless cards or supported phones. Its package includes a charging cradle, power components, paper roll and quick-start material, according to Gravity’s published guide.

Keep a browser-based backup path

Gravity Dashboard includes a Virtual Terminal that can process a Sale, Authorization, Capture or Force, and Void or Refund when the function is enabled for the merchant account. It is opened from the Virtual Terminal option in the Dashboard’s left control panel.

Gravity also states that a virtual terminal can run through an internet browser on a computer, tablet or smartphone, provided the business has internet access and an eligible merchant account.

That makes it a useful contingency when a physical reader fails. It is not an identical substitute for an in-person terminal: browser-entered payments are card-not-present transactions, and Gravity’s published pricing warns that card-not-present payments may not qualify for its advertised in-person flat rate.

Priority one is restoring the proper terminal. Use the browser method only through the approved account workflow and confirm how those transactions are priced.

Confirm the merchant ID and reporting access

Gravity assigns a Merchant ID, commonly abbreviated MID, to the processing account. The company says the number can be found in the email received after installation or in the upper-left corner of a merchant statement.

The MID matters when opening support requests, choosing certain login routes and identifying the affected account. Businesses with several locations may have more than one relevant merchant account, so a problem reported under the wrong location can slow troubleshooting.

Gravity Dashboard provides transaction activity, batch history, monthly statements and sales reporting. The Virtual Terminal is included when enabled for the account.

Before launch, verify that the expected location appears, a test sale reaches reporting, and the batch can be identified. Do not wait until the first reconciliation to discover that transactions were processed under another location or that a manager lacks statement access.

Common setup mistakes

The first mistake is treating delivered hardware as an activated account. A terminal can power on and connect to Wi-Fi while still waiting for account applications, an activation step or software-side configuration.

The second is connecting payment hardware to guest Wi-Fi. Gravity’s Clover documentation calls for a protected network and recommends a separate network for customers.

Other concrete frictions include:

  • Entering a Wi-Fi network name with incorrect capitalization on a PAX A80
  • Placing a wireless terminal outside reliable access-point coverage
  • Ordering integration-only hardware without confirming software compatibility
  • Looking for the MID before the post-installation email or first statement exists
  • Assuming the Virtual Terminal carries the same rate as an in-person card transaction

One small hardware problem can also look larger than it is. Gravity’s PAX A80 guide says blank receipt paper usually means the thermal roll has been installed backward. The paper should feed from the top of the roll, with approximately three inches pulled out before the lid is closed.

Contact support with the useful details

Gravity publishes 24-hour multilingual support at 866-701-4700. Before calling, its support library recommends confirming that the internet works, checking that devices are connected to power, and having the Merchant ID and any displayed error code available.

Start with the exact device model and the point where setup stops. “Terminal not working” is less useful than identifying whether the device lacks power, cannot join Wi-Fi, rejects activation or processes a sale that never appears in reporting.

Skip factory resets and account removal unless Gravity or the device provider specifically directs the action. Those steps can erase useful configuration or turn one fault into several.

FAQ

How long does Gravity Payments setup take?

Gravity says approval normally takes one to two business days, followed by two to three business days for equipment shipping. Integration, delivery and activation can extend the complete launch beyond that published window.

Does Gravity Payments provide terminals?

Yes. Gravity lists countertop, portable, mobile and integration-only devices, with published purchase prices and possible rental options.

Can Gravity Payments work without a physical terminal?

Sometimes. An enabled Gravity Dashboard Virtual Terminal can accept browser-based payments from an internet-connected device, but those payments are card-not-present and may be priced differently from qualifying in-person transactions.

Why will my PAX A80 not connect?

Check Wi-Fi coverage and confirm that the network details match exactly, including capitalization. Gravity also recommends restarting both the terminal and access point, then allowing time for the connection to return. Persistent or intermittent failures may involve coverage or competing Wi-Fi channels.

Where is the Gravity Payments merchant ID?

In the post-installation email or merchant statement.

Can a Clover Flex use public guest Wi-Fi?

Gravity instructs merchants to use a closed WPA or WPA2-protected network and to provide customers with a separate network. A business should not place its payment terminal on the same guest network offered to visitors.

What should be tested before opening?

Run the approved test workflow, confirm the transaction appears under the correct account or location, inspect receipt printing and verify access to the required reporting tools. For an integrated setup, confirm that the payment is also reflected in the connected business software.

A reliable launch depends less on how quickly the box arrives than on whether the chosen device, network, account and software connection were matched before the first live transaction.

Leave a Reply

Your email address will not be published. Required fields are marked *