How it works

The journey of a payment, start to finish.

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.

The happy path

Four steps, each one checked.

Checkout handoff

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.

Licensed processing

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.

Independent verification

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.

Guaranteed notification

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.

When things go wrong

Failure is a scenario, not a surprise.

Payments infrastructure is judged by its worst day. These cases are handled automatically:

The buyer pays the wrong amount
The confirmation won't match the original order. The payment is flagged for review instead of being credited — the discrepancy is visible in the payment's history.
The same confirmation arrives twice
Providers re-send confirmations when networks hiccup — that's normal. Quazko recognises repeats and acknowledges them without crediting again.
Your server is offline when a credit arrives
The notification is retried with increasing delays until your server confirms it. A credit can be delayed by your downtime — it cannot be lost.
Someone forges a "payment completed" message
Every confirmation must carry a valid cryptographic signature and is additionally re-checked against the provider's own records. Forged or unsigned messages are rejected and recorded.
A payment is refunded
A refunded payment is permanently marked as refunded. It can never be re-credited afterwards, no matter what messages arrive later.
Roles

Who does what.

PartyResponsibility
Your storeShows the payment page, sends the buyer to the cashier, credits the account when notified.
QuazkoRoutes to providers, verifies every confirmation, guarantees exactly-once crediting, keeps the audit trail.
Payment providerLicensed processing of the actual payment: checkout pages, funds, compliance of the money flow.
BuyerPicks a method and pays. Never needs a Quazko account.
Where is the money? Buyer funds are received and settled by the licensed payment provider directly to the merchant's configured settlement destination. Quazko orchestrates and verifies — it does not hold funds.

See the integration side.

If you're the developer, the whole surface is one redirect and one webhook.

Developer docs