Armenische Zahlungslizenz, lokaler Partner oder Entwicklungs-Tochtergesellschaft: Wie ein Fintech-Unternehmen die richtige Wahl treffen sollte

A fintech needs its own Armenian licence, with AMD 100,000,000 in prudential capital (about USD 276,450), only if its Armenian company will itself transfer customers’ money or process and clear payments for Armenian customers. If a licensed Armenian organisation can carry those functions, a partnership is faster. If the Armenian company will only write and support code for a foreign group, a development subsidiary is the usual answer. Which of these fits depends on four facts about the business: who contracts with the payer, who holds the money, who settles, and what the Armenian staff actually do to live payment data.

Map the functions first

Armenian payment law regulates functions. The licence follows what an entity does with payment instructions and money, whatever the company calls itself in its pitch deck. Before choosing a structure, write down for each product and each market:

1. Verträge. Which legal entity signs with the payer, and which with the merchant or beneficiary.
2. Gelder fließen. Whose bank account the money passes through, even for a few hours, and on whose instruction it moves on.
3. Siedlung. Which entity calculates what each party is owed and which pays it out.
4. Information functions. Whether the Armenian team receives, validates, routes or approves payment instructions in production, or only builds and maintains the systems that do.
5. Stored value. Whether users can hold a balance that they later spend or withdraw.

The answers to items 2 and 5 usually decide the licence type. The answer to item 4 decides whether a development subsidiary can stay outside licensing.

Where the licensing line sits

The Law on Payment and Settlement Systems and Payment Organisations recognises two licences. An organisation may hold either or both. Both are issued for an unlimited term, and neither can be transferred, pledged or used by another company.

Money-transfer licence

Receiving money from a payer in order to pay it on to a beneficiary is a money-transfer function. Collecting card or account payments from customers and paying merchants out of that money falls here, even when the product is marketed as “merchant settlement”. A company that holds customer funds at any point in the chain should start from the assumption that this licence applies.

Processing and clearing licence

Processing covers receiving, processing and transmitting the information in payment documents, and in some cases identifying the parties, validating the payment instrument and approving the transfer. Clearing covers collecting, sorting and exchanging payment documents and calculating the parties’ positions. Final settlement is a separate step. Because processing is defined by what happens to payment information, a provider can need this licence without ever touching a customer’s money.

E-money and payment systems

Issuing electronic money requires a separate CBA permission, available to a non-bank organisation only if it already holds a money-transfer licence. A processing and clearing licence alone does not qualify. Operating a payment and settlement system in Armenia needs its own CBA Board permit, and participating in a foreign system generally needs CBA permission too. Banks are covered by their own regime.

CBA Regulations 17/01 (licensing procedure, managers, premises and systems), 17/02 (capital, liquidity and protection of customer funds) and 17/03 (reporting) apply to licensees. They are rulebooks for licence holders, and they do not create further licence categories. Regulation 17/02 was restated with effect from 1 September 2026, with new liquidity and customer-funds protection rules; the capital floor did not change. The application file, review stages and post-licence obligations are set out in our guide to the payment services licence in Armenia.

Two points remain unsettled: whether a non-bank payment organisation may independently acquire ordinary card payments, and how long and in what account structure a licensee may hold pooled customer funds. No current provision or CBA guidance on either was located in our research.

The four structures compared

Own licence

The applicant must be an Armenian legal entity registered before it applies; a branch of a foreign company does not qualify. Foreign ownership of the licensee is permitted, and no ownership ceiling specific to payment organisations was found. The capital is a prudential requirement measured on an ongoing basis, so it must be actually funded and maintained, separately from the charter capital stated at registration. A firm holding both licences pays AMD 2,000,000 a year in duty (about USD 5,530), plus AMD 50,000 (about USD 138) for each branch of a money-transfer organisation.

The CBA has two months from receipt of a complete file to decide, extendable by up to one month. If the file is incomplete, the CBA must say so within 30 days and the applicant has 10 days to cure it. The licence issues within three days of approval, and an applicant that has paid the duty is treated as licensed if the CBA does not refuse within the decision period. Company formation, capital funding, systems and hiring all come before the file is complete, so the two months cover only the CBA’s decision.

Lokaler Partner

A licensed Armenian organisation may outsource many functions, keeping responsibility for them, but the law prohibits it from delegating the payment and settlement services themselves. So the partner, and not the foreign fintech, must be the entity that receives and pays out the money and processes the instructions. Your company can supply the product, front end and technology. Changes to a licensee’s approved operating rules need CBA agreement, which can affect how quickly a partner can launch your product. No general mechanism was found for an unlicensed Armenian subsidiary to act as a licensed partner’s agent.

Development or support subsidiary

Our research found no payment-licence requirement for an Armenian company that only develops and supports software, with no customer contracts, no funds, no settlement and no live processing of payment instructions. That conclusion is drawn from the list of regulated activities; the law contains no express exemption for development companies, and whether a notification or supervisory duty arises when such a subsidiary works for an Armenian licensee is being confirmed. Where the subsidiary employs engineers, the usual Firmenregistrierung, Beschäftigung und Steuer Regeln gelten.

What an Armenian licence does not give you in the EU

Armenia is outside the EU, so a CBA licence cannot be passported into any EU state. Under the EU Payment Services Directive (PSD2), a payment institution licensed in one member state can passport across the EU, and the minimum initial capital for an institution providing money remittance only is EUR 20,000. Other payment services and e-money carry higher capital requirements. A group that needs both markets typically holds an EU authorisation for EU customers and uses Armenia for engineering, for Armenian customers, or both. The EU’s replacement package (PSD3 and the Payment Services Regulation) was still in negotiation in 2026, so EU comparisons here rest on PSD2.

Armenia’s own rules are also moving. A draft Law on Payment Services was published for public consultation from 9 to 26 October 2026. It is not law, and its commencement and transitional terms were not available when this article was written. Separately, payment organisations must now publish audited annual statements on their websites, and new CBA sanctions-evasion controls apply from 21 August 2026.

An illustrative walk-through

This example is hypothetical and simplified. A payments company licensed in an EU state wants 40 engineers in Yerevan and, later, Armenian merchants as customers.

1. Jahr eins. The Armenian company employs the engineers, builds the platform and provides second-line support under an intra-group services agreement. Production systems approving and routing live transactions are run by the EU entity. Payment licensing is not triggered on the research so far.
2. Armenian merchants arrive. The merchants’ customers pay in drams, and the merchants want next-day payouts. Collecting that money and paying it out is a money-transfer function. The company signs with a licensed Armenian payment organisation, which contracts with merchants and moves the funds, while the group supplies the technology.
3. Volumes grow. The group applies for its own money-transfer licence through the Armenian company, funds AMD 100,000,000 in capital, and moves merchant contracts across once licensed. If it adds wallets, it applies for the e-money permission next.

The step that most often goes wrong is in year one: if the Yerevan team starts operating the live transaction switch for Armenian payments, the subsidiary may be processing in the statutory sense before anyone has decided to apply.

Rote Flaggen

• “Software only” with a bank account. If the Armenian entity’s account receives customer money, even briefly, it is in money-transfer territory.
• Assuming no funds means no licence. Processing payment information is a licensed function on its own.
• A partner that offers its licence. A licence cannot be used by another company, and the payment and settlement services cannot be delegated. An arrangement that puts your entity in the money flow under the partner’s name is the risk you were trying to avoid.
• Treating two months as a launch date. It is the CBA’s decision period on a complete file, and it starts only when everything else is done.
• Planning EU sales from an Armenian licence. No passport exists.

The practical first step is the five-point functions map above, done per product and per market, before the company signs a partner contract or forms the Armenian entity. Related reading: payment gateways and fintech solutions in Armenia, payment processing in Armenia, Armenia’s licensing framework und unseren Bankdienstleistungen.

Häufig gestellte Fragen

Letzte Aktualisierung: 13. Oktober 2026