Browse the guide

Payment Extension – install & connect

Get the browser extension installed and connected to your account in a few minutes.

On this page

Install the extension

The Merchant360 Payment Extension adds a small payment button to your Chrome or Edge browser. Use it when you take payments while working inside other software, such as a booking system, a CRM, or a web-based order screen, and you do not want to switch tabs to your virtual terminal.

Install it from the Chrome Web Store. Search for "Merchant360 Payment Extension", or use the Install button at merchant360.com/extension. One click adds it to Chrome or Edge. Nothing needs to be installed on the computer itself, and no card data is ever stored in the browser.

After it installs, the Merchant360 icon appears in the toolbar. Click the puzzle piece icon in the browser toolbar and pin Merchant360 so the button is always visible. Each person who takes payments installs the extension in their own browser profile and connects it with their own Merchant360 login.

You are done with this step when the Merchant360 icon shows in your toolbar and clicking it opens the extension's connect view.

If the icon does not appear after installing, open the puzzle piece menu in the toolbar and pin the extension from there. If the store page says the extension is not available, make sure you are using Chrome or Edge, since other browsers are not supported.

  1. 1Open Chrome or Edge on the computer where you take payments.
  2. 2Go to merchant360.com/extension and press Install, or search the Chrome Web Store for "Merchant360 Payment Extension".
  3. 3On the store page, press Add to Chrome, then Add extension.
  4. 4Click the puzzle piece icon at the top right of the browser and click the pin next to Merchant360.
  5. 5Click the Merchant360 icon. The extension opens to Take payments anywhere with the Connect with Merchant360 button.
On this screenWhat it does
Install button (merchant360.com/extension)Opens the Chrome Web Store listing for the extension. Clicking Add to Chrome installs it in the current browser profile.
Puzzle piece icon (browser toolbar)Lists your installed extensions. Pinning Merchant360 keeps its icon visible in the toolbar so you can open it with one click.
Merchant360 iconOpens the extension. Before it is connected it shows the connect view; after it is connected it shows the payment view.

Authorize the connection

The Connect the Payment Extension page shows exactly what you are granting. The extension can open hosted checkouts at amounts you choose in your software, and it can read the result of those checkouts, meaning the transaction ID, amount, and card last four. It cannot read card data, cannot use saved cards, and cannot change anything on your account.

Tick Connect in test mode first if you want to rehearse with no real charges. A test connection uses a sandbox key, so every payment is simulated and shows on the Test mode page instead of your live Transactions. Reconnect without the box ticked when you are ready to take real payments.

Click Authorize & connect. Because this creates an API key, Merchant360 sends a six-digit security code and asks for it before continuing. The code is texted to the mobile number on your login, or emailed if your login gets its codes by email or has no mobile number. The box that asks for the code shows where it went. Enter the code, and the page shows Connected and hands the key to the extension. The tab closes itself, or tells you it can be closed.

You are done when the page reads that the extension is connected and you can close the tab. The key is stored only inside the extension in this browser profile. It never appears on screen.

If the page stays on Handing the key to the extension for more than a few seconds, the extension is probably not installed in this browser profile. The page shows a hint after twenty seconds. Install the extension, then start the connection again from the extension. If the security code does not arrive, see If the security code does not arrive at the end of this chapter.

  1. 1Read the list under This will let the extension. It can open checkouts and read their results, nothing else.
  2. 2To practice with no real charges, tick Connect in test mode. Leave it unticked to take real payments.
  3. 3Click Authorize & connect. A Security check box opens and says where the code was sent.
  4. 4Type the six-digit code and press OK. If the code is not coming, press Email me a code instead (or Text me a code instead). If you use an authenticator app, you can type its six-digit code instead, or one of your backup codes.
  5. 5Wait for Connected. The tab closes itself or tells you it can be closed, and the extension turns green.
The Merchant360 consent page listing exactly what the extension can do
Review what the extension can do – open secure checkouts and read their results, nothing else – and click Authorize & connect.
On this screenWhat it does
This will let the extension (list)Shows the three grants: open hosted checkouts at amounts you choose, read the result of those checkouts, and nothing else. This is the full scope of the key that will be created.
Connect in test mode (sandbox, no real charges)Creates a test key instead of a live one. Payments taken through the extension are simulated and appear under Billing tools, Settings, Test mode.
Authorize & connectAsks for a six-digit security code, then creates the key and publishes it to the extension. While it works the button reads Connecting.
Security check boxSays where the code was sent and takes the code. Also accepts the six-digit code from your authenticator app, or a backup code, when your login has them.
Email me a code instead / Text me a code insteadSends a fresh code by the other channel. Shown when your login has both an email address and a mobile number.
ConnectedConfirms the key was created. Handing the key to the extension means the page is waiting for the extension to claim it; once claimed it reads that you can close this tab.
Extension not installed hintAppears after about twenty seconds if nothing claims the key. It tells you to install the extension in this browser profile and try again.

Confirm you're connected

Once connected, the extension shows a green confirmation. From this point every payment you start from the extension opens a secure hosted checkout on Merchant360, and the result comes back into the extension when the customer or your staff finishes.

There are three ways to start a payment. Key an amount into the extension to open the secure checkout. Send an amount to your card terminal so the customer can tap or insert their card. Or highlight an amount on any web page, right-click, and choose Charge with Merchant360.

Every payment taken this way shows in Billing tools, Transactions, with the same receipt, refund, and void controls as any other sale. Test connections show their payments on the Test mode page instead.

You are done when the extension shows the green connected state and a test payment appears in Transactions, or in Test mode if you connected in test mode.

If the extension still shows the connect view after you authorized, close and reopen the extension. If it asks you to connect again, the key was not claimed. Run the automatic connection again from the extension, and keep the Merchant360 tab open until it says the extension is connected.

The extension showing the green connected confirmation
The green confirmation means you're live – start taking payments.
On this screenWhat it does
Green connected confirmationShows the extension holds a valid key for your account. Click the icon to open the payment view.
Key a paymentType an amount and open the secure hosted checkout, where the card is entered on Merchant360's page, never in the extension.
Send to card terminalPushes the amount to your connected card terminal so the customer can pay in person. The result comes back into the extension.
Charge with Merchant360 (right-click menu)Takes a highlighted amount on any web page and opens the hosted checkout for that amount.

See the account the extension is connected to

The business name at the top of the extension shows which Merchant360 account it charges. Press the name to open the account screen. It shows the business name and legal name, Connected or not with the time of the last check, Live or Test mode, and the business email, phone and address.

The same screen lists the payment types on the account (Card Key-Entry, Card on file, Terminal with the number of paired terminals, ACH bank debit, eGiftSolutions, and the surcharge or dual pricing rate), your customer receipt settings (Email customers a receipt, Reply-to, BCC copy, Line items, Footer text) and the connected software, such as QuickBooks Online or ServiceTitan.

Check connection now loads the details again. Change settings in Merchant360 opens Billing tools, Settings in a new tab: the extension only shows the settings. Disconnect this browser is at the bottom of this screen.

On the main screen, ACH and eGiftSolutions show in grey with Not enabled on this account when your account does not have them. Ask your agent or EPI Merchant Support to add them.

Send to your card terminal

Card terminal in the extension sends the amount to a Merchant360 terminal. The terminal shows the name you gave it under Billing tools → Settings → Card readers (for example DOCTOR'S STATION 1 · EXAM ROOM 2); a terminal with no name shows its serial number.

With one terminal on the list, the extension sends the sale straight to it: no terminal to pick. With more than one, pick the terminal and press Send to terminal; your default terminal is preselected.

The list holds only the terminals that take sales from the PC. A terminal with Accept sales from the PC turned off is left out (a terminal in Integrated or POS Listener mode is always listed). With five terminals in the office and one at the front desk, ask Electronic Payments to leave Accept sales from the PC on for the desk terminal only; the extension then goes straight to it.

A person locked to one terminal on Account → Team (Merchant360 Terminal access) sees only that terminal in the extension they connected, and the sale goes straight to it.

Changes made in Merchant360 (terminal names, which terminals are listed, decline messages) reach the extension on their own. There is nothing to reinstall: close the extension panel and open it again, or press the business name at the top and then Check connection now.

If a card sale shows The processor rejected this before it reached the card issuer, the card was not declined: the sale never reached the bank. Try again in a few minutes. If it keeps happening, call Electronic Payments support at (800) 966-5520. Do not ask the customer for another card.

Pick the customer before you take the payment

Under the amount and description on the main screen there is a Customer box. Start typing a name, email or phone number and the list of your Merchant360 customers narrows as you type. Click a customer to pick them; the x in the box clears the choice.

The customer you pick is attached to the payment you take next: Terminal, Card Key-Entry, ACH or Card on file. This works for a customer with no card on file too. The payment shows on the customer's record under Customers, Payments, in your transaction reports and on the transaction itself.

With a customer picked, Card on file opens with a search for that customer's saved cards, and ACH Email customer to sign fills in their name and email.

The Customer box shows once the extension is connected with the customer lookup permission. If it does not show, press the business name at the top, press Disconnect this browser, then Connect with Merchant360 again.

Recent transactions

Today's transactions at the bottom of the main screen lists today's work: payments taken from the extension on this account today whose batch has not settled, newest first. Once the batch settles, or the next day, a payment leaves the list; refund and manage it in Merchant360, Transactions. It covers Card Key-Entry, Card on file, hosted checkout and terminal sales sent from the extension. Sales run on the terminal by themselves, in the Virtual terminal or elsewhere in Merchant360 are in Merchant360, Transactions.

A terminal sale shows once the terminal has an answer. A sale cancelled on the terminal before the card was charged is not listed. Click a row to see the payment and to void it before the batch closes.

An approved sale reads Approved. Bank (ACH) debits and gift card redemptions taken in the extension are listed too: a bank debit reads Submitted, In risk review (nothing is debited until EPI releases it), Settled, Returned or Declined. The payment's screen shows the Source: Terminal with the terminal's name and serial (for example Terminal · DOCTOR'S STATION 1 · EXAM ROOM 2 (2740236555)), Terminal (keyed), Key entered, Card on file, eGiftSolutions or ACH debit. Void shows for card and terminal sales; refunds, and bank and gift card payments, are handled in Merchant360.

Connect manually (API key)

The manual path is for merchants who prefer to control the key themselves, or who received a key directly from their account manager. The result is the same as the automatic path: the extension holds an API key scoped to opening hosted checkouts and reading their results.

The account owner creates the key under Developers & API in Merchant360. Create an API key, give it a name such as Payment Extension, choose Test or Live mode, and pick the Payments preset. Creating a key asks for a security code, texted or emailed the same way as the automatic path, or from your authenticator app. The key is shown once, so copy it right away.

In the extension, open Connect with an API key instead, paste the key into the box, and connect. The key is stored only in this browser, and card details are never entered in the extension. Every payment still happens on Merchant360's secure hosted page.

You are done when the extension shows the green connected confirmation. The key appears under Your keys on the Developers & API page with its last-used time, so you can see it working.

If the extension rejects the key, check that you copied the whole value and that the key was not revoked on the Developers & API page. A test key only takes test payments, so if real charges are not appearing, create a live key and connect again. To disconnect a browser, revoke its key on the Developers & API page; the extension will ask to connect again the next time it is opened.

  1. 1Signed in to Merchant360 as the account owner, open Accept Payments, then Developers & API in the Website & developers group.
  2. 2Under Create an API key, name it Payment Extension, choose Live (or Test to practice), and pick the Payments preset.
  3. 3Press Create key. Enter the security code (texted, emailed, or from your authenticator app).
  4. 4Copy the key right away. It is shown only once.
  5. 5In the extension, open Connect with an API key instead, paste the key, and press Connect.
The manual connection option with the API key field
Manual path – paste the API key you received from EPI and connect.
On this screenWhat it does
Connect with an API keyOpens the manual connect view in the extension with a single key field.
API key fieldTakes the key you copied from Developers & API. The value is kept only in this browser profile.
ConnectChecks the key against your account and, if valid, switches the extension to the connected view.
Developers & API: Create an API keyOwner only. Name, Mode (Test or Live), and Scopes. The Payments preset is enough for the extension. Asks for a security code and shows the key once.
Developers & API: RevokeDisables the key immediately. Any browser using it is disconnected and must connect again.

If the security code does not arrive

Connecting the extension and creating an API key both ask for a six-digit security code. The Security check box says where the code went. A text only reaches a mobile phone, so if the number shown is a landline or a business line, the code will not arrive there.

  1. 1In the Security check box, press Email me a code instead. A fresh code goes to the email address you sign in with.
  2. 2Open that email, type the six-digit code into the box, and press OK.
  3. 3If you set up an authenticator app under Account, Security, type the six-digit code from the app instead. A backup code (like K7QM-4TZP) also works.
  4. 4To have future codes texted to the right phone, open Account, Security and add your own mobile number for verification.