Plisio is a cryptocurrency payment gateway that enables businesses to accept payments in over 15 cryptocurrencies, including Bitcoin, Ethereum, and Litecoin.
Plisio is a cryptocurrency payment gateway that enables businesses to accept payments in over 15 cryptocurrencies, including Bitcoin, Ethereum, and Litecoin. On Nagent, Plisio is exposed as a fully-configurable payment processing integration that any agent can call — 12 actions, and API key authentication. No code is required to wire Plisio into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Plisio to automate the kinds of tasks payment processing teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Plisio into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Plisio, with input parameters and output schema. Drop these into any step of an agent built in Helix.
PLISIO_CREATE_INVOICETool to create a new cryptocurrency payment invoice with Plisio. Returns transaction ID and invoice URL for payment. For white-label accounts, includes additional fields like wallet hash, QR code, and commission details. Use when you need to generate a payment request for cryptocurrency transactions.
Input parameters
Auto-fill invoice email. Customer will be asked to provide email for notifications.
Payment amount in cryptocurrency (float value as string). Skip this field if using source_currency and source_amount for fiat conversion.
Plisio's internal field to identify integration plugin
Plisio's internal field to identify integration plugin version
Cryptocurrency code (e.g., 'BTC', 'ETH'). One of the cryptocurrencies supported by Plisio. If not set, one of the active cryptocurrencies from API settings is selected automatically.
Invoice language code. Currently only 'en_US' is supported.
Invoice expiration interval in minutes
Merchant internal order name for identification
Merchant invoice description for the customer
Full URL to receive invoice updates via POST request. If not set, uses the default Status URL from API settings.
Merchant internal order number. Must be unique for each new order in your store.
Payment amount in fiat currency (float value as string). Use with source_currency for fiat-to-crypto conversion.
Return existing invoice instead of error if order_number already exists. Default is 0 (disabled).
Fiat currency code for conversion (e.g., 'USD', 'EUR'). Use with source_amount instead of amount for fiat-to-crypto conversion.
'To the site' button link when invoice payment fails
Comma-separated list of allowed cryptocurrencies for payment. Customer can select one from this list.
Full URL for failed invoice callback. Add json=true to URL for JSON response format.
If true, redirects to Plisio's invoice page instead of returning JSON (not supported for white-label shops)
'To the site' button link when invoice is paid
Full URL for successful invoice callback. Add json=true to URL for JSON response format.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PLISIO_ESTIMATE_FEETool to estimate network fee for a withdrawal transaction to specific address(es). Use when calculating transaction costs before creating a withdrawal.
Input parameters
Amount or comma-separated amounts corresponding to each address for mass withdrawal
Fee plan selection: 'normal' for balanced cost and speed, 'priority' for faster confirmation at higher cost
Cryptocurrency ID from Plisio supported cryptocurrencies (e.g., 'BTC', 'ETH', 'USDT')
Wallet address or comma-separated addresses for mass withdrawal fee estimation
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PLISIO_GET_BALANCE_BY_CURRENCYTool to get the balance for a specific cryptocurrency in your Plisio account. Use when you need to retrieve the balance of a particular crypto asset.
Input parameters
ID column from one of the supported cryptocurrencies supported by Plisio (e.g., 'BTC', 'ETH', 'USDT')
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PLISIO_GET_COMMISSIONTool to estimate the total cost including network fee and Plisio commission for a transaction. Returns detailed breakdown of commission, fee, and fee plan options for the specified cryptocurrency and amounts.
Input parameters
Operation type: 'cash_out' for single withdrawal to one address, 'mass_cash_out' for batch withdrawal to multiple addresses.
Amount or comma-separated amounts that will be sent. For mass withdrawal, amounts should correspond to addresses in the same order. Use decimal string format (e.g., '0.3', '1.5,2.0').
Fee plan type for transaction processing.
Cryptocurrency identifier (e.g., 'BTC', 'ETH', 'USDT'). Must be one of the supported cryptocurrencies by Plisio.
Wallet address or comma-separated addresses when estimating fee for mass withdrawal. For single withdrawal use one address, for mass withdrawal separate multiple addresses with commas.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PLISIO_GET_CURRENCY_RATETool to retrieve list of supported cryptocurrencies with current rates filtered by fiat currency. Use when you need exchange rate information for cryptocurrencies in a specific fiat currency.
Input parameters
Fiat currency code for exchange rates (e.g., 'USD', 'EUR', 'GBP'). See https://plisio.net/documentation/appendices/supported-fiat-currencies for all 168 supported currencies.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PLISIO_GET_FEE_PLANSTool to retrieve available fee plans for a given cryptocurrency. Specify a currency symbol like 'BTC', 'ETH' to get fee plan details.
Input parameters
Cryptocurrency symbol, e.g., 'BTC'
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PLISIO_GET_FEE_PLANS2Tool to get available fee plans for a specific cryptocurrency. Returns fee values and configuration like gas limits for Ethereum-based coins or confirmation targets for Bitcoin. Use when you need to determine transaction fee options before creating or sending a transaction.
Input parameters
ID column from one of the supported cryptocurrencies supported by Plisio (e.g., 'BTC', 'ETH', 'USDT')
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PLISIO_GET_INVOICETool to retrieve detailed information about a specific invoice by its ID. Use when you need to check invoice status, payment details, or transaction information.
Input parameters
Invoice ID to retrieve details for
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PLISIO_GET_INVOICE_EMAILTool to retrieve invoice details by email ID. Use when you need to fetch detailed information about a specific invoice using the invoice ID and payer's email address.
Input parameters
Invoice unique identifier
Payer's email address associated with the invoice
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PLISIO_GET_SHOPTool to retrieve shop information by API key. Returns details about the shop associated with the current API credentials.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PLISIO_GET_TRANSACTIONSTool to retrieve a list of transactions and invoices. Use after authenticating with your API key to fetch historical operations with optional filters and pagination. Example: GetTransactions(status='paid', limit=20).
Input parameters
End date as UNIX timestamp (inclusive)
Page number (0-indexed)
Filter by operation type (withdraw, invoice, mass_withdraw)
Number of results per page (max 100)
Start date as UNIX timestamp (inclusive)
Filter by operation status (pending, paid, cancelled, error, expired, processing)
Filter by cryptocurrency code, e.g., 'BTC'
Filter by your own order ID
Filter by your own order name
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PLISIO_LIST_CURRENCIESTool to retrieve a list of supported cryptocurrencies with their rates and information. Use after API credentials are configured to get current exchange rates, commission percentages, and operational status for all available coins.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 80 agents privately built on Nagent that already use Plisio.
Build on Nagent
Connect Plisio to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Plisio, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Plisio is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Plisio is connected, you configure its 12 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Plisio steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Plisio event fires, the agent kicks off automatically.
Every Plisio action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Plisio ships with 12 pre-built payment processing actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Plisio together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Plisio-based workflows tailored to your business.