Tikkie QR

TypeQR Code

PrimaryNL

MentionedNL

Completeness86%high

Overview

Tikkie is the Netherlands' leading P2P payment-request app, developed by ABN AMRO and launched in 2016 [1, 2, nl-cro]. Despite being owned by a single Dutch bank, Tikkie works with all Dutch bank accounts — making it the de facto national P2P payment standard alongside ideal-qr's e-commerce dominance. By 2024, Tikkie processed 157 million payment requests worth €7.4 billion (+8 % YoY) with an average transaction of €47.28 and a rate of 5.3 Tikkies paid per second [nl-cro, 3].

Tikkie operates as a request-to-pay model: the recipient (creditor) generates a payment-request link or QR code, which the payer (debtor) opens / scans / receives via WhatsApp message integration (a structurally distinctive feature) [nl-cro, 1]. Settlement runs through the underlying ideal-qr / SCT Inst rail. No registration is required for payers — anyone with a Dutch bank account can pay a Tikkie just by clicking the link.

History

Background — Dutch P2P payment gap (pre-2016) [nl-cro, 1]:

Pre-Tikkie, Dutch P2P payments meant either bank-transfer with full IBAN-and-recipient-name entry (cumbersome) or cash.
ideal-qr (Currence, 2005) dominated online checkout but wasn't natively designed for P2P "send me 20 €" scenarios.
ABN AMRO recognised the gap and built Tikkie internally as an ABN-AMRO-developed-but-works-with-all-banks P2P-request product.

2016 — Tikkie launches [1, 2]:

ABN AMRO releases Tikkie as a standalone mobile app.
Initial proposition: send a payment request link to anyone via WhatsApp (Netherlands' dominant messaging app).
The recipient clicks the link → redirects to iDEAL → confirms payment in their bank app.
Universal Dutch bank-account compatibility from day 1 — not just ABN AMRO customers.

WhatsApp integration as the killer feature NL: Tikkie's structural innovation was leveraging WhatsApp as the share-the-link channel. Dutch consumers were already using WhatsApp for everyday communication; Tikkie made "send me a Tikkie via WhatsApp" the natural P2P payment pattern.

Subsequent evolution [nl-cro, 3]:

2017+ — Volume grew dramatically; Tikkie became cultural noun ("send me a Tikkie" entered Dutch vernacular).
2019+ — Tikkie-at-deposit-return-machines: Dutch supermarket bottle-return machines (statiegeld) integrated Tikkie QR for receiving deposit refunds.
2020+ — Schools, kiosks, public-event ticketing adopted Tikkie QR.
2024 — 157 million requests, €7.4 billion volume, average €47.28 per request.

Cumulative cultural status NL: Tikkie is one of the most successful single-bank-developed-but-cross-bank-used payment products in Europe — a structurally unusual outcome. Most peer national P2P payments are bank-consortium-owned (bizum Spain, mb-way-qr Portugal, blik Poland, swish-qr Sweden, twint Switzerland); Tikkie is ABN AMRO's product that works for everyone.

Technical specification

Tikkie's structural design is a request-to-pay layer atop existing Dutch bank infrastructure [nl-cro, 1]:

Layer	Description
Operator	ABN AMRO (Tikkie is an ABN AMRO product)
Universal compatibility	Works with all Dutch bank accounts (not just ABN AMRO)
Underlying payment rail	ideal-qr / SCT Inst via TIPS
Settlement	Real-time (sub-10-seconds, SCT Inst since 2019)
Currency	EUR
Per-request limit	€1,000
Payer registration	None required — anyone with a Dutch bank account can pay

Interaction modes [nl-cro, 1]:

Mode	Description
Payment request link	Recipient generates a link in Tikkie app; sends via WhatsApp / iMessage / email; payer opens link → iDEAL flow → confirms in their bank app
Payment request QR code	Recipient displays QR code (printed sticker or app screen); payer scans with phone camera → iDEAL flow
Recurring requests	Tikkie supports payment-request templates for recurring scenarios (e.g., monthly rent)

Distinctive feature — WhatsApp integration NL: Tikkie's "share via WhatsApp" flow is structurally important — most peer P2P apps require both parties to have the same app installed; Tikkie requires only the recipient to use Tikkie, with the payer simply clicking a link. This dramatically reduces network-effect barriers to onboarding.

Static Tikkie QR codes for deposit-return / retail scenarios NL:

Dutch supermarket statiegeld (bottle-return) machines display Tikkie QR — customers scan to receive deposit refund.
Schools display Tikkie QR for parent-payments.
Festivals and events use Tikkie QR for ticket sales.
The static-QR pattern works because every Dutch consumer has at least one bank account that supports iDEAL.

Use cases

Tikkie's deployment spans everyday Dutch P2P plus a unique retail/deposit-return ecosystem [nl-cro, 3]:

P2P transfers — the dominant use case. 5.3 Tikkies paid per second in 2024. Quintessential "split the bill" pattern.
Deposit-return refunds (statiegeld) — Dutch bottle-deposit machines at supermarkets use Tikkie QR to credit refunds to consumers.
School and event payments — parent-association fees, sports-club dues, festival tickets.
Small-merchant P2P-style payments — particularly informal vendors who haven't onboarded with ideal-qr or other merchant rails.
Friend-loan repayment — "I owe you €20 for dinner" → send Tikkie.
Donation collection — small-scale charitable / community fundraising.
WhatsApp-mediated commerce — buying second-hand items via Marktplaats / WhatsApp negotiation → Tikkie for payment.

Scale (2024) [nl-cro, 3]:

157 million requests (+8 % YoY)
€7.4 billion value
Average request: €47.28
5.3 Tikkies per second
All Dutch bank accounts can pay

Implementations

Tikkie integration is ABN AMRO-mediated — Tikkie's protocol is gated by ABN AMRO; consumer-facing access is via the Tikkie app + banking apps + WhatsApp NL.

Production apps consuming Tikkie:

Tikkie app — standalone iOS / Android app by ABN AMRO; the canonical Tikkie interface.
WhatsApp — payment-request links are commonly shared and opened in WhatsApp conversations.
Dutch bank apps — payers complete the iDEAL flow in their own bank's app (ING Mobiel Bankieren, Rabobank, ABN AMRO, Bunq, Knab, ASN, SNS, De Volksbank).

Acquirer / merchant integrations:

ABN AMRO directly for business Tikkie accounts.
Major Dutch PSPs (Adyen, Mollie, MultiSafepay) generally don't offer Tikkie as a checkout method — Tikkie is positioned as P2P / informal-merchant rather than e-commerce-checkout.

Open-source library scarcity — Tikkie's protocol is ABN AMRO-proprietary; no open-source library ecosystem.

Reference documentation [1, 3]:

Comparison

vs. ideal-qr (complementary, same country) — The defining peer relationship. iDEAL dominates e-commerce checkout (70 % Dutch e-commerce); Tikkie dominates P2P request-to-pay (5.3 per second). Both work with all Dutch bank accounts; both settle via SCT Inst. They are complementary, not competing: most Dutch consumers use iDEAL for online checkout and Tikkie for splitting the dinner bill, even though both are technically capable of either use case [ideal-ref, nl-cro].

vs. bizum (Spain), mb-way-qr (Portugal), blik (Poland), swish-qr (Sweden), twint (Switzerland) — Other European national P2P payment systems. Tikkie's structural distinction:

Owned by a single bank (ABN AMRO) — peers are bank-consortia or central-bank products.
WhatsApp integration is structurally central — peers focus more on standalone-app or in-bank-app flows.
Request-to-pay model with no-registration-for-payers — peers typically require app installation on both sides.

The result: Tikkie is the most informal, lowest-friction P2P payment of European peers — and consequently has high transaction velocity even at smaller individual transaction sizes (€47.28 average).

vs. wero (EPI's pan-European wallet) — Wero is being positioned to handle the P2P scenarios Tikkie currently dominates in the Netherlands. Unclear whether Tikkie will be absorbed into Wero or continue as ABN AMRO's separate product during the ideal-qr → Wero transition; the Wero-Netherlands rollout (2025-2027) primarily targets the iDEAL e-commerce-checkout use case rather than the Tikkie P2P-request use case [wero-ref].

vs. WhatsApp Pay / iMessage Pay — Tikkie's structural advantage over US-style messaging-app-embedded payments (WhatsApp Pay in Brazil/India, iMessage cash) is that Tikkie works with any Dutch bank account rather than requiring both parties to be on the same payment platform.

vs. PayPal / Venmo / Cash App — US-style P2P payment platforms typically require both parties to register on the same platform. Tikkie's no-registration-for-payers model is structurally more friction-free.

Fun facts

Tikkie became cultural noun in the Netherlands NL — "Stuur een Tikkie" ("send a Tikkie") is now the standard Dutch verbal expression for "send me a payment request," analogous to "Venmo me" in US English. Most successful national P2P payment systems become verbed: Bizum in Spain ("te bizumeo"), Swish in Sweden ("Swishar du mig?"), Tikkie in the Netherlands.

Tikkie is one of the most successful single-bank-developed-but-cross-bank-used payment products in European fintech history [nl-cro, 1]. The structural pattern — ABN AMRO built a product that works for every Dutch bank's customers, including its competitors' — is unusual. Most peer national P2P systems are owned by a bank consortium (so no single bank bears the development risk solo) or by a central bank / national payment infrastructure. ABN AMRO's willingness to invest in a cross-bank product is a notable strategic bet that paid off.

5.3 Tikkies paid per second in 2024 [nl-cro, 3] — among the highest per-capita P2P transaction rates of any European peer. With ~17 million Dutch population, that's roughly 1 Tikkie per Dutch resident per day, every day.

Tikkie's WhatsApp integration is the structural innovation that drove adoption NL — leveraging the existing WhatsApp installed base (essentially universal among Dutch smartphone users) for payment-request sharing eliminated the chicken-and-egg adoption problem most P2P apps face. Other markets have replicated this pattern (e.g., Splitwise internationally) but rarely with Tikkie's depth of national-bank integration.

Tikkie QR at supermarket deposit-return machines (statiegeld) NL is one of the most distinctive Tikkie use cases. The Dutch deposit-return system processes billions of bottles per year; Tikkie QR-mediated refunds are structurally important to consumer recycling participation. This blend of "consumer P2P payment app" and "national-infrastructure-grade-deposit-return-system" is unusual.

Status

Active, dominant in Dutch P2P, ABN-AMRO-owned [nl-cro, 3]:

157 million requests / year (2024) (+8 % YoY)
€7.4 billion value
Average €47.28 per request
5.3 Tikkies / second
All Dutch banks compatible
WhatsApp integration central to flow

Strategic context [nl-cro, wero-ref]:

iDEAL → Wero transition (2025-2027) primarily targets the iDEAL e-commerce-checkout use case; Tikkie's P2P niche is less directly affected.
ABN AMRO retains Tikkie ownership — no announced plan to fold Tikkie into Wero.
Continued growth — +8 % YoY in 2024 suggests Tikkie's market position remains strong.

Future considerations:

Whether Tikkie will eventually be integrated into Wero (alongside iDEAL) or remain as separate ABN AMRO product is not publicly announced.
Wero's roadmap includes P2P features that overlap Tikkie's territory, suggesting eventual consolidation pressure.

No deprecation planned. Tikkie is one of the most successful European P2P payment products and continues to grow.

Sources

Deployments

Found in the following country reports (grep across reports/countries/):

NL — NL-netherlands.md