Rent Collection in Poland for MamNajem¶
Executive recommendation¶
MamNajem should keep Stripe in the stack, but not make Stripe Connect-powered embedded rent collection the default Polish MVP. The strongest reason is not that Stripe is bad; it is that Polish rent collection is a scheduled, contract-driven workflow where low fees, direct bank settlement, and proof of payment matter more than an e-commerce-style checkout uplift, while the best-performing Polish online methods are BLIK and bank redirects rather than cards. BLIK is now enormous in Poland, with 2.9 billion transactions in 2025, and Stripe itself describes BLIK as Poland’s largest payment method with more than 65% e-commerce share; Stripe also notes that Przelewy24 aggregates bank-based Polish methods and that bank transfers account for a large share of Polish online payments. citeturn36search6turn6search5turn6search6
For the Polish MVP, the least risky move is to launch off-ledger rent management: payment requests, landlord IBAN, due dates, receipts/proof upload, automatic reminders, landlord confirmation, and audit logs. If embedded collection is validated later, MamNajem should add one Polish PSP rather than switch the whole platform, with PayU as the first PSP to evaluate for a future landlord-seller / marketplace model, because its public marketplace materials explicitly mention seller verification via API and broad local payment coverage; Tpay is a strong technical second choice, but its public marketplace docs currently list a narrower payment-method set in marketplace mode; Przelewy24 is attractive if you want a simpler local gateway, but its open-web marketplace detail is less transparent than PayU’s and Tpay’s. citeturn38view1turn38view2turn28view3turn20view1
The shortest direct answer is this: keep Stripe overall, add a Polish PSP later if rent collection proves valuable, do not launch full embedded rent collection now, and use payment requests plus bank-transfer proof for the MVP. That path minimizes regulatory exposure, engineering cost, support burden, and dispute/refund complexity while still fitting Polish user behavior. citeturn35search0turn35search4turn35search17turn34search0
How Polish rent collection differs from normal checkout¶
Residential rent in Poland is not a typical retail purchase. Lease arrangements are monthly, scheduled, and contractual, and Polish legal guidance on lease terms treats the payment method as a contract term that should be specified, with bank transfer and cash both treated as normal options; an institutional University of Warsaw rental template uses a monthly bank transfer model. That matters because landlords are usually optimizing for predictable due-date behavior, evidence, and direct settlement, not for the same type of conversion optimization that matters in e-commerce checkout. citeturn37search6turn37search17
If MamNajem does embed payment in Poland, the local UX leader is clearly BLIK, not cards. BLIK’s standard online flow is well understood: the tenant enters a six-digit code from a banking app and confirms the payment in-bank; Stripe says approval usually happens in under 10 seconds, and BLIK says users can shop with it in almost every online store in Poland. Meanwhile, the broader BLIK network remains heavily e-commerce-centric, with e-commerce still its strongest channel in 2025. citeturn5view0turn36search2turn36search6
That does not mean BLIK alone solves rent collection. BLIK is a payment method, not a complete landlord-payout stack. In practice, you still need an acquirer/PSP or platform product to accept it, reconcile it, refund it, and route funds to landlords. The decision therefore is not “Stripe versus BLIK.” It is closer to “which PSP stack gives MamNajem the right mix of BLIK, bank redirects, refunds, landlord onboarding, and compliance for Poland?” Public provider documentation shows BLIK being exposed through Stripe, PayU, Tpay, and Przelewy24-related stacks, which reinforces that point. citeturn40search0turn11view3turn32search4turn20view1
A second implication is that cards should not be the default mental model for Polish rent. Cards are still useful, especially for foreign tenants and for recurring authorization models, but they bring chargebacks/disputes, 3DS/SCA flows, and often higher effective support overhead. In contrast, bank-authenticated local methods such as Przelewy24 bank redirects and BLIK typically have lower fraud / “unrecognized payment” dispute risk than cards. citeturn40search1turn40search15turn13search0turn13search7
Provider and model comparison¶
| Option | Poland tenant UX | Public cost signal | Settlement, refunds, disputes | Payout and legal complexity | MVP implementation cost for MamNajem | Evidence |
|---|---|---|---|---|---|---|
| Stripe Connect | Good global UX, but local Poland fit is strongest only if MamNajem actively exposes BLIK and/or P24 rather than defaulting to cards. | Stripe publicly lists Polish local-method pricing such as BLIK 1.6% + €0.25 and Przelewy24 2.2% + €0.25 on its local-method pricing page; Polish card pricing is also published separately. | Strong API/webhook maturity. P24 on Stripe supports refunds up to 180 days and no dispute/chargeback process. BLIK on Stripe supports refunds and disputes, but recurring BLIK is constrained: not all banks support it, and off-session recurring BLIK is capped at 2000 PLN. Stripe says first live payouts typically start 7–14 days after first successful payments. | Connect is powerful, but platforms using separate charges and transfers are debited for Stripe fees, refunds, and chargebacks, which is a material risk transfer. Good if you truly need platform money movement; heavy if you do not. | Low incremental engineering cost because MamNajem already has Stripe/Connect/webhook pieces, but medium-to-high product/legal cost if used for Polish rent collection from day one. | citeturn7search12turn7search2turn7search1turn5view1turn5view2turn5view3turn40search0turn40search1turn40search15turn6search0 |
| PayU | Very strong local fit: PayU markets BLIK, bank transfers, cards, Google Pay/Apple Pay, plus recurring cards and BLIK in selected contexts. | Public SMB price page shows 1.1% + 0.30 PLN for bank transfers, BLIK, and cards, with 29 PLN activation; public legal fee tables also show a 0.20 PLN processing cost and BLIK scheme fees, so the headline offer is not the full commercial picture. | Refund APIs are mature; PayU says refunds are fully supported and public terms say refunds are processed on the next working day after merchant order. Card chargeback exposure is real, and PayU’s materials explicitly say merchants can remain financially liable for fraudulent card chargebacks where transactions were processed without SCA. Exact payout timing appears commercial-sheet / contract dependent, though the product messaging emphasizes configurable settlement and direct transfer to the merchant account. | Best-visible local marketplace story among the Polish PSPs reviewed: PayU publicly says it can verify seller documentation and expose that via API. That materially lowers landlord onboarding friction if you later move to landlord-as-seller/submerchant. | Medium-to-high. New integration, new commercial onboarding, new reconciliation logic. But it is the best add-later Polish PSP candidate if you need marketplace-style seller onboarding and local method coverage. | citeturn11view0turn11view1turn11view2turn11view3turn14view0turn15view0turn12search14turn12search11turn13search7turn13search8turn38view1turn38view2turn39search9 |
| Przelewy24 | Excellent local familiarity for BLIK, online transfers, cards, Apple Pay/Google Pay. Good fit for a “pay now” Polish consumer flow. | Clear public pricing: 1.29% + 0.30 PLN for online transfer, BLIK, standard cards, and wallets; refund handling 0 PLN; first four PLN payouts monthly are free, then 0.99 PLN each. | Public help says bank-transfer/BLIK refunds reach customers within up to 3 business days, while card refunds can take 7 business days to 30 calendar days. Card chargebacks exist; P24 publishes chargeback guidance and its terms allocate chargeback-related burdens to merchants. Payouts are configurable in the panel, including date-based / amount-based schedules, and P24 says immediate payout can be enabled. | Good local gateway economics, but the open-web marketplace/public API evidence is thinner than PayU’s and Tpay’s. P24 clearly advertises marketplace, recurring payments, and technical docs, but its open technical detail was less transparent in the pages reviewed. | Medium if you use it as a local gateway later; higher if you need a robust platform payout model and landlord KYC workflows. | citeturn20view1turn20view2turn24search0turn24search13turn21search1turn21search2turn21search18turn19search0turn19search6turn19search12turn22view0 |
| Tpay | Strong Polish UX for BLIK and PayByLink; good overall gateway. Public marketplace docs are unusually readable. | Package pricing is explicit: Starter from 1.59% + 0.39 PLN, Business from 0.99% plus 99 PLN monthly service fee; BLIK recurring in Business shows 0.99% + 0.02 PLN. Public fees also show 120 PLN per chargeback. | Strong webhook and refund docs. Refunds require merchant balance to cover refund plus fee; Tpay publishes full and partial refund flows. General payment terms say funds are transferred to the merchant account within up to 3 business days after instruction in PLN. Card tokenization is well documented for recurring charges, and Tpay documents 3DS handling explicitly. | The big caveat is marketplace mode: public marketplace docs say it requires Partner Program membership and a dedicated agreement, and the documented payment methods in that marketplace mode are BLIK, online transfer, installments, and BNPL. Cards are not listed there, which can be acceptable for Polish-local rent but is limiting for coverage. | Medium-to-high. Technically credible, but commercial onboarding for marketplace mode is heavier than the generic gateway implies. Very good second-choice PSP for a later Poland-specific pilot. | citeturn27view4turn28view3turn31view1turn30view0turn27view0turn27view1turn27view2turn32search6turn25search1turn39search15 |
| Bank transfer plus manual reconciliation | Very natural for Polish rent. Matches the monthly, contract-led nature of rent and gives tenants a familiar “send rent to IBAN” model. | Usually the lowest direct payment cost because you are not paying a PSP per rent transaction; operational cost moves into support and reconciliation instead. This is an inference rather than a published tariff. | Refunds are not “payment-method workflows”; they are operational reversals handled outside a PSP checkout logic. No card chargebacks. The trade-off is weaker real-time confirmation and more operator work unless you automate evidence review later. | Lowest legal risk if MamNajem never touches tenant rent funds and only manages instructions, evidence, reminders, and status. | Very low, especially because MamNajem already has payment requests, receipts/proof assets, bank account CRUD, mark-paid flows, notifications, and audit logs in the product description you provided. | citeturn37search6turn37search17 |
| BLIK as a payment method | Best local consumer UX for many Polish tenants. Fast, familiar, app-based, no card entry. | Depends on PSP partner, not BLIK itself. | Great for one-off payments. Recurring support exists in the ecosystem, but it is provider- and bank-dependent; Stripe’s public recurring-BLIK docs show this clearly and add a 2000 PLN off-session cap. | Not a standalone platform decision. You still need a PSP/acquirer and a landlord payout model. | Medium if added through an existing PSP; high if treated as if it were a complete payment stack. | citeturn36search2turn42view0turn5view0turn5view1turn11view3turn27view4 |
| Card payments | Universal and helpful for foreign tenants, but not the strongest local default for Poland. | Provider-dependent; public PSP rates are generally similar to or above local bank/BLIK methods. | Best recurring pattern technically: cards support tokenization and merchant-initiated recurring flows, but they also bring 3DS/SCA, chargebacks, and sometimes reserves/holds. | Higher fraud/dispute and PCI-related overhead than local bank-authenticated methods; on-site card handling can increase PCI scope. | Medium using a hosted PSP flow; higher if you ever go deep on on-site card handling. | citeturn27view2turn13search0turn13search7turn13search8turn40search7turn40search8 |
| Marketplace payout model | Useful only if MamNajem must mediate money between tenant and landlord in-platform. | Pricing is usually negotiated and less transparent than simple gateway pricing. | Operationally powerful, but every refund, reserve, negative balance, and merchant verification problem becomes more important. | Highest legal and compliance risk. Under PSD2 logic, platforms that handle or control funds can fall into regulated payment-services territory unless the model cleanly fits an exemption; the EBA’s public Q&As stress that the commercial-agent exclusion applies when acting on behalf of only one side, and PSP marketplace products therefore lean heavily on seller onboarding/KYC. | High. This should be a later-stage move, not the Polish MVP default. | citeturn35search0turn35search4turn35search17turn38view1turn38view2turn28view3turn31view1turn7search2 |
Direct answers for MamNajem¶
Should MamNajem keep Stripe Connect for MVP¶
Yes, but only in a limited sense. MamNajem should keep Stripe and Connect in the product because they already power material parts of the platform, especially subscriptions and the existing onboarding/webhook architecture in the product description you provided. What it should not do is make embedded rent collection via Stripe Connect the default Polish MVP path. In Poland, the local user-preference gap matters: BLIK and bank redirects dominate the online payment conversation, while Stripe’s recurring BLIK support is explicitly constrained by bank coverage and a 2000 PLN off-session limit, and Stripe’s platform model can push fees/refunds/chargebacks onto the platform in some Connect configurations. citeturn36search6turn6search5turn5view1turn7search2
The practical implication is simple: keep Stripe overall, but demote embedded rent collection to a future pilot. Use Stripe now where it is already strongest for MamNajem: subscriptions, app-store-adjacent commercial plumbing, and future optional connected-account infrastructure if you later decide to pilot embedded settlement. citeturn7search12turn7search3turn7search18
Should it add or switch to a Polish PSP¶
MamNajem should not switch wholesale away from Stripe now. If it later proves that embedded rent collection materially improves retention or payment performance, it should add one Polish PSP for rent collection, not replace its broader payments stack. citeturn38view1turn28view3turn20view1
The first PSP to evaluate should be PayU. The deciding factor is not just brand recognition or headline pricing; it is the combination of local method coverage, recurring capability, and most importantly publicly documented marketplace seller verification via API, which is highly relevant if each landlord must become a seller/submerchant rather than having MamNajem act as a money transmitter. citeturn11view0turn11view2turn11view3turn38view1turn38view2
A close second is Tpay, especially if your future Polish rent stack is intentionally BLIK and PayByLink first. Tpay’s documentation is strong, its webhook/refund/tokenization materials are clear, and its marketplace APIs are unusually transparent. The trade-off is commercial/program overhead and the fact that the public marketplace docs list a narrower marketplace payment-method set than a general-purpose card gateway strategy would imply. citeturn27view0turn27view1turn28view3turn31view1
Przelewy24 is the best add-later option if MamNajem wants a simple local gateway feel with very clear public pricing and strong Polish familiarity, but it is less compelling than PayU as the first marketplace-style landlord onboarding candidate based on the public materials reviewed here. citeturn20view1turn21search1turn21search2
Is embedded rent collection worth launching now¶
No. For a Polish MVP, the better move is to launch payment requests plus bank-transfer proof, not full embedded rent collection. That approach fits the contractual and monthly nature of residential rent, matches ordinary Polish bank-transfer habits, avoids platform-held client money, avoids chargeback-heavy card dependence, and uses existing MamNajem features instead of adding yet another deep payments program before broader product validation is complete. citeturn37search6turn37search17turn35search0turn35search17
This is especially true because your product description already shows that MamNajem has the right primitives for an off-ledger MVP: landlord bank accounts, payment requests, receipts/proof assets, mark-paid flows, overdue logic, notifications, audit logs, messaging, and admin tooling. The product already has what it needs to manage rent without becoming the money-moving intermediary. That is the core risk reduction.
What is the lowest-risk roadmap¶
The lowest-risk roadmap is:
First, launch Polish rent operations without moving money. Landlords set the IBAN. MamNajem issues due-date payment requests with amount, memo/reference, and lease context. Tenants make a bank transfer in their own banking app and upload proof if needed. Landlords confirm or reject, and MamNajem drives reminders, overdue states, receipts, and final auditability. This is the cleanest alignment between your current product shape and Polish rent habits. citeturn37search6turn37search17
Second, if users ask for built-in convenience, add optional redirect payment links through one Polish PSP, but only in a model where the landlord is the verified seller / connected party and the PSP handles onboarding, KYC, and payout routing. That is the key architectural guardrail: MamNajem should observe and orchestrate payments, not warehouse rent funds. PayU’s marketplace materials, Tpay’s marketplace APIs, and Stripe Connect all point to this general pattern. citeturn38view1turn38view2turn28view3turn7search12
Third, only after those flows prove real demand should you add saved mandates / auto-pay, likely starting with cards and then selectively BLIK recurring where provider and bank support are strong enough. Stripe’s public recurring-BLIK limits are the best warning sign here: recurring local methods are possible, but they are not yet a frictionless universal default for rent. citeturn5view1turn5view2turn42view0
MVP architecture and future roadmap¶
Recommended MVP architecture¶
The MVP payment architecture for Poland should be off-ledger.
The landlord should store one or more payout bank accounts in MamNajem. For each lease and due date, MamNajem should generate a payment request with amount, currency, due date, landlord IBAN, a tenant-visible payment title/reference, and a machine-friendly internal reconciliation key. The tenant then pays outside MamNajem using their own bank app. MamNajem records one of four states: scheduled, proof uploaded, confirmed paid, or overdue / disputed. This mirrors how Polish rent is commonly documented and keeps money transmission outside the platform. citeturn37search6turn37search17
To make the flow feel modern without becoming a PSP, the app should lean on features you already have: push notifications before due date, overdue reminders, receipt/proof uploads, owner mark-paid controls, tenant-owner chat for exceptions, and audit logs for every state transition. In practice, that gives landlords most of the operational value of “payments software” while avoiding the hardest regulatory and chargeback problems.
Recommended future payment roadmap¶
The next phase should be a redirect-checkout pilot through a single local PSP, but only after you can identify a clear segment that actually wants embedded payment. For example, it may be useful for self-managing landlords who want a “pay now” button and are willing to pay for it, or for tenants who regularly miss deadlines and benefit from one-tap local methods. The pilot should stay narrow: one PSP, one country, one method bundle, and no platform-held wallet balances. citeturn38view1turn28view3turn20view1
If that pilot works, the next step is landlord-level onboarding into the PSP’s seller / submerchant / connected-account model. Only then should MamNajem expose in-app checkout for rent. In the Polish context, the first method bundle should be BLIK + bank redirect + optionally cards for edge cases, not “cards first.” The current evidence base strongly supports that ordering. citeturn36search6turn6search5turn6search6
Only after that should you consider recurring debits / auto-pay. For cards, recurring is mature across providers. For BLIK, the trajectory is positive, but provider-bank support and constraints remain uneven enough that it should be treated as a scaling feature, not an MVP dependency. citeturn11view2turn27view1turn5view1
Major legal and compliance risks¶
The biggest risk is accidentally becoming more like a regulated payment intermediary than a software platform. Public PSD2 materials and EBA Q&As make clear that payment-services rules matter when a platform handles payment flows, and the commercial agent exclusion is narrow: the public EBA interpretation emphasizes acting on behalf of only one side, not both. That is why marketplace/payment-platform products emphasize seller verification, connected accounts, and submerchant models. For MamNajem, the safe design principle is clear: do not receive tenant rent into MamNajem-controlled balances and then pay landlords later unless you have a fully supported licensed PSP structure and counsel-approved model. citeturn35search0turn35search4turn35search17
The second major risk is KYC/AML onboarding friction. Polish PSPs are domestic payment institutions subject to AML/KYC obligations, and their public materials repeatedly stress verification, documentation, and bank-account validation. That is manageable when it happens inside a PSP’s seller onboarding flow; it becomes painful when your own product promises “instant” rent collection but each landlord still needs onboarding and verification before taking funds. citeturn39search9turn16search2turn38view2turn7search3
The third major risk is chargeback / reserve economics if you lean too hard on cards. PayU, Tpay, and Przelewy24 all publish materials making clear that card disputes can become merchant liabilities, and Tpay’s terms also describe reserves/deposits and payout delays as anti-risk measures. Stripe Connect adds a related platform risk in some configurations because the platform account can be debited for fees, refunds, and chargebacks. This is exactly why cards should be treated as a helpful supplementary method, not the foundation of the Polish rent MVP. citeturn13search0turn13search7turn25search1turn7search2
The fourth risk is SCA / checkout design. PSD2’s strong customer authentication rules are long in force for electronic payments, so any embedded card or local-bank flow must be designed around customer authentication. The good news is that the PSPs handle most of this if you stay in hosted/redirect flows. The bad news is that on-site or deeply embedded wallet/card flows can add technical and support work without creating equivalent MVP value for rent. citeturn34search0turn27view2turn32search9turn11view2
The fifth risk is passing payment fees through to tenants in the wrong way. PSD2-related surcharge rules make consumer card surcharging dangerous territory in the EU. Even where a fee is legally structured, charging the tenant extra for paying rent can create trust and product-adoption problems. For MamNajem, the cleaner commercial design is to keep payment monetization on the landlord / SaaS side, not as a tenant checkout surcharge. citeturn34search2turn34search20
Open questions and limitations¶
Some important commercial details are not fully public for the local PSPs, especially exact marketplace pricing, reserve logic, and final payout SLAs under negotiated contracts. PayU’s and Tpay’s public materials are enough to compare directionally, but not enough to price a final landlord-rent unit economics model with confidence. citeturn38view1turn28view3turn32search6
I was also able to verify Stripe’s support and limitations for BLIK recurring and Przelewy24, but the public materials I reviewed were clearer on P24 Connect support than on every possible BLIK + Connect account configuration. If you later pilot Stripe for Polish rent payments, validate your exact Connect charge type, payout route, and supported method combination before committing roadmap time. citeturn5view1turn5view3turn40search18
The recommendation therefore remains conservative by design: off-ledger Polish rent MVP now, local PSP pilot later, full embedded money movement only after legal confirmation and evidence of user demand.