Last updated
Lithuania Merchant Account for Non-Founders: Documents, Costs, and Timelines
Lithuania has an active banking, payments, e-money, and fintech market, but a merchant-account application still has to pass ordinary KYC, AML, ownership, authority, and business-model checks. If the person applying is not a founder or legal representative, the provider needs to understand why that person can speak for the company and who ultimately controls the business.
Do not treat a merchant account as a generic bank form. It is closer to a risk file: the provider is deciding whether it can process card or account-to-account payments for this merchant, whether settlement funds can be returned safely, and whether the stated activity matches company records, tax records, website claims, and customer flows.
Official source baseline
Use these official starting points before relying on provider blogs, forum answers, or old fintech onboarding checklists.
- Bank of Lithuania financial market participants
- Centre of Registers business services
- State Tax Inspectorate
What a non-founder must prove
The central question is authority. A founder or director may already appear in corporate records. A non-founder operator may be a finance manager, e-commerce lead, external consultant, accountant, employee, or agency. That person can often coordinate the file, but the provider still needs a bridge between the applicant and the Lithuanian company.
| Question | Why it matters | Evidence to keep ready |
|---|---|---|
| Who can bind the company? | The provider needs a valid contracting party. | Legal representative record, board authority, power of attorney, or signed mandate. |
| Who owns or controls the company? | Payment providers must understand beneficial ownership and control. | Shareholder list, UBO declaration, ownership chart, and parent-company documents. |
| Who operates the merchant activity? | The person answering onboarding questions must understand products, fulfilment, refunds, and customer support. | Role description, email domain, engagement letter, and internal approval to handle provider questions. |
| Where will funds settle? | Settlement must match the merchant and avoid unexplained third-party routing. | Business account in the company name or a documented settlement arrangement accepted by the provider. |
Document packet for a Lithuania merchant-account file
Prepare one evidence packet before opening several provider applications. Reusing a clear packet is faster than answering each provider in a different order.
| Document group | Examples | Delay prevented |
|---|---|---|
| Company record | Legal name, code, registered address, active status, representative details. | Provider cannot identify the merchant. |
| Tax and invoice evidence | Taxpayer details, VAT status where relevant, sample invoice, accounting contact. | Mismatch between checkout seller and tax/invoice issuer. |
| Authority file | Power of attorney, board approval, representative authorisation, applicant role. | Non-founder applicant appears unauthorised. |
| Business model | Product list, customer geography, average ticket, monthly volume, refund policy, fulfilment timing. | Risk team cannot price or approve the activity. |
| Website and descriptor | Domain ownership, legal pages, privacy/returns pages, billing descriptor, support channel. | Customer-facing merchant identity is unclear. |
| Funds flow | Settlement account, marketplaces, platforms, subscription billing, third-party processors. | Provider cannot understand where money goes after capture. |
Cost and timeline expectations
Public official sources rarely publish merchant-account prices because pricing is commercial. Treat published provider prices as offers, not rights. The costs that matter are usually setup fees, monthly minimums, transaction pricing, rolling reserve, chargeback fees, currency conversion, payout delay, refund handling, and integration work.
| Timeline stage | Fast case | Slow case |
|---|---|---|
| Initial review | A complete low-risk file may get a first answer in days. | Missing authority or unclear ownership can stall before underwriting starts. |
| KYC and UBO review | Straight Lithuanian ownership and one representative are easier to review. | Foreign parents, layered shareholders, nominee arrangements, or recent ownership changes need more evidence. |
| Website and product review | Clear terms, legal merchant identity, and delivery policy reduce back-and-forth. | Regulated goods, vague services, subscriptions, or high refund exposure trigger deeper checks. |
| Settlement activation | Business account and descriptor match the merchant. | Third-party settlement, new bank account, or name mismatch delays activation. |
Provider selection without over-optimising for price
A lower headline rate is not useful if the provider cannot support the merchant's real model. Compare provider type, regulated status, settlement currency, supported countries, reserve policy, chargeback operations, reporting exports, support quality, and ability to explain declined onboarding decisions. For a non-founder applicant, also ask whether the provider accepts delegated onboarding and what exact mandate language it expects.
Practical sequence
- Confirm the company record and legal representative before contacting providers.
- Create a one-page ownership and authority memo for the non-founder applicant.
- Check the provider type and regulated status through the Bank of Lithuania or the relevant home-country regulator.
- Align website legal pages, invoice issuer, settlement account, and customer support identity.
- Submit one complete packet instead of sending IDs first and explaining the business later.
- Track every provider question in a response log; repeated questions usually reveal the weak part of the file.