GuideJuly 2026 · 7 min read

Payabl Chargebacks: A Merchant Guide (2026)

Payabl — previously known as Paynetics before rebranding — is a European fintech acquirer licensed in both the EU and UK, with a specific strength in travel, forex, and regulated industries. What sets Payabl apart is that it issues its own prepaid cards, giving it visibility into disputes from both the merchant side and the card issuer side, a perspective most acquirers don't have. This guide covers Payabl's standard Visa/Mastercard dispute process and the European context — including 3D Secure and PSD2 SCA — that shapes it.

Key facts

  • Fee: **not publicly disclosed**, contract-based
  • Deadline: standard card network windows, managed via the **Payabl merchant portal**
  • Payabl issues its **own prepaid cards**, giving unique visibility into disputes from both the merchant and card-issuer side
  • Licensed in both the **EU and UK**
  • **PSD2 SCA (Strong Customer Authentication)** compliance affects fraud dispute likelihood for European transactions
  • Common merchant base: European travel, forex, and regulated fintech

How Chargebacks Work on Payabl

Payabl — rebranded from Paynetics — is a European fintech acquirer with dual licensing across the EU and UK, positioning it well for merchants who need regulated payment infrastructure across both markets without maintaining separate relationships. Its dispute process follows standard Visa/Mastercard rules, with cases managed through the **Payabl merchant portal** showing the reason code, disputed amount, and deadline.

What genuinely differentiates Payabl from most acquirers is that it **issues its own prepaid cards**. Most payment processors only ever see disputes from the merchant-acquiring side of a transaction — they never see how the issuing side of a dispute actually gets evaluated. Because Payabl also operates as a card issuer for its prepaid card products, it has direct visibility into how disputes are assessed from that side too, which can inform more nuanced guidance to merchants about what issuing banks are actually looking for in dispute evidence.

Given Payabl's European base and strong compliance posture, most Payabl merchants are already operating within **PSD2's Strong Customer Authentication (SCA)** requirements — mandatory 3D Secure-style authentication for most European card-not-present transactions. This has a direct effect on dispute rates: correctly authenticated transactions under SCA generally shift fraud liability toward the issuing bank rather than the merchant, meaningfully reducing fraud-related chargeback exposure for compliant merchants.

Payabl Response Deadline

Payabl follows standard card network deadlines — typically 20–45 days depending on the network — managed through the Payabl merchant portal. There's no publicly documented Payabl-specific internal deadline shorter than the network's own window.

Given the European regulatory context, merchants should also be aware that SCA-authenticated transactions may see different dispute outcomes and, in some cases, different practical timelines for resolution given the liability shift that strong authentication provides — though the formal response deadline itself follows the same card network rules regardless of authentication status.

Dealing with this type of dispute right now?

ChargeMate generates a compliant dispute response in 3 minutes — tailored to the exact reason code.

Try free — 3 cases/month →

Payabl Chargeback Fee

Payabl does not publish a standard dispute fee — pricing is contract-based, consistent with its focus on travel, forex, and regulated fintech merchants who typically negotiate individualized terms given the specialized nature of those industries.

Check your specific merchant agreement or contact your Payabl account manager for the fee structure applicable to your account.

Step-by-Step: How to Respond to a Payabl Chargeback

  • **Log into the Payabl merchant portal** and locate the case under Disputes
  • **Read the reason code and confirm the card network's deadline** for that transaction
  • **Check whether the original transaction used 3DS/SCA authentication** — if so, this is strong evidence for fraud disputes given the liability shift
  • **Gather evidence matching the reason code** — authentication data, delivery confirmation, or service records as appropriate
  • **Submit through the merchant portal** before the deadline
  • **For regulated-industry merchants (travel, forex)**, include any required compliance documentation (booking confirmations, account verification records) alongside standard dispute evidence

Most Common Dispute Reasons on Payabl

Payabl's core verticals — European travel, forex, and regulated fintech — shape a dispute pattern distinct from general ecommerce:

  • **Travel disputes** frequently involve deposits, installment payments, and cancellation-policy disagreements, where the gap between booking and service delivery creates room for customer confusion about what was actually authorized
  • **Forex-related disputes** often involve larger transaction amounts and require account verification and KYC documentation as core evidence
  • **Regulated fintech merchants** see disputes tied to service terms and account activity, requiring clear documentation of customer agreement to terms at signup
  • **Fraud disputes are comparatively lower** than a non-SCA-compliant baseline would predict, given Payabl's European merchant base operating under mandatory PSD2 Strong Customer Authentication

What Makes Payabl Chargebacks Unique

The defining quirk is Payabl's **dual role as both acquirer and card issuer** through its own prepaid card products. This gives Payabl a genuinely unusual vantage point on the dispute process — most acquirers only ever see their own side of a case, but Payabl's issuing business means it understands both perspectives, which can translate into more useful guidance for merchants trying to understand what will actually satisfy an issuing bank's evidence requirements.

The second distinguishing factor is the **European regulatory context**, specifically PSD2 SCA. Merchants on Payabl operating with strong 3D Secure authentication benefit from meaningfully reduced fraud dispute exposure compared to merchants in markets without an equivalent mandatory authentication regime — worth confirming your SCA implementation is solid if you're seeing higher-than-expected fraud dispute rates.

Frequently Asked Questions

Was Payabl previously called something else?
Yes. Payabl was previously known as Paynetics before rebranding. Merchants with older contracts may see the Paynetics name on legacy documentation.
How much does Payabl charge for chargebacks?
Payabl does not publish a standard dispute fee — pricing is contract-based, consistent with its focus on travel, forex, and regulated fintech merchants who typically negotiate individualized terms.
What is PSD2 SCA and how does it affect Payabl disputes?
PSD2 Strong Customer Authentication is a European regulatory requirement for authenticating card-not-present transactions, typically via 3D Secure. Correctly authenticated transactions generally shift fraud liability toward the issuing bank, reducing fraud-related chargeback exposure for compliant Payabl merchants.
Does Payabl issue its own cards?
Yes. Payabl issues its own prepaid cards, giving it direct visibility into disputes from both the merchant-acquiring side and the card-issuing side — a perspective most standard acquirers don't have.
Can ChargeMate help with Payabl disputes?
Yes. ChargeMate generates network-compliant rebuttals for Payabl disputes — you provide the reason code and evidence, and ChargeMate produces a response ready to submit through the Payabl merchant portal.

Don't want to handle this yourself?

ChargeMate's team writes and submits dispute responses for you. $10 per case or 20% on wins. No monthly minimum.

ChargeMate

Generate your response in minutes

Upload your evidence — AI writes a network-compliant rebuttal letter for you.

Try free → 3 responses included

Related Reason Codes