Who Powers Virtual Gift Cards on Shopify?

Genius Referrals illustrates the problem. Its Shopify listing presents Growth at $99 monthly. Its current vendor page presents a different plan structure, including Silver at $219 monthly, with different allowances and payout features. The two sources should not be silently treated as equivalent packages. The appropriate request is a written quote naming the Shopify integration, virtual-card fulfillment, advocate allowances, payout charges, and the plan that governs them. [S30], [S61].

GetAmbassador presents another mismatch. The current Shopify listing displays $12,000 per month, while the linked enterprise pricing page describes a scoped commercial offer. That displayed number should neither be relabeled as an annual price nor assumed to be the price of a particular virtual-card program. [S42], [S62].

White Label Loyalty separates the loyalty engine from fulfillment. Its $14,400 annual price is equivalent to $1,200 per month across the contract, not a $1,200 month-to-month offer. Its Runa-backed Reward Fulfilment module is separately purchased and requires a forecast and initial float. [S32], [S33].

AnyCard and Qwikcilver illustrate a product mismatch. A Shopify price for merchant gift cards does not establish the price of a separate Visa/Mastercard program. Qwikcilver's listing also uses rupee-denominated allowances and local-billing wording alongside Shopify's USD presentation. Those figures are unsuitable as an unqualified US virtual-card quote. [S63], [S48], [S49].

The providers behind and beyond the apps

The App Store directory is only one route to a supplier. Providers also sell through APIs, enterprise agreements and partners that a gift-card search may not surface.

For a direct relationship, start with the operating model: who buys and funds the rewards, who serves the merchants, and who supports recipients. A provider’s published offering can inform that discussion; approval and price for the proposed program require its own agreement.

T12. Virtual-card suppliers beyond an individual app

Giftbit, PerfectGift, InComm, and Onbe are included here as additional suppliers for consideration. This article does not claim that each has a verified connection to one of the 18 Shopify apps above. Onbe's public material establishes virtual prepaid and embedded payouts; the exact proposed US Visa/Mastercard and issuer combination still requires product documentation.

BHN and Tango: consolidation changes the supplier map

Tango says Blackhawk Network acquired it in May 2024. BHN announced completion of its Tango integration in March 2025. They should therefore be treated as one ownership group when assessing supplier concentration, even where their product brands and integration routes differ. [S75], [S76].

For a prospective partner, the useful question is which product team and contractual route fits the intended workflow. A Tango catalog integration already embedded in an app may be a different commercial proposition from a direct BHN digital-card program. Group ownership does not make the two offers automatically identical.

Tremendous: the recurring connection behind the apps

Tremendous’s recurring role makes sense in this app set. Referral and loyalty developers need to calculate rewards, while an external platform can handle the catalog, account funding and delivery. Several guides describe the account, campaign and payout settings that join those jobs together.

For a merchant already using one of those apps, the connection can provide a practical starting point. It also creates a shared dependency across apps: switching the marketing software may leave the underlying fulfillment provider unchanged.

The inventory explains that distribution pattern. It cannot rank uptime, approval rates or merchant satisfaction, and it says nothing about private terms available to a new distribution partner.

Runa: the commercial form matters as much as the API

Runa's prepaid terms, updated 27 February 2026, tie service and issuance fees to the Commercial Form and pass through applicable issuing-bank fees. They describe funding through a buyer float and a separate issuing bank. The terms also permit a pause in further issuance if, unless otherwise agreed, at least 30% of monthly card transaction value is spent outside the United States, including at online merchants not registered as US merchants. [S66].

For an ecommerce program, that geographic clause is commercially significant. A dollar-denominated virtual card and a US-oriented program do not necessarily permit an unrestricted international spending pattern. The approved product, recipient countries, merchant locations, and contractual exceptions should be discussed together.

Separately, White Label Loyalty's use of Runa does not prove that all Runa products are available through its module. A direct Runa agreement and a Runa-powered loyalty integration can have different catalogs and economics.

Giftbit: the product matters to the price

Giftbit's catalog explicitly separates US Visa from USD Mastercard products. Published denomination ranges begin at $0.01 for certain US Visa offerings and $1 for USD Mastercard, with products up to $2,000. Those ranges identify possible products; they are not a promise of approval for every merchant or use case. [S67].

Giftbit advertises no platform subscription or minimum-usage fee and lists a 2.9% credit-card funding fee. Selected prepaid products carry additional fees. Its issuer disclosures identify different banks for different offerings. A program should therefore be quoted by product rather than by the word “Giftbit” alone. [S77].

Its developer guidance distinguishes approved rewards use cases from restricted activities such as consumer resale or peer-to-peer gifting. A Shopify platform awarding incentives across multiple independent merchants should explain that operating model during onboarding instead of assuming a general API account covers it. [S68].

PerfectGift: branding the redemption experience

PerfectGift offers a provider-hosted digital redemption experience for Visa and Mastercard programs with partner branding. The detail to examine is how far that branding extends: the screens, domain, data access and support interactions may matter as much as the email that first delivers the reward. [S70].

Its corporate pricing page lists 3% credit-card funding, while Visa/Mastercard fees depend on quantity, expiration, and format. The page identifies Sutton Bank in the relevant program disclosures. A free corporate account should therefore not be mistaken for zero-cost card issuance. [S78].

Review the recipient demonstration and the fee schedule together. A well-presented redemption journey and economical card issuance are separate requirements.

InComm: distribution infrastructure and client-controlled presentation

InComm InCentives describes an API through which a client can build its own front end while InComm handles fulfillment. Its company disclosures identify Visa and Mastercard virtual accounts backed by particular issuing-bank programs. This supports a conversation about a direct integration even when no suitable app connection appears in the screening inventory. [S71], [S72].

The unresolved questions are the actual catalog made available to the partner, whether the business model is treated as a corporate reward program or distribution arrangement, and the complete commercial schedule. The cited 2025 product announcement is evidence of program relationships; its historical promotional offer is not current pricing.

Onbe: managed operations as part of the proposition

Onbe offers no-code, low-code, and API integration approaches, alongside a white-label partner model and program-management services. This positions it for discussions where implementation, reconciliation, and recipient operations matter alongside card delivery. [S79], [S74], [S80].

Its broader payout menu should not obscure the product question. A transfer to someone's existing debit card differs from issuing a new virtual reward card. The commercial proposal should name the intended US virtual program, network, issuing bank, reloadability, recipient verification, and applicable fees. Those specifics were not established for a proposed Shopify program in the public pages reviewed.

T13. Company-reported scale, with different measurement bases

These figures come from the companies’ websites and retain their different scopes. The annual metrics do not identify a measurement year; Tremendous’s figures have no stated annual period. Adding them together, ranking them as equivalent volumes or dividing them by a general gift-card market estimate would produce a misleading comparison.

The research materials contain no comparable provider-share dataset for US virtual rewards originating in Shopify programs. A useful volume request would specify the same twelve-month period, geography, product class and distribution channel, with both card count and loaded face value.

What happens between reward approval and spending

The word “sent” can conceal several unfinished steps. A reward may be earned, approved and delivered before a recipient claims it, obtains a card or makes a purchase. Each state belongs in the reporting.

T14. From reward earned to remaining balance

ReferralCandy provides a useful example: its Tremendous integration describes a successful reward status as email delivery. That confirms delivery, not claim or spending. A dashboard that calls every delivered reward “redeemed” would overstate recipient use. [S18].

A useful provider demonstration follows one recipient from message to purchase: accepting or choosing the reward, accessing credentials, finding the balance, making an eligible online payment and handling a remainder or failed attempt. These are steps to request in a demonstration; this investigation did not issue or spend a card.

A provider's claim page may also have different requirements from an app's signup form. Tango's published prepaid page says recipient information can be required and that additional identity information may be requested on first redemption. Digital delivery should therefore not be used as shorthand for anonymous or verification-free use. [S84].

Likewise, a general mobile-wallet feature does not settle the chosen product's wallet eligibility. A Shopify merchant gift-card pass is different from provisioning a network card for payment. The provider should demonstrate the exact virtual product and clarify any optional setup rather than rely on an undifferentiated wallet logo. [S85].

Unused value and merchant recovery rights

When money remains unused, the first question is where it sits: in the merchant’s funding account, behind an unclaimed reward link, or on a card already issued to a recipient. Those balances can have different owners and recovery rules.

T15. Five balances and the evidence needed for recovery

Unredeemed value may eventually contribute to breakage. Whether the merchant can recover money left on an issued card is a separate contractual question. The presence of an unused balance does not establish the merchant’s entitlement.

Tremendous allows cancellation of eligible unredeemed rewards: directly within 30 minutes, with reviewed requests available through the dashboard for up to seven days, and support involvement thereafter. Once the recipient chooses a payout option, its ordinary order-cancellation process does not refund that redeemed reward. This separates an unclaimed offer from an issued card with money left on it. [S86].

Tango's policy limits cancellation to specified eligible products and circumstances, such as delivery errors or fraud. Its self-service window for eligible, wholly unredeemed digital Tango Choice rewards is five days; later requests involve support; the policy specifies a cancellation or restocking fee for cancellations completed through support. This is not a general right to reclaim any unused virtual-card balance. [S87].

Giftbit publishes a default return of 25% of an unclaimed Promotional reward’s value to the sender’s account after the sender-set claim deadline. Standard rewards have no claim deadline. This concerns an unclaimed reward offer, not money left on a card that has already been issued. [S77].

Fondue's marketing discusses revenue retained when shoppers do not claim cashback. Its cardholder agreement separately says remaining promotional-card funds become unavailable to the cardholder after expiration. Neither statement, by itself, supplies the merchant's percentage, settlement timing, or entitlement to funds left on an issued card. [S35], [S05].

The material reviewed here does not establish an automatic merchant right to all unused issued-card balances. A recovery or revenue-sharing offer needs to identify the relevant stage, the entitled party, the calculation and the settlement date. An undisclosed fee or policy remains an unknown in the commercial model.

How to measure program value

A reward’s value depends on the job it is meant to do: acquisition, referrals, affiliate compensation or customer service. Network-card rewards give recipients spending flexibility beyond the originating store. Merchants therefore need an objective that does not depend on all the funded value returning as another purchase.

T16. Measures that match the program’s purpose

For a controlled evaluation, define the eligible population before offering the incentive. Compare equivalent groups over the same period, including customers who never claim. Deduct reward costs, app fees, funding, support, returns, and fraud losses consistently. If the contribution calculation already includes an expense, do not subtract it again.

The measure to pursue is the contribution created after program costs, compared with what would have happened without the incentive. App attribution can help assemble the evidence. It cannot establish the counterfactual on its own.

Choosing a provider and reading the evidence

Bring a defined product and operating model to the first provider discussion. “Virtual gift cards for Shopify” leaves open the recipient, the reward trigger, the issuing program and the party responsible for the funds. The questions below turn that broad request into something a provider can price and approve.

T17. Provider questions: product and access

T18. Provider questions: economics and remaining funds

T19. Provider questions: integration and recipient experience

Use the answers to build a proposed program with named products, responsibilities and costs. An API or an app connection is a starting point; it is not a substitute for those terms.

What the app connections tell us

The clearest pattern is the connection between marketing software and rewards infrastructure. A merchant can reach a virtual-card provider through an app it already uses. The provider, in turn, can reach merchants without supplying the entire referral or affiliate system.

The resulting choices span several business models. Tremendous recurs behind app integrations. BHN/Tango combines a large supplier group with digital reward delivery. Runa powers a separately purchased loyalty module, while Fondue embeds a particular promotional program. AnyCard and Pine Labs illustrate the distance that can exist between a provider’s wider prepaid business and the product described in its Shopify listing. Giftbit, PerfectGift, InComm and Onbe add further direct and partner routes.

The useful comparison is between complete workflows: a named virtual product, a price with clear units, a recipient journey and reporting that distinguishes delivery from use. Providers that make those elements easy for software partners to specify and explain are easier to evaluate. The agreement must also say what happens to every significant cost and balance.

The conspicuous absences: Stripe and Adyen

Two familiar names do not appear among the six fulfillment groups in this directory: Stripe and Adyen. That is worth highlighting because both offer virtual-card issuing. Their absence here concerns the app relationships identified by this research, rather than their ability to create cards or their use elsewhere in commerce.

The sheet review found no mention of either company in the checked fields of the 2,760 app records or in the comparison and provider tabs. [S01].

T20. Issuing platforms absent from the identified app relationships

The difference is between connecting an app to an existing reward catalog and building the card program behind the reward. Issuing infrastructure gives a platform more decisions to make about cardholders, funding, spending controls, and ongoing servicing. A referral app's ready-made reward option is a different starting point.

Product approval matters as well. Stripe's published Issuing rules prohibit specified consumer uses, including cards accessing consumer funds and cards disbursing payroll or payouts. A general statement that Stripe creates virtual cards therefore does not establish that the particular shopper-reward model proposed here is eligible. The exact product and permitted use case need to be established. [S92].

For Adyen, the published onboarding process explicitly begins with the business model, intended cards, and expected activity. It then defines the accounts, verification, funding, and authorization arrangements. That supports considering Adyen for an appropriately designed issuing program; it does not supply evidence of an existing connection to one of these 18 apps. [S91].

Neither absence explains why the app developers chose their current providers. The public inventory cannot reveal undisclosed infrastructure, private partnerships, or rejected proposals. Its narrower finding is still useful: large issuing platforms can sit outside the reward-provider relationships that are easiest for a Shopify merchant to discover.

Research scope and source boundaries

• Inventory: The app counts and provider groupings were checked against the underlying sheet. It records two Shopify App Store searches and 2,760 distinct app URLs. The 18 relationships form an editorial evidence set, not a universal list or market-share ranking.

• Evidence strength: Search descriptions, app listings, integration guides, provider catalogs, and cardholder agreements answer different questions. The directory preserves those differences, including configurable-catalog inferences and legacy documentation.

• Virtual scope: This article evaluates digital delivery and virtual-card pathways. Costs or capabilities for other formats are not used to price the virtual programs.

• Geography: US/USD is the principal comparison. A global catalog, US-dollar denomination, or multinational provider does not by itself establish eligibility in every country.

• Pricing: The comparison uses the public schedules cited for 16 September 2026. Calculations are labeled scenarios; unknown charges remain unknown. App fees, reward principal and provider/funding charges are separate.

• Statista: Consumer-experience data come from Accenture’s survey as published by Statista, with the population and multiple-response format stated. The US market series retains the source’s projection labels.

• Provider position: Corporate-scale figures are attributed to the companies and retain their stated scope. No equivalent market-share comparison or private commercial commitment is asserted.

• Evidence boundary: The article draws on the inventory and published materials. It claims no installation test, successful live issuance or response from a provider representative. Links accompany the relevant claims, including those inside tables.