Cryptoway Payment

In the block editor, add the “Cryptoway Payment” block and pick where the visitor pays: on the Cryptoway page, or right on your site (coin, address and QR code under the button). Everything else is in the block’s sidebar: a fixed amount or one the visitor picks or types, the button label, what to show after the payment, which payer fields to ask for.

On a classic editor, in a widget or in a theme, use the shortcode:

• [cryptoway amount="50" currency="USD"] — a fixed amount.
• [cryptoway amount="free" amounts="5,10,25" label="Support us"] — the visitor picks or types the amount.
• [cryptoway amount="free" pay="onsite"] — paid on your page: coin, address and QR code.
• [cryptoway amount="50" after="redirect" redirect="/thank-you/"] — a thank-you page after the payment.
• [cryptoway amount="free" fields="name,email,message"] — ask the payer for a name, an e-mail or a message.

Other parameters: amount="0" (the same as amount="free" : the visitor types the amount), min (the smallest amount a visitor may type, 1 by default), title (what the payment is for, shown on the invoice and in your list), message (shown after the payment), coins (the coin ids offered for payment on the page, e.g. USDTTRC20,BTC ), id (the button’s own name, see paid content below), class (your CSS class on the button’s wrapper).

A Cryptoway account with a project approved by Cryptoway (nothing works while it is in review). One project per site: Cryptoway accepts the keys only from the addresses in the project’s Allowed IPs, and the plugin shows a notice in your admin when it refuses them. WordPress 6.5 or later and PHP 8.1 or later, on a site reachable from the internet; on a network of sites (multisite), set the plugin up on each site separately. The site must be able to send e-mail for your alerts and for the access links of paid content.

Yes. In the block, set “After payment” to “Open hidden content on this page” and put the paid content into the block under the button — text, a link, a video, a file, a promo code. Before payment that content is not sent to the browser at all: it is not in the page, the feed or the site search (a search plugin that builds its own index may still pick it up). After the payment is confirmed it opens right in place of the button and stays open in that browser for the access period you set (30 days by default). The payer’s e-mail is always asked for, as the big checkouts do: a link that opens the content on any device goes there, and “Already paid?” under the button sends that link again. With the shortcode, put the content between the tags and give the button its own id : [cryptoway id="article-1" amount="3" access="30"]Your paid text[/cryptoway] . The block gets its id by itself.

Access is tied to the button, not to its texts: you can change the label, the price or the paid content of a block (or of a shortcode with its own id ) and those who paid keep their access. A page opened before you changed the price or the access period cannot be used to pay the old terms: the visitor is asked to reload it. Give each paid button on a page its own id ; when two share one, you see a warning above the second while you are logged in. The plugin does not create accounts or memberships. In Cryptoway Payment → Payments you can close a payer’s access by hand (after a refund) or open it for a payment you settled with the payer yourself.

Files you upload into the paid part are kept out of the public media lists and attachment pages, but anyone who has a file’s direct link can open it. For a file that must stay private, put a link to a private storage into the paid part instead. Keep footnotes out of the paid part: WordPress shows a post’s footnotes to every visitor.

The paid part is hidden by the plugin. If you deactivate it, WordPress shows the paid part of a block, and the text between the shortcode tags, to every visitor: take it off the page, or make the page private, before you deactivate the plugin.

By default the button looks like the other buttons of your theme. In the block’s sidebar (Looks) you can set the button colour, the text colour, the corner radius and make it full width; the shortcode takes the same: [cryptoway amount="50" color="#1f8a5b" text_color="#ffffff" radius="8" width="full"] . For payment on the page the QR code can be switched off in the block (Payment settings) or with qr="no" in the shortcode. “Frame around the form” (or frame="yes" ) puts the whole form in a card with a border and padding; a card is at most 30em wide, align the block wide or full to let it grow. A custom CSS class works too (the block’s Advanced panel, or class in the shortcode).

Every element has a stable class. The wrapper is .cwbtn , with modifiers .cwbtn--page / .cwbtn--onsite (where the payment happens), .cwbtn--full , .cwbtn--size-small / .cwbtn--size-large , .cwbtn--colored , .cwbtn--rounded , .cwbtn--framed . Inside the form: .cwbtn__form , .cwbtn__amount (the amount fieldset), .cwbtn__chips and .cwbtn__chip (suggested amounts; .cwbtn__chip--custom is “Other amount”), .cwbtn__input , .cwbtn__currency , .cwbtn__hint , .cwbtn__row and .cwbtn__label (coin and payer fields), .cwbtn__select , .cwbtn__button , .cwbtn__error . After the click: .cwbtn__panel , .cwbtn__status (plus --paid , --expired , --cancelled , --failed ), .cwbtn__amount-line , .cwbtn__pay , .cwbtn__field , .cwbtn__field-label , .cwbtn__field-value , .cwbtn__copy , .cwbtn__timer , .cwbtn__qr , .cwbtn__link , .cwbtn__again . The button colour, text colour and radius set in the block come as the CSS variables --cwbtn-accent , --cwbtn-accent-text and --cwbtn-radius ; the frame’s radius is --cwbtn-frame-radius . Put your rules in Appearance → Customize → Additional CSS or in your theme.

Yes. The form texts (the button, the amount label, “Other amount”, the coin and payer fields) are edited right in the block, or with the shortcode parameters label , amount_label , other_label , coin_label , name_label , email_label , message_label . The status lines shown after the click — “Waiting for your payment”, “Payment received, confirming”, “Your payment is being checked” and so on — are in Cryptoway Payment → Payment statuses: leave a field empty to keep the standard wording (in the site language once a translation is available), or type your own.

Visitors pay with the coins Cryptoway accepts; the plugin refreshes that list once a day. At the moment: USDT on Tron (TRC-20), Ethereum (ERC-20), BNB Smart Chain (BEP-20), Polygon, Arbitrum, The Open Network and Solana; USDC on Ethereum (ERC-20) and Solana; BTC; ETH on Ethereum and Arbitrum; LTC; TRX; BNB on BNB Smart Chain; POL; SOL; DOGE; GRAM on The Open Network. On the Cryptoway payment page the visitor picks the coin there. In Settings you can allow fewer coins, and a button can offer its own list with coins="..." .

There are two. The Cryptoway fee is charged on each successful payment; rates are on the pricing page , and in your project’s Fees and markup you choose whether you or the payer pays it, or both share it. The network fee is added by the payer’s wallet on top of the amount.

Less: the payment is marked Underpaid at once, with what was invoiced, what arrived and what is missing. If the rest arrives in time, it becomes Paid. More: the payment is marked Paid. Above a small tolerance, the history shows the overpaid amount to return from your Cryptoway account. Nothing within the time to pay: the payment expires. Late, after the time ran out: the payment is marked “Paid after the time ran out” for your review; the money is with Cryptoway.

The visitor chooses a coin and a network, and the plugin asks Cryptoway for an invoice with that coin. Cryptoway answers with the address and the exact amount in the coin, which the page shows with a QR code and a timer. The page checks the status by itself and shows “paid” once Cryptoway confirms the transfer.

No, there is no test mode. Make one real payment a little above the coin’s minimum deposit (about 1 USDT) and pay from your own wallet. Network and Cryptoway fees apply.

From your Cryptoway account, as a new transfer to an address the payer gives you. The plugin does not send refunds.

The keys are stored in the plugin’s settings on your site. The Secret key is not shown again, not sent (it only signs requests) and not logged.

When a visitor presses the button, the plugin asks the Cryptoway API (api.cryptoway.com) for an invoice: the amount and currency, what the payment is for (its title, the payment number and your site’s name), the coin if the visitor chose one on your page, the time to pay, the address of your site for the notification and for the return. When the payment is paid, expired or cancelled, Cryptoway sends a notification to your site, and the plugin reads the invoice back from the API. The plugin also reads the invoice when you press “Check with Cryptoway”, when a visitor’s page checks the status, and every 10 minutes for open payments. After you save the keys, the plugin asks the API for the project profile (to get the callback key that signs notifications) and for the list of coins.

Nothing about the visitor is sent: not the name, e-mail or message you may ask for, and not the IP address. Cryptoway’s Terms and Privacy policy apply to the service.

Payment notifications arrive at https://your-domain/wp-json/cryptoway-button/v1/webhook . It must be reachable from the internet. The status check every 10 minutes needs WP-Cron, which runs on site visits unless a server cron job calls it. Open the payment in Cryptoway Payment → Payments and pres