Sign in to Hub Book a demo
Legal · Stowe Family Law

Clients pay by link at any hour, and the payment posts itself to the case ledger.

Clients could only settle legal fees by reading card details to staff over the phone in office hours, and every payment then had to be re-keyed into the case ledger.

Talk to us about something similarAll case studies
ClientStowe Family Law
SectorLegal
WhenLive
Used byClients paying by link with no login, finance staff processing refunds, support using the audit tools
Plugs intoOpayo (Sage Pay), Opayo Reporting API, Proclaim
AINone. This one runs on rules, not models.
What we built

Pay by link, 3D Secure handled, refunds guarded, everything reconstructable.

A pay-by-link card page pre-filled from a Proclaim-generated link carrying the case reference, case type, name, address and amount.
3D Secure v2 handled in an embedded frame, with frictionless payments completing in one step and challenged ones resuming cleanly on return.
A staff refund page with an atomic guard that reserves the refund in the database before anything is sent to the payment provider.
XML generated on every completed transaction and refund, dropped into folders by case type for Proclaim to collect.
An admin transactions list pulled live from Opayo's reporting service with date-range filtering and paging.
A step-by-step audit trail of every payment journey, plus a debug viewer and a command-line lookup tool for support.
correctness

The double-refund guard

One insert with a unique key blocks a second refund from a double-click, a second tab or a second device, while still allowing deliberate repeats.

support

A journey you can replay

The browser logs every stage with the exact error, so a failed payment is reconstructable after the client has closed the tab.

honesty

Typed failure reasons

Not found, IP blocked, transport and bad response are distinguished, so 'the provider says no' is never confused with 'we could not ask'.

How it plugs in

Card data never touches the firm's systems.

The provider holds the card. The portal holds the audit trail. Proclaim receives a file per transaction from a pickup folder swept by a scheduled job on the firm's own network.

The applicationOpayo (Sage Pay)Opayo Reporting APIProclaim
job XML written the moment a transaction completes, on both the frictionless and 3D Secure paths
job A scheduled sweep on the firm's side collects every waiting file and deletes it after pickup
What changed

Clients pay faster and out of hours. Staff stopped taking card details over the phone. Completed payments reach the case ledger without anyone re-keying a figure.

one detail only this project hasThe refund guard was added after a real double-refund incident, and the reporting API is IP-restricted so only a whitelisted server can ask it questions.
Something similar?

Still taking card details over the phone?

Book a walkthroughRequest a callback