Skip to content
KezaroPay

KezaroPay Payments

Follow a merchant payment from checkout to its balance.

KezaroPay Payments brings Payment Links, hosted checkout and integration workflows into one merchant workspace. It keeps incoming payments, available funds and the Merchant Protection Reserve visible as different amounts.

Choose the checkout route that fits the sale

Payment Links illustrate a shareable checkout for a product, service or invoice. Hosted checkout presents customer fields and payment-method choices on a payment page.

The API and WooCommerce areas show integration setup and event-handling concepts. They are not connected processing services in this release; generated test credentials and sample responses must not be used as live merchant infrastructure.

Pending is different from Available

A successful customer-payment outcome and a settled balance are different states. The product separates Pending payments from Available funds, and shows gross amount, processing fee and net amount together.

A simulated success confirms only the test flow. It does not mean a processor charged a card, settled funds or made money available for withdrawal.

One Merchant Protection Reserve

The product rule is a $300 Merchant Protection Reserve for the Payments account, shared by Gateway and Payment Links. It is held while processing is active and tracked separately from Pending and Available funds.

Return of the reserve requires processing closure and account review. It is refundable under that process, not automatically released whenever the balance changes. It is separate from the initial Cards funding rule.

Lawful businesses and individual review

The intended merchant audience includes digital services, subscriptions, SaaS, advertising services, online communities and international ecommerce. Licensed streaming is a use context only where the business holds the required rights.

A high-risk category describes processing considerations, not permission to offer unlawful products or mislead customers. Every merchant requires review; category examples are not a promise of acceptance.

Move from an example to a live integration carefully

Before taking real payments, the merchant needs an active processing arrangement, configured credentials, accurate customer-facing terms and a working fulfillment and support process.

Those live financial integrations are outside the current release. You can explore the interface now, with the product and testing boundaries stated on each relevant flow.