Place Every Merchant With a Provider
That Will Actually Say Yesa deal fee of 80–125 EUR, scaled to merchant size, payable only when a provider takes your Merchant into underwriting
Stop shopping a Merchant around on instinct. Score them against every provider's live acceptance rulebook first, then submit only where they fit — without handing over your client relationship to do it. Your Merchant sees one application, not a trail of declines.
Every Speculative Submission Costs You Twice
Once in underwriter goodwill, and again in the client's confidence that you know where they fit.
Know the Answer Before You Ask
Run the Pre-Flight Check on your Merchant's profile and see how they score against every provider's published rulebook at once. Submit where they fit, and skip the rest.
Submit, Wait, Get Declined, Repeat
You place a Merchant with the acquirer you happen to know best, wait a week for a decision made on criteria you could not see, and start again somewhere else. The Merchant watches it happen.
How Payments Marketplace Works for ISOs
Four steps, all from your own portal.
Run the Pre-Flight Check on Your Merchant
Enter their profile the same way a Merchant would — industry, country, settlement currency, monthly volume, ticket size, processing history, the markets and payment methods they need. Payments Marketplace scores it against every published provider rulebook and shows you where they stand, with the reasons.
Decide Who Sees Them, and How Much
Submit to the providers you choose, one at a time. For each deal you decide whether the Merchant arrives anonymised or named — naming them lets a provider judge appetite up front, which is worth doing where you know the desk. Either way, their contact details are never released.
Watch It From One Desk
Every submission you have made, which provider holds it, and what they have done with it — accepted, declined, returned for changes, or still under review — with the full dated chronology on each. A deal returned for changes comes back to you to resubmit, not to your client.
Decisions Land in Your Onboarding Mailbox
Every outcome is answered to an address you nominate, so whoever covers the desk that day sees it. The provider corresponds with you and takes the introduction forward through you. Your relationship with the Merchant is the one thing this platform will not touch.
You Own the Relationship. We Keep It That Way.
The rules below are enforced by the platform, not by policy.
A Provider Cannot Reach Your Merchant Through Us
On a deal you introduce, the Merchant's email address is never shown to the provider and never receives platform mail — not on submission, not on acceptance. It is held as an identity key so the same business is recognised across providers, and nothing more.
Identity Is a Decision You Make Per Deal
Anonymised is the default: the provider sees the risk profile and the verified website findings, and nothing that identifies the business. Name them instead where the provider already knows them, or where the brand is the reason they will board.
No Duplicate Submissions, By Design
A Merchant can hold only one open application with any given provider, and a decision is final until that provider reopens it. That protects your standing with the underwriting desk — and it holds whoever submits, so the same business cannot arrive twice from two directions.
One Deal Fee, Scaled to Merchant Size
You pay only when a provider accepts your Merchant into underwriting — not when they go live, and never on a submission that is declined, returned or still under review. The fee is fixed by the Merchant's declared monthly processing volume, so the size of the placement carries the fee, not the looking around.
| Merchant monthly volume (EUR equivalent) | Deal fee per accepted deal |
|---|---|
| 0 – 5,000 | 80 EUR |
| 5,000 – 25,000 | 95 EUR |
| 25,000 – 100,000 | 110 EUR |
| 100,000+ | 125 EUR |
Declared volumes are converted from the Merchant's settlement currency at indicative rates, so a band means the same size of business whatever the currency. The band is read and the fee fixed at the moment you submit, so a later change to this schedule never reprices a placement you have already made.
The Provider Is Not Billed Twice
You already have revenue-share terms with the providers you place into. Charging them a lead fee on top would mean paying twice for one introduction, so on a deal you introduce the fee sits with you and the provider is not billed at all. Their desk shows the deal marked as billed to the ISO.
Embed Pre-Vetting into Your Brokerage Workflow
Whether you work out of the ISO portal or manage thousands of merchant accounts in your proprietary CRM, Payments Marketplace provides full API access and webhook events to automate pre-flight scoring, deal submissions, and decision tracking.
Your platform. Your brand. Powered by the Payments Marketplace Engine.
Embed the Payments Marketplace Engine natively into your platform, portals, and workflows via our comprehensive API suite. Deliver a seamless, fully branded onboarding journey under your own domain.
Programmatic Submissions and Real-Time Status Webhooks
Score deals in bulk and route submissions directly from your client onboarding tools. Receive signed webhook notifications as acquirers update deal status, request KYC amendments, or issue formal approvals.
// 200 OK — deal submitted to provider { "deal_ref": "PV-89X21", "provider_id": "psp_apex_pay", "mode": "anonymised", "score": 94, "status": "under_review", "submitted_at": "2026-08-23T10:15:00Z" }
Frequently Asked Questions for ISOs
Common questions about placements, confidentiality, and fees.
Not through us. On a deal you introduce, the Merchant's contact details are never shown to the provider and never receive mail from the platform — at any stage, including after acceptance. Every decision is answered to the onboarding mailbox you nominate, and the provider's desk carries a note asking them to correspond with you rather than approach the Merchant. What happens outside the platform is a matter for your own agreement with that provider, as it is today.
Yes — to as many providers as you like, and there is no cap on how many submissions you make or how many times you score a Merchant. The website scan behind a Pre-Flight Check is limited to ten per sitting, which only matters if you are placing more than ten Merchants back to back; signing in again clears it. What you cannot do is open a second application with the same provider while one is still with them, or reopen one they have already decided. That rule exists to protect your standing with their underwriting desk, and it applies to everyone equally.
At the point a provider accepts your Merchant into underwriting — that is, when they take the file on and you are introduced. Not on boarding, not on first transaction, and never before. Running the Pre-Flight Check is free and unlimited, and a deal that is declined, returned for changes, or still under review costs nothing. The fee is 80–125 EUR depending on the Merchant's declared monthly volume, fixed at submission, and your portal keeps a running ledger of what has been billed, settled and left outstanding.
Yes, and deliberately so. Your organisation is named on the deal from the moment it arrives — a provider's appetite depends partly on who is introducing, and hiding it would work against you. It is the Merchant's identity that is withheld until you choose to release it or the provider accepts, not yours.
Email connect@payments-marketplace.com and we will set one up for you. There is no self-serve route yet — the sign-up form on this site opens a provider account, which is not what you want. Fees are the published schedule above; there is nothing to negotiate before you start.
Payments Marketplace was founded and developed by David Copper, MSc, a full-stack developer and senior payments consultant, supported by a team of industry specialists. The development journey of this Next-Gen Payments Marketplace started on Friday, 4th October 2024, progressing through key engineering phases to its Public Beta release on 1st August 2026:
| Milestone Date | Release Focus | Key Engineering Deliverables |
|---|---|---|
| 04 Oct 2024 | Project Inception | Foundation, architecture charter, and multi-domain ecosystem setup (opaq.io) |
| Nov 2024 – Mar 2025 | Core Engine & Data | Rust matching engine, 120+ MCC taxonomy, MySQL transactional schemas, and pgvector (PostgreSQL) embeddings |
| Apr 2025 – Jun 2025 | Merchant & AI Scanner | Pre-flight wizard UI and AI website compliance & disclosure scanner |
| Jul 2025 – Sep 2025 | PSP Underwriting Portal | Provider rule customiser, appetite parameters, and anonymised deal flow |
| Oct 2025 – Dec 2025 | Commercials & Alpha | Tiered success fee ledger (€80–€125), APM/crypto rails, and closed alpha |
| Jan 2026 – Mar 2026 | ISO Broker Ecosystem | Multi-tenant ISO portal, commission split ledger, and anonymised mailbox |
| Apr 2026 – Jun 2026 | Security & PSP Sandbox | GDPR privacy verification, sub-50ms query tuning, and Pioneer PSP sandbox |
| 01 Aug 2026 | Public Beta Go-Live | General availability of the Payments Marketplace for Merchants, ISOs, and PSPs |
David's payment platforms have processed many tens of thousands of Merchant applications across the UK, Europe, and the US, providing the real-world experience behind Payments Marketplace's ability to bridge the gap between Merchant readiness and PSP underwriting requirements.