Quazko sits between your store and licensed payment providers. Here is exactly what happens when a buyer pays — and what happens when something goes wrong.
Your payment page sends the buyer to the Quazko cashier with three values: your project, the buyer's account, and the amount. The buyer sees the amount and picks a payment method available for your store.
The buyer completes payment on the checkout pages of a licensed payment provider. Sensitive payment data — card numbers, wallet keys — is handled entirely by the provider and never reaches Quazko.
When the provider reports the payment as completed, Quazko verifies the report's authenticity, then independently re-confirms the payment against the provider's records, and checks that the amount and currency match the original order exactly.
Your server receives a signed crediting notification. If your server is down, Quazko keeps retrying with increasing intervals until it's confirmed. Duplicates are impossible to credit twice by design.
Payments infrastructure is judged by its worst day. These cases are handled automatically:
| Party | Responsibility |
|---|---|
| Your store | Shows the payment page, sends the buyer to the cashier, credits the account when notified. |
| Quazko | Routes to providers, verifies every confirmation, guarantees exactly-once crediting, keeps the audit trail. |
| Payment provider | Licensed processing of the actual payment: checkout pages, funds, compliance of the money flow. |
| Buyer | Picks a method and pays. Never needs a Quazko account. |
If you're the developer, the whole surface is one redirect and one webhook.