Connect a payment provider to accept credit card payments from customers. FirearmCart supports firearm-friendly payment processors, and you don’t have to get your merchant account through us: connect the one you already have, or apply with Elite 2A Pay if you need one.
Why Firearm-Friendly Processors?
Standard processors like PayPal and Stripe prohibit firearm sales. Using them can result in:
- Account termination without warning
- Funds held for months
- Chargebacks and disputes
Our supported processors specialize in the firearm industry and won’t shut down your account.
Supported Providers
The Payments page is split into two sections: Card gateways and Buy now, pay later.
Card Gateways
| Provider | Credentials required |
|---|---|
| Fortis | User ID, User API Key, Location ID |
| Authorize.net | Login ID, Transaction Key, Environment (sandbox or production) |
| NMI Gateway | API Security Key, and an optional Processor ID |
| Converge (Elavon) | Converge Account ID, API User ID, PIN, Environment (sandbox or production) |
| Sandbox (Testing) | Default behavior for unknown cards (approve or decline) — no real charges |
Buy Now, Pay Later
| Provider | Credentials required |
|---|---|
| Sezzle | Public Key, Private Key, Environment, and an optional Webhook Signing Key |
| Credova | API Username, API Password, Store Code, Environment |
Only one card gateway can be active at a time, and only one BNPL provider — but a card gateway and a BNPL provider can both be active together.
Adding a Payment Provider
Step 1: Get Your Credentials
You can use a merchant account you already have with any supported provider, including one set up through another company, such as your current website provider: see Using Your Existing Merchant Account. If you don’t have an account yet, open one with a supported provider, or apply with Elite 2A Pay from FirearmCart.
Step 2: Add the Provider
- Go to Settings > Payments
- Click Add gateway under Card gateways (or Add provider under Buy now, pay later)
- Select your provider
- Enter an Account Name and your API credentials
- Click Add Provider
The first provider you add in a section is activated automatically.
Step 3: Configure Settings
Click Manage on a card gateway to configure:
- Monthly Limit - An optional cap on the account
- Accepted Cards - Which card logos are shown at checkout
- Credit card surcharge - An optional percentage, up to 3%, added to credit-card checkouts. Debit and prepaid cards are not surcharged. Fortis accounts mirror the surcharge configured at Fortis and do not accept a rate typed here. On Converge, Elavon enables the surcharge on your terminal and the rate you enter here only tells checkout what to show.
Step 4: Activate
Open the provider’s action menu and click Activate. Activating a provider deactivates any other provider in the same section.
Using Your Existing Merchant Account
FirearmCart doesn’t require you to get a merchant account through us. If you already accept cards with a supported provider, connect that account, including one another company set up for you, such as the company that runs your current website. You don’t need a new merchant account, MID or gateway.
Many processors give their merchants an NMI or Authorize.net gateway. If your processor isn’t listed under Supported Providers, ask whether your account can use one of those gateways. If it can, connect it with that gateway’s credentials.
- Get API credentials for your account from your provider, or from whoever set the account up (see the table below)
- Go to Settings > Payments and click Add gateway (or Add provider for Sezzle and Credova)
- Select your provider, enter an Account Name and the credentials, and click Add Provider
- For Fortis, Authorize.net, NMI and Converge, open the gateway’s ⋯ menu and click Test connection
Where to Find Your Credentials
| Provider | Credentials |
|---|---|
| Fortis | Fortis, or whoever set up your account, creates a user with API access for FirearmCart and gives you its User ID and User API Key, plus your Location ID. Each is a 24-character ID. |
| Authorize.net | Your API Login ID and Transaction Key, from API Credentials & Keys in the Authorize.net Merchant Interface. A new Transaction Key replaces the old one, so if another website already uses this account, get the current key from whoever runs that site instead of creating one. |
| NMI Gateway | A private API Security Key, created under Security Keys in your gateway’s merchant portal. Your processor may brand the portal with its own name. |
| Converge (Elavon) | Your 6–7 digit Converge Account ID (not the 10-digit Elavon merchant ID), the API User ID of a dedicated user on your eCommerce terminal, and that user’s PIN from Employees → the user → Show PIN in Converge. See Connecting a Converge Account. |
| Sezzle | Your public and private API keys, from your Sezzle merchant dashboard |
| Credova | Your API username, password and store code, from Credova |
Your processor still sets your rates and pays out your deposits, as it does now, and another website that uses the same account keeps working alongside your store. FirearmCart’s own transaction fee is billed separately, on your FirearmCart invoice (see Billing).
Connecting an Existing Fortis Account
FirearmCart adds its own Fortis developer ID to every request, so you don’t need one. Your Fortis location needs an active credit card product for online payments; if your account was only set up for in-person payments, ask Fortis to add one.
Test connection checks the User ID and User API Key. If Could not read surcharge settings from Fortis appears when you save, check the Location ID.
Connecting a Converge Account
Converge is Elavon’s gateway. FirearmCart sends card details to Converge’s XML API from a fixed set of server addresses, so Converge has to know those addresses and the user it should accept them from.
- In Converge, go to Employees and create a dedicated API user on your eCommerce terminal. Don’t use the Merchant Admin login.
- Open that user and click Show PIN. The PIN is what FirearmCart signs every request with.
- Go to Settings → Fraud Prevention Rules → API IP Address Allowed List and add FirearmCart’s addresses. They are shown in the Add gateway window and on the gateway’s Manage window. Converge rejects requests from any other address.
- In FirearmCart, add the gateway with your Converge Account ID, the API User ID, the PIN, and an Environment: Sandbox for a demo account Elavon issued you, Production for your live account. Elavon issues demo accounts on request; there is no self-serve sandbox.
- Open the gateway’s ⋯ menu and click Test connection.
FirearmCart stores the card and charges it directly, so Converge’s tokenization and Card Manager are not used. Subscription renewals through Reload are sent to Converge as merchant-initiated charges with the reference data from the first sale.
A void only works before the day’s batch settles on your terminal. Once a sale has settled, the void fails with a note to refund the order instead.
Applying with Elite 2A Pay
If you don’t have a merchant account yet, apply with Elite 2A Pay, a firearm-friendly credit card processor that partners with FirearmCart. The Accept cards with Elite 2A Pay card on the Payments page links to its application.
- Go to Settings > Payments
- Click Apply with Elite 2A Pay
- Fill out the application, which opens in a new tab
The last step of store setup, Set up payments, offers the same application. Apply with Elite 2A Pay opens it in a new tab and finishes setup; Skip for now finishes setup without it, and you can apply later from Settings > Payments.
Elite 2A Pay reviews your application and follows up with you. Once you’re approved, add your account under Card gateways as described in Adding a Payment Provider.
Pending Fortis Applications
A Fortis application you started from FirearmCart shows under Card gateways as a Fortis gateway marked Pending. Click Continue application on it to reopen the application. A pending gateway can’t be activated.
When Fortis approves the application, FirearmCart fills in the credentials and activates the gateway, replacing any other active card gateway. There is nothing to copy. If Fortis sends you credentials before that, click Manage on the pending gateway and enter them. The gateway is then marked Approved, and it becomes active if no other card gateway is.
Managing Providers
Viewing Your Providers
Go to Settings > Payments to see all connected payment providers.
Editing a Provider
- Click Manage on the provider
- Update credentials, the monthly limit, accepted cards, or the credit card surcharge
- Click Save Changes
Credit card surcharging
A credit card surcharge is a percentage added only when the customer pays by credit card. Debit, prepaid, and unrecognized cards are not surcharged. The rate cannot exceed 3%.
Register the surcharge with your processor and acquirer at least 30 days before you turn it on.
Connecticut, Massachusetts, Maine, and Puerto Rico ban credit card surcharges. FirearmCart never adds one when the billing address is in one of them, on any gateway, and Settings > Payments warns you if your store’s own address is there. Other states allow surcharges with limits: Colorado and Oklahoma cap them at 2%, and New York, New Jersey, and several others cap them at what you actually pay to accept cards. Pick a rate that fits your state, and confirm its current rule.
- Fortis — turn surcharging on with Fortis first. Save the account or click Test connection and FirearmCart copies the rate. The switch is read-only. If Fortis uses a flat fee, a minimum fee, or a separate surcharge transaction, FirearmCart leaves the switch off and charges without a surcharge.
- NMI — confirm your processor actually passes the surcharge field through. NMI does not calculate the fee.
- Authorize.net — the surcharge field is documented for TSYS merchants.
- Converge (Elavon) — ask Elavon to enable surcharging on your Converge terminal; Converge then adds the fee to every credit card sale itself. Turn the switch on in FirearmCart and enter the same percentage so checkout shows the fee. Before each charge, FirearmCart asks Converge what it will add for that card and never charges more than the total the customer saw. Orders record the fee Converge actually charged: if the switch is on but your terminal doesn’t surcharge, the order is saved without a fee, and if your terminal surcharges while the switch is off, FirearmCart turns the switch on at Converge’s rate. Test connection warns you when the switch and your terminal disagree. Elavon’s program decides where the fee applies, so FirearmCart’s state list does not apply to Converge.
NMI and Authorize.net add the surcharge only at storefront checkout. Fortis also surcharges orders you create in the admin, orders charged through the API, and subscription renewals when Fortis applies the surcharge to recurring payments. Converge surcharges every credit card sale the terminal runs, including subscription renewals. Post-purchase upsells and the $1 card check are never surcharged by FirearmCart, though a Converge terminal may still add its fee to them.
At checkout the order summary shows “Credit card surcharge (rate%)”, and a short disclosure appears under the card fields. The fee is not taxed, it is not charged on Sezzle or Credova, and a refund returns a proportional share of it. Ad-platform order values use the order total, so they include the surcharge.
Testing a Connection
Fortis, Authorize.net, NMI, and Converge expose a Test connection action in the provider’s menu. It validates the stored credentials against the gateway without moving money and reports the result as a toast. Sandbox and BNPL providers do not offer this action.
The test also checks two settings at the gateway:
- Authorize.net — if the account is in Test Mode, the test passes with a warning to turn Test Mode off
- NMI — the test fails if NMI refuses the Processor ID you entered
The AI assistant can run the same test for you and list your recent failed payments with the gateway’s reason for each.
Activating/Deactivating
- Active - Provider is used for checkout
- Inactive - Provider is not available at checkout
Deleting a Provider
- Open the provider’s action menu
- Click Delete
- Confirm deletion
Note: You cannot delete a provider that has any associated transactions. The Delete action is disabled in that case. Deleting a pending Fortis gateway only removes it from this page: if Fortis approves the application later, the gateway comes back connected.
Accepted Card Types
Choose which card logos are displayed at checkout:
- Visa
- Mastercard
- American Express
- Discover
- JCB
- Diners Club
Note: This setting controls which card logos customers see. It does not block a card brand from being submitted — your gateway decides what it will accept.
Sandbox Testing
The Sandbox (Testing) provider lets you test checkout end-to-end without processing real payments. Add it the same way as a live gateway (Settings > Payments > Add gateway > Sandbox (Testing)), choose whether unknown cards approve or decline, then use the card numbers below at checkout.
Use any future expiration date and any 3–4 digit CVV.
Only accept US-issued cards and Block prepaid cards under Settings > Checkout don’t apply while Sandbox is your active gateway, so these cards work with them on.
Approved Cards
These cards always succeed.
| Brand | Number |
|---|---|
| Visa | 4111 1111 1111 1111 |
| Mastercard | 5555 5555 5555 4444 |
| American Express | 3782 822463 10005 |
| Discover | 6011 1111 1111 1117 |
| JCB | 3530 1113 3330 0000 |
| Diners Club | 3056 9309 0259 04 |
Decline Cards
Each card simulates a specific decline reason returned by real processors.
| Number | Decline Reason |
|---|---|
4000 0000 0000 0002 |
Insufficient funds |
5100 0000 0000 0511 |
Insufficient funds (Mastercard) |
4000 0000 0000 0028 |
Lost card |
4000 0000 0000 0036 |
Stolen card |
4000 0000 0000 0069 |
Expired card |
4000 0000 0000 0127 |
Invalid CVV |
4000 0000 0000 0101 |
Do not honor |
4000 0000 0000 0119 |
Invalid card number |
4000 0000 0000 0259 |
Exceeds withdrawal amount limit |
4000 0000 0000 0333 |
Suspected fraud |
4000 0000 0000 0341 |
Restricted card |
4000 0000 0000 0358 |
Transaction not permitted |
4000 0000 0000 0366 |
Invalid expiration date |
4000 0000 0000 0374 |
Issuer or switch inoperative |
4000 0000 0000 0408 |
Activity limit exceeded |
4000 0000 0000 0416 |
AVS failure |
Gateway Error Cards
These simulate gateway-level failures (network, timeout, etc.) rather than card declines.
| Number | Scenario |
|---|---|
4000 0000 0000 9995 |
Gateway timeout |
4000 0000 0000 9996 |
Network error |
4000 0000 0000 9997 |
Configuration error |
4000 0000 0000 9998 |
Processing error |
4000 0000 0000 9999 |
General error |
3D Secure Cards
| Number | Behavior |
|---|---|
4000 0000 0000 3220 |
Authentication required |
4000 0000 0000 3238 |
Authentication successful |
4000 0000 0000 3246 |
Authentication failed |
4000 0000 0000 3253 |
Attempts processing |
Note: The Sandbox provider is for testing only. Activate your live gateway before going live so real customers can’t be routed to it. (Activating another card gateway automatically deactivates Sandbox.)
Troubleshooting
Payments Failing
- Verify API credentials are correct — use Test connection on Fortis, Authorize.net, NMI, and Converge
- Open a failed order and check the payment’s message in the Transactions section: it is the gateway’s own reason
- Check your provider dashboard for errors
- Ensure your provider account is in good standing
- Converge: a message about the API IP Allowed List means FirearmCart’s addresses are missing from Settings → Fraud Prevention Rules in Converge; add the addresses shown in the gateway’s Manage window
Payment Approved While Authorize.net Was in Test Mode
A payment that shows It appears this payment was successful, but your Authorize.net gateway was in Test Mode was approved while your Authorize.net account was in Test Mode. Look for the payment in your Authorize.net account before you fulfill the order. To take live payments, go to Account > Settings > Test Mode in Authorize.net and turn Test Mode off. Test connection warns you while Test Mode is on.
“Invalid processor” from NMI
NMI has no processor it can use for your payments. If you entered a Processor ID for the gateway, check that it matches one in your NMI account, or clear the field to use your account’s default processor. If the field is empty, ask NMI or your merchant services provider to finish setting up the processor on your account.
No Card Form at Checkout
- Make sure exactly one card gateway is marked Active
Credentials Rejected
- Double-check for typos
- Verify you’re using live credentials, and that the Environment field is set to
production(Authorize.net, Converge, Sezzle, Credova) - Converge: the API user must be a dedicated user on your eCommerce terminal, not the Merchant Admin login, and the PIN is the one Converge shows for that user
- Make sure your provider account is fully activated
Related Documentation
- Checkout Settings - Configure checkout options
- Billing - Your FirearmCart subscription
- Getting Started - Complete setup guide

