Banking for Online Dating Platforms: Why Subscription Businesses Get Flagged — and What Actually Helps
2026-10-01
A Legal Business That Still Reads as "High Risk"
Running a dating app or a subscription-based dating site is an ordinary, legal business. Millions of people pay for premium features every month, and the model is well understood. Yet founders in this space often find that opening a business account or getting card payments approved is harder than it is for almost any other kind of consumer app.
It's rarely about one thing. It's a mix of how the industry is categorised, how people pay for it, and what can go wrong on a platform where strangers meet. Understanding those three pieces makes it much easier to present the business in a way a reviewer can actually say yes to.
The Category Code Problem
Every business that accepts cards is assigned a merchant category code, or MCC. For dating, that code is 7273, and its official label is "Dating and Escort Services."
That single line explains a lot. A mainstream matchmaking app and an escort agency sit in the same category, so any risk policy written for one is applied to the other by default. An automated onboarding system sees 7273 and reacts to the category, not to the actual product.
This is where a lot of declines come from. Nothing in the business itself was assessed. The code simply landed in a bucket the provider had already decided to avoid.
Recurring Billing and the "I Don't Recognise This Charge" Dispute
Most dating platforms earn through subscriptions, often starting with a discounted first month or a free trial. It's a good model for the business and a common source of chargebacks.
The pattern is familiar. A user signs up, forgets about it, and three months later sees an unfamiliar name on their card statement. Instead of cancelling, they dispute the charge. Some users also dispute charges out of embarrassment, when a partner or family member asks what the payment was for.
Card schemes monitor chargeback ratios and escalate merchants whose ratios cross set thresholds, so a steady trickle of these disputes can become a real problem. Banks and acquirers know this, which is why they ask detailed questions about billing before they look at anything else:
- How clearly is the recurring price shown at checkout? - Does the user get a reminder before a trial turns into a paid plan? - How easy is it to cancel, and how many clicks does it take? - Does the billing descriptor on the card statement match the brand users actually know?
A platform with good answers to these questions looks very different from one that doesn't, even with the same MCC.
Scams, Refunds and Reputation: What Reviewers Actually Worry About
The second concern has less to do with payments and more to do with the platform itself. Romance scams are a well-known problem across the industry, and any provider supporting a dating business wants to know it isn't indirectly supporting fraud.
In practice, reviewers tend to look at a few things:
- Moderation. Is there a process for detecting fake profiles and reporting abuse, and who runs it? - Age checks. Dating is an adults-only service, so there should be a clear way of keeping minors out. - Money between users. Platforms that let users send each other gifts, credits or money raise more questions than those where money only goes from user to platform. - Refund policy. A written, reasonable policy that support staff actually follow lowers disputes and shows the business takes complaints seriously.
None of this is unusual for a well-run platform. The problem is that it often isn't written down anywhere a reviewer can see it.
What a Dating Platform Needs From Its Banking Setup
Payment acceptance gets most of the attention, but the everyday banking side matters just as much. A typical dating business deals with:
- Incoming payouts from payment providers and app stores, often in more than one currency. - Outgoing payments to developers, moderators, marketing agencies and ad networks, many of them in other countries. - Separate flows by market, when the same app runs in several regions with local pricing.
That's why a multi-currency IBAN account with both SEPA and SWIFT is often more useful to a dating company than a pure payment gateway. Revenue can arrive in the currency it was earned in, and suppliers can be paid over the rail that suits them.
How Polydirection Looks at Dating Businesses
Dating is one of the four industries Polydirection names directly on its homepage, next to crypto, gambling and forex, under the heading "Industries other providers route around — reviewed individually."
In practical terms, that means a few things. Applications are read by people rather than filtered out by category code alone. Dating businesses get a dedicated manager, which the homepage describes as "not a form letter decline." The Business account itself is a multi-currency IBAN for SEPA and SWIFT transfers, with Mastercard settlement for supported accounts.
Card acquiring is a separate question. Polydirection lists it as available on request, "for selected business cases — individually assessed," so it isn't automatically part of every account. And as the company's Individual Solutions page puts it, "There is no guaranteed outcome for every non-standard request, but every case gets a real review from a real person, not an automatic rejection."
What to Have Ready Before You Apply
The list below isn't an official Polydirection checklist. It's what tends to make any review of a dating business faster and smoother:
- A short description of the product and revenue model: subscriptions, one-off purchases, credits, or a mix. - Screenshots of the checkout and cancellation flow, including how trials and renewals are disclosed. - Your billing descriptor and an example of how the charge appears on a card statement. - Refund and complaints policy, as it's actually applied. - Moderation and age-verification approach, in plain language. - Processing history, if you've accepted cards before, including chargeback levels. - Company structure and countries involved: where the company is registered, who owns it, where the users and suppliers are.
The goal is simple. Show the reviewer the business behind the category code. Once they can see how the platform actually runs, 7273 stops being the whole story.
