On The Wire

payware
  • 0.0 (0)
  • Business

The payments industry is at an inflection point. Card networks still consume 2-3% of every transaction. Settlement takes days. Banks earn little while card schemes capture the value. It doesn't have to work this way. On The Wire explores the shift to account-to-account payments - where banks query a resolution network, funds move directly between accounts, and fees drop to 0.5%. For payment institution executives, ISV partners, and merchants rethinking the cost of commerce. Produced by payware - the transaction resolution network for instant A2A payments.

  1. 9h ago

    E-commerce Checkout Optimization: Beyond Card Payments - Full Episode | On The Wire

    Card checkout in 2026 is a good customer experience. One-click for returning buyers, wallets, guest flows, real-time fraud screening. The problem is not the front end. It is the economics behind it and the ways it fails. Total payment cost for e-commerce is 2-4% of revenue once you count everything: processing at 1.0-2.5%, fraud losses at 0.3-0.8%, false declines at 0.5-2.0% of revenue, expired card churn running 15-25% annual renewal failure, and chargeback operations at €8-25 per dispute. Merchants optimise the first line and ignore the other four. Three implementations, with the arithmetic. A fashion retailer, €22 million, 185,000 orders, €119 average, 42% repeat. Baseline payment cost €504,600, which is 2.3% of revenue against 8-12% net margins, so payments eat 20-25% of margin. A2A reached 3% in month one, 12% by month six, 25% at maturity. At 25%: processing down €38,500, fraud down €20,900, €16,000 in false-decline revenue recovered, chargebacks down €10,140, expired card benefit €8,000. Total €93,540 on a €9,000 build. Break-even 35 days, five-year NPV €458,000. Adoption skewed hard by segment: 32% among repeat customers, 8% among first-timers, 28% on mobile, 15% on desktop, 35% on orders above €150. A freelance services marketplace, €8.5 million, paying twice, once to collect from buyers and once to pay sellers. Baseline 3.0% of volume. Marketplaces carry 0.8% chargeback rates because "service not as described" is easy to claim and hard to fight. At 35% A2A: €32,725 processing, €5,950 payouts, €14,275 fraud, €14,620 chargebacks. €67,570 total, break-even 5.1 months. The structural win is that cryptographic authorization proof kills the "I did not authorize this" dispute, which is 60-70% of marketplace chargebacks. Sellers get paid instantly instead of waiting three days. A subscription box company, €4.2 million, 12,500 subscribers at €28 a month. Payment costs: €412,800. That is 9.8% of revenue. Processing is €58,800 of it. The other €354,000 is involuntary churn: 1,000 subscribers a year lost to failed payments, 65% of those to expired cards. 60-70% never update the card, because a failed payment is a good enough reason to quit. At 28% A2A: processing saves €10,584, involuntary churn prevention retains €70,560. Churn prevention is worth 6.7x the fee savings. Total €94,184, break-even 2.9 months. That ratio is the point. For subscriptions, payment stability beats payment cost, and it is not close. Also covered: why conversion did not drop in any of the three (flat at the retailer, up 0.2 points at the marketplace, up 0.4 at the subscription company); the honest limits, since A2A is debit-only and SEPA-bound, which still covers 85-95% of a European customer base and 70-85% of European card users who are on debit anyway; refunds landing in 10-15 seconds against 5-10 days for cards; and the optimisation details that moved the needle, like raising the bank option in the checkout list (+15% adoption) and putting bank logos next to it (+8%). Plus the competitive argument. Two €20M brands, one adopts in 2025 and one in 2027. The early mover banks €167,000 before the late mover starts, and reinvests it while the competitor is still paying full freight. For anyone who has audited their processing rate and thinks they have audited their payment costs. Full source material and the complete guide: https://go.payware.eu/p-checkout-f Produced by payware - the transaction resolution network for instant A2A payments. AI-generated from payware's published research and documentation.

  2. 9h ago ·  Bonus

    E-commerce Checkout Optimization: Beyond Card Payments - The Briefing | On The Wire

    Ask an e-commerce merchant what payments cost them and they quote the processing rate. 1.2%. The real number is roughly double that, and most of it never appears on the processor's invoice. A retailer doing €22 million a year pays €264,000 in card processing. They also lose €104,000 to fraud and prevention tooling, €65,000 to false declines where their own filters blocked real customers, €42,000 to chargeback fees and the staff time behind them, and €30,000 to reconciliation and chasing expired cards. Total: €505,000. That is 2.3% of revenue, not 1.2%. The line that gets ignored is false declines. 1.5% of legitimate customers are turned away by fraud filters. They do not retry. That is lost revenue that shows up nowhere in a payments report, because a sale that never happened has no invoice. Add A2A at 25% adoption and the picture changes on five lines at once. Processing drops €38,500. Fraud drops €20,900, because bank authentication takes the A2A fraud rate to 0.02%. €16,000 of previously declined revenue completes. Chargebacks fall €10,140. Expired card friction is worth another €8,000. Combined: €93,540 a year against a €9,000 integration. Break-even in 35 days. The conversion worry does not survive contact with data. Across the three implementations in this episode, conversion was flat or up. More payment options do not paralyse customers. They stop customers from being declined. Full episode for the fashion retailer, the marketplace, and the subscription box company where payment costs hit 9.8% of revenue, plus the segment data on who actually adopts. Full source material and the complete guide: https://go.payware.eu/p-checkout-b Produced by payware - the transaction resolution network for instant A2A payments. AI-generated from payware's published research and documentation.

  3. Jul 26

    Integration 101: How Payment Institutions Connect to payware - Full Episode | On The Wire

    Every bank evaluating A2A asks the same three questions: what does integration actually involve, how long does it take, and who do we need. This episode answers all three with real timelines, real team composition, and real budget figures. First, the structure of the network, because it determines your scope. Payment institutions bring customers, the people who pay. payware onboards merchants directly. payware is the neutral layer in between. This means a bank's integration is one-sided: connect your systems so your account holders can pay at every merchant already on the network. You do not recruit merchants. You do not support them. That work is done. Phase 1, evaluation and partnership, 2-4 weeks. Customer base analysis, opportunity sizing, competitive positioning, architecture review. Then licensing verification (PI or EMI under PSD2), AML and KYC alignment, GDPR review, liability allocation, SLAs, and the commercial agreement. Sandbox access and test credentials land at the end. A worked example from the episode: 2 million account holders, 400,000 strong A2A candidates, a conservative 10% first-year adoption gives 40,000 active users at 3 transactions a month and €45 average, which is €65 million of annual volume. Phase 2, technical integration, 4-8 weeks. The core flow: read the transaction ID, query the API for merchant name, amount and reference, present it in your app, authenticate the customer with biometric or PIN, authorize the debit, confirm back. Around it sits API-key or OAuth authentication, request signing, idempotency, error handling, retry logic. Two to three weeks. Then status callbacks: an HTTPS endpoint, signature verification, deduplication, asynchronous processing, status persistence. One to two weeks. Then settlement and reconciliation against daily reports, wired into your accounting systems, with exception handling. One to two weeks. Testing is where timelines are won or lost. Fifty to a hundred happy-path transactions, 30-50 edge cases (declines, timeouts, network failures, duplicate handling), sustained load testing above 500 transactions an hour, and 20-30 security scenarios covering authentication bypass, request tampering, callback spoofing and data exposure. Two to three weeks, overlapping the build. Phase 3, go-live, 1-2 weeks. Support runbooks, escalation paths, monitoring on API health, callback delivery, settlement reconciliation, error rates and latency, with alerting split between critical and warning. Resources. A technical lead at 60%, one or two backend engineers at 60-80%, a QA engineer at 40%, plus periodic legal, compliance and operations. Four to seven person-months over two to three calendar months. Budget €30,000-70,000 one-time: €5,000-15,000 integration fee, €20,000-40,000 internal development, €5,000-15,000 testing. Ongoing: 0.5% of volume plus €12,000-25,000 a year. The case study. A German regional bank, 1.5 million account holders, five backend engineers. Agreement signed in week 2. API integration weeks 3-6 with two engineers at 70%. Testing weeks 7-9, 150+ test cases, load and security passed. Support and go-live weeks 10-11. Live in week 12. Six months later: 45,000 customers using A2A, 2.8 transactions a month each, €28 million annualised volume, 4.6 out of 5 on payment experience, and 12% of volume running on-us at near-zero cost because both sides banked there. Also covered: what to do with a thin engineering team (managed integration, MCP-accelerated development, or a phased rollout over 4-5 months), why security testing cannot be compressed, and the ongoing maintenance load once things settle at 5-10 hours a month. The constraint was never technical feasibility. It is timing. Full source material and the complete guide: https://go.payware.eu/p-pi-integration-f Produced by payware - the transaction resolution network for instant A2A payments. AI-generated from payware's published research and documentation.

  4. Jul 26 ·  Bonus

    Integration 101: How Payment Institutions Connect to payware - The Briefing | On The Wire

    A regional bank with 2 million account holders decides to offer A2A payments. The product team budgets a year. They are off by a factor of four. Integration runs 7 to 12 weeks. Evaluation and partnership takes 2-4 weeks. Technical integration takes 4-8 weeks. Go-live preparation takes 1-2 weeks. With a modern API stack and an experienced team, the floor is 5-6 weeks. The reason banks overestimate is that they assume a bank's job in a payment network is to recruit merchants. It is not. payware onboards and manages merchants directly. The bank's scope is one connection: link your systems to the API so your account holders can pay. From day one of go-live, your customers can pay at every merchant already on the network. There is no merchant-by-merchant rollout, because that side is already built. What actually gets engineered is smaller than most product teams expect. Read a transaction ID, query payware for the payment details, present them in your app, authenticate the customer, authorize the debit, confirm. Then status callbacks, then settlement reconciliation. Start with one method and expand later. The economics: €30,000-70,000 one-time, roughly 4-7 person-months across 2-3 calendar months, then 0.5% of volume plus €12,000-25,000 a year to run. After stabilisation, maintenance is 5-10 hours a month. One number worth knowing before you model anything. When the payer and the merchant both bank with you, it is an on-us transaction settled by internal book transfer, and the cost approaches zero. In the German bank case in this episode, that was 12% of volume within six months. Full episode for the phase-by-phase breakdown, the API and callback specifics, the testing burden, team composition, and the case study numbers. Full source material and the complete guide: https://go.payware.eu/p-pi-integration-b Produced by payware - the transaction resolution network for instant A2A payments. AI-generated from payware's published research and documentation.

  5. Jul 19

    Understanding Interchange Fees: Why They Exist and Why They're Declining - Full Episode | On The Wire

    Interchange is the most scrutinised fee in payments and the least understood. This episode takes it apart: where the money actually goes, why the fee exists, why the original justifications no longer hold, and why it is now declining for structural reasons rather than political ones. Start with the flow. On a €100 card payment in regulated Europe, the merchant keeps €98.65-99.30. The acquirer takes €0.20-0.40, the card network €0.10-0.15, the issuer €0.20-0.30, the gateway €0.30-0.50. Total merchant cost: €0.70-1.35. Run the same $100 through an unregulated US credit card and the issuer alone takes $1.50-2.50. Total merchant cost: $2.10-3.55. Same infrastructure, 2-5x the price. Four justifications, examined. Fraud risk is real, but it is 0.05-0.15% of volume. It justifies roughly 0.10%, not 0.30%, and certainly not 2%. Infrastructure was a real cost in 1975. Those authorization systems are depreciated. Marginal cost per transaction is near zero. Bank account maintenance runs €2-10 per customer per year, while US interchange on €10,000 of annual card spend extracts $150-300. Credit risk and float is defensible for credit cards, where banks already charge 15-25% APR for the same risk. It is indefensible for debit, where no credit is extended, no float exists, and interchange applies anyway. Rewards is circular reasoning. Banks charge merchants to fund programmes that make cards attractive, then cite the programmes as the reason for the charge. Premium cards cost merchants the most precisely because they pay customers the most. What actually explains fees running 5-20x cost is network lock-in. Cards became mandatory, alternatives did not exist, and pricing moved to what the market would bear. Then the correction. Europe's 2015 regulation capped consumer interchange at 0.2% debit and 0.3% credit, down from 0.8-1.2%, saving merchants €1.5 billion annually. The US Durbin Amendment capped debit for banks over $10 billion and left credit untouched. Australia started in 2003 and has twenty years of data showing lower interchange does not kill card payments, it just ends their economic advantage. Regulation is no longer the main story. Five structural forces are compressing interchange everywhere: A2A payments at 0.5% flat give merchants a real alternative; regulatory momentum runs one direction only; merchants on thin margins have found leverage and stopped being price-takers; instant payment infrastructure (SEPA Instant, FedNow, Faster Payments, PIX, UPI) removed the last technical reason cards were the only instant option; and 70%+ mobile banking adoption removed the consumer barrier that existed in 2010. The bank strategy split, with the arithmetic. A regional bank earns €1M a year in interchange from 500 merchants. It defends the fee, loses 10% of those merchants to a competitor offering A2A, and preserves €100K of interchange while losing €300K in business banking and €400K in lending. €800K destroyed to protect €100K. The bank that enables A2A at 0.6% instead takes a 15% hit to payment revenue, retains every merchant, attracts 50 more, and is up 10% overall inside 18 months. Defending interchange is profitable quarterly and disastrous strategically. Also covered: why small merchants subsidise large ones for identical infrastructure, what happens to acquirers and PSPs when the interchange-plus model stops working, and the 10-year outlook to an equilibrium 40-60% below today where interchange still exists but reflects cost plus a reasonable margin rather than pricing power. For anyone in payments who has been told that interchange is simply how the industry works. Full source material and the complete breakdown: https://go.payware.eu/p-interchange-101-f Produced by payware - the transaction resolution network for instant A2A payments. AI-generated from payware's published research and documentation.

  6. Jul 19 ·  Bonus

    Understanding Interchange Fees: Why They Exist and Why They're Declining - The Briefing | On The Wire

    A merchant runs €10 million through cards and pays €100,000 in fees. They ask their processor where the money went. The answer is one word: interchange. Interchange is the fee the merchant's bank pays the customer's bank on every card transaction. It has been justified the same four ways since the 1970s: fraud risk, infrastructure investment, credit risk, and customer rewards. Each one fails on arithmetic. Fraud losses run 0.05-0.15% of volume. Regulated European interchange is 0.20-0.30%. Unregulated US interchange is 1.5-3.0%. Fraud coverage justifies about 0.10%. Card authorization systems were built decades ago and are long depreciated, and the marginal cost of one more transaction is near zero. Debit cards extend no credit and carry no float, and they still carry interchange. That leaves rewards, which is circular. Merchants pay 3% so banks can hand customers 2% back and keep the difference. The merchant funds a loyalty programme they do not run and cannot opt out of. The real explanation is market power. When 80% of transactions run on cards and a merchant cannot refuse them without losing the sale, price stops tracking cost. Europe capped interchange in 2015 at 0.2% debit and 0.3% credit. That cut the component 60-75% and saved merchants over €1.5 billion a year. The US left credit cards alone. American merchants now pay 2-5x European rates for identical infrastructure. The part most merchants miss: small merchants pay 1.8-2.8% in total fees while large merchants negotiate 0.8-1.3%. The interchange component is the same for both. The markup is not. A small retailer subsidises Amazon. Full episode for the regulation history, the five structural forces compressing interchange whether regulators act or not, the bank strategy split with the numbers behind it, and the 10-year outlook. Full source material and the complete breakdown: https://go.payware.eu/p-interchange-101-b Produced by payware - the transaction resolution network for instant A2A payments. AI-generated from payware's published research and documentation.

  7. May 31

    Merchant Integration: From Zero to Live in 2-4 Weeks - Full Episode | On The Wire

    Merchant evaluations of A2A keep stalling on the same misconception: that adding it is a multi-month engineering project comparable to standing up a card acquiring relationship from scratch. It is not. This full episode walks through what A2A integration actually looks like, by merchant type, with realistic timelines and the cost math. Three integration paths. Path one, e-commerce plugin. WooCommerce, Magento, PrestaShop, Shopify - install from marketplace, enter API credentials, configure the button, test in sandbox, go live. 1-2 hours end to end. Skill requirement: basic. Cost: zero to €200/month for premium tiers. Path two, API integration for custom checkouts. Implement the payment initiation endpoint, handle status webhooks, drop the A2A button into checkout, test in sandbox, switch credentials. 40-80 hours of developer time. €2K-4K at €50/hour. Full UI/UX control. The path most subscription and custom-cart merchants take. Path three, POS integration. Confirm the POS supports A2A (Square, Lightspeed, Toast and most major systems do), install the module, configure, train staff, soft launch. 2-3 weeks, but most of that is human change management - registers, scripts, customer education at the counter. Cost: €300-1,400 in year one. Skill requirement: minimal. Three operational realities most merchants get wrong before they integrate. PCI compliance. A2A does not transmit, process, or store card data. PCI DSS scope does not apply. That removes €1-10K of annual compliance cost and a security surface. Cards plus A2A, not cards or A2A. A2A complements, does not replace. Mature adoption typically lands at 30-50% of transactions. Offer both. Some customers want cards for rewards or habit; others want bank-direct for cost or speed. Failure modes. Customer cancels: order stays pending, no charge, no harm. Timeout at 10 minutes: payment expires automatically, customer retries. Technical failures: under 0.5% in mature infrastructure. Early-month completion runs 60-70%, climbs to 75-85% as customers familiarise. Adoption goes 2-5% month one, 8-12% month three, 20-30% by month twelve. Two examples with the math. A WooCommerce fashion retailer on €3M revenue: 2.5-hour install, 18% adoption in six months, €4,320 saved against €0 in implementation cost. A 160x return on the install time. A SaaS subscription business on €8M ARR: 60-hour custom API integration, 42% of subscribers switched to bank-direct billing, €20K saved annually, 15% reduction in involuntary churn. A complete pre-launch, during-launch, and post-launch checklist. The next-step decision tree by merchant type. And the answer to the customisation question (plugin: moderate, API: full, POS: limited). For merchants in e-commerce, retail, restaurants, SaaS and any custom-built checkout evaluating whether A2A integration is worth the time. The honest answer: for most merchants, the time is hours to weeks, and the ROI window is days to months. Full source material and the complete guide: https://go.payware.eu/p-merchant-int-f Produced by payware - the transaction resolution network for instant A2A payments. AI-generated from payware's published research and documentation.

  8. May 31 ·  Bonus

    Merchant Integration: From Zero to Live in 2-4 Weeks - The Briefing | On The Wire

    An e-commerce retailer doing €5M a year pays €65K in card fees. They want to add A2A. They budget a six-month integration project. They are off by an order of magnitude. For most merchants, A2A integration is hours to weeks, not months. WooCommerce, Magento, PrestaShop, Shopify - install the plugin, configure, test, go live. Two hours. Custom checkouts on a properly staffed API integration: one to two weeks of developer time, €2-4K. Point-of-sale systems: two to three weeks, and most of that is staff training, not engineering. This briefing walks the three integration paths, what each actually involves, and why the PCI question changes the cost picture. A2A does not touch card data - no card number, no CVV, no expiration. PCI DSS scope does not apply. That removes €1-10K of annual compliance overhead for most merchants and a non-trivial security surface on top of it. The savings show up immediately. A fashion retailer on WooCommerce hit 18% adoption in six months and saved €4,320 against a 2.5-hour install - a 160x return on the implementation time. A SaaS company on a custom API integration saved €20K a year and cut involuntary churn by 15%, because bank accounts do not expire the way cards do. Full episode for failure-mode handling, the customer-learning curve by month, the full pre-launch and post-launch checklist, and what to do when your platform does not have a plugin yet. Full source material and the complete guide: https://go.payware.eu/p-merchant-int-b Produced by payware - the transaction resolution network for instant A2A payments. AI-generated from payware's published research and documentation.

See All (30)

About

The payments industry is at an inflection point. Card networks still consume 2-3% of every transaction. Settlement takes days. Banks earn little while card schemes capture the value. It doesn't have to work this way. On The Wire explores the shift to account-to-account payments - where banks query a resolution network, funds move directly between accounts, and fees drop to 0.5%. For payment institution executives, ISV partners, and merchants rethinking the cost of commerce. Produced by payware - the transaction resolution network for instant A2A payments.

Information

  • Creator
    payware
  • Years Active
    2026
  • Episodes
    30
  • Rating
    Clean
  • Copyright
    © payware
  • Show Website
    On The Wire