Payline
Provenance unknown Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Monext S.A. · www.payline.com
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
Payline at a glance
- Vendor
- Monext S.A.
- Headquarters
- Not stated on the vendor’s pages as of 17 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 17 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 17 Nov 2026
- Panel verdict
- The AI panel rates Payline 1/5, the mean of 6 judges. Payline is Monext S.A.'s online payment acceptance solution, judged from the captured homepage and repository. how scores are made
- As of
- Vendor pages captured 17 Nov 2026; evaluated by the panel 18 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Payline is Monext S.A.'s online payment acceptance solution, judged from the captured homepage and repository. Its strongest showing is on plainly stated basics: payment methods (Carte Bancaire, Apple Pay, PayPal) drew 3 from five of six judges, and checkout and SCA — a hosted checkout evidenced by a secured homepage demo, a Web Payment Widget and published test cards — drew 2 from the same five. The genuine splits are settlement and reconciliation (two judges at 4, three at 2, one at 0) and sovereignty (0 to 4): the 4s credit a documented API with an OpenAPI specification and SOAP SDKs for PHP, Java and.NET, while the 2s found no public information on payout cadence, reconciliation reports or webhooks; the sovereignty spread turns on how far a French contracting entity — Monext S.A., a French financial services provider located in France — carries the question when data residency, subprocessors and a data processing agreement are unknown. Weakest are recurring billing, scored 0 throughout, and licence and account terms, clustered at 2 with no public information on licence or dispute terms. No rates are published; the only figure is a 39,99€ demo basket.
Speaks for it
- Hosted checkout is evidenced by a secured homepage demo, a Web Payment Widget and published test cards.
- The three accepted payment methods are named outright: Carte Bancaire, Apple Pay and PayPal.
- A broad public integration surface spans an OpenAPI specification, SOAP SDKs for PHP, Java and.NET, mobile SDKs, and plugins for WooCommerce, Magento2, Prestashop and Sylius.
- The vendor states it operates the full payment chain from collection to the transfer into your bank account.
- The contracting entity is named and located: Monext S.A., a French financial services provider in France.
Held against it
- Recurring billing scores 0 throughout, with no public information on stored cards, SEPA mandates, dunning or token portability.
- We found no public information on 3-D Secure handling, SCA exemptions, PCI scope or fraud screening.
- We found no public information on payout schedules, settlement currencies, reconciliation reports, fee itemisation or webhooks.
- We found no public information on the licence type, supervisor or register number, or on dispute handling, safeguarding of merchant funds, reserves or termination terms.
- Beyond the French entity we found no public information on where payment and cardholder data are processed, on subprocessors, or on a data processing agreement.
Best for
- You take one-off card-and-wallet payments — Carte Bancaire, Apple Pay, PayPal — and want a hosted checkout with published test cards to build against.
- Your engineering team wants to integrate from public artefacts: an API reference, an OpenAPI specification and SOAP SDKs for PHP, Java or.NET into stacks such as Magento2, Prestashop or WooCommerce.
- You want a named French contracting entity — Monext S.A., a French financial services provider located in France — as your payments counterparty.
Avoid if
- You run subscriptions or recurring revenue — recurring billing is scored 0 throughout, and the subscription-focused judge gave 0 on all criteria.
- You sell across multiple EU markets and need local methods such as iDEAL or Bancontact — the homepage names exactly three methods, and none of them are local schemes beyond Carte Bancaire.
- Your finance team needs documented payout cadence and reconciliation reporting before committing — the finance-focused judge scored settlement and reconciliation 2, finding no public information on payout schedules or reports.
The scores
| Criterion | Panel median |
|---|---|
| Payment methods & local coverage | 1.5 of 5 |
| Checkout, SCA & fraud | 1 of 5 |
| Settlement, reconciliation & API | 1 of 5 |
| Licence, risk & account terms | 1 of 5 |
| European sovereignty | 1 of 5 |
Payment methods & local coverage
panel disagrees
Show reasoningHide reasoning
How this is scored
Which methods a European customer can actually pay with — cards and wallets, SEPA Direct Debit, and the local methods that decide conversion per country — judged on the named list per market rather than on a method count.
0 — Not a payment acceptance product; customers cannot pay through it.
3 — Card payments with the major schemes, plus wallets such as Apple Pay or Google Pay.
5 — Cards and wallets plus SEPA Direct Debit and several European local methods (for example iDEAL or Wero, Bancontact, Klarna, EPS) listed by name.
8 — Broad EU coverage named per country with the countries and currencies each method serves — including methods such as BLIK, TWINT, Przelewy24, EPS and Wero — multi-currency acceptance with settlement currencies stated, and which methods support refunds and recurring charges documented per method.
10 — Coverage is documented as a matrix a merchant can plan against: every method with its countries, currencies, refund, partial-capture and recurring support, and the provider's own acquiring versus third-party routing stated per method.
The Finance Lead
The homepage names exactly three methods — Carte Bancaire, Apple Pay and PayPal — which is card acceptance plus a wallet, and nothing more. We found no public information on SEPA Direct Debit or on named local methods per country, so this stays at the cards-and-wallets level. 1
The E-Commerce Lead
The homepage names exactly three ways to pay — Carte Bancaire, Apple Pay and PayPal — which is cards plus two wallets and nothing more. For my eight EU markets I need iDEAL, Bancontact, EPS and the rest named per country, and I found no public information on SEPA Direct Debit or any local method beyond the French card scheme. Three named methods is not coverage I can plan conversion against. 1
The SaaS Founder
The homepage names Carte Bancaire, Apple Pay and PayPal — cards plus a wallet — which is the basic card-and-wallet level. For a subscription business the part that matters most is absent from the captures: we found no public information on SEPA Direct Debit or any country-specific method, so I cannot plan European conversion on this. 1
The Payments Engineer
The homepage names exactly three methods — Carte Bancaire, Apple Pay and PayPal — which is cards plus wallets. No SEPA Direct Debit and no European local methods such as iDEAL, Bancontact or Klarna are named, and there is no per-country coverage list to plan a launch against. 1
The Compliance Officer
The homepage names exactly three methods — Carte Bancaire, Apple Pay and PayPal — which is cards plus wallets and nothing more. I found no public information on SEPA Direct Debit, other named local European methods, or per-country coverage and settlement currencies. 1
The Skeptic
The captured homepage names exactly three methods — Carte Bancaire, Apple Pay and PayPal — cards plus two wallets. We found no public information on SEPA Direct Debit or named local European methods, let alone per-country coverage or refund and recurring support per method. 1
Checkout, SCA & fraud
Show reasoningHide reasoning
How this is scored
The path from basket to authorised payment under PSD2: hosted and embedded checkout options, 3-D Secure and SCA exemption handling, fraud screening, and what the provider documents about keeping legitimate payments from failing.
0 — No checkout or payment form; the product does not take a payment to authorisation itself.
3 — A hosted payment page or payment links with 3-D Secure.
5 — Hosted and embedded checkout options, 3-D Secure 2 with SCA handled by the provider, and fraud screening with configurable rules.
8 — SCA exemptions (low value, transaction risk analysis, merchant-initiated) applied and documented, the PCI DSS scope of each integration type stated, fraud tooling with rules and risk scores exposed to the merchant, network tokens or account updater, and liability shift explained per flow.
10 — Authorisation is engineered and shown: exemption strategy documented, soft-decline retry handled, authorisation-rate reporting by method and issuer country, and a checkout the merchant can run in their own domain while staying at the lowest PCI scope.
The Finance Lead
A hosted checkout plainly exists: a Web Payment Widget described as secured, a checkout demonstration on the homepage, and test cards in the documentation. We found no public information on 3-D Secure, SCA exemptions, fraud screening or PCI scope on the captured pages, so the evidence reaches the existence of a hosted checkout but not the hosted-page-with-3D-Secure level. 1 2
The E-Commerce Lead
There is a genuine checkout surface — a web payment widget, native payment sheets in the mobile SDKs, and a checkout demo on the homepage — but I found no public information on 3-D Secure, SCA exemptions or fraud screening on the pages I read. I cannot run my conversion targets on a checkout whose challenge behaviour is undocumented. 1 2
The SaaS Founder
A hosted Web Payment Widget and a checkout described as secured are shown, so the product does take payments to authorisation itself. We found no public information on 3-D Secure, SCA exemptions or fraud screening, and since failed authorisations are churn nobody chose, I cannot credit more than the hosted checkout itself. 1 2
The Payments Engineer
A hosted web payment widget and a checkout the homepage calls secured are documented, with test cards for integration work. We found no public information on 3-D Secure handling, SCA exemptions, fraud screening rules, or the PCI scope of each integration type. 1 2
The Compliance Officer
A hosted checkout is evidenced — the homepage shows a secured checkout demo, a web payment widget is offered, and test cards are published — but I found no public information on 3-D Secure, SCA exemption handling, PCI scope or fraud screening. 1 2
Subscriptions & recurring payments
n/r
n/r
n/r
n/r
n/r
n/r
Show reasoningHide reasoning
How this is scored
Charging the same customer again: card-on-file and merchant-initiated transactions, SEPA mandates, subscription logic and dunning — and whether the stored payment credentials can leave with the merchant.
0 — One-off payments only; the product stores no payment method for a later charge.
3 — Saved cards (card-on-file) charged again for repeat or recurring payments.
5 — Stored cards and SEPA Direct Debit mandates for recurring charges, merchant-initiated transactions, and subscriptions or scheduled payments with notification of failed payments.
8 — Subscription billing with trials, proration and plan changes, smart retries and dunning, card account updater, mandate management with pre-notification, and a documented process for exporting payment tokens to another provider.
10 — Recurring revenue is a first-class product: usage-based and invoice-based billing, dunning with measurable recovery, token migration in and out documented with a stated timeline and format, and recurring support stated for every local method that allows it.
The Finance Lead not rated — no public information
We found no public information on subscriptions, saved cards for later charges, SEPA mandates, retries, dunning or token portability in either of the captured pages, so this criterion is unevidenced. 1 2
The E-Commerce Lead not rated — no public information
I found no public information on recurring billing, stored cards, SEPA mandates or dunning on the captured homepage and repository pages — nothing on them bears on charging the same customer a second time. 1 2
The SaaS Founder not rated — no public information
We found no public information on stored cards, SEPA mandates, subscription logic, dunning, or whether payment tokens can be exported to another provider. For a business like mine that is the whole question — a provider that keeps the tokens keeps the customer base hostage — but the captured homepage and repository pages say nothing either way. 1 2
The Payments Engineer not rated — no public information
We found no public information on saved cards, SEPA mandates, merchant-initiated transactions, subscription logic or dunning in the captured pages — the homepage and the code repository only. 1 2
The Compliance Officer not rated — no public information
I found no public information on recurring payments: the captured homepage and code repository say nothing about saved cards, SEPA mandates, merchant-initiated transactions, subscription logic or dunning. 1 2
Settlement, reconciliation & API
panel disagrees
Show reasoningHide reasoning
How this is scored
Getting the money and knowing what it was: payout cadence and currencies, fee itemisation per transaction, reports that match a bank statement, and an API and webhooks a team can build finance processes on.
0 — No merchant reporting: the product is a payment button or link with no dashboard, report or API.
3 — A dashboard of transactions and payouts, a stated payout schedule, and CSV export.
5 — The payout schedule stated, reports or exports that link each payout to its transactions and fees, and a documented API with webhooks and a test mode.
8 — Configurable payout schedules and settlement currencies, reconciliation reports that match bank lines, accounting integrations or exports named, a versioned API with idempotency and published rate limits, and a public status page with incident history.
10 — Finance can close the month from the provider's data: interchange and scheme fees itemised per transaction, automated reconciliation to the ledger, a deprecation policy for the API, and full historical data exportable after the contract ends.
The Finance Lead
The vendor states it operates the entire chain from collection to transfer of funds to the merchant's bank account, and API documentation with SDKs for several languages and test cards is published. No payout schedule, transaction report, export format or webhook documentation appears on the captured pages, and for a finance buyer those specifics are the substance of this question. 1 2
The E-Commerce Lead
The pages state the whole chain is operated from payment collection through to a payout into my bank account, and API documentation with test cards exists — but I found no public information on payout schedule, reports linking payouts to transactions and fees, or webhooks. Finance would get money in the bank with no documented way to reconcile it. 1 2
The SaaS Founder
API documentation and an OpenAPI specification exist, test cards imply a test mode, and the vendor says it operates the chain from collection through to the transfer into your bank account. We found no public information on payout cadence, fee reporting, webhooks or reconciliation, so finance cannot close a month from what is captured. 1 2
The Payments Engineer
There is a documented API with an OpenAPI specification, SDKs for PHP, Java and.NET, and test cards, and the vendor describes operating the chain from collection to transfer to the merchant's bank account. But no payout schedule, webhook or reconciliation reporting appears on the pages we read, and I cannot build a finance process on what is not documented. 1 2
The Compliance Officer
The vendor states it operates the full chain from collection to transfer into the merchant's bank account, and API documentation, an OpenAPI specification and test cards are published. I found no public information on payout cadence, settlement currencies, transaction reports, reconciliation or webhooks. 1 2
The Skeptic
They say they operate the chain from collection to the transfer into your bank account, and API documentation, an API reference and test cards are published — but no payout delay is stated anywhere. We found no public information on payout schedules, reconciliation reports, fee itemisation or webhooks. 1 2
Licence, risk & account terms
Show reasoningHide reasoning
How this is scored
Who holds the merchant's money under which licence, and what the contract lets the provider do on a bad day: freezes, reserves, termination, chargebacks. Scored on what the terms and the imprint state, not on reputation.
0 — The terms let the provider freeze funds or close the account at any time with no notice, reason or timeline.
3 — The regulated entity or the licensed partner behind the payments named, and a chargeback or dispute process described.
5 — The regulated entity named with its supervisor or licence type, the dispute process and chargeback fee published, and either safeguarding of merchant funds or a notice period for ordinary termination stated.
8 — Entity, supervisor, register number and passporting stated per country; safeguarding stated; reserve and rolling-hold conditions defined with limits and release timelines; freeze and termination terms with reasons and a route to appeal; PCI DSS level and attestation published.
10 — The bad day is written down: every regulated entity in the chain named with register links, reserve calculation disclosed, funds release timelines after termination committed, a documented complaint route to the supervisor, and exit terms that include handing back payment tokens and transaction history.
The Finance Lead
Monext S.A. is named and described as a French financial services provider located in France, so the entity behind the payments is identifiable. We found no public information on its licence type or supervisor, on any dispute or chargeback process, on reserves, freezes or termination terms in the captured material. 2
The E-Commerce Lead
Monext is named as a French financial services provider located in France, so there is a European entity behind the money. I found no public information on licence type or supervisor, dispute process and chargeback fees, safeguarding, reserves or termination terms on the captured pages. 2
The SaaS Founder
The entity behind the payments is named: Monext S.A., described as a French financial services provider located in France. We found no public information on its licence or supervisor, a dispute or chargeback process, safeguarding of merchant funds, or freeze and termination terms — the bad-day questions that decide whether my revenue is hostage. 2
The Payments Engineer
The captured pages identify Monext as a French financial services provider located in France, which names the entity behind the payments. We found no public information on the licence type or supervisor, any chargeback or dispute process, safeguarding of merchant funds, reserves, or termination and freeze terms. 2
The Compliance Officer
The provider identifies itself as Monext, a French financial services provider located in France, but the captured pages give no supervisor, licence type or register number for the regulated entity. I found no public information on dispute handling, safeguarding of merchant funds, reserves or termination terms. 2
The Skeptic
The captures name Monext S.A., described as a French financial services provider located in France — an entity, yes, but I look for the licence and register number and its supervisor and find neither. We found no public information on the dispute process, chargeback fees, safeguarding, reserves or termination and freeze terms on the pages read. 2
European sovereignty
panel opinion
panel disagrees
Show reasoningHide reasoning
How this is scored
Who the contracting and regulated entity is, and where transaction and cardholder data are processed and stored. Independently sourced by the sovereignty pipeline. The card schemes are US-based for every provider, so the scheme layer is not held against any one vendor; the part the vendor controls is.
0 — Contracting entity and processing of payment data both shown to be outside the EU, with no transfer safeguard stated.
3 — A named contracting entity and a privacy policy or data processing agreement; the processing location of payment data not stated or partly outside the EU.
5 — An EU contracting or regulated entity, with EU processing of core payment data stated or a subprocessor list published, and a data processing agreement offered.
8 — EU entity and EU licence, payment and cardholder data processed and stored in the EU on named infrastructure, subprocessor list published with locations, and a DPA covering the processing the provider does as processor versus as controller.
10 — Sovereign end to end and evidenced: European ownership, EU entity and licence, every processing location and subprocessor European, European rails (SEPA, Wero or national schemes) offered alongside cards, and certifications published.
The Finance Lead
The only proven fact here is domicile: a contracting entity that is French and located in France. We found no public information on where payment or cardholder data is processed, on a data processing agreement, on subprocessors or their locations, so the European position rests on the entity's nationality alone and nothing further. 2
The E-Commerce Lead
The contracting entity is proven French, which is a real start for an EU merchant. Everything downstream — where payment and cardholder data are processed and stored, subprocessors, or a data processing agreement — is not stated on the pages I read. 2
The SaaS Founder
Monext S.A. is named as the contracting entity and located in France, and described as a French financial services provider, which is worth something. The rest — where payment and cardholder data are processed, the subprocessor list, a data processing agreement — is unknown rather than non-European, so I can only credit the French entity itself. 2
The Payments Engineer
The contracting side is proven French — a French financial services provider based in France. The captured pages state nothing about where payment or cardholder data is processed or stored, publish no subprocessor list, and we found no public information on a data processing agreement. 2
The Compliance Officer
The contracting entity is presented as French, which is a start, but I found no public information on where transaction and cardholder data are processed or stored, on a subprocessor list, or on a data processing agreement distinguishing processor from controller roles. 1 2
The Skeptic
The contracting entity is shown as French — Monext S.A., a French financial services provider in France — which puts the entity dimension in Europe. We found no public information on where payment and cardholder data are processed, on a data processing agreement, or on subprocessors and their locations. 2
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide reasoning
How this is scored
Whether a merchant can compute the effective fee for their own mix of cards, countries and methods — including cross-border and currency conversion markups, chargebacks, refunds, payouts and monthly fees — from public pages alone.
0 — No public prices at all; every rate is a sales conversation.
3 — A headline rate published for one method or card type, or a "from" percentage.
5 — Rates published per main method with domestic and international cards distinguished, and any monthly or plan fee stated with its billing period; ancillary fees (currency conversion, chargeback, payout) may still be missing or "on request".
8 — Every method priced publicly, cross-border and currency conversion markups stated, chargeback, refund and payout fees listed, minimum monthly fees and contract term given, and whether the model is blended or interchange++ said plainly.
10 — Complete fee computability: the effective rate derivable for a given volume, card mix and country mix — interchange++ with the markup published or a blended rate with every exception listed — plus volume tiers, reserves and every ancillary fee on a public page.
The Finance Lead not rated — no public information
We found no public pricing on the captured pages — no rates, plan fees, conversion fees or chargeback fees of any kind. The only figure shown is a 39,99€ example amount in the checkout demonstration on the homepage, which is a sample purchase price rather than a price for the service, so this criterion is unevidenced. 1 2
The E-Commerce Lead
The only price-like figure on the captured pages is a 39,99 € demo basket in the homepage checkout example — a customer amount, not a merchant rate. I found no published rates for any method, no monthly fee and nothing on chargeback or payout fees, so an effective fee cannot be computed from what is public. 1 2
The SaaS Founder not rated — no public information
We found no public information on merchant fees across both captured pages — the only figure is a 39,99€ example amount in the homepage checkout demo, which is a shopper display, not a rate a merchant could plan with. 1 2
The Payments Engineer not rated — no public information
We found no public information on merchant pricing in the captured pages — the only price figure anywhere is a 39,99€ demo basket shown in the homepage checkout recap, which is a shopper amount, not a rate. 1 2
The Compliance Officer not rated — no public information
I found no public information on pricing: the only figure on the captured pages is a 39.99 euro example basket in the homepage checkout demo, which is not a merchant-facing rate. No headline rate, per-method fee or monthly plan is documented in the captured material. 1 2
European sovereignty — proven facts
0 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined | — | uncited Report an error |
|---|---|---|---|
| Hosting location | Not determined | — | uncited Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Payline
Is Payline European?
Not determined: the vendor’s pages as captured do not say where Payline is based.
Where does Payline store data?
Not stated on the vendor’s pages as of 17 Nov 2026.
Does Payline have a free plan?
Not stated on the vendor’s pages as of 17 Nov 2026.
What are the best alternatives to Payline?
As of 18 Nov 2026, the panel rates Novalnet (3.5/5), PayPal (3.5/5) and Mollie (3/5) highest among the other 45 Payment products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Novalnet (EU-Made, Germany). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Payline alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 17 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- We could not confirm any compliance information on the vendor’s own pages as captured, so this page shows none rather than a statement we cannot stand behind. Know more? Tell us
- 5 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
Sources (2)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page www.payline.com Checked 17 Nov 2026 Details →
- 2 Code repository (open-source licence) — found from the homepage github.com Checked 17 Nov 2026 Details →