Boosts, Roses and Credits: Billing Dating App Add-On Purchases
Dating app in-app purchases billing, explained: price credit packs around fees, route App Store refunds and keep the evidence that wins disputes.

Photo: Pixabay
On this page 6 sections
- Why Dating App In-App Purchases Billing Differs From Subscriptions
- Price Credit Packs so the Fixed Fee Doesn't Eat the Sale
- App Store or Web Checkout: Who Owns the Refund
- Expiring Credits Can Fall Under Gift Card Law
- Define "Delivered" for Every Consumable
- Build the Evidence File Before the Dispute Arrives
Key takeaways
- When an in-app purchase is refunded, Apple or Google sends you a refund signal (a notification from Apple, an API record from Google). Set your system to take back the matching credits, or members can get their money back and still spend the boosts.
- Refund partly used packs at the pack's per-unit price, not the single-item price. Using the single price can send back the whole pack while the member keeps what they used.
- Credits bought with an app have no delivery address. To use Visa Compelling Evidence 3.0, match the member's login ID with their device ID or IP address, and keep at least 365 days of purchase history.
- Before you move members to web checkout to avoid store commissions, count your own dispute fees and reserve terms.
Dating app in-app purchases billing works when you treat every boost, rose or credit pack as a one-time digital good with its own price floor and its own paper trail. Price packs so the fixed per-transaction fee can't swallow the sale, log every credit from purchase to spend or expiry, and know before launch whether Apple, Google or your own merchant account owns each refund. With those in place, refunds take minutes and disputes land on an evidence file that already exists.
Consumables carry a different risk from subscriptions. They are small impulse buys, often made right after a conversation goes quiet, and whether the buyer feels they "got" anything is subjective. A subjective grievance can still end in a card dispute. If your whole model charges per message, see our guide to credit billing for pay-per-message dating sites.
Why Dating App In-App Purchases Billing Differs From Subscriptions
A subscription sells access over time, so its billing work centers on renewals and cancellation. A consumable sells one unit of value that is delivered when the member uses it, sometimes weeks after payment. At any moment a purchased credit is available, spent or expired, and support and dispute evidence both need to know which. A cardholder who disputes a credit pack is often disputing a mix of spent and unspent credits, and each half needs different evidence.
Keep consumables in their own ledger even when a subscription tier includes some. Label a premium plan's monthly boosts as included credits, separate from purchased ones, so refunding the plan leaves paid credits alone and refunding a pack doesn't touch the plan.
All of this sits inside an account that is high-risk by classification. Dating services process under MCC 7273, which appears on LegitScript's list of merchant category codes that Visa, Mastercard or both treat as requiring high-risk registration (Visa's High Integrity Risk registration and Mastercard's Specialty Merchant Registration Program). Registration is a network rule. Reserves and pricing are your processor's terms. For what those terms look like at major providers, see our guide to whether Stripe, PayPal and Square allow dating sites.
Consumables add a narrower problem on top: many small card-not-present sales, any one of which can become a dispute that costs more than the sale. Our guide to why dating site rolling reserves happen and how to lower them covers how those reserves work. If your account is ever closed, see our guide on what to do when a dating site merchant account is terminated.
Price Credit Packs so the Fixed Fee Doesn't Eat the Sale
Web card pricing usually combines a percentage with a fixed amount per transaction. The fixed piece barely registers on a large sale and takes a real bite out of a small one.
Illustrative example, not a quote. Assumptions: web checkout through your own merchant account, an all-in card cost of 3% plus $0.30 per approved sale, no refunds or disputes. A single boost priced at $5 costs $0.45 to process, or 9% of the sale. Five singles bought on five different nights cost $2.25 in fees. The same five boosts sold as one $15 pack cost $0.75, or 5%.
Your real rate depends on your processor agreement, but the shape of the math holds at almost any rate. Sell credits in bundles and price the single unit high enough that the pack looks like the obvious choice.
The fixed cost follows you after the sale. Depending on your agreement, the original processing fee often isn't returned on a refund, and chargebacks usually carry their own processor fee that can exceed a $5 sale. Even failed authorizations cost something, which is why we argue against blind retries in our piece on cutting the cost of retrying declined cards.
The smallest pack also attracts card testers. A cheap digital purchase that delivers instantly is a quick way to check a stolen card, and on a dating platform it can fund messages aimed at your own members. Cap how many small packs one account, device or card can buy in a short window. Our guide to stopping romance scammers who pay with stolen cards covers the signals worth watching.
App Store or Web Checkout: Who Owns the Refund
Inside an iOS or Android app, store policies generally require digital goods like boosts to go through Apple's or Google's billing. That is a store rule, not a card network rule or a law. The store collects payment, keeps its commission and handles refunds and card disputes; you never see the member's card. Apple's standard in-app commission is generally 30%, and developers in the App Store Small Business Program pay 15%, a rate that applies to the first $1 million in earnings each calendar year. Google Play sets its own service fees, so check its current developer terms.
| Same $15 pack, illustrative | Store or card cost | You keep | Who handles refunds and disputes |
|---|---|---|---|
| Apple, standard 30% | $4.50 | $10.50 | Apple |
| Apple, Small Business Program 15% | $2.25 | $12.75 | Apple |
| Web checkout at 3% + $0.30 (assumed) | $0.75 | $14.25 | You |
The web row looks best, but it is the only one that carries dispute fees, chargeback ratios, network registration and any reserve, and none of those are in the $0.75. Subtract your own disputed-dollar rate from that row before you push members to the web.
Store refunds still need your attention. When a member asks Apple to refund a consumable, Apple sends your server a CONSUMPTION_REQUEST notification, and the consumption data you return helps the App Store decide between a full refund, a prorated one or none. A REFUND notification follows if Apple grants it, and acting on it is your job. Google's Voided Purchases API lists purchases that were canceled, revoked or charged back so you can claw back the items they granted. Wire both into your ledger, or a member can get money back from the store and still spend the boosts.
On web checkout you are the merchant. The sale runs through your online payment processing, you set the refund policy, and every dispute counts against your ratios. Higher-value packs suit 3-D Secure authentication, which adds an issuer check on card-not-present purchases; our explainer on 3D Secure liability shift for online stores covers the tradeoffs. Rules on whether apps can link to outside payment options have changed and differ by country, as the South Korea fines against Apple and Google show, so check each store's current guidelines first.
Run both channels through one ledger and tag every credit with its channel and transaction ID. If a member who bought through the App Store asks you for a refund, send them to Apple. A web refund on top of a store refund pays them twice.
Expiring Credits Can Fall Under Gift Card Law
Separate two kinds of credits before you set any expiration. Paid credits are value a member bought. Bonus credits are ones you gave away, such as sign-up gifts or make-goods after an outage. Bonus credits are usually easier to expire on a short, disclosed timeline. Paid credits deserve more care.
The federal rule to know is the gift card section of Regulation E, 12 CFR 1005.20. For gift certificates, store gift cards and general-use prepaid cards, the underlying funds can't expire sooner than five years after issuance or the last load. The regulation's exclusions carve out several categories, including loyalty, award and promotional cards. State gift card and unclaimed property laws add their own rules, and some can reach unused stored value. Whether your credits fit any of these definitions depends on how they're structured and where members live. This is general information, not legal advice; have a qualified attorney review your credit terms before paid credits expire, and ask your accountant how to recognize revenue from unused balances.
Visa and Mastercard rules don't set your expiration policy, but an issuer reviewing a dispute will weigh whether the terms were clear at the point of sale. Four practices help:
- Show expiration terms on the checkout screen, next to the price. A footer link to your terms is weaker evidence.
- Spend credits in a stated order, bonus and soonest-expiring first.
- Send an expiration notice by email or in the app, and keep a record that it went out.
- Publish what happens to unused paid credits when an account is deleted or banned, and apply it every time.
Define "Delivered" for Every Consumable
Most refund fights trace back to one missing sentence: what "delivered" means for each item. Write it into your terms and build logs that prove it. A reasonable starting point:
- A boost is delivered when it runs its full advertised window while the profile is visible and eligible to be shown.
- A super like or rose counts once it lands in the recipient's queue.
- Message credits are used up when the message is sent.
- An undo or rewind is complete when the skipped profile reappears.
Non-delivery then has a clear meaning: an outage during the boost window, a super like sent to an account deleted before it was shown, a profile pulled into moderation mid-boost. Those are your failures. Restore the credit automatically, which costs nothing in card fees.
"I boosted and got no matches" is a different complaint. A boost sells visibility; matches depend on other people, and your terms and ads should say so. Ads implying guaranteed matches hand the cardholder a "not as described" argument. Matchmaking services face the same logic, covered in our guide to winning "no good matches" chargebacks. If you also run in-person events, see our guide to speed dating event payments, no-show terms and check-in.
Refund Partial Packs at the Pack's Unit Price
Support teams often get this one wrong. In the illustrative $15 five-boost pack, the unit price is $3. A member who used two boosts gets $9 back for the remaining three. Refunding at the $5 single price would return $15, the whole pack, while the member keeps two boosts.
Refund to the original payment method, and do it before a dispute is filed: that avoids the dispute fee and keeps the charge out of your dispute count. Once a dispute exists, a separate refund usually won't stop it and you can pay twice. Respond through the dispute process instead, and ask your processor how it handles refunds on disputed transactions. Our guide to fighting dating site chargebacks and fraud claims covers when a refund costs you less than fighting.
Build the Evidence File Before the Dispute Arrives
For "I didn't make this purchase" disputes on Visa, the strongest answer is Compelling Evidence 3.0. You show two earlier transactions on the same card, not reported as fraud, processed more than 120 and no more than 365 days before the dispute. At least two data elements must match across all three transactions: login ID, delivery address, device ID or fingerprint, or IP address, and one match must be the IP address or device ID.
Digital credits have no delivery address, so a dating app's realistic pair is login ID plus device ID or IP. Capture both on every purchase and keep at least 365 days of history, or your most loyal repeat buyers won't qualify. For each consumable purchase, also log:
- The checkout screen version the member saw, with pack contents, expiration terms and acceptance time
- Receipt email and its send time
- Credit balance before and after each purchase and spend
- Timestamped usage events, such as boost start and end or a super like sent
- Logins from the same device during and after use
Redact other members' identities before submitting evidence; you need to show a super like was sent, not who received it. Make your billing descriptor match the name members know the app by, which heads off "I don't recognize this charge" disputes.
Start with last quarter's data. Tag every consumable refund and dispute by item and channel, find the item driving the most, and tighten that item's delivery definition and logging first. For web checkout, MannyPay offers high-risk merchant accounts and payment gateways including Authorize.net and NMI; approval depends on underwriting. You can request a free quote, and a MannyPay specialist responds within one business day.
Sources
- What Are Merchant Category Codes (MCCs)? (LegitScript)
- App Store Small Business Program (Apple Developer)
- Apple's App Store Small Business Program: 15% Commission Explained (Appbot)
- Dive into App Store Server APIs for In-App Purchase, WWDC25 (Apple Developer)
- Fight Fraud and Abuse, Play Billing (Android Developers)
- § 1005.20 Requirements for Gift Cards and Gift Certificates (Consumer Financial Protection Bureau)
- 12 CFR Part 1005, Regulation E (eCFR)
- Visa Compelling Evidence 3.0 (CE3.0): Rules and 2026 Changes (Chargeflow)
This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.


