Georgia sits at a crossroads of European ambition and pragmatic regulation. A payment institution operating without the right licence in this market risks enforcement action, frozen correspondent relationships and a banking stack that collapses when it is needed most. The question for any digital-asset business eyeing Georgian rails is not whether to licence – it is how to structure the licensing and banking layers so that the fiat side of the operation holds.
Payment institution licensing in Georgia is governed by the National Bank of Georgia (NBG), which supervises payment services under the country's payments legislation and its implementing regulations. The regime requires any entity providing payment services commercially – including money transfer, account-based payment services and the issuance of payment instruments – to hold an NBG-issued licence. For businesses combining crypto activity with fiat settlement, this intersects directly with the country's approach to virtual asset service providers, creating a dual-layer compliance requirement that inbound operators frequently underestimate.
This page sets out the regulated perimeter, the application process, the cross-border interaction with tax and banking, and the practical decision points for businesses weighing Georgia as a payment infrastructure base.
Who needs a payment institution licence in Georgia?
Any business providing payment services to third parties on a commercial basis in Georgia requires authorisation from the National Bank of Georgia unless an explicit statutory exemption applies. The regulated perimeter covers account-based payment services, payment initiation, money remittance and the issuance and acquisition of payment instruments. Operating outside that perimeter – or relying on a foreign licence without a Georgian establishment – creates regulatory exposure that counterparty banks will price into their risk assessments.
The practical trigger for most inbound digital-asset businesses is not the crypto activity itself but the fiat leg: the moment a business holds or moves client funds in Georgian lari or any other currency on behalf of customers, it is almost certainly inside the payment services perimeter. In our practice, operators who set up a Georgian legal entity for tax or structuring reasons, and then begin processing client settlements through that entity, discover the licensing obligation later than they should.
The NBG also supervises virtual asset service providers (VASPs) – entities that exchange, transfer or provide custody of virtual assets. Where a business combines both payment services and VASP activity, two separate regulatory tracks apply. A payment institution licence alone does not authorise VASP activity, and vice versa. That distinction shapes the entire entity design decision for a crypto-adjacent payments business.
What does the Georgian payment regime actually license?
The NBG payment services regime distinguishes between payment institutions and e-money institutions, each carrying different activity permissions and capital expectations. Payment institutions are authorised to execute payment transactions; e-money institutions may additionally issue electronic money and are subject to requirements around float management and redemption. The choice between the two licence categories drives the structural design of the product.
For a crypto exchange or custody business building a fiat on-ramp, the e-money institution route is typically more relevant: it allows the entity to issue stored value, hold balances on behalf of clients and move those balances through the Georgian banking system. A pure payment institution, by contrast, executes transactions without maintaining client balances in a stored-value form – a narrower permission set that suits acquiring or remittance-focused operators.
The NBG's approach to authorisation is function-based. The regulator looks at what the applicant actually does in the market, not how it labels its product. Businesses that describe their service as a "crypto wallet" but hold fiat on behalf of users sit squarely inside the e-money perimeter. Operators we advise are consistently surprised by how quickly the functional analysis reaches that conclusion.
How does the application process work, and how long does it take?
The NBG payment institution application follows a documented submission process: the applicant submits a complete application package, the NBG conducts a fitness-and-propriety review of controllers and senior management, assesses the governance and AML programme, and issues a licence decision. Timelines vary by complexity and the completeness of the initial submission; in our experience, well-prepared applications at comparable regulators in the region typically progress over a period of several months, though the NBG's own processing windows should be confirmed with current legislation at the time of application.
The documentation burden is substantial. The NBG typically requires: a detailed business plan with projected payment volumes; an organisational chart showing beneficial ownership to the natural-person level; governance and internal control policies; an AML/CFT programme that meets FATF standards; evidence of minimum capital adequacy; IT system descriptions; and draft customer contracts and terms. For businesses with a crypto dimension, the AML/CFT documentation must address the specific risks of virtual-asset flows – many initial applications fail or are delayed because the submitted programme treats crypto customers identically to conventional payment clients.
A common mistake at this stage is submitting a programme written for a different jurisdiction. Georgian AML law reflects FATF Recommendation 15 obligations for virtual assets, and the NBG expects a programme calibrated to local requirements, not a repurposed EU document. Regulators read the gap between the two quickly.
The process above describes the standard path. Your facts – the entity structure, the user base, the banking relationships – change the analysis significantly. To map the right licensing approach for your build before you submit, contact OBOLUS at info@oboluslaw.com.
What are the AML and Travel Rule obligations for a Georgian payment institution?
Georgian AML/CFT obligations for licensed payment institutions are anchored in national legislation that implements FATF standards, including the Travel Rule – the obligation to pass originator and beneficiary identification data alongside a payment or virtual-asset transfer. For a payment institution that also operates as a VASP, the Travel Rule applies to virtual-asset transfers above the applicable threshold, requiring the institution to collect, verify and transmit the required data to the counterpart institution at the receiving end.
In practice, the Travel Rule creates an infrastructure problem for smaller operators. The institution must be able to send and receive Travel Rule data in a compatible format with counterpart institutions globally. Where the counterpart institution is not Travel Rule-compliant – a common situation in emerging-market correspondent chains – the Georgian institution must have a documented policy for managing the gap. The NBG will assess that policy as part of both the initial authorisation and ongoing supervision.
Customer due diligence expectations are tiered. The NBG applies enhanced due diligence requirements to higher-risk customers, including those dealing in virtual assets, politically exposed persons and cross-border transfers above specified thresholds. Businesses that combine payment institution status with VASP activity carry a compounded AML risk profile that the NBG assesses separately from conventional payment operators.
How does Georgian payment institution licensing interact with tax and banking across borders?
Georgia's territorial tax system is one of the primary commercial attractions for international operators. A Georgian-registered company that earns income from foreign sources and does not distribute those earnings in Georgia generally benefits from a low effective tax rate under the Estonian-model profit tax that Georgia adopted. For a payment institution, this interacts favourably with a business model that processes international payment flows: the Georgian entity earns processing fees, retains them within the corporate structure and is taxed only on distribution. Operators should, however, apply the substance rules carefully – the NBG licence creates a substantive local operation requirement that satisfies most substance tests, but the tax analysis must be reviewed jurisdiction by jurisdiction for the full group structure.
Banking is the harder problem. Georgian commercial banks – the principal correspondent relationships for any licensed payment institution – apply their own AML and crypto-risk policies independently of the NBG licence. Holding a valid payment institution licence does not guarantee a bank account. In our practice, we regularly advise clients who have obtained a Georgian licence but find the commercial banking step blocked by a bank's internal crypto-sector policy. The solution is pre-application engagement with prospective banking partners, ideally before the regulatory application is filed, so that the business plan and AML programme are calibrated to satisfy both the regulator and the bank simultaneously.
For businesses with a cross-border group structure – for example, a Georgian payment institution sitting alongside a MiCA-licensed entity in the EU or a VARA-licensed entity in Dubai – the interaction between payment rails, custody layers and the tax treatment of inter-entity flows requires a coordinated analysis. A Georgian payment institution does not benefit from EU passporting; it operates in the Georgian domestic and correspondent-banking system. Businesses that need EU retail access will require a separate CASP authorisation under MiCA in a member state, with the Georgian entity functioning as the settlement or processing layer rather than the point of consumer contact.
A cross-border payment licensing matter
In a recent structuring matter, a payments company with a token-based remittance product sought to establish a Georgian payment institution as the fiat settlement layer for a multi-jurisdiction stack. The group held a DPT licence in Singapore under the Monetary Authority of Singapore (MAS) Payment Services Act framework and was planning a VARA authorisation in Dubai. We identified that the Georgian entity's proposed activity – holding client balances in lari pending crypto-to-fiat settlement – placed it within the e-money institution perimeter rather than the narrower payment institution category. The AML programme had been drafted for the Singapore entity and required a full rebuild to address Georgian requirements and the NBG's virtual-asset risk expectations. We restructured the programme, mapped the Travel Rule data flows between the three entities and engaged the prospective Georgian banking partner before submission. The application was filed with a coherent group-wide AML narrative. The banking relationship was confirmed ahead of licence issuance.
Which operators should seriously consider a Georgian payment institution licence?
The Georgian payment institution regime suits a specific operator profile. Understanding that profile prevents misallocated structuring effort.
Profile A – the regional fiat-on-ramp operator. A business that needs a regulated fiat settlement layer for CIS and Caucasus markets, combined with a favourable tax environment, finds Georgia well-positioned. The Georgian payment institution licence provides regulated status, a functional banking relationship with local commercial banks and access to SWIFT correspondent chains. Timeline to operational readiness runs from several months to over a year depending on the complexity of the AML programme and the bank onboarding process. The principal risk is the banking step – not the licence itself.
Profile B – the EU-facing crypto operator seeking a low-cost processing layer. This profile faces a structural mismatch. The Georgian licence does not passport into the EU. A business that needs to serve EU retail clients through a Georgian entity will encounter both regulatory and banking friction. The better structure in this scenario places the EU consumer-facing activity under a MiCA CASP authorisation and uses Georgia for back-office processing or treasury functions only.
Profile C – the fund or institutional operator moving large volumes between jurisdictions. Georgia can function as a processing and settlement layer for institutional flows where the counterparties are themselves licensed. The territorial tax system is attractive for fee income. The primary due-diligence question is whether the Georgian commercial banking system can support the required correspondent chains at the required volume – an operational question that must be answered before, not after, the licence application.
A common assumption is that a single offshore licence is sufficient to serve clients globally. It is not. Each jurisdiction where a payment institution's services are received by end-users is a potential licensing trigger in its own right. Georgia provides regulated status within the Georgian and regional correspondent-banking environment. Operators who present a Georgian licence to EU or UK regulators as a substitute for local authorisation will find it does not serve that purpose.
If a prior application stalled or your banking relationship was refused, a second read of the group structure frequently surfaces the issue. Contact OBOLUS at info@oboluslaw.com to map the route forward.
Self-assessment: are you ready to apply?
Before filing a Georgian payment institution application, an operator should be able to answer the following questions affirmatively.
- Is the Georgian entity legally incorporated, with a registered address and at least one local director or responsible officer?
- Does the business plan accurately describe the payment flows, the customer base and the role of any crypto activity in the service model?
- Has a Georgian-law AML/CFT programme been prepared – not adapted from a foreign template – with specific procedures for virtual-asset customers if applicable?
- Has a prospective banking partner confirmed in principle that it will provide a settlement account to the entity?
- Are the beneficial ownership and control structures documented and clear, including any holding entities in other jurisdictions?
- Has the group structure been reviewed for the interaction between the Georgian entity's activity and licensing requirements in the jurisdictions where customers are located?
An application that reaches the NBG without positive answers to all of the above will encounter a request for further information at best, and a substantive objection to the application at worst. We map the licence stack across operating, custody and payment layers before our clients commit to the process.
Related at OBOLUS
- Banking, payments and EMI onboarding for digital-asset businesses – end-to-end guidance on acquiring and maintaining fiat rails for crypto operators.
- PSP and acquiring agreements in Hong Kong – how payment service provider relationships are structured under the SFC and HKMA frameworks.
- Crypto regulation and licensing in Switzerland – FINMA's token taxonomy and the licensing routes available to Swiss-based digital-asset businesses.
FAQ
Why do banks close crypto company accounts?
Banks close crypto company accounts primarily for two reasons: an undisclosed or inadequately documented crypto activity that triggers a compliance flag on review, and a bank-wide sector policy that excludes virtual-asset businesses regardless of licensing status. A Georgian payment institution licence mitigates the first problem but not the second. The most reliable approach is to engage prospective banking partners during the licence application process, presenting the AML programme and business plan together, so the bank's internal compliance team approves the relationship before the licence is issued rather than after.
How can a VASP onboard with an EMI?
A VASP (virtual asset service provider) seeking to onboard with an e-money institution should expect enhanced due diligence from the outset. The EMI will review the VASP's own licensing status, its AML programme, its Travel Rule compliance infrastructure and its transaction monitoring capability. Preparation of a structured onboarding pack – covering corporate structure, regulatory status, AML policies and recent audit or assessment outputs – materially reduces the time the EMI needs to complete its review and increases the probability of a successful outcome.
What does client-money safeguarding require?
Client-money safeguarding for a licensed payment institution requires the institution to hold client funds in a manner that keeps them separate from the institution's own funds – typically through a designated safeguarding account at a credit institution or through coverage by an eligible guarantee scheme. The specific safeguarding method and the operational requirements around reconciliation, shortfall management and record-keeping are set by the applicable national legislation and the NBG's supervisory expectations. Failure to meet safeguarding requirements is among the most common grounds for supervisory action against licensed payment institutions.
OBOLUS is an independent digital-asset law boutique acting only for businesses. We advise exchanges, custodians, token issuers and funds on licensing across 70+ jurisdictions, on disputes and on-chain asset recovery across 25+ forums, and on the tax, banking and compliance that sit around them. Digital assets are the whole of our practice. We map the licence, banking and tax stack across operating, custody and payment layers before our clients commit to a structure – and we work alongside forensic partners to convert on-chain evidence into court-ready disclosure applications when recovery is required. To discuss your situation, contact info@oboluslaw.com.
By Victor Olsen, Regulatory & Compliance Analyst – specialising in payment institution and VASP licensing for cross-border digital-asset businesses, including inbound operators structuring Georgian, EU and regional fiat-rail arrangements.
This publication is general information about the law and does not constitute legal advice. It is not a substitute for advice tailored to your circumstances. OBOLUS accepts no liability for action taken or not taken on the basis of this material. For advice on your situation, contact info@oboluslaw.com.