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.
The operating foundation behindyour financial proposition.
Build the product, experience and commercial model your customers see. Use the operating and regulated infrastructure beneath it according to the model that fits your organisation.
- You control
- Product · Brand and journeys · Pricing within parameters · Distribution and support
- PayFacLite® operates in the operated arrangements
- Acquiring · Onboarding, KYC, KYB and AML · Risk and ultimate approval · Processing, settlement, reconciliation · Reporting and compliance
For licensed arrangements, responsibilities follow the agreed programme or your organisation’s own permissions. Licensing the platform does not confer regulated status.
One foundation. Built for your proposition.
Acquirer infrastructure is the technology and regulated operating foundation behind merchant onboarding, payment acceptance, processing, settlement, reconciliation and reporting. PayFacLite® makes that foundation available for businesses to build into their own proposition.
Built independently, each of these is a separate acquiring, regulatory, operational or technology investment, with the teams to run it.
What PayFacLite® provides.
- Acquiring and the regulated operation
- The acquiring relationship, merchant onboarding, risk, processing, settlement, reconciliation, reporting and compliance controls, operated as one layer.
- Technology to build on
- Application source or one API contract with signed events, sandbox access and approved integration tooling.
- Commercial capability
- In-person and online acceptance, hardware and eligible financial products, packaged within agreed programme parameters.
How the regulated arrangement works differs by operating model. Under the operated models PayFacLite® operates the regulated foundation and holds the acquiring relationship; under the licensed models responsibilities follow the agreed programme or the organisation’s own permissions. Building on or licensing the platform never confers regulated status.
Clear roles. Defined responsibilities.
Every responsibility sits on one side of the boundary. Under the operated models, Hosted and Embedded, you control the proposition and the customer experience, PayFacLite® operates the infrastructure, and the regulated relationship is held by the regulated entity beneath it.
Responsibility split for Hosted and Embedded.
You
Build, control
- Who builds it?
- Your product, journeys, UX and UI, on the contract or from the supplied application source.
- Who controls the customer experience?
- Brand, journeys, communication and how payments appear inside your platform.
- Who owns merchant support?
- Your support experience, with PayFacLite® operational support under the agreed model.
- Who sets pricing and packaging?
- Within the programme and risk parameters agreed with PayFacLite®.
PayFacLite®
Operate, hold
- Who operates it?
- Acquiring, onboarding, risk, processing, settlement, reconciliation and reporting infrastructure.
- Who conducts risk review?
- Underwriting, KYC, KYB and AML, and ongoing monitoring.
- Who holds ultimate risk approval?
- Retained by the regulated entity beneath PayFacLite®, Verofy® Acquiring.
- Who operates settlement and reconciliation?
- Settlement batches, payouts and matching, with each state returned to your platform.
- Who holds the regulated relationship?
- The acquiring relationship and the regulated merchant relationship.
Building on the layer does not make your business the regulated acquirer. Under the licensed models, PayFac and Acquirer, this split does not apply as written: responsibilities follow the agreed acquiring programme or the organisation’s own permissions, and an Acquirer organisation operates the platform itself.
Your proposition.Your arrangement.
The same technology runs every model. What changes is what is supplied, who develops and operates each part, how acquiring is structured and where regulated responsibility sits.
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.
Supplied components, licence terms and responsibilities are confirmed for each programme. Licensing the infrastructure never confers regulated status.
Trust CentreImplementation Support across every operating model.
Implementation Support is an optional support and development resource available across every operating model. The technical team can review architecture, design the integration and troubleshoot the implementation. It can also map your schema, extend your development capacity, and deliver agreed integration or migration work through testing and production readiness.
Architecture review · Integration design · Implementation troubleshooting · Schema mapping · Development capacity · Agreed integration or migration work · Testing · Production readiness
- Not a fifth operating model, and never mandatory.
- Work is scoped separately.
- Availability is subject to technical assessment and capacity.
- Commercial terms are bespoke.
- It does not change the responsibility boundary of the selected operating model.
One flow, from your product and back again.
A merchant applies from your screens; verification, underwriting and the risk decision run in the layer. Payments are accepted, processed, settled and reconciled beneath it, and every state returns as a signed event.
Your product
Applications, configuration and payment instructions out. Signed events back.
The PayFacLite® operating layer
Operating- 01
Merchant onboarding
Application from your screens
- 02
Identity, business and anti-money-laundering checks
Verification and screening (KYC, KYB, AML)
- 03
Underwriting and risk decision
Ultimate approval retained
- 04
Acceptance
In person and online
- 05
Processing
Capture and refunds
- 06
Settlement
Batches and payouts
- 07
Reconciliation
Matching and exceptions
- 08
Reporting
Presented in your platform
Every station returns its state to your product as a signed event.
Returned to your productOperated-model acquiring foundation
Hosted and Embedded: Verofy® Acquiring holds the acquiring and merchant relationships, with ultimate risk approval.
PayFac and Acquirer arrangements use the same platform infrastructure, while regulatory responsibility follows the agreed programme entity or the Acquirer organisation’s own permissions.
Acquirer-direct. One relationship runs it.
No gateway, programme layer or processor to assemble and negotiate through. Scheme and technical dependencies sit inside your one relationship with PayFacLite®.
In Hosted and Embedded, Verofy® Acquiring holds the regulated relationships. In PayFac and Acquirer arrangements, responsibility follows the agreed programme entity or your organisation’s own permissions.
Your product
You
Gateway or programme layer
Intermediary
Processor
Intermediary
Acquirer
Intermediary
Card schemes
Your product
You
The PayFacLite® operating layer
One commercial and operating relationship
Regulated acquiring foundation
Held by the regulated entity
Card schemes
What each capability makes possible.
See what each service does, the customer outcome it creates, the commercial value it can support and the boundary that applies.
Payment typesMeet customers wherever they pay.
Card-present
What it doesIn-person card acceptance on compatible payment hardware, processed on the acquiring infrastructure.
Customer outcomeMerchants take payments at the point of sale inside a proposition that carries your brand.
Commercial valueAcceptance volume and the hardware estate become part of your portfolio.
Boundary / qualificationCard data is handled on the regulated foundation, keeping PCI DSS scope off your product.
E-commerce
What it doesOnline acceptance for checkouts and hosted flows through the same contract.
Customer outcomeCustomers pay within the online journeys your product already runs.
Commercial valueOnline volume joins in-person volume in one relationship and one commercial model.
Boundary / qualificationProcessing and settlement run on the acquiring infrastructure beneath your product.
Payment links
What it doesA payment requested and collected remotely without a checkout build.
Customer outcomeInvoices, deposits and remote sales are paid without leaving your relationship.
Commercial valueAcceptance reaches transactions a checkout would never see.
Boundary / qualificationEach link runs on the same processing and settlement infrastructure as every other payment.
Virtual payments
What it doesTake assisted payments remotely through a secure virtual terminal.
Customer outcomeA customer pays over the phone or in an assisted conversation without leaving your relationship.
Commercial valueMeet customers wherever they pay.
Boundary / qualificationCard data is handled on the regulated foundation, keeping PCI DSS scope off your product.
SoftPOS
What it doesCompatible devices become acceptance points without dedicated hardware.
Customer outcomeSmaller and mobile merchants accept in person from a device they already carry.
Commercial valueAcceptance extends to merchants a hardware estate would not reach.
Boundary / qualificationDevice eligibility and acceptance rules follow the acquiring programme.
Operating controlControl the relationship end to end.
Onboarding
What it doesApplication, data capture, status and activation inside your product, with KYC, KYB and AML run beneath it.
Customer outcomeMerchants apply and are activated in your experience rather than an external portal.
Commercial valueActivation stays inside your journey, so conversion and time to first payment are yours to shape.
Boundary / qualificationVerification is run and ultimate approval retained on the regulated foundation.
Risk workflows
What it doesVerification, review and decision states connected to your product, with monitoring after activation.
Customer outcomeMerchants see clear, timely status rather than silence while checks run.
Commercial valueFewer stalled applications and a portfolio kept within agreed risk parameters.
Boundary / qualificationUnderwriting decisions and ultimate risk approval remain with the regulated entity.
Processing
What it doesAuthorisation, capture and refunds on the acquiring infrastructure behind every transaction.
Customer outcomePayments complete reliably in every channel your proposition offers.
Commercial valueOne processing relationship beneath every channel, with no separate gateway and acquirer to assemble.
Boundary / qualificationOperated on the regulated foundation under the acquiring programme.
Settlement
What it doesSettlement batches and payouts, with the state of each returned to your platform.
Customer outcomeMerchants see when funds move and why, inside your reporting.
Commercial valueSettlement timing and visibility become part of the proposition you offer.
Boundary / qualificationMovement of funds and safeguarding of relevant funds sit with the regulated entity.
Reconciliation
What it doesPayments, refunds and fees matched to settlement, with exceptions surfaced.
Customer outcomeMerchants reconcile from your platform rather than from separate statements.
Commercial valueLower servicing cost and a portfolio you can see at transaction level.
Boundary / qualificationHow reconciliation data is applied within your systems is part of the integration design.
Reporting
What it doesTransaction, settlement and portfolio reporting returned through the contract.
Customer outcomeOne view of activity and settlement inside the product merchants already use.
Commercial valuePortfolio visibility for pricing, servicing and growth decisions.
Boundary / qualificationReporting reflects the programme and the responsibilities agreed for it.
Added productsCreate more value from every relationship.
Commercials
What it doesThe activity across your merchant portfolio, reported per merchant and per programme.
Customer outcomeNothing changes for the merchant: the value of the relationship accrues to the proposition they already use.
Commercial valueA recurring share of the economics your platform creates, agreed for the programme.
Boundary / qualificationCommercial terms are bespoke and depend on the agreed commercial structure. No return is guaranteed.
Collections
What it doesCollect merchant fees and charges through settlement rather than relying on a separate manual process.
Customer outcomeMerchants see what has been charged and when, against the settlement it was taken from.
Commercial valueCreate more value from every relationship.
Boundary / qualificationWhat is collected, and on what terms, follows the agreed commercial arrangement and the settlement operations on the regulated foundation.
Hardware
What it doesPayment hardware supplied and managed across the portfolio, by you or through PayFacLite®.
Customer outcomeMerchants are equipped through the proposition rather than a separate supplier.
Commercial valueRevenue and margin on the estate, alongside acceptance.
Boundary / qualificationProvisioning and logistics are operated where applicable, under the agreed model.
Lending
What it doesEligible finance offered to merchants through approved programmes.
Customer outcomeWorking capital reaches merchants inside a relationship they already trust.
Commercial valueA broader financial relationship and a further product line in the proposition.
Boundary / qualificationLending is subject to eligibility, programme availability and applicable partner-provider conditions.
Payouts
What it doesFunds moved to the merchants and parties your platform pays, on regulated rails.
Customer outcomePayees are paid through the proposition rather than a separate arrangement.
Commercial valueMoney movement extends the proposition beyond acceptance.
Boundary / qualificationPayouts are subject to programme eligibility, and movement of funds sits with the regulated entity.
Commercial terms are bespoke, agreed with each partner around the proposition, the portfolio and the capabilities activated. Responsibilities follow the selected operating model; nothing above is a guarantee of availability, approval or return.
Behind the boundary, the regulated entity.
Hosted and Embedded operate on a regulated foundation: Verofy® Acquiring holds the acquiring and merchant relationships and retains ultimate risk approval, while PayFacLite® operates the infrastructure and controls. For PayFac and Acquirer arrangements, regulatory responsibility sits with the agreed programme entity or Acquirer organisation under its own permissions.
The Trust Centre carries the evidence: the regulated entity, PCI DSS scope, safeguarding, privacy, environments and access, and incident communication.
- Operated models
- Verofy® Acquiring is authorised and regulated by the Financial Conduct Authority under the Payment Service Regulations 2017, reference 785762. Hosted and Embedded operate on this foundation.
- Licensed models
- For PayFac and Acquirer arrangements, regulatory responsibility follows the agreed programme entity or the Acquirer organisation’s own permissions.
- Security standard
- PCI DSS Level 1.
- Safeguarding
- Relevant funds are safeguarded in line with regulatory requirements.
- Operating environment
- The regulated acquiring foundation is operated in the United Kingdom. The platform supports propositions across the United Kingdom, Europe and the United States.
Market availability depends on programme structure, product scope and applicable regulatory requirements.
From first conversation to launch.
What happens after the first conversation, in order. Each stage completes when it is ready.
- 01
The workshop
A focused conversation with the partner team about what you want to build.
- 02
Proposition and commercial model
Packaging, pricing within agreed parameters, hardware, eligible products and the commercial terms, agreed with you. Exact terms are bespoke.
- 03
Responsibilities and programme parameters
For Hosted and Embedded, what PayFacLite® operates and what you operate; for PayFac and Acquirer, the agreed programme or your own permissions, risk parameters and regulated boundary.
- 04
Integration and sandbox
Developer and sandbox access for your team: the contract, signed webhooks, test merchants and settlement states, exercised end to end.
- 05
Controlled production readiness
Platform, commercial and compliance onboarding complete; production credentials issued under the agreed operating model.
- 06
Launch and expansion
Your first merchants transacting inside your platform, then further channels and eligible products on the same integration.
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.