Security
How a payment is confirmed, and why a browser redirect is never enough.
Payments
Card details never touch this siteCustomers enter payment details on our payment partner's secure checkout. We never see or store card numbers.
Confirmed on our serversAn invoice is marked paid only after the payment provider confirms it directly to us with a signed notification, which is checked before anything is read from it.
A repeat can never pay twiceEvery notification carries an identity we record. A repeated delivery finds the work already done and changes nothing.
Matched to the orderA payment is matched to its own order, amount and currency before anything is delivered or credited.
Your account
Secrets stay on the serverAPI keys live in server side configuration, never in a page, a link or anything a browser can read.
Invoice under your work nameRegister under your legal name and invoice under your trading name. Customers see the name you choose and only the contact details you decide to share.
Pending before availableNew payments settle into a pending balance first, which is what makes a reversal manageable rather than a surprise.
An auditable historyEvery payment, fee, refund and payout is an entry you can read back. The balance is the sum of its history, not a number we assert.
Questions about any of this?
We are happy to walk through exactly how a payment is confirmed.