KONEBE · PEURO PAY · PAYMENT TECHNOLOGY
Multicurrency merchant payment infrastructure for in-person and online sales. Two APIs, three checkout experiences and integration with Konebe Wallet.
PEURO · BTC · ETH · TRX · BNB · LTC · DOGE · SOL
PEURO PAY · KONEBE
A clear foundation: one API for POS and direct payment requests; another for checkout sessions and widgets. Every experience uses the appropriate contract.
Your store creates a charge and tracks its status.
POST /api/merchant-pdvPOST /api/merchant-pdv · create/status. Your server selects the cryptocurrency, creates the payment and checks its status. Used by in-store POS, online store APIs and Checkout 1.0.
The checkout adapts the payment experience for buyers.
POST /api/merchant-checkoutPOST /api/merchant-checkout · session-create/session-status and dedicated widget actions. Checkout 2.0 offers buyer asset selection; Checkout 3.0 uses an authorized HTML widget.
PEURO PAY · KONEBE
Six experiences for distinct business needs — without confusing checkout products with separate APIs.
Charge on mobile; an authorized main wallet receives.
Charge from a cashier phone while the authorized main wallet receives funds in the relevant flow. This is not a separate API.
Connect your physical POS and track sales status.
Connect your till system to the POS API to create charges and check settlement status. Keep the credential server-side.
Connect your e-commerce backend directly.
Your backend picks the asset, creates a charge through the POS API and displays a payment link or QR to the buyer.
Buyers pay on Konebe checkout; the store picks the asset.
Your system chooses the asset and creates a charge; the customer pays in Konebe hosted checkout. Uses the POS API.
Buyers select the cryptocurrency in hosted checkout.
Your backend sends the commercial amount and currency. The customer chooses an allowed asset in Konebe checkout. Uses the Checkout API.
Embed HTML in your site without building a backend.
Embed HTML with a public widget ID on a simple website. Supports configurable open-amount donations or fixed-price payments. Uses the Checkout API.
Protected credentials, authorized destinations and verified payment status, with full details available to integrators.
The merchant connection defines approved assets and destinations. Keep the PDV Key only in a protected server-side component; the widget uses a public identifier only. Payment links and QR codes must contain no seeds or private keys. POS API payment QR codes must use order.paymentUrl exclusively.
Opening checkout, scanning a QR, receiving HTTP 200 or sharing a TXID is not proof of payment. The merchant server must verify the legitimate paid state before automatically fulfilling an order.
Documented assets, subject to activation: PEURO, BTC, ETH, TRX, BNB, LTC, DOGE and SOL. Commercial pricing currencies: BRL, EUR, USD or PEUR. Direct receipt sends native crypto to authorized addresses. Converted receipt settles into PEURO after verification, minus the configured fee.
Converted settlement has a minimum of 1 and configurable upper limit of up to 10,000 PEURO equivalent per charge. This reserve commercial cap does not apply to direct receipt, which remains subject to technical and network rules. Fees follow the operator configuration.
PEURO PAY · KONEBE
Merchant configuration, POS connection and asset selection in the existing interface.
Reference screens from the Wallet merchant area. Interface labels may vary by language and account configuration.
PEURO PAY · KONEBE
Four V2.35 guides in English for integrators, software companies and merchants.
In 1.0 the store selects the asset through the POS API; in 2.0 the buyer selects it via the Checkout API; in 3.0 the merchant embeds an HTML widget powered by the Checkout API.
Direct API integration, Checkout 1.0 and Checkout 2.0 need a merchant backend. Checkout 3.0 is designed for sites without their own backend, but the merchant still configures a connection in Wallet.
PEURO, BTC, ETH, TRX, BNB, LTC, DOGE and SOL, subject to the assets enabled on the merchant connection.
Yes, through the direct mode and pre-approved addresses. Converted settlement into PEURO is also documented, with its own fees and limits.
Only after the authorized integration verifies the legitimate paid status. A QR, TXID or HTTP 200 is insufficient.
Yes. The POS API and Checkouts 1.0, 2.0 and 3.0 have official V2.35 PDFs in Portuguese, English and Spanish. This page links to the English editions.
Compare sales channels, backend requirements and who selects the cryptocurrency.
Technical basis: official KONEBE V2.35 manuals. Public product information; operations require an active merchant connection and authorized environment.