Hosted
Launch a custom payments proposition on your own domain.
- Suited to
- Teams that want to launch without building every interface from zero.
- Operating position
- PayFacLite® operates the regulated foundation.
One operating foundation.Models that fit the business.
Choose how the customer experience is delivered, then how the programme beneath it is operated. The four arrangements stay distinct, but they sit on the same PayFacLite® foundation.
One consistent structure.Four ways to operate.
Hosted and Embedded define the customer-facing delivery route. PayFac and Acquirer define the licensed operating position beneath it. Compare all four in the same order used across the site.
Operated infrastructure
Embedded
Build the payments experience into your own product.
- Suited to
- Teams seeking complete control of product and architecture.
- Operating position
- PayFacLite® operates the regulated foundation.
Licensed infrastructure
PayFac
Run an agreed acquiring programme on licensed infrastructure.
- Suited to
- Payment organisations with an acquiring strategy or relationship.
- Operating position
- Operate within an agreed programme structure.
Acquirer
Operate the full platform on licensed infrastructure under your own permissions.
- Suited to
- Appropriately regulated organisations seeking greater control.
- Operating position
- Your organisation operates under its own regulatory permissions.
The right arrangement depends on the proposition, customer relationship, permissions and operating responsibilities you intend to hold. Licensing infrastructure does not itself confer regulated status.
Trust CentreCompare the arrangements in detail.
Use the same four-column structure to compare customer experience, control, programme design, integration and regulated responsibility.
| Operated infrastructure | Licensed infrastructure | |||
| Platform model | HostedExplore Hosted | EmbeddedExplore Embedded | PayFacExplore PayFac | AcquirerExplore Acquirer |
|---|---|---|---|---|
| What it defines | How the payments experience is delivered in your product. | How the payments experience is delivered in your product. | The programme and operating arrangement beneath the proposition. | The programme and operating arrangement beneath the proposition. |
| Customer experience | A PayFacLite®-hosted experience configured around your brand, domain and proposition. | Built into your own product, against the same contract. | Set by the delivery route chosen for the programme. | Set by the delivery route chosen for the programme. |
| Customer / merchant relationship | Yours to hold and grow, within the agreed structure. | Yours to hold and grow, within the agreed structure. | Yours to hold and grow, within the agreed programme structure. | Yours to hold and grow, under your own permissions. |
| Product and platform control | Brand, journeys and roadmap | The complete product architecture | Configuration, estate and operations | Product, operation and commercial model |
| Commercial participation | Agreed in the commercial arrangement for the programme. | Agreed in the commercial arrangement for the programme. | Agreed in the programme’s commercial structure. | Set by your organisation within its own structure. |
| Programme structure | PayFacLite®, acquirer-direct | PayFacLite®, acquirer-direct | Agreed acquiring programme | Regulated organisation’s approved structure |
| Regulated responsibilities | The regulated entity beneath PayFacLite® | The regulated entity beneath PayFacLite® | Programme-defined | Regulated organisation under its permissions |
| Integration route | Pre-integrated; extended through the same contract. | APIs, SDKs, webhooks, sandbox and approved integration tooling. | The platform connected to an agreed acquiring environment. | The licensed platform, integrated with your acquiring or programme structure. |
| Likely fit | Teams that want to launch without building every interface from zero. | Teams seeking complete control of product and architecture. | Payment organisations with an acquiring strategy or relationship. | Appropriately regulated organisations seeking greater control. |
Platform model
Operated infrastructure
Hosted
Explore Hosted- What it defines
- How the payments experience is delivered in your product.
- Customer experience
- A PayFacLite®-hosted experience configured around your brand, domain and proposition.
- Customer / merchant relationship
- Yours to hold and grow, within the agreed structure.
- Product and platform control
- Brand, journeys and roadmap
- Commercial participation
- Agreed in the commercial arrangement for the programme.
- Programme structure
- PayFacLite®, acquirer-direct
- Regulated responsibilities
- The regulated entity beneath PayFacLite®
- Integration route
- Pre-integrated; extended through the same contract.
- Likely fit
- Teams that want to launch without building every interface from zero.
Operated infrastructure
Embedded
Explore Embedded- What it defines
- How the payments experience is delivered in your product.
- Customer experience
- Built into your own product, against the same contract.
- Customer / merchant relationship
- Yours to hold and grow, within the agreed structure.
- Product and platform control
- The complete product architecture
- Commercial participation
- Agreed in the commercial arrangement for the programme.
- Programme structure
- PayFacLite®, acquirer-direct
- Regulated responsibilities
- The regulated entity beneath PayFacLite®
- Integration route
- APIs, SDKs, webhooks, sandbox and approved integration tooling.
- Likely fit
- Teams seeking complete control of product and architecture.
Licensed infrastructure
PayFac
Explore PayFac- What it defines
- The programme and operating arrangement beneath the proposition.
- Customer experience
- Set by the delivery route chosen for the programme.
- Customer / merchant relationship
- Yours to hold and grow, within the agreed programme structure.
- Product and platform control
- Configuration, estate and operations
- Commercial participation
- Agreed in the programme’s commercial structure.
- Programme structure
- Agreed acquiring programme
- Regulated responsibilities
- Programme-defined
- Integration route
- The platform connected to an agreed acquiring environment.
- Likely fit
- Payment organisations with an acquiring strategy or relationship.
Licensed infrastructure
Acquirer
Explore Acquirer- What it defines
- The programme and operating arrangement beneath the proposition.
- Customer experience
- Set by the delivery route chosen for the programme.
- Customer / merchant relationship
- Yours to hold and grow, under your own permissions.
- Product and platform control
- Product, operation and commercial model
- Commercial participation
- Set by your organisation within its own structure.
- Programme structure
- Regulated organisation’s approved structure
- Regulated responsibilities
- Regulated organisation under its permissions
- Integration route
- The licensed platform, integrated with your acquiring or programme structure.
- Likely fit
- Appropriately regulated organisations seeking greater control.
Acquiring infrastructure for international platforms.
Build and operate across the UK, Europe and the United States from a single governed PayFacLite® operating foundation.
United Kingdom
Regulated acquiring foundation
Europe
Infrastructure for multi-market propositions
United States
Infrastructure for international growth
Market availability depends on programme structure, product scope and applicable regulatory requirements.
- Verofy Ltd (trading as Verofy® Acquiring) — FCA Authorised Payment Institution
- PCI DSS Level 1
- Safeguarding in line with regulatory requirements
- United Kingdom
What will you build?
Keep control of the customer relationship, shape a proposition that’s yours, and create more value in your business. We’ll help map the right operating model.
A clear view of your platform route.
- Your proposition
- Who it serves and what it offers.
- The operating model
- Where the regulatory boundary sits.
- Delivery and integration
- How your team connects and goes live.