How it works
The structure works because EU acquirers underwrite the contracting party's domicile, not the underlying business. Putting an EU entity on the application is what unlocks them — even when your real operations sit in St. Lucia, the UAE, or BVI. The agent (typically Cyprus) takes payments from the PSPs and transfers funds to your operational entity under a payment agent agreement.
Your operational entity — whether it's in St. Lucia, UAE, Mauritius, or BVI — remains the business. It runs the product, serves the customers, and employs the team. The payment agent exists for one reason: to give EU PSPs an EU-based contracting party they'll onboard.
Why EU PSPs require it
EU acquirers underwrite based on the contracting entity, not just the merchant story. A compelling business with clean compliance and strong volume projections still gets rejected if the entity on the application is domiciled in an offshore jurisdiction. The acquiring bank's risk policy requires an EU entity — end of conversation.
Without an EU presence, you're limited to offshore acquiring. That means non-EU acquirers routing your EU card transactions cross-border, which produces lower approval rates, higher interchange costs, and ongoing risk of the PSP offboarding you when they tighten their risk appetite. Closing this gap is the practical heart of high risk payment processing — the right entity behind the right PSP, in the right region.
The fund flow
- Customer pays via PSP → funds land in the payment agent entity's merchant account
- Payment agent agreement governs the relationship between the EU entity and the operational entity
- Agent transfers funds to the operational entity per the terms of the agreement
- Operational entity receives funds and runs the business
The payment agent agreement is the legal instrument that makes this work. It defines the scope — the agent collects payments on behalf of the principal — and the transfer terms. PSPs and their acquiring banks are familiar with this structure. It's not a workaround. It's the standard, recognized model for non-EU operators processing EU payments.
Why Cyprus
Cyprus is the default jurisdiction for payment agent entities because EU acquirers and PSPs have seen it many times. The incorporation process is straightforward, the corporate infrastructure is mature, and the jurisdiction is well-understood by compliance teams at Tier 1 processors. Other EU jurisdictions work in theory, but Cyprus has the deepest track record for this specific structure.
When you need one
- Your operational entity is offshore (St. Lucia, UAE, Mauritius, BVI, Seychelles) and your customers are in the EU
- Tier 1 EU PSPs are rejecting your applications because of your entity's domicile
- You're processing EU card transactions through offshore acquiring and approval rates are suffering
- You want to access local EU acquiring with proper BINs and issuer relationships
If your operations and customers are both outside the EU, you don't need a payment agent. The structure solves a specific mismatch: offshore entity, EU customers, EU PSPs that won't onboard non-EU entities. This is one of the foundational moves in high risk payment processing — particularly relevant for prop firms and CFD brokers running offshore operations with EU customer bases.
Key Takeaways
- A payment agent is an EU entity that contracts with PSPs on behalf of an offshore operator.
- EU PSPs underwrite based on the contracting entity's domicile — offshore entities get rejected.
- Funds flow from PSPs to the agent entity, then to the operational entity via a payment agent agreement.
- Cyprus is the standard jurisdiction — acquirers know the structure.
- You need one when your operations are offshore but your customers are in the EU.