Skip to content

Build the experience into your own product and platform.

No supplied interface, and nothing of ours in front of your customer. You build the experience through the API contract, signed events, the sandbox and approved integration tooling, and PayFacLite® operates the regulated foundation beneath it.

Discuss your operating model
Best for
Software Platforms & ISVs
You receive
APIs, events and tooling
You control
The complete product architecture
Operated by
PayFacLite®

Embedded finance as part of your platform, not a page your customer is sent to.

Embedded is for a team whose product is already the place its customers work, and which will not hand that relationship to a third-party interface at the moment money moves.

Own the journey
A merchant applies, is activated, takes payments and reads their settlements in your screens. Nothing redirects, and nothing arrives in a different design language.
Your platform, your architecture
You decide the data model you present, the workflows, the states you expose and how payments appear in your information architecture. The platform fits your product rather than the other way round.
One contract behind it
The same contract across the SDK, raw HTTP and agent tooling, with signed events returning every state, so the integration your team builds is the integration that runs.

You build the experience. PayFacLite® runs the operation.

The boundary does not move with the depth of the integration. However far your product goes, the regulated operation stays on one side of the line.

You control

Shape the four parts of the experience your team owns.

  • Design your productOwn the frontend, architecture and the way the product works.
  • Shape every journeySet the UX, UI and workflows your customers move through.
  • Embed the servicesDecide how PayFacLite® services fit inside your platform.
  • Put your data to workUse operational and event data in your own systems.

PayFacLite® operates

  • Connect to acquiringAcquirer-direct acquiring.
  • Verify merchantsMerchant verification and anti-money-laundering controls.
  • Assess and approveUnderwriting, risk review and ultimate approval.
  • Process and settleProcessing, settlement and reconciliation.
  • Monitor the operationOngoing monitoring and regulatory operations.

Support, updates and assurance

  • PayFacLite® integrationPlatform layer access and technical support.
  • Platform operationsPlatform and operations support.
  • Updates and statusSoftware updates and the status page.
  • Monthly assuranceMonthly performance and audit reports.
  • Hosting optionsPayFacLite-hosted or self-hosted.

Licence, modification and maintenance terms; supplied source and components; native apps and app-store arrangements; support and report scope; hosting responsibilities; permitted product presentation and parameters; and regulatory roles are agreed for each programme. Platform access or a licence does not itself confer regulated status.

The surface you build against.

Four surfaces define the technical relationship: API, signed events, sandbox and approved tooling. Use them to connect online and remote payments, with SoftPOS on compatible devices where available.

One API contract
The same objects and the same semantics across the SDK, raw HTTP and agent tooling, so a decision made in one surface holds in the others.
Signed events
Every state change returns as a signed webhook, so your product holds its own view of onboarding, acceptance, settlement and exceptions.
Sandbox
Test merchants, test acceptance and settlement states, exercised end to end before anything touches production.
Approved integration tooling
SDKs and agent tooling as available, plus the technical team where you want implementation support rather than documentation.

Build around the contract.Own the experience.

The object model, the webhook catalogue and the route to production live on the developer platform and are not restated here.

Add PayFacLite® technical delivery where architecture, integration or additional build capacity is wanted. It never changes the responsibilities of the arrangement.

Discuss Implementation Support

From the contract to production.

An Embedded programme is a build, so its route is shaped around your engineering rather than around a delivery.

  1. Workshop

    What you are building, where payments belong inside it, and which states your product needs to hold.

  2. Responsibilities

    What you present, what PayFacLite® operates, the risk parameters and the regulated boundary, set out before anything is built.

  3. Integration

    Developer and sandbox access for your team: the contract, signed webhooks, test merchants and settlement states, exercised end to end.

  4. Signoff

    Platform, commercial and compliance onboarding complete; production credentials issued under the agreed operating model.

  5. Launch

    Your first merchants transacting inside your platform, then further channels and eligible products on the same integration.

Add PayFacLite® technical delivery where architecture, integration or additional build capacity is wanted. It never changes the responsibilities of the arrangement.

Explore Implementation Support

See how Embedded compares.

Compare Hosted, Embedded, PayFac and Acquirer in the same structure used across the site. Each arrangement keeps its own delivery, operating and regulatory boundary.

Platform model

Operated infrastructure

Embedded

You are here
Best for
Software Platforms & ISVs
Proposition
Build the payments experience into your own product.
What is supplied
The API contract, signed webhooks, sandbox, and SDKs and agent tooling as available.
Delivery and integration
APIs, SDKs, webhooks, sandbox and approved integration tooling.
What you control
The complete product architecture
What PayFacLite® operates
PayFacLite®
Acquiring structure
PayFacLite®, acquirer-direct
Regulated responsibility
The regulated entity beneath PayFacLite®
Route to live
Build against the contract in the sandbox, then move the same integration to production.
Capability access
The operated capability set, within agreed programme parameters.

Operated infrastructure

Hosted

Explore Hosted
Best for
ISOs & Utility Platforms
Proposition
Launch a custom payments proposition on your own domain.
What is supplied
Frontend and native iOS and Android application source, pre-integrated with the operating layer.
Delivery and integration
Pre-integrated; extended through the same contract.
What you control
Brand, journeys and roadmap
What PayFacLite® operates
Operated by PayFacLite®
Acquiring structure
PayFacLite®, acquirer-direct
Regulated responsibility
The regulated entity beneath PayFacLite®
Route to live
Source supplied, shaped by your team, launched on the operated foundation.
Capability access
The operated capability set, within agreed programme parameters.

Licensed infrastructure

PayFac

Explore PayFac
Best for
PAYFACS, PSPS & REGULATED PAYMENT COMPANIES
Proposition
Run an agreed acquiring programme on licensed infrastructure.
What is supplied
PayFacLite® platform technology, licensed and configured for the programme.
Delivery and integration
The platform connected to an agreed acquiring environment.
What you control
Configuration, estate and operations
What PayFacLite® operates
Programme-defined
Acquiring structure
Agreed acquiring programme
Regulated responsibility
Programme-defined
Route to live
Agree the programme, configure the platform to it, then operate within it.
Capability access
The platform’s capabilities, within the agreed programme.

Licensed infrastructure

Acquirer

Explore Acquirer
Best for
ESTABLISHED ACQUIRERS OPERATING UNDER THEIR OWN PERMISSIONS
Proposition
Operate the full platform on licensed infrastructure under your own permissions.
What is supplied
The complete licensed platform and supporting technical infrastructure.
Delivery and integration
The licensed platform, integrated with your acquiring or programme structure.
What you control
Product, operation and commercial model
What PayFacLite® operates
Regulated organisation
Acquiring structure
Regulated organisation’s approved structure
Regulated responsibility
Regulated organisation under its permissions
Route to live
Confirm permissions and acquiring structure, configure the platform, then operate it yourself.
Capability access
The platform’s capabilities, configured under your own permissions.
Book a workshop with our technical partner team

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
PFL Trust Centre

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.

Book a 30-minute workshop

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.

Email us: enterprise@payfaclite.com

Call us: 0330 088 1251

Visit us: Bank House, Manchester.