Paid twice, shipped once
A retry after a timeout creates a second payment. The customer sees two debits and the counter sees one order.
Services
Payment gateways and digital wallets
A customer pays, the money leaves, and the order still shows as unpaid — or it is marked paid twice and the second refund costs a phone call to explain. The gateway is rarely where that breaks. It breaks at the seam between the provider's confirmation and your ledger: a notification that arrived before the order existed, a confirmation that never arrived at all, a rounding difference in the currency nobody wrote down. That seam is the work.
Who it is for
- Shops taking orders online and confirming payment with a screenshot.
- Businesses where cash on delivery is the default, so refused parcels come back unmatchable.
- Anyone whose accountant rebuilds the month's revenue from a bank statement.
Problems it solves
The notification is the only witness
Confirmation depends on one call reaching one endpoint. If it fails at 2am, the order waits as pending until the customer calls.
Cash on delivery hides the loss
A refused parcel returns as stock and as a courier invoice. The delivery cost lands in a monthly total, never on the order that caused it.
Use cases
Card and wallet checkout
A hosted payment page, so card data never touches your server, and an order state that moves only on the provider's confirmation.
Local transfer and manual confirmation
A bank transfer or a local wallet, a reference field your accountant matches by hand, and a queue for the ones nobody matched.
Refunds and partial refunds
A refund writes a credit note and a stock decision. It is not a delete, and it should not require a developer.
Cash-on-delivery settlement
Each delivered parcel marks the order paid; each refusal restores the stock and books the return cost against the order, by wilaya.
What is in scope
Fixed scope. Fixed price.
Agreed in writing before anything is built. You approve before we start.
- A payment flow diagram: who confirms, who retries, who gets told
- One integration per provider you actually use, with sandbox and live credentials kept apart
- Webhook handling with signature checks, idempotency keys and a replay queue
- A daily reconciliation report: provider settlement against your invoices, with the unmatched listed
- Refund, partial refund and cancellation paths, tested on both sides
- Handover: credentials, keys and documentation in your name
How it is delivered
- 01
Follow one payment by hand
We sit with whoever reconciles yesterday's takings and trace a single order from the customer's screen to the bank line.
- 02
Decide the source of truth
The provider holds the money; your system holds the debt. Write down which one is allowed to be wrong, and how you find out.
- 03
Test the failures first
A timeout, a duplicate callback, a wrong amount, a refund after settlement. The happy path is the easy part.
- 04
Reconcile daily, not monthly
A report that lists what did not match while someone still remembers the order.
FAQ
Questions about this service.
What owners usually ask before requesting a quote for it.
Which providers do you integrate with?
Whichever ones your business or your bank can actually open an account with; the shape of the work is the same. We do not resell any provider's service and we take no commission from one.
Do we have to store card numbers?
No. Hosted pages and tokens keep card data out of your systems. If a provider requires you to hold it, the answer is to change provider, not to build a vault.
What happens when a payment notification is lost?
A replay queue keeps the notifications that did arrive, and a daily sweep compares the provider's settlement with your records and names every order still pending.
Will this stop refused parcels and payment disputes?
No. A refused parcel is a pricing and delivery problem; a dispute is a problem of trust between you and the customer. We can make both visible in the numbers, and make the refund fast enough to avoid some of them. We cannot make them disappear.
Start a project
Want this scoped for your business?
Send the brief. It comes back as a written scope and a fixed quote before anything is built.