Skip to content
coinkun
Dashboard

Accept crypto payments on your website

Find the integration that fits your product. Start with an account, understand the payment flow, and build one clear step at a time.

Build with the API

Use 17 implemented methods for accounts, addresses, balances, History, Transfers, fee quotes and Callbacks on Litecoin regtest. Other endpoints have explicit implementation labels.

Explore the API

Start with a widget

Try a payment button, a checkout form or a donation layout. Configure the design in your browser before connecting payment processing.

Configure a preview

Connect your store

Explore the planned WooCommerce, PrestaShop and OpenCart integrations. Plugin packages will follow the underlying payment API.

See integrations

1. Create your account

Open the dashboard and create an account. Save the Account ID and the one-time Transfer Key in a safe place. The ID identifies your account; the key authorizes protected actions. They are not interchangeable.

Create a development account

2. Explore receiving addresses

Account creation attempts to prepare a public keyset from our configured local Signer. Once ready, Add address on Litecoin Addresses and the public API can issue addresses without Unlock or a node. If preparation is pending, restore the original source, unlock the same account and retry Prepare Litecoin keys. An address is not proof of payment.

Understand address generation

3. Choose a customer experience

An online shop may need a form and an order reference. A creator may prefer a donation button. A physical counter may need a terminal view. The previews let you explore those layouts without sending money or saving customer details.

  • Online stores: try the form and mini cart layouts.
  • Creators and charities: explore a donation widget.
  • Custom apps and bots: begin with the versioned API reference.

4. Test before accepting funds

On local regtest, the confirmed-block scanner and mempool worker save receipts and spending observations. History shows Pending, Not seen, Recorded and Orphaned receipts alongside outgoing Transfers. The balance reader verifies node evidence and returns unavailable when it cannot establish the current state, not a guessed zero. Transfers reserve account-owned outputs and use the local Signer; Callbacks deliver receipt updates through a separate worker. The reviewed capacity and recovery defects have been corrected; bounded reads and local acceptance do not establish unlimited scale or production readiness. Invoices and automated forwarding are deferred; live mainnet acceptance is still pending. Do not connect this environment to a live storefront or send real funds.

Open the testing bench
BUILD WITH COINKUN

Your next step starts here.

Explore the dashboard, learn the API and develop with local test coins.