SOFTPOS01 / 04
SDK inside your merchant app
SoftPOS is the PCI MPoC SDK and platform banks and PSPs embed inside their own Android merchant apps. The institution owns the brand experience; Firisbe operates the certified backbone.
ABOUT FIRISBE
Payment infrastructure built from YTU Technopark
Founded in 2022 at Yildiz Technical University Technopark, Firisbe builds white-label payment infrastructure for banks, PSPs, acquirers, e-money institutions, and fintech teams.
MISSION AND VISION
A payment team, not a sales wrapper
Firisbe focuses on infrastructure that survives certification, procurement, integration, and production operations.
Mission
Make modern payment products easier to launch without weakening compliance, risk, or operational control.
Vision
Become the trusted white-label infrastructure layer for global payment ecosystems.
Technopark base
Operate from Yildiz Technical University Technopark with an engineering-first culture.
Certification mindset
Treat PCI, audit evidence, and regulated operations as product requirements.
Modular build
Compose Payment Hub, Tap2Mobile SoftPOS, JetEMV, Open Banking, and Digital Wallet around the roadmap.
Global ambition
Build for local regulatory depth and international expansion from the same platform discipline.
WHAT WE OPERATE
Different product surfaces, one certified operating model
The user-facing layer changes by program. The PCI boundary, telemetry, audit cadence, and operator console stay consistent.
TAP2MOBILE02 / 04
Ready app for SMB merchants
Tap2Mobile is the Android acceptance app SMB merchants download, onboard into, and use without extra POS hardware. It can be white-labeled or published under a bank or PSP brand.
ORCHESTRATION03 / 04
Routing across providers
Payment orchestration routes traffic, applies fallback rules, exposes provider health, and keeps reconciliation evidence visible for support, risk, and finance teams.
CARD PROGRAMS04 / 04
Certified card controls
Card personalization infrastructure supports EMV production, physical and virtual card programs, wallet provisioning, and issuer-grade control records.
COMPANY FACTS
Small enough to engineer closely, serious enough for regulated launches
Use these facts as the page anchor; detailed commercial and certification evidence belongs in the first technical review.
FoundedStarted at Yildiz Technical University Technopark
Technopark officeDavutpasa Campus, Istanbul
Product linesPayment Hub, Tap2Mobile, JetEMV, Open Banking, Digital Wallet
Operating focusWhite-label regulated payment infrastructure
WORKING MODEL
How we move from scope to production ownership
The process keeps commercial, engineering, certification, and operations decisions in the same conversation from day one.
Map the boundary
Define the product surface, customer owner, acquirer path, scheme requirements, data flows, and PCI responsibilities.
Open controlled access
Provide sandbox credentials, SDK/API references, test cards, webhook examples, and a named technical contact.
Prove live paths
Run a measured pilot with real transactions, known merchants, support flows, and reconciliation checkpoints.
Transfer controls
Set operator access, alert rules, incident paths, release gates, reporting, and evidence ownership before rollout.
Operate audit cycles
Keep service data, change records, QSA material, and expansion plans current after the first production month.
Map the boundary
Define the product surface, customer owner, acquirer path, scheme requirements, data flows, and PCI responsibilities.
Open controlled access
Provide sandbox credentials, SDK/API references, test cards, webhook examples, and a named technical contact.
Prove live paths
Run a measured pilot with real transactions, known merchants, support flows, and reconciliation checkpoints.
Transfer controls
Set operator access, alert rules, incident paths, release gates, reporting, and evidence ownership before rollout.
Operate audit cycles
Keep service data, change records, QSA material, and expansion plans current after the first production month.
POSITIONING
Infrastructure partner, not merchant SaaS
This distinction keeps product ownership, procurement review, and certification scope aligned before integration starts.
Criterion
Firisbe
Not Firisbe
Primary customer
Banks, PSPs, acquirers
Direct merchant SaaS
SoftPOS model
SDK / platform embedded by institutions
Merchant download app
Tap2Mobile model
Ready app merchants can use
SDK banks embed
Certification scope
Operated inside Firisbe controls
Rebuilt per project
After launch
Monitoring and incident ownership
Delivery handoff
Commercial posture
Partner to regulated teams
Competes for merchants
Primary customer
Firisbe
Banks, PSPs, acquirers
Not Firisbe
Direct merchant SaaS
SoftPOS model
Firisbe
SDK / platform embedded by institutions
Not Firisbe
Merchant download app
Tap2Mobile model
Firisbe
Ready app merchants can use
Not Firisbe
SDK banks embed
Certification scope
Firisbe
Operated inside Firisbe controls
Not Firisbe
Rebuilt per project
After launch
Firisbe
Monitoring and incident ownership
Not Firisbe
Delivery handoff
Commercial posture
Firisbe
Partner to regulated teams
Not Firisbe
Competes for merchants
FAQ
Questions teams ask before they engage
Short answers for product, engineering, compliance, and procurement teams.
WORK WITH US
Scope a regulated payment program with Firisbe
Bring a product surface, market, or operating problem. A Firisbe payment engineer will map the integration boundary, certification scope, and first pilot path.