Instant Payments in Lithuania: From T+2 Cards to A2A Seconds

The source data for this reference guide contains no Lithuanian instant-payment figures, no rail comparisons, and no policy numbers. That absence is itself the most important fact: the public case for the upcoming mandate rests on a structural argument, not on a data sheet.

The argument is simple. When a customer pays by card, the money moves as an instruction that can be reversed. The merchant waits for settlement, and the customer keeps a refund button. When a customer sends an instant account-to-account payment, the money arrives with finality. There is no button to press afterward.

The mandate does not need to replace cards. It reclassifies them. Cards are the rail for transactions that may need to be taken back; instant payments are the rail for transactions that must be certain. The difference is not speed, though speed is how people notice it. The difference is who owns the risk once the money is gone.

From T+2 Cards to A2A Seconds

A chip tap in Vilnius returns an approval in under a second, yet the merchant’s account is not funded until the T+2 business-day settlement clock finishes. That mismatch is the baseline for Lithuania’s upcoming instant-payment decision: the speed you feel at the terminal is not the speed the merchant gets paid.

On the card rail, a chip or mobile-wallet tap on a Visa/Mastercard terminal in Lithuania is authorized in under a second, but the acquirer batches the day’s transactions and credits the merchant on a T+2 business-day schedule. That T+2 clock is the default, and it still applies even when the payer used a phone.

SEPA Instant is a different clearing species. Under the EPC’s SCT Inst scheme, the payer’s PSP must send and the payee’s PSP must credit the beneficiary within seconds, around the clock, in central-bank money rather than an interbank IOU. That central-bank settlement makes the speed real, not just an updated ledger entry.

The European infrastructure carrying these transfers is split between two competing rails: EBA CLEARING’s RT1, a live pan-European instant clearing house, and the ECB’s TIPS, a live RTGS-style instant settlement service. A Lithuanian bank routes through the Bank of Lithuania’s Eurosystem connection to one of these, which is why the instant window holds even on weekends and bank holidays.

Mechanically, an instant transfer is a push transaction. The payer authorizes in a banking app or an open-banking app; the bank debits the account and sends a standardized payment message; and the payee PSP must make the funds available before the prescribed window closes, or the payment is rejected. There is no pull from the merchant and no chargeback attached to that push.

Two things that look like new rails are really wrappers. Tokenized wallets such as Apple Pay and Google Pay substitute a device token for the PAN and add biometrics, but the underlying Visa/Mastercard settlement remains on the T+2 card clock. Open-banking payment-initiation providers such as Tink and TrueLayer sit on top of SEPA Instant as consent/API layers; they add authentication and merchant-account data, but the actual settlement is still the same SCT Inst route.

Dispute risk, not settlement speed, should decide the rail. Faster rails should not simply replace cards, because instant rails remove the card dispute window — faster means riskier for a payer who later needs recourse. If the payer may need a refund or a dispute right, the card rail’s chargeback still matters, and the T+2 wait is the price of that right. If no chargeback is needed, SEPA Instant gives final payment in seconds in central-bank money.

Before you pay in Lithuania, ask: will I ever need a chargeback on this payment? If yes, use a card or a card-tokenized wallet. If no, use SEPA Instant and take the immediate finality.

The Mandate's Evidence

According to an impact assessment from the European Commission, only a minority of euro-area credit transfers were instant at that point. That fact should change how you read Lithuania’s payment market under the mandate: the current status of mandatory instant payments is a legislated default, not a spontaneous market shift. Consumers and merchants did not organically migrate to SEPA Instant before the law forced the issue; the regulator had to create the default.

The Instant Payments Regulation is the binding clock. Every euro-area payment service provider was required to be reachable to receive instant payments and to be able to send them. By calendar arithmetic, the first full year under that obligation applies to every Lithuanian PSP. That sequencing matters for anyone building on these rails: there was no graceful adoption curve left to manage, only hard legal deadlines that have already passed.

The same regulation removes the economic reason for the old bank-transfer habit. It bans a discriminatory fee: an instant transfer may not cost the payer more than a standard SEPA credit transfer. That fee cap eliminates the price premium that had kept consumers and corporate payers on the T+2 habit. After the ban, the slower route does not even win on cost; what remains is inertia, not rational price-sensitive choice.

Speed, however, is bounded by a value ceiling. The SCT Inst scheme rulebook caps one transaction at a set maximum; any amount above that still has to travel on the T2/standard SEPA transfer route, so the speed promise is true only under the cap. That value cap matters more than the speed SLA for product decisions. A treasury or wallet team building Lithuanian payment logic must make an explicit product decision at the cap before any instruction reaches the instant layer: split the payment into amounts below the cap, or accept the fallback to the slower route. The cap, not the settlement timer, is the first design constraint.

If you read the mandate as proof that faster rails should replace cards, you are reading the wrong document. The mandate delivered reachability, fee parity, and a value ceiling. It did not deliver a chargeback right. The evidentiary record therefore points to the same decision rule: use SEPA Instant only when no recourse is needed, and keep card rails whenever the payer might need the dispute window that this mandate did not create.

Finality, Chargeback, or Both

Under the Instant Payments Regulation — fully applicable in Lithuania — a euro account-to-account push settles in seconds, and banks may not price it above a standard SEPA transfer. That speed is real, and it is the wrong default for most purchases. The settlement clock and the dispute clock run on different calendars: the rails that fund the merchant fastest are precisely the rails that give the payer no post-send remedy.

The matrix below is the whole decision in one view. It compares the five realistic ways a Lithuanian payer can move euro value under the mandate: SEPA Instant, card rails, open-banking PIS over SEPA Instant, tokenized mobile wallets, and crypto stablecoin wallets such as USDC on Solana.

On speed and payer cost, SEPA Instant wins cleanly. The payer pays no premium over a standard bank transfer, and the payee holds funds immediately — no T+2 wait. The crypto row does not win on cost or anything else: the network fee and exchange spread are variable, and a USDC wallet on Solana offers no EU-regulatory accountability, no IBAN integration, and no PSD2-style recovery mechanism if the payment lands at the wrong address or a fraudulent counterparty.

On protection, card rails win — and not marginally. A cardholder has a contract with the issuer and a dispute process that can force a chargeback for goods that never arrive, services not rendered, or a merchant that fails. SEPA Instant gives the payee finality and the payer a receipt; there is no "goods not received" or "counterfeit item" remedy on the SEPA scheme. Finality for the payee is the payer's risk.

Open-banking PIS sits exactly between the two. It executes through SEPA Instant and adds a consent and strong-customer-authentication layer, but it adds no buyer protection. It wins only for B2B suppliers who have already pre-verified the invoice and the IBAN — the authentication proves who authorized the push, not that the invoice will be fulfilled.

That makes the overall winner conditional. Use card rails whenever the payment involves a purchase that could fail: physical goods, online services, marketplace sellers. Use SEPA Instant for person-to-person transfers, bill splits, landlords under a signed lease, and verified single-payer invoices. A dinner split in Vilnius is a SEPA Instant payment; a marketplace SSD is a card payment. The dividing line is not settlement speed — it is who bears the failure risk after the money moves.

The myth that faster rails should replace cards inverts this. Instant rails remove the card dispute window, so for a buyer who might later need a refund, faster is more dangerous, not better. Speed is a feature of the rail; finality is a feature of the legal relationship. The correct rail is decided by dispute risk — never by the clock alone.

What the Data Hides

Revolut's Lithuanian user sees a transfer land in seconds, but that clock includes the app's internal risk engine, core-banking write, and notification pipeline — none of which the SEPA Instant SLA measures. The stated speed obligation applies at the clearing infrastructure level: the time between the sending PSP submitting the message and the receiving PSP making funds available. Everything before submission (app authentication, fraud scoring, AML filters, internal ledger holds) and everything after (posting, reconciliation, push notification) runs on the institution's own clock. So the seconds a Lithuanian consumer observes inside Revolut or Paysera is a lower bound on real-world latency, not a uniform statistic; one bank's test payment may clear in a couple of seconds, another's may consume most of the SLA at the infrastructure layer plus several more inside the core ledger.

The speed statistics also ignore authorized push payment (APP) fraud. Once a payer confirms a SEPA Instant transfer, there is no chargeback right under that rail, and no card-network rule forces the receiving bank to return the funds. If a Lithuanian consumer is tricked into confirming a payment, the loss moves permanently to the payer unless the bank voluntarily chooses to compensate. That is exactly when the canonical rule bites: choose card rails whenever the payer may need recourse, because the card dispute window is the only enforceable clawback. Faster is not safer; it is simply faster, and the missing dispute window is a risk premium, not an efficiency gain.

The headline "T+2 to seconds" applies to the average small-value transfer, not the value-weighted flow. The rail's value cap keeps large B2B and invoice payments on T2 or standard SEPA, so the euro value outside the cap remains on the legacy clock. A Lithuanian wholesaler paying a supplier's invoice above the cap gets no speed benefit from the regulation, even though the published statistics look dramatic.

Regulatory cost data cannot show hidden bundled fees. Banks may charge the same amount for instant and standard transfers instead of lowering the standard price, so a "free" instant credit transfer is often a package-account feature priced elsewhere. The line-item comparison understates the true cost of choosing the rail.

Card networks have responded with their own instant push-payout rails, so the card row's T+2 default is not immutable. Merchant acquirers can buy same-day or real-time funding, which narrows the speed gap. The decision matrix must therefore compare the chosen product — standard funding vs. real-time funding — rather than the brand rail.

Finally, there is no public corridor-by-corridor latency table from the clearing operators for Lithuania. The published number is a maximum, not a median, so bank-to-bank variance inside Lithuania sits outside the official statistics. A merchant's actual experience depends on its acquiring bank's processing stack, which no regulator publishes.

Worked Case

On a Tuesday morning, a customer at Aido Knygos, a Vilnius bookseller, buys a book bundle on a debit card. The card network authorizes in under a second — but the acquirer batches the transaction and credits the merchant's account on Thursday, which is T+2 in business days. The same customer, choosing "Pay by bank" in an open-banking checkout, would move the payment from Luminor to Swedbank through a pan-European instant settlement hub and have it final and spendable moments later. Speed is the headline, but it is the wrong decision variable. The right rail is chosen by dispute risk, not speed.

Under the EU Interchange Fee Regulation, the debit-card interchange on that transaction is capped at a small percentage; the credit-card version is capped at a slightly higher percentage. Scheme and acquirer fees are added on top of those caps, so the merchant absorbs more than the interchange alone before the T+2 payout lands. The bank route strips those costs out: no interchange, no settlement batch, and a flat initiation fee — or nothing when the business account bundles instant payments.

If the books never arrive, the cardholder can initiate a chargeback for the full amount on either card rail. A SEPA Instant push cannot be clawed back by the payer; it is final by design. So the merchant's cash-flow difference between the rails is measured in cents and calendar days, while the buyer's difference is measured in the entire purchase amount. The buyer's loss is the meaningful number. A merchant who sells on card rails pays at least the capped interchange, plus scheme and acquirer fees, and waits until Thursday. A merchant who sells on SEPA Instant gets finality the same minute, at a flat fee or nothing. But the buyer who paid by card carries a dispute right; the buyer who paid by bank carries none.

This is why the fashionable conclusion — that faster rails should simply replace cards — inverts the actual trade-off. An instant rail removes the card dispute window, so "faster" is more risky for a buyer who may later need a refund. Apply the decision rule before payment: will the payer ever need a chargeback? If yes, use a card or a card-tokenized mobile wallet. If no, use SEPA Instant. The winner is not the faster rail; it is the rail whose risk profile matches the context.

Five Rules

Pay a person you already know — a friend, a freelancer, a landlord — with SEPA Instant in your banking app, once the IBAN has been confirmed on a second channel. One channel is the message; the second is a voice call or a signed contract. For a Kaunas-based freelancer you have worked with before, no chargeback right is needed because the relationship is the enforcement mechanism — you settle disputes by talking, not by reversing a bank. Paying by card would drag the money through a T+2 settlement cycle and incur acquiring costs for protection you cannot use.

Pay any merchant for physical goods or services with a major-brand debit or credit card, or a card-tokenized mobile wallet like Google Wallet or Apple Pay. The reason is not approval speed; it is the dispute window that follows. The card scheme's chargeback process lets your issuer force a reversal if goods never arrive or the service is defective. SEPA Instant has no equivalent: a push is an instruction you authorized, and afterward your bank can only tell you the funds are gone. For physical goods, the chargeback is the only cheap consumer protection left after the purchase, and it is why card rails survive the instant mandate.

A merchant should show the card as the default checkout rail and offer instant bank transfer only as an explicitly irreversible, lower-fee alternative for verified customers or B2B payments. Defaulting consumer goods to instant A2A transfers the buyer's fraud risk to the buyer, and buyers cannot price that risk. A button that reads "Instant bank transfer — irreversible, no chargeback" turns a fee-saving tactic into a consent decision. Verified repeat customers and B2B payables can rationally accept finality in exchange for a lower fee.

Never use SEPA Instant for a first-time marketplace purchase, a classifieds deal, an auction payment, or a PayPal friends-and-family-style transfer. These are the authorized-push-payment fraud patterns that instant finality makes unrecoverable: a Skelbiu.lt seller demands a push to "hold" an item, the buyer sends the funds, and both vanish within the hour. Your bank executed your instruction and has nothing to reverse; a card route puts the merchant-acquirer relationship between you and the fraudster. Every push is a gift until it is a gift to a stranger.

For any single payment above the single-transaction cap, or where the beneficiary must pre-validate ownership, leave the instant rail and use the T2/standard SEPA route — never trust an IBAN shared by phone. A push that lands in the wrong account is a serious recovery problem. The IBAN-name verification field is the final gate: it compares the beneficiary name against the account's registered name and catches the fraudster who texts an IBAN that does not match the person you mean to pay. Read it; in doubt, send a small test payment first — T2 leaves room to cancel.

Frequently Asked Questions

If I tap my Visa card in Vilnius, when does the merchant's account actually get funded?

A chip or mobile-wallet tap on a Visa/Mastercard terminal in Lithuania is authorized in under a second, but the acquirer batches the day's transactions and credits the merchant on a T+2 business-day schedule.

Can a SEPA Instant payment be reversed with a chargeback if something goes wrong?

No, an instant transfer is a push transaction; there is no pull from the merchant and no chargeback attached to that push.

What happens to an instant payment above the SEPA Instant value cap?

Any amount above the SCT Inst scheme cap still has to travel on the T2/standard SEPA transfer route, so a treasury or wallet team must decide at the cap whether to split the payment into amounts below it or accept the slower fallback.

Can Lithuanian banks charge a fee for instant transfers that is higher than standard SEPA credit transfers?

No, the Instant Payments Regulation bans a discriminatory fee: an instant transfer may not cost the payer more than a standard SEPA credit transfer.

Do Apple Pay and Google Pay payments in Lithuania settle on SEPA Instant?

No, tokenized wallets such as Apple Pay and Google Pay substitute a device token for the PAN and add biometrics, but the underlying Visa/Mastercard settlement remains on the T+2 card clock.

What did the European Commission's impact assessment say about the adoption of instant credit transfers before the mandate?

According to an impact assessment from the European Commission, only a minority of euro-area credit transfers were instant at that point.

Quick answers

Sources: Flyertalk, Frequentmiler, Frequentmiler, Thepointsguy, Thepointsguy

Also worth reading: 2026 Fraud Split and Decision Matrix: Keyed vs Tokenized: 2026 Fraud Split and Decision · 2026 Visa Fee Hike: Break-Even Up, Small Merchants Route to PayTo: 2026 Visa Fee Hike: Break-Even · 2026 EU 10-Second Settlement: Merchants Face New Fraud-Liability: 2026 EU 10-Second Settlement: Merchants