For merchants taking payments in person
Use a merchant-presented QR flow when you want the customer to move from physical checkout to a bank authorisation journey on their own device.
Merchant-presented QR
UK pay by bank
Hosted checkout
In-person pay by bank for merchant teams that need a sharper checkout surface.
TruLayer Pay gives merchants a QR-led flow to create a checkout, hand off bank authorisation to the customer device, and reconcile the payment outcome back into one operating workflow.
Settlement model
Webhook-led status updates
Customer journey
Scan, authorise, confirm
Operating surface
Dashboard and QR checkout
Product overview
What this product is for
For teams that need a clean operating trail
The product is built around hosted payment creation, payment references, webhook-driven updates, and dashboard visibility rather than ad hoc transfer instructions.
For staged rollout
Start with single immediate payments, merchant-owned vendors, and explicit payment status handling before expanding into broader marketplace or recurring-payment models.
Preview
Operator workflow
North Star Roastery
£12.50
Ready to present
Merchant QR
Checkout session
LiveCustomer scans, chooses bank, and authorises on their own device.
Settlement state
Webhook pendingThe dashboard updates when the server-to-server payment event arrives and the checkout moves beyond authorisation.
How it works
1. Create a checkout
A merchant selects the vendor, enters the amount, and generates a short-lived checkout session with a customer-facing pay page and QR code.
How it works
2. Authorise in bank
The customer scans the QR, reviews the amount, selects their bank, and authorises the payment through the hosted TrueLayer flow.
How it works
3. Reconcile by webhook
The app treats the webhook as the source of truth, updates the payment record, and moves the checkout out of pending states when execution or settlement events arrive.
Why this direction
Built for a merchant workflow, not a generic framework demo.
Safer public surface
The public page explains the product instead of exposing checkout activity or merchant operations.
Operationally clearer
Internal activity stays inside authenticated merchant surfaces where payment status and vendor ownership actually matter.
Faster merchant adoption
The messaging explains the core flow in plain terms for operators, stakeholders, and prospective merchants.
Aligned with the product plan
Merchant-presented QR, hosted bank auth, and webhook-led reconciliation remain the primary product story.
Commercial shape
Pricing placeholder
Pilot onboarding
Structured as a rollout phase for selected merchants while payment operations, webhook handling, and settlement visibility are tuned in production-like conditions.
Operator-facing value
The product value is less about a generic payment widget and more about a usable merchant workflow: vendor setup, QR checkout creation, and status-driven reconciliation.
Frequently asked
Common product questions
Is this a direct bank transfer product?
No. The intended flow is Open Banking pay by bank through TrueLayer, with hosted authorisation and server-side status updates.
Why use a QR flow at checkout?
It creates a clean handoff from a merchant-operated checkout surface to the customer’s own banking device, which suits in-person payment collection.
What confirms the payment in the app?
The webhook is the source of truth. Browser return alone is not treated as final settlement confirmation.
Next step
Put the product in front of real merchant operations, not just sandbox payments.
Use the merchant dashboard to create checkout sessions, validate webhook-driven payment updates, and shape the operator workflow before broadening the commercial rollout.