Getting Paid in Romania in 2026: The Practical Map

A Romanian SRL with eight clients does not need a payments stack. It needs a bank account, one way to take cards, and a rule about what goes in the payment reference. The hard part is not accepting the money. It is knowing, three weeks later, which invoice the money belonged to, and doing that again for every client, every month, without a spreadsheet that only one person understands.

We have set this up for our own studio and for clients, and the pattern is always the same: checkout takes an afternoon, reconciliation takes the rest of the year. This is the map we wish we had at the start.

The set of options is small enough to list

A Romanian small business can collect money in five ways: a domestic bank transfer in lei, a card payment through a Romanian processor, a card payment through Stripe, a payment link attached to an invoice, and a SEPA transfer in euro from outside the country. Almost everything else is a variation on one of these. That is good news, because a short list can be understood completely, and most of the decisions are about administration rather than technology.

Fees below were read on the providers' own pages on 22 October 2026 and are linked where they appear. They change, and the rate you are offered depends on volume and risk. Treat them as the shape of the market, not as your price.

Bank transfer, and the bill that arrives later

For business-to-business work in Romania, a bank transfer in lei is still the default, and usually the cheapest way to be paid. Receiving one is cheap or free at most banks, and unlike a card payment it does not come back weeks later as a chargeback. The cost is not at the bank. It is in the matching.

The failure modes are boring and repeatable:

• the client pays without a reference, so the statement shows a company name and an amount;
• the reference is a proforma number, an invoice number, or a contract number, depending on who at the client pays it;
• one payment covers three invoices, or half of one;
• the payer is a different legal entity from the client, often the parent company or the founder's personal account;
• the amount is short by the transfer fee, because the sender chose to share the cost.

None of these is a bank problem and none of them is solved by a better dashboard. They are solved by deciding, before the first invoice, that every invoice carries a unique payment reference and that no payment is matched automatically on amount alone. A unique reference turns the statement into a join key. Matching on amount turns it into a guess, and the guess is wrong exactly when two clients owe similar sums, which is every month.

Keep an unmatched queue with an owner and a weekly review. Money that arrived and has not been explained is not revenue yet; it is a question. The queue is the cheapest control you will build, and it is the one that catches the payment from the client's accountant with no reference at all.

Card processors a Romanian company can sign with

Three local names come up in every conversation: EuPlătesc, Netopia Payments and PayU Romania. All three are established, all three require a contract and a verified business, and they differ mainly in how they price and how much integration work they leave to you.

EuPlătesc publishes a starting point of "de la 1,2%" per transaction, described on the page as indicative, with the final rate set after a discussion and depending on the type of activity and risk. The same page offers a negotiable rate once monthly processed volume passes 500,000 RON, which tells you the published number is a floor for small merchants rather than a price list.

Netopia does not publish a rate at all. Its page describes online registration and an electronic contract, and shows Visa and Mastercard acceptance, but no percentage, no setup fee and no monthly fee. The same is true of PayU Romania, whose site talks about reducing international and currency-conversion costs without printing a number. With both, you have to ask for a quote, and the quote is the beginning of a negotiation rather than a published fact.

That absence is worth noticing. When a provider does not publish a price, the price depends on you: your volume, your average ticket, your chargeback history, the industry code on your contract. For a small merchant the difference between two quotes can be larger than the difference between the published rates of the providers that do publish.

What Stripe actually requires

Stripe is available to businesses in Romania. The supported-countries list includes Romania without a preview or invite label, and registration uses the standard flow with the country set to RO. Its Romanian pricing page states 1.5% + 1.00 lei for standard European Economic Area consumer cards, 2.8% + 1.00 lei for premium EEA cards, 2.5% + 1.00 lei for UK cards and 3.15% + 1.00 lei for other international cards, with an additional 2% when currency conversion is required. There are no setup or monthly fees on standard pricing.

What it requires in practice is a business, not a personal account: legal name, address, tax identifier, a bank account that matches the business, and a beneficial-owner declaration for the people who own it. Stripe performs know-your-customer checks on all of that, and its documentation is explicit that once a service is activated on a live account you cannot change the business origin country; you would open a new account instead. Plan the entity before the integration, not after.

For a studio billing European clients, Stripe's advantage is not the rate. It is that cards, payment links, invoices and SEPA direct debit sit behind one integration and one export, and the export is the thing your reconciliation actually consumes.

Payment links, invoices and the reference that survives

Most small businesses do not need a checkout page. A payment link is a hosted page you can send by email or put in a PDF, with no website involved, and Stripe prices the optional post-payment invoice at 0.4% of the transaction, capped at 2.00 lei per invoice; a custom domain is US$10 per month. Invoicing tools do the same job from the other side: SmartBill, for example, starts at 5,84 EUR per month plus VAT for invoicing and lists card-payment integration as a feature of its plans. We are naming these as examples of the mechanism, not recommending a stack.

The design rule matters more than the tool. One link per invoice, not one link per client. The invoice number travels in the payment metadata and in the reference field, and the same string appears in your ledger. When the payment lands, the reference is the only thing that connects a bank line to an invoice, a client and a month.

SEPA, EUR and the currency question

Romania is inside the geographical scope of the SEPA schemes, as the European Payments Council's country list shows, and Romanian payment schemes have existed for lei since 2012, with an instant variant since 2019, according to the Romanian Banking Association. In practice a euro invoice to a German client is an ordinary SEPA credit transfer: an IBAN, a BIC where the bank still wants one, and a reference.

Two things trip people up. First, the currency of the invoice and the currency of the account are not always the same, and the difference is a real cost that somebody bears. Decide in the contract who pays the conversion and at which rate; if you invoice in euro and receive in lei, the rate on the day the money arrives is the one that matters, not the one on the invoice. Second, SEPA direct debit is not instant money. Stripe supports it for Romanian accounts but presents in euro only, settles around six business days after submission, and the customer's bank can return a debit within eight weeks without giving a reason, or up to thirteen months if the debit was unauthorised. Do not spend a direct debit before it has settled.

Where e-Factura meets reconciliation

Romania's e-invoicing system creates a second stream that has nothing to do with the first. The invoice goes to ANAF through RO e-Factura within the legal deadline; the money goes through the bank whenever the client decides to pay. Neither system knows about the other. The invoice XML does not confirm that anyone paid, and the bank statement does not know which invoice it is settling. The rules and deadlines are covered in our guide to e-Factura; what matters here is the join.

Your own reference is that join, and it has to be chosen before either stream starts. Put it in the invoice, in the payment details your client copies into their bank, and in the ledger entry. Then a daily job can read the statement, match on the reference, and mark the invoice as paid. Everything it cannot match goes to the queue a human reviews. The e-Factura submission status is a separate column: an invoice can be accepted by ANAF and still be unpaid, and it can be paid before the XML is even sent.

A boring setup that works

This is what we would build for a ten-person company billing Romanian and European clients:

• Bank transfer in lei as the default, with a unique reference on every invoice and a proforma that carries it too.
• One card processor, chosen on the quote, the settlement time and the export format rather than the headline percentage.
• Stripe for international clients, because the same account handles cards, links, invoices and SEPA in one place.
• Payment links on the invoice, one per invoice, so the client does not have to type an IBAN.
• A daily statement import that matches on the reference and writes an unmatched queue for everything else.
• A monthly check that the sum of the ledger equals the bank balance, with a named person who signs it off.

None of that is sophisticated. It is the difference between a business that knows what it is owed and one that finds out at the end of the quarter.

What we would not do

We would not reconcile by amount. We would not build card capture ourselves, because the compliance surface is larger than the feature. We would not take client money into a personal account, even briefly, because it makes the bookkeeping and the tax position worse in ways that are hard to undo. And we would not let a client pay "whenever, however" without a reference, because every exception costs more to resolve than the fee it avoided.