Built to say yes.
KITRA directs each payment to the provider most likely to approve it, based on the payer's country, the payment method and current provider performance. Settlement arrives in USDC in the merchant's own wallet.
Most declines are a routing question.
A decline usually reflects the route chosen for the payment: an issuer that blocks the merchant category, a provider without the local method, or a limit set for another country. KITRA resolves it while the payer is still on the page.
- 01
Read the context
Country, currency and payment method are assessed when the payment page opens.
- 02
Select the route
Routing rules and current provider performance determine the first route. The payer's preferred local method comes first where it performs better than cards.
- 03
Recover the decline
When a provider declines, the payment moves to the next eligible route. The payer is told that no funds were taken and is offered the next option.
- 04
Settle to the merchant
Funds arrive in USDC in the merchant wallet. USDT can be selected in the console settings instead.
The merchant decides how much the router decides.
Automatic
DefaultKITRA selects the provider and the order of fallbacks for each country and method. Changes in provider performance are reflected without manual intervention.
Mixed
The merchant fixes preferred providers for selected countries. KITRA manages all other countries and every fallback.
Manual
The merchant defines the full route table. The console shows the risk of each choice before it is applied.
One button for the buyer. The rest runs by itself.
The buyer pays in the card provider's window. A wallet is created for the buyer's email, receives the USDC and forwards it to the merchant automatically. The page reports every step.
The payer pays the way their country pays.
The payment page presents the methods that perform best in the payer's country, ahead of the global default. New local methods join the routing table as providers are connected for each market.
Solid: available today. Dashed: added to routing as the provider for the market is connected.
Funds go to the merchant. KITRA keeps the route.
No custody
USDC moves from the buyer's wallet directly to the merchant's address. KITRA holds no funds and has no keys to either wallet.
No card data
Card details are entered only in the provider's secure window. They never reach KITRA servers, logs or storage.
Exact amount, exact address
The buyer signs a transfer of the order amount to the merchant's address only. Our relayer submits it and pays the network fee, but cannot change either.
Payout asset
USDC by default, USDT on request. A provider without the selected asset settles in its fallback asset and is never removed from the route for that reason.
One request. Every country.
Create an invoice through the API and open the KITRA payment page with the widget or a redirect. Routing and fallbacks are handled by the platform. Signed webhooks confirm every final status.
REST API with HMAC signatures and idempotency keys, a test mode on Base Sepolia and a demo store.
OpenAPI description// 1. Create the invoice on your server { "amount": 249.00, "currency": "EUR", "network": "base", "merchant_order_id": "A-10482" } // returns { "checkout_url": "https://pay.kitra.ch/pay/inv_7QX4" } // 2. Open the checkout on your page KITRA.open(checkout_url, { onPaid, onClose }) // 3. Fulfil the order on the webhook invoice.paid amount_received, tx_hash, fee_amount
Charged only on completed payments.
The buyer's payment reaches the merchant wallet in full. Nothing is deducted in transit.
See a test paymentA percentage of each paid invoice, agreed with the merchant and fixed in every invoice. Unpaid and expired invoices carry no charge.
Get startedA fee statement every day at 00:00 UTC, or on request in the console and the API. Settled in USDC.
Discuss your rateQuestions
Does KITRA store card details?
No. Card details are entered only in the window of the card provider. KITRA never sees, stores or logs them.
Does KITRA hold merchant funds?
No. The USDC moves from the buyer's own wallet to the merchant's wallet address in one on-chain transfer. KITRA has no access to either wallet.
Does the buyer need a crypto wallet?
No. A wallet is created for the buyer's email during the payment and the transfer to the merchant runs automatically. Buyers who already hold USDC or USDT can pay from their own wallet instead.
Which currencies and networks are supported?
Invoices in USD, USDC, USDT, EUR, GBP, CHF and other currencies with an ECB reference rate. Card payments settle in USDC on Base. Wallet payments are accepted on Ethereum, Base, Polygon, Arbitrum, BNB Chain and Tron.
How quickly does the money arrive?
Once the card provider delivers the USDC to the buyer's wallet, the transfer to the merchant usually completes in under a minute. An identity check at the card provider can add time on a first purchase.
How is the fee charged?
The merchant receives the full amount of each payment. The KITRA fee is a percentage of paid invoices, billed in a daily statement settled in USDC. Every statement and accrual is visible in the console and the API.
Is there a test mode?
Yes. The test mode runs on Base Sepolia with test USDC, and the demo store shows the complete flow from the Buy button to the paid invoice.
Start with one integration.
One API, one payment page and one console for every market the merchant serves.