No enterprise tier. The same platform, at volume.
Enterprise normally signals a quote, a procurement cycle, and features held behind both. We do not work that way: one rate, every feature included, and an integration you can finish without speaking to anybody. What a larger digital business actually needs is depth in the API, webhooks that behave under load, reconciliation that ties out, and one integration that holds in every market. So that is what this page covers, along with what we do not offer.
What volume actually asks for
- An API over the whole object graph
- Products, offers, orders, payments, subscriptions, users, discounts, checkout elements and webhooks, over REST at api.fungies.io/v0. One object per request, rate limited, HTTPS only, with public keys for reads and secret keys for writes.
- Webhooks you can build a ledger on
- Every delivery is signed with HMAC-SHA256, retried up to five times, and recorded in a delivery history you can inspect attempt by attempt. Events carry an idempotency key, and the documentation states which ones can race each other rather than leaving you to find out in production.
- Reconciliation that separates the numbers
- Each order carries its value, the tax collected and the commission taken, so gross, tax, fee and net are four figures rather than one derived guess. Transaction reports sit in the dashboard, and the same records are readable through the API and the CLI on whatever schedule your finance systems want.
- Many markets on one integration
- Over 250 payment methods presented by the buyer's country and currency, customers anywhere in the world, and a single settlement stream into your own connected account across over 110 supported countries. Adding a market is configuration, not a project.
- Access split along sensible lines
- A workspace holds multiple team members, and API credentials separate reading from writing: the public key can survive being in a build, the secret key stays on your server, and the two rotate independently. A valid key without the right permission is refused rather than partially honoured.
- A rehearsal path
- Full sandbox mode, a test-mode flag on every event, and a synthetic test event you can fire at a live endpoint. You can walk the whole flow, including the failures, before anything real depends on it.
How an evaluation usually runs
- 01
Read the reference and fire a test event
The API and webhook documentation are public. The quickest honest read on the integration is to send a synthetic event at a staging endpoint and look at what arrives.
- 02
Run the flow in the sandbox
A purchase, a renewal, a plan change, a declined charge and a refund, without a real card. This is where integration surprises surface, and it costs nothing to find them here.
- 03
Prove reconciliation in one market first
Take live orders in a single market and tie the dashboard's gross, tax, fee and net back to your own ledger before you widen anything.
- 04
Open the rest of the markets
Payment methods, currencies, localisation and tax for a new country are platform behaviour rather than new code. The integration you already built is the one that serves them.
Being straight about what we are not
There is no published tier ladder
The standard rate is 5% + 50¢ per successful transaction, with no monthly fee, no minimum and no annual commitment, and it is negotiable at volume — but there is no table of thresholds to plan against, so you have to ask. Even then, at high volume a directly negotiated processing rate plus your own tax vendor and the staff to run it can work out lower as a percentage. It is also a considerably larger thing to operate, so compare total cost with the headcount included.
There is no account manager or signed SLA
Support runs through email and a Discord community, and the terms are the published ones rather than a document your legal team redlines. If a contractual service level is a hard requirement, we would rather you knew that now than after an integration.
We are the seller, which is a decision for finance and legal
As Merchant of Record the customer's contract is with us and our name is on the invoice — that is precisely what removes the tax, fraud and chargeback burden. If your buyers sign agreements with your company, or their procurement requires you as the contracting party, this model is the wrong shape for that revenue.
What does scale well here
No tiers to outgrow, no per-seat pricing, no caps on products, plans or volume, and no separate line item for compliance. Entering another twenty markets adds tax work on our side and configuration on yours, not a bigger contract.
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.”
Questions from larger teams
Comparisons and the questions larger teams ask.
Judge it from the API reference, not a sales call
Generate a test key, run the full flow through the sandbox, and reconcile one live market before you move anything else across.