Skip to main content

Taking a Payment on the Website

Taking a Payment on the Website

Your CloudFFL website lets customers browse your inventory, add items to their cart, and pay online — just like any other online store. Card payments on the website are handled securely by your payment processor (NMI or Authorize.net), so you don't have to worry about card data touching your server.

How Website Payments Work

When a customer checks out on your website, they see a secure card entry form embedded right in the checkout page. The form looks like part of your site, but behind the scenes the card details go straight to your payment processor. This keeps everything PCI-compliant and safe.

NMI Website Payments

  • Uses the Collect.js inline form at checkout — the same secure technology used in the back office.
  • Customer enters their card number, expiration date, and CVV directly on your checkout page.
  • Supports saved cards — returning customers can save their card for faster checkout next time. The card is stored as a secure token, not as an actual card number.

Authorize.net Website Payments

  • Uses the Accept.js inline form at checkout — same secure, embedded experience.
  • Customer enters their card details on your checkout page just like with NMI.
  • Also supports saved cards with secure tokenization.
  • ACH / eCheck option (if enabled): customers can pay directly from their bank account by entering their bank routing number and account number. This is especially useful for large orders.

ACH/eCheck payments are only available with Authorize.net. They're a great option for large orders — like a bulk ammunition purchase or a high-value firearm — where the customer wants to pay from their bank account instead of a credit card.

What Your Customer Sees (Step by Step)

Here's what the checkout experience looks like from your customer's perspective:

  1. The customer browses your website and adds items to their cart — for example, a Glock 19 and two boxes of 9mm ammunition.
  2. They click Proceed to Checkout.
  3. They fill in their shipping and billing information (or log in to their account if they already have one).
  4. In the Payment section, they choose their payment method:
    • Credit Card — to pay by Visa, Mastercard, etc.
    • eCheck / ACH — to pay from a bank account (Authorize.net only, if enabled)
  5. They enter their card details (or bank details for eCheck) in the secure form.
  6. They click Pay Now.
  7. The payment is processed immediately. If approved, the order is confirmed and the customer sees an order confirmation page. You'll also see the new order in your CloudFFL back office under Sales → Orders.

Saved cards are safe. When a customer saves their card for future purchases, the actual card number is never stored in your system. Instead, your payment processor stores it and gives CloudFFL a secure token — a random reference code that only the processor can use. This is completely PCI-compliant.

What You See in the Back Office

When a customer pays on the website, everything flows into CloudFFL automatically:

  • A Sales Order is created with all the items the customer purchased.
  • An Invoice is generated and already marked as Paid.
  • The Payment is recorded and linked to the invoice, showing the processor used (NMI or Authorize.net) and the transaction reference number.
  • If the order includes items that need to ship, a Delivery Order is created so your warehouse knows to pick and pack.

You don't need to do anything to process the payment — it's all handled at checkout. Just fulfill the order as you normally would.

Check your Sales → Orders screen regularly for new web orders, or set up email notifications so you know the moment a new order comes in.

No comments to display

Back to top