Card payments (Stripe, Paddle)

The web shop takes card money through Stripe or Paddle. Both are payment gateways on the same register as the bank transfer: each firm decides which it offers, with its own credentials — nothing is shared between firms.

What the customer sees

At checkout the customer picks the card option and is sent to the processor's own payment page — Stripe's hosted checkout or Paddle's checkout. After paying they land back on their order page, which shows the order as paid. The money is recorded on the order automatically, exactly once, with the processor's reference.

Per-provider pages

Every gateway configures on its own page, and the real processors carry their own documentation:

• Stripe — hosted checkout, immediate refunds.
• Paddle — Paddle-hosted checkout, webhook-first completion, reviewed refunds.
• Bank transfer — the built-in manual gateway: IBAN and a message.

How completion works

The webhook is the truth. When the processor confirms the money, the signed webhook records a completed payment on the order; delivering the same webhook again changes nothing. A webhook that fails its signature, is too old, or names an order this site does not hold is refused with a plain answer that reveals nothing; the operator's log carries the precise reason.

Who invoices the customer

A paid order normally becomes your firm's invoice, mailed to the buyer. One kind of provider changes that: a merchant of record (Paddle) is itself the seller towards the customer — it invoices them with their country's VAT and pays your firm out later. For an order such a provider paid, the platform issues no invoice of its own; the customer is pointed at the provider's customer portal instead. Stripe and bank transfer leave your firm the seller, and the invoice road is unchanged for them. The details and the reasoning are on the Paddle page.