STORE PLUGIN · ON-SITE + HPP

Accept Crypto Payments with thirty bees 1.6

Native payment module and order history for thirty bees 1.6.

Download thirty bees 1.6 ZIP Follow the steps ↓

New adapters are initial integration builds. Complete installation and real-payment acceptance in your own staging store before enabling live traffic.

Choose the correct package and PHP environment

Shopping platform	PHP environment for this package
thirty bees >=1.6.0 <1.7.0	PHP 7.4.x / 8.0.x / 8.1.x / 8.2.x / 8.3.x; use the matching thirty bees distribution

Use the PHP version permitted by both this package and your exact core release. A plugin does not make an older store core compatible with newer PHP.

New packages use optional request_id deduplication and require MochiPay Web65 or later. Existing customers can keep their current plugins and API integrations.

01 · Prepare your MochiPay account

Create an account · activate a subscription.
Wallets · Enable a receiving wallet for every asset/network you will offer. Back up recovery material before checkout.
API Credentials · Keep the merchant API key and secret on the server. Never put credentials into checkout HTML or browser scripts.

02 · Install and enable the native gateway

Upload the ZIP in Modules > Add a new module, or extract mochipay into modules/mochipay. Install MochiPay.
The installer creates an unpaid waiting state. Open Configure, enter credentials, enable the gateway, choose the amount direction and save.
Allow the required countries, customer groups and fiat currencies in native payment restrictions. Keep Payment accepted configured correctly.
Use the matching PHP distribution for thirty bees 1.6. Clear the cache and use a single native order; split-cart orders are refused for review.

The English README inside each ZIP includes the exact paths, native configuration, dependencies and upgrade notes. Follow it for your platform.

03 · Review the ready-made defaults

Setting	Default value
MochiPay URL	https://mochi.bz
Payment mode	ON_SITE
Unique amount direction	UP
Selected currencies and networks	USDT/TRC20 · USDC/ERC20 · BTC/Bitcoin · ETH/Ethereum · SOL/Solana
Gateway enabled	Disabled until credentials and receiving wallets are ready.

Enter your API credentials, choose UP or DOWN for Unique amount direction, enable MochiPay and save. ON_SITE and all five methods are preselected; offer only methods with an active receiving wallet. Native payment-method and channel settings still apply.

04 · ON_SITE and HPP use the same payment

ON_SITE

Payment dialog in your store

The default ON_SITE dialog shows the exact amount, address, network, QR and payment status on your store domain.

HPP

MochiPay hosted payment page

HPP opens the MochiPay payment_url and returns to your store after checkout. Select HPP in the same gateway settings.

Reopening checkout or switching presentation reuses the saved payment order. No payment_mode parameter is added to the MochiPay API.

Try the public ON_SITE/HPP simulation →

05 · Verify a staging order before going live

Place a small staging order. Confirm the fiat total, selected asset, network and exact crypto amount before sending payment.
Verify that the server queries MochiPay and records the native paid state only after a matched PAID result. A return URL or callback body alone is not payment proof.
Test HPP, ON_SITE, reopening checkout and repeated notifications. Confirm that the same order is reused and payment completion is applied once.

These downloads have source/interface checks and simulated checkout validation. Full native-store installation and real paid checkout still require staging acceptance.

Understand server-side payment verification →

Troubleshooting and downloads

If the gateway is missing, check the exact store branch, PHP, cache, native method activation and channel restrictions. If an order remains pending, check credentials, active subscription, wallets and public callback reachability. Keep existing payment attempts when updating.

Download thirty bees 1.6 ZIP All store plugin packages →