The platform
Five modules, specified plainly.
The modules behind every Fusion build, opened to the specification level: what each one does, what it produces, and where it connects. The composition differs per business; the parts do not.
composition varies · parts do not
Module 01
Payment pages & links
- reach:
- link · QR · statement · embed
- runs:
- hosted by Fusion, or embedded in the site
- records:
- payer + txn → your reporting · on capture
Get paid without a phone call.
Hosted or embedded pages a customer can reach from a site, a statement, a text message, or a QR code on the counter. Each page carries the business's name and branding, clears through the same processing account as everything else, and posts the payer and the transaction to your reporting the moment it captures.
Module 02
Donations & recurring giving
- modes:
- one-time · monthly · pledge
- option:
- donor-covers-fee, offered at checkout
- posts:
- gift → donor record · receipted
Turn intent into recurring support.
One-time and recurring giving for nonprofits, churches, and foundations: campaign pages, pledge schedules, and the option for a donor to cover the processing cost at checkout — offered, never imposed. Gifts post to the donor record receipted and whole.
Module 03
Ecommerce & cart
- stack:
- catalog · cart · checkout
- built:
- reusable components, adapted to the catalog
- chain:
- order → fulfillment → settle
Launch faster with less risk.
Catalog, cart, and checkout assembled from proven components and adapted to the catalog you actually sell — not rebuilt from zero, and not rented from a builder that owns your storefront. The payment event carries order context with it, so fulfillment and settlement stay chained.
Module 04
Invoicing & recurring billing
- flow:
- invoice → reminder → stored method
- send:
- text · email · link
- match:
- payment ↔ invoice · closed automatically
Collect in days, not weeks.
Invoice, balance, and scheduled billing workflows with stored payment methods where supported. The invoice link is the payment page: sent by text or email, paid without an account or a portal login, and matched back to the invoice automatically when it clears.
Module 05
Retail & in-person
- hardware:
- countertop · mobile · integrated
- arrives:
- configured — programs loaded, tested
- settles:
- batch → deposit · reconciled
One experience across every counter.
Countertop, mobile, and integrated terminals matched to the workflow and the volume — selected for the setting, configured before they ship, and supported by the same team that runs the rest of the stack. Batches settle to deposits that reconcile against the day.
* Module names are ours; the outcomes are yours. Which modules a build composes — and in what order — is decided in phase 02 and written into the build plan before it is priced.
Start here
Tell us how your organization needs to show up and get paid.
We map the practical path from the website to the transaction and the systems behind it.
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.
