Northbank Financial · card disputes · reported 20 Aug 2026, 20:11 UTC
£1,240.00Exposure
—Report to capture
0/3Checks complete
20:11 UTC
Case timeline0 events
Evidence pack
Waiting for the case to open
Press play to watch the case assemble in real time.
CustomerStory, in their words8 min
Captured 12 minutes after Northbank routed the case. Approved by the customer before sending — quotes are unedited.
How they found itAn ad on Instagram for a refurbished MacBook, £1,240 when the shop price is nearer £1,900. It looked like a proper shop, they had reviews and a returns page and everything.
What made it seem realThere was a countdown saying four left at that price. When I clicked pay it went to a page that looked exactly like the normal card page, with the padlock and the bank logo at the top.
What happened afterI got an order confirmation email straight away with a tracking number, but the tracking number doesn't work on any courier site. Then the Instagram account was gone by the next day.
FlaggedPage & gateway0.94
The checkout imitates a genuine gateway but collects card details directly. No real processor was ever involved. Captured while live — the page returned 404 the following morning.
⚠secure-checkout-verify.shop/pay?ref=881220:33
🔒 Secure Card Payment
Protected checkout · SSL encrypted
Pay £1,240.00
Sandboxed snapshot held in the evidence bundle · DOM, headers and redirect chain preserved
DerivedDomain age — 6 days at time of payment, registered 14 Aug, registrar privacy enabled
DerivedCard field posts to45.13.x.x — not to any processor endpoint
DerivedBranding — padlock and bank logo copied byte-identical from a genuine processor's CDN
DerivedSame page seen in 17 reports across 4 institutions in 9 days
The statement descriptor does not resolve to a registered entity, and the registered address is a mail-forwarding service shared by hundreds of registrations.
NorthbankDescriptor — SECURE-CHECKOUT-VERIFY, first seen on statements 11 days ago
DerivedRegistry — no Companies House match for the trading name
DerivedAddress — virtual office shared by 340+ registrations
DerivedTracking number — format matches no active UK courier scheme
ReviewCall analysis0.71
Intent classified as a purchase dispute. Below the 0.75 threshold because the caller describes a second unrecognised payment — routed for a human to read rather than auto-closed.
Derived00:02:31 — "the tracking number they sent doesn't work anywhere"
Derived00:05:47 — "there was another one last month I didn't recognise either"
DerivedFlag — possible second transaction, not yet identified. Statement review needed.
ActionableWhat this case needs from you20:47
Suggested typology
Purchase scam · goods not received CNP / PURCHASE_SCAM / GNR
Route
Card scheme chargeback — not APP reimbursement Customer authorised the payment to a fraudulent merchant
Evidence bundle
Live page snapshot, DOM, headers, merchant registry check, customer statement
Filing window
Confirm scheme deadline before filing
Open thread
Second unrecognised payment — needs statement review
This is a suggestion, not an assessment. Axnable gathers and ranks evidence. It carries no view on reimbursement, on whether the customer acted reasonably, or on liability — those are Northbank's to determine. Scheme reason codes and deadlines vary by network, region and card product: verify against current scheme rules before filing.
axnable
Synthetic case for demonstration · no real customer or merchant dataWe capture and check. Your institution decides.