How Much Does a Gift Card Platform Cost to Build in 2026?
A gift card and stored value platform costs $70,000 to $450,000 to build.
On this page
A gift card and stored value platform costs $70,000 to $450,000 to build. A focused first release covering the balance ledger, real time authorisation at the till and online, activation and reload, and a liability report by entity runs $70,000 to $150,000 over 12 to 18 weeks, and a full platform adding distributor activation feeds, multi jurisdiction escheatment, fraud controls and business to business bulk issuance runs $180,000 to $450,000 phased over 6 to 12 months, based on Digital Heroes delivery experience. The decision that moves the number most is how many separate point of sale (POS) estates you have to authorise against. One till system keeps you at the bottom of the band; a group running Toast in some sites and an older Oracle Micros estate in others is doing the integration twice, often with a middleware shim in between, and that alone can add $40,000 and two months.
The bands a stored value build falls into
A focused first release runs $70,000 to $150,000 and ships in 12 to 18 weeks. That covers the balance ledger, real time authorisation for the till and the website, activation, reload, refunds and voids, and a liability report your controller can run. A full platform runs $180,000 to $450,000 phased over 6 to 12 months, adding distributor activation feeds, dormancy and escheatment by jurisdiction, the fraud engine, franchise settlement and bulk corporate issuance.
Card volume is not the driver people expect. The ledger handles a million cards as easily as a hundred thousand. What sets the number is how many places have to ask the ledger a question, how many rule sets it has to answer under, and whether there are existing balances sitting in customers' wallets that have to move without breaking.
- Balance ledger and card lifecycle, $30,000 to $60,000. The card, its funding event, every authorisation attempt, every redemption, every fee and its dormancy state as one authoritative record rather than four partial ones.
- Real time authorisation, $28,000 to $55,000. Two phase hold then capture, partial redemption, split tender, tips added after authorisation, voids and returns reversing to the original instrument, and a written offline policy with a configurable floor limit per channel.
- Point of sale integration, $22,000 to $45,000 per estate. Toast, Oracle Micros, Aloha, NCR and Lightspeed are genuinely different problems with different offline behaviour, and experience with one does not transfer cleanly.
- Ecommerce and digital delivery, $18,000 to $38,000. A code delivered by email is a bearer instrument sitting in an inbox and needs its own controls.
- Liability reporting by entity, $20,000 to $40,000. Outstanding balance, aged balances and movement, derived from the ledger rather than reconciled into a spreadsheet.
- Dormancy, breakage and escheat files, $30,000 to $60,000. Per jurisdiction clocks, scheduled breakage recognition producing journal entries, and a per state file.
- Fraud controls, $25,000 to $50,000. Balance enquiry rate limiting, enumeration detection, activation to first redemption scoring, first use holds, and an admin screen where your risk lead edits rules with an audit trail.
- Distributor activation adapters, $18,000 to $35,000 each. Every distributor has its own format and its own settlement terms.
- Franchise settlement, $25,000 to $50,000. Automatic inter entity entries at the agreed reimbursement rate with a statement each franchisee can dispute against a line item.
- Bulk corporate issuance, $22,000 to $45,000. Self serve portal, approval step, upload, per recipient delivery and its own invoice.
- Balance migration with a parallel period, $25,000 to $55,000.
What drives a stored value build up
- Multiple point of sale estates. The most expensive line in the whole category. Older estates frequently need a middleware shim before they can call anything modern, and the offline behaviour has to be characterised per estate rather than assumed.
- Multi entity and multi currency. This changes the ledger design rather than adding to it, so it is not a feature you bolt on in month eight. Decide before the first schema is written.
- Distributor count. Each third party retail relationship is a separate format, a separate activation timing, and a separate reconciliation flow with real money at stake.
- Jurisdiction spread. State unclaimed property treatment of gift cards varies considerably, so a group operating across many states carries several variants of the same dormancy rule. Get your specific position from unclaimed property counsel rather than a vendor datasheet.
- Migrating live balances. Those cards are already in wallets and cannot be reissued, so the migration runs as a dual authorisation period of two to four weeks with daily reconciliation. Budget that parallel period as project cost, not overhead.
- One ledger for stored value, loyalty and store credit. This is where most groups eventually land and it is a design decision with a price, not a later configuration.
What keeps the number down
- One entity, one point of sale, one country for release one. Distributors and franchise settlement go to phase two. This is the single largest lever available.
- Keep the card production and fulfilment vendor. Plastic, packaging and rack distribution are not software problems and rebuilding them buys nothing.
- Defer the fraud engine by one phase, not two. Instrument the ledger from day one so the signals are being recorded, then build the rules once you have a few months of your own data to tune against. Building rules against imagined patterns costs more and works worse.
- Write the offline policy before the code. Deciding whether a disconnected till declines stored value or authorises to a floor limit is a commercial decision that takes an afternoon and saves weeks of rework.
- Report from the finance warehouse you already have. If the controller lives in NetSuite, feed it rather than building a second reporting stack inside the platform.
- Gift card numbers are not cardholder data under the payment card standard. That spares you a scope many teams budget for by reflex.
A worked example that adds up
A restaurant group with 210 locations, of which 60 are franchised, roughly $14M in outstanding liability, two point of sale estates because an acquisition brought an older Oracle Micros footprint alongside Toast, operations across several states, an ecommerce and digital delivery channel, and existing balances on an incumbent processor that have to move.
- Discovery, ledger design and jurisdiction rule capture: $12,000
- Balance ledger and card lifecycle: $46,000
- Real time authorisation with hold and capture: $44,000
- Toast integration: $31,000
- Oracle Micros integration including middleware shim: $38,000
- Ecommerce and digital delivery channel: $27,000
- Liability reporting by entity and jurisdiction: $33,000
- Dormancy, breakage recognition and escheat files: $45,000
- Fraud controls with an editable rule admin: $36,000
- Franchise settlement and statements: $37,000
- Balance migration with a dual authorisation period: $41,000
That totals $390,000. Add a 12 percent contingency, because at least one state's treatment will turn out to differ from what finance believed, and the committed number is $437,000 across roughly eleven months. Distributor adapters and corporate bulk issuance are deliberately excluded and would add $18,000 to $35,000 per distributor and $22,000 to $45,000 respectively.
How the spend phases
- Weeks 1 to 4, about $12,000. Ledger design and jurisdiction rule capture with finance, legal and operations in the room together. The output is a written offline policy and a documented breakage policy your auditor has seen.
- Weeks 4 to 18, about $90,000. The ledger and the authorisation engine. Nothing else can be built until a hold and a capture behave correctly under a dropped connection.
- Weeks 12 to 24, about $69,000. Both point of sale estates, overlapping the ledger work because integration lead times are outside your control.
- Weeks 16 to 44, about $41,000. Migration, starting early and running long because the dual authorisation period is measured in weeks of parallel operation and daily reconciliation.
- Weeks 20 to 28, about $27,000. Ecommerce and digital delivery.
- Weeks 22 to 34, about $78,000. Liability reporting and the dormancy, breakage and escheat engine. This is the phase the chief financial officer is paying for.
- Weeks 26 to 36, about $36,000. Fraud controls, built once several months of real activation and enquiry data exist to tune against.
- Weeks 30 to 42, about $37,000. Franchise settlement and statements, last because it depends on redemption posting being trusted.
The ongoing costs nobody quotes
- Support and maintenance, 18 to 25 percent of build. On a $437,000 platform that is roughly $79,000 to $109,000 a year.
- Unclaimed property rule maintenance, $12,000 to $30,000 a year. State treatment changes and you enter new states. Each change is a dormancy clock and a file format, not a memo.
- Point of sale version upgrades, $8,000 to $25,000 per estate per major version. Till software moves on its own schedule and authorisation is the first integration to break.
- Fraud rule tuning, $10,000 to $25,000 a year. Draining patterns shift every holiday season, which is exactly when nobody has time to change them unless the rules are editable by your risk lead.
- Distributor onboarding, $18,000 to $35,000 each. Commercial teams add retail rack partners without consulting engineering.
- Hosting, security and access review, $12,000 to $30,000 a year. Full card numbers must not be freely browsable by support staff, and proving that is an annual exercise.
- Audit support, $10,000 to $25,000 a year. An unclaimed property examination is far cheaper to answer from a ledger than from a reconstruction, but it still takes finance and engineering time.
Comparing a build against your current renewal
Neither Givex nor Paytronix publishes pricing, and neither do the distribution networks, so you have to assemble this yourself. Ask your incumbent for a three year total that includes per location fees, per transaction fees at your actual volume, card production, digital delivery, and the quoted price of the two or three custom changes you have wanted for the last eighteen months. That last item is usually the revealing one, because a change request against someone else's roadmap has both a price and a date, and the date is often the real cost.
Then add the internal cost the subscription does not show. If your finance team spends four days a month reconciling a processor liability figure against the point of sale journal, that is roughly a fifth of a finance salary. Total last year's goodwill refunds on drained cards, and count the hours lost to franchise settlement disputes.
The result is often that the subscription is not the expensive part. The expensive parts are the reconciliation, the goodwill refunds and the changes you cannot get made. A build removes the second and third and largely removes the first, while adding maintenance you now own. Be honest about that maintenance line, because a stored value ledger with no funded owner drifts into exactly the state you were trying to leave.
When buying beats building
Buy if your outstanding liability is under roughly $2M, you operate in one or two states, you have a single point of sale estate and you are not selling through third party retail racks. Givex and Paytronix are genuinely solid at that scale, the till integrations already exist, and a build is an expensive way to arrive at the same place. Put the difference into stores.
Buy also if nobody in finance is currently asking for a jurisdiction breakdown. The escheatment engine is the most expensive component in the full platform, and without it the case for building collapses to the authorisation layer alone, which the incumbents already do competently.
Build when two or more of these are true. Outstanding liability is over $10M and finance cannot produce a jurisdiction breakdown on demand. You sell through distributors and reconciliation is manual. Franchise settlement disputes are a recurring meeting. You have been hit by card draining and your only tool is a goodwill refund. Or stored value, loyalty points, store credit and refund credit need to sit in one ledger, which is where every multi brand group eventually lands and where bolt on products stop working entirely.
If you would rather someone argued with your brief than agreed with it, Digital Heroes contracts through India LLP, US LLC and UK LTD entities, so the agreement and the intellectual property assignment sit under law your own advisers already read. Nothing about that commits you to the build.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- 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) →
- The NRF discontinued its long-running annual shrink report, stating that a broad study of retail shrink 'is no longer sufficient for capturing the key challenges and needs of the industry' - important context that qualifies how POS/shrink benchmarks should be cited going forward. Source: Retail Dive (2024) →
- Almost half of all the activities people are paid almost $16 trillion in wages to do in the global economy have the potential to be automated by adapting currently demonstrated technologies. Source: McKinsey Global Institute (2017) →
- OECD research finds that digitalisation offers SMEs opportunities to improve performance, spur innovation, enhance productivity and compete more evenly with larger firms; it reports that increased use of online platforms produced significant multi-factor productivity gains in SME-heavy sectors such as hospitality and retail, while smaller firms lag in adoption due to skills, resource and financing gaps. Source: OECD (2021) →
Frequently asked questions
How much does it cost to build a custom gift card platform?
A first release with the balance ledger, real time authorisation at the till and online, activation, reload, refunds and a liability report runs $70,000 to $150,000 over 12 to 18 weeks. A full platform adding distributor feeds, escheatment by jurisdiction, fraud controls, franchise settlement and bulk corporate issuance runs $180,000 to $450,000 over 6 to 12 months.
A realistic multi state restaurant group with two point of sale estates, franchise settlement and a live balance migration lands around $437,000 including contingency, across roughly eleven months.
What does each additional point of sale system add to the cost?
Commonly $22,000 to $45,000 per estate, and older estates sit at the top of that range because they often need a middleware shim before they can call a modern service. Toast, Oracle Micros, Aloha, NCR and Lightspeed have genuinely different offline behaviour, so each has to be characterised rather than assumed.
Ongoing, budget $8,000 to $25,000 per estate for each major version upgrade, since authorisation is usually the first integration to break when till software moves.
What does a stored value platform cost to run each year?
Budget 18 to 25 percent of build for support and maintenance, which on a $437,000 platform is roughly $79,000 to $109,000 a year. Add $12,000 to $30,000 for unclaimed property rule maintenance as state treatment changes and you enter new states.
Then fraud rule tuning at $10,000 to $25,000 a year, hosting and access review at $12,000 to $30,000, audit support at $10,000 to $25,000, and $18,000 to $35,000 for each new distributor your commercial team signs.
Is Givex or Paytronix cheaper than building our own platform?
At a single entity in one or two states with one till system and no third party retail distribution, yes, comfortably, and we would say so before quoting. The integrations already exist and the programme complexity does not justify a build.
The comparison shifts once liability is over roughly $10M and finance cannot produce a jurisdiction breakdown, or when you need stored value, loyalty and store credit in one ledger. Ask your incumbent for a three year total including per transaction fees at your volume and a quoted price and date for the custom changes you have been waiting on. The date is often the real cost.
How long does it take to build a gift card platform?
Twelve to eighteen weeks for a first release covering the ledger, authorisation, activation, reload and liability reporting for one entity on one point of sale system. A full multi jurisdiction platform with distributors, fraud controls and franchise settlement is 6 to 12 months.
The item most likely to extend the schedule is not code, it is legal. Confirming your dormancy and escheatment position across states takes weeks and it has to happen before the ledger schema is finalised, because jurisdiction has to be stamped on the card at creation rather than derived later.
How much does the escheatment and unclaimed property engine cost?
Thirty thousand to sixty thousand dollars for dormancy clocks per jurisdiction, scheduled breakage recognition producing journal entries rather than a memo, and a per state escheat file. It is the most expensive single component in the full platform and it is usually why the chief financial officer funds the project.
The prerequisite is cheap and non negotiable: every card must record its issuing entity, issuing location and jurisdiction at the moment of sale. Reconstructing that from sales data during an examination is expensive and hard to defend.
What does migrating existing gift card balances cost?
Twenty five thousand to fifty five thousand dollars, most of which is the parallel operating period rather than the data move. Those cards are in customers' wallets and cannot be reissued, so lookups run against the new ledger with a fallback to the old processor for two to four weeks, with daily reconciliation.
Budget that parallel period as real project cost. Groups that treat migration as a cutover weekend are the ones that end up refunding balances by hand for a month.
Does a gift card system fall under payment card security scope?
Gift card numbers are not cardholder data in the sense the payment card standard regulates, so a stored value ledger does not pull you into card scope on its own. That is a real saving and one many teams budget for unnecessarily.
Design it as a bearer instrument anyway: rate limit balance enquiries, avoid exposing full numbers to support staff, and log access. Doing that at the schema stage costs almost nothing, and it is also the foundation the fraud engine sits on later.
What does a fraud engine for card draining cost, and when should we build it?
Twenty five thousand to fifty thousand dollars for enquiry rate limiting, enumeration detection, activation to first redemption scoring, first use holds on high value online redemptions, and an admin screen where your risk lead edits rules with an audit trail.
Build it in phase two, but instrument the ledger from day one so the signals are already being recorded. Rules written against imagined patterns cost more and work worse than rules tuned on three months of your own activation and enquiry data.
How many SaaS seats do we need before building custom becomes cheaper?
The crossover usually shows up between 20 and 50 seats on premium tiers. Salesforce Enterprise lists at $165 per user per month, so 40 users cost about $79,000 a year in subscriptions, which is real money against a custom system you would own outright. Run the comparison over three years: if subscription spend beats the build cost plus 15-20% annual maintenance, custom wins on price before you even count workflow fit.
How do I vet a development agency for a POS project specifically?
Ask to see a live POS or payments product they built, then ask exactly how they handled offline mode, receipt printing, and PCI scope, because those three areas expose anyone who has only built ordinary web apps. A competent agency will name the payment SDKs they used, such as Stripe Terminal or Adyen, and describe their terminal certification process without checking notes. If the portfolio is all marketing sites and dashboards, keep looking.
Can a custom POS beat Square's 2.6% plus 10 cents processing rate?
Yes, because a custom POS lets you choose interchange-plus processing instead of flat-rate pricing, which in the client migrations Digital Heroes has run commonly lands near 2 percent all-in on card-present volume for established businesses. On $1.5 million of annual card volume, each half point saved is worth $7,500 a year before you count software fees. Below about $250,000 in annual card volume the savings rarely justify the build, so run the math on your processing statements first.
Who owns the code when an agency builds my software?
You should, completely, through a written intellectual property assignment that transfers everything on final payment; without that clause, copyright stays with whoever wrote the code by default. Insist that the repository lives in your own GitHub organization from day one and that hosting, domains, and third-party accounts are registered to you. Also check for licenses to the agency's proprietary frameworks buried in the contract, because those can make switching vendors practically impossible even when you own your own code.
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.
Should I use a freelancer or an agency to build my POS system?
A POS build needs backend, client app, payments integration, and hardware testing skills running at the same time, which is more surface area than one freelancer reliably covers. Freelancers make sense for narrow additions, like a reporting module on an existing system, at typical rates of $30 to $90 per hour. For a ground-up build, an agency with a dedicated QA function is the safer choice because a register failure stops your revenue at the counter in real time.
Does it matter which tech stack the agency wants to use?
Yes, but not in the way most buyers expect: the goal is boring, popular technology such as React, Node.js or Python, and PostgreSQL, because any future team can maintain it and hiring a replacement developer takes days, not months. The red flag is an agency-proprietary framework or an unusual language, which welds you to that one vendor no matter what your contract says about code ownership. A useful test: could you find three freelancers fluent in this stack within a week? If not, push back.
If an agency builds my POS, who actually owns the source code?
You should own it outright, and the contract must say so through a full IP assignment clause that transfers copyright on payment, not a license to use it. Also require the code to live in a repository under your own account from day one, so ownership is a fact rather than a promise. Walk away from any agency that keeps the code and charges you to stay on their platform; that is a more expensive version of the vendor lock-in you were trying to escape.
What should I prepare before contacting a software development agency?
A one-page brief beats a 40-page requirements document: the business problem in plain words, who will use the system, the 5 to 10 workflows it must handle, the tools it must connect to, and your budget range and deadline driver. You do not need wireframes, a specification, or technical vocabulary; producing those is the agency's job during discovery. Stating a budget range up front is the single best move, because it gets you honest scoping instead of a quote engineered to win the meeting.
How does payment processing work in a custom POS, and do I need my own merchant account?
Your POS software handles the order, then hands the charge to a payment provider; you never build card processing yourself. The two common routes are an aggregator like Stripe, live in days at a published in-person rate of 2.7 percent plus 5 cents, or a dedicated merchant account with interchange-plus pricing, which takes 1 to 3 weeks of underwriting but costs less at volume. Most Digital Heroes POS builds launch on Stripe Terminal and renegotiate processing once volume justifies it.
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
Published · Last updated .
