Dedicated by design.
Dedicated Litecoin regtest addresses, connected to your account and ready to explore.
Read moreA clearer way to move on-chain
Dedicated addresses. Clear payment flows.
A workspace built around your business.
Development edition Litecoin regtest
01 / The workspace
From a dedicated address to the details of a transaction. See how the pieces fit together.
Open dashboardA calm workspace for your crypto activity. Explore currencies, open an account and keep each receiving address connected to its owner.
Account dashboard availableGenerate dedicated Litecoin regtest addresses, browse their public details and share a QR code. Your address history stays with your account.
Regtest address generation availableBrowse regtest receipts and Transfers, search by TXID and inspect payment details. Pending, Not seen, Recorded and Orphaned describe incoming observations. A receipt is not an available balance; the balance reader separately checks current node evidence.
Receipt and payment History · RegtestCreate a focused payment experience for each order, with an amount, an address and a clear status. Invoice processing is part of the roadmap.
Design preview · Invoices plannedConfigure receipt Callbacks and inspect actual HTTP attempts in the private Callback Log. Workers retry without acknowledgement; reorg revisions distinguish a lost observation from a new payment. Delivery is at least once, not proof of final settlement.
Callbacks and private log · Regtest02 / Make your move
Set your recipients. Review the details. Make your next move with a clear view of the amount and fee.
Regtest Transfers support one or multiple destinations with integer amounts and an explicit fee limit. Review the plan in the dashboard before confirming. These landing illustrations never send a payment.
Multi-recipient Transfers · RegtestTransfers reserve account-owned outputs, sign the approved transaction locally and keep the same signed bytes for retries. API requests use a Transfer Key and Idempotency-Key; dashboard sending requires Unlock and a reviewed fee limit.
Owned-output Transfers · RegtestA dedicated space for forwarding destinations and transfer preferences. Automation will be added step by step, on top of the payment foundation.
Design preview · Automation planned03 / A deliberate foundation
Litecoin first. More possibilities ahead.
One network at a time, with a clear boundary between what works and what comes next.
Small beginnings. Solid foundations.
Local test network. Live mainnet acceptance is still ahead.
More networks are on the horizon.
Roadmap illustrations · not available
04 / Made for builders
Start with the API. Explore what's next for storefronts and embedded payments. Build at your own pace.
Use 17 implemented methods under /api/v1 for accounts, addresses, balances, History, Transfers, fee quotes and Callbacks. This is local Litecoin regtest; the reference separates working methods from planned products. Client libraries are not released.
17 API methods · Regtest API DocsFamiliar integrations for WooCommerce, PrestaShop and OpenCart are part of our vision. Plugin packages are not available in this version.
Roadmap · E-commerce integrations Explore the dashboardPayment buttons, compact forms and donation experiences will make integration more accessible. The example here is a visual concept, not a live checkout.
Design preview · Widgets plannedExplore the foundation
Dedicated Litecoin regtest addresses, connected to your account and ready to explore.
Read moreA workspace for assets, incoming receipts and your next transfer.
Read moreStart with an account. Connect your application to the payment flow with API v1.
Read moreFollow the payment foundation, capacity and recovery work, and the next product milestones.
Read moreIt means that payments are recorded on the blockchain, with public transaction references and receiving addresses. Coinkun is being built around that model; the current version is a local Litecoin regtest environment.
Create an account, issue addresses, inspect mempool and block observations, read verified balances, send regtest Transfers and receive Callbacks. Public keys are prepared from the local Signer. Scanners and payment processing need an enabled core worker; callback delivery uses a separate worker. Rails server alone does not process the chain.
Yes. Addresses belong to a specific account's vault and public keyset. The application derives receiving addresses from public key material without storing a seed phrase in the dashboard.
No. This version is for Litecoin regtest only. Regtest coins are local test coins, not real Litecoin. Do not use this development environment for customer payments or real funds.
Start with the /api/v1 reference and its implemented-method labels. Keep the one-time Transfer Key private, preserve each transfer's Idempotency-Key and verify callback event revisions before updating an order. Plugins, widgets, invoices, Wallet API and JWT Authorization remain planned.
The reviewed capacity and recovery defects have been corrected and the local acceptance pass completed. Processing limits still apply: unavailable evidence is not a zero balance. Live mainnet acceptance and deployment remain separate, uncompleted milestones; further products need their own agreed step. Local tests are evidence for tested scenarios, not production certification.
Your next chapter starts here
Explore on Litecoin regtest.
No real funds needed.
A dedicated workspace for your payment project.
Shown once. Keep your private access somewhere safe.
Create an address. Explore the dashboard. Try the API.