How to Hire a Gift Card and Stored Value Platform Development Company
Make every candidate describe authorisation failure cases before you discuss price: connection lost after the hold, refund to a card since merged into a wallet, split tender on a taxed total. No two-phase hold and capture means no shortlist.
On this page
Make every candidate describe authorisation failure cases before you discuss price: connection lost after the hold, refund to a card since merged into a wallet, split tender on a taxed total. No two-phase hold and capture means no shortlist. Expect $70,000 to $150,000 for a first release over 12 to 18 weeks, and $180,000 to $450,000 for a full platform.
A gift card programme is the only marketing initiative that eventually ends up in front of an unclaimed property examiner. Hiring someone to build one is closer to hiring a custodian for a vault whose keys are printed on cardboard and hung by the door of every supermarket that agreed to carry your rack. The money is real, it is other people's, and most of the controls around it are made of paper and goodwill.
The reason this is hard to buy is that three departments each own a third of the problem and none of them owns the object in the middle. Marketing owns the programme and cares about activation and promotion. Operations owns till behaviour and cares about the queue. Finance owns the liability, the breakage policy and the state-by-state remittance question, and finds out about design decisions during the first audit. Every vendor sells convincingly to one of those three. What you actually need is a single ledger where a card, its funding event, every authorisation attempt, every redemption, every fee and its dormancy state live together, and nobody in the building thinks to ask for a ledger.
What a stored value platform company actually does
The card lookup is trivial. The build is everything around it. Authorisation has to be a hold then a capture rather than a single deduct, so a dropped connection between a till and the platform never leaves the balance ambiguous and a store manager guessing in the customer's favour. There has to be a written offline policy, chosen deliberately, with a floor limit configurable per channel and per store rather than an accident discovered during an outage.
Then jurisdiction, which has to be recorded at creation rather than reconstructed later: issuing entity, issuing location, funding source and a dormancy clock per jurisdiction on every card. Then fraud instrumentation across the whole lifecycle, because draining begins before activation when numbers are lifted from a rack and the packaging restored, which means balance enquiry patterns and the interval between activation and first redemption carry more signal than redemption velocity ever will. Then distributor activation files in per-partner formats, franchise redemption producing inter-entity settlement entries automatically, and bulk corporate issuance so that nobody is hand-processing four thousand named cards in December.
What it really costs in 2026
These bands assume you keep your distribution partners and build the ledger and control layer yourself.
| Scope | Cost | Timeline |
|---|---|---|
| Balance ledger and liability reporting alongside an existing processor | $40,000 to $75,000 | 6 to 10 weeks |
| First release: ledger, real-time till and online authorisation, activation, reload, refunds, liability by entity | $70,000 to $150,000 | 12 to 18 weeks |
| Full platform: distributor feeds, dormancy and escheat by jurisdiction, fraud engine, franchise settlement, bulk issuance | $180,000 to $450,000 | 6 to 12 months |
| Support, rule changes and additional till estates | 18 to 22 percent of build per year | Retainer |
Two line items go missing. The first is the parallel period during balance migration. Those cards are already in customers' wallets and cannot be reissued, so the old processor stays reachable while lookups check the new ledger and fall back, with a daily reconciliation, for two to four weeks. That is genuine project cost in engineering and in finance hours, and treating it as overhead is how a migration turns into a customer service incident at the service desk.
The second is the second till estate. A group running two or three point of sale (POS) systems is doing the integration two or three times, and older estates usually need a middleware shim with its own offline behaviour and its own test matrix. Have the second estate priced on its own line. And ask directly about card scope, because gift card numbers are not cardholder data in the sense the payment card standard regulates, and buyers routinely accept compliance work in a quote they did not need. Treat the number as a bearer instrument and design access controls accordingly, which is cheaper and more relevant than a scope you do not have.
Signals of a strong partner
What tells you a firm has built financial infrastructure rather than a loyalty feature.
- Authorisation is described as hold then capture, unprompted. Along with what happens when the line drops between the two.
- Offline behaviour is a policy with a number attached. Decline or authorise to a floor limit, chosen deliberately and configurable per channel.
- Jurisdiction is captured at creation. Issuing entity, issuing location and dormancy clock on the card, never derived from sales data afterwards.
- They raise pre-activation fraud. Balance enquiry rate limiting and enumeration detection, not just redemption velocity rules.
- Fraud thresholds are editable by your risk lead. With an audit trail, because the pattern shifts every holiday season.
- They name the till systems they have integrated, with versions. Offline behaviour differs sharply between them and experience does not transfer cleanly.
- Breakage recognition produces journal entries. Against a documented policy your auditor has seen, not a memo at quarter end.
Red flags
- A single deduct authorisation model. You will discover the gap at Christmas, at a service desk, with a queue.
- Jurisdiction reconstructed from sales history. That is your next audit finding, described to you in advance and charged for.
- Fraud rules hard-coded by developers. Every threshold change becomes a release, and draining patterns change faster than your release cycle.
- A hard cutover on balance migration. Any plan without a parallel period and a daily reconciliation is a plan to strand live customer balances.
- Payment card compliance work bundled in without explanation. Ask precisely which scope applies and why, because a stored value ledger does not pull you into card scope on its own.
Questions to ask on the first call
- The connection drops after the hold and before the capture. What does the customer experience and what does the ledger hold?
- What is your recommended offline policy at the till, and what floor limit would you set for a franchise store?
- How does a card record where it was sold, by which entity, on the day it was sold?
- How would you detect a rack of cards being drained within minutes of activation in a different channel?
- Who can change a fraud threshold, and what is recorded when they do?
- Which point of sale systems have you integrated, and how did their offline behaviour differ?
- How does a franchise redemption become a settlement entry the franchisee can dispute line by line?
- Walk me through migrating live balances without reissuing a single card.
- Who owns the ledger, the database and the cloud accounts, and what does an export look like?
A simple way to decide
Rather than comparing proposals, buy a paid discovery phase from your preferred firm. Two to four weeks, priced up front, delivering a written specification you own outright and can put in front of anyone.
It should set out the ledger design, the authorisation flow including every failure case, the offline policy with its floor limits, the jurisdiction and dormancy model, the breakage policy expressed as journal entries, the fraud controls and who may change them, the distributor and franchise flows, the migration plan with its parallel period, and a fixed price for release one. Have your controller and your unclaimed property counsel read it before it goes to your shortlist. Quotes that cluster confirm the scope; quotes that scatter tell you who had not read the second half.
Digital Heroes produces that document before writing code, and contracts through an India LLP, a US LLC or a UK LTD so intellectual property assigns under your own law, which matters when the system holds a regulated liability. The record is verifiable through D-U-N-S, Clutch and Trustpilot.
Book a 30-minute call with Digital Heroes and get a written plan and a fixed quote within 48 hours.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- Global retail loses an estimated $1.73 trillion annually to inventory distortion (out-of-stocks and overstocks), equal to about 6.5% of global retail sales, despite $172 billion spent on improvements in the past year. Source: IHL Group (2025) →
- Item-level RFID tagging enabled 99.9% order accuracy in the retail supply chain, versus a baseline where 69% of orders shipped between brands and retailers contained data errors - showing how RFID-at-POS integration reduces inventory inaccuracy. Source: Auburn University RFID Lab & GS1 US (2018) →
- A study (led by Prof. Pak-Lok Poon, published in Frontiers of Computer Science, 2024) reviewing decades of spreadsheet-quality research found that about 94% of spreadsheets used in business decision-making contain errors, illustrating the hidden risk of manual spreadsheet workarounds that custom software is built to replace. Source: Central Queensland University / phys.org (Prof. Pak-Lok Poon et al.) (2024) →
- In a February 2026 survey of 517 small-business employers, 82% had adopted at least one AI tool (typical firm uses five), 66% reported revenue increases linked to AI (22% reported gains exceeding 10%), and 74% said digital platforms make it easier to compete with larger firms; owners saved a median of 5 hours per week and businesses saved a median 11.5 employee-hours weekly. Source: Small Business & Entrepreneurship Council (SBE Council) (2026) →
Frequently asked questions
How much does it cost to build a custom gift card platform?
A first release with the balance ledger, real-time till and online authorisation, activation, reload, refunds and liability reporting by entity runs $70,000 to $150,000 over 12 to 18 weeks. A full platform adding distributor activation feeds, dormancy and escheat by jurisdiction, fraud controls, franchise settlement and bulk corporate issuance runs $180,000 to $450,000 across 6 to 12 months. The number of separate till estates is the dominant driver.
What is the one authorisation question that separates good vendors?
Ask what happens when the connection drops after the hold and before the capture. The correct design is two-phase, a hold then a capture, so the balance is never ambiguous and a store manager is never guessing in the customer's favour. A vendor describing a single deduct has built a balance lookup, and you will find out during the busiest week of the year.
Why does jurisdiction have to be recorded when the card is sold?
Because unclaimed property obligations depend on where the card was issued, or in some cases the purchaser's address, at the moment of sale. Reconstructing that from sales history later is expensive and hard to defend. Every card should carry issuing entity, issuing location and a dormancy clock from creation. Confirm your specific obligations with unclaimed property counsel rather than a vendor datasheet.
How should a developer handle card draining fraud?
By instrumenting the whole lifecycle, not just redemption. Draining starts before activation when numbers are lifted from a retail rack and the packaging restored, so velocity rules fire too late. The strongest early signal is balance enquiry behaviour, since attackers poll to detect activation. Rate limit enquiries, detect enumeration against number ranges, and let your risk lead edit thresholds without a code release.
Does a gift card build pull us into payment card compliance scope?
Not on its own. Gift card numbers are not cardholder data in the sense the payment card standard regulates, so be careful about accepting compliance work in a quote that may not apply. That said, a card number is a bearer instrument, so design access controls, logging and rate limits as if it were payment data and keep full numbers away from casual support browsing.
How much does it cost to build a custom POS system for a small business?
A single-location custom POS covering checkout, inventory, receipts, and payment integration typically lands between $30,000 and $70,000, based on Digital Heroes delivery data across 2,000+ projects. Multi-location systems with kitchen displays, franchise reporting, or offline sync usually run $80,000 to $250,000. The biggest cost drivers are custom hardware support and how much of the payment flow you build versus integrate.
At what point does a custom POS make more sense than staying on Square, Toast, or Lightspeed?
The crossover usually arrives when your combined subscription and processing costs pass roughly $30,000 to $40,000 a year, or when a workflow you depend on simply does not exist off the shelf. A 10-location restaurant on Toast's published $69 per month plan, plus device fees, add-on modules, and processing markup, often clears that bar; a single cafe on Square's free plan or a boutique on Lightspeed Retail at $89 per month almost never does. Custom also wins when the POS is your product, for example if you plan to license it to other operators.
Can I build my product on a no-code tool like Bubble instead of hiring developers?
For testing whether anyone wants the product, yes, and Bubble's paid plans start at $29 a month, which is the cheapest validation you will ever buy. The ceiling arrives with complex data relationships, heavy integrations, performance at a few thousand users, and the fact that you cannot export a Bubble app to servers you control. A path many Digital Heroes clients take: prove demand on no-code, then rebuild custom once revenue justifies it, treating the no-code version as a paid prototype rather than a foundation.
Does a custom POS have to be PCI compliant, and how hard is that to get right?
Any system that touches card payments falls under PCI DSS, but the practical burden depends entirely on architecture. If your POS uses certified terminals from Stripe, Adyen, or a similar processor so card data never reaches your servers, most of the compliance scope shifts to the processor and you typically complete only a short self-assessment questionnaire. Building your own card capture puts you in full PCI DSS audit territory, which is why Digital Heroes has never recommended it in a POS engagement.
We run multiple restaurant locations on Toast. Would switching to a custom POS actually save money?
Usually only at 8 or more locations, where per-terminal software fees, add-on modules like online ordering and loyalty, and processing markup commonly total $8,000 to $20,000 per location per year in the statements Digital Heroes reviews for restaurant groups. A custom system converts that into a one-time build of $100,000 to $250,000 plus maintenance, which models out to 18 to 30 month payback for most groups. Under five locations, stay on Toast and put the money into operations.
Should I hire a freelancer or an agency for my software project?
A skilled freelancer is the right call for a single-discipline scope under roughly $15,000, like a website, a plugin, or one integration. Above that, projects need design, backend, testing, and project management at once, and a solo builder becomes the single point of failure: if they get sick or take a bigger client, your project simply stops. Agencies bill 20-40% more per hour but carry continuity, code review, and someone to escalate to, which is what you are actually buying.
How many people should be working on my software project?
Three to five for a typical focused build: a project lead, one or two engineers, a designer, and part-time QA, which is the standard shape across 2,000+ Digital Heroes projects. Larger platforms justify 6 to 10, but a ten-person team on a small first version usually signals bill padding rather than horsepower. What predicts success is whether a senior engineer is writing your code daily, not the headcount on the proposal.
How much should a small business budget for its first custom app or website?
For a focused first build, most small businesses land between $8,000 and $60,000: roughly $8,000 to $45,000 for a custom website and $25,000 to $60,000 for an internal tool or simple web app, based on Digital Heroes delivery across 2,000+ projects. Customer-facing products with payments, logins, or a mobile app start around $40,000. Quotes far below these bands usually mean a template with your logo on it, not software shaped around your workflow.
What should I have ready before I contact an agency about building a POS?
Bring three things: a written list of your 10 to 15 must-have workflows (returns, split payments, voids, shift close), your last three months of processing statements, and every system the POS must talk to, such as QuickBooks, your loyalty program, or a kitchen display. Agencies quote against unknowns, and this preparation tightens estimates by 20 to 30 percent in Digital Heroes scoping calls. You do not need wireframes or a technical spec; producing those is the agency's job.
What are the biggest mistakes first-time software buyers make?
Choosing the lowest bid, paying more than 30-40% upfront instead of on milestones, skipping a written specification, and having no maintenance plan for after launch. The most expensive of the four in Digital Heroes rescue projects is the missing spec: without written acceptance criteria, done becomes an argument instead of a checklist, and every disagreement resolves in the vendor's favor. Fix those four and you have avoided most of the ways these projects fail.
Can custom software connect to the tools we already use, like QuickBooks, Stripe, and Google Workspace?
Yes, and connecting your existing tools is one of the main reasons to build custom: mainstream platforms like QuickBooks, Stripe, Shopify, and Google Workspace all publish documented APIs. Budget 1 to 3 weeks of work per integration depending on API quality and how much data flows in both directions. Ask any vendor whether they have integrated with your specific tools before, because quirks like QuickBooks' OAuth token handling and API rate limits get learned on someone's project, and it should not be yours.
Who can build a custom POS software system?
Digital Heroes builds custom POS software systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other POS software companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
More from Shubham.
Senior Full Stack Developer · Lucknow · 1 post on the site
Published · Last updated .
