Pixl is built as a collection layer that sits above payment providers.
Merchants keep their own gateway relationships; Pixl standardises how
requests are created, sent, paid, and reconciled.
Gateway-agnostic collections
Merchants are not forced onto a single acquirer or PSP. Pixl connects
to the payment methods and providers each business already uses — or
wants to offer — and presents one consistent pay experience to the
customer. Settlement stays with the merchant’s chosen provider; Pixl
orchestrates the request, checkout options, and outcome.
Supported method families include Open Banking account-to-account
payments, card checkout, Direct Debit, and SoftPOS / Tap to Pay.
Providers can be mixed per tenant (for example Open Banking alongside
Stripe, SumUp, Worldpay, or GoCardless) so businesses are not locked
into one stack as they grow or change commercial terms.
Prepaid credits model
Usage is metered with prepaid credits rather than a share of every
transaction’s settlement. Merchants top up credits on the platform;
credits are reserved when payment requests are created and consumed
when collections succeed. That keeps Pixl’s commercial model separate
from the merchant’s gateway fees and bank settlement.
Payment requests at scale
Teams can raise requests one-by-one, import batches by CSV, or create
them through a REST API from their own systems. Each request becomes a
branded pay link that can be reused or scoped to a single collection,
with status tracked through to paid, cancelled, or expired.
Branded delivery by email and SMS
Requests are sent to customers with the merchant’s branding, not a
generic Pixl checkout identity. Links can also sit on a merchant custom
domain, so the customer journey stays on the business the payer already
knows.
In-person and remote collection
The same payment request model covers remote links and face-to-face
collection. Staff can take payment with SoftPOS / Tap to Pay hardware
or present an Open Banking QR code, without switching to a separate
tool or a different gateway-specific app for every method.
Payers, webhooks, and operations
Merchants manage a payer CRM, reusable payment links, team access, and
outbound webhooks so their own systems stay in sync. Payers can open a
short link, choose an available method, and receive a receipt; optional
“My Payments” history lets them revisit requests across merchants via
a magic link.
Multi-tenant isolation
Each merchant operates in an isolated tenant: their branding, provider
credentials, payers, requests, and reporting stay separated. Platform
operators can provision tenants and oversee billing without mixing
customer data between businesses.
