Frequently asked questions.
Direct answers.
How the models work, who holds each responsibility, how integration is delivered and what it takes to launch.
The model
What the model is, and who holds what.
Is PayFacLite® white label?
No. White label is a finished product with your branding on the surface. PayFacLite® is the infrastructure beneath a product that is yours, supplied as application source or built against the contract.
Who is the regulated entity when PayFacLite® operates the foundation?
Verofy® Acquiring, the regulated entity beneath PayFacLite®. It holds the acquiring and regulated merchant relationships in that arrangement, whether the customer experience is Hosted or Embedded. PayFacLite® is the brand and platform, not the regulated entity.
Can a non-regulated company use the model?
Yes, under an agreed PayFacLite®-operated arrangement. You control the proposition while PayFacLite® operates the platform. The regulated entity beneath PayFacLite® holds the acquiring and regulated merchant relationships. Hosted or Embedded delivery alone does not set the regulatory position.
What does the partner control?
The product, brand, UX and journeys, packaging and pricing within agreed parameters, distribution, communication and the support experience. The Trust Centre sets out the responsibility model activity by activity, and says where an allocation depends on the programme.
Who makes the risk decisions?
The regulated entity beneath PayFacLite®, when PayFacLite® operates the agreed acquiring foundation. Underwriting, KYC, KYB and AML, ongoing monitoring and ultimate risk approval remain with that regulated entity. In a PayFac or Acquirer arrangement, risk ownership follows the agreed programme or the organisation’s own permissions, whether the experience is Hosted or Embedded.
What is acquirer-direct?
One direct commercial and operating relationship with PayFacLite®, the layer that operates acquiring, instead of a gateway, a processor and an acquirer assembled separately. Scheme and technical dependencies sit inside that one relationship.
Models and arrangements
Two connected choices, not four products.
Which operating model applies?
There are two connected layers rather than four separate products. Hosted and Embedded define the customer-facing experience. Either can be used with a PayFac or Acquirer arrangement; the programme determines operating and regulated responsibilities.
Can Hosted or Embedded be combined with a PayFac or Acquirer arrangement?
Yes. Both Hosted and Embedded can be used with either a PayFac or Acquirer arrangement, subject to the agreed programme, permissions and responsibilities. A PayFacLite-operated foundation is also available where appropriate.
Who hosts a Hosted experience?
You can host it on your own infrastructure or use PayFacLite®-managed hosting on your domain. Domain configuration, security, maintenance and support responsibilities are agreed before launch.
What is the difference between a PSP, a PayFac and an Acquirer?
Payment service provider is a broad description of an organisation providing payment services, and it settles nothing about that organisation’s permissions. Payment facilitator is a specific programme and operating structure agreed under an acquiring relationship. An acquirer is an organisation operating under its own acquiring permissions. Two organisations using the same label may hold very different permissions.
Does licensing PayFacLite® make us regulated or give us acquiring permissions?
No. Licensing technology does not confer regulated status, regulatory permissions or scheme approval. What an organisation is permitted to do comes from its own permissions and the acquiring programme agreed in writing around it.
What does a PayFac / PSP programme require?
The programme structure, the acquiring relationship, the permissions relied on, how merchant contracts are allocated, who owns risk, how settlement and reporting are handled and where each regulatory accountability sits are assessed and agreed in writing. None of it is assumed from the label, and no organisation automatically qualifies.
What must an Acquirer bring?
The organisation must hold, or obtain, the appropriate regulatory permissions and an approved acquiring structure, and it operates under its own governance. PayFacLite® provides the licensed platform infrastructure and the agreed technical and operating capacity beneath that operation.
Is one route a step up from another?
No. Hosted and Embedded are customer-experience routes; PayFac and Acquirer describe operating arrangements. They are connected choices, not stages or a progression.
Building on it
How it is built, and who builds it.
Which integration routes are available?
Three, all reaching the same governed contract. Guided, where implementation support works beside your team. Schema-aware, which maps PayFacLite® into the customer, merchant, payment and ledger models your platform already uses. Direct, where your engineers work with the contract, APIs, approved SDKs and the sandbox. The developer platform states each route’s current availability beside it.
What is Implementation Support?
An optional implementation service, not a fifth model: our technical team can deliver agreed integration, application and production-readiness work under any operating model. Commercial terms are bespoke.
Do we need our own technical team?
No. You can deliver with your team, work alongside PayFacLite® engineers or agree for our technical team to deliver defined architecture, application and integration work. The technical delivery choice does not change the operating or regulated responsibilities of your programme.
What interfaces does the platform provide?
Approved APIs, SDKs, signed webhooks, an API playground, a sandbox and governed agent-assisted tooling, with each surface carrying its current availability where it is named. Request and response shapes are published in the reference issued with developer access rather than on the public site.
Commercial and launch
Terms, launch and territory.
How does the commercial model work?
Through commercial participation in the activity across your merchant portfolio, the hardware you supply, your own packaging within agreed parameters and additional eligible financial products. Terms are bespoke and agreed for each programme. Lending is subject to eligibility, programme availability and applicable partner-provider conditions.
What is required to launch?
A platform conversation, an agreed proposition, commercial model and responsibilities, then integration, sandbox and controlled production readiness. Progression to production follows technical and programme approval.
Which markets does PayFacLite® support?
Verofy® Acquiring operates the UK-regulated acquiring foundation. PayFacLite® infrastructure can support European and US propositions through the right programme and local arrangements. Market availability depends on programme structure, product scope and applicable regulatory requirements.
Acquiring infrastructure for international platforms.
Market availability depends on programme structure, product scope and applicable regulatory requirements.
United Kingdom
Regulated acquiring foundation
Europe
Programme-dependent infrastructure
United States
Programme-dependent infrastructure
- 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.