Every step between a player pressing buy and money reaching you
Game content is handed over the instant it is paid for, which changes how the payment behaves. A decline costs you the sale rather than delaying it, a dispute arrives after the item is already in an account, and a large share of your players live somewhere a card is not the normal way to pay. This page is about those mechanics rather than about the storefront around them.
What the payment path does on your behalf
- Chooses the methods for the player's country
- What appears at checkout is picked from the player's location and the charging currency. Cards and wallets everywhere, then bank redirects, vouchers, buy-now-pay-later, PayPal and the South Korean methods where those are what people use — over 250 in total.
- Shows a price the player recognises
- Pricing can be localised and displayed tax-inclusive, so the figure on the product page is the figure charged. A total that grows at the last step is one of the cheapest ways to lose a purchase.
- Screens the transaction before it settles
- Instantly delivered digital goods attract card testing and stolen-card use, because there is nothing to intercept in the post. Screening happens before settlement rather than after you have already granted the item.
- Takes the dispute when one arrives
- We are the legal seller, so a chargeback is filed against us and worked by us. It does not land on a merchant account of yours. A sustained negative balance, from a run of refunds for example, may still be debited from your bank account.
- Puts a name on the statement players know
- The statement descriptor is editable. A line item nobody recognises two weeks after a purchase is a common trigger for a dispute that was never really fraud.
- Settles into your own account daily
- Net revenue goes to the payout account you connected, on a daily schedule by default, across over 110 supported countries. Weekly, monthly or manual are available if your finance side prefers them.
What happens during a single purchase
- 01
The checkout opens
As a full hosted page, an overlay on your store, or an embedded frame. In all three the card fields belong to a surface we run, so nothing sensitive touches your servers and none of your infrastructure comes into PCI scope.
- 02
The charge is authorised, screened and taxed
Billing details are collected because we are the seller of record, the correct rate for the buyer's country is applied, and the transaction is screened before it is allowed to complete.
- 03
Your systems are told
A payment webhook reaches your backend, carrying any custom checkout fields you configured — a player ID or account name, typically. That is what lets the entitlement be granted server-side rather than trusted from a client.
- 04
The money moves
The customer pays into our merchant account, the amount is redirected instantly to your connected sub-account, our 5% + 50¢ comes out, we pay the processing fees, and the net balance follows your payout schedule.
Why game payments behave differently
Delivery cannot be recalled
A currency pack that has been credited is spent within minutes. The defence is not a better refund policy, it is granting on the payment webhook and listening for the refund and chargeback events so access is withdrawn when a payment reverses.
The player is not always the cardholder
Some share of purchases in any game with young players are made on a card belonging to somebody else, and a proportion of those come back as disputes. A recognisable descriptor and local payment methods that do not involve a family card both reduce it. Neither removes it, and no processor can honestly claim otherwise.
Your players are not where your studio is
A player in Brazil, Poland or South Korea who does not see a way to pay that they already use tends to close the tab. Nothing appears in your dashboard when that happens, which is why method coverage is easy to under-invest in.
One rate covers the whole path
Processing, tax calculation and filing, fraud screening, refunds and chargebacks sit inside a flat 5% + 50¢ per successful transaction. There is no monthly platform fee and nothing at all in a month where you sell nothing. Negotiable once you are selling at volume.
What sellers say once they have switched
★★★★★ 4.8/5 from 10 reviews on G2 →
Vadim Finayev “We work with quite a few merchants of record, but none comes close to the support and speed of implementation of Fungies. If you want a payment partner that actually gives you the feeling they want to work with you — rather than leaving you on read for three days or randomly restricting your account — you are in the right place.”
David Elliott “I researched the options and Fungies was the best fit for functionality and customisation within a store builder you can connect to your own domain. Taking a small percentage of sales, instead of charging a subscription for every environment and plugin, is refreshing.”
Elnura Abdimanap Kyzy “The platform is user-friendly, integrates easily with APIs and webhooks, and simplifies managing digital products and subscriptions. We were up and running quickly and support has been responsive throughout. Fungies is clearly tailored to the needs of SaaS businesses.”
Francisco Magnone Rienzi “Fungies has been a great partner — fast setup, competitive pricing, and real humans providing quick answers. They are constantly rolling out new features, and I am excited to see what is next.”
Payment questions from studios
Selling to players without a marketplace in the middle.
Take a test payment through it first
Build a product, open a checkout in sandbox, and watch the webhook arrive before you connect a payout account or ship anything to players.