Skip to content
In-store payments infrastructure

Any device is now a payment terminal.

Commerce moved to software — but taking payments in person still means buying hardware, wiring up acquirers, and a year of certification. Tapaya puts the whole in-store payments stack in one SDK, so your product accepts tap-to-pay on any phone, tablet, or kiosk — under your own brand.

In-person payments are ~6× bigger than online — and now they fit in a few lines of code.

Backed by

  • Passion Capital
  • Depo Ventures
  • BADideas.fund
  • €1M pre-seed
The problem

In-person payments are brutally hard to build

In-person payments are roughly 6× bigger than online — yet the tooling for software builders never caught up. Doing it yourself still means hardware, acquirers, and a year of certification.

A year-plus to certify

Card-network and device certification drags on — and hundreds of thousands of euros — before a single tap goes through.

  1. Acquirer contractsweeks
  2. KYB & onboardingweeks
  3. PCI DSS audit~2 mo
  4. Network certification6–9 mo
  5. Device certification3–6 mo
  6. Re-certify per marketagain

18–24months

+ hundreds of thousands of € — before a single tap goes through.

A new maze each market

A different acquirer, scheme, and compliance regime in every country — rebuilt and re-certified as you expand.

Tapaya collapses all of it into one SDK

Networks, acquirers, compliance and certification — pre-integrated. You ship product; we run the rails underneath.

See how it works
checkout.ts
import { Tapaya } from "@tapaya/sdk";
await tapaya.payments.start({ amount: 13.50 });

Tap to pay · €13.50

Approved

~30 min to your first in-person payment

Locked to the hardware

Every terminal is a purchase, a logistics chain, and a fleet to maintain — tying your product to one device and one vendor.

Terminal

€13.50

Tap to pay
1234567890

Months, not minutes

A year-plus of certification before a single live transaction.

Hundreds of thousands €

Hardware, acquirer contracts, and audits — all paid upfront.

A payments team

Engineers maintaining rails and re-certifications, not your product.

How it works

One SDK. Any device. Live in 30 minutes.

Accepting payments should be as simple as turning on a light.

  1. Step 1: Sign up & get API keys

    Create an account and grab your keys. No hardware to order, no contracts to wait on — start in the sandbox right away.

  2. Step 2: Drop in the SDK

    Embed the SDK into your phone, tablet, or kiosk app. Your UI, your brand — customers never see Tapaya.

  3. Step 3: Accept payments

    Tap to pay, live. Card networks, acquirer connections, and compliance come pre-integrated underneath.

Deploy anywhere

If it runs Android or iOS, it takes payments.

Any commercial phone, tablet, kiosk or enterprise/ERP device — not locked to one ecosystem or hardware vendor.

The Tapaya checkout on an iPhone showing a contactless tap, beside an Android phone showing a QR / SEPA payment
  • PhoneApple & Google devices
  • TabletCountertop POS
  • KioskSelf-serve & unattended
  • ERP / enterprisePurpose-built hardware
Your brand, not ours

Customers never see Tapaya.

The SDK's payment UI is themed to your product, end to end — your brand, your flow, our rails underneath.

The platform

Everything handled, under one SDK

The hard, regulated parts of in-person payments — networks, acquirers, compliance, certification — come pre-integrated. You ship product; we run the infrastructure underneath.

The Tapaya partner dashboard at platform.tapaya.com — total revenue, upcoming payout, a gross-volume chart, and payment-method and device-OS breakdowns

Card networks

Accept all major card networks out of the box.

Alternative payment methods

Wallets and local APMs your customers already use.

Account-to-account

Direct A2A payments, settled straight to the bank.

Acquirer connections

Pre-wired acquirer links — no contracts to chase.

Online KYB & onboarding

Verify and activate merchants in a single flow.

PCI & compliance

Security and regulatory obligations handled for you.

Certification

Network and device certification carried by us.

Analytics

Transaction insight and reporting, ready to embed.

Multi-market

One integration that scales across regions.

For developers

Stripe-for-in-person — in a few lines of code.

Initialize the SDK, start a payment, done. Sandbox keys, native SDKs, and docs from day one.

  • Kotlin
  • Swift
  • Expo
  • Java
  • iOS
  • Android
SPMgithub.com/tapayadot/accept-ios
Checkout.swiftSandbox
import Accept

// Initialize + authenticate (sandbox)
try await Accept.initialize(demo: true)
try await Accept.authenticate(merchantToken: merchantToken)

// Turn this device into a terminal
let intent = AcceptCardPaymentIntent(
    amount: 4250,                  // €42.50, minor units
    requestedCurrency: .eur,
    settlementCurrency: .eur
)
let outcome = try await Accept.pay(intent)

switch outcome {
case .completed(let status):
    showReceipt(status.paymentToken)
case .canceled:
    promptRetry()
}
Who it's for

Built for the software companies reinventing commerce

From a single counter to thousands of devices across markets — if your product takes payments in person, Tapaya fits the way you already ship.

  • Restaurant & hospitality POS
  • Retail
  • Field services
  • Events & pop-ups
  • Marketplaces
  • Vertical SaaS
  • Banks & fintechs
  • Kiosks & ERP
Why us

We spent years inside the 18-month certification grind — so you don't have to.

The team has built and certified payment products before. We're focusing on the hardest part — physical payments — so you can ship on top of it.

Mastercard Lighthouse — 2026 selected company in the Baltics

“We want accepting payments to be as simple as turning on a light.”

Laura Ďorďová, CEO
  • Recognized by the networks

    Winners of awards from both Mastercard and Visa — recognition straight from the card networks themselves.

  • Built and certified before

    The founding team has shipped and certified payment products — we know the maze because we have walked it.

  • Backed to go deep

    €1M pre-seed from Passion Capital, Depo Ventures, and BADideas.fund to focus on the hardest part: physical payments.

FAQ

Questions, answered

From the blog

Latest writing

Product updates and field notes from the team building in-store payments infrastructure.

Early access

Payments, handled. Now build.

One SDK, your brand, live in ~30 minutes. Tell us what you’re building and we’ll get you started.