Implementation
How a Factor4 gift card program gets built
This is the full implementation path, stage by stage: what happens, what we need from you, what we handle, and the mistake that most often costs a week. Most merchants run it in two to four weeks from first call to first card sold, and the four workstreams overlap rather than running strictly in sequence.
- 1Day 1
Scope the program
In the first conversation you decide what the program has to do: physical cards, digital, or both; single location or pooled across many; gift only or gift plus loyalty; and whether you are converting balances from an existing provider. These four answers determine pricing and timeline.
Bring your POS name and version, your location count, your rough monthly gift card volume if you have a program today, and any promotional mechanics you already run. If you are switching providers, bring a recent liability report — the outstanding balance figure is what gets converted. Nothing here requires a technical resource on your side.
Scoping is a conversation, not a questionnaire. The four answers that matter — card format, location structure, gift versus gift plus loyalty, and whether balances are being converted from another provider — determine both the quote and the calendar. Everything downstream inherits these decisions, so it is worth being honest about volume rather than optimistic.
What you provide
- POS platform and version, plus your reseller or gateway if one manages the account
- Location count and whether balances should pool across sites
- Rough monthly gift card volume today, if you already run a program
- A recent liability report if you are switching providers
What Factor4 handles
- Confirm the integration path for your specific setup
- Price the program against your actual configuration rather than a tier sheet
- Set a target launch date and work production and training dates back from it
Where this stage goes wrong. Scoping around the program you have rather than the one you want. Adding pooling or loyalty after launch is possible, but it is cheaper to decide now.
Stage output: An agreed program shape, a quote and a dated launch plan.
- 2Days 2–10
Connect your POS
Factor4 connects to your existing point of sale through one of 150+ certified integrations rather than replacing it. For most supported systems this is a configuration step handled between Factor4 and the POS vendor, not a hardware change or a new terminal on your counter.
The integration path depends on the platform. Clover and similar app-market systems install a merchant-facing app. Terminal-based setups on PAX, Verifone or Dejavoo receive a configuration through the gateway, often Datacap, BridgePay or TSYS. Enterprise systems such as Micros Simphony coordinate with the reseller. If your system is not on the list, the RewardOS™ API or the Virtual Terminal covers the gap.
Integration is where merchants expect pain and rarely get it, because Factor4 connects to the POS you already run instead of replacing it. The path varies by platform: an app install on app-market systems, a gateway configuration on terminal-based setups, or a coordination step with a reseller on enterprise systems. Where a platform is not supported, the API or the Virtual Terminal covers it.
What you provide
- Authorization for your POS or gateway account where the vendor requires it
- A terminal available for a short test window outside peak hours
- Contact details for your POS reseller if applicable
What Factor4 handles
- Configure the integration and liaise with the POS vendor or gateway
- Provision test cards and validate activation, redemption, partial redemption and balance inquiry
- Confirm exactly what the register workflow looks like for your staff
Where this stage goes wrong. Scheduling a cutover on the promise of an integration nobody has watched work on a live terminal. Test first, then set the date.
Stage output: A verified integration on the terminals you actually use.
- 3Days 3–15
Design and produce cards
Choose from roughly 70 stock designs to launch in days, or submit custom artwork for in-house production on 30mil PVC. Custom runs need artwork approval and a production window, so brands targeting the November–December window should start design in late summer.
Alongside the card itself, decide on carriers, envelopes and counter display. The carrier is functional real estate: print the balance-check URL, the terms and a reload prompt on it. Digital-only programs skip this stage entirely and can be live in under a week, which is why many merchants launch digital first and add plastic on the next reorder cycle.
Card production is the stage with a physical deadline attached, which makes it the usual cause of a slipped launch. Stock designs move fast. Custom artwork adds a proof cycle and a production window, and production does not begin until a proof is approved in writing. Digital-only programs skip this stage entirely.
What you provide
- Print-ready artwork, or your selection from roughly 70 stock designs
- Logo, brand colors, printed terms, balance-check URL and support number
- Written approval on the digital proof
- Quantities for cards, carriers, envelopes and counter display
What Factor4 handles
- Supply templates and the stock design library
- Proof, produce and encode cards in-house on 30mil PVC
- Ship cards, carriers and display to your locations
Where this stage goes wrong. Treating the carrier as packaging. It is functional real estate: the balance-check URL, the terms and a reload prompt all belong on it.
Stage output: Cards, carriers and display in hand before your first selling weekend.
- 4Days 10–18
Configure rules and promotions
Before launch you set the program rules: denominations, reload limits, whether promotional value expires separately from purchased value, loyalty accrual rates, receipt messaging and which staff roles can void or adjust a balance. These are configuration settings, not development work.
This is also where compliance decisions get recorded. Federal law under the CARD Act protects purchased funds for at least five years and restricts inactivity fees; several states go further. Set your terms once, print them on the carrier and mirror them in the platform so what the customer reads matches what the system enforces. Load your first bonus promotion here if you are launching into a holiday.
Configuration records how your program behaves and what your customers were told. Denominations, reload limits, loyalty accrual, receipt messaging and staff permissions are all settings. So are the compliance decisions: keep purchased value permanent and fee-free, and let only promotional value carry a date.
What you provide
- Denomination list and any reload minimum or maximum
- Loyalty earn rate, redemption threshold and exclusions, if running loyalty
- Which staff roles may void or adjust a balance, and who holds admin access
- The terms you are printing, so the platform and the card agree
What Factor4 handles
- Configure rules, permissions and reporting access
- Separate promotional value from purchased value in the ledger
- Load your first bonus promotion if you are launching into a holiday
Where this stage goes wrong. Mixing bonus value into the same bucket as purchased value. It either gives away more than you intended or creates a compliance problem.
Stage output: A configured program whose printed terms match what the register enforces.
- 5Days 15–21
Train staff and go live
Staff training is short because the workflow lives inside the POS they already use: activate at sale, swipe or scan at redemption, check a balance on request. Factor4 provides live onboarding, and support runs seven days a week for the questions that surface in the first busy weekend.
The two things worth rehearsing are partial redemption — the balance stays on the card, the customer pays the difference — and the balance inquiry, because that is the most common customer question. Put a counter display up before your first weekend; a program with no visible cards sells almost nothing regardless of how well it is configured.
Training is short and specific. Staff already know the POS; what they need is three workflows and one script. Rehearse partial redemption and the balance inquiry, put the display up before the weekend, and know who to call. Support runs seven days a week precisely because the questions arrive on a Saturday.
What you provide
- A 20–30 minute window with managers and admins
- A shift huddle to walk the counter script
- Counter space for the display before your first weekend
What Factor4 handles
- Run live onboarding for managers
- Provide the register one-pager and balance-inquiry script
- Stay reachable through your first busy weekend
Where this stage goes wrong. A live program with no visible cards. A configured program with an empty counter sells almost nothing.
Stage output: Staff who can activate, redeem and answer a balance question without calling a manager.
Start with your POS
The fastest way to get an accurate timeline is to tell us what you run at the register. Check the integration directory, or send your details and we will confirm the path for your exact setup.