Limits and availability
Payment availability depends on method, amount, country and the terms of a particular invoice. Check the total, restrictions and applicable processing time before confirmation.
On this page
Adapter and channel limits#
Kevmi checks the ranges below before creating an operation. A payment channel may impose additional restrictions; an amount within range does not guarantee approval. Changing gateway configuration does not automatically change Kevmi limits.
A new payment and card intent require the merchant’s latest website-review application to be approved. Approval alone does not connect the payment gateway. If the review changes after dispatch, the existing operation remains available for status reads, reconciliation and a requested bank code.
| Method | Amount checked | Kevmi range |
|---|---|---|
| Card / Alipay | USD base price | $1–$1,000 |
| SBP | RUB customer total | ₽1–₽100,000 |
| Crypto | USDT customer total | 1–1,000,000 USDT + selected network limits |
Validation is not a commercial limit#
The calculator and API reject negative amounts, invalid currencies and calculations where the merchant’s allocated fee and VAT exceed the base amount. These checks protect data correctness.
Passing arithmetic validation does not guarantee that a provider can accept the payment. Commercial and risk limits are checked separately by the payment channel.
Refunds and disputed transactions#
Verified refunds, partial refunds, disputes and review states appear in the operation and merchant events. This does not imply that creating a refund or payout is implemented in the account.
Do not fulfil again for payment.partially_refunded, payment.refunded, payment.disputed or payment.review_required. Preserve the original order/payment association and route disputed cases to an authorized operator.
Recurring charges#
Kevmi has no subscriptions or recurring payments. Saving an order link does not authorize an automatic future charge. Each new order is paid separately.
Readiness checks#
gateway.configured in /api/config reports the required gateway settings, while /api/health checks server storage. Neither establishes connectivity to a payment provider. Use invoice.availability in GET /api/checkout/{token} for a specific invoice’s terms; payment success is verified separately against the gateway operation.