Pocket Pay card payments

What it does

Customers pay by card on a secure Pocket Pay page and come straight back to the shop, and the order unlocks on its own. No transfer receipt to upload, no one checking a bank app and approving orders by hand.

Senimerge Shop is the first store on it: an e-book bought by card lands in the reader's library within seconds of paying. It is proven end to end on Pocket Pay's test server and opens to every customer when the merchant keys are issued. QR payments with automatic confirmation follow in November.

How it is built

• One module shared by every site: start a payment, confirm it, release the order. A new shop only plugs in its own "what does paid unlock" step.
• The order is released only after the server asks Pocket Pay directly and the amount matches to the cent, never because a browser said "success".
• The confirmation and the customer's return both arrive, often seconds apart, and the order is still released exactly once.
• A declined or abandoned payment leaves the order open with a "Pay with card" retry, and unpaid orders close themselves so stock is not held forever.
• Tested against the real gateway, not a mock: successful payment, declined card, timed-out page, retry and same-day void.

Where it goes next

The same module drops into the other shops and systems I run (storefronts, bookings, the parcel and café systems) with only their fulfilment step changing.