Skip to content
Fusion Payments

Fusion Payments — Operating Record

Figures as reported*

Ten years. Two hundred merchants. One accountable team.

01
10 years
Serving merchants nationwide
02
20 years
Combined payments experience
03
200+
Merchants supported
04
Millions monthly
Processed securely
05
FL based
Winter Garden, Florida. Veteran-owned.

* Current operating figures for the merchant-services practice. Updated as the record changes — not rounded up for a landing page.

From the invoice to the deposit

From the sale to the deposit — and everything it has to touch.

LIVE TRACE txn_01J9ZKQM4E7R $184.00 · VISA ·· 4242 · card_present: false*
  1. T+0.00 s

    01 Customer

    Gets the invoice by text or email, or hands over a card at the counter.

  2. T+0.04 s

    02 Pay

    Opens it on their phone and pays by card or bank. Or taps at the terminal. No account to create.

  3. T+41.20 s

    03 Tokenized capture

    Card data is captured in provider-hosted fields and tokenized. It never lands in your systems.

  4. T+42.61 s

    04 Processing

    Authorized, captured, and settled through supported payment infrastructure.

  5. T+42.90 s

    05 Your books

    Recorded and reconciled into QuickBooks Online, your CRM, or whatever your team actually runs.

Most companies own one piece of this. Fusion owns the path.

Typically — invoicing app · gateway · processor · nobody

Fusion — one team, all five stages

* Elapsed: 42.90 s. About 41 s of that is the cardholder deciding. Every hop Fusion owns runs in milliseconds.

Fusion Payments — How it is controlled

Concrete controls, not absolute claims.

“Secure” is an adjective. A control is something you can point at, test, and hold us to. These four are structural — they hold whether or not anyone is watching.

Register
FP-SEC-4
Revision
2026-08
Review cycle
Quarterly
Applies to
Every build shipped

The build standard behind this register runs a good deal longer than this page. Ask, and we will walk you through it.

ID Control Status
  1. CTRL-01

    Tokenized capture

    Enforced

    Card data is captured through provider-hosted or tokenized fields. Nothing here stores a raw card number.

    verify: zero card-number fields in our DOM — capture lives inside provider-hosted iframes · stage 03 · payment experience

  2. CTRL-02

    Separated zones

    Structural

    The public site, the invoicing app, and the payment pages are technically separated, not just visually.

    verify: separate origins, separate deploys — a compromise of the public site has no path to a checkout · stages 02–03 · pay + capture

  3. CTRL-03

    Registered and sponsored

    Registered

    Generosity LLC, dba Fusion Payments, is a registered Independent Sales Organization of Wells Fargo Bank, N.A., Concord, CA.

    verify: the sponsor bank is named in the footer of every page, in the form the card brands require · stage 04 · processing

  4. CTRL-04

    Verified before pay

    Enforced

    An invoice asks the payer for a six-digit verification code before the pay page opens.

    verify: a six-digit code, checked before the pay page opens — a forwarded link alone pays nothing · stage 02 · pay

Stage numbers refer to the connected system above

Fusion Commerce — Platform

One configurable platform for the ways your organization gets paid.

Start with proven components. Configure the workflow. Extend it when the business needs more.

  1. Module 01

    Payment pages & links

    Get paid without a phone call.

    Hosted or embedded pages a customer can reach from a site, statement, message, or QR code.

    reach: link · qr · statement · embed

  2. Module 02

    Donations & recurring giving

    Turn intent into recurring support.

    One-time and recurring giving experiences for nonprofits and foundations.

    modes: one-time · monthly · pledge

  3. Module 03

    Ecommerce & cart

    Launch faster with less risk.

    Catalog, cart, and checkout built from reusable components and adapted to the catalog.

    stack: catalog · cart · checkout

  4. Module 04

    Invoicing & recurring billing

    Collect in days, not weeks.

    Invoice, balance, and scheduled billing workflows with stored payment methods where supported.

    flow: invoice → reminder → stored method

    See Invoicing by Fusion Payments
  5. Module 05

    Retail & in-person

    One experience across every counter.

    Countertop, mobile, and integrated terminals matched to the workflow and the volume.

    hardware: countertop · mobile · integrated

Modern payment terminal accepting a card tap
In-person · hardware card_present: true

When the payment happens in person, the hardware is part of the design.

Countertop, mobile, or integrated into the counter workflow — selected for the volume and the setting, configured before it ships, and supported by the same team that built the site it stands next to.

See Fusion Commerce

How Fusion works

Four steps, one accountable team.

Every phase ends in an artifact you sign. Nothing advances on a status call, and nothing is rebuilt later because nothing moves forward unfinished.

  1. Phase 01 · WK 00–02

    Discover

    Map the customer, patient, payment, and operational journey as it exists today.

    on the table: processing statements · quote-to-cash · the site as it stands

    Gate 01 → 02 · admits: the journey map — one page, signed by both sides · nothing else

  2. Phase 02 · WK 02–04

    Design

    Select the processing, invoicing, hardware, and integration path that fits.

    decided here: modules · hardware · integration path — priced, in writing

    Gate 02 → 03 · admits: the build plan — scoped, priced, approved · nothing else

  3. Phase 03 · WK 04–08

    Deploy

    Board, configure, train, and launch — with a person on the phone the whole way.

    discipline: tagged → staged → live · rollback rehearsed — CTRL-03

    Gate 03 → 04 · admits: the live system — verified against the plan · nothing else

  4. Phase 04 · WK 08 →

    Improve

    Support the system and add durable enhancements as the organization changes.

    exit criterion: none — this phase does not close

04 feeds 01 · when the business changes — new location, new system, new way of getting paid — discovery re-opens. The team it re-opens with does not change.

* Weeks shown are typical for a standard build; integrations widen the windows, never the order. Three gates, three signatures — the only phase without an exit criterion is the last one. That is what accountable means on a timeline.

Fusion Payments — Customer Record

Source: Google · Reproduced verbatim*

7 reviews on the record. Published whole. Edited never.

Named customers, real workflows, and the people who answer the phone when something changes.

5.0

7 reviews · Google

5
7
4
0
3
0
2
0
1
0

sample: complete · 7/7 five-star · edits: none

Entry 01

“Fusion Payments were honest about the industry rates and helped me secure a great rate for my restaurant with no hidden fees. Integration was too easy and seamless.”

Luis Salazar Restaurant Owner

Entry 02

“Starting a business can be hard enough, but the transition over to Fusion Payments has made business handling so smooth. Larry has been a great help and has been so transparent over the years. It's been a pleasure working with them.”

Ashley Morton Founder

Entry 03

“We recently converted our POS and credit card processing over to Fusion Payments. The setup and process was extremely easy. Communication and response time was very fast!! I would recommend any of their services.”

Daniel Leonetti Business Owner

Entry 04

“I've had the opportunity to work with Larry and Fusion Payments and the experience has been great for my small business. Providing a simple mobile solution that allows me to make changes on the go and provide a great experience for my customers.”

Albert Dukes Business Owner

Entry 05

“These people are on top of their game. They are technically savvy. In our case it was accomplished quickly and we are up and running. Thanks!”

Dave Joswick Executive Director

Entry 06

“These guys have done a great job taking care of our payments the past few years!”

Jose Lightner CEO

Entry 07

“Great customer service, quick response and if the answer is not known then questions are asked to get to the bottom of the issue. We have been pleased with the service received.”

Charles Roper Business Owner

* Every review on record at time of publication, reproduced in full from Google — phrasing, ratings, and roles as posted. Uncompensated, unedited, nothing withheld. / end of record

Fusion Payments — Advanced integrations

When payments have to work with everything else.

Connect payments to CRMs, practice and business systems, accounting workflows, ecommerce operations, and software products — with one team accountable for the result.

Discuss an integration

INT-01

CRM & practice systems

Push transactions and customer records where your team already works.

push: txn + payer → the record your team works in · on capture

INT-02

Accounting & reconciliation

Custom transaction and reconciliation workflows that survive month-end.

match: transaction ↔ deposit · at settlement · survives month-end

INT-03

Ecommerce operations

Catalog, order, and fulfillment connections around the payment event.

chain: order → fulfillment → settle · event-driven

INT-04

ISV & embedded payments

Payment capability inside someone else's software, with the onboarding path to match.

embed: payments inside your product · sub-merchant onboarding included

Every interface above is specified in the build plan — phase 02, before it is priced

Fusion Payments — The other practice

Your website, handled.

Fusion Payments builds and hosts the sites its payment stacks run behind — one vendor, one accountable team, from the first visit to the deposit. If yours is due for a rebuild anyway, ask about the website program.

See the web practice

terms: asked for, not posted — priced alongside your statement reading

Start here

Tell us how your business gets paid today.

We map the practical path from the invoice or the sale to the deposit, and the systems it has to reach.

call: (407) 395-2832 · a person answers, not a queue

write: info@fusionpayments.com · read by the people who build

* The first conversation is a reading, not a pitch — bring last month's processing statement and leave with every line on it explained. No fee, no obligation.