概要
公開日: 2026-07-01
翻訳生成に失敗したため、原文をそのまま保存しています。
原文
This is a guest post from Roman Kuchařík - the co-founder of tapaya., a Prague-based startup building software-only SoftPOS infrastructure that turns any mobile device into a secure payment terminal. … Every team building a POS app eventually runs into the same problem: accepting in-person card payments. You can have a working product, merchants ready to test, and a clear roadmap, but the moment you add payments, things become significantly more complicated. Suddenly you are dealing with PCI requirements, EMV certifications, acquirer relationships, hardware dependencies, and long development cycles before anything is production ready. At Tapaya, we believe this process should be much simpler. So we decided to test how quickly we could build a real Expo-based POS application and add in-store card payments using our own SDK. The result: from idea to first approved payment took less than an afternoon! This post explains: - what inspired the app - what we built - and exactly how we integrated card payments into an Expo app Tapaya app What inspired the app idea? The original idea was simple. We wanted to build a lightweight POS system for one of our favorite local coffee shops, something fast, minimal, and easy to use on a regular phone instead of traditional payment hardware. Most small merchants do not want to manage separate terminals, cables, charging docks, and multiple systems just to accept payments. They want a single device that can: - manage products - handle transactions - onboard merchants - accept tap to pay card payments instantly We also wanted to test a broader question internally: Could a developer build a production ready SoftPOS experience in Expo without spending months on payment infrastructure? That became the experiment. And we had an incredible opportunity to take on this experiment at a Hackathon in Prague hosted by STRV and Expo! Prague Hackathon What app did we build? We built a simple cross platform POS application using Expo. Cafe app The app included: - a product inventory screen - a checkout flow - transaction history - merchant onboarding (KYB) - in-person tap to pay card acceptance The goal was not to build a complex enterprise POS system. The goal was to create a clean functional prototype that demonstrated how quickly modern payment infrastructure can be integrated into a React Native application. By the end of the afternoon, the app could: - onboard a merchant - authenticate with the Tapaya platform - accept contactless card payments - process approved sandbox transactions directly on an NFC enabled iPhone or Android device No external payment terminal required. Why we chose Expo Before building the app, we evaluated several frameworks and workflows. We ultimately chose Expo because it dramatically simplified the native mobile setup required for payments. Expo Config Plugins simplified Native SDK setup By adding a single config plugin to app.json and running expo prebuild, the native iOS and Android bindings were generated automatically. No manual Swift or Kotlin setup was required. EAS Build simplified iOS Tap to Pay entitlements Setting up Apple Tap to Pay manually can become complicated quickly. Expo’s Services handled much of the provisioning and entitlement workflow for us. EAS Update improved iteration speed We could push UI and logic updates rapidly without repeatedly waiting for App Store review cycles during testing. Expo Router accelerated development We built screens for: - Sales - Transactions - KYB onboarding - Settings The process required very little boilerplate. Tapaya’s SDK was built for Expo The integration worked exactly as expected with Expo’s config plugin system, which made the setup surprisingly smooth. Here’s how we built the app: We started by building the core POS interface in Expo during the morning: - simple inventory management - checkout screen - transaction handling Once the UI flow was working, we moved on to adding in-person payments. To speed up development, we p