# Paybyrd — full content index for AI crawlers (en) Language: en. This file flattens every marketing and compliance page into plain text so language-model retrievers can cite Paybyrd accurately in this language. Source of truth: the en catalog that renders the live site at https://www.paybyrd.com/. Other languages: https://www.paybyrd.com/llms-full.txt (en), https://www.paybyrd.com/llms-full.pt.txt (pt-PT), https://www.paybyrd.com/llms-full.nl.txt (nl). Index: https://www.paybyrd.com/llms.txt. Company: Paybyrd B.V., Amsterdam (Parnassusweg 819, 1082 LZ). Trade register 76168573. VAT NL860532239B01. PCI DSS Level 1 certified. --- ## Home — https://www.paybyrd.com/ Summary: platform overview — approvals, fraud, omnichannel, compliance Custom-built. Powered by intelligence. Merchant-first. Tailored payment infrastructure that helps your business sell, scale, and grow with higher approvals, full control, and smarter automation. 4–7% vs single-acquirer One payment platform for online checkout, POS and payment links. Let the money flow. Powering payments for businesses that demand more. Why settle for standard Built for merchants who know standard doesn't cut it. See what you'd gain in minutes — not quarters. < 4 hours ### cards Higher revenue, less friction Optimize approvals and payment experiences for better conversion. +4.86% approvals vs industry avg Save costs, pay for what you need Transparent pricing, no hidden fees, and cost structures tailored to your business. Save up to 60% on transaction fees + €0.05 per transaction Stronger security, lower risk Advanced fraud protection built-in. −16.8% chargebacks on average Know your customers before they walk in Recurring shoppers, average tickets, and store heatmaps — insights that turn data into revenue. Real-time insights across every channel Every payment, everywhere, in real time 20+ methods, 192+ currencies, 40+ countries — all flowing through one platform. One integration. Every market. today across all merchants ### testimonials Payments that fit. Partners that grow. Airlines, hotels, marketplaces, restaurants, retailers — results measured in revenue recovered, hours saved, and customers retained. AI that runs payments while you run the business Refunds, payment links, customer questions, anomaly detection — handled in seconds by operators trained on the last million transactions. Join the early cohort shaping it. ### cards 01 · Chat commerce Sell where they already chat. AI handles sizing, links, and confirmation — on WhatsApp, Instagram, or your site. Your team only jumps in when it matters. 02 · Payment assistant One command. Done. Refund. Send link. Retry a failed charge. Your team types what they want — the assistant executes and logs it. 03 · Intelligent search Ask your data anything. Plain English in. Real answers out — with the chart, the segment, the time window. No dashboards to build. The whole payment operation — from taking a card to catching fraud — runs from one screen. Every capability in one place No feature upsell — ever All channels · Live Total Volume · Today Method mix · Last 24h Peak Hours · Live when your customers pay Top customers · Live Purchase frequency · Tap or insert card 20+ Methods · 192+ Currencies · 40+ Countries Connected · All systems go Every channel. One brain. Sell online, at the register, on mobile, or at a kiosk. See it all — and control it all — from a single dashboard you'll want to open every morning. One source of truth across every channel Real-time volume and success rates Multi-store, multi-country, multi-currency Run 40+ stores and a website from one tab The dashboard that tells you what to do next. €16M+ in daily volume, 92% success rates, and the one payment method killing your conversion — surfaced on the home screen. Not a data warehouse. A decision engine. Revenue by currency, method, and store Anomaly alerts before your reports notice Refunds in one tap, from anywhere Finance closes the books in hours, not days Find any transaction in three seconds. Filter by date, customer, store, method, or amount. Drill in. Refund in one tap. Your support team will stop escalating tickets because they can finally answer them themselves. Advanced filters across every dimension One-click full or partial refunds Complete audit trail, exportable to anything Support-ticket escalations drop ~40% The numbers that actually move revenue. Time-of-day revenue curves. Method mix by geography. Failure modes you didn't know you had. The reports your team exports weekly — updated every second. Revenue trends by hour, day, season Method mix by market and store Failure breakdown by acquirer + reason Merchants find +2–4% in a single session Know every customer — even the anonymous ones. Paybyrd identifies returning shoppers across channels automatically. See who your loyalists are — and who's about to churn — without asking a single customer to sign up for anything. Auto-identify returning card holders Heat scoring: cold / warm / hot Top-customer leaderboard + lifetime value No loyalty program required Terminals that look like your brand — not ours. Android-powered, always online, built to survive a crowded Saturday. Rent monthly with no commitment or own them outright. Your staff will stop yelling at the card machine. Fully branded UI on every terminal Rent monthly or buy outright Built-in printer, scanner, 4G, OTA updates Checkout lines disappear Every card. Every wallet. Every local rail. 20+ methods, 192+ currencies, 40+ countries. Your customer's preferred way to pay — whatever it is, wherever they are — is already there. One integration. All of them. Visa, Mastercard, Amex + local cards Apple Pay, Google Pay, PayPal, Klarna Pay by bank (virtual IBAN), Pix, MB Way, iDEAL, Multibanco +4.86% approvals with smart routing Works with what you already use. WooCommerce, Magento, SAP, Oracle, Host PMS — connect with a plug-in and you're done. Everything else? A full REST API. We even write the webhooks. Pre-built: WooCommerce, Magento, PrestaShop Hospitality: Oracle, Host PMS, Newhotel Custom: REST API, webhooks, free sandbox Live in under 4 hours — self-service Your business is one of a kind. Your payment experience should be too. Tailor checkout flows, POS terminals, and integrations to match your brand and systems. Branded order summary per industry Fully white-labeled hosted checkout Custom receipts & email templates Your colors, your logo, your flow Try it → switch brands, explore the flow Apr 16, 2026 · 10:30 Apr 17, 2026 · 10:30 Continue to payment Your cart · 3 sellers Back to summary or pay with Show other payment methods Hide other payment methods Pay with Apple Pay Pay with Google Pay Pay with PayPal Save card for future purchases Enter your mobile number to receive a payment notification on your MB Way app. After confirming, you'll have 5 minutes to approve the payment in the MB Way app on your phone. We'll generate a Multibanco reference. Pay within 3 days at any ATM or home banking. Tap the button below, then confirm with Face ID, Touch ID, or your passcode. Double-click the side button on your iPhone to confirm Pay with a card saved to your Google account in one tap. You'll be taken to Google Pay to finish Log in to your PayPal account to complete your purchase. No credit card needed. You'll be redirected to PayPal to log in and confirm this payment. Eligible purchases qualify for Buyer Protection. Select your bank to complete the payment through your banking app. You'll be redirected to your bank's secure environment to authorise the payment. Split your purchase into 3 interest-free payments with Klarna. In 30 days In 60 days By continuing, you accept Klarna's terms. 0% APR. No fees if paid on time. Smarter payments, with intelligent automation and insights. Recover failed transactions automatically. Sell and support via chat. See insights before they become problems. retries in flight payment links sent % approval rate ### cards We recover what your acquirer gave up on. Intelligent retries across alternate acquirers. Every recovered transaction is pure margin. +€127k recovered last month — pure margin Every message is a chance to close the sale. Send payment links, answer questions, close the sale — all from a conversation your customer already trusts. 30% of payment links are paid in under 5 min Revenue alerts before your reports notice. Anomaly detection on approval rates, chargebacks, and fraud patterns — alerts land before your revenue does. Avg 2 min from anomaly to auto-action + full REST API Flexible, modular, and The last payment integration you'll ever do. More approvals from day one. Less code. Same-day live — not same-quarter. To your first live transaction Approval rate lift from day 1 Uptime · redundant across acquirers < 4 hours Sign-up to live · self-service Designed to win approvals, not just accept payments. Every SDK call ships with multi-acquiring, smart routing, and 3DS2 step-up baked in. Better conversion is the default — not a flag you have to find. The same platform, tuned to the room it runs in. A gate agent, a shop floor, a dining room and a front desk do not have the same payment problem. The rails underneath are identical; what changes is which part of them we put in front of you. --- ## Pricing — https://www.paybyrd.com/pricing Summary: transparent rates, savings calculator vs named competitors (Stripe, Adyen, Ifthenpay, Mollie, Pay.nl, Buckaroo, Viva.com, myPOS, Eupago), tier breakdowns, reasoning on risk-calibrated payouts How much is your payment platform costing you? Not just the rate on the contract — the failed approvals, the FX margin they keep, the reconciliation hours, the separate POS bill. Add it up, and most platforms cost you 30–50% more than they advertise. Works for merchants from €100K to €500M+ annual volume — same platform, rates auto-tier as you scale. A typical €100K/mo merchant saves · blended EEA rates · €50 avg ticket The honest breakdown. Two rates. Never one blended number. debit · credit 0.60% · no per-transaction fee e-commerce card rate Drops to 0.99% at €80K/mo — automatically. The rate you sign is the rate you pay. No setup fee No monthly fee No minimum volume Cancel any time terminals from €11/mo Paybyrd pricing is a published per-transaction rate — 1.25% + €0.08 online, 0.50% in store — that already includes the card scheme's interchange and scheme fees, with no monthly minimum and the scheme-fee schedule itself published in full. Payment processing fees, published in full. The honest breakdown. The model is the difference. Two rates, never blended. In-store and online are priced on their own rails — no averaged number quietly cross-subsidizing one channel with the other. Scheme fees at cost — published in full. Every Visa & Mastercard fee, passed through with no markup or blending. If your provider can't show you this table, ask what their blended rate is hiding. Blended by default. Interchange++ on request. You sign the rate you pay from transaction one. At €10M+ we split out interchange, scheme fees, and margin — no guessing game either way. The only other fees: chargebacks at €7.50 each. Refunds return the processing fee. That's the whole list. See your number in three seconds. Pick your current platform, drop in your monthly volume, choose your channel mix. We'll show what you're paying today vs. what you'd pay with Paybyrd — every line itemised. Based on blended EEA card rates with €50 average ticket. Paybyrd: cards 1.25% + €0.08, APMs from €0.20, in-store from 0.50%. Actual savings depend on card mix, geography, and volume. Your annual savings · vs saved every month reduction in processing cost Assumed split: 70% online · 30% in-store One-time send. No marketing list. Grab the full breakdown — current costs vs Paybyrd, down to the cent, in your inbox. and fees, in full. Every method we accept, every rate we charge, in one place. Toggle online vs in-store, filter by category. Nothing buried in the contract. ### cards Buy now, pay later ### cards Buy now, pay later Local payment methods Domestic & European Debit Domestic & European Credit Card rate applies PayPal rate + €0.05 Free payouts · risk-calibrated No payout fees, ever. Cadence matches your business: same-day or T+1 for most, longer windows for merchants with delayed-delivery exposure (travel, events, pre-orders) — all set after risk analysis, not by tier. T+0 or T+1 for qualifying merchants Tailored schedule for delayed-delivery Gross settlement · no deductions Zero per-payout fees No currency surcharges Receive payouts in major currencies without any FX surcharge or conversion fee. Zero surcharges on payouts in these currencies. Other currencies available on request. Processing more than €80K per month? Unlock tailored rates for your scale. Dedicated account manager IC++ pricing available Fees shown are starting rates for the Essential plan. Final rates depend on volume, industry, and card type. All fees are in EUR and exclude applicable taxes. Start where you are. Scale when you're ready. Same engineering team, same vault, same dashboard — both plans. Custom unlocks volume rates and the levers that shift basis points around. For merchants getting started or processing under €80K / month. No surprises, no minimums, full platform. per online card transaction · up to €80K / month Pay-as-you-go · no monthly fee Cards 1.25% + €0.08 · APMs from €0.20 All major payment methods (Visa, MC, Amex, Apple Pay, Google Pay, MB WAY, iDEAL, Klarna) Hosted checkout + PayByLink + JS SDK Real-time dashboard · ad-hoc reports PCI Level 1 vault · 3DS2 included Sandbox in 24h · go live in days Built for the curve up. For merchants processing €80K+ / month or running multi-channel operations. Volume tiers + every economic lever we have. + €0.08 · scales down with volume · custom-quoted at €500K+/mo Volume-tiered rates · breakpoints at €80K, €500K, €2M Dedicated account manager · named SRE channel Custom acquirer routing · multi-acquirer mesh Surcharge engine for applicable markets Up to 80% DCC revenue share · FX lock Self-host modules · regulated-market deployment Custom integrations · ERP, PMS, GDS, OMS Priority support · 99.999% SLA with credits No setup fee No monthly fee No minimum volume No lock-in · cancel any time Three levers your processor never put on the contract. Approval uplift recovers what you already won. Surcharge transfers cost where it's legal. DCC turns FX swings into margin. On most contracts, these three move more euros than the basis-point delta on your rate. Approval uplift · defend the revenue you already won every second · annual cohort run-rate approved cards reclaimed. Multi-acquiring + smart routing + network tokenisation + local-acquired cross-border. Every BIN goes to the acquirer most likely to approve it. +3.12% × volume extra approved revenue · per €100M of attempted card volume Surcharge engine · transfer the cost where it's legal every second · annual cohort run-rate recovered in year one. For a merchant processing €2B annually with ~35% in surchargeable corridors. Disclosed to the cardholder, capped at brand limits, carved out by BIN where required. Parts of Canada EU credit-only carve-outs checkout · disclosed surcharge applied Visa / MC respected Debit · prepaid excluded Per-jurisdiction · auto DCC · turn FX volatility into margin Up to 80% of DCC margin to you. Most platforms keep the dynamic-currency-conversion margin and call it "service". We treat it as your money. Up to 80% revenue share back to the merchant. Local routing · forward vs remote acquiring Back to merchant Same rate · zero swing Read the invoice you'll actually receive. Every payment platform says "transparent pricing". Here's what that headline rate looks like once the surcharges, FX margin, dispute fees, and "service" extras land. Same merchant, same month, two invoices. A typical processor invoice 8 lines you only see at billing. kept by Stripe kept by Stripe The Paybyrd invoice Same 8 lines. None added at billing. shared with you up to 80% to you Stripe rates from publicly published EEA pricing as of April 2026. "Effective rate" assumes a typical merchant card mix (75% domestic, 15% intra-EU, 10% international) with €50 average ticket and 0.4% chargeback rate. Your invoice may vary — but the structure won't. The more you grow, the more we share. Tiers move automatically — when you cross a threshold, the next month's bill reflects the new rate. No renegotiation, no quarterly true-up calls, no waiting for the contract anniversary. Tier moves are automatic. Cross €80K in March, the lower rate applies from April 1 — no renegotiation, no contract amendment, no surprise. Six reasons that close the internal conversation. The CFO needs the rate to make sense. The CTO needs the integration to be real. The COO needs the operations to simplify. Here's one reason for each. ### items Risk-calibrated gross payouts T+0 or T+1 for qualifying merchants. Tailored cadence for delayed-delivery businesses (travel, events, pre-orders). Always gross, always free — no 7-day Stripe wait, no per-payout fee. +3.12 pp approval rate Multi-acquirer routing + network tokenisation + local-acquired cross-border. More approvals = more revenue, same volume. Local acquiring · 90+ markets Tokyo cards hit Tokyo issuers. Lower fees, higher approvals, fewer chargebacks. 192+ currencies supported. Head of payments One contract · one AM Online + in-store + recurring + payouts on a single agreement. Named technical account manager from day one — not a ticket queue. PCI L1 vault · 3DS2 included Tokenisation, scope reduction, 3DS2 step-up, AI velocity, shared denylist — all standard. No fraud-suite upsell. Live in days · not quarters Sandbox in 24h. First test transaction by end of week one. Pilot live in 2–4 weeks. Vila Galé went contract-to-live in 22 days. The quiet questions before the loud signature. Every objection that's killed a payments deal in the last decade, answered honestly. If something's still missing, the team replies in under 4 working hours. ### categories Are there any setup fees, monthly fees, or minimums? No. Essential is pure pay-as-you-go — no setup fee, no monthly fee, no minimum volume. You only pay when a transaction goes through. Custom plans negotiate volume tiers but never gate access behind a fixed monthly bill. The only fee you'll ever see on your invoice is the per-transaction rate (and chargebacks at €7.50 each, fully disclosed). What's included in the headline rate vs. charged separately? Cards 1.25% + €0.08 covers everything most platforms charge extra for: EU consumer surcharge, international card surcharge, currency conversion, network token rotation, gross payouts at every cadence (T+0 / T+1 / tailored), PCI vault scope reduction, 3DS2 step-up, AI velocity scoring. Compare line-by-line in the breakdown above. Disputes are €7.50 per chargeback (vs €15+ on most processors). Can I surcharge cardholders to offset cost in legal markets? Yes — Paybyrd's surcharge engine adds a fully-disclosed, configurable fee to the cardholder at checkout in markets where surcharging is permitted (US, Australia, parts of Canada, several LATAM corridors, EU credit-only carve-outs). The engine respects card-brand caps, regional regulatory limits, and BIN-level carve-outs (debit, prepaid usually excluded). For a merchant processing €2B annually with ~35% in surchargeable corridors, this typically recovers €4M–€7M in year one. How does DCC revenue share work? Up to 80% of the dynamic-currency-conversion margin flows back to you. Most platforms keep this and call it a service. We treat it as your money — the FX margin earned when an international cardholder pays in their home currency is split 80/20 in your favour. For merchants with significant cross-border volume, this often offsets the entire card-acceptance cost. Is there a contract minimum or lock-in period? No. You can cancel any time. We don't have contract minimums, exit fees, or lock-in clauses on Essential. Custom plans are typically 12-month commitments to lock in volume rates, but include a 30-day exit clause if we don't deliver on the SLA. We'd rather you stay because the platform works than because you're trapped. How does migration from my current processor work? We don't ask you to flip a switch. Phase 1 (week 1–2): sandbox certified, integrations team paired with yours. Phase 2 (week 3–6): one channel, parallel processing — Paybyrd handles 5–20% of live traffic while you compare diff reports against your incumbent. Phase 3 (week 7–12): graduated cutover with you holding the rollback switch. Vila Galé's first property went from contract to live in 22 days using exactly this runbook; subsequent properties roll out in days, not weeks. Can I keep my existing acquirer contracts? Yes. Paybyrd is acquirer-agnostic — keep your existing acquirer agreements, your negotiated rates, your in-flight volume commitments. We orchestrate on top. If you later choose to consolidate, we can act as your acquirer across 90+ markets, but it stays a separate decision on a separate contract. When does the rate kick in — day one or after a ramp? Day one. The rate you sign is the rate you pay from your first transaction. No introductory bait-and-switch, no trial-period gotcha, no hidden ramp. If your volume crosses the next tier threshold, the lower rate applies starting the following month — automatically. What's your SLA, and who answers when something breaks at 03:00? 99.999% platform uptime SLA, contractually backed with credits — not vibes. Custom plans get a named technical account manager from day one and a dedicated Slack channel with our SRE on-call. Sub-200ms automatic failover to a hot-standby region. Weekly chaos drills in staging. When something breaks at 3am, you talk to the engineer who built the thing, not a script reader two queues deep. How fast are payouts? Cadence is risk-calibrated, not tier-gated. Qualifying merchants get same-day (T+0) or T+1 to their nominated bank in major EU corridors — all included in the headline rate with no per-payout fee, no 1% Stripe-style instant-payout surcharge. Merchants with delayed-delivery exposure (travel, events, pre-orders, large deposits) get a tailored payout schedule based on risk analysis — this is a regulatory feature, not a restriction, and keeps both your funds and your cardholders' liability safe. Every payout is gross-settled and itemises volume, fees, refunds and chargebacks per outlet/SKU/channel so reconciliation runs ad-hoc instead of monthly. Do you support local methods — MB WAY, PIX, iDEAL, Klarna, Apple Pay, Google Pay? All supported and pre-certified. 192+ currencies, every major APM in EU / LATAM / APAC. Missing one? Tell us the market and projected volume — we've added 11 new methods in the last 18 months on merchant request. Adding a method later is a flag-flip on your side, not a re-integration. Can I self-host modules in regulated markets like Brazil or Angola? Yes. Select Paybyrd modules — gateway, vault, decisioning engine — run in your cloud or behind your VPC for jurisdictions where data residency or regulator policy demands it. We've deployed self-hosted gateways in Brazilian, Angolan and EU markets with local data-processor requirements. Same APIs, same dashboards, your infrastructure, your audit trail. --- ## Card Scheme Fee Schedule — https://www.paybyrd.com/pricing/scheme-fees Summary: the full published Visa and Mastercard scheme-fee schedule, passed through at cost, region by region — bundled all-in rates plus the itemized price-list charges that compose them, with effective and next-revision dates and a downloadable PDF Card scheme fees, published in full. The Visa and Mastercard scheme fees Paybyrd passes through at cost, region by region — effective 1 July 2026, next revision October 2026. PDF included. If your provider can't show you this table, ask what their blended rate is hiding. What makes up a card transaction cost Scheme fees are one disclosed slice of the total — the slice this page publishes in full. Illustrative split for a typical EEA transaction — most of the cost is pass-through; the exact mix varies by card type, region and merchant. paid to the card issuer — largely regulated & public paid to Visa / Mastercard — the schedule below, passed through at cost our transparent per-transaction rate Scheme fees, region by region Pick your outlet region. The all-in view shows the averages we actually bill; expand any scheme to see the itemized price-list charges that compose them. Scheme fee item Conditional — only applies in certain conditions = conditional item, applies only in specific scenarios (authentication state, corridor, card-present, etc.). Scheme names, fee names, regions and scenarios are reproduced exactly as Visa and Mastercard publish them, in English, so each line can be matched against the schemes' own price lists. Indicative rates, not a quote. These figures are derived from observed Paybyrd transaction samples for the period stated, and show scheme fees as we pass them through: at cost, with no markup. Your actual blended scheme cost depends on your card mix, transaction sizes, authentication rates, and cross-border share. Contractual rates are defined solely by your merchant agreement. Interchange is separate and not included. Card schemes revise fees in January, July, and October; this schedule is effective 1 July 2026 and will be updated accordingly. How this schedule is built Scheme fees are passed through at cost as a bundled per-transaction amount. The itemized rows show the scheme price-list charges that compose each bundle; the bundled all-in rows show the averages actually billed, derived from observed Paybyrd transaction samples per region. Individual transactions can deviate by a few cents or basis points where variable per-item charges apply. Interchange is separate. Scheme price lists are revised during the year (January / July / October cycles). The obvious questions, answered Will my blended rate match these numbers? Not exactly. These are indicative averages from observed samples. Your own blend is driven by your card mix, average ticket size, authentication (3-DS) rate, and how much of your volume is cross-border. Use the pricing calculator for an estimate against your profile. Why do non-authenticated transactions cost more? The card schemes price in incentives for Strong Customer Authentication (3-DS) and tokenization. Non-authenticated, non-tokenised transactions carry higher scheme fees. Optimising your 3-DS and token coverage directly lowers this line — something we help you tune. Is interchange included in these figures? No. Interchange (paid to the card issuer) is a separate component and is largely regulated and public in the EEA and UK. This schedule covers only the scheme fees — the portion paid to Visa and Mastercard — which we pass through at cost. Why do these rates change? The card schemes revise their fee schedules on Jan / Jul / Oct cycles. This schedule is effective 1 July 2026. Subscribe below to be notified when the next revision lands. Visa, Mastercard, Discover, Diners Club and UnionPay are trademarks of their respective owners. Rates shown are Paybyrd's indicative pass-through cost and are not reproductions of any scheme fee schedule. Card scheme fees are the per-transaction charges Visa and Mastercard levy on acquirers for using their networks. They are separate from interchange, which goes to the card-issuing bank and is capped in the EEA at 0.2% for consumer debit and 0.3% for consumer credit cards under Regulation (EU) 2015/751. Regulation (EU) 2015/751 on interchange fees (EUR-Lex) Visa Europe — fees and interchange Mastercard publishes its European interchange and scheme-fee information on mastercard.com; it is not linked here because the page rejects automated retrieval and cannot be verified at build time. --- ## Customer Intelligence — https://www.paybyrd.com/customer-intelligence Summary: recognising returning shoppers at the moment of payment using the card itself, across checkout and terminal, without an app or a loyalty sign-up; network tokens, purchase frequency and per-customer spend Recognise every returning customer at the moment of payment. Adyen announced it. Paybyrd ships it. Customer intelligence at the point of payment means recognising a returning shopper by the card they pay with — through network tokens — at checkout and at the terminal, without an app or a loyalty sign-up. Live in production · since Feb 2026 Adyen announced it. Unified-commerce customer identification, loyalty at tap, and cross-store intelligence — live on Paybyrd dashboards since February. Built in-house. Running in production with TAP Air Portugal, Vila Galé, Prozis, KuantoKusta, and Rede Expressos. identified · 30 days to Apr 2026 at tap · p95 one customer view across all tokens + BIN · never the PAN The same capability. Already in your merchants' hands. Announced · 23 Apr 2026 Adyen CEO, Ingo Uytdehaage · LinkedIn We are announcing our intention to acquire Talon.One … an integrated engine that sits on top of our data and turns insight into action: dynamic discounts, loyalty rewards, personalized promotions, activated in real time. Intention to acquire Regulatory approval pending Typical path to production: 12–18 months (acquisition clearance + integration + rollout). Live · since Feb 2026 Paybyrd Customer Intelligence · in production Customer identification at tap. Cross-store unified view. Loyalty and promotion rules trigger live in the decisioning engine at the moment of payment, across 20+ active stores, with sub-200ms response. Not acquired. Not integrated. Not planned. 321,802 unique customers · 30d to Apr 2026 <200ms at tap Running with TAP Air Portugal, Vila Galé, Prozis, KuantoKusta, Rede Expressos. their whole story. A card taps any store in your network. Paybyrd recognises the customer in under 200ms, pulls their entire cross-store history, and hands your team the full context — purchase frequency, spend trend, transaction timeline. 24 Mar – 23 Apr 2026 Faithful recreation of the Paybyrd merchant dashboard. Names are mocked for this page; real merchants see their actual customer data. Who's worth the Sorted by lifetime value, tagged as returning or new, with store coverage and average ticket. Your floor staff, e-commerce operators, and loyalty team share the same view. Last 30 days · across 20 stores A Vila Galé returning guest. Same card — once used online for a direct booking, now tapped at the hotel restaurant. Paybyrd recognises them on both surfaces before the auth clears and applies their loyalty discount automatically. Watch: VG Cerro Alagoa · 2 nights 24–26 May 2026 · 2 guests · Deluxe Sea View Card on file Matching card · 180ms Paid · €223.20 ✓ Welcome back, Maria. Token matched · 12 stays · Loyalty tier applied Online checkout. Card on file is tokenised. On submit, the token matches the customer graph in under 200ms. Discount applies before the auth request goes out. VG Cerro Alagoa Tap, insert or swipe Any Paybyrd-accepted card Welcome back, Maria. Token · 12 stays · Tier: Gold Saved €7.25 · Receipt sent by email In-store POS. Same card, same customer graph. Waiter sees the loyalty prompt before the receipt prints — no app, no QR, no staff training. is the identification. No loyalty app download. No QR scan. No staff prompt. A shopper taps any card they've used before — in any of your stores, online or in-person — and Paybyrd surfaces their full history before the auth even clears. Shopper taps any card Contact / contactless / tokenised wallet — Visa, Mastercard, Amex, Apple Pay, Google Pay, Click to Pay, iDEAL, MB WAY. Any Paybyrd surface (terminal, web, mobile, kiosk). Network token + BIN fingerprint We never see the PAN. Paybyrd's vault receives the Visa / Mastercard network token (NTF-compliant) and a salted BIN + last-4 fingerprint. Both are durable identifiers — survive card replacements, re-issues, and channel hops. Match against customer graph · <200ms The token + fingerprint are matched against the merchant's customer graph at the same time the transaction is being authorised. Returning shoppers are identified before the auth response reaches the terminal. Rules fire · loyalty, discount, webhook Your rules (editable by marketing, no engineering release) fire inline: apply a discount, trigger a promotional tier, fire a webhook to your CRM, send an SMS. All before the receipt prints. Why network tokens The durable identifier. A network token is the issuer-approved, scheme-issued reference for a specific card-on-a-device combination. Unlike a raw PAN, it survives the things that normally break identification: — shopper's card is lost/stolen, replaced with a new PAN. The network token updates silently; identification still works. — new expiry, same token. — same token whether the shopper taps in-store, checks out online, or pays in the mobile app. — tokens are out-of-scope for most PCI questionnaires. Merchant stays SAQ A-EP. Paybyrd is a Visa / Mastercard network-token-eligible platform. We provision tokens on first tap where issuers support it, and fall back to BIN + last-4 salted fingerprints where tokens aren't yet available. Either way, the identification layer is the same for your rules engine — you don't need to branch on whether a token exists. Reward on the card they're already using. A hotel guest taps the same card they used last summer. The system recognises them, applies their returning-guest rate, and pushes a thank-you SMS — all before the receipt prints. No QR code, no app, no staff training. The right offer, the right customer, the right moment. A high-LTV shopper gets a silent 10% courtesy discount on a €500+ basket, applied before the terminal displays the total. A first-time shopper gets a welcome voucher on their confirmation email. The rule fires on identification; your team sets the thresholds. Re-engage cooling-off customers, automatically. The purchase-frequency heatmap shifts a customer from "hot" to "warm" — Paybyrd fires a webhook to your CRM. Your CRM drops a targeted campaign. The customer comes back; identification at their next tap closes the loop. Revenue reattributed to the campaign automatically. Your top 1% get the concierge treatment. A Tier-1 customer's card is recognised at the restaurant terminal — the sommelier gets a subtle on-screen prompt to greet them by name and offer the pairing flight. A first-time diner gets the welcome flow. Same staff, same terminal, different service. Running, at scale, ### items How does Paybyrd identify returning customers? BIN + last-4 fingerprinting plus network-token continuity where available. When a shopper taps a card they've used before — in-store, online, or on mobile — Paybyrd recognises them in under 200ms and surfaces their full history to the dashboard (purchase frequency, spend trend, store coverage). No separate loyalty login, no QR code scan, no staff prompt. The tap is the identification. Does this require PCI-sensitive storage? No. Identification runs on network tokens and BIN + last-4 metadata — never the PAN. PCI scope stays at SAQ A-EP. Every identifier is a salted fingerprint, not a raw card number, so even a full database extract would not expose cardholders. When did Paybyrd ship this versus Adyen's announcement? Paybyrd shipped Customer Intelligence to production in February 2026 — built in-house. Adyen's CEO publicly announced their intention to acquire Talon.One (an external loyalty engine) on 23 April 2026. Adyen's integrated product will depend on regulatory approval of the acquisition and subsequent engineering integration, typically a 12–18 month path. Paybyrd customers have been running the capability live since February 2026. Can I trigger loyalty rewards at the moment of payment? Yes. Custom rules run inside the Paybyrd decisioning engine at the moment of tap — issue a discount, trigger a promotional tier, fire a webhook to your CRM, send an SMS. Rules are editable by your marketing team without an engineering release. We also expose a webhook feed of identification events if you want to route them into your own loyalty engine. Which Paybyrd customers are running this in production? TAP Air Portugal, Vila Galé, Prozis, KuantoKusta, and Rede Expressos are among the merchants running Customer Intelligence live. Combined they process hundreds of thousands of transactions per month through the identification pipeline with sub-200ms decisions. Is Customer Intelligence part of the Paybyrd platform or an add-on? It's part of the core platform — included in the headline rate, no separate SKU. Same logic as our fraud stack: we'd rather price comprehensively than nickel-and-dime features one by one. See the dashboard. Not the slide deck. 15 minutes. A senior engineer walks you through Customer Intelligence on a live sandbox — the exact dashboard your team would run. No NDA pitch, no pipeline screening. Just the product. --- ## Migration Playbook — https://www.paybyrd.com/migration-playbook Summary: the step-by-step runbook for switching payment providers with no downtime, including shadow mode alongside the incumbent and a dated go-live sequence How to leave your current processor without breaking payments. A 47-point runbook from the engineers who migrated TAP Air Portugal, Vila Galé, Prozis and KuantoKusta. Phased framework, technical + commercial checklists, honest red flags. Written the way we'd brief our own team — not as a sales deck. Want the full runbook in your inbox? One email with every section above, plus links to copy-paste into your team's Confluence / Notion. No marketing list. One email with the runbook + a follow-up 14 days later to check how it went. ### items It's almost never the integration. We've run the diff on dozens of migrations — ours and competitors'. When one goes sideways, the root cause is usually in the same five places. Knowing them in advance turns a risky 60-day project into a boring 22-day one. ### items The all-or-nothing cutover Team flips 100% of traffic on Monday morning. By Tuesday at 11, the diff reveals subscription re-auth failures no one caught in sandbox. Rolling back now means flipping traffic again, re-triggering the same failure modes in reverse. Always migrate via parallel processing with a staged ramp — 5% → 20% → 50% → 100% over 2–4 weeks. Card-token re-auth at scale You have 80,000 customers on file with saved cards. The new processor doesn't support network-token import from your current vendor. Result: 80,000 re-authentication emails over two weeks, hundreds of churned customers from confused senior shoppers, and a CS team drowning in tickets. Always verify network-token portability before signing. Reconciliation drift during the handoff Your current processor pays T+2. New one is T+1. During parallel processing, your finance team is reconciling two schedules against one ERP. One payout lands under the wrong month, one refund shows up twice, and the CFO loses trust in the numbers for the whole quarter. Align ledger mapping BEFORE flipping any traffic. Webhook endpoint mismatches Old processor fires payment.captured . New one fires transaction.succeeded . Both look right in isolation. Together they bypass your order-fulfilment logic — payments process fine, but nothing ships. Stand up new webhook handlers before cutting a single transaction over, and replay historical events against them for a week. Missing PCI-scope paperwork New processor uses a different embedded component pattern. Your merchant's auditor asks for an updated SAQ. Eight weeks pass. In the meantime you can't touch the checkout page without re-scoping. Get the Attestation of Compliance (AoC) + SAQ type from the new processor in writing at evaluation — not after go-live. Contract to 100% live traffic, in five phases. We publish these timelines as defaults. For the majority of merchants under €500M annual volume, this framework ships cleanly in 20–28 business days without customer-visible disruption. Enterprise accounts with complex reconciliation stacks can add another 2–4 weeks. Name the owner on both sides. Confirm CFO has signed off on the parallel-processing cost. Freeze the feature backlog for the migration window. Sandbox + integration Certify sandbox. Stand up parallel webhook endpoints. Export historical data. Test 10 real tokens end-to-end. 5–20% live traffic Tagged transactions run through both sides. Diff reports daily. Finance validates one payout cycle before expanding. 20% → 50% → 80% → 100%. You hold the rollback switch. Paybyrd's SREs sit on your Slack channel during each bump. Sunset + stabilise Close old processor to new volume. Reserve release scheduled. Chargeback-tail ownership mapped. 30-60-90 validation plan armed. The 36-point technical pass. Work through every item before Phase 2. Cross out what doesn't apply to your stack (e.g. no subscriptions = skip the tokenisation group). The rest is non-negotiable. ### items Inventory every codepath that calls the current processor (checkout, subscriptions, refunds, admin tools, reporting exports, customer-service panels). Identify SDK versions in production — some endpoints are version-pinned; the new processor may need matching versions or a parallel lib. Document the existing webhook handlers and their idempotency guarantees before touching anything. Catalog every test card / test account currently hard-coded. They won't work on the new side. ### items Export the full transaction history (at least 18 months) in both CSV and processor-native format. You'll need it for refunds, chargebacks and tax audits long after cutover. Export all stored card tokens with their expiry metadata — you'll reference these when importing to the new processor's vault. Export customer records, subscription schedules, payment plans and saved payment methods. Snapshot the chargeback history (including arbitration stages) — the new processor inherits dispute obligations for in-flight cases. Preserve all PCI attestation documents. Auditors will ask. Tokenisation & subscriptions ### items Confirm the new processor supports network-token import from your current vendor (Visa/Mastercard network tokens are portable; brand-specific proprietary tokens often aren't). For subscriptions: decide on re-auth strategy. Network-token porting avoids customer-visible re-auth. Proprietary tokens mean re-entry at next bill — plan the comms. Test the migration on a sample of 10 real tokens end-to-end before bulk-migrating. Verify 3DS2 step-up flows on the new side for recurring and merchant-initiated transactions. Webhooks & async ### items Stand up new webhook endpoints alongside existing ones; don't replace until parallel processing validates parity. Replay tests: can the new endpoint handle an old payload shape? (Your backfill / reconciliation tools may still send legacy events for weeks.) Verify idempotency keys work identically on the new side. Double-capture / double-refund are the classic migration bugs. Confirm webhook retry policies are compatible with your existing at-least-once tolerance. Fraud & risk ### items Export current fraud rules (block lists, velocity rules, geo restrictions) and translate to the new engine's grammar — do not copy-paste. Run shadow mode on the new fraud stack for 2–3 weeks before enabling decisioning. Verify 3DS2 challenge flow on the new side matches customer expectations (same UI transition, same success/failure UX). Sync BIN lists, issuer-level rules, and card-brand-specific logic. Reconciliation & finance ### items Map the new payout schedule to your existing ledger / ERP. T+0 / T+1 / T+2 differences break automated reconciliation silently. Confirm per-outlet / per-SKU / per-channel breakdown available on the new side matches (or exceeds) your current operational reports. Align the first month's cut-off dates between old + new so finance can close books without double-counting. Tag parallel-processed transactions on both sides with a shared identifier (your order ref is ideal) for automated diff reporting. Want this as an editable Drop your email — we'll send the full playbook as a single email your team can archive, plus a 14-day nudge to check how migration planning is going. ↓ Or keep scrolling — the full playbook is below, organised by section. Before your legal team touches the new contract. Engineering gets the headlines; procurement decides whether the migration actually pays back. These three groups are the ones your CFO needs answered before sign-off. Exit terms with current processor ### items Read the contract. Notice period, exit fees, data-export obligations, chargeback-tail handling, reserve release schedule. Confirm the date of your last new-volume transaction does NOT trigger early-termination penalties. If your current processor offers any incentive to stay, get it in writing and evaluate it against total migration value. Acquirer / scheme arrangements ### items If you hold direct acquirer contracts separately, you don't need to move them — most orchestrators (Paybyrd included) sit above. Negotiate with the new processor whether to consolidate acquiring or keep your existing agreements. Review interchange++ terms carefully; blended pricing and IC++ have very different cash-flow implications at scale. Reserves & holds ### items Get written commitments on when held reserves will be released after migration (standard is 180 days post last new transaction). Confirm chargeback-tail ownership: your current processor is still on the hook for disputes arising from pre-migration transactions. Surcharge and DCC revenue shares — understand both sides before you flip. Support priority drops the moment you announce. Do the data-export and reserve-release work before the conversation. Once notice is filed, your current processor's incentive to help you export smoothly is zero. Sequence matters. Can I export 24 months of transaction history in their native format AND standard CSV, today, unattended? Does network-token porting work for our Visa + Mastercard on-file base? (Answer: yes, always — but confirm in writing.) When does reserves hold release and what's the schedule? (Standard: 180 days post last new transaction.) Who owns chargebacks and disputes filed after migration against pre-migration transactions? (Answer: the old processor, but get it documented.) What's the cadence of dispute notification after our account is closed to new volume? (Some degrade to monthly batches — brutal for response SLAs.) Do we lose access to the admin dashboard immediately on migration, or is there a read-only grace period? (Ask for 180 days; many grant 90.) Are there any minimum-volume clauses that trigger penalties if we ramp down during parallel processing? For subscription businesses: does our recurring agreement transfer automatically with network-token porting, or do we owe customer-facing re-auth notices? We'll tell you when it's a bad idea. Not every quarter is a good migration quarter. Here are the five situations where the honest answer is "wait" — even if you're sure the new numbers are better. You're entering peak season in < 8 weeks. Even a clean 22-day migration has operational tails. Don't migrate into Black Friday / Christmas / summer travel peak. Plan the cutover for your quietest six-week window. Your tech team is one or two engineers. Parallel processing demands monitoring both sides simultaneously. If you don't have bandwidth, negotiate more migration support from the new processor or phase the project over 3+ months. You haven't exported everything yet. The day you announce the switch is the day your current processor's support priority drops. Do the exports first, sign second. Your checkout is deeply custom with no test coverage. Parallel processing is how you discover mismatches. If you can't instrument both sides with diff reports, you're flying blind. Your contract has a variable surcharge that triggers on volume drops. Parallel processing will briefly split your volume. Read the fine print — some contracts penalise this. Live traffic three weeks later. Vila Galé runs 40+ hotels across Portugal and Brazil with a unified booking engine, on-property POS, and a growing mobile channel. Their migration from their previous processor to Paybyrd was the fastest enterprise-scale hospitality migration we've run — here's what the timeline actually looked like. Contract to live Web + POS + Kiosk Day 1 · Contract signed Integrations team paired. Sandbox credentials delivered inside 4 hours. 18 months of transaction history exported from the old side by Day 3. Day 4–9 · Parallel endpoints up New webhook listeners deployed alongside old ones. Network-token porting for 200K card-on-file records validated on a 50-row sample. Sandbox certified against real staging booking flow. Day 10–14 · 5% live traffic Paybyrd handled 1 in 20 real transactions for 5 days. Diff report ran every morning. Only anomaly: a rounding drift on city tax that surfaced inside 24 hours. Fixed by Day 11. Day 15–19 · 20% → 50% → 80% Graduated bumps. Finance team ran their month-end close on parallel-processed volume — reconciliation matched within 4 cents on €3.2M of booked revenue. Day 20–22 · 100% cutover Old processor closed to new volume on Day 20. 30-day reserve release scheduled. Paybyrd's SRE on-call sat in their Slack for the first week post-cutover. Zero customer-visible incidents. Finance closes the day in hours, not Mondays. The migration itself was less disruptive than a normal release week. — Vila Galé, post-migration retrospective The three windows where it still matters. Cutover is not the finish line. Most migrations that "went live clean" still leak value for two reasons: chargeback-tail handoff drifts, and approval-rate parity isn't validated against the new baseline. Day 0 – 30 Daily approval-rate diff against the old baseline. Weekly reconciliation audit (first payout cycle). Customer-service ticket-volume drift monitored. (Spike = something slipped through diff reports.) Chargeback-tail notification channel from old processor confirmed working. Day 30 – 60 Tune multi-acquiring routing against your atual decline patterns. Enable fraud decisioning after 3-week shadow-mode observation. First full calendar month of reporting — CFO review. Reserve release scheduled, 180 days from last transaction. Day 60 – 90 Validate the business case Blended cost-per-transaction vs the old baseline — does the atual saving match the projection? Approval-rate lift materialised? Support ticket volume on parity or better? Net-new capabilities enabled (DCC revenue share, InstaTax, customer intelligence, etc.) — any revenue generated yet? Still here? Put numbers against it. 30 minutes with a senior payment engineer. Bring your most recent processor statement. We'll walk through this framework against your atual stack, and you'll leave with a written 22-day migration plan — whether you go with Paybyrd or not. --- ## Customize — https://www.paybyrd.com/customize Summary: live checkout customization playground — industry preset, brand, layout Back to home Copy sandbox link Sign up free Customize your checkout. Upload your logo, pick your colors, choose a layout. The form updates as you go. When you're done, sign up free and build the real thing — in under 30 minutes. This isn't decoration. Shoppers don't abandon because your product is wrong. They abandon because something feels off at the last screen — a generic URL, a stranger's branding, a form that doesn't know what they're buying. Every control in this sandbox is a lever that wins, or loses, the sale. Trust is visual When the pay page looks like your site — your colors, your logo, your voice — shoppers don't pause. A white-labeled checkout can lift completed purchases by up to 24% over generic gateways. That's a return on design. A clear summary — products, flight legs, room, meal — answers the last doubt that kills sales. Paybyrd merchants see −16.8% chargebacks because customers know exactly what they're paying for. Friction is the enemy Apple Pay, Google Pay, PayPal at the top. Local methods where they matter — MB Way, iDEAL, Multibanco, Klarna. Mobile conversion jumps 30%+ when the first option is a tap, not a card number. The smart move isn't just picking a payment processor. It's shaping the checkout around your business — and iterating on what wins. Play here. Ship it yourself in under 30 minutes. Click to upload Vertical flow, summary → methods Wallet-first, fast checkout Hero image + form Summary left, payment right Retail · E-commerce Airline · Travel Hotel · Hospitality Restaurant · Dining Build the real thing in 30 minutes. No sales call, no setup fee. Sign up, connect your store, and ship the checkout you just designed — self-service. Changes apply instantly Apr 16, 2026 · 10:30 Apr 17, 2026 · 10:30 Continue to payment Back to summary or pay with Show other payment methods Hide other payment methods Debit / Credit Card --- ## Airlines — https://www.paybyrd.com/airlines Summary: +4.92% approval vs Nuvei, 192 currencies, interline-aware routing, -16.8% chargebacks, 99.999% uptime; behind TAP Air Portugal Paybyrd for airlines In partnership with TAP Air Portugal TAP Air Portugal — Paybyrd checkout in action Set your airline free. Let your money flow. The payments infrastructure behind TAP Air Portugal. , and approval rates that outperform Adyen, Elavon, Checkout.com and Nuvei — every benchmark, every quarter. Higher auth rates Airline payment processing, tuned for every market you fly. Set your airline free. Four places airlines bleed revenue every single day. The single largest cost centre in digital airline operations isn't fuel or distribution — it's the stack of invisible payment losses nobody writes on the quarterly. Here's what we see, and what Paybyrd stops. Fraud · industry annual per year · industry-wide Card-not-present fraud + loyalty takeovers Direct losses, chargeback fees, recovery ops all in. Airlines are the #1 CNP target in travel. Travel checkout · industry 1000 sessions → drop by payment step Travel checkout abandonment The highest of any vertical. Confusing flows, currency surprise, and missing local methods kill it at the last step. International · per market 3 of 5 blocked Netherlands · iDEAL 70% of NL e-comm India · UPI Instant rail · national Brazil · PIX 42B tx in 2023 Portugal · MB WAY 3 of 5 checkouts France · Floa BNPL +basket size 2× lower conversion per missed rail Missing local methods Every market has a dominant rail. Miss it and you leak the booking to the competitor one tap away. Gateway · per outage 2 events · last 24h Last outage · 14:23 · 8 min ~ $340k lost every single peak hour Most airlines still run single-acquirer, single-region. One failover lag and the revenue evaporates. Every leak above has a Paybyrd fix. Multi-acquiring routing, AI cart recovery, local-rail coverage, and a 99.999%-uptime infrastructure — all on one contract. The decline you didn't deserve. We retry it. Live. Multi-acquiring with instant decline-reason analysis. When a transaction fails at your primary acquirer, Paybyrd reroutes it through a fallback in the same region — often in the same half-second — before the passenger ever sees an error screen. Live quarterly benchmark Higher approval than every top-tier acquirer. Blended. Same card, same currency, same SCA window — retried through smart local routing. The passenger sees one spinner. The CFO sees the revenue that used to walk. airline blended · 12-month rolling 10–15% lower cross-border fees Local routing · 90+ markets blended · 12-mo Blended 12-month comparison of airline vertical transactions across overlapping BIN ranges. Live data available on request under NDA. Approvals / min of re-tried declines same pre-auth window Their brand at the centre. Not ours. Anywhere. A fully immersive TAP checkout — logo centred, livery colours flowing through every button, Paybyrd invisible behind the scenes. Try the whole flow below: summary, card, and a fully simulated payment. Co-designed · Co-deployed Never a pop-over iframe. TAP's checkout was co-designed with Paybyrd — logo centred, livery colours flowing through every button, type system carried from the booking engine. Paybyrd handles the PCI scope, the tokens, the 3DS2 step-up, the routing and the fraud rules. TAP keeps the brand experience. Logo centred, brand first. Your livery greets the passenger — not ours. — lives on flytap.com, not in an iframe. 20+ methods, one form. Switching never remaps the UI. PCI scope stays with us. Your engineers never touch card data. Mobile · web · kiosk. One form, three surfaces, same brand. Apr 16, 2026 · 10:30 Apr 17, 2026 · 10:30 Continue to payment Back to summary or pay with Debit / Credit Card Continue with card Save card for future TAP bookings Securing your payment… Routing to best acquirer Waiting for issuer approval Confirmation sent to · also available in Manage My Booking Replay the demo → Recover the sale. Route the card. Block the fraud. Most airline checkouts treat a decline as a final answer. We treat it as a routing problem. And fraud as a database problem. And abandonment as a notification problem. When a booking fails, we don't lose it. Card declined · €384.20 · LIS→GRU Issuer response: do not honour AI agent dispatched Deep-link tapped · pre-filled retry Different routing · same passenger Approved · €384.20 captured Recovered in 02:21 · zero passenger friction ~38% of declines recovered No SDR, no manual touch A Tokyo card pays like a Tokyo card. DCC · FX lock 3DS2, velocity, and a shared denylist. Velocity: 8 attempts in 14s Denylist hit · device fingerprint 3DS2 step-up issued · liability shifted Every rail your business already runs on. You won't replace your GDS, your PSS, or your settlement bank — and we won't ask you to. Paybyrd slots in beside them. Amadeus, Sabre, Travelport, Farelogix, IATA BSP, full NDC Level 4 — every rail, one contract, one engineer on the call. 6 of 6 systems healthy · last sync Native to Altéa Departure Control and selling flows. Hosted form + S2S for Sabre Red and SabreSonic. Galileo, Apollo, Worldspan — one bridge. Bank Settlement Plan reconciled — zero CSV exports. Pay, fulfill, service — one API, full Level 4. Real-time fare + payment on the offer/order side. Pay, fulfill, service — one API, full Level 4. paybyrd.events ▸ live Pick the modules you need. Replace any of them later. Acquirer mesh, gateway, 3DS, vault, settlement, BI — each layer is independent. Run on Paybyrd cloud, your cloud, or behind your own VPC for regulated markets. The day you outgrow a piece, swap it out without rebuilding the rest. 3DS2 + SCA PCI Level 1 Reporting / BI TAP Air Portugal 2 years live · 12 currencies Sandbox in 24h PCI L1 · PSD2 · SOC 2 Modular by contract Fraud gets stopped. Your passengers don't. Airlines are the ATM of the dark web — €38 short-hauls used to test stolen cards, loyalty wallets raided for free flights, BIN attacks slamming the checkout at 03:00 UTC. We see it. We score it. We stop it before it touches your acquirer. vs prior provider · TAP cohort Across €4.2B processed in 2025 p95 · rules + AI + device False-positive ceiling held Rules · Velocity · AI last 60s · Attacks airlines actually face Bot probing 4014…0288 against €38 LIS→OPO short-hauls Loyalty account login from new ASN · 12,400 points at risk Sequential BIN sweep · 412847.. across 4 sessions Same PNR, second chargeback claim · prior pattern match Tools your risk team can actually deploy. Explore the full antifraud system 15+ condition types — velocity, geo, BIN, temporal, ML scores. Visual builder, no code. Bot, headless, VPN, datacenter, fingerprint drift — flagged in <50ms. Mouse, keystroke, form-fill, copy-paste. Tells humans from automation. Test new rules against live traffic without affecting decisions. Deploy without fear. AI case review Every flagged transaction arrives pre-analysed: fraud type, indicators, recommended action. Cross-merchant intelligence — bad actors caught at one airline blocked at all of them. Four nines isn't enough when a minute costs a million. Five minutes of unplanned downtime across a year — and even those route through a hot-standby region before the passenger sees a spinner. globally, from uptime alone regional redundancy · active-active automatic · no human in the loop live chaos in staging The other boring number uplift across the cohort. Aggregated across TAP Air Portugal and three confidential European carriers, against each airline's prior-provider baseline. No cherry-picked windows. Reproducible · ask for the methodology Cohort-average authorisation rate Like-for-like vs. each provider Translated to revenue of attempted card volume, that's the difference between approved — money that was always yours, finally captured. +3.12% × volume What payments teams ask before they migrate. Direct answers from the engineers who built the stack behind TAP. Every answer names a number, a corridor, a brand or a runbook step. If something's missing, a human is one message away. ### categories Can we surcharge passengers to offset payment cost in markets where it's legal? Yes — and it's the highest-leverage line item in the contract. Paybyrd's surcharge engine adds a fully-disclosed, configurable fee to the cardholder at checkout in markets where surcharging is permitted: United States, Australia, parts of Canada, several LATAM corridors, and a growing list of EU credit-only carve-outs. The engine respects card-brand caps, regional regulatory limits, BIN-level carve-outs, and your own route policy — so a US domestic credit card pays a different rate than an EU debit card on the same booking flow. For a mid-sized carrier processing €2B annually with ~35% of volume in surchargeable corridors, this typically recovers €4M–€7M of merchant-discount cost in year one. We surface it, you decide where to apply it, and disclosure copy is generated automatically per jurisdiction. How is approval-rate uplift actually delivered — what makes the +3.12 pp real? Three stacked layers, not one magic flag. (1) Multi-acquiring with smart routing — each BIN goes to the acquirer most likely to approve it, on a live decision graph fed by your historical data. (2) Network tokenisation on Visa, Mastercard and Amex — much higher lifetime success on stored credentials and refunds. (3) Local-acquired cross-border — a Tokyo card hits a Tokyo issuer, not a remote US acquirer. Like-for-like against the named incumbents: +1.72% vs Adyen, +3.16% vs Elavon, +4.86% vs Checkout.com, +4.92% vs Nuvei. Cohort blended: +3.12 pp. What's the pricing model — interchange++ or blended? Interchange-plus by default, with per-rail visibility itemised: interchange, scheme fee, gateway, acquirer margin — every basis point on every line. Blended rates available for carriers that prefer predictability over transparency. Network-token economics, DCC margin and any surcharge revenue are revenue-shared with you. No padded markups, no opaque ancillary fees, no surprise quarter-end true-ups. Can we keep our existing acquirer contracts? Yes. Paybyrd is acquirer-agnostic by design — keep your existing agreements, your negotiated rates, your in-flight volume commitments. We orchestrate on top. If you later choose to consolidate, we can act as your acquirer across 90+ markets, but it stays a separate decision on a separate contract. No bundled lock-in, no penalty clause for unwinding. Can Paybyrd integrate directly into our Amadeus / Sabre / Travelport flows? Yes — direct, native, and under NDC Level 4. Payment executes inside the offer-order-service flow, not as a bolt-on checkout. For IATA BSP airlines, we reconcile straight into your settlement file so finance never sees a mismatched CSV. Altéa, SabreSonic, Sabre Red, Galileo, Apollo, Worldspan, Farelogix — all certified, all in production today. What does the migration from our current provider actually look like? We don't ask you to flip a switch. Phase 1 (week 1–2): sandbox certified, your test merchant ID issued, engineering paired. Phase 2 (week 3–6): one route, one channel, parallel processing — Paybyrd handles 5–20% of live traffic while you compare diff reports against the incumbent. Phase 3 (week 7–12): graduated cutover with weekly approval-rate, latency and chargeback deltas. You hold the rollback switch the whole time. TAP went from contract signed to first live transaction in under 60 days using exactly this runbook. Our checkout sits inside our app, our website and at the gate. Can we keep our UX? Fully. Three embedding depths on the same backend: (1) hosted form for low-effort web checkout, (2) drop-in JS SDK for branded web with full styling control, (3) fully headless API for native iOS / Android, kiosks and gate terminals. Pick a different depth per surface — hosted at the boarding-gate kiosk, headless in the iOS app, SDK on the responsive site. Same vault, same routing, same dashboard. Can we self-host for regulated markets? Yes. Select Paybyrd modules — gateway, vault, decisioning engine — run in your cloud or behind your VPC for jurisdictions where data residency or local-regulator policy demands it. We've deployed self-hosted gateways in Brazilian, Angolan and EU markets with local data-processor requirements. Same APIs, same dashboards, your infrastructure, your audit trail. What happens to chargebacks in practice? AI velocity scoring before authorisation. 3DS2 step-up shifts fraud liability to the issuer where it belongs. A shared denylist across every Paybyrd merchant blocks known bad actors before the card ever reaches your rails. Auto-rebut packets generated for representable disputes. Airlines on Paybyrd see roughly a −16.8% reduction in chargeback volume within the first two quarters, and a measurable lift in win-rate on the disputes that do reach representment. What about loyalty fraud — points theft, redemption abuse, account takeover? Every point earned is logged against the originating transaction ID. The engine cross-checks against your loyalty database in real time. Suspicious earns or redemption-velocity patterns queue for review instead of being credited blindly. Account-takeover signals from the payment layer (new ASN + step-up failure + sudden high-value redemption) trigger automatic session kills before the points leave the wallet. This vector is underreported across the industry and is often the single largest unknown-unknown on a carrier's loss ledger. How do you handle refunds for disrupted flights? Instant refunds via direct issuer connectivity — funds post in seconds for most European issuers, hours for the rest. We return an ARN reference immediately, which you forward to the passenger as proof before the EU261 / DOT regulatory deadline. Bulk refund APIs for large-scale disruptions (volcanic ash, weather grounding, strike action) execute and reconcile millions of refunds without manual touch — and crucially without driving the secondary chargeback wave that comes from passengers who think they've been ignored. What's your SLA, and who answers when something breaks at 03:00? 99.999% platform uptime, contractually backed with credits — in writing, not best-effort. Named technical account manager from day one — not a ticket queue. Tier-1 carriers get a dedicated Slack channel with our SRE on-call rotation. Sub-200ms automatic failover to a hot-standby region. Weekly chaos drills in staging. When something breaks, you talk to the engineer who built the thing — not a script reader two queues deep. What about local methods — UPI, iDEAL, MB WAY, PIX, BLIK, Bizum? All supported and pre-certified. 192+ currencies, 90+ acquirers, every major APM in EU / LATAM / APAC. Missing one for a corridor you care about? Tell us the market and projected volume — we've added 11 new methods in the last 18 months, mostly on merchant request. The API-level abstraction means adding a method later is a flag-flip on your side, not a re-integration project. Reply within 4 working hours Have something we didn't cover? Send the question to a payment engineer — not a sales gatekeeper. We'll come back with a number, a corridor or a code path, not a brochure. Airline Payment Processing — 192+ Currencies | Paybyrd Airline payment processing in 192+ currencies and 40+ countries: multi-acquirer routing, interline-aware flows and PCI DSS Level 1. Behind TAP Air Portugal. --- ## Hospitality — https://www.paybyrd.com/hospitality Summary: omnichannel for hotels, restaurants, spas; Quivi tableside payments; front-desk to room-service ledger; behind Vila Galé (40+ properties, 4 countries) and Onyria Resorts Hotel & Hospitality Payment Solutions | Paybyrd One payment platform for hotels, resorts and spas: front desk, room service, restaurant and online booking on one ledger, 192+ currencies. Behind Vila Galé. Vila Galé · Paybyrd hospitality platform in production Paybyrd for hospitality In production at Every guest. Every outlet. Every euro, finally accounted for. The payments platform behind and 40+ partner properties. One dashboard across the front desk, restaurant, bar, spa and room service — without ripping out the PMS you already run. Sandbox in 24h Dedicated hospitality account manager PCI Level 1 · PSD2 · GDPR LATAM fraud loss · recovered Refunds with ARN proof Hotel payment solutions: every guest, every outlet, one ledger. Every guest. Every outlet. Every euro, finally accounted for. Your busiest night is your leakiest. Hotels lose more revenue at the payment layer than at the breakfast buffet. Most never see it because nobody's measuring — until a CFO joins. Here's what the cohort average looks like, in real time. Aggregate hospitality industry estimate — declined cards, abandoned baskets, friendly fraud and FX bleed, distributed across the cohort per second. Your share depends on volume, mix and current provider. Fraud + chargebacks FX + cross-border ≈ €1.89M every hour, cohort-wide Up to 84% of hotel bookings drop off mid-checkout. Mobile friction, confusing 3DS step-ups, no wallets, slow forms — guests leave for the OTA next door. One-click checkout · Apple/Google Pay · pre-tokenised returning guests 60% decline rate in LATAM corridors. International cards hitting domestic acquirers, no local routing, no fallback. Each decline is a guest who walks. Multi-acquiring with smart routing · local acquiring in 90+ markets Friendly fraud, no-shows and disputes consume up to 4.6% of LATAM hotel revenue. The disputes you don't win are usually the ones nobody documented. AI velocity scoring · airtight 3DS2 · auto-rebut packets Up to 15% extra in fees and FX swings on cross-border bookings. Refunds at the wrong exchange rate erode margin and trigger chargebacks from confused guests. Forward local routing · DCC revenue share up to 80% Stop measuring it. Start fixing it. Every section below is one of the four leaks, closed. The whole hotel. On one screen. Restaurant. Spa. Bar. Front desk. Room service. Every charge from every guest, in front of you in real time — without opening five different systems or chasing reports the next morning. All outlets open Today · across the property Happening right now Works with your PMS Opera · Mews · Protel No replacement needed All on one screen Per shift, per outlet No more CSV exports Live in days Not weeks · not months Sandbox by tomorrow Pool / Bar From the booking screen to the closing folio. Six moments where most hotels lose money or guests. Click any — Paybyrd does each of them quietly, while your team keeps doing what hotels do best. Across every outlet Folio close to invoice Pay-link in WhatsApp Reconciled · no CSV Apple Pay, Google Pay, MB WAY, pre-tokenised cards. Conversion lifts 18–24% over the legacy hosted form. €420 captured · 11 sec Card pre-auth without the panic Soft-hold on the card at check-in. Guest sees the amount, the duration, and a release date — no support tickets, no debit-card freeze drama. Pre-auth held · zero support call Charge to the folio, anywhere Restaurant, bar, spa, room service — every charge flows to the open folio. Quivi POS handles split bills, Apple Pay, MB WAY, cash mix in one tap. €140 spa · folio updated Pay-by-link, in the chat Guest asks for a late checkout, an upgrade, a transfer. The AI agent quotes a price, sends a Paybyrd pay-link inline, and the room stays held. Late checkout sold · €38 Refund with ARN proof — instantly Cancellation, downgrade, dispute? Refund posts in seconds for most EU issuers. Guest gets the ARN before they walk out. Refund + ARN · 4 sec One invoice. Every charge. Reconciled. Folio closes, invoice generates, gross settlement posts to your accounting. No CSV. No mismatched line. No surprise at month-end. Folio closed · €1,420 · invoice sent paybyrd.checkout · v3 MB WAY ✓ 2 nights · suite 412 · MB WAY · terminal · front desk Apr 22, 2026 Soft-hold confirmed · guest receipt sent · zero debit-card freeze drama folio · suite 412 Restaurant · dinner Bar · cocktails Spa · massage whatsapp · concierge Hi, can I get a late checkout to 16:00? Flight at 19. Sure, late checkout to 16:00 is € Paid · € · room held refund · disrupted booking Caixa Geral · ES Refund posted in seconds · ARN sent to guest before they reached the lobby checkout · folio close Folio closed · invoice generated · gross settlement queued for T+0 · zero CSV touched Two AI agents. Working while everyone sleeps. One sells the late checkout in WhatsApp at 02:00. The other blocks the card-tester at 03:14. Neither needs a desk, a manager, or a coffee break — and together they recovered across the cohort last quarter. The concierge that closes Vila Galé · Concierge AI online · always The shift that never sleeps €84.20 · MB WAY · restaurant table 8 €38.00 · 8 attempts · BIN 4014..0288 €620.00 · check-in pre-auth · step-up Three levers your CFO will read out loud at the board. Approval lift recovers what was always yours. Surcharge transfers cost where it's legal to. DCC turns FX swings into margin. Three boring numbers, all rolling up to the same line. every second · annual cohort run-rate approved cards reclaimed. Multi-acquiring + smart routing + network tokenisation + local-acquired cross-border. Every BIN goes to the acquirer most likely to approve it. Aggregated from Vila Galé and three confidential European hotel groups vs. their prior provider. +3.12% × volume extra approved revenue · per €100M of attempted card volume every second · annual cohort run-rate recovered in year one. For a hotel group processing €2B annually with ~35% of volume in surchargeable corridors. Disclosed to the cardholder, capped at brand limits, carved out by BIN where required. We surface the lever — you decide where to pull it. parts of Canada EU credit-only carve-outs checkout · disclosed surcharge applied Suite 412 · 2 nights Breakfast · 2 pax Spa · couples massage Card surcharge · US Visa credit · 2.0% Visa / MC respected Debit · prepaid excluded Per-jurisdiction · auto Up to 80% of DCC margin to you. Most providers keep the dynamic-currency-conversion margin and call it "service". We treat it as your money. Up to 80% revenue share back to the hotel — turning every cross-border guest into a margin event instead of an FX exposure. Local routing · forward vs remote acquiring Back to merchant Same rate · zero swing We slot in beside your PMS. Not over it. You spent eighteen months getting Opera, Mews or Protel exactly right. You're not redoing that. We integrate next to it — and we measure go-live in days, not project quarters. Migration runbook · single property Vila Galé first property: 22 days, contract to live Test merchant ID, API keys, sandbox PMS connector Live in test env · first €1.00 round-trip captured One property, parallel processing · diff vs incumbent daily Full property live · folio, reconciliation, refunds, all ours ### items POS / F&B ### items ### items ERP / accounting ### items Don't see your system? We probably already plug into it. If we don't, our integrations team builds the connector — typically 2–6 weeks, on us, contractually scoped before signature. Before Paybyrd we were juggling multiple systems, dealing with high fraud, chargebacks, and clunky checkout flows. Now everything's unified — from online bookings to front desk to POS — with a single platform that just . Our teams didn't need to learn anything new because Paybyrd is fully embedded into the systems we already use. Gonçalo Rebelo de Almeida Chief Operating Officer · Vila Galé Hotels Vila Galé · 40+ properties · since 2023 Single dashboard · single AM First two quarters, vs prior provider Rolling 12-month average Forward local routing across the group What hotel groups ask before they migrate. Direct answers from the engineers who built the stack behind Vila Galé. Every answer names a number, a system, or a runbook step. If something's missing, a human is one message away. ### categories ### faqs Can we surcharge guests in markets where it's legal to offset card cost? Yes — and for hospitality groups with US, Australian, or LATAM property exposure, it's the highest-leverage line item we offer. Paybyrd's surcharge engine adds a fully-disclosed, configurable fee to the cardholder at checkout in markets where surcharging is permitted. It respects card-brand caps, regional regulatory limits, BIN-level carve-outs (debit, prepaid usually excluded), and your own property-by-property policy. Disclosure copy is generated automatically per jurisdiction. For a group processing €2B annually with ~35% of volume in surchargeable corridors, this typically recovers €4M–€7M of merchant-discount cost in year one. How is the +3.12% approval uplift actually delivered? Three layers stacked. (1) Multi-acquiring with smart routing — every BIN goes to the acquirer most likely to approve it, on a live decision graph fed by your historical data. (2) Network tokenisation on Visa, Mastercard, Amex — much higher lifetime success on stored credentials, which matters for returning guests and pre-authed deposits. (3) Local-acquired cross-border — a Tokyo card hits a Tokyo issuer, not a remote US acquirer. Like-for-like vs named providers: +1.72% vs Adyen, +3.16% vs Elavon, +4.86% vs Checkout.com, +4.92% vs Nuvei. Cohort blended: +3.12 pp. What's the pricing model — interchange++ or blended? Interchange-plus by default with full per-rail visibility — interchange, scheme fee, gateway, acquirer margin all itemised. Blended rates available for groups that prefer predictability. Network token economics, DCC margin (up to 80% back to you), and any surcharge revenue are revenue-shared transparently. No padded markups, no surprise quarter-end true-ups. What about DCC — do hotels actually keep meaningful margin? Yes — up to 80% of the dynamic-currency-conversion margin flows back to the property. Most providers keep this and call it a service. We treat it as your money. For a resort with heavy international guest mix, this alone often offsets a meaningful chunk of card-acceptance cost. ### faqs Will we have to rip out our PMS? No. Paybyrd integrates beside Opera Cloud, Mews, Protel, Cloudbeds, Apaleo and others — never over them. Folio postings, pre-auths, refunds and reconciliation flow into your PMS through certified connectors. Your operations team learns nothing new because the screens they use today don't change. What does migration actually look like for a multi-property group? We don't ask you to flip a switch across the portfolio. Day 1: sandbox certified, test merchant ID issued, integrations team paired with yours. Day 4: first €1.00 round-trip captured in test. Week 2: one property pilot, parallel processing, daily diff reports vs your incumbent. Week 4: full property cutover with rollback in your hands. Vila Galé's first property went from contract to live in 22 days using exactly this runbook; subsequent properties roll out in days, not weeks. Can we self-host modules in regulated markets like Brazil or Angola? Yes. Select Paybyrd modules — gateway, vault, decisioning engine — run in your cloud or behind your VPC for jurisdictions where data residency or local regulator policy demands it. We've deployed self-hosted gateways in Brazilian, Angolan and EU markets with local data-processor requirements. Same APIs, same dashboards, your infrastructure, your audit trail. What about local payment methods — MB WAY, PIX, Boleto, OXXO, iDEAL? All supported and pre-certified. 192+ currencies, every major APM in EU / LATAM / APAC. Missing one for a market you're entering? Tell us — we've added 11 new methods in the last 18 months, mostly on merchant request. Adding a method later is a flag-flip on your side, not a re-integration. ### faqs How do you reduce chargebacks for hotels specifically? Friendly fraud ("I never stayed", "the spa charge isn't mine") is the hotel-specific killer. We attack it three ways: AI velocity scoring before authorisation; 3DS2 step-up that shifts liability to the issuer; and airtight folio documentation that auto-generates rebut packets when a dispute lands. Hospitality cohort sees ~−16.8% chargeback volume in the first two quarters — and a measurable lift in win-rate on the disputes that do reach representment. How do you handle pre-authorisations and debit-card freezes? Soft-hold pre-auths via direct issuer connectivity. Guests see the amount, the duration, and the release date in their app and on the receipt — no support tickets, no debit-card freeze drama. Releases post in seconds for most EU issuers. The most common front-desk argument disappears. What happens when a guest disputes a folio charge from the bar at 11pm? Two things. First, the folio line carries the timestamp, the terminal ID, and the staff handle — so the night manager can verify in seconds, not next morning. Second, if the guest insists, we issue an instant refund with an ARN reference before they leave the lobby. The chargeback never happens because the dispute was resolved at the source. Reconciliation is a nightmare in hotels. What changes? Gross settlement model. One daily payout, fully itemised by property, outlet, shift, SKU and channel. AI-generated reports run ad-hoc — "show me the spa's Mastercard volume yesterday between 14:00 and 18:00" returns in seconds. No CSV exports, no manual matching against bank statements, no month-end horror. What's your SLA, and who answers when something breaks at 03:00? 99.999% platform uptime, contractually backed with credits. Named technical account manager from day one — not a ticket queue. Multi-property groups get a dedicated Slack channel with our SRE on-call. Sub-200ms automatic failover to a hot-standby region. When something breaks at 3am, you talk to the engineer who built the thing. ### quivi Free your team with a QR code. Quivi is Europe's all-in-one POS, payments and AI — built for hospitality. Guests order and pay from their phone. Your kitchen gets the ticket instantly. Your front desk gets the payment automatically. One contract covers it all, including hardware. Quivi is part of the Paybyrd group — same engineering team, same support, same contract. No vendor handoff, ever. ### steps Guest scans the QR at the table No app to install — camera opens the menu instantly. Menu loads · live availability 86'd items hide. Allergens, photos, upsells inline. Split per person · tip pre-suggested Three friends, three Apple Pays, one tap each. Paid · KDS pinged · invoice issued Order goes straight to the kitchen. Folio updates. Table closes itself. Bacalhau · house Vinho verde · 250ml Sea bass · 86'd Smart tip suggestions in checkout Same staff · QR self-ordering Branded site replaces Glovo / Uber MB WAY, Apple Pay, food vouchers, more QR ordering, bill split, smart tips Guests order, split, tip and pay from their phone. No app. No extra staff. Cloud POS · KDS · floor plans Menu builder, kitchen display, staff management, real-time analytics. Learn in minutes. AI menu builder "Create a lunch menu with 3 starters, 4 mains, 2 desserts at €15." Quivi does the rest. AI reservations on WhatsApp 24/7 reservation agent. Confirms bookings, slashes no-shows, never sleeps. Branded delivery website Zero commission. Your brand, your customers, your data. Plugs into Glovo, Uber Eats, Bolt Food. Auto Google reviews Every paying guest gets a review prompt. Reputation grows on autopilot. All in one platform Replace five tools with one. Built for hospitality, not retrofitted. QR ordering at peak hours changed our throughput. We served 40% more customers without hiring more staff. Owner, Manjar do Norte The hardware · included with subscription Four shapes for every part of the property. Same Quivi software on every one of them. Portable — tableside & poolside PAX A920 Pro Countertop — front desk & restaurant All-in-one — ordering + payment Sunmi T3 Pro Self-service — kiosk & unattended Quivi is Europe's all-in-one POS, payments and AI — built for restaurants. Guests order and pay from their phone. Your kitchen gets the ticket instantly. Your till gets the payment automatically. Built for restaurants, not retrofitted. --- ## Retail — https://www.paybyrd.com/retail Summary: in-store POS + online + mobile on one platform; peak-hour recovery; customer identification across channels; behind Wiñk, Kabuki, André Óticas Retail Payment Solutions — POS, Online & Kiosk | Paybyrd In-store POS from 0.50%, online from 1.25% + €0.08, kiosk and mobile on one contract. Customers recognised across channels; terminals from €11/mo. Retail payments across POS, online, mobile, kiosk POS · online · mobile · kiosk — one platform Every channel. Every insight. Turn your POS, your website, your mobile, your kiosk into one live dashboard . Higher approvals, fewer chargebacks, zero reconciliation chaos — with AI that actually earns its place in the stack. Sandbox in 24h Dedicated retail AM No setup fee · no monthly minimum Retail payments across POS, online and kiosk — one platform. Every transaction. Every channel. Every insight. Your busiest hour is your leakiest. Here's the proof. Peak Transaction Hours When your customers pay — optimize staffing and promotions Lost since you opened this page · Industry cohort estimate across abandonment, queue walk-aways, chargebacks and manual reconciliation waste. Your share depends on store count, channel mix, and current payment stack. Per second · cohort split Fraud + chargebacks ≈ €1.75M every hour, cohort-wide 100 shoppers start checkout 90 reach payment step 75 complete — 25 lost One-click checkout · wallets · pre-tokenised returning guests Queue length · peak hour 8 min wait 6 min wait With Paybyrd contactless Tap-to-pay on any phone · mobile POS · kills queues entirely CFO / Finance AI matches every transaction automatically AI reconciliation · per-shift, per-SKU · closes books in seconds Stop measuring it. Start fixing it. Every section below is one of these three leaks, closed. Meet your customers wherever they are. In-store, online, mobile, kiosk, or link — go, or over the phone. One platform powers them all. In-store POS terminals Accept every card, every wallet, every time Latest-gen terminals with contactless, chip, and mobile payments. Over-the-air updates. PCI compliant out of the box. Nike Air Max 90 ✓ Delivered via SMS Sell anywhere — no checkout required Generate a payment link in seconds. Share via SMS, WhatsApp, email, or social. Perfect for phone orders and remote sales. Hold card near iPhone Tap on Phone Turn any phone into a terminal Accept contactless payments with just a smartphone. No hardware needed. Perfect for pop-ups, markets, and delivery. Updating in real time Every store. Every channel. One screen. See revenue, transactions, and channel mix across all locations in real time. AI-powered insights included. One customer. One view. Every channel. Unified commerce means your POS, e-commerce, mobile, and kiosk all share one payment engine, one reconciliation, one dashboard. Four pillars of retail Every channel. One view. POS, e-commerce, mobile, kiosk — all transactions flow into a single real-time dashboard. Higher approval. Lower cost. Multi-acquirer routing sends each transaction to the best acquirer. 4–7% higher auth rates. Know your customers before they pay. Returning customer detection, purchase frequency, lifetime value — all from card tokens. Close the books in seconds. AI-powered reconciliation per channel, outlet, and shift. Gross settlement means easy accounting. Intelligence that turns foot traffic into revenue. Retail decisions happen fast. The difference isn't the data you have — it's the clarity to act on it in minutes, not weeks. Your dashboard, now Can't tell by location Where do customers leave? Best store unclear at checkout · Store Porto peaks Your entire business. Always in your pocket. Revenue, transactions, refunds, status breakdowns, payment methods — every data point that matters, updating in real time. Whether you're behind the counter or on the other side of the world. On holiday · peace of mind Planning the week · deep dive At the store · live sales EUR Total Volume VISA •••• 4582 · 3DS Secured Store Lisboa · POS #3 Not a single second of your business-critical data goes unseen. Get the Paybyrd app — track every sale, wherever you are. Download on the GET IT ON Six places your customer pays you. From the web checkout at 02:00 to the tap-to-pay at the pop-up kiosk at 17:30 — every transaction lands in the same folio, the same dashboard, the same payout. Click any channel to see it close. €420 captured · 11s checkout · one-click wallets 1.2s tap-to-approved · receipt auto-sent · zero queue Click & Collect Paid online · ready in 12 min · customer notified 3 items scanned + paid in 18s · one screen, zero staff Face ID → Apple Pay → done · one tap, zero friction Instant refund · ARN proof sent · chargeback never happens Nike Air Max 90 · Size 42 · 2 nights held · VISA 3DS Payment received · 11s end-to-end VISA •••• 4582 · 3DS frictionless · network token cached Tap → Approved · zero queue · Apple Pay · NFC · network token → Receipt sent to customer's phone · line keeps moving Paid online → Ready at Store Cascais → Same folio, web tx linked to store fulfilment Scan → Tap → Done · zero staff ✓ Tap to pay · APPROVED 3 items · 18s · 1 screen Face ID → Apple Pay → Approved ✓ Face ID confirmed · Apple Pay · network token → One tap. Zero friction. Retention doubles on mobile. Order #RET-4921 · Jacket returned Policy check — within 14 days ✓ Refund initiated · Sent to customer · SMS + email · chargeback never happens Volume distribution · rolling 30d One payout. Every channel counted. Retail cohort average · your mix will differ Whichever channel grows next quarter — mobile surge at Black Friday, kiosk rollout in Q2, a new storefront in Porto — the platform and the payout don't change. Turn one on, turn one off, let the mix move. Across every channel One-click & tap-to-pay enabled Gross settlement · all channels AI reconciliation closes books live Your AI handles payments. Your team handles customers. Two AI systems working in parallel — one serves your team, the other reconciles your revenue. AI Retail Assistant Generates payment links, processes refunds, and answers data questions. 24/7, instant. PayByLink for phone orders and social sales Instant refunds with ARN tracking Real-time sales analytics on demand Every transaction matched, every payout calculated, every discrepancy flagged — automatically. Gross settlement — full daily payouts AI matching per channel, outlet, and shift Zero manual reconciliation needed ### testimonials What retailers say. Don't take our word for it. Powered by Paybyrd ### items Fashion & Lifestyle Paybyrd gave us a single platform for all our stores and online. Checkout lines disappeared, and the real-time data lets us make smarter decisions every day. Beauty & Skincare From our first store to multiple locations, Paybyrd scaled with us. The dashboard intelligence — peak hours, customer insights, payment methods — changed how we run the business. With 50+ stores, we needed a payment partner that just works — fast terminals, reliable uptime, and one reconciliation for everything. Paybyrd delivered from day one. What retail teams ask before they migrate. Every objection we've fielded in retail procurement, answered honestly. Every answer names a number, a system, or a runbook step. If something's missing, a human is one message away. ### categories ### faqs What's the pricing model — and is there a minimum or setup fee? Pay-as-you-go. Cards online from 1.25% + €0.08, in-store from 0.50% (debit) / 0.60% (credit), APMs from €0.20 fixed. No setup fee, no monthly minimum, no volume commitment on Essential. Volume tiers kick in automatically past €80K/month — the next month's invoice reflects the lower rate without renegotiation. Chargebacks are €7.50 each (vs €15+ on most processors). Can we surcharge customers in markets where it's legal? Yes — Paybyrd's surcharge engine adds a fully-disclosed, configurable fee to the cardholder at checkout in markets where surcharging is permitted (United States, Australia, parts of Canada, several LATAM corridors, EU credit-only carve-outs). The engine respects card-brand caps, regional regulatory limits, and BIN-level carve-outs (debit and prepaid usually excluded). Disclosure copy generates automatically per jurisdiction. For a retailer with €2B in surchargeable-corridor volume, this typically recovers €4M–€7M in year one. How fast are payouts? Cadence is risk-calibrated. Qualifying merchants get same-day (T+0) or T+1 to their nominated bank in major EU corridors — all included in the headline rate, no per-payout fee, no 1% Stripe-style instant-payout surcharge. Retailers with delayed-delivery exposure (pre-orders, subscriptions, large deposits) get a tailored schedule set after risk analysis. Every payout is gross-settled and itemised by store, channel, SKU and shift so reconciliation runs ad-hoc instead of monthly. Do I own my transaction data? Yes — 100%. Export any timeframe via API or CSV at any time. Full audit trail retained for the period your plan specifies. No data-hoarding, no "premium analytics" paywall, no per-report fee. Your data is one of the deliverables of our platform, not a feature we charge extra for. ### faqs Which e-commerce platforms and ERPs do you integrate with? Pre-built plugins: WooCommerce, Magento, PrestaShop, nopCommerce, Shopify (app), Shopware. ERP: SAP, NetSuite, Sage, Primavera, Microsoft Dynamics. Custom integrations via REST API + webhooks — the whole API surface is 30+ endpoints, fully documented at docs.paybyrd.com. Most retailers are live in under a week; multi-store rollouts in 2–4 weeks. Which POS terminals do you support — and do I rent or buy? Both. PAX A77 (portable · tableside and poolside), PAX A920 Pro (countertop), Sunmi V3 (all-in-one ordering + payment), Sunmi T3 Pro (self-service kiosk). All PCI Level 1 certified, all receive over-the-air updates. Rent monthly with no long-term commitment, or buy outright — most retailers mix both (rent for seasonal pop-ups, buy for permanent storefronts). What does migration from my current processor look like? Phase 1 (week 1–2): sandbox certified, first test transaction captured. Phase 2 (week 3–6): one store or one channel runs parallel processing — Paybyrd handles 5–20% of live traffic while you compare diff reports against your incumbent. Phase 3 (week 7–12): graduated cutover with rollback in your hands. No "big bang" flip — you control every step. Multi-store groups close the full portfolio in 30 days with the standard runbook. Can I keep my existing acquirer contracts? Yes. Paybyrd is acquirer-agnostic — keep your existing acquirer agreements, your negotiated rates, your in-flight volume commitments. We orchestrate on top. If you later choose to consolidate, we can act as your acquirer across 90+ markets, but it stays a separate decision on a separate contract. No bundled lock-in. ### faqs How does Paybyrd reduce retail chargebacks and fraud? Four layers: (1) AI velocity scoring before authorisation, (2) 3DS2 step-up that shifts liability to the issuer, (3) a shared denylist across every Paybyrd merchant blocks known bad actors before the card reaches your rails, (4) device intelligence + behavioral biometrics catch card-testing bots at the source. Retailers on Paybyrd see roughly −16.8% chargeback volume in the first two quarters. Plus cross-channel refunds: an online payment refunds at the POS, a POS payment refunds online — removing the #1 in-store chargeback trigger. How does reconciliation work across multiple stores and channels? Gross settlement model. One daily payout, itemised by store, channel, outlet, SKU and shift. AI-powered ad-hoc reporting: "show me Store Porto's Mastercard volume yesterday 14:00–18:00" returns in seconds. No CSV exports, no manual matching against bank statements, no month-end marathon — and the same view covers web, POS, kiosk, mobile and PayByLink. Refunds, chargebacks and fees itemise per-line on the payout so your accounting team runs clean. Do you support mobile, self-checkout, and kiosk flows? Yes — all first-class, not afterthoughts. Scan-and-go via QR (guests scan with their phone, pay, walk out). In-app checkout via native iOS/Android SDK. Kiosk flows on Sunmi T3 Pro with unattended 3DS handling. Tap-to-pay on any NFC-capable phone (no extra hardware needed for small shops or pop-ups). Every mode settles into the same folio and the same payout. What AI features are available today? Three shipping-today capabilities: (1) AI reconciliation — cross-channel transaction matching, anomaly detection, discrepancy alerts; (2) AI dashboard assistant — ask natural-language questions, get PayLinks, pull transaction details; (3) AI fraud screening — velocity, device reputation, behavioral biometrics, cohort-wide shared denylist. No black-box scoring — every component signal stays visible on the review page. Are you PCI and GDPR compliant? Yes. PCI DSS Level 1 certified (the highest tier), PSD2-compliant 3DS2, GDPR-ready with EU-resident data storage by default. Tokenisation on every card so your systems never hold raw PAN data — scope reduction is immediate. Self-hosting available on Custom plans for regulated markets with stricter data residency requirements (Brazil, Angola, and specific EU jurisdictions). Can we manage payments across multiple store locations centrally? Yes — designed for multi-store from day one. Partner → Merchant → Store hierarchy with shared rule sets that cascade down (one top-level fraud policy applies to every store automatically, with per-store overrides where needed). Each store workspace stays fully isolated — a compromise at one never reaches another. Role-based access: HQ sees everything, Store Manager sees their store only, Regional sees their region. --- ## E-commerce — https://www.paybyrd.com/e-commerce Summary: checkout conversion lift; BNPL; local methods (iDEAL, MB WAY, Multibanco, Bancontact, Pix); recovery flows for abandoned carts; behind KuantoKusta E-commerce Payment Gateway — 20+ Methods, 1.25% | Paybyrd Online payment gateway from 1.25% + €0.08 with 20+ methods — iDEAL, MB WAY, Multibanco, Apple Pay — plus smart routing, decline recovery and antifraud. that finishes the sale. Smart routing, local methods, AI fraud, one-click wallets. A checkout that keeps picking up the revenue your competitors leave on the table. checkouts finished today recovered from smart routing approval rate · rolling avg The e-commerce payment gateway that finishes the sale. 7 of 10 carts leave. Here's the four fixes. Every abandoned cart traces back to one of four failures. Paybyrd handles all four — and shows you exactly how much they were costing you. due to checkout friction avg lost cart value Live before lunch. Not next quarter. Every day you're not processing is money on the table. 96% of merchants go live in one business day — with a plug-in or 10 lines of API. Three fields. Email verified instantly. Automated checks. No back-and-forth. WooCommerce, Magento, Shopify. One click. Sandbox pings. Webhook fires. First real euro in. The checkout where The right method at the right moment, auto-surfaced by country and device. Every method you enable recovers a cohort your competitors lose. For a merchant at €800k MRR. NL desktop + mobile Every toggle changes which customers check out. Most merchants enable 4+. Stop guessing why Full funnel intelligence, in real time. Filter by device, country, payment method, campaign — find the exact euro that's leaking. +4.2pp vs industry Industry avg: 82.3%. You're already above. Paybyrd shows you exactly which segment is dragging. Add to cart Checkout → Paid is 86.5% — 4.2pp above industry. Worth €38k/mo at your volume. Every euro accounted for. One dashboard. Every transaction. Refunds in one click. Chargebacks fought with your data automatically. No spreadsheets, no reconciliation nights. Avg 3s to original card Nightly → now Days → seconds Built. Tested. Shipping today for 400+ merchants. Conversion is five jobs. Every abandoned checkout traces back to one of these. Every one of them is shipping today. Every one of them compounds on top of the others. that don't make you type. The average mobile checkout asks for seven taps. Ours asks for two — and the customer never sees the form at all. Apple Pay, Google Pay, MB Way auto-surface by device and country. avg €800k merchant CHECKOUT · 7 FIELDS CVV / exp CHECKOUT · 0 FIELDS ⌐ Face ID to confirm The 47 approvals your gateway is losing. Decline hits, alternate acquirer takes it in 90ms. Your dashboard shows 920. Ours shows 967. Doesn't block your customers. AI risk score per transaction. 3DS only when the signal warrants it — frictionless for the 99.92% who don't. The 14th shouldn't be where subs die. Tokenized cards, smart retry, dunning and rescheduling. Renewals that would've failed — now recovered. Right method. Right country. MB Way for Portugal. iDEAL for Netherlands. Pix for Brazil. Apple Pay for Californians with iPhones. Auto-detected per checkout. All five pillars compound. Merchants on Paybyrd see +28% revenue in 90 days vs their legacy gateway. Every decimal point is a number on a P&L. One percentage point of approval rate on €100M of volume = €1M. We're not rounding up. Approval rate advantage Paybyrd vs. the competition. Production data from airline transactions. Impact shown on €100M annual volume . Your provider is on this list. lost at current rate at Elavon-level approvals 1,000 attempts · the mechanics Retry · alt acquirer 920 / 1,000 vs industry avg · rolling 30 days real merchant average recovered / year Pays for Paybyrd in the first week. Every week after is upside. From add-to-cart to confirmation — every tap, every drop-off, every euro, mapped live. Numbers below are from a real Paybyrd merchant, updated by the second. % of cart Abandonment recovery via email, WhatsApp, PayByLink One-page, mobile-first, native wallets surface first Smart routing · alt acquirer retry on decline Branded receipt · ERP webhook · next-sale prompt +12% vs yday Four stages. One dashboard. Every euro accounted for. Fraud gets stopped. You don't get stopped. A real-time engine that scores every transaction, fingerprints every device, and watches how every customer behaves on your form — before the money moves. Rules · Velocity · AI Last 24h · rolling Scored this hour Session · Human user Session · Bot / automation ⛔ BLOCKED · 98.2% Human · Real Bot · Blocked 1512 × 982 1024 × 768 Natural cursor movement · not automated Keystroke cadence · human-range No headless browser signals IP / geolocation / billing match Straight-line cursor · automation detected Zero dwell time between fields Headless Chrome + WebDriver flag Datacenter IP · no billing match in <50ms on every session. Every result feeds the scoring engine. evaluated · last hour Configurable rule engine 15+ condition types · velocity, pattern, geo-distance, BIN, temporal, ML scores. Visual builder, no code. Bot and script detection, headless browsers, device fingerprinting, VPN/proxy/datacenter flags. Mouse dynamics, keystroke timing, form-fill velocity, copy-paste patterns. Humans from automation. IP geo + reputation, email deliverability, phone validation, billing/shipping distance — instantly. Run new rules in parallel without affecting live decisions. See approval-rate and false-positive impact. AI case review Every flagged transaction comes pre-analyzed: fraud type, risk indicators, recommended action. Partner → Merchant → Store. Shared rule sets cascade down. Each workspace fully isolated. 12+ live widgets: country heatmaps, rule leaderboards, scheme breakdowns, peer benchmarks. This is just the preview The full antifraud platform Rule builder, case queue, shadow testing, device catalog, workspace hierarchy, analytics suite — the complete operator control panel. See it in full. ### testimonials Don't take our word for it. Tap to expand ### items Cart abandonment was our biggest leak. After implementing Paybyrd's checkout with Klarna and local methods like MBWay, we saw conversion jump meaningfully. The right payment method at the right moment changes everything. Head of Payments TAP Air Portugal Paybyrd gave us what no other provider could — a single integration handling 20+ payment methods across 90 markets, with approval rates that recovered millions in revenue we were leaving on the table. 700+ routes, thousands of daily ticket purchases — every one needs to clear instantly. Paybyrd gave us the speed and reliability our passengers expect, with zero downtime during peak booking windows. 0 downtime · peak Every straight answer. Questions we hear most from merchants on the fence. If yours isn't here, a payments specialist will answer in under one business hour. ### categories ### items Can I keep my current e-commerce stack? Yes. Paybyrd plugs directly into WooCommerce, Magento, PrestaShop, Shopify, nopCommerce, and any custom stack via a single REST API. No re-platforming. No retraining. No disruption. Most merchants install the plugin, run a test transaction in sandbox, and are processing real payments by end of day — typically under 4 hours from install to first live transaction. How fast will I actually go live? Under 4 hours is the average — signup to first real transaction. KYB verification runs automated for most businesses (completes in ~15 minutes). Plugin installs take one click. Integration test, webhook verification, and you're live. For custom API work, typical merchants ship in a day; complex enterprise rollouts complete in a week. Is the migration painful? What if it breaks my site? You migrate at your own pace. Paybyrd runs in parallel with your current gateway — switch 10% of traffic, verify the conversion numbers, then move the rest. Our onboarding engineers shadow your team through the first 72 hours with a shared Slack channel. Zero downtime is the default, not the premium tier. Why are your approval rates better than Stripe or Adyen? Three reasons. (1) Smart routing — we try multiple acquirers in milliseconds on soft declines, where single-acquirer gateways just give up. (2) Local acquiring in 40+ countries means cards are processed in-country, not cross-border — typically worth 2–4pp of approval rate alone. (3) 3DS orchestration that triggers only when risk signals warrant it. Net result: +3.12pp average approval lift vs. industry, independently measured in production for TAP Air Portugal and KuantoKusta. Won't a new checkout slow down my site? The opposite. Our hosted checkout loads in <400ms on 4G mobile (real user monitoring, 95th percentile). The inline SDK is 18KB gzipped. Apple Pay, Google Pay, and saved cards fast-path bypass the full form entirely — most returning customers complete checkout in under 3 seconds end-to-end. We publish our Core Web Vitals monthly. How much will cart abandonment actually drop? Industry average is 70%. Paybyrd merchants see 51–58% abandonment — a 12–19 percentage-point improvement. The levers: one-page mobile-first checkout, locally relevant methods (MB Way in PT, iDEAL in NL, Klarna EU-wide), native wallet fast-path, and smart-retry on soft declines. KuantoKusta saw a 19% abandonment drop in the first 60 days after switching. What about transaction latency at peak? Scoring latency is sub-50ms P95. End-to-end payment authorization averages 680ms including 3DS challenge prompts. Infrastructure is multi-region active-active across EU and Americas with auto-failover. 99.999% uptime SLA in our enterprise tier. During Black Friday 2024, Paybyrd processed 14× average volume with zero customer-visible degradation. How do you reduce fraud and chargebacks? Real-time scoring on 47 signals per session: IP intelligence, device fingerprinting, velocity counters, email reputation, behavioral biometrics (mouse dynamics + keystroke cadence), and ML risk models. 3DS fires only on flagged transactions so the 99.92% of legit customers sail through. Our merchants see −38% chargebacks on average, with a 0.08% false-positive rate. PCI compliance, GDPR, data residency — how's that handled? We're PCI DSS Level 1 certified (audited annually by an external QSA). Tokenization reduces your PCI scope to SAQ-A — the lightest assessment. GDPR: all EU merchant data is processed and stored in EU regions (Frankfurt + Dublin), no data ever leaves the bloc unless you explicitly opt in. PSD2 SCA and 3DS2 are built in, not bolted on. What happens if a customer disputes a transaction? Paybyrd pre-assembles the evidence package: transaction metadata, IP, device fingerprint, 3DS authentication result, delivery confirmation (if provided), and scoring history. Your team reviews and submits with one click. Win rates on disputes run 2.8× the industry average. If a chargeback is clearly fraud our team represents the case on your behalf. What does it cost? Any hidden fees? From 1.25% + €0.08 per transaction, depending on volume and method mix. €0 setup. €0 monthly. €0 for chargebacks in your first 30 days. No minimum volume, no per-API-call fees, no markup on cross-border that isn't already disclosed. We publish our full rate card; we don't negotiate it behind closed doors and then charge you more. What if my current provider is cheaper on paper? Usually they're not once you add the cross-border surcharge, the PCI audit fee, the chargeback fee, the monthly platform fee, the authorization fee, and the ad-hoc FX markup. We built a TCO calculator that accepts your last three months of statements and shows the real number. Merchants who switch see an average effective-rate drop of 12%, before approval-rate gains. Can I cancel anytime? What's the lock-in? Cancel anytime with 30 days' notice — no termination fees, no exit penalties. The first 30 days include a money-back guarantee on all commissions if you're not satisfied. No multi-year contracts. No break clauses that only protect us. If we're not earning our 1.25% every month, you shouldn't be paying it. Who do I call when something breaks at 2am? A human, in Portuguese, English, Spanish, or French. Median response time for priority tickets: 4 minutes. Our 24/7 support team is based in Lisbon and Madrid — not outsourced, not a chatbot tree. Every Paybyrd merchant gets a dedicated account manager from day one, with their direct line on file. During outages you get a WhatsApp update every 15 minutes, not a status page that lags reality. How do refunds and reconciliation work? Refunds: one click in the dashboard or one API call — processed instantly with an ARN reference returned to the customer on the spot. Reconciliation: AI-powered dashboards unify across your webstore, marketplaces, BNPL providers, and POS. Gross settlement means your bank receives predictable daily payouts — no surprise fee deductions at month-end. Webhooks fire into your ERP automatically. Can I expand internationally without payment expertise? That's exactly what Paybyrd was built for. 20+ methods, 192+ currencies, local acquiring in 40+ markets. Launch in a new country with one API call — the right methods, the right currency, the right compliance, the right language — all surface automatically based on the customer's IP and browser. No new integration per country. What makes Paybyrd different from Adyen or Stripe? We're not trying to be the biggest, we're built to be the best for merchants who process €1M–€500M/year. That band is underserved by giants (who focus on the Fortune 500) and undercapacitated by small processors. You get Fortune-500-grade infrastructure with a named human account team that actually picks up the phone. Our approval rates consistently beat the large processors by 1.7–4.9% in head-to-head production tests. --- ## Omnichannel — https://www.paybyrd.com/omnichannel Summary: one customer across every channel; unified ledger across POS + web + link + mobile + kiosk Omnichannel Payment Platform — POS, Online, Mobile | Paybyrd One omnichannel payment platform for POS, web, mobile, kiosk and payment links: one customer profile, one ledger, one contract. 20+ methods, 192+ currencies. POS, web, mobile, kiosk, WhatsApp — Paybyrd is the payment brain that remembers every interaction and pays out as one. 5 channels, 1 ledger Same customer recognized everywhere One reconciliation, one payout Omnichannel payments means one contract, one ledger and one customer record across POS terminals, online checkout, payment links, mobile and kiosk, so a sale in any channel reconciles in the same place. Omnichannel payments: one customer, every channel, one view. Your customer isn't split. Your payments shouldn't be either. Same person, five touchpoints, one decision. Legacy stacks treat each as a stranger. Paybyrd recognizes them everywhere — and carries context with them. Five systems. Five silos. Terminal vendor A One brain. Every signal. €142 · In-store · 14:22 €89 · Checkout · 16:08 €24 · App · 18:31 €56 · Self-service · 19:05 €312 · PayByLink · 20:40 What it actually looks like on the shop floor. Happening right now Lift the bottle. Scan the tag. Paid before she reaches the counter. 14:22 — checked out on the couch. 16:04 — collected at the counter. Same transaction. Started the return from the sofa. Finished it in ninety seconds. Funds back on the card. Saw the queue. Opened the app. Scanned to buy. Walked out. ### scenarios Customers don't live Your payments shouldn't either. Six flows that used to live on email threads — now one transaction, one customer, one ledger. Click & Collect 01 / Click & Collect Collected at the counter. One transaction. Two channels. Your staff scans the QR, the customer walks out with the goods. You never touch the settlement. One rail · same customer ● Order placed Sneakers · Size 42 ● Settled · same rail 02 / BORIS Returned at the counter. Scan the receipt. Funds back on the original card before the customer leaves the store — ARN, audit, and inventory update included. Web · 3d ago Wool jacket · Size M €149.00 · Visa ••4821 Refunded to Visa ••4821 ARN 7492-1183-4821 · instant 03 / Tap-to-Pay QR Sticker on the table. Customer scans. Apple Pay, Google Pay, or any local wallet. Paid before the waiter walks back. A printed sticker. TABLE 4 · SCAN TO PAY Pay Café · €8.40 ✓ Pay with Face ID 04 / PayByLink Send a payment where they already chat. WhatsApp, SMS, Instagram, email, or your app. Generate a link, they pay, you're done. Same ledger as your storefront. Under 4 minutes Can I order the mug set + candles? Sure! Here's your link → Just paid ✓ Thanks! Shipping tomorrow. 05 / Self-service Kiosk that actually bust queues. Full-screen kiosk, fully branded, running on Paybyrd hardware. Syncs to your main POS in real time. No separate backend to babysit. Syncs to POS · real-time 06 / Auto-loyalty before they ask. Returning customers spotted at the card tap. Rewards, discounts, and tier bumps applied silently — no app, no card, no "do you have our app?" Maria Silva recognized 42 visits · Gold tier · LTV €6.2k Gold tier: 10% off applied No coupon, no prompt seen in full. Five channels, one record. Not a transaction log — a living profile that tells you who, when, where, and what to do next. paybyrd · customer intelligence Recognized on every channel Monthly spend · 12 months Last 72 hours · every channel Every receipt tells a story. Paybyrd reads every one. Lisboa · Portugal Push Friday 10% offer Send Thu 12:00 Buys Fri 18:00 · 78% confidence Algarve · Portugal Offer spa on next arrival 4 prior stays included spa · 82% 2 weeks ago Porto · Portugal Activate 2nd-purchase offer Next 3 days Day-14 churn cliff · 61% risk Every line you've read so far — backed by a number, a customer, or a contract clause. No marketing asterisks. 01 / Conversion They finish paying. Fully white-labeled checkout. Every method your customer reaches for — already there, mobile-first, PSD2-ready. Select payment method SSL · PCI DSS L1 Powered by Paybyrd Pay with MB WAY Visa, Mastercard, and more Pay with your PayPal account Buy now, pay later Pay with your bank account Avg signup → first tx No card required + €0.08 fixed Every commission refunded 02 / Performance Numbers that outpace the spec sheet. Smart routing, local acquiring, real-time retry. The rate creeps up quietly, month after month. Approval rate · 30 days Rolling · all methods 03 / Human support Someone picks up. Real humans in Europe. Dedicated account manager from day one. The phone is answered in Portuguese, English, Spanish, and French. Lisbon · Madrid · Porto We had a customer in the middle of a €12k transaction that wouldn't authorize. I called support, someone answered in under a minute, and it was resolved before the customer walked out. Try that with your last payment provider. Carlos Rodrigues · CFO, Vila Galé Rolling 90 days Ops always on 04 / Hardware The gear that doesn't quit. Android-powered. PCI 6 SRED certified. IP65 water and dust resistant. Our software pre-loaded. Over-the-air updates included. Buy outright or rent monthly — cancel anytime Free 4G SIM included on every device Built-in printer, scanner, NFC, and camera On-site swap within 24h · spares stocked in Lisbon & Madrid Reception, restaurant, spa, golf, kids' club — a guest can tap once, charge anywhere on the property, and we reconcile it all in one close at night. Paybyrd made that possible across 40+ hotels in four countries. CFO, Vila Galé 3d → 2h Close across 40+ properties POS · Web · Mobile · Kiosk · Link Folio follows the guest Was five spreadsheets What one platform ### items Is a POS sale and an online sale the same customer record? Yes. A card used at the terminal and the same card used at checkout resolve to one customer through network tokens, so purchase history, loyalty and recognition follow the customer across channels. Do I need separate contracts per channel? No. POS terminals, online checkout, payment links, mobile and kiosk sit on one contract, one integration and one dashboard, with one payout and one invoice. Which channels are covered? In-store terminals and tap-to-pay on Android, hosted online checkout, payment links, in-app payments and self-service kiosks. Can a customer buy online and return in store? Yes. Because the sale and the refund are on the same ledger, a return in store against an online order settles against the original transaction rather than as a fresh, unmatched payment. How does reporting work across channels? Every channel writes to the same ledger, so reconciliation is by outlet, SKU or channel from one view rather than from one export per provider. --- ## POS — https://www.paybyrd.com/pos Summary: Android POS lineup (PAX, Sunmi); rent-or-buy; SoftPOS tap-to-pay; MDM for fleet management; InstaTax-free retail; behind Rede Expressos (700+ routes) for the counter. Not the pitch deck. Running Android POS at mass scale since 2017 — before anyone else even tried. PCI 6 SRED certified. Nine years of shipping the lineup your staff will never fight with at Saturday rush. Sunmi V3 Mix Android 12 · PCI 6 SRED 4G + Wi-Fi Free SIM · zero-touch NFC · EMV · MSR QR · Wallet · PIN 58mm · silent · auto-cut Android POS rolled out at mass scale 100k devices across EU 1M+ devices · still shipping POS terminals from €11/month, built for the counter. Not the pitch deck. Every counter covered. Android-only. Certified to PCI 6 SRED. Paybyrd software pre-loaded. Each one built for a specific counter — not a compromise. The smart handheld. Carry it. Tap at the table. Close deals wherever they happen. Restaurants · Events · Field 5" HD · touch 4G · Wi-Fi · BT The countertop champion. The retail staple. Big screen, built-in printer, never out of battery. Retail · QSR · Counters 5.5" HD · touch AC-powered + backup 4G · Wi-Fi · BT The unsinkable tower. The counter star. Customer-facing screen, silent printer, brand-ready. Hotels · Premium retail · Kiosks PCI 6 SRED · EMV L1/L2 The full-counter workstation. The everything-desk. Dual display, cash-drawer ready, runs the whole shift. QSR · Self-service · Checkout 15.6" + 10" customer Drawer · scale · scanner PCI 6 SRED · EMV L1/L2 The hardware is the easy part. The software is why it ships. Nine years of opinionated choices, baked into every tap, refund, and sync. One unified OS across every device in your fleet. Staff trained in ten minutes. Your brand, not ours, on every screen. Paybyrd OS · running on Renegade · PAX A77 Works with your stack + 40 more Your brand on every screen Fully white-label lock screen, boot logo, tip copy, receipt layout, wallpaper. Your customers never see Paybyrd — unless you want them to. Lock screen live. Logo, wallpaper, wake copy — all yours. Loyalty that recognises the tap Returning customers detected the moment the card touches the reader. Discounts applied before they ask. No cards, no apps, no awkward pauses. Card matched in 180ms · discount applied pre-auth. Tip prompts that lift takings Contextual suggestions by service, ticket size, and location. Opt-in, never forced. The average guest pays happily. One-tap gratuity · no friction, no guilt. Price in their home currency Show the total in the shopper's native currency with DCC handled automatically. Higher conversion on tourist and cross-border transactions. DCC rate locked 60s · tourist conversion +7%. Refund in one tap Match the receipt, confirm, done — back on the original card with an ARN in under three seconds. No ops ticket, no hold music. Issued 2.7s ago · ARN 24 9187 23 045. Offline mode · online sync Wi-Fi dropped mid-rush? Keep selling. Transactions queue locally and settle the instant connectivity returns. Connection lost · store-and-forward engaged. per register, typically with DCC out of the box Android across the fleet end-to-end, with ARN Running Android POS at mass scale since 2017. The rest of the industry still hasn't. One OS, one update pipeline, one SDK. Your whole fleet upgrades overnight — not spread across three generations of Telium, Verix, and proprietary firmware forks your supplier quietly stopped supporting. The bet, year by year Android POS rolled out at mass scale across Iberia. PCI 5 certified fleet-wide. OTA pipeline live. Paybyrd OS v2 — unified fleet SDK shipped. PCI 6 SRED across every active device. 4 terminals. 192 currencies. One OS across it all. Every terminal you'll ever run. A full payments stack behind every Paybyrd terminal. Native SDK. Remote triggers. OTA fleet management. Every European payment method, one integration. Plug it in — ship in days, not quarters. Plug in payments with a single Intent. Your app calls our SDK via Android Intents or JavaScript. We handle PCI compliance, card reading, tokenization, and authorisation — you get a clean APPROVED or DECLINED callback. Web POS? Same SDK, JS flavour. Zero scope inherited Waiting for SDK call callback · 1.8s avg Fire a payment from the cloud. Pass a terminal's serial number via REST API. The device prompts the cardholder, you receive the result via webhook. No cables, no pairing, no middleware. OTA fleet mgmt Deploy to 50 or 50,000 at once. Push updates, deploy apps, configure settings across every active device — without a single site visit. Staged rollouts, rollback in one click. Stage 1 · Zero-touch provisioning Stage 2 · OTA deployment Stage 3 · Healthy — rollback ready Awaiting provisioning stream... ⟳ OTA v5.12.3 → 21 terminals ✓ Deployed to 6 stores · 21 terminals Every way they want to pay. One terminal. Card, MB WAY, SEPA, iDeal, PayPal, Klarna, Revolut Pay, Pay by Link, Floa, Multicaixa — all on one device. Switch methods mid-checkout without remapping the UI. All enabled · zero config paybyrd · fleet · all stores last sync · 1 offline · 2 updating +18% vs last Wed Tip flow + security patches · 12 MB Devices · live One dashboard · Ops + IT + Finance · same screen rolling 12-month SLA DSS + PIN + P2PE ERP · POS · E-comm · PMS < 1 wk sandbox → production Six counter moments. All muscle memory. Trained in ten minutes. Every flow designed with real baristas, waiters, and shop staff — not payment engineers. The boring parts, boringly perfect. The moments that matter, built to delight. Featured · Tips system Tips that lift takings. A tip prompt that respects the guest and rewards the staff. Contextual by ticket size, service, and time of day — opt-in, never forced. Attribution to the person who earned it. Daily payouts, so your team sees it the moment they leave their shift. Opt-in by default. Guests see a gentle "add a tip?" — never a pressured ask. Skip is one tap. Four amounts tuned to ticket size, service type, and local norms — not a generic 15/18/20. The server who rang the ticket gets the tip. Splits, pooling, and tronc models all supported. A little "Thanks!" with the staff member's name on screen. Small moment, big morale. Turn it on in minutes · roll it back in seconds Contextual prompt · staff-attributed €0.90 for Maria · €47.20 today ### cards Tap to pay NFC, Apple Pay, Google Pay, and contactless cards. Two seconds from tap to approved. Chip + PIN EMV L1/L2 certified, PCI 6 SRED hardware. Clean chip insert, four-digit entry. Pay at the table QR code on the receipt, scanned at the guest's pace. Split totals calculated live. Split the bill By head, by item, or by percentage. Running totals tick up as you tap each name. Match the receipt, confirm, done. Back on the original card with an ARN in three seconds. Pay by link Generate on the terminal, send via SMS or WhatsApp. Lands in your ERP the moment they pay. Pay as you go, or own it outright. Cancel anytime. Swap within 24 hours. Most merchants start with rental — switch to ownership when the fleet stabilizes. Cancel anytime · free swap One-time · full ownership 4G SIM included 24h swap guarantee 2-year hardware warranty Rental includes replacement, updates, SIM, and swap. Buy is straight CAPEX. Break-even is month 21 — most merchants happily keep renting for the coverage. Ready to ship tomorrow. Free delivery across the EU, 30-day no-questions trial. The smart handheld. The countertop champion. The unsinkable tower. The full-counter workstation. Now with instant payouts Eligible POS merchants can pay out today's takings on demand, in seconds, from €1. Daily settlement stays included. How instant payouts work Tourists pay less. You earn more. Every foreign card that taps your reader is a missed tax-free refund — and a missed revenue share for you. Paybyrd InstaTax detects eligible tourists automatically, offers the refund right on the terminal, and deposits your cut into your account. No integrations, no staff training, no paper forms. Detected at the tap. Refunded without the friction. A foreign card touches the reader. InstaTax pattern-matches the BIN against eligible issuers in under 200ms, surfaces a gentle tax-refund prompt, and — if the shopper accepts — generates a digital claim they finish on their phone. No printed slips, no app downloads, no trained-up baristas. Runs on your existing terminals. If it's Android, it's InstaTax-ready. Activated remotely — no new hardware. Zero staff training. The terminal asks the question. Your team keeps ringing up coffees. Works with any of your existing acquiring arrangements. We plug in behind the scenes. Ready in a day. No integrations. No legal marathon. Most merchants are live within 24h of saying yes. InstaTax · live flow Detecting foreign card origin… Tax-free refund offered on-screen Refund scheduled · you earn your share A foreign card taps the reader. InstaTax identifies eligibility in under 200ms. A gentle refund prompt appears on the terminal. Guest taps yes, gets an SMS link. Claim is completed on mobile. Customer gets the VAT back. You earn your share. higher income versus any other tax-refund platform more eligible tourists actually complete their claim tax-free volume run through the platform in 2023 shoppers refunded without downloading an app The tax-free revenue hiding in every foreign tap. Activate InstaTax on your existing Android fleet today. Most stores are live the same day and seeing new revenue on the first weekend. Talk to sales Retail, hospitality, beauty, eyewear. Different shifts, different ticket sizes — the same four Paybyrd devices and the same Android OS running under them. Tap to expand For a premium retail brand, every touchpoint matters — including payment. Paybyrd gave us terminals that match our store experience and analytics that help us understand our customers better than ever before. In a restaurant, speed is everything. Since switching to Paybyrd's terminals, our table turnover has improved and checkout complaints have dropped to near zero. The system just works — every single service. ~0 checkout complaints Fourteen stores, hundreds of brow and lash appointments a day. Paybyrd's terminals keep our rhythm — checkout is as quick as a finishing touch, and the real-time analytics show us which stores convert and which customers come back. 14 stores · 1 fleet The terminal matches our aesthetic, handles Apple Pay and MB WAY seamlessly, and the loyalty programme runs on it directly. Our guests feel the care in every detail — including checkout, which most spas get wrong. +23% loyalty signups What operations teams ask before they switch. Nine years of merchant conversations, compressed into straight answers. If something's missing, a human is one message away — no bots, no ticket queue. ### items Can I keep my current terminals and just switch to Paybyrd software? If they're Android-based PAX or Sunmi devices with recent firmware, yes — we flash Paybyrd OS on your existing fleet in under an hour per device, fully remote. Legacy Telium, Verix, or proprietary locked-down terminals can't run Paybyrd; we swap those out in a staged rollout with zero sales downtime. What happens if a terminal breaks at Saturday lunch? A replacement courier is dispatched inside the hour. Most swaps arrive within 24h — often within 4h in Lisbon, Madrid, Porto, or Barcelona. We hold same-model spares at the nearest regional hub. You never count cash at the till because we couldn't ship fast enough. Does it really work offline? Yes. Every Paybyrd terminal has store-and-forward mode. Transactions queue locally and settle the instant connectivity returns. You can sell through a Wi-Fi outage, a 4G dead zone, or a power dip onto battery. Typical buffer: 500+ transactions per device. Zero dropped sales. Should I rent the terminals or buy them? At €199 for Maverick and €225 for Renegade or Rawhide, buying breaks even on rental in roughly 17 months. Titan (€599) is the one device where long-term rental keeps winning on TCO once you factor in swap + SIM + OTA coverage. Rent if you're scaling, buy if the fleet is stable — most merchants rent the first year and transition to ownership as operations settle. Can I customize the terminal screen with my own branding? Fully. Lock screen, boot logo, tip prompt copy, receipt layout, color scheme, and language — all white-labeled. Your customers see your brand end-to-end; Paybyrd stays invisible unless you choose to show us. Typical rollout: one day once we have your brand assets. How do I train staff to use the new terminals? Ten minutes per register, typically. The UI is a consumer-grade Android app — anyone who has used a smartphone already knows the gestures. We run shadow-mode rollouts where old and new terminals coexist for a week so staff learn without pressure. Zero sales lost to ramp-up. Does it integrate with my POS, ERP, or inventory system? Pre-built connectors for SAP, Oracle, Host PMS, Newhotel, Moloni, Vendus, Primavera, WooCommerce, Magento, Shopify, and 40+ more. For custom stacks, a REST API + webhooks your engineers can integrate in an afternoon. If your POS runs on iPad or Windows, we ship a companion app that pairs with the terminal in minutes. What about PCI compliance and my liability? Paybyrd is PCI DSS Level 1 certified end-to-end, with PCI 6 SRED hardware on every active device. Using our terminals collapses your PCI scope to SAQ-B-IP — the lightest questionnaire for physical devices. We handle every annual re-certification cycle; your bank stops sending PCI questionnaires. How does Paybyrd InstaTax (tax-free refunds) actually work? When a foreign card taps the reader, InstaTax matches the BIN against eligible tourist-issuing banks in under 200ms. If eligible, the terminal quietly offers the refund right on screen — the customer completes the claim on their phone via an SMS link. No paper forms, no staff training, no downloads. You earn a share of every completed refund, paid out daily. Remote activation on your existing fleet takes a day. Will the tip system actually increase what my staff takes home? Merchants typically see +23% gratuity uplift from smart contextual prompts versus flat amount entry, and repeat tipping climbs once the staff member's name shows on screen. Tips are opt-in, never forced, and paid out daily to the server who rang the ticket. Pooling, splits, and tronc models are all supported. Most teams prefer it within the first shift. Can my developers build directly on your SDK? Yes — we publish a native Android SDK (Intents + typed callbacks), a JavaScript SDK for web-based POS, and a full REST API for cloud-triggered payments. Sandbox access is free and delivered within 24h of signup. PCI scope stays with us — your app never touches card data. A typical first integration ships in under a week. Do I have to change acquirers to use Paybyrd? No. Paybyrd is acquirer-agnostic — keep your existing banking relationships, your current processing rates, your in-flight contracts. We run on top of them. If you do want to consolidate, we can also act as your acquirer across 90+ markets, but that's a separate conversation. --- ## Antifraud — https://www.paybyrd.com/antifraud Summary: 55 fraud signals, 47ms decisioning, device + IP + behavioural intelligence, rule builder, case review, shadow-mode deploys, merchant-hierarchy rulesets Payment Fraud Prevention — Real-Time Antifraud | Paybyrd Real-time payment fraud prevention built into the gateway: device, IP and behavioural signals, visual rule builder, shadow mode, case review. PCI DSS Level 1. scored in 47 milliseconds. Fifty-five fraud signals. One decision engine. Zero tickets in the morning. Paybyrd Antifraud scores every payment before it reaches your acquirer — blocks the attackers, passes the shoppers, and explains every call your analysts need to review. in exposure prevented Watch it live Rules + AI + device · every payment VPN · Tor · datacenter · threat score History · reputation · biometrics Paybyrd's own payments book — now yours to deploy Watch the engine work. Every transaction. Every outcome. Explained. The monitor below is synthetic — but every signal, score, and rule you'll see is the real engine. Plug in a sandbox key and your own traffic flows through this exact pipeline. Live · synthetic load · eu-west-1 Rules · Velocity · AI · Device · IP Passed · 60s Blocked · 60s €84.20 · MB WAY · restaurant · domestic BIN €1.00 · velocity · 12 BINs in 22s · card tester €1,420 · Amex · check-in · step-up issued · OTP ok €38.50 · Visa Debit · subscription renewal · trusted device €892 · residential proxy · geo mismatch · 4 cards Every decision explained. Every transaction passes through Pre-Auth Screening, Issuer Authorization, and Final Decision — each stage scored, each score visible, each reason logged. This is the actual detail view your analysts will see in the console. This transaction requires manual review Approved: score 300 from 2 rules, below thresholds. Apr 20, 2026 · 10:57:12 Velocity, device reputation, and IP intelligence checked before the card is even sent to the issuer. Fast-path for trusted sessions — no friction added. Apr 20, 2026 · 10:57:13 Transaction sent to the issuer through the acquirer most likely to approve this BIN. Response captured, rate applied. Sent to review by 4 rules. Apr 20, 2026 · 10:57:13 Post-issuer analysis fires our review rules — velocity surge, device risk, BIN country mismatch. Human-in-the-loop for the €420 threshold your team set. Know where the payment is actually coming from. Every online payment originates from an IP address. Our IP Intelligence module answers two questions instantly: where is this person is this person hiding Resolved · 12ms Card-issuer → Session location Lisbon · Caixa Geral Nairobi · Safaricom Geo-distance > 4,000 km from issuing country ISP: Safaricom Mobile — legitimate consumer carrier No VPN, Tor, datacenter, or known-attacker match geo-distance > 4000 → review Send to review Stops fraud before it costs money — no chargebacks, no scheme fines. Buyer location to the city level Legit consumer ISP or suspicious provider Kilometres from the card's issuing country Anonymisers masking real location Fraud rings routing through real homes Bots running from AWS, GCP, Azure, OVH IPs flagged in global threat intelligence Automated card-testing attacks Aggregate IP risk in a single metric Has this IP touched our platform before? Know the device, not just the transaction. Instead of scoring a single payment in isolation, Device Intelligence builds a persistent profile of every browser and phone that touches your checkout — and follows that profile across every merchant on the platform. All 45+ signals rolled up. Your rules don't need to fire on 40 signals. The Device Risk Score rolls them all into a single 0–100 metric — and every component stays visible on the review page when your analyst needs to drill in. ### categories Device history · global Has this device been seen before? Days since first seen across every Paybyrd merchant Total visits, ever Number of distinct merchants visited New-device flag (0-7 day threshold, configurable) A device brand-new to the entire platform carries different risk than one seen 200 times over 6 months. Context beats context-free scores every time. Has it been seen at THIS merchant? Visit count scoped to this merchant only Last purchase on this merchant Cross-merchant vs same-merchant pattern A device trusted by Merchant A might be brand-new to Merchant B. The rule engine lets you weigh both — cross-merchant reputation AND your own history. What's this device's track record? Chargeback rate on past transactions Unique cards used from this device Unique emails & phones bound to this device Manual approve/decline history from your analysts Aggregate reputation score (0-100) A device that's used 15 different cards is almost certainly a fraud tool. Reputation aggregates historical signal into one number your rules can pivot on. Is the buyer hiding their tracks? Private / incognito browsing detected WebView inside an app (common in phishing kits) Browser automation — Selenium, Puppeteer, Playwright A shopper with DevTools open and incognito on is inspecting your checkout — not buying. These signals separate real visitors from reconnaissance. Does the user act human? Mouse movement naturalness Typing speed & keystroke count Paste events on card / CVV fields Form-fill duration (200ms = bot, 20-40s = human) Aggregate behavioral risk score Bots type instantly. Humans don't. Bots paste whole card numbers. Humans usually type them. This is the layer that catches the sophisticated attack no static rule will. Is this device lying about itself? User-Agent spoofing — claims Chrome/Mac but isn't Headless browser detection Antidetect / fraud browser fingerprint Canvas noise injection (fingerprint evasion) Aggregate spoofing risk score Professional fraud rings buy antidetect browsers to look like clean devices. We detect the forgery itself — the browser is lying and we know it. Bots type instantly. The same checkout, filled by a human and a bot. Same card number. Same IP even. Behavioral biometrics separate them in under two seconds — here's how. mouse · natural arcs · 240 px/sec Human · 3.2 chars/sec variance 28.4s · in range Natural arcs · no jumps 12 / 100 · Pass mouse · teleport jumps · no velocity 0 keystrokes · full paste 3 · on sensitive fields 180ms · impossibly fast 96 / 100 · Block Compose rules your team Visual rule builder. Drag signals, pick operators, choose an action. No SQL, no code, no support ticket to change a threshold. Below are the exact seven rules most risk teams deploy in their first week. Seven starter rules · deployed week one 15+ condition types · velocity · pattern · geo-distance · BIN · temporal · ML scores · device · IP · behavioral High-risk devices outright First-time devices making large purchases Card-testing: a device cycling through stolen numbers Automated form-filling with pasted stolen credentials Bots running without a real browser Devices with a history of chargebacks Anonymous first-time visitors Your analysts' morning isn't a ticket queue anymore. Every flagged transaction lands in Alerts with SLA countdown, assignee, triggering rule and one-click Approve / Decline. No spreadsheet exports, no CSV joins, no "let me check with the acquirer". Status · All Assigned to · Any 20 Apr 2026, 11:42 High-Value Fraud Risk 20 Apr 2026, 11:38 Card Testing Attack 20 Apr 2026, 11:31 Velocity · 12 BIN/22s 20 Apr 2026, 11:22 Geo-mismatch · 4,814 km 20 Apr 2026, 11:08 20 Apr 2026, 10:54 ThreatScore > 85 Approve / Decline / Escalate No SQL, no support ticket Per-rule response windows Alert triggers · auto-escalation Full audit trail Every action logged Analyst · decision · reason · timestamp Your Head of Risk opens this at 08:45. Every metric live-updating, every chart breathing, every anomaly highlighted before the coffee is made. Configurable widgets — add a shadow-pass-rate line, swap the world map for a merchant ladder, drop in a rule-firing heatmap. 20 Apr · 08:45:21 Good morning, Luiz Here's your fraud operations overview · since last login. with unusual decline spike today decline rate > 10% 7-day approval heatmap Hour-by-hour approve rate · click a cell to drill in Tue 11:00 · 94% Sun 03:00 · 64% Transaction origins · live Pulsing dots scaled by volume · trailing 7 days velocity · 12 BINs · 22s €84.20 · MB WAY · trusted device €1,420 · check-in · step-up OK headless browser · DevTools open €38.50 · Apple Pay · recurring residential proxy · geo mismatch ThreatScore 78 · new device + large order 12+ configurable widgets. Alert strip · approve/decline · flagged for review · top rules · merchant risk · country breakdown · shadow pass rate · rule-firing heatmap · 7-day trends. Add, remove, rearrange. Deploy without fear. Measure before you break anything. Run a new rule set in shadow — it scores every live transaction in parallel but doesn't affect the decision. Compare shadow vs. production side-by-side in the dashboard, then promote the rules that moved approvals up without moving false positives. Live · affects decisions €8,420 in fraud prevented · Shadow · scores but doesn't decide +3.1 pp vs live −3.1 pp vs live €9,100 prevented · 2 chargebacks · −33% Shadow vs Live · 7-day moving average Live rules · 83.3% Shadow rules · 86.4% +3.1 pp uplift One ruleset at the top. Every brand inherits it. Built for agencies, hotel groups, franchises, and marketplaces. Shared rules cascade down. Each workspace stays fully isolated. Overrides at any level when one brand needs a tighter policy than the rest. Paybyrd Pay Group Baseline rules · compliance guardrails · shared denylist 3DS2 · mandatory ThreatScore > 80 → decline Tor → decline Nova Hotels Group Hospitality overrides · folio-aware Airline overrides · GDS aware E-commerce overrides · global ship Top-level policies automatically apply to every merchant and store below — unless explicitly overridden. Each merchant's data, users, API keys, and audit log are fully isolated — a compromise at one never reaches another. Shared threat intel A bad actor blocked at one merchant is flagged instantly across every other — the denylist is platform-wide by default. Three ways in. All of them small. Use Antifraud standalone (inline API), fully orchestrated with our gateway + acquirer mesh, or subscribe to webhooks and keep your own stack. Sandbox in 24 hours · first real decision by end of week one. Score every transaction before auth Single REST call. Fires on your checkout, gets a decision in <50ms, you route accordingly. Zero change to your acquirer integration. Sits between checkout and acquirer Paybyrd handles both — antifraud decision + acquirer routing. One integration covers fraud, acquiring, tokenisation, 3DS2. Most popular for new merchants. React to decisions after the fact Get fired-rule events, SLA breaches, shadow-mode diffs delivered to your endpoint in real-time. Drop into Slack, PagerDuty, your own risk engine. Sandbox in 24h · first decision by end of week one. REST, webhook, or orchestrated — all three supported from day one. Swap between them later without re-integration. The questions risk teams ask before they commit. Every objection we've fielded in the last two years, answered honestly. If something's missing, the team replies in under 4 working hours. ### categories ### faqs How many fraud signals do you actually evaluate? 55+ per transaction — 10 from IP Intelligence (country/city/ISP/geo-distance + VPN/proxy/Tor/residential/datacenter/known-attacker/bot + threat score), 45+ from Device Intelligence across 7 categories (global history, workspace history, reputation, environment, behavioral biometrics, spoofing, composite score). Plus the transaction-level signals your rules access directly: amount, BIN country, shopper email domain, velocity windows, currency, etc. Do you use ML or rules? Both — rules run first because they're explainable and fast, ML runs in parallel and contributes weighted scores into the composite. Every ML signal is still visible on the review page so your analysts can see exactly why the score moved. Black-box "trust us" scoring is explicitly out of scope. Can I add custom signals from my own data? Yes. Pass any field from your checkout (loyalty tier, internal risk score, cohort ID, CRM segment) into the scoring call — it becomes available in the rule engine as a first-class signal. Custom ML features can be trained on your data in a dedicated workspace for merchants on Custom plans. ### faqs How long does it take to go live? Sandbox access in 24 hours. First real scoring call by end of week one. Production cutover typically in 2–3 weeks with shadow mode running in parallel first — your team sees impact on their existing traffic before any decision changes. A full multi-property rollout can close inside 30 days with the standard runbook. Do I have to change my acquirer integration? No. Use Antifraud inline via one REST call, fire it before you authorise. Your existing acquirer integration is untouched. The orchestrated mode (Paybyrd gateway + acquirer mesh + antifraud together) is available if you want the full stack, but it's never required. Can I run it alongside my current fraud tool? Yes — many merchants do this for 2-3 months during evaluation. Paybyrd runs in shadow mode, scoring every transaction but deferring the final decision to your incumbent. You compare outcomes daily. When the numbers justify the switch, you promote Paybyrd to live and the incumbent goes silent. Zero traffic blown up. ### faqs What's included in the headline rate vs. charged separately? Scoring, rule builder, case review, shadow mode, dashboard, API access, webhooks, SLA tracking, 15+ condition types, composite scores, behavioral biometrics, device + IP intelligence, multi-tenant hierarchy — all included. No per-signal pricing, no ML-feature upsell, no "enterprise edition" paywall. Priority support and named TAM are included on Custom plans. What's your SLA? 99.999% platform uptime, contractually backed with credits. p95 decision time 47ms. Sub-200ms automatic failover to a hot-standby region. Named technical account manager and SRE Slack channel for Custom plans — you talk to the engineer who built the thing, not a script reader. Do I own my data? Yes. Every signal we collect on your transactions stays yours — you can export the full history at any time, revoke access, or require us to delete everything within the retention period your plan specifies. Shared threat intelligence (the cross-merchant denylist) is anonymised — only the device/IP identifier is shared, never your merchant context. Can we self-host in regulated markets? Yes. The decisioning engine, vault and gateway modules can deploy in your cloud or behind your VPC for jurisdictions where data residency or regulator policy demands it. We've deployed in Brazilian, Angolan and EU markets with local data-processor requirements. Same APIs, same dashboards, your infrastructure, your audit trail. --- ## Payment Methods — https://www.paybyrd.com/payment-methods Summary: 20+ methods, 192+ currencies, 40+ countries; complete catalog with availability, capability chips and regional grouping Every way they want to pay. One integration. Cards, wallets, buy-now-pay-later, bank rails, and the local methods tourists expect at checkout — every single one pre-certified, tokenizable, and ready to switch on with a single flag. cards · wallets · BNPL · bank · local from Lisbon to Luanda with built-in DCC every method, one API A payment method is any rail a customer can pay with — cards, wallets, bank transfers, local schemes such as MB WAY, Multibanco and iDEAL, and buy-now-pay-later. Paybyrd exposes more than twenty of them through one integration. Every payment method they expect. One integration. One integration flag away. Every method below is already live on the Paybyrd platform — tokenization, 3DS2, and reconciliation flow into the same dashboard. Flip a flag, go live. ### categories No methods match that filter. Try "All methods" or a broader search. View integration docs ### items Credit & debit · the baseline everyone has. Credit & debit · full commercial + consumer support. Higher ticket, higher acceptance. We route it right. The largest network by volume. Essential for tourism corridors. Cross-honoured with Diners — one integration, both networks. Hospitality-heavy usage. Strong in EMEA and LatAm. The conversion winner on mobile web. Native in every browser Safari touches. Fast-tracked for Q2 deployment across the Android fleet. Works on more terminals than any other wallet — even non-NFC ones. The new darling of European checkout. Zero decline on tourist cards. Older demographic, higher ticket. Turn it on for premium retail. The secret weapon. Generate a link anywhere, paid anywhere. Doubles average order value in retail. EU-wide consumer trust. The go-to BNPL for French checkout. Deep merchant discount. The European rail. Low fees, high trust, built for subscriptions. Bank transfer with a unique virtual IBAN per invoice or order. Matched on arrival, same webhook as cards. Not optional if you sell to the Netherlands. Full stop. Portuguese shoppers prefer it over cards. 3 out of 5 checkouts. The unbanked's bridge to e-commerce. Generate, wait, confirm. Brazil's national instant rail. Faster than card, cheaper than card. The Angolan equivalent of a national card network. Mobile-first counterpart. Dominates urban Angola checkouts. Face ID / Touch ID Pay in 3 Pay in 30 Where you sell, what wins the cart. Every market has a dominant rail. Miss it and you leak revenue to the competitor one tap away. Here's the shortlist per region — pre-wired into every Paybyrd integration. Not on the list? Tell us your market → We've added 11 methods in the last 18 months. ### items MB WAY is non-optional. 3 of 5 Portuguese checkouts go through MB WAY. iDEAL or lose the cart. iDEAL owns 70%+ of Dutch e-commerce volume. PIX is the new rail. PIX processed 42B transactions in 2023 — more than cards. Multicaixa for the whole market. Multicaixa + Express cover virtually every banked Angolan. Floa doubles basket size. BNPL usage in French e-commerce doubled year on year. EU · the rest Cards, wallets, SEPA, Klarna. One configuration unlocks 27 EU markets at once. Rest of world Cards + global wallets. 90+ markets live, including USD, GBP, CHF, CAD, AUD, JPY, CNY. Every foreign card, every tap. 192 currencies · automated tax-free refunds for eligible tourists. The plumbing nobody wants to think about. Tokenization, SCA, refunds, chargebacks, recurring, DCC — already done, across every method. Your team ships features, not payment specs. ### items SCA-compliant everywhere it's needed. Frictionless flow where the issuer allows, step-up challenge where they insist. Cards tokenized at the network level — longer life, higher approval, and no scope on your side. Apple Pay & Google Pay included. Visa + Mastercard Pre-auth + partial capture Lock funds, settle later — with partial capture when the final amount differs. Built for hotels, rentals, and any open-tab flow. One transaction, multiple payees. Built for marketplaces, multi-merchant POS, and any revenue-share model. Recurring + saved cards Subscriptions, top-ups, and one-click repeat purchases. Cards stay on file at the network, not on your server. DCC · 192 currencies Dynamic Currency Conversion on every card. Tourists pay in their home currency, you book in yours, rates lock for 60s. Full + partial refunds Refunds post in under 3s with an ARN. Partial, full, and split across methods. No ticket to the acquirer, no hold music. < 3s with ARN Automated evidence packs. We compile the AVS, 3DS, delivery, and tokenization proofs in one click and submit on your behalf. −16.8% CB rate Connected to the systems you already trust. Plug-and-play for the platforms you run. REST + webhooks for the ones we don't cover yet. A week of engineering time, max. Don't see yours? Build on the REST API — our open-source starter hits production in 4 days on average. ### groups Official plugin · WP.org Adobe Commerce certified REST API + webhooks ERP · POS · PMS Hybris + ECC connectors Opera Cloud ready Host hotel systems PT retail POS Android SDK + JS SDK Analytics · Finance US/UK book export Missing a method? We've got you. We added 11 new methods in the last 18 months — most on a merchant request. If you sell into a market we don't yet cover, or your stack needs a bespoke integration, build on the open API or send us a note. Either way, you're talking to a human. Build on our API Open-source starter kits · sandbox in 24h · production in a week. Request a method Tell us your market and volume — we'll come back within two business days. Two-day response · human-typed Thanks — we'll be in touch within 2 business days. and the rates behind them. ### items Are MB WAY, Multibanco and iDEAL included at local rates? Yes. Local methods are native on Paybyrd, not routed through a third party, and each is priced on the pricing page rather than as a surcharge. How do I enable a method? From the dashboard, per outlet or per checkout. Most methods are live immediately; some require a short scheme onboarding that Paybyrd runs for you. Which currencies settle natively? Paybyrd accepts payments in 192+ currencies and settles in the order currency by default, or in euros with a published conversion rate, with refunds always in the customer's original currency. Which countries can I sell into? Card and wallet acceptance covers 40+ countries across the EEA and partner markets; local methods are enabled per market where they are used. Where are the fees for each method? On the pricing page, per method, and the card scheme fees inside those rates are published in full on the scheme-fee schedule. --- ## Marketplaces — https://www.paybyrd.com/marketplaces Summary: split at capture into a dedicated safeguarded wallet per seller held at Banking Circle through Ztlment ApS (Complypay) under Danish FSA supervision; optional card issuing on the seller wallet; automated KYB/EDD, rolling reserves and DAC7 reporting One payment in. ready to spend. The payments rail built for marketplaces. Split at capture into a dedicated safeguarded wallet per seller, then optionally issue them a card to spend it — compliance built in, not bolted on. Bank-safeguarded seller wallets Split at capture Sandbox same day Marketplace payments split one customer checkout at capture between the platform's commission, a rolling reserve and each seller's safeguarded wallet, held at a licensed bank rather than on the platform's balance sheet. Incoming · 3-seller cart Platform commission · 12% Rolling reserve · 8% 3 seller wallets · safeguarded Apple Pay ready A marketplace running on Paybyrd Touch seller money, and you might be a The moment client funds flow through your accounts on the way to your sellers, you risk operating as an unlicensed payment institution — a regulatory exposure most platforms underestimate. Paybyrd captures each payment straight into a safeguarded wallet: seller money never lands on your balance sheet, never sits in your bank account, never makes you the regulated party. Where the money actually sits Paybyrd orchestrates the checkout, the split, the wallets and the cards — it never holds your sellers' money. Client funds sit in safeguarded wallet accounts at Banking Circle , a fully licensed bank, through Ztlment ApS (Complypay) , a licensed financial institution supervised by the Danish FSA (Finanstilsynet) . Insolvency-remote from both you and Paybyrd. View Ztlment on the Danish FSA register → Every seller verified before first payout — KYB, UBO, sanctions & source-of-funds Automated KYB & EDD fire at your volume thresholds, then clear themselves Holds & rolling reserves applied at source — full audit trail, exportable on demand EDD · UBO · sanctions passed threshold — review open PSD2 / SCA PCI DSS Level 1 Safeguarded wallet accounts KYB · AML · EDD · UBO Priced at cost, like everything we do — see the published scheme-fee schedule Your DAC7 report already lives in the ledger. EU platforms must report seller identities and income to tax authorities under DAC7. Every reportable field — verified seller identity, tax IDs, per-seller income totals — already lives in your Paybyrd ledger. Export it; don't rebuild it from spreadsheets. One checkout. Money split the instant it lands. The customer pays once on your storefront. At capture we split commission, hold a rolling reserve, and settle each seller into their own safeguarded wallet — zero commingling on your balance sheet. ### steps Customer pays once A single hosted checkout, your brand — multi-seller cart, 3DS2, SCA, 20+ methods. Split at capture Commission to you, reserve held at source, each seller's share routed instantly. Safeguarded & spendable Funds land segregated in safeguarded wallet accounts at a licensed bank — ready to pay out to the seller's bank, or spend on an optional issued card. Simulated · illustrative A safeguarded account for every seller. Every seller gets their own safeguarded wallet account at a licensed bank — insolvency-remote from your balance sheet. Client money is never commingled with your operating cash. Provable to auditors on any given day. Dedicated IBAN-level segregation per seller Held in safeguarded accounts at Banking Circle, a licensed bank Real-time balance, ledger & statements Sellers pick the marketplace that pays them first. A seller's share is spendable at capture — usable the moment the split lands, with no payout wait and no external bank. Optionally, let them spend it directly on an issued card added to Apple Pay or Google Pay, in-store or online. Instant access to earnings is how you win sellers off slower platforms — and keep them. Opt-in per seller — standard bank payout is always available Virtual cards issued in seconds, physical on request Apple Pay & Google Pay tokenization built in Spend controls, limits & freeze — you stay in control Add to Apple Pay Add to Google Pay Onboard a thousand sellers without killing activation. Sellers start selling fast. KYB and enhanced due diligence run automatically and trigger at configurable volume thresholds, so compliance protects activation instead of throttling it — verification runs on our rails, behind your onboarding UX. Progressive onboarding — sellers transact first, EDD triggers at volume Identity, UBO, sanctions & source-of-funds, automated Your branded onboarding UX, our verification rails Full, exportable audit trail per seller Your branded onboarding UX Seller signs up in seconds and starts selling Transacting from day one baseline KYB cleared Volume threshold crossed EDD triggered automatically Identity · UBO · sanctions · source-of-funds audit trail retained & exportable One API call splits the payment. Commission, rolling reserve and every seller's share — routed at capture from a single request. No payout batch, no nightly reconciliation job to babysit. One capture, N recipients — commission, reserve and sellers in the same payload Amounts in minor units — no rounding drift on the split Same primitives in sandbox and production Illustrative request — see the full API for the production contract. Read the API docs → side by side. The same job, four different rails — compared on what actually matters to a marketplace. Safeguarded at a licensed bank (Banking Circle) — you never touch them Held by Stripe until payout Safeguarded in a licensed EMI wallet Held by Adyen (licensed bank) At capture — the moment the split lands On payout (T+N); instant payout carries a fee On payout to bank On the payout schedule Yes — optional, Apple/Google Pay Separate Issuing product Published at cost Blended published + negotiated Custom / negotiated Interchange++ , enterprise-negotiated US-first, broadest global coverage EU-native, long marketplace tenure Global enterprise scale Sandbox same day · first split week one Fast self-serve onboarding A payment engineer Docs + tiered support Last verified July 2026. Competitors' capabilities change — we keep this current and cite sources on request. Compared on the axes that matter to a marketplace; each provider has real strengths of its own. The questions your CTO ### items Refund across a split Refunds debit the relevant seller's wallet first; the rolling reserve covers any shortfall, so the reversal never lands on your balance sheet. A chargeback is clawed back from the seller's wallet; where the balance can't cover it, the reserve absorbs it, then platform-level rules apply. If a seller wallet would go negative, the rolling reserve absorbs it and the balance is recovered from future settlements — never from your operating cash. When a seller leaves, their funds stay safeguarded and are settled out per your offboarding rules; the audit trail is retained. Rolling reserves release on a configurable schedule once the exposure window passes, back into the seller's spendable balance. The questions operators ### items What happens to refunds and chargebacks across a split? A refund or chargeback is debited from the relevant seller's wallet first; if that wallet can't cover it, the rolling reserve absorbs the shortfall, then platform-level rules apply. Reserves exist precisely so a reversal never lands on your balance sheet unexpectedly. Who holds the licence — you or Paybyrd? Paybyrd orchestrates the flow; it never holds your sellers' money. The regulated flow-of-funds runs through Ztlment ApS (Complypay), a licensed financial institution supervised by the Danish FSA (Finanstilsynet), and client funds are held in safeguarded wallet accounts at Banking Circle, a licensed bank — insolvency-remote from both you and Paybyrd. How is this different from Stripe Connect? Connect pays sellers out on a delay to an external bank; here the split lands instantly into a safeguarded wallet the seller can spend from a card immediately — and pricing is published at cost, not blended. How long until we're live? Sandbox same day, shadow-mode alongside your current provider, first live split in week one. How does Paybyrd split a marketplace payment across sellers? The customer pays once on your storefront. At capture, Paybyrd splits your commission, holds any rolling reserve at source, and settles each seller's share into their own dedicated safeguarded wallet — with zero commingling on your balance sheet. Where is seller money held, and what happens if Paybyrd becomes insolvent? Each seller's funds are held in safeguarded wallet accounts at Banking Circle (a licensed bank), through Ztlment ApS (Complypay), a licensed financial institution supervised by the Danish FSA (Finanstilsynet) — segregated from Paybyrd's own operating cash, and insolvency-remote from both your marketplace and Paybyrd. Can sellers spend their balance right away? Yes. Paybyrd can issue a virtual card on every seller wallet the moment it's funded — no payout wait and no external bank. Sellers add it to Apple Pay or Google Pay and spend in-store or online, with the wallet balance as the limit. You keep spend controls, limits and freeze. How does KYB and compliance work for sellers? KYB and enhanced due diligence are automated and trigger at configurable volume thresholds — identity, UBO, sanctions and source-of-funds checks run and clear themselves. You can apply holds and rolling reserves at source, with a full, exportable audit trail. Does seller money ever sit on our balance sheet? No. Seller funds are safeguarded in segregated wallet accounts at Banking Circle, a licensed bank — never commingled with your operating cash — so €0 of seller money sits on your balance sheet. --- ## Compare payment providers — https://www.paybyrd.com/vs Summary: hub of every Paybyrd comparison — Stripe, Adyen, Mollie, Checkout.com, Ifthenpay, Eupago, Pay.nl, Buckaroo — with one dated published-rate line per provider and the local providers listed first on /pt and /nl Compare Payment Providers — Paybyrd vs Stripe & More Paybyrd compared with Stripe, Adyen, Mollie, Checkout.com, Ifthenpay, Eupago, Pay.nl and Buckaroo: published rates, where each is stronger, the migration path. Paybyrd against the providers you are actually choosing between. Each comparison uses the rates the other provider publishes, dated, with the places they are genuinely stronger stated first. Run your own volume through the calculator on any of them. Paybyrd: 1.25% + €0.08 online, 0.50% in store, €7.50 per chargeback, no monthly minimum. --- ## Paybyrd vs Stripe — https://www.paybyrd.com/vs/stripe Summary: Paybyrd compared with Stripe on published rates, approval performance, EU market coverage, support model and migration effort, with dated rate tables and the savings maths Paybyrd compared with Stripe. Stripe is excellent infrastructure. It's also the priciest way to take a card in Europe. Primary markets for Stripe: Global · strongest in US. Typical migration to Paybyrd: 22 business days. Where Stripe is genuinely strong: - Industry-leading developer experience — clean APIs, great docs, huge ecosystem. - Global coverage across 46 countries, useful if you process outside the EU. - Deep platform features — Connect, Billing, Issuing — if you're building a marketplace. Where merchants switch to Paybyrd: - 1.50% + €0.25 online vs Paybyrd 1.25% + €0.08 — that's €0.17 lower on every single transaction, plus 0.25% off the rate. - €15 chargeback fee vs Paybyrd's €7.50 — half the cost on every dispute. - Single-acquirer routing on Stripe. Paybyrd's multi-acquiring orchestration recovers an additional 4–7% of transactions on typical EU card volume — soft declines retry on a second acquirer in under 200ms. - Stripe's instant payouts cost 1% extra. Paybyrd's gross-settled T+0 / T+1 payouts are included in the headline rate, with per-outlet / per-SKU / per-channel itemisation for reconciliation. - Multibanco, MB WAY, iDEAL and Bancontact at local rates (not the international-card surcharge Stripe applies). 20+ EU-native methods pre-certified, 192+ currencies, 40+ countries. - Up to 80% DCC revenue share — the FX margin on international-card payments flows back to you. Stripe keeps 100%. For cross-border-heavy merchants this often offsets the entire card-acceptance cost. - Paybyrd Antifraud: 47ms p95 decisions, 55+ fraud signals per transaction, −16.8% chargebacks on average. 3DS2, network tokens, AI velocity scoring all included — not a Radar-style add-on. - Engineer-led support with a named TAM + dedicated Slack channel and SRE on-call (Custom plans). 99.999% uptime SLA backed with contractual credits — with teeth, in writing. Sub-200ms automatic failover to a hot-standby region. - 22-day parallel-processed migration for an enterprise-scale rollout (Vila Galé first-property reference; subsequent properties roll out in days; SMB merchants typically live in <4 hours). Rollback switch always one config flag away. No big-bang cutover, no re-authenticating cards, no lock-in — Essential is pure pay-as-you-go. Published rates used in the comparison (see the page for the effective date and the full table): - Stripe online cards: 1.5% + EUR 0.25 - Stripe card-present: 1.4% + EUR 0.10 - Stripe chargeback fee: EUR 15.00 - Stripe monthly minimum: none published - Paybyrd online cards: 1.25% + EUR 0.08 - Paybyrd card-present: 0.5% + EUR 0.00 Q: Will switching from Stripe break my checkout integration? A: No — Paybyrd exposes REST APIs, hosted payment pages, drop-in web components, and WooCommerce / Adobe Commerce / nopCommerce plugins. Most Stripe integrations map 1:1 to a Paybyrd endpoint. Our migration team pairs with yours and we parallel-process 5-20% of live traffic for 2-4 weeks so you compare diff reports against your incumbent before fully cutting over. Q: Does Paybyrd support Apple Pay, Google Pay, and local methods like iDEAL / Multibanco? A: Yes — Apple Pay, Google Pay, iDEAL, Multibanco, MB WAY, SEPA, Bancontact, Klarna, PayPal, Revolut Pay and 180+ more. Local methods are at local rates (not the surcharged international-card rate Stripe charges for Multibanco / iDEAL). Q: What about 3DS, fraud scoring, and PCI scope? A: 3DS2 with device-ID-based step-up, AI velocity scoring at 47ms p95, Visa Trusted Listing, network tokenisation — all included. PCI scope is SAQ A-EP via our embedded web components (same reduction Stripe Elements gives you). Q: I'm already on Stripe Tax / Connect. Can I use just Paybyrd for processing? A: Yes — Paybyrd is modular. Keep Stripe Tax, use Paybyrd for processing. Gross payouts land in your account with a full per-outlet / per-SKU breakdown so your existing tax and ledger flows don't change. Q: Can I keep my existing acquirer contracts? A: Yes. Paybyrd is acquirer-agnostic — keep your negotiated rates and in-flight volume commitments. We orchestrate on top. If you later choose to consolidate, we can act as your acquirer across 90+ markets, but it's a separate decision on a separate contract. --- ## Paybyrd vs Adyen — https://www.paybyrd.com/vs/adyen Summary: Paybyrd compared with Adyen — enterprise scale and global reach against EU-native depth, published at-cost pricing and a named payment engineer Paybyrd compared with Adyen. Adyen is built for enterprise. If you're under €2B volume, you're paying for features you don't use. Primary markets for Adyen: Global enterprise. Typical migration to Paybyrd: 22 business days. Where Adyen is genuinely strong: - Genuine enterprise-grade platform — unified commerce, in-house acquiring in 30+ markets. - Direct acquiring relationships cut fewer intermediaries out of the chain. - Sophisticated reporting and unified data across channels at real scale. Where merchants switch to Paybyrd: - Zero monthly minimums, zero implementation fees, zero setup costs. Adyen's floor typically starts at €500/mo plus bespoke integration fees billed upfront. - Transparent blended rates from day one. No IC++ guessing game — you sign the rate, you pay the rate on your first transaction. Custom plans offer IC++ on request above €10M/yr if you want scheme-level granularity. - +1.72% effective cost savings vs Adyen on typical EU retail profiles (blended card rate, after scheme / assessment / interchange are rolled in). - 22 days contract-to-live for enterprise rollouts (Vila Galé first-property runbook; subsequent properties in days; SMB merchants live in <4 hours) vs Adyen's typical 2-4 month sales + integration cycle. Sandbox in 24 hours, parallel processing Week 3, graduated cutover with rollback. - Same multi-acquiring orchestration across 90+ markets — route to the best acquirer per transaction, retry soft declines in under 200ms, without the enterprise contract gauntlet. - 99.999% uptime SLA backed with credits (10% credit under 99.999%, 25% under 99.99%, 50% under 99.95%). Named TAM + dedicated Slack channel with SRE on-call from day one on Custom plans. Sub-200ms automatic failover. - Self-hosted modules for regulated markets — gateway, vault, and decisioning engine run in your cloud or behind your VPC for BR / AO / EU data-residency requirements. Same APIs, your infrastructure, your audit trail. - Up to 80% DCC revenue share back to the merchant. Surcharge engine in legal markets (US / AU / LATAM / EU credit carve-outs) recovers €4M–€7M/yr for a €2B merchant with ~35% surchargeable corridors. Adyen doesn't offer these commercial levers. - Paybyrd Antifraud: 47ms p95 decisions, 55+ signals per transaction, rules-then-ML hybrid with every signal explainable on the review page. Shadow mode runs 2–3 months alongside your incumbent so your team sees impact before any decision changes. - Engineer-led 15-minute discovery calls. No SDR, no slide deck, no procurement runway. On Custom plans you keep your existing acquirer contracts (Paybyrd is acquirer-agnostic) and add orchestration on top — zero bridge-burning. Published rates used in the comparison (see the page for the effective date and the full table): - Adyen online cards: 1.5% + EUR 0.12 - Adyen card-present: 1.5% + EUR 0.12 - Adyen chargeback fee: EUR 15.00 - Adyen monthly minimum: EUR 500.00 - Paybyrd online cards: 1.25% + EUR 0.08 - Paybyrd card-present: 0.5% + EUR 0.00 Q: We're evaluating Adyen for enterprise payments. When should we pick Paybyrd instead? A: Under ~€2B in annual volume, Paybyrd's blended cost is materially lower — our data shows +1.72% effective cost savings vs Adyen on typical EU retail profiles. Above that, Adyen's in-house acquiring starts to pay back the minimums and implementation cost. If you're a PSP-scale enterprise with dedicated payment ops, Adyen makes sense. If you're a high-growth merchant with €10M–€2B volume, Paybyrd gives you the same multi-acquiring without the ramp. Q: What about the interchange++ (IC++) pricing model? A: Paybyrd offers IC++ on request for merchants over €10M annual volume. Default pricing is blended so most merchants don't have to reason about scheme fees, assessment fees, and interchange levels — you get a predictable headline rate. Custom plans can split it out. Q: Can Paybyrd act as an acquirer or just as a gateway? A: Both. Default: we orchestrate across your existing acquirer contracts or ours, route to the best one per transaction. On request: Paybyrd acquires direct in 90+ markets. Unlike Adyen you can flip between modes per channel or per market without re-integrating. Q: How does your SLA compare to Adyen? A: 99.999% contractually backed with credits (10% bill credit for <99.999%, 25% for <99.99%, 50% for <99.95%). Dedicated Slack channel for custom-plan merchants and a named technical account manager. Sub-200ms automatic failover to a hot-standby region. Q: Can I keep my existing acquirer contracts? A: Yes. Paybyrd is acquirer-agnostic — keep your negotiated rates and in-flight volume commitments. We orchestrate on top. If you later choose to consolidate, we can act as your acquirer across 90+ markets, but it's a separate decision on a separate contract. --- ## Paybyrd vs Mollie — https://www.paybyrd.com/vs/mollie Summary: Paybyrd compared with Mollie — two European providers on rates, method coverage, in-person support and settlement Paybyrd compared with Mollie. Mollie is the Dutch default. It's also expensive at scale, and its APM rates don't scale down with volume. Primary markets for Mollie: Netherlands, Belgium. Typical migration to Paybyrd: 18 business days. Where Mollie is genuinely strong: - Excellent developer experience for small-to-mid NL merchants — clean docs, quick setup. - Strong iDEAL + Bancontact coverage at flat fees. - Friendly brand, pay-as-you-go pricing with no commitment. Where merchants switch to Paybyrd: - 1.80% + €0.25 online vs Paybyrd 1.25% + €0.08 — 0.55% lower rate AND €0.17 lower fixed on every transaction. At €1M/yr that's €5,500+ back in your pocket. - iDEAL flat €0.29 forever, no matter the volume. Paybyrd's iDEAL starts at €0.19 and drops further above €10M/yr — you get economies of scale Mollie doesn't pass through. - Single-acquirer routing on Mollie. Paybyrd's multi-acquiring recovers an additional 4–7% of otherwise-lost transactions (soft declines retry on a second acquirer in under 200ms). On a €1M/yr Dutch merchant that's ~€20K–€35K of recovered revenue. - €15 chargeback fee vs Paybyrd €7.50 — cut dispute cost in half. - 99.999% uptime SLA with contractual credits (10% / 25% / 50% tiers). Sub-200ms failover to hot-standby. Mollie operates on best-effort SLAs with no credit-backed commitments. - Paybyrd Antifraud: 47ms p95 decisions, 55+ signals per transaction, −16.8% chargebacks average. Shadow mode lets you run alongside your current fraud stack for 2–3 months before flipping decisioning over. Mollie's fraud tooling is rule-based only. - Per-outlet / per-SKU / per-channel reconciliation in the dashboard. Finance teams close the day in hours, not Mondays (Vila Galé's phrase). Mollie's single payout line forces manual splits. - Card-present payments from 0.50% with Paybyrd terminals (PAX A77 from €199, rent or buy, OTA updates, InstaTax for tax-free refunds, offline store-and-forward with 500-txn buffer). Mollie is online-only. - Up to 80% DCC revenue share back to the merchant on international-card volume. Useful for NL merchants with any cross-border exposure (EU tourism, UK spill-over, US buyers). Published rates used in the comparison (see the page for the effective date and the full table): - Mollie online cards: 1.8% + EUR 0.25 - Mollie card-present: 1.2% + EUR 0.00 - Mollie chargeback fee: EUR 15.00 - Mollie monthly minimum: none published - Paybyrd online cards: 1.25% + EUR 0.08 - Paybyrd card-present: 0.5% + EUR 0.00 Q: We're processing >€1M/year on Mollie. How much would we save on Paybyrd? A: At €1M annual volume with a typical NL card-heavy mix (40% card / 50% iDEAL / 10% wallet), the blended Mollie cost is around €18,000/year. Paybyrd at the same volume is around €12,500/year. €5,500 in year-one savings, before the 4–7% approval-rate lift from multi-acquiring routing. Q: Does Paybyrd offer iDEAL at competitive rates? A: Yes — iDEAL is a flat €0.29 on Mollie regardless of scale. Paybyrd offers iDEAL at volume-tiered rates starting from €0.19 and dropping further above €10M/year. We also support the new iDEAL 2.0 specifications ahead of schedule. Q: Can we migrate our subscription / recurring setup without re-tokenising? A: In most cases yes — Paybyrd supports network-token imports from Mollie, Stripe, and Adyen so your existing card-on-file relationships survive the move. Our migration team runs this as a parallel process over 2-4 weeks with zero card re-authentication required from customers. Q: Is there a minimum commitment? A: No — Essential plan is pure pay-as-you-go, no setup fee, no monthly minimum. Custom plans (volume tiers) are typically 12-month commitments for the better rates, but include a 30-day SLA-breach exit clause. We'd rather you stay because the platform works than because you're locked in. Q: Can I keep my existing acquirer contracts? A: Yes. Paybyrd is acquirer-agnostic — keep your negotiated rates and in-flight volume commitments. We orchestrate on top. If you later choose to consolidate, we can act as your acquirer across 90+ markets, but it's a separate decision on a separate contract. --- ## Paybyrd vs Checkout.com — https://www.paybyrd.com/vs/checkout-com Summary: Paybyrd compared with Checkout.com on approval performance, pricing transparency and what the contract commits to Paybyrd compared with Checkout.com. Checkout.com is built for enterprise. Paybyrd benchmarks show a +4.86% approval-rate lift on typical EU merchant profiles. Primary markets for Checkout.com: Global enterprise. Typical migration to Paybyrd: 22 business days. Where Checkout.com is genuinely strong: - Direct acquiring in major markets, strong enterprise reputation. - Robust API and developer tooling for high-volume merchants. - Tailored pricing and dedicated account teams for Tier-1 accounts. Where merchants switch to Paybyrd: - +4.86% approval-rate lift benchmarked against Checkout.com on typical EU merchant card volume. Multi-acquiring retries soft declines on a second acquirer in under 200ms — on €10M/yr volume that's ~€500K of recovered revenue a year. - Transparent blended rates from day one — no procurement gauntlet, no IC++ guessing game, no bespoke implementation-fee negotiation. 1.25% + €0.08 published, tiered to 0.99% / 0.85% at higher volumes, custom @ €2M+. - Zero monthly minimums, zero setup fees, zero implementation fees. Checkout.com typically requires enterprise commitments and upfront integration fees billed before first transaction. - 22-day contract-to-live for enterprise rollouts (Vila Galé first-property runbook; subsequent in days; SMB merchants live in <4 hours) with parallel processing and rollback switch. Checkout.com's typical onboarding is 2–4 months of sales + integration before first live transaction. - 99.999% uptime SLA with contractual credits (10% / 25% / 50% tiers) + named TAM + dedicated Slack SRE channel from day one on Custom plans. Same enterprise muscle, with the named engineer who built the thing on the other end of the channel. - Self-hosted modules for regulated markets — gateway, vault, decisioning engine run in your cloud or behind your VPC for BR / AO / EU data-residency requirements. Same compliance flexibility enterprise teams expect from Checkout.com. - Up to 80% DCC revenue share back to the merchant on international-card volume. Plus a surcharge engine for legal markets (US / AU / LATAM / EU credit carve-outs) that recovers €4M–€7M/yr for a €2B merchant. Novel commercial levers Checkout.com doesn't offer. - Paybyrd Antifraud as a standalone product or bundled: 47ms p95 decisions, 55+ signals per transaction, rules-then-ML hybrid with every signal explainable. Shadow mode runs 2–3 months alongside your incumbent before any decision changes. - Acquirer-agnostic: keep your existing acquirer contracts, your negotiated rates, your in-flight volume commitments. Paybyrd orchestrates on top. Consolidate to Paybyrd acquiring later if you want — separate decision, separate contract. - Engineer-led 15-minute discovery. No SDR, no slide deck. €7.50 chargebacks vs Checkout.com's €15. Cancel anytime on Essential — no lock-in. Published rates used in the comparison (see the page for the effective date and the full table): - Checkout.com online cards: 1.45% + EUR 0.10 - Checkout.com card-present: 1.4% + EUR 0.10 - Checkout.com chargeback fee: EUR 15.00 - Checkout.com monthly minimum: none published - Paybyrd online cards: 1.25% + EUR 0.08 - Paybyrd card-present: 0.5% + EUR 0.00 Q: Where does the +4.86% approval-rate lift come from? A: Multi-acquiring routing. When a card is declined by one acquirer for a soft-decline reason (insufficient funds flag, velocity check, issuer-side heuristic), Paybyrd automatically retries on a second acquirer in <200ms. Across a typical EU card volume against a Checkout.com-equivalent single-acquirer baseline, we recover roughly one transaction in twenty that would otherwise have been lost. The exact number depends on your card mix, geography, and average ticket — the demo walks through your real numbers. Q: We're enterprise-scale (>€500M volume). Is Paybyrd appropriate? A: Yes. Our biggest merchants process €10B+ annually on Paybyrd. At enterprise scale you get: named technical account manager, dedicated Slack channel with SRE on-call, custom SLAs with credit-backed uptime commitments, interchange++ pricing on request, multi-region deployment, data-residency self-hosted modules (gateway, vault, decisioning engine). Q: How does your 3DS and fraud stack compare? A: 3DS2 with device-ID-based step-up (Visa Trusted Listing where eligible), 47ms p95 decision engine with 55+ fraud signals, network tokenisation, behavioural biometrics. We also offer Paybyrd Antifraud as a standalone product if you want scoring without the processing. Q: Can I keep my Checkout.com contract during migration? A: Yes — we parallel-process. Paybyrd handles 5-20% of live traffic while your Checkout.com pipeline keeps running. You compare diff reports against your incumbent for 2-4 weeks before committing to full cutover. Rollback is always one config flag away until you're 100% confident. Q: Can I keep my existing acquirer contracts? A: Yes. Paybyrd is acquirer-agnostic — keep your negotiated rates and in-flight volume commitments. We orchestrate on top. If you later choose to consolidate, we can act as your acquirer across 90+ markets, but it's a separate decision on a separate contract. --- ## Paybyrd vs Ifthenpay — https://www.paybyrd.com/vs/ifthenpay Summary: Paybyrd compared with Ifthenpay for Portuguese merchants — Multibanco and MB WAY coverage, SIBS rails, pricing and migration Paybyrd compared with Ifthenpay. Ifthenpay headlines the lowest Multibanco rate in Portugal. It doesn't tell you what actually shows up on your invoice. Primary markets for Ifthenpay: Portugal. Typical migration to Paybyrd: 14 business days. Where Ifthenpay is genuinely strong: - Cheapest headline Multibanco rate for pure EEA-consumer volume. - Strong domestic Portuguese brand, familiar to SMB merchants. - Simple flat-fee MB WAY pricing. Where merchants switch to Paybyrd: - Real blended rate is 1.65% + €0.20 on a typical 85/10/5 EU mix once non-EEA +1% and business-card +1% surcharges apply. Paybyrd is 1.25% + €0.08, full stop — no surcharge pyramid. - Tourist-heavy merchants (Lisbon centro, Algarve, Porto ribeira) bleed 0.2–0.4% on every non-EEA card. Paybyrd routes international cards through dedicated acquiring at competitive rates — same MB WAY + Multibanco on SIBS, none of the tourist tax. - 4–7% approval-rate lift via multi-acquiring routing. Ifthenpay is single-path; if the issuer declines, the sale is gone. Paybyrd retries soft declines across acquirers in under 200ms — on €500K/yr that's ~€20K–€35K of recovered revenue. - Paybyrd Antifraud: 47ms p95 decisions, 55+ signals (10 IP + 45 device + transaction-level), −16.8% chargebacks on average. Rules + ML hybrid with every signal explainable. Ifthenpay has no comparable fraud product. - Card-present payments from 0.50% with Paybyrd terminals (PAX A77 from €199, Sunmi T3 Pro Max from €599). Rent from €12/mo or buy outright. OTA updates, white-label boot logo + receipts, offline store-and-forward buffering 500+ transactions. 24h swap guarantee in Lisbon / Porto. - InstaTax built into every Android terminal: detects eligible tourists via BIN match in under 200ms, offers tax-free refund on-screen, pays you a revenue share daily. +50% merchant revenue vs other tax-refund platforms. Activation in 24h, zero staff training. - 192+ currencies, 40+ countries, 20+ EU-native methods — native iDEAL, Bancontact, Klarna, Floa, Revolut Pay, Apple Pay, Google Pay for merchants with any cross-border or EU-wide exposure. - 99.999% uptime SLA with contractual credits + engineer-led support (no ticket queues). Named TAM + Slack SRE channel for Custom plans. Ifthenpay publishes no SLA. - Per-outlet / per-channel / per-SKU reconciliation in the dashboard. Finance closes the books in hours, not Mondays. Ifthenpay's dashboard shows a daily total and little else. - Up to 80% DCC revenue share on international-card volume, paid out daily. Material for tourist-heavy merchants — this alone often offsets the entire card-acceptance cost. Published rates used in the comparison (see the page for the effective date and the full table): - Ifthenpay online cards: 1.65% + EUR 0.20 - Ifthenpay card-present: 0.85% + EUR 0.00 - Ifthenpay chargeback fee: EUR 10.00 - Ifthenpay monthly minimum: none published - Paybyrd online cards: 1.25% + EUR 0.08 - Paybyrd card-present: 0.5% + EUR 0.00 Q: We mostly accept Multibanco and MB WAY. Is Paybyrd competitive vs Ifthenpay? A: Yes. Paybyrd's Multibanco rate is from €0.20 fixed, MB WAY from 0.70%. The difference vs Ifthenpay at small volume is nominal; the savings compound on card-present and international-card volume, where Ifthenpay surcharges heavily and we don't. Q: What if we have tourist-heavy volume (Lisbon, Algarve, Porto)? A: This is where the Ifthenpay blended rate blows out. Non-EEA cards surcharge +1%, business cards +1% — on a 15% tourist/business mix that's an extra 0.15% across ALL your volume. Paybyrd routes non-EEA cards through dedicated international acquiring at competitive rates, typically saving 0.2-0.4% on tourist-heavy merchants. Q: Does Paybyrd work with SIBS / Unicre for acquiring? A: Yes — Paybyrd orchestrates across SIBS, Unicre, and our own acquiring relationships. You keep your existing Portuguese acquirer contract if you have one; we add multi-acquiring routing on top so transactions declined by one route automatically retry on another. Q: How fast is the switch? A: 14 business days is typical for an Ifthenpay → Paybyrd migration. Your MB WAY and Multibanco references keep working — we map them 1:1 on our side. Card tokens import cleanly. Most PT merchants are live in under 3 weeks with zero customer-facing disruption. Q: Can I keep my existing acquirer contracts? A: Yes. Paybyrd is acquirer-agnostic — keep your negotiated rates and in-flight volume commitments. We orchestrate on top. If you later choose to consolidate, we can act as your acquirer across 90+ markets, but it's a separate decision on a separate contract. --- ## Paybyrd vs Pay. — https://www.paybyrd.com/vs/pay-nl Summary: Paybyrd compared with Pay. (pay.nl) for Dutch merchants — iDEAL and card rates against a monthly package fee, multi-acquirer routing, in-store terminals and the 18-day migration path; rates as published on pay.nl on 2 September 2026 Paybyrd compared with Pay.nl. Pay.nl is the all-in-one Dutch PSP: 100+ plugins, iDEAL from €0.19, and a monthly package fee you pay before the first transaction. Primary markets for Pay.nl: Netherlands. Typical migration to Paybyrd: 18 business days. Where Pay.nl is genuinely strong: - Genuinely Dutch — NL support, iDEAL | Wero from €0.19, Bancontact, Pay by Bank and 100+ shop plugins. - Fast to start: registration and first payments within minutes on the Professional package. - A deep NL ecosystem — credit management, subscriptions, an Optimize module per sales channel on the Business tier. Where merchants switch to Paybyrd: - €35/month for the Professional package before a single transaction (€89/month on Business). Paybyrd has no monthly fee: 1.25% + €0.08 online, iDEAL from €0.19, and that is the whole price list. - Consumer EU cards 1.50% + €0.15; business and non-EU cards 2.80% + €0.15. Blended for a typical mix that is about 1.70% + €0.15, against Paybyrd's 1.25% + €0.08 — the fixed part alone is €0.07 less on every transaction. - One acquirer behind the checkout. Paybyrd routes each authorisation across several acquirers and retries a soft decline on a second one before the customer sees an error. - In-store on Pay.nl means partner terminals and a separate arrangement. Paybyrd terminals sit on the same contract, from 0.50% in-store, rent or buy, with tap-to-pay on Android. - Package rates are blended. Paybyrd publishes the full Visa and Mastercard scheme-fee schedule and passes it through at cost, so you can see exactly what the networks charge. - Pay.nl publishes no chargeback fee on its pricing page. Paybyrd's is €7.50 per dispute, on the same page as every other rate. - Switching takes 18 business days with shadow mode alongside Pay.nl — iDEAL | Wero and Bancontact carry over, nothing is ripped out. Published rates used in the comparison (see the page for the effective date and the full table): - Pay.nl online cards: 1.7% + EUR 0.15 - Pay.nl chargeback fee: not published - Pay.nl monthly minimum: EUR 35.00 - Paybyrd online cards: 1.25% + EUR 0.08 - Paybyrd card-present: 0.5% + EUR 0.00 Q: Is Paybyrd cheaper than Pay.nl? A: On published rates, yes for most merchants: Paybyrd has no monthly package (Pay.nl's Professional package is €35/month, €420 a year before any transaction), a lower fixed fee per card transaction (€0.08 vs €0.15) and iDEAL from the same €0.19 with no package attached. Run your own numbers in the calculator — it uses these published rates. Q: Can I keep iDEAL | Wero and Bancontact? A: Yes. Both are on Paybyrd, iDEAL | Wero from €0.19 per transaction, and they are carried over during migration so your checkout offers the same methods on day one. Q: How long does switching from Pay.nl take? A: 18 business days is the typical Dutch migration, including a shadow-mode period where Paybyrd runs alongside Pay.nl before traffic moves. Nothing is ripped out. Q: What about my shop plugins? A: Paybyrd offers a hosted checkout, payment links and integrations for the major shop platforms. A payment engineer checks your stack before you commit, so you know the integration path before signing anything. Q: Does Paybyrd charge a monthly fee? A: No. There is no package, no minimum and no activation fee. You pay per transaction, and every rate — including the card-scheme fees passed through at cost — is published on the pricing page. --- ## Paybyrd vs Buckaroo — https://www.paybyrd.com/vs/buckaroo Summary: Paybyrd compared with Buckaroo for Dutch merchants — iDEAL bundles versus a flat per-transaction rate, €50 versus €7.50 chargebacks, card-present terminals and migration; rates as published on buckaroo.nl on 2 September 2026 Paybyrd compared with Buckaroo. Buckaroo is the omnichannel Dutch PSP — pin terminals, iDEAL bundles and credit management under one roof. Its prices reward commitment; its chargebacks cost €50. Primary markets for Buckaroo: Netherlands, Belgium. Typical migration to Paybyrd: 18 business days. Where Buckaroo is genuinely strong: - Online and in-store from one provider, with pin terminals to buy, lease or rent, and Tap to Pay on Android. - Strong in Belgium as well as the Netherlands — Bancontact at the same rates as domestic debit. - Credit management and subscription management built in, which few PSPs offer. Where merchants switch to Paybyrd: - iDEAL | Wero is €0.30 pay-as-you-go, or €0.199–€0.249 inside a monthly bundle of 20–100 transactions at €4.99–€19.99 per month. Paybyrd's iDEAL starts at €0.19 with nothing to commit to. - Cards at 1.35% for EU consumer cards and 2.30% for business and non-EU cards — about 1.49% blended for a typical mix. Paybyrd: 1.25% + €0.08, and the scheme fees inside that are published at cost. - €50 per chargeback on Visa and Mastercard. Paybyrd: €7.50. - A €58 one-off registration fee, €3.70 per month per SoftPOS device, and test transactions at €0.03 after the first 100. Paybyrd: no registration fee and a free sandbox. - One acquirer behind the checkout. Paybyrd routes each authorisation across several acquirers and retries a soft decline on a second one before the customer sees an error. - Percentages are blended. Paybyrd publishes the full Visa and Mastercard scheme-fee schedule, region by region, and passes it through at cost. - Switching takes 18 business days with shadow mode alongside Buckaroo — iDEAL | Wero and Bancontact carry over. Published rates used in the comparison (see the page for the effective date and the full table): - Buckaroo online cards: 1.49% + EUR 0.00 - Buckaroo chargeback fee: EUR 50.00 - Buckaroo monthly minimum: none published - Paybyrd online cards: 1.25% + EUR 0.08 - Paybyrd card-present: 0.5% + EUR 0.00 Q: Is Paybyrd cheaper than Buckaroo? A: On published rates: iDEAL from €0.19 at Paybyrd against €0.30 pay-as-you-go or a €4.99–€19.99 monthly bundle at Buckaroo; cards 1.25% + €0.08 against roughly 1.49% blended; chargebacks €7.50 against €50; no registration fee against €58. Run your own volume through the calculator — it uses these published rates. Q: Does Paybyrd do in-store payments like Buckaroo? A: Yes. Android terminals (PAX, Sunmi) and tap-to-pay on the same contract as online, from 0.50% in-store, rent or buy — with no monthly device subscription. Q: Can I keep iDEAL | Wero and Bancontact? A: Yes. Both are on Paybyrd and are carried over during migration, so the checkout offers the same methods from day one. Q: How long does switching from Buckaroo take? A: 18 business days is the typical Dutch migration, including a shadow-mode period where Paybyrd runs alongside Buckaroo before traffic moves. Q: What happens to chargebacks after I switch? A: Disputes on transactions processed by Buckaroo stay with Buckaroo. New disputes on Paybyrd cost €7.50 each and are handled from the same dashboard as everything else. --- ## Paybyrd vs Eupago — https://www.paybyrd.com/vs/eupago Summary: Paybyrd compared with Eupago for Portuguese merchants — local method coverage, rates and the migration path Paybyrd compared with Eupago. Eupago ships Multibanco and MB WAY well. It doesn't ship approval-rate routing, and its card rates blow out on non-EEA volume. Primary markets for Eupago: Portugal. Typical migration to Paybyrd: 14 business days. Where Eupago is genuinely strong: - Solid Multibanco + MB WAY native integration with the SIBS rails. - Familiar Portuguese brand, many SMB e-commerce merchants use it as a default. - Simple flat-fee APM pricing at low volume. Where merchants switch to Paybyrd: - Online card rate blends to 1.65% + €0.20 on a typical EU mix (after non-EEA +1% + business +1% surcharges). Paybyrd is 1.25% + €0.08 — that's 0.40% lower PLUS €0.12 lower on every single transaction. - Eupago's blended APM rate is 1.10% + €0.14 (Multibanco 60% / MB WAY 40%). Paybyrd Multibanco starts at just €0.20 fixed, MB WAY from 0.70% — same SIBS rails, significantly better blended outcome. - No card-present rate published — Eupago card-present merchants pay the online rate. Paybyrd card-present from 0.50% with terminals from €199 (rent or buy), OTA updates, offline store-and-forward buffering 500+ transactions. - 4–7% approval-rate lift via multi-acquiring routing. Eupago runs single-path — when the issuer soft-declines, the sale is gone. Paybyrd retries across acquirers in under 200ms. - Paybyrd Antifraud: 47ms p95 decisions, 55+ signals per transaction (10 IP + 45 device + behavioral biometrics + shadow-mode rollout). −16.8% chargebacks average. Eupago offers only basic rule-based screening. - InstaTax tax-free refunds built into every Paybyrd terminal — detects eligible tourist cards in <200ms, offers refund on-screen, pays you a daily revenue share. +50% merchant revenue vs other tax-refund platforms. 24h activation, zero staff training. - 99.999% uptime SLA with contractual credits (10% / 25% / 50% tiers). Named TAM + Slack SRE channel on Custom plans. Engineer-led support, not a ticket queue. Eupago publishes no comparable SLA. - Per-outlet / per-channel / per-SKU / per-currency reconciliation in the dashboard. Anomaly alerts before your reports notice. Eupago's dashboard is a daily total and little else. - 192+ currencies, 40+ countries, 20+ EU-native methods (iDEAL, Bancontact, Klarna, Floa, Apple Pay, Google Pay, Revolut Pay) — for any PT merchant with cross-border exposure. - Acquirer-agnostic: keep your existing SIBS / Unicre contracts and add Paybyrd orchestration on top. Or flip to Paybyrd acquiring in 90+ markets when ready. No bridge-burning. Published rates used in the comparison (see the page for the effective date and the full table): - Eupago online cards: 1.65% + EUR 0.20 - Eupago card-present: 1.65% + EUR 0.20 - Eupago chargeback fee: EUR 10.00 - Eupago monthly minimum: none published - Paybyrd online cards: 1.25% + EUR 0.08 - Paybyrd card-present: 0.5% + EUR 0.00 Q: We use Eupago for Multibanco + MB WAY. Does Paybyrd support both natively? A: Yes — both Multibanco and MB WAY are first-class at Paybyrd with the same SIBS rails Eupago uses. MB WAY from 0.70%, Multibanco from €0.20 fixed. Your existing payment references stay valid; we map them 1:1 on our side during migration. Q: What's the saving for a typical Portuguese e-commerce merchant at €500K / year? A: Blended savings on the same card + APM mix land around €3,800-€5,200 per year in direct fee reduction before the approval-rate lift. On tourist-heavy Lisbon / Algarve profiles with >20% non-EEA cards, savings can cross €8,000 thanks to the routing that avoids Eupago's non-EEA surcharge stack. Q: How does Paybyrd's Multibanco reference generation differ? A: Same underlying SIBS rails, same reference format, same customer-facing experience. What changes is the reporting: Paybyrd's dashboard shows Multibanco references alongside card and international-method volume in a single reconciliation view. One daily payout, one invoice per month, all channels reconciled together. Q: Can I keep using Eupago for some methods and Paybyrd for others during transition? A: Yes — Paybyrd runs in parallel with any existing PSP during migration. Most Portuguese merchants start with us handling card + international methods while keeping Eupago on MB WAY / Multibanco, then migrate the APM rails once the card-path diff reports show parity. Q: Can I keep my existing acquirer contracts? A: Yes. Paybyrd is acquirer-agnostic — keep your negotiated rates and in-flight volume commitments. We orchestrate on top. If you later choose to consolidate, we can act as your acquirer across 90+ markets, but it's a separate decision on a separate contract. --- ## Book a demo — https://www.paybyrd.com/book-demo Summary: 15-minute call with a payment engineer 15-min call · real engineer know no limits. Answer six short questions. A senior payment engineer reviews your stack and brings a tailored plan — live approvals math, routing, timeline. Book a 15-minute demo with a payment engineer. Growth should know no limits. ### steps What payment channels do you run today? Helps us route you to the right engineer. ### options Terminals, tap-to-pay, counter flows Web checkout, APMs, subscriptions Omnichannel — one ledger across every rail What are you trying to improve? Optional — skip if you just want the call. What's your annual payment volume? Rough is fine — shapes the conversation. ### options Tell us about your company. We'll come to the call with context. ### fields What's your name? ### fields Last step — where can we reach you? We'll email time slots within 12 hours. ### fields PCI Level 1 Live in 4 hours --- ## Contact — https://www.paybyrd.com/contact Summary: engineer-triaged contact form Live humans · 24h reply Talk to a Skip the gatekeeper. Write what you're actually dealing with — approvals in LATAM, POS rollout, chargebacks, integrations — and a senior engineer writes back. Paybyrd engineers answered faster than our own infra team. We were live in a day. Head of Payments, TAP Air Portugal --- ## Security — https://www.paybyrd.com/security Summary: PCI DSS Level 1, encryption (TLS 1.2+, AES-256, HSM via Azure Key Vault), 24/7 SIEM, quarterly pentests, 72h GDPR breach notification, multi-AZ resilience (RTO ≤ 4h, RPO ≤ 15 min) 21 Apr 2026 Security is the product. Paybyrd moves money, and the controls that protect it are built in, not bolted on. This page sets out — concretely — the standards we hold, the architecture we run on, and the commitments we make to merchants and their customers. This translation is provided for convenience. The English version is the authoritative text. On this page ### sections Our security commitment Merchants hand Paybyrd two things that are hard to recover once damaged: their money in flight, and their customers' card data. Our promise is that both are treated with more care than our own. We run the company under the supervision of financial-services regulators, we hold PCI DSS Level 1 — the highest merchant/service-provider tier in the payment-card industry — and we treat cardholder data as radioactive: it is touched by as few systems, as few people and for as few reasons as the service permits. This page covers the entire production estate of Paybyrd's payment services: the public APIs, the merchant dashboard, the POS fleet and the backing platform on which authorisations, captures, refunds and webhook delivery run. Corporate IT and internal tooling are governed by equivalent policies but are out of scope for this document. The commitments that follow are written to be verifiable. Every claim on this page is something we are prepared to evidence in a security questionnaire, a regulator audit or a scheme examination. Standards and certifications Paybyrd aligns its security programme to the frameworks that matter in payments, in the EU and in the jurisdictions we serve. PCI DSS Level 1 — certified. Annual Report on Compliance refreshed every 12 months by an independent Qualified Security Assessor; quarterly ASV scans against our public ingress; attestation available to merchants under NDA. ISO/IEC 27001 — information-security management system maintained across the platform; independent certification in progress. SOC 2 Type II — report in preparation , with a 12-month observation window commencing 2026; bridge letter available on request once the first report is issued. PSD2 — strong customer authentication. Authentication flows implement RTS-compliant SCA with exemption handling (TRA, low-value, MIT) and 3-D Secure 2.x for remote card transactions. GDPR / AVG. Full alignment with Regulation (EU) 2016/679 and the Dutch implementation; DPO appointed; records of processing activities maintained; breach-notification procedure aligned to articles 33 and 34 (see Privacy Policy). NIS2. Where the Directive applies to Paybyrd or to a group entity, we operate an aligned risk-management, supply-chain and incident-reporting regime. We do not claim certifications we do not hold. Where a control or certification is in progress, we say so. The platform is designed so that compromise of any single component does not compromise the cardholder data or the money-movement path. PAN tokenization on ingress. Primary Account Numbers are tokenized at the first system that sees them; downstream services hold and transmit tokens, not PAN. Detokenization is gated, audited and limited to the minimum set of processes that require it. Encryption in transit. TLS 1.2+ enforced on every public endpoint (TLS 1.0 and 1.1 disabled); HSTS with preload; modern cipher suites only; mTLS for sensitive service-to-service calls and for partner integrations that require it. Encryption at rest. AES-256 encryption for all production data stores, backups and snapshots; separate encryption domains for PCI-scoped data. Key management. Cryptographic keys are generated, stored and used within HSM-backed key-management infrastructure; key usage is logged; rotation runs on a published cadence with emergency re-keying procedures. Network segmentation. Production runs in isolated VPCs with private subnets, egress-only NAT and no inbound internet reachability for compute. The PCI DSS scope is a distinct environment with its own ingress, its own identities and its own change-control. Immutable audit logs. Security-relevant events — authentication, authorisation, configuration change, data access — are written to append-only storage with tamper-evident retention suitable for forensic review. Access control and identity Who can touch production is as important as how production is built. Least privilege. Access is granted through role-based access control, provisioned from HR systems and reviewed against job function. Default is no access. Hardware-key MFA. Hardware security keys (WebAuthn / FIDO2) are mandatory for every production touchpoint — SSO, cloud console, bastion hosts, deployment pipelines, administrative tooling. Software one-time codes are not accepted for production. Quarterly access reviews. Every production entitlement is re-certified at least every 90 days by the owning manager; stale grants are revoked automatically at the end of the review window. Just-in-time elevation. For incident response and rare operational tasks, privileged access is obtained through time-bounded JIT grants with documented justification; standing admin rights are avoided wherever practicable. Session recording. Privileged shells are session-recorded and retained for forensic replay. Offboarding SLA. On termination or role change, production access is revoked within one hour of the triggering HR event, irrespective of business hours. Monitoring and detection Attacks are detected by the controls that see them, not by hope. 24/7 SIEM correlation. Security telemetry from the platform, the cloud control plane, endpoints and identity providers is centralised and correlated in real time; detection rules cover known attacker techniques and are tuned against Paybyrd's own threat model. Anomaly detection. Authentication events, transaction flows and API-usage patterns are modelled for deviation; anomalous behaviour triggers automated containment and a human review. On-call and pager SLA. A security on-call rotation answers Sev-1 pages within 15 minutes , 24/7. Engineering, platform and fraud on-calls are paged in parallel for incidents that cross domains. SOC staffing. Monitoring is delivered by an internal security operations function supported by a vetted managed-detection partner for out-of-hours coverage; handover runbooks are rehearsed. Finding problems early is cheaper than explaining them later. Third-party penetration tests. Independent pentests are commissioned at least quarterly , covering the public APIs, the merchant dashboard, the POS estate and the internal authenticated surface. Findings are tracked to closure with SLA-bounded remediation. Continuous SAST and DAST. Static analysis and dynamic application security testing run on every deploy; pipelines block merges that introduce critical findings. Software composition analysis. All dependencies are continuously scanned against authoritative CVE feeds; critical patches ship with a 7-day SLA from disclosure, shorter where active exploitation is observed. Bug bounty. Paybyrd operates a responsible-disclosure programme open to good-faith security researchers. Reports go to security@paybyrd.com . Safe harbour. Good-faith research within the scope of the programme is authorised and will not be subject to legal action by Paybyrd. Researchers who respect scope, avoid degradation of service and do not exfiltrate or disclose data beyond what is strictly necessary to evidence a finding are covered by this safe harbour. Incidents are rehearsed, not improvised. Classification. Incidents are triaged into four severities — Sev-1 (payments systemically impacted, suspected data breach, regulatory exposure), Sev-2 (significant degradation without systemic impact), Sev-3 (localised impact or single-merchant/partner), Sev-4 (low-impact, workaround available). 72-hour breach notification. Where a personal-data breach meets the article 33 GDPR threshold, Paybyrd notifies the competent supervisory authority without undue delay and, where feasible, within 72 hours . Affected merchants are notified in parallel so that controllers can discharge their own obligations; where the breach is likely to result in a high risk to data subjects, article 34 notification follows without undue delay. Scheme and regulator reporting. Card-scheme operational-incident reports and financial-regulator notifications are filed on the timelines prescribed by the relevant rules. Monthly IR drills. The response team runs at least one tabletop or technical drill every month, covering a rotating set of scenarios (ransomware, key compromise, fraud wave, third-party outage). Public post-mortem. For every Sev-1 affecting merchants, Paybyrd publishes a post-incident review to the status page within a reasonable period, describing impact, root cause and remediation. Data is handled on the principle that the safest record is the one we never collected, and the next safest is the one we have already destroyed. Residency. Production data for the payment platform is stored in the European Economic Area by default (primary region: eu-central-1, Frankfurt). Cross-border transfers occur only with appropriate article 46 safeguards and are documented in the Privacy Policy. Retention. Data is retained for the periods required by legal, regulatory and scheme obligations, as set out in the Privacy Policy. Retention is enforced by automation, not memory. Destruction. At end of retention, data is destroyed through cryptographic shredding — the encryption keys that protect the data are destroyed within the HSM, rendering the ciphertext unrecoverable — in addition to logical deletion from the data store. Environment separation. Live and sandbox environments are strictly separated: separate networks, separate identities, separate keys, separate datasets. Production data is not used in sandbox or development. Business continuity and resilience Payments cannot pause, and the platform is engineered to keep moving when components fail. Multi-AZ deployment. Core payment services run across multiple availability zones within a region; the loss of a single zone is expected and handled automatically. Automated failover. Database primaries, API gateways and message brokers are configured for automated failover with health-checked routing. RTO and RPO. For production payment services, the recovery-time objective is ≤ 4 hours and the recovery-point objective is ≤ 15 minutes for a regional-level event requiring activation of the disaster-recovery plan. Tabletop exercises. Business-continuity and disaster-recovery plans are exercised at least once per quarter , including at least one full-scope exercise per year that spans engineering, security, operations and customer-facing functions. Report a vulnerability --- ## Service Level Agreement — https://www.paybyrd.com/sla Summary: 99.999% monthly availability, tiered service credits (10/25/50%), Sev-1 15-min pager, published exclusions 21 Apr 2026 Service Level Agreement. Specific numbers, not aspirational prose. This SLA governs the availability of Paybyrd's core payments platform, the response we commit to when things go wrong, and the credits merchants are entitled to when we fall short. This translation is provided for convenience. The English version is the authoritative text. On this page ### sections Paybyrd commits to a monthly availability of 99.999% for the core payments API — specifically the authorization, capture, refund and webhook-delivery endpoints — measured across each calendar month. Definition of monthly availability Monthly availability is calculated as: Availability (%) = (Total Minutes in Month − Unavailable Minutes) / Total Minutes in Month × 100 "Unavailable Minutes" means minutes during which more than 5% of valid requests to the covered endpoints, measured at the platform edge and aggregated over rolling one-minute windows, return HTTP 5xx errors or fail to respond within the published timeout, for reasons attributable to Paybyrd and not falling within the Exclusions below. Planned maintenance Planned maintenance is excluded from the availability calculation, provided that it is announced on the status page at least seven (7) days in advance and that the total duration of planned maintenance in any calendar month does not exceed four (4) hours . Maintenance windows are scheduled outside peak merchant hours wherever feasible. Service credit schedule If monthly availability falls below the committed level, the merchant is entitled to a service credit against the next invoice, calculated as a percentage of the monthly fees for the affected service: Monthly availability < 99.999% and ≥ 99.99% — 10% credit Monthly availability < 99.99% and ≥ 99.95% — 25% credit Monthly availability < 99.95% — 50% credit How to claim Credit claims must be submitted in writing to sla@paybyrd.com within 30 days of the end of the month in which the shortfall occurred. Claims must identify the affected service and the period concerned; Paybyrd may request reasonable corroborating detail. Where the claim is valid, the credit is applied to the next invoice issued after validation. Service credits are the merchant's sole and exclusive financial remedy for availability shortfalls under this SLA. Incident severity tiers and response When an incident affects production, the first task is to classify it. Severity governs pager behaviour, the cadence of communications and the escalation path. Sev-1 — payments down or systemic Pager response: ≤ 15 minutes Initial status-page update: ≤ 30 minutes from detection Ongoing updates: at least hourly until resolved Post-mortem: published to the status page after resolution Sev-2 — significant degradation Pager response: ≤ 1 hour Initial status-page update: ≤ 2 hours from detection Ongoing updates: every 4 hours until resolved Sev-3 — single feature, merchant or partner degraded Response: ≤ 4 working hours Updates: by end of working day Sev-4 — low impact, workaround available Response: next working day Tracked as a standard engineering ticket Support response commitments Paybyrd offers plan-tiered support with consistent severity-based response targets. Response targets by severity — all plans Sev-1 — first response ≤ 15 minutes Sev-2 — first response ≤ 1 hour Sev-3 — first response ≤ 4 working hours Sev-4 — first response next working day Coverage hours Standard plan — support during merchant working hours (08:00–20:00 CET, Monday to Friday) for Sev-3 and Sev-4; 24/7 for Sev-1 and Sev-2. Business plan — extended support hours (07:00–23:00 CET, seven days a week) for Sev-3; 24/7 for Sev-1 and Sev-2. Enterprise plan — 24/7 support across all severities, named account engineer, dedicated Slack Connect channel and quarterly operational reviews. Paybyrd maintains multiple parallel channels for SLA-relevant communication. Merchants should not need to guess where to look. Status page — status.paybyrd.com . Real-time incident status, scheduled maintenance and historical uptime metrics. Merchants can subscribe to email and webhook notifications per component. Email — help@paybyrd.com for all merchants and severities; sla@paybyrd.com for credit claims. Slack Connect — a dedicated shared channel is provided to Enterprise merchants for day-to-day operational contact and direct Sev-1 escalation. Phone bridge — for live Sev-1 incidents, a phone bridge is opened and bridge details are shared via the channels above. The following do not count against Paybyrd's availability commitment or generate service credits: Planned maintenance that complies with the notice and duration limits in the Service availability section above. Force majeure — events beyond Paybyrd's reasonable control, including but not limited to natural disasters, armed conflict, civil unrest, generalised internet or DNS outages, and acts of a sovereign authority. Merchant-caused outages — including but not limited to invalid or revoked API credentials, misconfigured webhook endpoints, IP allow-list errors on the merchant's side, exhaustion of merchant-side rate limits, and failures of merchant infrastructure. Scheme Owner, Acquirer or upstream provider failures — outages or degradations at card schemes (for example Visa, Mastercard), acquirers, issuing banks, alternative-payment-method providers or other third-party processors outside Paybyrd's operational control. Beta, sandbox and non-production services — services expressly labelled as beta, preview or sandbox are excluded from this SLA. Changes requested by the merchant that cause the outage — for example, a merchant-requested configuration change that takes a production endpoint offline. Claim a credit --- ## Privacy Policy — https://www.paybyrd.com/privacy-policy Summary: GDPR-compliant; sub-processor list (Azure West Europe, Cloudflare, Datadog, Google Workspace); 30-day prior notice on sub-processor changes; data-subject rights; DPO contact dpo@paybyrd.com 21 Apr 2026 Your data, handled with the same care we give your money. This policy explains what we collect, why we collect it, how long we keep it, and the rights you have over it. Written in plain terms; legally binding in English. This translation is provided for convenience. The English version is legally binding. On this page ### sections Who we are Paybyrd.com — which includes Paybyrd B.V. and all affiliated companies (together, "Paybyrd" , "we" , "our" or "us" ) — respects your privacy and is committed to protecting your personal data. This policy governs how personal information is handled across Paybyrd's platforms and services. Paybyrd B.V. acts as the data controller and is based in the Netherlands. Depending on the context, we act as either a data controller or a data processor. Our representative in the EU Paybyrd B.V. is registered in the Netherlands under number 76168573, with its registered office at Parnassusweg 819, 1082 LZ Amsterdam, The Netherlands. Data Protection Officer Email: dpo@paybyrd.com (available in English, French and Spanish) Post: Data Protection Officer, Paybyrd B.V., Parnassusweg 819, 1082 LZ Amsterdam, The Netherlands You have the right to lodge a complaint with a supervisory authority, but we would appreciate the opportunity to address your concerns first. Please contact us before filing a complaint. Personal data we collect From your use of our website Full name, email address, phone number, website URL Browser information, IP address, visit duration, pages viewed Cookie and server log data From your use of our services Sandbox users: name, email address and website information. Merchants: full name, email, date of birth, home address, proof of address, copy of ID or passport, and compliance-related documentation. Payment processing: billing address, delivery address, date of birth, purchase amount, date of purchase, payment method, credit or debit card number, and bank account information. Compliance data: information obtained from credit reference agencies, fraud-prevention services and government sanction lists. Sandbox Hub notice Our Sandbox Hub is intended to be used as a test environment. We do not envisage collecting, storing or processing any personal data while you use it. Cookies and similar technologies What we use Two analytics and marketing tools touch your visit to paybyrd.com: Plausible Analytics — cookieless, privacy-first traffic measurement. Records page views, referrers, and country at an aggregate level. Sets no cookies, identifies no individual visitor, and is never shared with third parties. Google Ads conversion tracking — measures whether visitors who arrive from a paid Google Ads click later complete a meaningful action on the site (booking a demo, submitting the contact form). Sets the cookies _gcl_aw , _gcl_au and _gcl_dc , which store an anonymous click identifier ( gclid ) tying the click to the later action. These cookies expire approximately 90 days after they were set and contain no personally identifying information. Opting out You can block these cookies at any time without registering a preference with us. Use one or more of the following: Browser controls — block third-party cookies, clear stored cookies, or run a tracking-protection extension. Every major browser supports this in two clicks. Google's ad-personalisation settings — visit adssettings.google.com to opt out of personalised advertising across all Google services. EDAA / NAI opt-out tools — youronlinechoices.eu (EU) or networkadvertising.org/choices (US) for industry-wide opt-outs. What we don't use Paybyrd does not use Meta Pixel, TikTok Pixel, LinkedIn Insight, Hotjar, FullStory, or any session-replay or behavioural-analytics tool that records what you do on a page. We don't sell or share visitor data with data brokers. How we use your personal data Legal bases for processing Performance of our contract with merchants Our legitimate business interests Legal and regulatory compliance Product improvement and analysis Purposes Fraud detection and prevention Payment processing and customer service Identity verification and KYC/AML compliance Account authentication Marketing communications Business analytics and intelligence Service improvement and development Website administration and troubleshooting Notice to our merchants Merchants are responsible for ensuring that their customers' personal data is handled in compliance with applicable privacy laws. You must comply with the personal data protection laws of your country of origin and of the countries in which you offer products or services. Where applicable, you must also comply with the Mastercard Binding Corporate Rules. Where we act as a data processor on your behalf, we will follow your documented instructions under a written data-processing agreement. Disclosures of your personal data We may share your personal data with the following categories of recipients: Affiliates — companies within the Paybyrd group, to provide our services Business partners — card schemes, payment providers, acquirers and merchant service providers Service providers — cloud, hosting, analytics, IT infrastructure and customer-service vendors Advertising networks — Google AdWords and Facebook, for remarketing Legal and safety — law enforcement, fraud-prevention bodies and regulators We do not allow our third-party service providers to use your personal data for their own purposes. All third parties must comply with data-protection regulations and implement appropriate security measures. Transfer of data Our preference is to store and process your data within data centres located in the European Economic Area (EEA). Transfers outside the EEA occur only with adequate safeguards and under written agreements that comply with EU data-protection law. Transfers may occur when you transact with non-EEA merchants, when you use non-EEA payment methods, or when you use non-EEA currencies. Paybyrd will take all reasonable legal, technical and organisational measures to ensure that if your data is transferred outside the EEA, it is treated securely. We are PCI DSS (Payment Card Industry Data Security Standard) Level 1 compliant, which is the highest standard set by the payment card industry. Access to your personal data is limited to employees and third parties with a genuine business need, all of whom are bound by duties of confidentiality. We have procedures in place to address any suspected data breach and will notify you and any applicable regulator where we are legally required to do so. Breach notification commitment. In accordance with article 33 of the GDPR, where a personal data breach is likely to result in a risk to the rights and freedoms of natural persons, Paybyrd will notify the competent supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware of the breach. In accordance with article 34 of the GDPR, where the breach is likely to result in a high risk to the rights and freedoms of affected data subjects, Paybyrd will communicate the breach to those data subjects without undue delay, in clear and plain language, together with the information prescribed by article 34(2). Affected merchants acting as controllers will be informed in parallel so that they can discharge their own notification duties. Where Paybyrd processes personal data on behalf of a merchant (acting as a data processor under article 28 of the GDPR), we may engage carefully selected sub-processors to assist in delivering the service. A sub-processor is a third party engaged by Paybyrd that processes personal data on our documented instructions, under a written contract containing data-protection obligations at least equivalent to those owed by Paybyrd to the controller. Our main categories of sub-processors are: Microsoft Azure (EU, West Europe — Amsterdam) — production cloud infrastructure, object storage, database hosting and key management via Azure Key Vault. Cloudflare (global, with EU data-residency controls) — DDoS protection, web application firewall and content delivery network in front of our public endpoints. Datadog (EU region) — observability, metrics, log aggregation and SIEM correlation for operational and security monitoring. Google Workspace (EU residency for mail) — internal collaboration, email and document authoring. No production cardholder data is processed in this environment. The Financial Institutions named in our Terms & Conditions section J.15 — licensed acquirers, scheme participants and settlement banks that execute payment processing, acquiring and card-scheme settlement on our network. An up-to-date list of sub-processors is available on request from dpo@paybyrd.com . Paybyrd will give merchants acting as controllers at least 30 days' prior notice of any intended addition or replacement of a material sub-processor. Merchants have the right to raise a reasoned objection to any such change; where an objection cannot be resolved, the merchant may terminate the affected service in accordance with the Merchant Agreement. Retention of your information We only retain your personal data for as long as necessary to fulfil the purposes for which we collected it. Indicative retention periods: Identity and contact data (merchants) — 5 years after contract termination or last contact, for contract performance and regulatory purposes Technical and usage data — 3 years for prospects; 5 years for clients after termination Identity, contact and technical data — 5 years post-termination, for business administration and protection Credit card and transaction data — 5 years from transaction date or end of business relationship, for transaction processing and AML/regulatory compliance Closed accounts retain data for legal-compliance purposes. Data may be anonymised for statistical use without further notice. Please keep your information current. Under data-protection law you have the following rights in relation to your personal data: Access — to receive a copy of the personal data we hold about you Correction — to have inaccurate or incomplete data corrected Erasure — to request deletion where there is no legitimate reason to continue processing Objection — to object to processing based on legitimate interests or direct marketing Restriction — to suspend processing while we verify accuracy or legal grounds Portability — to receive your data in a structured, machine-readable format Withdraw consent — to revoke consent for specific processing purposes at any time Manual review — to contest automated decision-making in transaction processing If you wish to exercise any of these rights, please contact dpo@paybyrd.com . Withdrawal of consent does not affect the lawfulness of processing carried out before the withdrawal. Changes to this privacy policy We reserve the right to update this privacy policy at any time, and we will publish an updated policy if we do so. Updates may be communicated through publication of the revised policy on our website or by other appropriate means. --- ## Terms and Conditions — https://www.paybyrd.com/terms-and-conditions Summary: merchant agreement — 12 sections, governed by Dutch law, courts of Amsterdam 21 Apr 2026 The rules of the road for using Paybyrd. These Terms and Conditions form part of the Merchant Agreement between Paybyrd B.V. (Parnassusweg 819, 1082 LZ Amsterdam, Chamber of Commerce 76168573, VAT NL860532239B01) and the Merchant. Please read them carefully. This translation is provided for convenience. The English version is legally binding. On this page ### sections The following defined terms apply throughout these Terms and Conditions: 3D Secure — a protocol (Verified by Visa, Mastercard SecureCode) for transaction authentication. Account Holder — a person authorised to use an issued Payment Method. Acquirer — a licensed financial institution enabling Payment Method acceptance. API — a direct, secured internet connection between the Merchant site and the Paybyrd environment. Authorisation — the process of requesting permission to use a Payment Method for a purchase. Bank Account — an account held with the Acquiring Financial Institution for fund settlement. Business Day — a regular working day unimpeded by holidays or special events. Capture Period — the timeframe within which an authorised transaction may be executed (varies by Payment Method). Capturing — confirmation to execute an authorised transaction and charge the Account Holder. Card — a Credit or Debit Card used for transactions. Card Association / Card Scheme — Visa, Mastercard, Discover or comparable bodies. CVM Code — the 3- or 4-digit code on a card (CVV2, CVC2, CID). Cardholder — a person issued and authorised to use a Card. Chargeback — a transaction reversal requested by the Account Holder or Issuer per Scheme Rules. Chargeback Fee — a fee charged by Paybyrd per chargeback occurrence. CNP (Card Not Present) Transaction — a transaction where the cardholder is absent from the point of sale. Credit Card — a card permitting transactions on the cardholder's credit account. Customer Area — the secured interface for Merchant transaction management and settings. Debit Card — a card enabling debit account transactions. Delivery Date — the date Merchant Products/Services are delivered to the Account Holder. Delay Level — the minimum Deposit level set for the Merchant. E-Commerce Transaction — a transaction submitted via secure internet without physical presence. Eligible Merchant — a Merchant meeting Paybyrd qualification and Acquirer/Card Scheme requirements. Financial Institutions — Acquirers or other regulated authorised entities. Fine — an additional payment imposed by Scheme Owners or Acquirers for violations, fraud or chargeback excess. Hosted Payment Pages — the Paybyrd-hosted interface for Account Holder payment entry. Inflation — Euro-area inflation (HICP All Items) from Eurostat. Interchange Fee(s) — the collective fees from Issuing Banks, Card Schemes and Acquirers. Issuer / Issuing Bank — the institution issuing Payment Methods to the Account Holder. Merchant — a company processing transactions via Paybyrd for products/services. Merchant Agreement — the contract for Paybyrd service provision, including these Terms and Conditions. Merchant Product/Service — a product or service sold by the Merchant that requires transaction processing. MO/TO (Mail Order/Telephone Order) Transaction — a non-present transaction via mail, fax or phone. MSC (Merchant Service Charge) — a fee per transaction (percentage, fixed, or combination). Order Currency — the currency in which the transaction was originally offered to the Account Holder. Payment Currency — the currency in which the transaction is processed. Payment Details — the information required for transaction submission and fraud checks. Payment Interface — the electronic connection method for providing transaction details. Payment Method — a method enabling payment (Cards, bank transfers, direct debits). PCI DSS — the security standards for card-data transmission, processing and storage. POS (Point of Sale) Transaction — a transaction via a POS Terminal with the cardholder present. POS Terminal — a device submitting POS transactions via encrypted internet connection. Processing Fee — a fee charged per transaction submission regardless of amount or method. Refund — a partial or full transaction reversal reimbursing the Account Holder. RFI (Request for Information) — a request by a Scheme Owner or Acquirer for transaction information. Scheme Owner — the entity offering or regulating the relevant Payment Method. Scheme Rule — the bylaws, rules, regulations and procedures from Scheme Owners (binding). Service(s) — the technological services provided by Paybyrd. Settlement — payment from the Acquiring Financial Institution (AFI) to the Merchant minus refunds, chargebacks, fees and deposit requirements. Software — programs and data that Paybyrd develops or operates for service provision. Terms and Conditions — the current version of these terms. Traffic — the Merchant transaction profile (volume, spread, geographical distribution). Transaction — an Authorisation request from the Account Holder submitted by the Merchant. Transaction Fee — the sum of the MSC and the Processing Fee. Uncompleted Order Amount — the total of authorised, captured or settled transactions for undelivered products. Working Hours — 09:00–18:00 CET on Business Days in the Netherlands (or published alternatives). 2. Scope of the agreement A.1 — Payments acceptance Paybyrd enables Merchants to accept customer payments for products and services. Paybyrd assumes no liability for the items purchased. During service provision, Paybyrd acts as technical service provider for the Financial Institution that ultimately provides the payment services. A.2 — Payments platform service The Paybyrd platform delivers real-time or near real-time processing with high availability (see Service Levels). Services include reconciliation for Transactions acquired and settled via Paybyrd partner financial institutions. Submission requirements: Card Not Present Transactions: Hosted Payment Page, Card Collect functionality, or iFrame POS Transactions: via a Paybyrd-approved POS Terminal Merchant obligations: Provide all Paybyrd-requested data for each transaction Non-compliance authorises immediate suspension of transaction processing Paybyrd may revise required data via Customer Area notification A.3 — Final pricing and customer details Pricing is the pricing registered on our website for self-service signups, or the rates specified in the Merchant Agreement. Paybyrd reserves the right to adjust acquiring fees based on: nature and risk level of the business, type of product/service, Merchant credit history, processing history, and other business-related factors. Any adjustment will be communicated with a reasoned explanation. 3. Registration with Paybyrd B.1 — Registration process Merchants must provide information about their business, activities and shareholders to enable Paybyrd to comply with anti-terrorism, financial-services laws and KYC requirements. The Merchant warrants that all Registration Information is correct and current. Paybyrd conducts identity verification and risk assessment and may share information with Financial Institutions for independent assessment. Acceptable registration materials include financial statements, invoices, and government-issued permits, identifications and permissions. Support for specific Payment Methods is subject to Scheme Owner/Acquirer acceptance and may be withheld or withdrawn at their discretion; some methods may require direct Acquirer agreements. The Merchant authorises Paybyrd, by mandate, to act in the Merchant's name with relevant Acquirers and Financial Institutions; to execute, amend, renew and terminate agreements on the Merchant's behalf; to handle requests and instructions regarding pricing, settlement and bank-account details; and to submit Registration Information to Scheme Owners and Acquirers for permission. The Merchant will not hold Paybyrd, any Acquirer or any Financial Institution liable for actions taken in reliance on this mandate. B.2 — Onboarding requirements Services are available only to legal persons or constructs (organisations) and exclude payments relating to the personal, family or household sphere. At agreement entry and on request, the Merchant must provide: Chamber of Commerce certificate; shareholder registry; proof of ultimate beneficial owners; certified government-issued identity documents for all beneficial owners and managers; bank statements; business proof of address; manager/owner proof of address; Tax ID; and certified company financials. Paybyrd may request additional documents without notice. The Merchant represents that registering persons are competent and authorised; the Merchant is a national of the indicated country; the Merchant is authorised for business development in the indicated country or countries; and all provided information is complete, truthful and will remain current. Changes in corporate name, status, structure, service type or scope must be communicated within 48 hours. Access credentials: Paybyrd provides a username (partner ID) and a temporary password. Credentials are strictly personal and non-transferable; the Merchant is responsible for any damage or loss resulting from misuse and must report loss, theft or misuse immediately. B.3 — Verification and acceptance By accepting this agreement the Merchant permits Paybyrd and its Financial Institutions to retrieve Merchant information, share information with third parties (including credit-history and data providers) and update information periodically for continuous verification. The Merchant permits Paybyrd to share information with Financial Institutions regarding application and account status, transactions, statutory/supervisory compliance, payment-service management, service improvement and risk management. Paybyrd may, in exceptional circumstances, request an office inspection or examination of financial records. Non-compliance with an information request within 10 days may result in suspension or termination. B.4 — Authorisation for registration and contracting formalities Paybyrd may undertake necessary formalities for Merchant registration with Acquirers or specific payment methods. Paybyrd cannot guarantee acceptance by any specific Acquirer or payment method; the Merchant remains responsible for legal and regulatory compliance. 4. Services provided by Paybyrd C.1 — Omnichannel payment platform Paybyrd commits commercially reasonable efforts to maintain platform availability, with a minimum 99.9% average uptime measured quarterly. The uptime calculation excludes downtime caused by Merchant acts or omissions, Acquirer or Scheme Owner actions, Merchant-requested changes, internet failures, individual Payment Method failures, or force majeure. The Merchant must immediately notify Paybyrd of any downtime experienced and cooperate in full with investigation and resolution. Paybyrd minimises offline requirements for planned maintenance and provides advance notice where possible. Emergency maintenance is used only for force majeure or emergency situations. Paybyrd may immediately suspend service, deny Payment Platform access, terminate the agreement and recover incurred losses if the Merchant is suspected of conflict with the agreement. Prohibited uses include (non-exhaustively) purchase or sale of goods or services conflicting with applicable law or public morals; sale without willing or able delivery within a reasonable period; personal-data use conflicting with GDPR; hacking or phishing; payment collection without a legally valid customer contract; deliberate misleading of customers, institutions, intermediaries, suppliers or third parties; and commission of, or assistance with, fraudulent activities. C.2 — Payment methods Each Payment Method has distinct characteristics, risks and conditions, including cost structure, payment term, payment manner and customer dispute/refund possibilities. Conditions are published on our public website or in the final pricing form. By enabling a Payment Method via the Dashboard the Merchant is assumed to understand and accept those conditions. Paybyrd may add, delete or restrict Payment Methods. C.3 — Foreign currency Paybyrd offers multi-currency payment acceptance. Financial partners convert payments into euros or into the original currency. Settlement amount is calculated on an individual payment basis using a buying rate (currency exchange rate plus partner supplier costs) with a mark-up. Refunds are converted to the customer's original payment currency regardless of who initiates the refund. The customer receives the full original payment amount; the Merchant is charged per the buying-rate calculation plus mark-up. C.4 — Account Holder payment currency Paybyrd may offer Account Holders a Payment Currency different from the Order Currency. The Merchant always receives Settlement in the Order Currency unless otherwise agreed, or unless the Merchant does not provide an account for Order Currency settlement. C.5 — Cardholder authentication methods For Hosted Payment Page transactions, 3D Secure authentication is offered as a Merchant option where the Acquirer or Payment Method supports it and the current Paybyrd Software supports it. C.6 — Fraud control All transactions are screened by the Paybyrd Fraud Control Tool, which performs checks and attaches fraud-likelihood scores. The tool does not guarantee prevention of fraudulent transactions, chargebacks or fines. Paybyrd may change Merchant-set scoring values if there are clear, objective indications of unacceptable fraud risk or excessive chargebacks, and may add or change checks without notice. Paybyrd may cancel transactions reasonably suspected of being fraudulent or criminal. C.7 — Captures For some Payment Methods, Merchants may request Authorisation without immediate Capture. Authorised transactions have a maximum Capture Period (set by the Issuing Bank or Scheme Owner). The Merchant is responsible for timely capture. Beyond the Capture Period, prior authorisation assurance is invalid, increasing non-settlement and chargeback risk. General account: minimum 5-day Capture Period. C.8 — Settlements The Merchant is responsible for evaluating Payment Method settlement conditions as communicated via the Customer Area and Scheme Owner channels. Paybyrd will not compensate for late or non-performance, insolvency or bankruptcy of any Acquirer or Scheme Owner. Paybyrd may request that a Financial Institution withhold settlement if captured transactions are suspected of fraud or illegality, or are likely to be subject to chargeback, pending investigation. No interest is due over amounts held prior to settlement, except where Settlement is delayed by 90 days or more due to Paybyrd's intent or gross negligence, in which case interest accrues at 3-month EURIBOR + 2%. C.9 — Data requirements The Merchant provides Paybyrd with all requested information regarding current and expected Delivery Dates, average time from Authorisation to Delivery, current ability to provide Products/Services, and financial status, solvency and liquidity. This information is used to estimate the likely Uncompleted Order Amount for Deposit Level determination. 5. Merchant obligations D.1 — Scope of acceptance The Merchant may only use the Services for payment of Merchant Products/Services registered in the Merchant Agreement. Paybyrd acceptance is strictly linked to the registered description; prior written approval is required for changes or additions. D.2 — Prohibited activities The Merchant may only accept and process payments for lawful goods and services. Prohibited categories include (non-exhaustively): erotic content or services; high-risk financial products or services; certain medicines; illegal or stolen products; illegal games of chance; narcotics and certain food supplements. The full list is published on our public website and may be changed at any time. If Paybyrd suspects use of the Services for prohibited activity, the Merchant must cease immediately upon request. Failure to comply within the timeframe set by Paybyrd authorises immediate termination. D.3 — Merchant obligations and restrictions Paybyrd's acceptance does not constitute advice on the legality of Products/Services or their use of the Services. The Merchant is solely responsible for compliance with Scheme Rules, laws of the country of origin, laws of the customer base, and Payment Method-specific restrictions. Services may not be used for Products/Services with Delivery Dates exceeding 12 months after transaction submission. E-commerce requirements. The Merchant must provide Account Holders with per-transaction website information including a complete goods/services description; returns and refund policy; customer-service contact details; address; delivery policy; consumer data-protection policy; and any information legally required in the relevant jurisdiction. Records. The Merchant must maintain electronic or other records relating to the transaction and the ordering and delivery of the Products/Services for the greater of 2 years after processing or the applicable warranty period. Records include shipping details, invoices for delivered Products/Services and all Account Holder contacts. The Merchant will cooperate in any record audit during a Chargeback, suspected-fraud or RFI investigation. D.4 — Laws and regulations The Merchant warrants that its online and offline activities comply with all relevant laws, regulations and this Agreement; that it makes correct use of the Payment Platform; and that it provides correct payment-platform information to its customers. The Merchant will not perform or omit acts it knows, or could reasonably know, would result in punishable or unlawful use of the Payment Platform or could cause damage. D.5 — Scheme Owner fines Key Scheme Rule violations expose the Merchant to significant fines (from €25,000 up to €1 million or more). Scheme Owners levy fines to protect Account Holders, Merchants and Payment Method providers against misuse, fraud, illegal activities, law violations, reputational damage and excessive costs. Fine-subject Scheme Rules include: use of a Payment Method for unauthorised Products/Services; use for law-violating Products/Services; use for Scheme-Owner-prohibited Products/Services (adult content, drugs, arms, gambling); use for third-party benefit or resale; chargeback percentage exceeding acceptable levels; Payment Details security or confidentiality breaches; and fraudulent or misleading activities against Account Holders. Merchants are advised to review current Scheme Rules and applicable law changes regularly. Paybyrd provides Scheme Rule access and summaries via the Customer Area. The Merchant fully indemnifies Paybyrd against fines resulting from breach of the Merchant Agreement or Scheme Rules. D.6 — Information provision The Merchant website must show: contact information (customer-service address, phone, email); product/service pricing; delivery information (timeliness and charges); payment terms; and subscription information (term, cancellation method) where relevant. Delivery delays and order cancellations must be communicated clearly and proactively. Paybyrd may charge the Merchant for any investigation costs arising from complaints that require Paybyrd's involvement. 6. Payments and funds E.1 — Safeguarding customer funds Paybyrd's partner Financial Institutions are obliged to safeguard funds received. They may use separate, regulated or registered entities that receive funds on behalf of the parties or hold them securely. Payments are made per Paybyrd's instructions; incorrect payments are the consequence of incorrect Paybyrd instructions. Payment requests are directed to Paybyrd, not to the financial entities. The Merchant waives any right to demand amounts from those entities or to take legal action against them. E.2 — Rates and pricing Paybyrd charges per successful Transaction at the rates displayed in the Dashboard (or, if absent, at the basic rates published on our website). Paybyrd may unilaterally raise service prices on one month's prior notice, with the increase effective for services rendered after the notice period. The Merchant may cancel during the one-month notice period by written notice, subject to a three-month end-of-notice period. Rates are exclusive of VAT and government charges unless stated otherwise. This clause does not apply to communicated Acquirer or Scheme Owner fee increases not included in Paybyrd fees (e.g. Interchange Fee increases with Interchange Plus pricing) or to changes required by applicable law. Without Merchant notification or failure to terminate, rate increases are effective from the Paybyrd-set date. E.3 — Transactions Paybyrd processes only transactions authorised by an Intermediary or Financial Institution. The Merchant is responsible for the correctness of Transaction Data submitted to the platform. The contractual relationship is between the Merchant and the customer, and between the Financial Institution and the customer; Paybyrd is explicitly outside that relationship. E.4 — IC++ pricing / MSC blended fee The Merchant acknowledges that the underlying Interchange Fee is calculated per the Merchant-provided Traffic characteristics documented in the Merchant Agreement. If actual Traffic materially differs from the figures provided, Paybyrd may proportionally adjust the blended fee or apply IC++ pricing. Current Card Scheme Interchange pricing is published by the Card Schemes and linked from the Customer Area. E.5 — Payment fee exemption Merchants meeting certain volume requirements may be eligible for payment-fee exemption. Payment fees are charged at transaction time and refunded within 60 days upon receipt of a marketing-fees invoice. The invoice must include a clear description of Paybyrd Platform Marketing fees and a PO number issued by Paybyrd finance, and is subject to finance-team review and a 45–60 day refund processing window. E.6 — Payment The Merchant agrees that fees and sums, including Chargebacks, Fines and Deposit Level requirements, may be withheld from Settlement amounts. If a Settlement is insufficient to cover amounts due to Paybyrd, the remaining amount is due within 30 days of invoice date. Paybyrd may require immediate payment or set-off merchant debts against Settlements in refund/chargeback cases where the outstanding amount exceeds the Settlement, in coverage of merchant liability, or for other Agreement-required charges including fines. Interest of 1% per month accrues on unpaid Merchant-owed amounts. Upon acceptance of these Terms, Paybyrd is granted the right to establish a direct-debit mandate for daily, weekly or monthly debiting of outstanding fees. E.7 — Funds segregation Transaction payments (after AFI cost deduction not included in Paybyrd rates) are received into an AFI account. The AFI holds the Paybyrd-owed portion for Paybyrd and the remainder for the Merchant. The Merchant authorises Paybyrd to receive all transaction-related payments into AFI-held accounts. E.8 — Settlement criteria The minimum balance payment threshold is €5 unless agreed otherwise. If Paybyrd discovers a difference between payment and outstanding balance, Paybyrd may settle the difference or reclaim an incorrect payment. The Merchant may set the settlement frequency in the Dashboard. Paybyrd may change frequency or suspend Payment Services or Settlements, or cancel Transactions, in case of complaints, attachments or fraud investigations. Obligations during suspension remain fully in force. E.9 — Deductions and receivables All transaction payments (after AFI cost deduction) are received at the AFI, which may maintain a separate safeguarding entity. The AFI holds the Paybyrd-owed portion for Paybyrd and the remainder for the Merchant. E.10 — Reserves and settlement delays Paybyrd is entitled to establish and maintain a reserve to cover credit risk, chargebacks, disputes, delayed delivery, card-scheme fines, regulatory fines and other losses. Reserve amounts are determined at Paybyrd's sole discretion, adjusted for Merchant risk profile, sales volume, nature of products/services sold and any other factor Paybyrd deems relevant. Paybyrd may engage third-party risk-management services for reserve management. E.11 — Account maintenance fees and inactivity charges For in-person payment-method users, a €50 minimum monthly account-maintenance fee applies from 30 days after contract signature where the agreed monthly volume is not met. A €25 fee applies per inactive terminal unless a rental price is established. An inactive month is any calendar month during the agreement term in which the in-store terminal is not used for payment processing. The inactivity fee is the greater of €50 or 50% of the expected monthly revenue (preceding six months or shorter agreement period); for subsidised merchants it may reach 100% of expected monthly fees. The fee is due within 30 days of the end of the inactive month. Paybyrd may waive the inactivity fee at its sole discretion. Merchants wishing to terminate must provide notice and settle outstanding fees before closure. E.12 — Volume shortfall compensation If monthly processed volume is less than 75% of the contracted volume at onboarding (the point at which pricing is determined), Paybyrd is entitled to charge an amount equal to 50% of the revenue derivable from processing the Contracted Monthly Volume, less the revenue actually derived from Merchant volume. Revenue derivable = Contracted Monthly Volume × per-unit contract price. This is a genuine pre-estimate of loss (not a penalty), billed separately and payable within 7 days of invoice. The parties acknowledge this clause as a material term. It does not preclude other rights or remedies available to Paybyrd. E.13 — Setup fees Paybyrd may charge one-time setup fees for certain Merchant types or business activities. Setup fees are communicated in advance and paid upfront before account activation or processing. Amounts are determined by business nature, associated risk level and any other factor Paybyrd deems relevant. A breakdown and reasoning are provided. Setup fees are non-refundable and non-prorated for early account termination. E.14 — Set-off Paybyrd may, at its sole discretion and without notice, set off Merchant-owed amounts (present, future, actual, contingent, potential, liquidated or unliquidated) or amounts owed to Paybyrd affiliates against amounts Paybyrd owes the Merchant, Reserve Account amounts, or any Paybyrd/third-party intermediary Merchant property. This right is not limited by assignment to third parties, formal collection measures or bankruptcy proceedings unless legally precluded or expressly relinquished in writing. E.15 — Reverse merchant set-off The Merchant is not entitled to offset or deduct Paybyrd liabilities or obligations (under this Agreement or other agreements) from amounts owed to Paybyrd. 7. Chargebacks and refunds F.1 — Chargeback liability Scheme Owners — in particular credit-card issuers — allow Account Holders to request chargebacks per Scheme Rules, resulting in cancellation of transactions already paid or due to be paid to the Merchant. Receipt of Settlement or Authorisation does not unconditionally entitle the Merchant to receive or retain Settlement amounts; a Chargeback results in loss of entitlement and immediate return of funds to the Account Holder via Paybyrd. Paybyrd credits the Merchant's Bank Account on condition that no Chargeback occurs. If a Chargeback occurs, Paybyrd may debit the credited amounts. Scheme Owners and Paybyrd do not accept excessive Chargeback generation. The general standard is that more than 0.5% of authorised transaction volume is considered unacceptable; consequences include suspension of processing and Payment Method-specific fines (for which the Merchant is responsible). Some Payment Methods have higher or lower tolerances per Scheme Rules as published in the Customer Area. Non-immediate action by a Scheme Owner, Acquirer or Paybyrd does not constitute consent or waiver. The Merchant may not provide refunds to Account Holders using a different Payment Method than the original; original transactions may still be subject to Chargeback, creating double-refund liability. If Paybyrd suspects non-delivery, fraudulent basis, high chargeback likelihood or illegality, Paybyrd may suspend related Settlements and block related Authorisations pending satisfactory assurance. F.2 — Chargeback fees A non-refundable Chargeback Fee is charged per Chargeback per the Merchant Agreement. F.3 — Chargeback payment Paybyrd may deduct Chargeback amounts from Merchant Settlements or from the Deposit where the Settlement amount is insufficient. F.4 — Chargeback recovery Despite termination of the Merchant Agreement for any reason, Paybyrd is entitled to recover Chargebacks, Chargeback Fees and related fines for Transactions during the agreement term. F.5 — Refunds Paybyrd gives no guarantee and accepts no liability for automated or completed transactions subsequently reversed in any form by a customer or Financial Institution. Refund causes include (non-exhaustively) customer disputes, unauthorised or incorrectly authorised transactions, transactions not compliant with Scheme Rules or Agreement rules, allegedly unlawful or suspicious transactions, and other Card Network or Financial Institution reasons. The Merchant is fully responsible and liable for Refunds regardless of reason, timing or outcome. The Merchant is immediately liable to Paybyrd for the full Refund amount, costs and penalties. The Agreement authorises the AFI or Paybyrd to set off total Refund claims against Merchant claims on Paybyrd, or to debit the Merchant's known bank account. If Paybyrd cannot collect directly, the Merchant must pay the full amount immediately on request. If a Refund is suspected, the AFI may retain the possible Refund amount or withhold it from future balances until: the Refund is established from a customer complaint; the Merchant successfully disputes the Refund; the applicable legal dispute period expires; or non-occurrence is established. Merchants may dispute Refunds with Paybyrd notification; Paybyrd has no liability for its role in any dispute. The Merchant must provide complete and accurate information in time, at its own expense, and permits relevant information sharing with the Cardholder, card-issuing institution and Financial Institution. Incomplete or untimely information may result in an irreversible Refund. Determination of excessive Refunds may result in changes to guarantee conditions or amounts, cost increases, outpayment delays or suspension or termination of Payment Services. Financial Institutions and Intermediaries may implement additional checks or restrictions. F.6 — Refund charges Refunds are charged as Merchant Transactions. Refund fees apply where manual intervention is needed or additional Paybyrd costs are incurred (after prior notice). Paybyrd will not execute Refunds where funds cannot be subtracted from the next Settlement. Refunds are not funded by the AFI from the Deposit or from the AFI's own means. Merchants may request a separate Deposit for immediate Refund execution regardless of Settlement amounts. F.7 — No refund of fees Original transaction execution fees are not refunded, in whole or in part, upon Refund or Chargeback. G.1 — Hosted Payment Pages, iFrame, Card Collect Unless otherwise agreed, Services are used for Card Not Present Transactions via Hosted Payment Pages. The Merchant redirects the Account Holder to the Paybyrd-secured Hosted Payment Page for payment submission. Pages can be customised using standard skin options. The Merchant shall not capture, register or have the Account Holder fill Payment Details — expressly including credit-card data — on the Merchant site, but must use the Hosted Payment Pages. Screen-grabbing or emulation technologies for Hosted Payment Page input are prohibited. G.2 — API Payment Interface Where the Merchant has expressly agreed to use the API Payment Interface for CNP Transactions, the connection is via REST API over HTTPS, authenticated by username/password, IP, and/or client certificate. Merchants not activating 3D Secure for available Payment Methods understand that higher Card Scheme or Acquirer Interchange Fees and other restrictions may apply. PCI-DSS compliance. Merchants using the API interface must fully comply with current PCI-DSS rules, demonstrate compliance upon request, provide valid certification and notify Paybyrd immediately upon invalidation. Paybyrd may immediately suspend processing if there is any indication of non-compliance that the Merchant cannot immediately prove unfounded. The Merchant fully indemnifies Paybyrd against losses, claims (including Scheme Owner fines), costs and damage from breach of obligations. G.3 — Merchant equipment and POS terminals The Merchant is solely responsible for the equipment and software required to connect to the Payment Interface and submit transactions, including installation, servicing, maintenance, security and operation. Paybyrd provides standard software modules and installation guides; while professional input is ensured, the Merchant remains responsible for correct implementation per the Customer Area instructions. POS Transactions may only be submitted if expressly agreed in the Merchant Agreement, and only using Paybyrd-approved POS Terminals per current usage instructions. Where a Paybyrd POS Terminal is provided or recommended together with a third-party device (tablet, iPad, cash register, etc.), the Merchant must install current Paybyrd software and updates on that device. Paybyrd is not responsible for third-party device functioning; use is subject to the third-party provider's terms. Paybyrd may provide software building blocks (libraries) "as is" without warranty. G.4 — Merchant integration responsibility The Merchant is responsible for complying with Paybyrd-issued instructions and installation manuals, including updates issued via the Customer Interface. Paybyrd is not obligated to provide notification of Software or interface changes that do not impact the Merchant's use of the Services if the Merchant correctly followed integration instructions. G.5 — Defensive programming Paybyrd strongly recommends "defensive programming" where automated decisions default to non-delivery. For example, systems should deliver only on receipt of express payment authorisation, not in the absence of an explicit rejection. G.6 — Authorised payment status An "Authorised" status means likely transaction success, but 100% certainty is not given. A payment may still be blocked or subject to Chargeback where Scheme Rules permit. Success likelihood varies by Payment Method — for direct debits, "Authorised" typically indicates only that the Account Holder's bank account exists, not that sufficient funds are available. G.7 — Changes to API and Software Paybyrd may change or amend Software or interfaces at any time, provide new versions and change functionality, except where this would materially reduce functionality explicitly committed in the Merchant Agreement — unless required for industry-standard changes, law or Scheme Rule changes, security-risk-identified increases, or other reasonable grounds. Merchants significantly impacted by a material functionality reduction may terminate within one month of the change announcement by written notice. Paybyrd announces material API Interface changes at least six months in advance where reasonably possible; shorter notice may apply for legal, Acquirer/Scheme Owner or security reasons. G.8 — Security of Payment Details The Merchant guarantees that Payment Details (credit-card numbers, CVM codes, PIN codes) are not copied, captured or intercepted on Hosted Payment Pages or POS Terminals. If Paybyrd suspects copying, capturing or interception, Paybyrd may suspend processing and Settlement. The Merchant fully indemnifies Paybyrd against losses, claims (including Scheme Owner fines), costs and damage from breach of obligations. 9. Service Level Agreements H.1 — Customer support Regular support is available by email, web and telephone during Business Days and Working Hours. Emergency support is available 24 hours a day. Supported languages: English, Portuguese and Dutch. Support documentation is provided in English, alongside a knowledge base, news and troubleshooting helpers on our support website. H.2 — Uptime commitment — Payment Platform Paybyrd commits commercially reasonable efforts to maintain a minimum average 99.9% Payment Interface uptime, measured quarterly, for Transaction request receipt. The calculation excludes downtime caused by Merchant acts or omissions, Acquirer or Scheme Owner actions, Merchant-requested changes, general internet failures, individual Payment Method failures or force majeure. Merchants must immediately notify Paybyrd of any experienced Payment Interface downtime and cooperate reasonably in investigation and resolution. Planned maintenance is announced where practical and scheduled to minimise affected transactions; in emergencies (force majeure, terrorist attack) all available resources are used to minimise downtime. H.3 — Back-office maintenance The standard weekly maintenance window is Tuesdays 07:00–07:15 CET, or at other times determined by Paybyrd and communicated to the Merchant. The Customer Area may be temporarily unavailable during planned maintenance. Back-office maintenance only exceptionally affects Payment Interface transaction availability. 10. Security and confidentiality I.1 — Security and compliance Paybyrd provides reasonable secure payment-system measures and maintains PCI-DSS certified systems for service provision. I.2 — Security and fraud measures Paybyrd provides security procedures and fraud-reduction suggestions, including Paybyrd-developed or third-party processes and two-factor authentication (2FA) for Dashboard login. Merchants assess the appropriateness of procedures, select those that fit their activities and use additional non-Paybyrd procedures if necessary. Disabling or refusing security measures increases the chance of unauthorised transactions. The Merchant is responsible for use of lost or stolen cards to purchase goods or services on the Merchant website; Paybyrd is not responsible for, and does not indemnify the Merchant against, losses from lost or stolen card usage or from lost or stolen credit cards, usernames or passwords falling into the wrong hands. I.3 — Confidentiality Information relating to the Merchant or to Paybyrd that is designated as confidential, or that can reasonably be deemed confidential by its nature or content, is "Confidential Information" regardless of express designation. Each party retains ownership of data it provides. The Merchant acknowledges the Merchant Agreement terms and information about the Paybyrd Services (including support communications) as Confidential Information. Each party will take all necessary steps to protect Confidential Information: sharing only with personnel or representatives where necessary to exercise rights and obligations under the Agreement; and not disclosing to third parties without prior written consent (with an exception for Paybyrd for disclosures necessary to perform the Services). Confidentiality survives termination. Without special mention, the following are confidential: all financial data; Merchant Agreement-agreed specific terms and conditions; software user manuals, guides and Paybyrd product/service materials. I.4 — Privacy Paybyrd acts as a data processor under the Merchant's direction and responsibility in accordance with the EU General Data Protection Regulation (2016/679) and applicable Dutch privacy laws when personal data is processed for service provision. The Merchant complies with personal-data-protection laws of its country of origin and of countries where it offers products or services, particularly where personal data is processed in the context of the Services or submitted to Paybyrd. Paybyrd and the Merchant implement appropriate technical and organisational measures against personal-data misuse. I.5 — Protection of user data Merchant contracts or applicable customer terms must state that Paybyrd is used for transaction processing and that the Merchant shares personal data with Paybyrd in that context. Where applicable, the Merchant ensures that customers directly or indirectly provide Paybyrd with all explicit consent required under applicable privacy legislation. The Merchant guarantees GDPR compliance for personal data presented through the Payment Platform. Non-compliance, or a request from an Intermediary, Financial Institution, court or government body, authorises Paybyrd to suspend obligations. The Merchant is fully responsible for data security on its website, app and possessions, and for compliance with applicable national and international personal-data and payment-data collection, storage and dissemination laws. Where applicable, the Merchant complies with PCI-DSS and PA-DSS. An Account Data Compromise (ADC) caused by Merchant actions results in Merchant liability. Where Paybyrd or an Intermediary conducts an ADC investigation, the Merchant accepts the involved costs (only if Paybyrd previously shared an amount or cost indication). The Merchant uses only PCI-standard-compliant suppliers for Payment Data storage or transmission, particularly for PANs, card expiration dates and CVV2 codes. CVV2 storage is strictly prohibited in any form. Suspected data breaches involving payment data require Paybyrd notification without delay, no later than 48 hours after discovery; the Merchant will promptly provide any additional information requested. 11. Final stipulations J.1 — Intellectual property rights All Software, materials and intellectual-property rights related to Paybyrd services are owned by Paybyrd or its licensors. The Merchant Agreement grants the Merchant a limited, non-exclusive, non-transferable licence to use the Software and materials solely in conformity with the Agreement and applicable usage instructions. J.2 — Duration The Agreement enters into force at the moment of service signup. The initial term is 48 months. Thereafter the Agreement tacitly continues indefinitely with a 12-month notice period. J.3 — Liability Paybyrd is liable only for its own acts and omissions, not for third parties — expressly including Scheme Owners and Acquirers — or for events outside Paybyrd's system (e.g. internet disturbances, third-party system malfunctions), except where caused by Paybyrd's intent or gross negligence. Paybyrd's total annual liability towards the Merchant under the Agreement, whether in breach, tort or other legal theory, is capped at the total Processing Fees paid by the Merchant in the previous full calendar year (or, if there was no previous year of service, the fees payable under the initial 12-month term). Paybyrd is not liable for loss of profit, business, contracts, revenues or anticipated savings, or for damage to goodwill or reputation, or for any special, indirect or consequential damages. Nothing excludes or limits liability for intent, gross negligence, death, fraud or personal injury. J.4 — Indemnification and fines Where third-party claims assert that the parties own Paybyrd Software or system rights, Paybyrd will indemnify the Merchant without delay against such claims and reasonable legal defence costs, and will provide necessary legal-defence assistance. The Merchant indemnifies Paybyrd against third-party claims (expressly including Scheme Owner or Acquirer fine-payment claims) brought against Paybyrd as a result of Merchant violations of the Merchant Agreement, applicable law or Scheme Rules. J.5 — Termination Applicability. The Agreement applies to all legal acts between the parties and remains applicable after service termination regardless of express termination communication. Other conditions or agreements are explicitly rejected unless the parties expressly agreed otherwise in writing. Premature termination. Either party may prematurely terminate by registered letter with six months' notice. Immediate termination. Either party may terminate immediately by registered letter upon Merchant breach of the Merchant Agreement terms or conditions, or upon Merchant conduct harmful to Paybyrd's image or credibility. Mutual termination. Upon agreement of both parties. J.6 — Transfer Paybyrd may, at any time, assign, novate or transfer the Merchant Agreement to a Paybyrd group company (at least 50% shared shareholding) without prior Merchant consent, by written transfer notice. J.7 — Null provisions An invalid or inapplicable Agreement provision is deemed non-existent; all other provisions remain applicable. The parties will take steps to remove the invalid provision and replace it with one that approaches the economic objective of the original as closely as possible. J.8 — Entire agreement The Merchant Agreement contains all commitments of the parties and replaces all prior contractual commitments. No representation, warranty or undertaking has effect unless expressly written in the Agreement; all implied or prior representations, warranties or undertakings are excluded to the fullest extent allowed by law. J.9 — Use of name and marketing The Merchant agrees to inclusion of its name and standard logo (as published) on the Paybyrd client list and sales materials; Paybyrd may use this list freely in its commercial efforts. Any other use of the Merchant's name, logo or information requires prior written Merchant approval, which the Merchant may withhold. The Merchant may reference Paybyrd as its payment service provider in the "frequently asked questions" section of its website, explaining how Paybyrd appears on customer bank statements, and may include a link to the Paybyrd website in that context. The Merchant may not mention Paybyrd on its home page. The Merchant must clearly state that customers of Paybyrd-processed payments should not contact Paybyrd for support or questions. Use of the Paybyrd logo on the Merchant's website requires prior express written Paybyrd approval, which may be refused or withdrawn at Paybyrd's discretion. J.10 — Agreement and Terms and Conditions changes Paybyrd may revise the Terms and Conditions from time to time by giving at least 30 days' written notice to the Merchant via email or a notice in the Customer Area. If the change has a material adverse impact on the Merchant and the Merchant does not agree to the change, the Merchant may give written notice of its objection to Paybyrd within thirty days after receiving notice of the change. If Paybyrd receives such notice, Paybyrd will contact the Merchant to discuss the objections. If the Merchant continues to refuse to accept the change and Paybyrd refuses to withdraw the announced change, the Merchant may terminate the Merchant Agreement by giving at least one month's written notice to Paybyrd (such termination notice to be sent at the latest 60 days after the Merchant received notice of the change). The Merchant is not entitled to object and shall not have the rights set out in this clause for any change which Paybyrd implements in order to comply with applicable law or requirements imposed by the relevant Acquirers and/or Scheme Owners. For such imposed changes, shorter notice periods may be applied by Paybyrd as is needed to comply with the relevant requirement. J.11 — Deviating terms The applicability of the Merchant's purchasing or other general terms and conditions is expressly rejected. If the Merchant accepts a proposal made by Paybyrd (including a proposed Merchant Agreement) by issuing a separate written statement — for example a purchase order — which refers to the proposal and/or the Merchant Agreement, then additional or deviating terms or conditions contained in or referred to in such separate document shall not apply between the parties unless such deviating terms are explicitly accepted in a written statement issued and signed by a Paybyrd board member. In any case, the terms of the Merchant Agreement as proposed by Paybyrd, including the Paybyrd Terms and Conditions, shall take precedence over any terms and conditions contained or referred to in any such acceptance document from the Merchant. J.12 — Online contracting — written confirmation Where the Merchant has concluded the Merchant Agreement with Paybyrd via the Paybyrd website or any other online means, Paybyrd may at any time request that the Merchant re-confirm its acceptance of the terms of the Merchant Agreement (including these Paybyrd Terms and Conditions) by means of a written document signed by an authorised representative of the Merchant. If the Merchant does not comply with such request within 5 working days after receiving a request by Paybyrd to do so (which request may be issued to the Merchant via the contact email address submitted by the Merchant when concluding the Merchant Agreement), Paybyrd reserves the right to suspend part or all of the Services until the Merchant has complied. J.13 — Applicability of Payment Services Directive Title 7B of Book 7 of the Dutch Civil Code (Burgerlijk Wetboek) and other laws and regulations implementing Directive (EU) 2015/2366 ("PSD2") or its predecessor, Directive 2007/64/EC ("PSD"), are not applicable to the extent it is permitted to deviate from relevant provisions in relationships with non-consumers, in accordance with articles 38 and 61 PSD2 (or articles 30 and 41 PSD). Where Paybyrd provides payment services for the Merchant within the European Economic Area ("EEA") and where the Account Holder's payment service provider is located in the EEA, the parties hereby agree and confirm in accordance with article 62(2) of PSD2 that the Merchant shall pay the charges levied by Paybyrd and the Account Holder shall pay the charges levied by his payment service provider (i.e. the 'SHA' (shared) principle). J.14 — Third party clause The parties acknowledge that this Agreement also entails a third-party clause (as referred to in Book 6, Section 253 of the Dutch Civil Code) for and for the purposes of the AFI. Rights of parties under this Agreement will not require the approval of any third party. J.15 — Statement regarding financial institutions The following Financial Institutions act as processors, acquirers and/or account payment / BaaS providers: For POS and Ecom transactions processed under the brands MasterCard, Visa, China Union Pay and Diners: Bambora Group AB (a Worldline Company), with offices at Vasagatan 16, SE-111 20, Stockholm, Sweden, telephone +46 10 106 60 00; Worldline S.A. — Tour Voltaire, 1 Place des Degrés, CS 81162, 92059 Paris la Défense Cedex; Rapyd Europe HF — 33M4+3M2, Dalshraun, 220 Hafnarfjordur, Iceland; Transactions under the American Express brand processed by American Express Travel Related Services Company Inc. and/or American Express Payment Services Limited, Hoogoorddreef 15, 1101 BA, Amsterdam-Zuidoost, telephone +31 20 504 8504; PayPay — Estrada Regional 104 N.º 42-A, 9350-203 Ribeira Brava, Madeira, Portugal; PPRO Payment Services — 23 Hanover Square, London, W1S 1JB, United Kingdom; Elavon Financial Services — Level 15, CityPoint, One Ropemaker St, London EC2V 9AW, United Kingdom; Cielo S.A. — Alameda Xingu, 512 – 21º a 25º andar – Alphaville – SP – CEP: 06455-030, Brazil; MANGOPAY S.A. — Avenue Amélie, L-1125 Luxembourg, registered under Number B173459 on the Luxembourg Trade and Company Register and approved as an Electronic money institution by the CSSF, Commission de Surveillance du Secteur Financier, 283, route d'Arlon — L-1150 Luxembourg; CURO Payments B.V. — Obrechtstraat 21, 5344 AT Oss, The Netherlands, telephone +31 88 12 62 880; PagBrasil Electronic Payments LTDA — Municipality of Porto Alegre, State of Rio Grande do Sul, at Avenida Dr. Nilo Peçanha, no. 1,221, Conj. 902, Três Figueiras, CEP 91330-000. All Financial Institutions declare that: they are the party or parties concerned that possess licenses to process the aforementioned Transactions on your behalf; in that capacity, they form part of this Agreement; they are responsible for informing you of the rules with which you must comply on behalf of the aforementioned brands, but this information may be provided via Paybyrd; they are responsible for the ultimate payment of funds; they are responsible for all funds retained temporarily as a guarantee for possible Claims for Refund (see Article E.5 and Article F.5). J.16 — Other stipulations This Agreement supersedes all previous agreements between the parties, regardless of whether these agreements were made orally or set out in writing. Paybyrd reserves the right to amend this Agreement. Notification may be made in writing, by email or via the Paybyrd Dashboard. The amendments will enter into effect one (1) month after notification, unless stipulated otherwise. If the Merchant does not wish to agree to these amendments, it is entitled to terminate the Agreement with a notice period of one (1) month. This Agreement is governed exclusively by Dutch law and the parties must bring disputes before the court in Amsterdam. If the court declares articles of this Agreement invalid, the other articles will remain fully in force. Paybyrd has the right to outsource some of its services to third parties. Transfer by the Merchant of this Agreement or the rights and obligations contained in it is only possible with prior written permission from Paybyrd, which permission may be given under certain conditions, to be determined at such time. The Merchant hereby gives Paybyrd permission in advance, as referred to in Book 6, Section 159 of the Dutch Civil Code (BW), to transfer this Agreement at any time desired by Paybyrd to a third party to be indicated by Paybyrd. If and insofar as necessary or desirable, the Merchant further undertakes to confirm the aforementioned permission in writing. J.17 — Law and jurisdiction The Merchant Agreement and these Terms and Conditions are solely governed by Dutch law, excluding the Convention on Contracts for the International Sale of Goods. In the absence of an amicable agreement, any dispute relating to the validity, interpretation or fulfilment of the Merchant Agreement shall be submitted to the exclusive jurisdiction of the competent courts of Amsterdam, the Netherlands. J.18 — Code of conduct Paybyrd adheres to a comprehensive Code of Conduct, designed in accordance with the highest standards and best practices in the financial services industry. To review our full Code of Conduct, please review our Code of Conduct (PDF) . 12. Partnership contract K.1 — Formation of partnership contract By signing the Order Form provided by Paybyrd ("the Company"), the signatory party ("the Partner") hereby enters into a binding partnership contract with the Company for a term of twenty-four (24) months ("Contract Term"), subject to the terms and conditions outlined herein. K.2 — Basis of agreement and pricing The agreement and pricing structure are founded upon the information provided by the Partner during the onboarding process. The Partner agrees to supply accurate and complete information, acknowledging that any discrepancies or inaccuracies may affect the validity of the agreement and associated pricing. K.3 — Volume requirements and additional fees The Partner acknowledges that it is subject to volume requirements as specified in the agreement. Failure to meet these volume requirements may result in the Company imposing additional fees, the amount and nature of which will be detailed in the agreement. K.4 — Termination rights The Company reserves the right to terminate the partnership contract with a notice of sixty (60) days, should it deem necessary. Furthermore, if an invoice remains unpaid for a period of more than sixty (60) days, the Company may terminate the partnership contract with immediate effect. K.5 — Rights upon rescindment for breach In the event that the partnership contract is rescinded due to the Partner's bad behaviour, non-payment, or breach of any terms outlined in this agreement, the Company reserves the right to seek damages and compensation. The Partner will be liable for compensation equivalent to the total value of the contract for the full Contract Term, in addition to any other remedies available to the Company under applicable law. K.6 — Indemnification The Partner agrees to indemnify and hold harmless the Company, its affiliates, and their respective officers, directors, agents, and employees from any and all claims, liabilities, damages, and expenses (including reasonable attorneys' fees) arising out of or in connection with the Partner's breach of this agreement. K.7 — Governing law This agreement and any disputes or claims arising out of or in connection with it or its subject matter or formation (including non-contractual disputes or claims) are governed by and construed in accordance with the law of the Netherlands. K.8 — Amendments The Company reserves the right to amend these terms and conditions at any time. The Partner will be notified of any significant changes, and continued use of the Paybyrd platform constitutes acceptance of the amended terms and conditions. K.9 — Protection of business and revenue The Partner agrees not to engage in any activities or practices that would harm the reputation, business operations, or revenue of the Company. This includes, but is not limited to, any form of competitive actions, misuse of company resources, and dissemination of proprietary information. Breach of this clause will be grounds for immediate termination of the partnership contract and may result in legal action for damages. K.10 — Confidentiality Both the Company and the Partner agree to maintain the confidentiality of all information obtained during the execution of this agreement. Unauthorised disclosure of confidential information will be deemed a breach of this agreement and will entitle the non-breaching party to seek appropriate remedies under applicable law. By entering into this partnership contract, both the Company and the Partner agree to adhere to the aforementioned terms and conditions. Questions about these terms? --- ## Code of Conduct — https://www.paybyrd.com/code-of-conduct Summary: 12-section standard — integrity, anti-bribery, confidentiality, whistleblowing channels, sanctions screening 21 Apr 2026 Code of Conduct How we behave — toward merchants, their customers, each other, and every regulator, scheme and partner we touch. Binding on every Paybyrd employee, contractor, officer and board member. This translation is provided for convenience. The English version is the authoritative text. On this page ### sections 1. Purpose and scope Paybyrd is trusted with something simple and valuable — other people's money, as it moves. This Code describes the standards every Paybyrd employee, contractor, officer and director is expected to hold, whatever their role, wherever they work from. It is not a list of rules for their own sake. It reflects the behaviour we owe to the merchants who integrate with us, to the cardholders and shoppers whose data passes through our systems, to the regulators and scheme owners we answer to, and to each other. If anything in our day-to-day choices conflicts with this Code, this Code wins. This Code sits alongside Paybyrd's Merchant Terms & Conditions and Privacy Policy. Where a specific policy is more stringent — for example, PCI DSS requirements around cardholder data — the specific policy applies. 2. Our principles Five principles steer every decision we make: Merchant-first. Our product exists to make merchants' lives easier and their businesses stronger. If a decision helps Paybyrd at the merchant's expense, it's the wrong decision. Integrity in every transaction. We are honest in pricing, accurate in reporting, and clear about what we can and cannot do. We do not promise what we cannot deliver. Security by default. Cardholder and merchant data are treated as radioactive. Access is on a need-to-know basis; encryption and logging are always on. Transparent dealing. Fees, contracts, policies and system status are published, not hidden. Changes are announced, never sprung. Accountability. Mistakes get owned, documented, and fixed. Near-misses are shared, not buried. Every quarter, the leadership team reviews this Code in practice. 3. Regulatory and scheme compliance Paybyrd operates under the supervision of financial-services regulators across the markets we serve. Compliance is not a department — it is an operating constraint that shapes what we build and how we behave. Every Paybyrd employee and contractor is expected to understand, at a working level, the obligations relevant to their role, including: Payment Services Directive (PSD2) and its successor regimes — strong customer authentication, open banking interfaces, dispute timelines. PCI DSS Level 1 — the Payment Card Industry Data Security Standard, which governs how cardholder data is stored, processed and transmitted through our systems. GDPR (EU) 2016/679 and the Dutch Algemene verordening gegevensbescherming (AVG) — lawful bases for processing, data-subject rights, breach notification, cross-border transfer safeguards. Anti-Money Laundering and Counter-Terrorist Financing — the Wet ter voorkoming van witwassen en financieren van terrorisme (Wwft) and equivalent national regimes across the EU. Scheme rules published by Visa, Mastercard, American Express, Discover and other card networks, as updated from time to time. Sanctions regimes — OFAC (United States), the EU consolidated sanctions list, UK HMT, and UN Security Council resolutions. Where a Paybyrd employee becomes aware of any actual or suspected breach of these obligations, they must notify the Compliance team immediately via compliance@paybyrd.com . Failure to escalate is itself a breach of this Code. 4. Fair dealing with merchants and their customers Merchants choose Paybyrd because they believe we will treat them fairly. We honour that trust in five concrete ways: Pricing is honest. We publish our rates. We do not introduce hidden fees, surprise surcharges, or unexplained adjustments to settlement. Where rates change, merchants are notified in writing with at least 30 days' notice. Contracts are clear. Merchant Terms & Conditions are written to be read, not to hide behaviour. Material changes follow the notice procedure in the Terms. Disputes are resolved, not ignored. Chargebacks, technical incidents and billing disagreements are investigated in good faith and answered within the timelines published in our Service Level Agreement. Data is for service. Merchant data is used to provide the service, meet our legal obligations, and (with consent) improve the product. It is never sold. Customer-facing surfaces are respectful. Every checkout, payment link, terminal flow or chat message that Paybyrd touches carries the same standard of honesty and clarity we expect of ourselves. 5. Anti-bribery and anti-corruption Paybyrd has zero tolerance for bribery and corruption in any form, in any jurisdiction, regardless of whether local practice appears to tolerate it. Paybyrd employees and contractors must not, directly or through intermediaries: offer, promise, give, request, agree to receive or accept any financial or other advantage to induce or reward improper behaviour; make or accept facilitation payments — small unofficial payments to expedite routine government action — even where such payments are informally tolerated locally; make political contributions on behalf of Paybyrd without the prior written approval of the CEO and CFO. Gifts and hospitality. Reasonable business entertainment is part of normal commercial life. It becomes inappropriate when it is excessive, secret, or creates a sense of obligation. Any gift or hospitality with a value above €150 per person per year (aggregate, per counterparty) must be declared to the Compliance team before acceptance or offer. Paybyrd reports bribery and corruption concerns via the channels described in section 10 (Speaking up). Retaliation against a good-faith report is itself a breach of this Code. 6. Conflicts of interest A conflict of interest is any situation in which a private interest could compromise, or appear to compromise, the judgement we owe to Paybyrd or its merchants. We manage conflicts by disclosing them early and recusing from decisions where necessary. Paybyrd employees and contractors must disclose, in writing to their manager and to the People team: any ownership, board role or paid advisory role in a competitor, merchant, partner, vendor, scheme owner or acquirer; close family or personal relationships with anyone working for any of the above; outside paid work that overlaps with Paybyrd's business, or consumes time that would materially affect Paybyrd responsibilities; any personal financial interest — direct or indirect — in a transaction Paybyrd is considering entering. Disclosed conflicts are managed, not automatically prohibited. What is never acceptable is a concealed conflict. 7. Confidentiality, data protection and information security Confidential information — merchant commercial data, pricing, pipelines, product roadmaps, customer PAN/CHD, authentication secrets — is handled only on a need-to-know basis, only within authorised systems, and only for the purposes for which it was collected. Specific obligations every Paybyrd employee must meet: Never store, transmit or process Primary Account Number (PAN) data outside the PCI DSS-scoped environment. When in doubt, ask Security Engineering before touching the data. Encrypt data at rest and in transit. Disable TLS 1.1 and below. Rotate secrets and access keys on the published cadence. Use Paybyrd-issued devices for Paybyrd work. Do not email confidential data to personal accounts or copy it to unapproved cloud drives. Report any suspected security incident — phishing attempt, lost device, unexpected system behaviour, vendor breach notice — to the Security team within one hour of becoming aware. Do not investigate on your own. Respect data-subject rights under GDPR/AVG. Requests for access, rectification, erasure and portability are routed to the Data Protection Officer at dpo@paybyrd.com . Access to production systems is logged. Logs are reviewed. Unusual access is investigated. 8. Market integrity and fair competition Paybyrd competes on the merits — price, reliability, security, service, speed of integration — and nothing else. No anti-competitive agreements. We do not agree, tacitly or otherwise, with competitors on pricing, customer allocation, market division, or bid rigging. No abuse of dominance. Where Paybyrd is strong in a particular corridor or vertical, that strength is not used to foreclose merchants or partners from choosing alternatives. Respect for intellectual property. Paybyrd builds on open-source and licensed code responsibly, honouring licence obligations. We do not misappropriate competitor trade secrets, technical documentation or merchant lists. Truthful marketing. Public claims about performance, savings, or uptime are based on verifiable data. Comparative claims about competitors are fact-checked before publication and reviewed on request. No market manipulation. Employees with access to non-public information about Paybyrd, its investors, or its merchants do not trade on that information, tip others, or discuss it outside the minimum circle required. 9. Workplace conduct Paybyrd expects every person to be treated with respect, regardless of role, seniority, background, identity or belief. Harassment, bullying and discrimination have no place in our offices, our remote workplaces, our customer meetings, our events or our digital channels. Non-discrimination. Decisions about hiring, compensation, promotion and assignment are based on skill, contribution and fit — never on race, colour, ethnic or national origin, sex, gender identity or expression, sexual orientation, religion, age, disability, marital or family status, or any other protected characteristic. No harassment. Harassment includes unwelcome conduct of a sexual nature, verbal or physical, as well as any hostile or intimidating behaviour that creates an abusive environment. It does not become acceptable because the context is a social or after-work setting. Health and safety. Physical workspaces and remote work arrangements are designed to be safe. Safety concerns are raised immediately; they are not a low-priority backlog item. Substance use. Employees do not report for work — including work on video calls — while impaired by alcohol or drugs in a way that affects judgement or safety. Social and customer-facing conduct. Behaviour at Paybyrd offsites, industry events, and customer dinners is held to the same standard as behaviour in the office. 10. Speaking up — whistleblowing and reporting concerns A Code is only as strong as the willingness of the people under it to speak up when it is broken. Paybyrd protects and encourages good-faith reporting. Where to report. Concerns about actual or suspected breaches of this Code, of law, or of internal policy can be raised through any of the following channels, in increasing order of independence: your direct manager or skip-level; the People team at people@paybyrd.com ; the Compliance team at compliance@paybyrd.com ; the Data Protection Officer at dpo@paybyrd.com for data-related concerns; the confidential whistleblowing inbox speakup@paybyrd.com , which is read only by the Audit Committee and the DPO. Non-retaliation. Paybyrd will not tolerate retaliation — firing, demotion, exclusion, threat or any other adverse action — against anyone who raises a concern in good faith, takes part in an investigation, or refuses to participate in suspected wrongdoing. Retaliation is itself a disciplinary offence. Anonymity. Reports can be made anonymously. Anonymous reports are investigated with the same seriousness as named ones, subject to the practical limits of acting on information that cannot be verified with the reporter. External rights preserved. Nothing in this Code prevents a Paybyrd employee from reporting suspected unlawful conduct to a regulator, law-enforcement authority or the Dutch Huis voor Klokkenluiders (Whistleblowers' Authority). 11. Sanctions, third parties and outsourcing Paybyrd does not do business with sanctioned persons, entities or jurisdictions, and the people, products and merchants we connect to our network are screened on that basis. Screening. Every merchant, principal and counterparty is screened against the OFAC, EU consolidated, UK HMT and UN sanctions lists at onboarding and on an ongoing basis. Hits are escalated to the Compliance team and cleared or rejected before service continues. Prohibited jurisdictions. Paybyrd does not knowingly facilitate payments into or out of jurisdictions subject to comprehensive sanctions (Cuba, Iran, North Korea, Syria, and the non-government-controlled regions of Crimea, Donetsk, Kherson, Luhansk and Zaporizhzhia), and restricts activity in partially-sanctioned jurisdictions in line with the applicable regime. Vendor standards. Every vendor or partner with access to Paybyrd systems, merchant data or cardholder data is subject to due diligence, a written agreement including data-protection and security terms, and a review cadence proportionate to their risk profile. Vendors of material services are named in Paybyrd's Terms & Conditions. Outsourcing oversight. Where Paybyrd outsources any service, accountability for the outcome remains with Paybyrd. Outsourced work is monitored on the same standards Paybyrd holds itself to. 12. Accountability, review and contact This Code is overseen by the Paybyrd Compliance team, with sponsorship at board level. The CEO and Chief Compliance Officer are jointly responsible for ensuring it is applied in practice. Training. Every Paybyrd employee completes initial Code-of-Conduct training during onboarding and annual refresher training thereafter. Role-specific training (PCI DSS, AML/CFT, sanctions) is additional to — not a substitute for — this baseline. Consequences of breach. Breaches of this Code are addressed through Paybyrd's disciplinary process, which is proportionate to the seriousness and context of the breach. Consequences range from remediation plans to termination of employment or engagement. Certain breaches — including bribery, data theft, serious harassment and sanctions-list violations — are grounds for immediate termination and may be reported to law-enforcement or regulatory authorities. Annual review. This Code is reviewed at least once per year by the Compliance team, and updated as regulation, scheme rules and our own business evolve. Material updates are communicated to all employees and published on paybyrd.com/code-of-conduct . Questions. Any employee, merchant, partner or member of the public who has a question about this Code, a concern to raise, or a situation they are unsure about can write to compliance@paybyrd.com . The Compliance team commits to a substantive response within five working days. Questions, concerns, or want to speak up? --- ## Paybyrd Engage — loyalty, promotions & referrals — https://www.paybyrd.com/engage Summary: loyalty, promotions and partner referrals decided against the verified transaction — merchant-funded campaigns with hard budget ceilings, partner-commissioned referral codes with tracked SEPA payouts, and voucher entry embedded in the hosted checkout Loyalty · Promotions · Referrals — native to payments Turn every payment into Engage builds loyalty, promotions and partner referrals directly into the Paybyrd rails you already run on. No new vendor. No new integration. No development work. Runs on existing integrations Hard budget ceilings Live in minutes Loyalty · every 10th visit card •••• 4582 — reward unlocked Voucher · TAPSUMMER25 validated against payment · partner 8% €20,000 ceiling · auto-stop Paybyrd Engage is a loyalty, promotions and partner-referral layer that decides every reward against the verified payment, with hard budget ceilings and automated partner payouts, on the payment rails a merchant already runs. Card-linked loyalty and promotions, inside the payment. Turn every payment into repeat revenue. Loyalty tools sit the payment. Engage sits Every reward is decided against the real transaction — its amount, market, method and card brand. Earned on verified payments, never on clicks or claims. ### cards Verified, not self-reported Offers qualify on the real transaction — precise and fraud-resistant by construction. Decided at checkout The payment asks which offers apply and gets an instant answer — every time. Settled without work Redemption, ledger entries and partner payouts happen automatically — no manual reconciliation. Two instruments, one platform Campaigns fund discounts. Vouchers fund growth. Campaigns · merchant-funded Automatic discounts with a hard budget ceiling. Percentage or fixed-amount, targeted by market, method, card brand and spend. The campaign stops itself the moment the budget is reached. 10% off card payments over €50 in Portugal — capped at a €20,000 budget. The Engage campaign rule builder, showing discount type, targeting conditions and the budget ceiling Vouchers · partner-commissioned Referral codes that pay a tracked commission. Unique codes tied to an influencer or affiliate — customer discount on one side, partner commission on the other, with redemption limits you set. SUMMER25 — 25% off for the customer, 8% to the partner, 1,000 redemptions max. The Engage referral code screen, showing the customer discount, the partner commission and the redemption cap One form, zero extra systems The code lives the payment form. Voucher and discount entry is embedded directly in your hosted checkout. No coupon engine, no affiliate platform, no reconciliation layer — the systems you'd normally stitch together simply disappear. Runs on your existing integration — zero development work Fully white-labeled — themed to match your brand, like TAP below Every redemption validated against a real payment Live demo — hosted form The Paybyrd hosted payment form themed for TAP Air Portugal, with the Engage voucher field in the checkout What you can run ### cards Loyalty at the terminal The card is the program. No app, no sign-up. Declarative rules — every Nth visit, every €X spent — evaluated per card, live within seconds. Mint a code. Set the economics. Customer credit on one side, tracked partner commission on the other. Attribution and monthly payouts handled automatically. Budgets that can't overrun. Hard ceilings, an auditable ledger, atomic redemption. A campaign stops itself at its budget — no overspend, ever. The Engage partner onboarding form, capturing the commission rate, banking details and the code a new partner will share Granular by default Your payment data is already here. So is the targeting. Because every payment already flows through Paybyrd, Engage inherits the full picture and acts on any slice of it. Marketing teams launch offers immediately — no data pipeline, no engineering ticket. Run an offer in one market only, without touching the rest. Target frequent flyers, first-time bookers, or lapsed travelers. Scope to route, cabin class, fare type, or minimum spend. Ad-hoc campaigns — capped, measured, stopped on demand. Engage vs traditional loyalty Six differences that Clicks, sign-ups, self-reported activity Verified payment transactions Batch, after the fact Real time, at checkout Automatic ceiling, auto-stop Separate affiliate tool + manual reconciliation Built-in ledger + automated SEPA settlement Native to the payment flow Fragmented across tools What merchants typically among reward-program participants · redemptions per customer per period from relevant offers at the moment of payment · offer-to-payment rate ceilings enforced automatically · utilization vs. ceiling, never exceeded Growth figures are industry-typical ranges — merchant targets, not guaranteed outcomes. The questions merchants ask before a pilot. ### items Who funds the discount? Campaigns are merchant-funded: you set the discount and a hard budget ceiling, and the campaign stops itself when the ceiling is reached. Vouchers are partner-commissioned: the customer discount and the partner's commission are set per code. Does Engage need a new integration? No. It runs on the Paybyrd integration you already have. Voucher and discount entry is embedded in the hosted checkout, and loyalty rules run at the terminal, so there is no coupon engine or affiliate platform to connect. Can a partner referral be paid out automatically? Yes. Every redemption is validated against a real payment, the commission is written to an auditable ledger, and partners receive a SEPA statement and payout every month without manual reconciliation. Is there a budget cap per campaign? Every campaign has a hard ceiling. Redemption is atomic, so a campaign cannot overspend, and a customer cannot redeem the same offer twice. How fast is a change live? A loyalty rule or campaign edited in the dashboard is live within seconds, and the first pilot is scoped to one program with one ceiling so results can be read at the transaction level. --- ## Instant payouts for POS merchants — https://www.paybyrd.com/instant-payouts Summary: on-demand settlement for eligible POS merchants in hospitality, travel and similar sectors: tap Pay out now and today's takings are sent to the business bank account by instant transfer at any hour, from €1 per payout (sector rates via sales); the free daily settlement stays included; roles and daily caps, the fee shown before confirming, one ledger for instant payouts, daily batches, refunds and fees New · Instant payouts for POS merchants Instant payouts for POS merchants Your takings. Your bank. Right now. Settle on demand, any hour of the day. Paybyrd Instant Payouts is on-demand settlement for eligible POS merchants: instead of waiting for the daily batch, you tap Pay out now and today's card takings are sent to your business bank account by instant transfer. Daily settlement is included and always will be. But when you need the money today — a supplier invoice, a Saturday payroll, a deposit to refund — tap once and today's takings land in your account in seconds. From €1 per payout. Hospitality, travel & similar sectors Daily settlement stays free ### items Friday's takings shouldn't wait for Monday. Standard settlement batches at midnight and pays on the next business day. Sell on a Friday night and the money sits until Monday — three days your suppliers, your staff and your guests don't care about. Included · next business day Arrives Mon 09:00 ~58 hours waiting On demand · from €1 Arrives Fri 23:12 · seconds later Illustrative timeline. The daily batch closes at midnight and pays on the next business day, so a Friday-night sale is paid on Monday. Times and amounts are examples, not a live account. No forms, no calls. ### steps Sell as usual Every approved POS transaction lands in your Paybyrd balance as it happens. Nothing to switch, nothing to configure. Tap Pay out now Choose the full balance or just what you need. The fee is on screen before you confirm — never a surprise on the statement. Money arrives in seconds Straight into your business bank account by instant transfer, with the payout on your Paybyrd ledger and your bank statement. Built for businesses that Big tickets, deposits, seasonal peaks, and suppliers who want paying now. Instant payouts are offered to Paybyrd POS merchants in hospitality, travel and similar sectors — with rates set for your business by the sales team. A guest tapping a card on a Paybyrd terminal at a front desk Hotels & resorts Friday's check-ins pay Saturday's suppliers. Deposits refunded on the spot. Travel & tour operators Pay the airline or hotel the same day the customer books — no float, no bridge loan. Car rental & mobility Deposits back to the driver and fleet costs covered, the same afternoon. Events & venues Pay crew and vendors the night of the show, not three days later. Similar sector, not on the list? Eligibility is decided case by case. On demand doesn't mean out of control. ### cards Roles & caps Decide who can trigger a payout and set a daily limit per role. Fee before you confirm The cost is on screen every time. Nothing appears on the statement you didn't approve. Instant payouts, daily batches, refunds and fees on the same statement. Reconciliation stays boring. Daily settlement untouched Whatever you don't pay out arrives with tomorrow's batch, at no cost, exactly as today. per instant payout Pay only when you use it. Your regular daily settlement stays included, and hospitality and travel merchants get sector rates agreed with the sales team. From €1.00 each You're a fit if: You take payments on Paybyrd POS terminals You operate in hospitality, travel or a similar sector Your business bank account accepts instant transfers Already on Paybyrd POS? Ask your account manager to switch it on. Not on Paybyrd POS yet? See the terminals Questions merchants ask before switching it on. ### items Does this replace my daily settlement? No. Daily settlement stays included at no cost. Instant payouts sit on top: use them when you need money today, and let everything else arrive with the next batch as usual. Can I pay out part of the balance? Yes. Choose the full available balance or enter the amount you need. The rest carries on to your daily batch. How fast is "instant"? Typically seconds. The payout is sent as an instant bank transfer, so your account has to accept instant transfers. Since 9 January 2025, banks in the euro area must be able to receive instant euro transfers under the EU Instant Payments Regulation, so nearly every business account already does; it is one of the three eligibility checks either way. What does it cost? From €1 per instant payout, shown on screen before you confirm. Merchants in hospitality, travel and similar sectors get rates agreed with the sales team. Who can use it? Paybyrd POS merchants in hospitality, travel and similar sectors. If your sector is close but not listed, ask sales; eligibility is decided case by case. Does it work at night and on weekends? Yes. You can trigger a payout at any hour, on any day. That is the point: a Friday night should not wait for Monday morning. --- ## Pay by bank with virtual IBANs — https://www.paybyrd.com/pay-by-bank Summary: bank transfer as a payment method with a unique virtual IBAN generated per customer, invoice or order; SEPA Instant fully supported and standard SEPA accepted; the IBAN is the reference so the transfer is reconciled on arrival and a payment.received webhook fires exactly like a card payment; API-generated so the IBAN can be printed on invoices or pushed into any CRM/ERP; a low flat fee per transfer (rate via sales) rather than a percentage, IBAN creation, reconciliation and webhooks included New · Pay by bank with virtual IBANs Pay by bank with virtual IBANs Bank transfers that behave like card payments. Unique virtual IBANs. Instant reconciliation. One webhook. Paybyrd Pay by bank gives every customer, invoice or order its own virtual IBAN. When the transfer lands, in seconds over SEPA Instant or on the usual timeline over standard SEPA, it is matched automatically and a payment.received webhook fires exactly like a card payment. Give every customer, invoice, or order its own IBAN. When the transfer lands, it matches itself, and your systems hear about it exactly the way they hear about a card payment. At a flat fee per transfer, not a percentage. Any CRM or ERP via API Same webhooks as cards ### items The reference field is where reconciliation goes to die. One shared IBAN, a free-text reference, and a customer who types whatever they like. Finance spends the afternoon matching. Nobody knows an invoice is paid until someone looks. A virtual IBAN removes the guesswork: the account itself says who paid. ref: "INV 0418 thanks!!" ref: "viagens atlantico apr" 3 transfers · 0 auto-matched finance: the whole afternoon …0418 7 → INV-2026-0418 …0421 3 → INV-2026-0421 …0422 9 → INV-2026-0422 3 transfers · 3 auto-matched · 3 webhooks sent finance: 0 minutes Manual · 2 days Illustrative statement. Amounts, references and timings are examples, not a live account. ### steps Generate a virtual IBAN One API call creates an IBAN for a customer, an invoice, or an order. Thousands, if you need them. Put it where the customer pays Print it on the invoice from your ERP, show "Pay by bank" in your checkout, or push it into your CRM. Any reference text works, or none. Matched and notified in seconds The transfer arrives over SEPA Instant, matches the invoice automatically, and payment.received hits your webhook, identical to a card. Built for invoices, big tickets, Anywhere card fees sting and a bank transfer already makes sense. Now without the reconciliation tax. ### cards Every invoice leaves your ERP with its own IBAN. Paid means paid, the moment the money lands. Offer "Pay by bank" next to cards on €2,000 baskets, travel, furniture, tuition, and keep the margin. Group & corporate bookings Deposits and balances for hotels and travel agencies, matched to the booking without a single email. Finance & AR teams Close the day, every day. One ledger for cards and bank, no unallocated cash to explain. Anything, via REST API + webhooks Same API. Same webhooks. If you already take cards with Paybyrd, you already have the integration. Virtual IBANs are a resource, not a project. Create and list IBANs per customer, invoice, or order. payment.received with the matched reference, amount, and rail. SEPA Instant first Seconds when the payer's bank supports it; standard SEPA transfers land too. Test your webhook in the sandbox before go-live. Field names are illustrative; the reference docs are the contract. Read the API docs A small fee per bank payment rather than a percentage of the basket: the bigger the ticket, the more you keep. Your rate is agreed with the sales team alongside your card pricing. Low fee per transfer — "Pay by bank" alongside your card and wallet methods. — generated per invoice or per customer and printed from your ERP. CRM & ERP integrations — via the REST API and webhooks, in the SEPA area. Already integrated? Ask your account manager to enable virtual IBANs. Questions finance and developers ask before switching it on. ### items Is it SEPA Instant? Yes. Our accounts fully support SEPA Instant, so transfers from banks on the instant scheme arrive in seconds. Standard SEPA credit transfers to the same IBAN land too, on the usual timeline. How does reconciliation work without a reference? Each virtual IBAN belongs to exactly one invoice, order, or customer. Whatever the payer types in the reference field, the money arriving on that IBAN is the match. No rules engine, no manual allocation. One IBAN per invoice or per customer? Either. Per invoice gives you exact matching; per customer gives repeat payers one number to save. Mix both if it suits your flow. Do I need a new integration? No. Virtual IBANs are created through the same REST API you already use, and payments arrive on the same webhook endpoint as your card events. Cards and bank share one ledger. What does it cost? A low per-transfer fee rather than a percentage, agreed with the sales team alongside your card pricing. Creating IBANs, reconciliation, and webhooks are included. What if the customer pays the wrong amount? The payment is still matched to its invoice or customer, and the event carries the amount received, so your system decides what happens with a partial or over-payment, exactly as with a card. --- ## What are card scheme fees? — https://www.paybyrd.com/learn/card-scheme-fees Summary: explainer: what card scheme fees are, how they differ from the regulated interchange, what drives them (authentication, issuing region, card type), how they appear on a blended versus interchange++ statement, a worked €50 example against Paybyrd's published rate, and the Jan/Jul/Oct revision cycle What are card scheme fees? Card scheme fees are the per-transaction charges Visa and Mastercard levy on acquirers for using their networks. They are separate from interchange, which goes to the card-issuing bank and is capped in the EEA under Regulation (EU) 2015/751; scheme fees are not capped, which is why a merchant should be able to see them. Updated September 2026 · schedule effective 1 July 2026, next revision expected October 2026 ### sections How scheme fees differ from interchange Three parties take a cut of a card payment. Interchange is paid by the acquirer to the issuing bank and, for consumer cards in the EEA, is capped at 0.2% (debit) and 0.3% (credit), with some national variations. Scheme fees are paid by the acquirer to Visa or Mastercard for the network itself and are set by the schemes, not by regulation. The acquirer or payment provider adds its own margin on top. A blended rate hides all three inside one number; interchange++ shows each. What drives a scheme fee up or down Authentication is the largest lever: a transaction authenticated with 3-D Secure or paid with a network token carries a lower scheme fee than one that is neither. Where the card was issued matters next — a card issued outside the EEA costs more to accept than a domestic one, and an interregional card more still. Card type (consumer, commercial, debit, credit) and whether the transaction is card-present complete the picture. How they appear on a merchant statement On a blended contract the scheme fee never appears: it is inside the single percentage you pay. On an interchange++ contract it appears as its own line, per transaction, next to interchange and the provider's margin. Paybyrd publishes the schedule it passes through either way, so a merchant on a blended rate can still see what part of that rate is the networks'. A worked example On a €50 online payment with an EEA-issued consumer Visa card, authenticated with 3-D Secure: the regulated interchange at 0.2% is €0.10 and the scheme fee at 0.113% + €0.035 is about €0.09 — roughly €0.19 that goes to the issuer and the network. Paybyrd's published online rate of 1.25% + €0.08 is €0.71 on that payment and already includes both; the same card without authentication would carry about €0.13 in scheme fees instead. Why the numbers change Visa and Mastercard revise their price lists on January, July and October cycles. Paybyrd re-extracts its schedule from the source rate card on each revision, states the effective date and the next expected revision on the page, and keeps the previous PDF available so a merchant can see what changed. The three components of a card transaction cost in the EEA Paid by → to Typical EEA range acquirer → card-issuing bank percentage of the transaction, capped by Regulation (EU) 2015/751 for consumer cards 0.2% debit · 0.3% credit acquirer → Visa / Mastercard percentage plus a fixed amount; varies with authentication, issuing region and card type ≈0.11–0.13% + €0.035–0.045 authenticated consumer cards; ≈0.19–0.20% + €0.03–0.06 non-authenticated merchant → acquirer / payment provider set by contract; the only component a merchant negotiates Paybyrd: inside 1.25% + €0.08 online, 0.50% in store the schedule gets asked. ### items Are card scheme fees regulated? No. The Interchange Fee Regulation caps interchange for consumer cards; scheme fees are set by Visa and Mastercard and are not capped. That is why Paybyrd publishes the schedule it passes through. Can a merchant negotiate scheme fees? No — they are set by the networks and charged to every acquirer. What a merchant can change is the share of transactions that are authenticated and tokenised, which is the largest driver of the fee, and the provider margin on top. What is the difference between interchange and scheme fees? Interchange goes to the bank that issued the card and is regulated in the EEA; scheme fees go to the card network for running it and are not. Both are charged to the acquirer and passed on to the merchant, blended or itemised depending on the contract. Who pays scheme fees? The acquirer pays them to the scheme and recovers them from the merchant. On a blended rate they are invisible inside the percentage; on interchange++ they are itemised; on Paybyrd they are published either way. Where can I see the actual numbers? On the scheme-fee schedule: bundled all-in rates per region and the itemised price-list charges beneath them, as a page, a PDF, a JSON file and a CSV. --- ## Customer stories — https://www.paybyrd.com/customers Summary: index of nine customer stories — TAP Air Portugal, Wink, Vila Galé, KuantoKusta, Kabuki, Rede Expressos, André Óticas, Onyria Resorts, SkinBoutique by LMR — each told in the customer's words with the outcome they report The merchants running on Paybyrd, in their own words. Every story here is told by the customer. The outcomes are theirs; the footage was shot on location. Read the story --- ## TAP Air Portugal — customer story — https://www.paybyrd.com/customers/tap-air-portugal Summary: how TAP Air Portugal runs payments on Paybyrd, told by the customer; linked to /airlines TAP Air Portugal: Millions unlocked in new revenue Global and local transaction processing with higher approval rates and lower fraud — typically recovering millions in payment volume across 90+ markets. What TAP Air Portugal runs on Paybyrd: See how Paybyrd works for this industry — airline payments (/airlines). In their words: “Paybyrd tuned approval rates across every market we fly to. We stopped leaving money on the runway.” — João Frias, Head of Payments, TAP Air Portugal. Millions unlocked in new payment volume — across 90+ markets. TAP Air Portugal: +€3.8M recovered revenue --- ## Wink — customer story — https://www.paybyrd.com/customers/wink Summary: how Wink runs payments on Paybyrd, told by the customer; linked to /retail Wink: Real-time visibility across all stores Leveraging real-time data across own stores and franchise network to boost loyalty, identify recurring shoppers, and increase basket size. What Wink runs on Paybyrd: See how Paybyrd works for this industry — retail payments (/retail). In their words: “We went from guessing what sold to knowing exactly who bought it and when they'll come back.” — Filipa Muñoz de Oliveira, CEO, Wiñk. Real-time visibility across every store and every franchise. --- ## Vila Galé — customer story — https://www.paybyrd.com/customers/vila-gale Summary: how Vila Galé runs payments on Paybyrd, told by the customer; linked to /hospitality Vila Galé: Omnichannel across 40+ hotels Seamless payment orchestration across one of the largest hotel groups in Portugal and Brazil — from front desk to spa to room service. What Vila Galé runs on Paybyrd: See how Paybyrd works for this industry — hotel payments (/hospitality). In their words: “Every revenue center is connected. Finance closes the day in hours, not Mondays.” — Carlos Rodrigues, CFO, Vila Galé. Omnichannel payments across 40+ hotels — front desk to spa to room service. Vila Galé: One platform · 40+ properties --- ## KuantoKusta — customer story — https://www.paybyrd.com/customers/kuantokusta Summary: how KuantoKusta runs payments on Paybyrd, told by the customer; linked to /e-commerce KuantoKusta: Higher checkout conversion with BNPL High-performance checkout with multi-payment strategy including BNPL and local methods — reducing cart abandonment and increasing order value. What KuantoKusta runs on Paybyrd: See how Paybyrd works for this industry — e-commerce payments (/e-commerce). In their words: “The multi-method checkout is a revenue lever. Every cart abandoned is a test we now win.” — Rita Faria, CEO, KuantoKusta. Higher checkout conversion with BNPL and local methods that customers actually want. KuantoKusta: +18% checkout conversion --- ## Kabuki — customer story — https://www.paybyrd.com/customers/kabuki Summary: how Kabuki runs payments on Paybyrd, told by the customer; linked to /restaurants Kabuki: Bespoke POS with loyalty insights Tailored terminal experience with branded checkout flows and full customer loyalty visibility — turning every transaction into a relationship. What Kabuki runs on Paybyrd: See how Paybyrd works for this industry — restaurant payments (/restaurants). In their words: “Tableside payments are one tap. And we finally know who our regulars are without asking.” — Victor Jardim, General Manager, Kabuki. Bespoke POS with full loyalty visibility — every bill becomes a relationship. --- ## Rede Expressos — customer story — https://www.paybyrd.com/customers/rede-expressos Summary: how Rede Expressos runs payments on Paybyrd, told by the customer; linked to /transport Rede Expressos: Seamless ticketing across 700+ routes Powering frictionless payments for Portugal's largest intercity bus network — online, at the counter, and on the go. Every seat sold faster. What Rede Expressos runs on Paybyrd: See how Paybyrd works for this industry — transport payments (/transport). In their words: “Selling a ticket used to take 40 seconds. Now it takes 8. Lines disappeared.” — Nelson Silva, General Manager, Rede Expressos. Frictionless ticketing across 700+ routes — online, at the counter, on the go. --- ## André Óticas — customer story — https://www.paybyrd.com/customers/andre-oticas Summary: how André Óticas runs payments on Paybyrd, told by the customer; linked to /retail André Óticas: Premium checkout for premium eyewear Elevating the in-store payment experience for high-end optical retail — with tailored POS flows that match the care behind every pair. What André Óticas runs on Paybyrd: See how Paybyrd works for this industry — retail payments (/retail). In their words: “The terminal feels like our store. Staff never fight it — they forget it's there.” — Dr. Plínio Leal, CEO, André Óticas. Premium POS flows to match the craftsmanship behind every frame. André Óticas: Checkout in 12 seconds --- ## Onyria Resorts — customer story — https://www.paybyrd.com/customers/onyria-resorts Summary: how Onyria Resorts runs payments on Paybyrd, told by the customer; linked to /hospitality Onyria Resorts: Unified payments across resort properties From golf clubhouse to spa to fine dining — seamless omnichannel payments across one of Portugal's most prestigious resort groups. What Onyria Resorts runs on Paybyrd: See how Paybyrd works for this industry — hospitality payments (/hospitality). In their words: “One platform across every touchpoint. Our guests feel it without knowing why.” — Paulo Figueiredo, COO, Onyria Resorts. Unified payments from clubhouse to spa — across every resort property. --- ## SkinBoutique by LMR — customer story — https://www.paybyrd.com/customers/skinboutique-by-lmr Summary: how SkinBoutique by LMR runs payments on Paybyrd, told by the customer; linked to /pos SkinBoutique by LMR: Effortless payments for premium care Streamlined checkout for high-value treatments — installments, recurring billing, and a payment experience as refined as the clinic itself. What SkinBoutique by LMR runs on Paybyrd: See how Paybyrd works for this industry — POS payments (/pos). --- ## Knowledge Hub — https://www.paybyrd.com/knowledge-hub Summary: index of everything Paybyrd publishes, grouped by intent: evaluating, switching, building and running Everything we publish, in one place. Grouped by what you are actually trying to do rather than by what team wrote it. Nothing here is gated, and nothing asks for an email first. ### groups The numbers before the conversation. ### items Pricing and the rate calculator Published rates, plus a calculator that runs your own volume and card mix. TAP, Vila Galé, KuantoKusta, Rede Expressos, Kabuki, Wink and more — outcomes in the customer's words. Card scheme fee schedule The full Visa and Mastercard schedule we pass through at cost, region by region — as a page, a PDF, JSON and CSV. What card scheme fees are The explainer behind the schedule: interchange versus scheme fees, what drives them, a worked example. All provider comparisons Stripe, Adyen, Mollie, Checkout.com, Ifthenpay, Eupago, Pay.nl and Buckaroo on one page, with a dated rate line each. Compared with Stripe Where each one is genuinely stronger, on the axes that decide it. Compared with Adyen Enterprise scale against EU-native depth and a named engineer. Compared with Mollie Two European providers, side by side. Compared with Checkout.com Approval performance and what the contract actually commits to. Compared with Pay.nl A monthly package against no monthly fee, iDEAL from €0.19. Compared with Buckaroo iDEAL bundles, €50 chargebacks and terminals, side by side. What the move looks like before you commit to it. ### items The step-by-step runbook for switching with no downtime, including shadow mode alongside your current provider. Talk to a payment engineer Not a sales qualification call — the person who would run the integration. For whoever has to integrate it. ### items REST API, SDKs, plugins and webhooks. The same primitives in sandbox and production. Free sandbox access A working sandbox the same day, with no contract in front of it. For merchants already live. ### items Guides and answers for day-to-day operation, disputes and reporting. Live availability and incident history for every service. --- ## Approvals & routing — https://www.paybyrd.com/approvals-routing Summary: multi-acquirer routing — how an authorisation is scored against acquirer, market, card brand and method, retried on a second acquirer when the first soft-declines, and failed over when an acquirer degrades Get more payments A decline is often a routing outcome, not a verdict on the card. Paybyrd picks the acquirer most likely to get each transaction approved — by BIN, by issuer, by market — and re-presents when the first answer is wrong. cohort average, rolling Illustrative simulation of one routing decision. The card and identifiers are generated for this page; the signal set and ranking behaviour mirror production. Local licence · same market Nothing about the cardholder changed. Multi-acquirer routing sends each card authorisation to the acquiring bank most likely to approve it, and retries a soft decline through a second acquirer before the customer sees an error. Multi-acquirer routing: get more payments approved. three attempts, one approval. Watch the decision the router makes. Each attempt goes to a different acquirer, chosen on the signals below — not in a fixed order. Illustrative simulation of the routing cascade. Transaction identifiers are generated for this page; the signal set and acquirer sequencing mirror production behaviour. Local licence available Historic approval rate Network token present Three stacked layers. Not one magic flag. Approval uplift is not a setting somebody forgot to switch on. It is three independent mechanisms compounding. ### items Each BIN goes to the acquirer most likely to approve it, on a decision graph fed by your own historical outcomes rather than a static preference list. A Tokyo card hits a Tokyo issuer through a locally licensed acquirer, not a remote one. Domestic transactions are trusted differently, and the difference is measurable. Visa, Mastercard and Amex tokens survive card reissue and carry higher issuer trust than a raw PAN, lifting success on stored credentials and refunds. Same merchants, same traffic, same period — parallel-processed against the provider they came from. Cohort-blended uplift across all comparisons. Figures pending clearance; see the proof registry. ### items Do I have to change acquirers to use this? No. Paybyrd is acquirer-agnostic: keep your existing acquirer agreements, your negotiated rates and your in-flight volume commitments. Routing orchestrates on top of what you already have. If you later decide to consolidate, we can act as your acquirer across 90+ markets, but that stays a separate decision on a separate contract. How does the router decide where a transaction goes? On the signals available at authorisation time: issuer country, BIN range, whether a locally licensed acquirer is available in that market, the historic approval rate for that combination, and whether a network token exists. The decision graph is fed by your own outcomes, so it gets more accurate on your traffic specifically rather than on an industry average. Does routing add latency to checkout? The routing decision itself is sub-millisecond — it happens before the authorisation leaves us, not as an extra round trip. A retry through a second acquirer adds one authorisation cycle, typically a few hundred milliseconds, which is why same-session recovery is usually invisible to the shopper. What happens if an acquirer goes down? Traffic fails over to the next candidate automatically. Because the router already holds a ranked list per BIN, an outage is handled as a routing change rather than an incident — you do not need to make a decision or deploy anything for failover to happen. Can I override the routing? Yes. You can pin specific traffic to a specific acquirer — by BIN range, market, card type or merchant account — where a commercial agreement or a regulatory requirement demands it. Overrides sit above the automatic decision, and you can see what the router would have chosen instead. Approval rate is the least-managed number in your payment stack. Merchants negotiate the rate for months and never ask what proportion of their transactions actually get approved. One is a line on a contract. The other decides how much revenue reaches the bank — and it is the one nobody is accountable for. ### args A tenth of a point is not a rounding error At €100M of volume, one percentage point of approval rate is €1M. Merchants who would fight for two basis points on their processing fee routinely accept an approval rate nobody has ever benchmarked. The fee is visible on every invoice; the declines are not on any of them. That asymmetry is why the smaller number gets all the attention. Geography is not a detail, it is the mechanism A card issued in Tokyo presented by an acquirer in Amsterdam looks, to the issuer, like a cross-border transaction from an unfamiliar counterparty — and is scored accordingly. The same card presented by an acquirer holding a local licence looks domestic. Nothing about the cardholder, the basket or the risk changed. The route did, and issuers treat the two differently. Your BIN mix is not anyone else's A static acquirer preference list is a guess made once, by someone who has never seen your traffic. Routing that learns from your own outcomes gets better on the specific issuers, markets and card types you actually process, rather than on an industry average that describes nobody. The longer it runs on your volume, the less it resembles a default. The gains are independent, so they compound Multi-acquirer routing, local acquiring and network tokenisation solve different failures: the wrong counterparty, the wrong geography, and a credential the issuer no longer trusts. Because they are independent, they stack rather than overlap — which is why the blended figure is a cohort result and not a single lever anybody switched on. You negotiated the rate for months. Nobody asked what your approval rate was. Routing is not a setting to enable. It is the decision made on every authorisation before it leaves us, and on Paybyrd it is already running on the traffic you send today — with your existing acquirer agreements intact. Not a retry loop. A decision, made every time. Before an authorisation leaves us it is scored against the signals below and sent to the acquirer most likely to approve it. The same card, presented two different ways, gets two different answers. Illustrative simulation. Identifiers are generated for this page; the signals, ranking and failover behaviour mirror production. What the router knows Issuer country, BIN range, whether a locally licensed acquirer covers that market, the historic approval rate for the combination, and whether a network token exists. Candidates ordered on evidence The acquirer list is re-ranked per transaction. A locally licensed acquirer in the cardholder's own market outranks a cross-border one with a better headline rate. One authorisation, best route The transaction goes to the top candidate. This is not a retry — nothing has failed yet. It is the first attempt, made deliberately rather than by default. An outage is a routing change If a candidate stops responding, traffic moves to the next one automatically. You do not deploy anything, and you do not get paged. --- ## Payment recovery — https://www.paybyrd.com/payment-recovery Summary: what happens after a decline — soft-decline classification, network-token re-presentment through a different acquirer, payday-aware retry scheduling, and the recovered-revenue ledger what others decline. Most processors return a decline and move on. Paybyrd treats it as the start of the flow: classify the reason, repair what can be repaired, and re-present through a different acquirer before the customer notices. recovered this month Illustrative simulation of the retry waterfall. Transaction identifiers and amounts are generated for this page; the acquirer sequence and decline handling mirror production behaviour. 05 · do not honour re-presenting · Acquirer B · local licence network token attached Approved · €89.90 captured classified: soft decline Illustrative simulation of one payment failing and healing. Amounts and identifiers are generated for this page; the decline codes and retry sequence mirror production. Payment recovery is the set of retries a platform runs after a card is declined: classifying the decline, re-presenting it through a different acquirer or a network token, and timing the retry to when funds are likely to be there. Failed payment recovery: win back what others decline. One thousand attempts, and where they actually end up. The gap between a 92% processor and a 96% one is not luck. It is what happens in the four seconds after the first decline. Retry · alternate acquirer 920 / 1,000 Four reasons a card says no. Three of them are recoverable. Recovery is not retrying blindly — that burns issuer trust and can breach scheme rules. Every decline is classified first, and only the recoverable ones are re-presented. ### items Insufficient funds, temporarily Re-presented on a schedule tuned to payday cycles and issuer behaviour rather than a fixed timer. The customer is never asked again. The acquirer was the problem, not the card The same card is re-presented through a different acquirer — often one with a local licence in the cardholder's market, where issuer trust is higher. Card expired or was reissued Network tokens follow the cardholder through reissue, so a stored credential keeps working after the plastic changes. Stolen, blocked, or refused outright Never retried. Re-presenting a hard decline damages your issuer standing and breaches scheme retry rules — so we stop. Approval rate is not a metric. It is revenue. One percentage point of approval rate on €100M of volume is €1M. Recovery is the cheapest percentage point you will ever buy, because the customer already decided to pay. cohort blended vs prior provider at €100M annual volume recovered / year The customer already wanted to pay. Recovery is the difference between capturing that and writing it off. without the hand-waving. ### items Is retrying a declined card allowed? Yes, within limits the card schemes set — and those limits are the point. Visa and Mastercard cap retry attempts and require that hard declines (stolen, blocked, do-not-honour with a permanent reason code) are never re-presented. Paybyrd classifies every decline against those rules before deciding, so recovery never puts your issuer standing or your scheme compliance at risk. Retrying blindly is the practice that gets merchants fined; this is the opposite of it. Will my customer be charged twice? No. A retry only ever happens on an attempt that was declined, meaning no funds were captured. The authorisation is re-presented, not duplicated, and idempotency keys on our side prevent a double capture even if your system sends the same request twice. If a retry succeeds, the customer sees exactly one charge. Does the customer know a retry happened? Usually not, and that is the design goal. Same-session retries through an alternate acquirer resolve in under a second, so the shopper sees a normal approval. Scheduled retries for soft declines happen server-side against a stored credential — the customer is not asked to re-enter anything, and only hears from you if every attempt fails. How is this different from my current processor's retries? Most single-acquirer processors can only retry against the same acquirer that just declined, which is why their recovery rates are low — they are asking the same question twice. Paybyrd is multi-acquirer, so a retry can go to a different acquirer entirely, often one holding a local licence in the cardholder's market where issuer trust is materially higher. That routing decision is the recovery. What happens to subscription and stored-card payments? This is where recovery pays for itself fastest. Network tokenisation keeps a stored credential valid through card reissue and expiry, so recurring charges that would otherwise fail silently keep working. Combined with soft-decline scheduling tuned to payday cycles, involuntary churn on subscriptions drops without you writing a single line of retry logic. Do I need to change my integration to get this? No. Recovery runs inside the payment flow you already use — hosted checkout, embedded components or direct API. There is no separate product to integrate and no retry logic to maintain on your side. If you are already sending payments through Paybyrd, it is already running. followed all the way to revenue. A single transaction, from the moment the issuer says no to the moment the money lands. Every step is a decision the platform makes without asking you. Illustrative simulation. The transaction is generated for this page; the decline classification, retry scheduling and acquirer sequencing mirror production behaviour. The issuer says no An authorisation comes back declined with reason code 05 — do not honour. It is the most common decline in card payments, and it almost never means what merchants assume it means. Soft or hard? The code is matched against scheme rules. 05 is ambiguous and recoverable; a hard decline like stolen or blocked is never re-presented, because that is what breaches retry limits. Through whom, and when The acquirer list is re-ranked on issuer signals so a locally licensed acquirer goes first. For funds-related declines the remedy is time instead — a retry scheduled against payday behaviour. The same card, sent differently The authorisation is re-presented — not duplicated — through a different acquirer, with a network token in place of the raw card number. The sale completes The customer sees one charge and never knew there was a second attempt. The revenue was always there; it just needed a different route. You already paid for the customer who just got declined. Every declined transaction is a customer who found you, chose you, and reached for their card. The acquisition cost is spent. The inventory is reserved. The only thing missing is an authorisation — and most processors treat that as somebody else's problem. ### args A decline is not a verdict on the customer The most common decline code in card payments is 05 — do not honour. It is a refusal with no stated reason. It does not mean the card is bad, the customer is broke, or the purchase was fraudulent; it means one issuer, at one moment, through one acquirer, said no. Send the same card through a different acquirer — ideally one holding a licence in the cardholder's own market — and the answer frequently changes. Nothing about the customer changed. Only the route did. The economics are unlike anything else you can buy Improving conversion normally means spending more: better creative, more traffic, deeper discounts. Recovery is the opposite. The customer is already at the payment step with intent proven and cost sunk. A point of approval rate on €100M of volume is €1M, and it arrives without a single additional visitor. There is no other line item in a payments contract where the return is this direct. Most processors are structurally unable to fix it A single-acquirer processor can only retry against the acquirer that just declined — asking the same question twice and expecting a different answer. That is why their recovery rates are low, and why the topic rarely appears in their reporting. It is not negligence; it is architecture. Multi-acquirer routing is the prerequisite, and it has to be built before the first decline, not after. On subscriptions, a decline is churn you never chose For recurring revenue the cost compounds. A card expires or is reissued, a renewal fails silently, and a customer who never decided to leave is gone. This is involuntary churn, and it is routinely larger than the voluntary kind. Network tokens keep a stored credential valid through reissue, and funds-related declines get retried against payday behaviour rather than a fixed timer — so the subscription survives without anyone being asked to re-enter a card. The revenue was always there. It just needed a different route. Recovery is not a feature bolted onto the payment flow. It is what the payment flow should have been doing from the beginning — and on Paybyrd it runs on every transaction you already send us, with nothing to integrate and no retry logic to maintain. --- ## Restaurants — https://www.paybyrd.com/restaurants Summary: tableside ordering and payment from the guest's own phone via Quivi; bill splitting, contextual tipping, kitchen display, and card-based recognition on the return visit; behind Kabuki Tableside pay and loyalty in one tap. Turn tables faster without hiring. Guests scan, order and pay from their own phone; the kitchen sees it immediately; the card that paid is the card you recognise next visit. Illustrative simulation of one table's service. Names, items and amounts are generated for this page; the flow mirrors Quivi in production. Restaurant group · Paybyrd customer Filmed on location at Kabuki. The overlay describes the tableside flow set out on this page, not this venue's live data. Scan · no app To the kitchen Paid and split From signature to first order Gratuities vs flat tip entry Card approval at the table Restaurant payments: pay at table, tips and loyalty in one tap. The card is the loyalty card. No plastic, no app, no sign-up. The same card that pays is the identifier. A returning guest is recognised at the table and at the counter, across every one of your locations, without anyone being asked to join anything. Recognised on the second visit, not the tenth Works across every venue you operate, on one guest record Runs on network tokens and BIN metadata — never the card number Nothing for the guest to install, remember or carry ### items Do guests need to download an app? No. Ordering and payment open in the phone's browser from a QR code on the table. There is no app to install, no account to create and nothing for the guest to remember on the next visit — which is the reason adoption at the table is high rather than theoretical. Does this replace my POS or sit alongside it? It can do either. Quivi is a full point-of-sale — orders, kitchen display, floor plan, reporting — so most venues run it as their POS. If you already have a POS you are committed to, Paybyrd terminals and pay-at-table work alongside it and the payment side is handled either way. What happens when the Wi-Fi drops mid-service? Terminals keep taking card payments offline and reconcile when the connection returns, so service does not stop because the router did. QR ordering needs the guest's own mobile data or your Wi-Fi; if both are down, staff take the order on a handheld as normal. How do tips reach the staff? Tips are captured at payment and reported separately from revenue, so distribution follows whatever policy you already run — per shift, per section, pooled or individual. The figures are in the same reporting as everything else rather than in a separate app somebody has to reconcile by hand. Can I run several venues on one account? Yes. Multiple venues sit under one merchant account with per-venue reporting, per-venue menus and a single settlement. Guest recognition works across all of them, so a regular at one location is known at the next. The bill is the slowest part of the meal. Everything before it has been optimised for decades — the kitchen, the menu, the seating plan. Then service stops dead while somebody finds a card machine, walks it to the table, and does arithmetic out loud for six people who are already standing up. ### args Table turn is the only capacity you can add for free You cannot add covers without adding tables, staff or hours — except at the end of the meal. The twelve minutes between asking for the bill and vacating the table is dead time on a finite asset, repeated every sitting, every night. Compress it and you have added covers to a Friday without hiring anyone or moving a wall. The card machine is a staffing decision in disguise Every payment that requires a member of staff to walk to the table, wait, and walk back is labour spent on administration rather than service. On a busy night that is not an inconvenience; it is the difference between a section running smoothly and a section running behind. Paying from the guest's own phone takes the whole task out of the rota. Splitting is where good service goes to die Dividing a bill is arithmetic performed under social pressure by people who have been drinking. It produces the longest, most error-prone and least pleasant moment of the evening — and it is entirely avoidable. When the table splits on their own screens, six ways if they want, the awkwardness disappears and so does the queue at the till. The card already knows who your regulars are Loyalty schemes fail because they ask the guest to do something: download, sign up, remember, carry. The card they are already paying with is a stable identifier across every one of your venues. Recognition on the second visit, with no plastic and no app, is the version of loyalty people actually participate in — because participation is not required. You cannot add tables. You can stop wasting the last twelve minutes of every one. Quivi is a Paybyrd company — the same engineering team, the same support, the same contract — so the point of sale, the payments and the guest recognition are one system rather than three vendors pointing at each other when service goes down. Seated at 20:14. Gone by 21:38, without waiting for anyone. The parts of service you cannot automate are the parts worth paying for. Everything else — taking the order, finding a terminal, dividing the bill — is a queue standing between your team and the next table. Illustrative simulation. Guest names, order lines and amounts are generated for this page; the sequence and timings mirror Quivi in production. The guest opens the menu from the QR on the table. No app, no download, no account — which is the only reason table-side ordering gets used rather than admired. Items go straight to the kitchen display. Nobody carries a docket, and nobody mishears an order across a loud room. The bill is settled from the guest's own phone, or on a handheld brought to the table. No walk to the till, no queue to leave. Four people, four cards, one bill — divided on their own screens without arithmetic performed out loud. The prompt appears at the moment of payment, on the guest's device, with amounts you set rather than a fixed default. The card that paid is the identifier. They are known on the second visit, at any of your venues, without having joined anything. ### items Wagyu gyoza · 6 Yuzu highball · 2 3rd visit · last seen 18 days ago Six ways to divide one bill. None of them involve a calculator. Splitting is arithmetic performed under social pressure by people who have been drinking. It is the longest and least pleasant moment of the evening, and it happens at every table with more than two people. One tap. The bill divides by the number of people paying. Each guest selects what they ordered from their own screen. Custom proportions when one person is covering more. Someone pays part of the bill; the balance stays open. The table settles on a single card, tip included. Cash and card Mixed settlement without breaking the ticket. A Friday service, hour by hour. Covers are not spread evenly and neither is the pressure. The bottleneck is rarely the kitchen — it is the eleven minutes at the end of each table when service has finished but the table is not yet free. Turning tables faster at peak is the only way to add covers without adding tables, staff or hours. Asked at the right moment, on the right screen. A tip prompt on a terminal held by a member of staff is a social transaction. The same prompt on the guest's own phone, at the moment they are already paying, is a private one — and the difference shows up in the average. smart contextual prompts vs flat amount entry Amounts you set, per venue and per service Reported separately from revenue, so distribution follows your existing policy Per shift, per section, pooled or individual — the model is yours Never forced, never a default the guest has to decline Five logins per shift. Four bills per month. The average venue runs a POS, a card terminal from someone else, a delivery tablet, a reservations tool and a reporting spreadsheet that reconciles none of them. Quivi is a Paybyrd company, so the till and the payments are one contract and one support number. Same engineering team, same support, same contract — no vendor pointing at another vendor when service goes down. for two jobs. Tableside and counter are different problems. One needs to be carried all night; the other needs a printer, a drawer and a customer-facing screen. ### items 5" HD touch · 9h battery · 4G / Wi-Fi / BT Tableside · terrace · events Sunmi T3 Pro Max 15.6" + 10" customer display · drawer, scale and scanner · PCI 6 SRED Counter · pass · self-service ### quivi Free your team with a QR code. Quivi is Europe's all-in-one POS, payments and AI — built for hospitality. Guests order and pay from their phone. Your kitchen gets the ticket instantly. Your front desk gets the payment automatically. One contract covers it all, including hardware. Quivi is part of the Paybyrd group — same engineering team, same support, same contract. No vendor handoff, ever. ### steps Guest scans the QR at the table No app to install — camera opens the menu instantly. Menu loads · live availability 86'd items hide. Allergens, photos, upsells inline. Split per person · tip pre-suggested Three friends, three Apple Pays, one tap each. Paid · KDS pinged · invoice issued Order goes straight to the kitchen. Folio updates. Table closes itself. Bacalhau · house Vinho verde · 250ml Sea bass · 86'd Smart tip suggestions in checkout Same staff · QR self-ordering Branded site replaces Glovo / Uber MB WAY, Apple Pay, food vouchers, more QR ordering, bill split, smart tips Guests order, split, tip and pay from their phone. No app. No extra staff. Cloud POS · KDS · floor plans Menu builder, kitchen display, staff management, real-time analytics. Learn in minutes. AI menu builder "Create a lunch menu with 3 starters, 4 mains, 2 desserts at €15." Quivi does the rest. AI reservations on WhatsApp 24/7 reservation agent. Confirms bookings, slashes no-shows, never sleeps. Branded delivery website Zero commission. Your brand, your customers, your data. Plugs into Glovo, Uber Eats, Bolt Food. Auto Google reviews Every paying guest gets a review prompt. Reputation grows on autopilot. All in one platform Replace five tools with one. Built for hospitality, not retrofitted. QR ordering at peak hours changed our throughput. We served 40% more customers without hiring more staff. Owner, Manjar do Norte The hardware · included with subscription Four shapes for every part of the property. Same Quivi software on every one of them. Portable — tableside & poolside PAX A920 Pro Countertop — front desk & restaurant All-in-one — ordering + payment Sunmi T3 Pro Self-service — kiosk & unattended Quivi is Europe's all-in-one POS, payments and AI — built for restaurants. Guests order and pay from their phone. Your kitchen gets the ticket instantly. Your till gets the payment automatically. Built for restaurants, not retrofitted. --- ## Transport — https://www.paybyrd.com/transport Summary: ticketing sold online, at the counter and on board on one contract; offline card capture with deterministic queueing and reconciliation on reconnect; unattended kiosk and validator sale; behind Rede Expressos Passengers buy where they are: on the site, at the counter, at the gate, or on board. Same fares, same settlement, same reporting — and a card that still works when the connection does not. Portugal's intercity coach network Filmed on location with Rede Expressos. The overlay illustrates the three channels described on this page. Sold at the counter Sold on board · offline Routes on the network we serve Channels on one contract Settlement and reconciliation Transport ticketing payments: online, at the counter and on board. Every seat, sold. Sell the seat wherever the passenger is standing. Most operators run web, counter and onboard as three separate systems with three reconciliations. They do not have to be. ### items Web and mobile checkout Cards, wallets and local methods with the routing that keeps approval rates high on cross-border and last-minute purchases. Station and agent terminals Attended sale at the desk with the same fare logic as the site, so a ticket bought at a window settles identically to one bought online. Handheld and SoftPOS Sell and validate on the vehicle. Payments captured offline when coverage drops and reconciled automatically once the signal returns. A tunnel is not a failed payment. Transport runs where connectivity does not. Offline capture is not a degraded mode bolted on afterwards — it is how onboard sale is designed to work. Cards accepted with no live connection, reconciled on reconnect Deterministic queueing — no duplicate captures when the signal returns Same settlement and reporting as online sales, not a separate ledger Terminals rated for vehicle mounting and all-day shifts ### items Can we sell onboard without a live connection? Yes. Onboard terminals capture card payments offline and queue them locally, then reconcile automatically once coverage returns. The queue is deterministic, so a journey through a long tunnel or a rural stretch produces exactly one capture per sale — not a duplicate when the signal comes back. Do online and counter sales settle together? Yes. Web checkout, station terminals and onboard devices all settle into the same account with one reconciliation, itemised per channel, per route and per device. That is usually the reason operators consolidate: three systems means three reconciliations and three sets of numbers that never quite agree. How do refunds and cancellations work across channels? A ticket bought online can be refunded at the counter, and one bought onboard can be refunded online, because the payment record is the same record everywhere. Refunds follow the original payment method automatically, including to a card that has since been reissued where a network token exists. Can we handle peak-hour surges? Capacity is the platform's, not the terminal's — a commuter peak or a holiday weekend is a routing and throughput question we handle upstream. Onboard devices are unaffected by peak load on the web channel, because they are not queuing behind it. What about unattended sale — kiosks and gates? Supported on the same platform. Unattended terminals sell and validate without staff, with the same fare logic and the same settlement, which is what keeps a kiosk sale from becoming a separate reporting stream nobody reconciles. Three systems selling the same seat. Most operators run web, counter and onboard as separate stacks bought at different times for different reasons. Each one settles somewhere else, reports differently, and produces a number that never quite agrees with the other two. ### args Reconciliation is the tax you pay for three systems Every channel that settles separately is a set of figures somebody has to align by hand at month end — and a discrepancy nobody can explain without opening three dashboards. That work is invisible on any invoice, which is exactly why it never gets costed. One settlement is not a convenience; it is the removal of a recurring job. Connectivity is a route characteristic, not an incident Transport operates through tunnels, across rural stretches and inside vehicles moving at speed. Treating a lost signal as an outage means designing for a condition that occurs on every journey. Offline capture is not a fallback mode — it is the normal operating state for onboard sale, and the deterministic queue is what stops a returning signal producing a second charge. The refund is where the seams show A passenger who bought online and needs a refund at the counter will discover, in about four seconds, whether your channels share a payment record or merely coexist. Nothing exposes a fragmented stack faster than a customer standing at a desk while somebody explains that the ticket was bought on a different system. Peak is a platform problem, not a terminal problem A holiday getaway or a commuter surge is throughput, and throughput belongs upstream where it can be absorbed. When capacity is handled at the platform rather than the device, a driver's handheld is unaffected by whatever the web channel is doing — because it was never queuing behind it. Three systems means three reconciliations and three sets of numbers that never quite agree. One platform across web, counter and onboard is not a consolidation project for its own sake. It is what makes a ticket refundable anywhere, a signal drop survivable, and a month-end close something that finishes on the first attempt. Lisboa to Porto. Sold three different ways, settled once. The same service, the same fare, the same reconciliation — whether the seat was bought on the site three weeks ago, at the counter this morning, or from the driver as the doors closed. Illustrative simulation of one service. Route, times and identifiers are generated for this page; the channel behaviour and settlement model mirror production. Lisboa · Sete Rios Porto · Campanhã Three weeks out Bought on the site with a card and a wallet. Routed for approval like any other e-commerce payment. Attended sale at Sete Rios. Same fare logic as the site, so the ticket settles identically. As the doors closed Sold by the driver on a handheld. Captured offline through the tunnel and reconciled on reconnect. A tunnel is not a failed payment. Between Lisboa and Porto a vehicle loses coverage repeatedly. Designing for that is not a resilience feature — it is the normal operating condition of selling on a moving vehicle. Illustrative simulation of a coverage gap. Times and identifiers are generated for this page; the queueing and reconciliation behaviour mirror production. ### steps The vehicle enters a tunnel. The terminal keeps accepting cards. Two tickets sold. Both queue locally with a deterministic key. A third sale joins the queue. Nothing is lost and nothing is retried yet. The queue drains in order. Three captures, three tickets — never four. The deterministic queue is the part that matters. A returning signal must not produce a second charge for a passenger who already has a ticket. Kiosks and gates, on the same platform. Unattended sale is where fragmented stacks usually break: a separate device, a separate merchant account, a separate reporting stream nobody reconciles. It does not have to be a separate anything. ### items Sells and prints without staff, on the same fare logic and the same settlement as the counter. Validates a ticket bought through any channel, because the payment record is one record. One reporting stream Kiosk sales appear beside counter and onboard sales, per route and per device — not in a separate export. Rated for the vehicle, not the countertop. A terminal on a coach spends its life mounted, vibrating, and running a full shift away from power. That is a different specification from a device that sits on a bar. ### items 5.5" HD touch · AC + battery backup · 4G / Wi-Fi / BT Counter · station desk 5" HD touch · 9h battery · 4G / Wi-Fi / BT Onboard · conductor · platform ---