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.
PayFacLite® gives your team one governed technical and operating foundation for payments and financial services. You do not have to assemble every regulated, payments and operational capability yourself.
Bring the product, customer relationship and commercial proposition. PayFacLite® provides the platform, integrations and operating capability beneath it.
A full payments and financial-services proposition requires more than a checkout or an API. It brings product, payment operations, regulated infrastructure and ongoing programme delivery together.
PayFacLite® brings these layers together as one governed foundation, configured around the proposition you are building.
The customer experience and operating arrangement may change. The underlying platform, integration discipline and delivery controls remain connected.
Launch a custom payments proposition on your own domain.
Build the payments experience into your own product.
Run an agreed acquiring programme on licensed infrastructure.
Operate the full platform on licensed infrastructure under your own permissions.
Hosted and Embedded define how payments appear in the experience. PayFac and Acquirer define the programme and operating arrangement beneath it.
Trust CentrePayFacLite® connects the product experience your teams build to the operating capabilities required to deliver it, with clear interfaces and responsibility boundaries between each layer.
Your product
Customer journeys, proposition, brand and commercial experience.
PayFacLite® interfaces
Approved APIs, SDKs, signed webhooks, sandbox and implementation tooling, with integration support where applicable.
PayFacLite® operating layer
Onboarding, payment processing, risk controls, settlement, reconciliation, reporting and support capabilities.
Programme and partner configuration
The agreed programme structure, commercial setup, partner arrangements and applicable operating controls.
Customer, merchant and operating outcomes
The service, information and operational outcomes returned to the product and teams that own the relationship.
Capabilities are connected through one operating layer, and each exists to support a specific part of the proposition and programme.
Configure who the programme serves and how decisions are governed.
| Capability | What it enables | Operating or commercial outcome |
|---|---|---|
| Onboarding | Application, data capture, status and activation inside your product, with KYC, KYB and AML run beneath it. | Activation stays inside your journey, so conversion and time to first payment are yours to shape. |
| Risk workflows | Verification, review and decision states connected to your product, with monitoring after activation. | Fewer stalled applications and a portfolio kept within agreed risk parameters. |
Onboarding
Risk workflows
Meet customers wherever they pay.
| Capability | What it enables | Operating or commercial outcome |
|---|---|---|
| Card-present | In-person card acceptance on compatible payment hardware, processed on the acquiring infrastructure. | Acceptance volume and the hardware estate become part of your portfolio. |
| E-commerce | Online acceptance for checkouts and hosted flows through the same contract. | Online volume joins in-person volume in one relationship and one commercial model. |
| Payment links | A payment requested and collected remotely without a checkout build. | Acceptance reaches transactions a checkout would never see. |
| Virtual payments | Take assisted payments remotely through a secure virtual terminal. | Meet customers wherever they pay. |
| SoftPOS | Compatible devices become acceptance points without dedicated hardware. | Acceptance extends to merchants a hardware estate would not reach. |
Card-present
E-commerce
Payment links
Virtual payments
SoftPOS
Operate the service with clearer controls, evidence and accountability.
| Capability | What it enables | Operating or commercial outcome |
|---|---|---|
| Processing | Authorisation, capture and refunds on the acquiring infrastructure behind every transaction. | One processing relationship beneath every channel, with no separate gateway and acquirer to assemble. |
| Settlement | Settlement batches and payouts, with the state of each returned to your platform. | Settlement timing and visibility become part of the proposition you offer. |
| Reconciliation | Payments, refunds and fees matched to settlement, with exceptions surfaced. | Lower servicing cost and a portfolio you can see at transaction level. |
| Reporting | Transaction, settlement and portfolio reporting returned through the contract. | Portfolio visibility for pricing, servicing and growth decisions. |
Processing
Settlement
Reconciliation
Reporting
Create more value from every relationship.
| Capability | What it enables | Operating or commercial outcome |
|---|---|---|
| Commercials | The activity across your merchant portfolio, reported per merchant and per programme. | A recurring share of the economics your platform creates, agreed for the programme. |
| Collections | Collect merchant fees and charges through settlement rather than relying on a separate manual process. | Create more value from every relationship. |
| Hardware | Payment hardware supplied and managed across the portfolio, by you or through PayFacLite®. | Revenue and margin on the estate, alongside acceptance. |
| Lending | Eligible finance offered to merchants through approved programmes. | A broader financial relationship and a further product line in the proposition. |
| Payouts | Funds moved to the merchants and parties your platform pays, on regulated rails. | Money movement extends the proposition beyond acceptance. |
Commercials
Collections
Hardware
Lending
Payouts
Availability depends on the programme structure, eligibility and applicable regulatory requirements. Lending and payouts are subject to eligibility and programme availability. Where a capability is AI-assisted, the rules, policy controls, review routes and accountability around every decision stay visible, and no decision is taken without them.
The allocation is not identical across every operating model. Under the operated models PayFacLite® operates the regulated foundation; under the licensed models responsibilities follow the agreed acquiring programme or the organisation’s own permissions, and the arrangement is confirmed in writing.
Explore the Trust CentreThe route is shaped by the proposition, operating model and programme structure, not by a generic implementation checklist.
Proposition
Define the relationship, product experience and commercial model.
Operating model
Identify the Hosted, Embedded, PayFac or Acquirer arrangement that fits.
Programme design
Confirm roles, controls, commercial structure and applicable responsibilities.
Integration
Connect the product, teams, workflows and approved interfaces.
Readiness
Validate operational processes, evidence, support and launch conditions.
Live operation
Run, monitor, improve and extend the proposition over time.
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.
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.