Terms of Service

ON THIS PAGE+

1. About These Terms 2. P2Flux Services 3. Non-Custodial Infrastructure 4. Wallets and Blockchain Transactions 5. Merchant and Platform Responsibilities 6. Payment Transactions 7. Recurring Payments 8. Payments by AI Agents 9. Fees and Network Costs 10. Refunds and Cancellations 11. API / SDK and Software Use 12. Third-Party Wallets and Networks 13. Lawful Use 14. Intellectual Property 15. Service Availability 16. Changes to the Service 17. Disclaimers 18. Limitation of Liability 19. Suspension or Restriction 20. Changes to These Terms 21. Governing Law 22. Contact

1. About These Terms

These Terms of Service ("Terms") govern access to and use of the P2Flux software, application programming interfaces, software development kits, smart contracts, documentation and related infrastructure (together, the "Services"), provided by Modulout LLC, a Wyoming limited liability company, operating as P2Flux ("P2Flux", "we", "us" or "our").

By accessing or using the P2Flux Services — including integrating, calling or deploying against them — you agree to these Terms. If you do not agree, do not use the Services. If you are using the Services on behalf of a company or other organisation, you confirm that you have authority to accept these Terms on its behalf, and "you" refers to that organisation.

Payers using payment links. A payer who starts a subscription through a payment link agrees to these Terms as they apply to payers, by signing on the payment page where they are shown. They cover the payer’s authorisation, the renewals P2Flux initiates under it, retries, fees, revocation, and the difference between stopping recurring collection and cancelling the payer’s agreement with the merchant, as set out in section 7. The P2Flux service fee is paid by the merchant out of each payment; the payer pays the amount signed and, for each renewal, the network cost at the time, never above the maximum shown when signing.

These Terms describe what the Services do and do not do. They are not legal, tax, financial or regulatory advice.

2. P2Flux Services

P2Flux provides software and infrastructure for blockchain-based payments. Depending on the features you integrate, the Services may provide:

• creation of payment requests and payment parameters;
• verification of payment transactions;
• splitting of a payment between the recipient addresses specified through the integration, including the P2Flux service fee;
• execution of recurring payments under an authorisation given by the payer;
• collection of recurring payments created through a payment link, within the limits the payer authorised;
• confirmation of transaction status back to your system.

Payment transactions execute on blockchain networks. P2Flux does not operate those networks and does not control whether, when or in what order a network confirms a transaction.

P2Flux is not the buyer or the seller in transactions made using the Services, does not provide the goods or services being purchased, and does not operate your store, marketplace, product or underlying business.

Today the Services support payments in USDC on the Base network, both as one-time payments and as recurring payments executed under an authorisation the payer signs in their own wallet using EIP-712. A hosted checkout is provided for the payer-facing step, and P2Flux operates server-side infrastructure alongside the smart contracts that execute settlement. Where a supported flow offers it, the blockchain network cost of a payment may be paid in the payment currency instead of the network’s native currency.

P2Flux does not exchange or convert between crypto-assets and fiat currency, does not provide banking services, and does not operate the blockchain networks, wallets, node providers or RPC endpoints a payment depends on. Their availability is outside the control of P2Flux and is not guaranteed.

3. Non-Custodial Infrastructure

P2Flux does not hold a merchant balance and does not take custody or possession of payment funds. Payments are executed through blockchain transactions and settle to the wallet addresses specified through the integration.

P2Flux may provide transaction logic, verification and execution without becoming the custodian of the underlying funds. In particular:

• P2Flux does not provide bank accounts.
• P2Flux does not provide stored merchant balances.
• There is no P2Flux withdrawal or payout process for merchant payment funds, because those funds are never held by P2Flux.
• P2Flux does not provide a custodial wallet as part of the current payment Services.

P2Flux may receive its service fee as part of the same blockchain transaction that pays the merchant. Receiving a service fee does not create a merchant balance, a custodial relationship, or any obligation on P2Flux to hold, forward or return the merchant's payment funds.

You are responsible for securing and controlling your own wallets, keys and signing infrastructure. P2Flux cannot access, restore or recover a private key or recovery phrase, and cannot reverse a transaction that a network has already confirmed.

4. Wallets and Blockchain Transactions

Payers use their own wallets. Merchants receive payments into wallets they control. P2Flux does not control the payer's wallet or the merchant's wallet and does not sign on their behalf outside the mechanisms described in these Terms.

Blockchain transactions may be irreversible once confirmed. An incorrect address, an incorrect amount, an incorrect asset or an incorrect network configured through your integration may result in a loss that cannot be undone by P2Flux.

Network conditions, congestion, reorganisations, protocol changes, node availability and third-party infrastructure may affect whether and when a transaction confirms. P2Flux does not guarantee confirmation times.

5. Merchant and Platform Responsibilities

P2Flux is infrastructure and is not a party to the underlying commercial transaction. The merchant or platform, not P2Flux, is responsible for the products, services, pricing, delivery, customer relationship, refunds, taxes and legal obligations associated with its business.

You are responsible for:

• what you sell and how you fulfil it;
• the accuracy of the payment parameters your integration submits, including amounts, assets, networks and recipient addresses;
• your own consumer, contractual, tax and regulatory obligations;
• the information and disclosures you present to your customers at checkout;
• your own records of orders, customers and subscriptions.

P2Flux is not responsible for disputes between merchants and buyers, between marketplace buyers and sellers, or between platforms and their users. If P2Flux later introduces a service that addresses such situations, that service will be governed by its own terms.

You are also responsible for the sanctions, export-control and other compliance obligations that apply to your own business and your own customers, and for the terms, privacy notice and other disclosures your website or application is required to provide.

You are responsible for securing the wallets, keys and signing infrastructure used with your integration, as described in section 3.

6. Payment Transactions

A payment is initiated through your integration and authorised by the payer from the payer's own wallet. Where the Services split a payment, the split is executed as part of the payment transaction, sending the merchant amount to the merchant address and the service fee to the P2Flux address.

A transaction that has been submitted to a network is not the same as a transaction that has settled. Status information provided by the Services reflects the state observed at the time it is reported.

P2Flux does not guarantee that a payment will succeed. A payment may fail, be rejected by the payer, or remain unconfirmed for reasons outside the control of P2Flux.

7. Recurring Payments

For recurring payments, the payer creates and approves an authorisation from their own wallet. Renewals may then be executed under that authorisation, without P2Flux holding subscription funds between billing periods.

A P2Flux relayer may submit a renewal transaction to the network. Where a relayer initially pays network gas in order to submit the transaction, that cost may be reimbursed through the renewal flow, so that the payer ultimately bears the applicable blockchain gas cost. The merchant receives settlement through the blockchain transaction.

The payer may cancel or revoke the authorisation using the mechanism supported by the Services. Once revoked, further renewals under that authorisation will not execute. Revocation does not affect renewals that have already settled.

Payment links. Where a merchant offers a subscription through a payment link, P2Flux keeps the payer’s signed authorisation and submits each renewal itself, instead of waiting for the merchant’s system to ask. P2Flux may submit renewals only within the amount, billing frequency and other limits authorised by the payer. A merchant cannot increase the recurring amount or shorten the billing period without a new authorisation from the payer.

If a renewal cannot be collected, P2Flux may try again during a retry window equal to the shorter of 25% of the billing period or three days after the scheduled renewal; after that the renewal is skipped and is not collected later. After three renewals in a row that could not be collected because of the payer’s wallet (for example insufficient balance or allowance), the subscription ends. If a renewal becomes due and remains uncollected, for any reason, for at least the number of days the merchant set for the link (7 unless the merchant chose otherwise, at most 90), P2Flux pauses collection, at the latest when the retry window of the following renewal ends.

The merchant may pause or stop P2Flux’s collection of future renewals. The merchant may resume a paused or stopped subscription only while the payer’s authorisation remains valid; a stopped subscription that is not resumed ends after three billing periods. Only the payer can revoke the wallet-level authorisation.

Stopping or revoking recurring collection through P2Flux does not by itself determine whether the payer’s underlying subscription or other agreement with the merchant has been cancelled. The merchant remains responsible for cancellation, refund and consumer-rights obligations relating to the underlying goods or services.

P2Flux does not hold funds between periods for payment-link subscriptions: each renewal is a blockchain transaction from the payer’s wallet to the merchant’s wallet, with the P2Flux service fee taken in the same transaction. P2Flux does not guarantee that any renewal will be collected; a renewal may fail because of the payer’s balance or allowance, network conditions or the availability of the Services.

The description a merchant adds to a payment link is the merchant’s own statement. It is shown to payers as not verified by P2Flux, and the merchant is responsible for it, including for not putting sensitive or unnecessary personal data in it.

P2Flux Gate (Telegram). P2Flux Gate is a Telegram bot that admits members of a private Telegram channel or group who subscribe through a P2Flux subscription link, and removes them when the subscription stops. The channel owner is the seller: the subscription is between the channel owner and the member, and P2Flux provides the payment link and the bot that manages access.

Access follows the subscription. A member is admitted once the first period is collected, and is removed when a renewal could not be collected because of the member’s wallet, or when the subscription was cancelled, paused by the channel owner or reached its end — in each case after the period already paid. A short outage of P2Flux removes nobody; a member whose renewals stay uncollected for two periods in a row, or whose collection was paused after an uncollected period, is removed until a renewal is collected again.

The bot manages only people who join through it; people admitted another way are not checked. The channel owner keeps the channel private, gives the bot the rights it needs, and is responsible for the channel’s content and for following Telegram’s rules.

Telegram can limit or remove the bot at any time. Nobody new is then admitted and nobody is removed; existing subscriptions are not affected. P2Flux is not liable for Telegram’s decisions. A member who wants a refund contacts the channel owner: payments go on-chain directly to the channel owner’s wallet, and P2Flux never holds them.

8. Payments by AI Agents

The Services include software that lets a website or API ask automated clients, such as AI agents and crawlers, to pay for a request using the open x402 protocol. The seller decides what is paid for and the price. The payer is whoever controls the wallet the agent pays from. P2Flux provides the software that prepares and submits the payment; it is not a party to the sale between the seller and the payer.

Payment per request. The payer signs a transfer for the price of one request. The payment settles on the blockchain to the seller, with the P2Flux service fee taken in the same transaction. One payment gives access to one response. A payment that has been used is refused if it is presented again. If the payer does not receive the response after the payment has settled, for example because a connection was lost, the payment is not reversed by P2Flux; any remedy is a matter between the payer and the seller.

Prepaid balance. Where offered, a payer may place an amount in advance in a payment-channel smart contract of the x402 protocol and then pay individual requests with signed vouchers. That contract is public, open-source software that P2Flux did not write and does not own, operate or control. P2Flux never holds the prepaid amount and cannot withdraw it: under the contract it can only be paid to the seller for vouchers the payer has signed, or returned to the payer. The payer can withdraw the unused amount through the contract at any time, subject to the waiting period the contract applies. P2Flux may also return the unused amount when the payer asks for it through the seller’s site, and may return larger unused amounts automatically after a period of inactivity; both are a convenience and not an obligation. Amounts owed to the seller are paid out in batches, with the P2Flux service fee taken in the payout transaction.

What sellers should know. Recognising an automated client is imperfect. A client that presents itself as an ordinary browser may not be asked to pay, search engines are not asked to pay, and content served from a cache or content delivery network before it reaches the P2Flux software is not protected. P2Flux does not guarantee that any agent will pay, or any amount of revenue. The seller is responsible for the content or service it sells, for its prices, and for its own terms with its customers.

Directory. A seller may choose to have its site listed in a public P2Flux directory so that agents can find it. The listing consists of information the site itself publishes: its name, description, address, prices and the titles of recent paid items. The seller can remove the listing at any time by switching the option off. A listing is not an endorsement. P2Flux may decline or remove a listing.

Software that pays on your behalf. P2Flux also publishes software, including an MCP server, that lets a person’s own AI assistant pay sellers. It runs on your device and creates a wallet there. You alone hold the key to that wallet; P2Flux never receives it and cannot recover it or the funds if the device or the key is lost. Spending limits are a feature of the software, not a guarantee. The pages and other content your assistant retrieves come from third parties, and P2Flux is not responsible for them or for what your assistant does with them. Keep only small amounts in such a wallet.

The fees for payments by AI agents are published with the other fees described in section 9.

9. Fees and Network Costs

P2Flux charges a service fee for use of the Services, as published for the relevant payment type. The service fee is taken as part of the payment transaction rather than invoiced against a held balance.

Blockchain network fees, commonly referred to as gas, are separate from the P2Flux service fee, are set by the network rather than by P2Flux, and may vary.

P2Flux may change its fees. Changes will be published before they take effect for new transactions.

10. Refunds and Cancellations

Because P2Flux does not hold merchant funds, a refund is a new transaction made by the merchant from a wallet the merchant controls, not a reversal of the original payment by P2Flux. Where the Services provide refund support, they provide the mechanism; the decision, the funds and the obligation remain the merchant's.

Private payments. A payment made privately through Hinkal (an option a merchant may offer) is paid by Hinkal’s contract, not by the buyer’s own wallet. P2Flux therefore does not prepare a refund for it: money sent back to that contract would not reach the buyer. A merchant who wants to refund such a payment sends it to an address the buyer gives them, at the merchant’s own discretion and risk. Hinkal charges the buyer its own fee for the private payment, in addition to the price.

Cancellation of a recurring payment is described in section 7. Your own refund and cancellation policy, and any consumer rights applicable to your business, remain your responsibility.

Stopping or revoking recurring collection through a payment link is described in section 7. Cancellation of the underlying purchase or subscription, and any resulting refund rights, are matters between the payer and the merchant, subject to applicable law.

11. API / SDK and Software Use

Subject to these Terms, P2Flux grants you a limited, non-exclusive, non-transferable, revocable right to use the APIs, SDKs and documentation to integrate the Services into your own product.

You must not: interfere with or attempt to circumvent rate limits, authentication or security controls; attempt to gain unauthorised access to the Services or to other users' data; use the Services to build a substantially similar competing payment infrastructure using P2Flux proprietary materials; or remove or obscure proprietary notices.

You are responsible for the security of any credentials issued to you and for all activity that occurs under them.

12. Third-Party Wallets and Blockchain Networks

The Services depend on third-party wallets, blockchain networks, token contracts, node providers and other infrastructure that P2Flux does not own or control. Their availability, behaviour, fees and terms are outside the control of P2Flux, and P2Flux is not responsible for them. Your use of a third-party wallet or network is subject to that third party's own terms. This includes Hinkal, whose software and servers make the optional private payments: P2Flux does not operate Hinkal, does not hold or control a buyer’s Hinkal balance, and is not responsible for Hinkal’s availability, fees or conduct.

13. Lawful Use

You may not knowingly use the Services:

• for unlawful activity;
• to violate applicable law or applicable sanctions;
• to facilitate fraud;
• to steal or misappropriate funds;
• to attack, overload or abuse P2Flux infrastructure;
• to interfere with other users, wallets or networks;
• in a way that infringes the rights of others.

You are responsible for determining whether your own use of the Services is lawful, and for meeting any legal requirements that apply to your business and your customers.

P2Flux may use technical security, fraud-prevention, abuse-prevention and compliance controls to protect the Services. Merchants remain responsible for compliance obligations applicable to their own business and customers.

Sanctioned and restricted wallets. P2Flux does not process payments, subscriptions, refunds or payouts involving a wallet that appears on the U.S. OFAC Specially Designated Nationals list, whether as payer or as the merchant’s receiving wallet, nor for a paying wallet the token’s issuer has restricted. Where P2Flux takes part, such payments are refused before any transaction is submitted. A payment a listed wallet sends directly cannot be stopped by P2Flux; P2Flux flags it to the merchant, keeps a record of it and will not prepare or submit any further movement of it. P2Flux may keep records of such matches and report them where the law requires. For a private payment through Hinkal, the private-payment page checks the wallet the buyer connects against the OFAC list before the payment is built (a best-effort check: the private balance may have been funded from another wallet, and a payment can also be made through Hinkal’s own app without this page); on the blockchain the payer is then Hinkal’s contract, so no check of the buyer’s wallet is possible when the payment is verified, and Hinkal applies its own checks to its users. Merchants remain responsible for their own sanctions compliance, including funds that reach their wallet outside P2Flux.

14. Intellectual Property

P2Flux and its licensors retain all rights in the Services, including the software, APIs, SDKs, documentation, design, name and marks. These Terms do not transfer any ownership. You retain all rights in your own product, content and data. Open-source components, where included, are governed by their own licences.

15. Service Availability

The Services are provided without a guaranteed level of availability unless separately agreed in writing. Maintenance, network conditions, third-party outages and security measures may interrupt or degrade the Services.

16. Changes to the Service

P2Flux may add, change, deprecate or remove features, endpoints, supported assets or supported networks. Where a change would materially affect an existing integration, P2Flux will aim to give reasonable advance notice through the documentation or another appropriate channel.

17. Disclaimers

To the maximum extent permitted by law, the Services are provided "as is" and "as available", without warranties of any kind, whether express or implied, including any implied warranties of merchantability, fitness for a particular purpose, non-infringement, or that the Services will be uninterrupted, secure or error-free.

P2Flux does not provide investment, tax, accounting or legal advice, and does not warrant the value, stability or continued availability of any token, asset or network.

18. Limitation of Liability

To the maximum extent permitted by law, P2Flux will not be liable for indirect, incidental, special, consequential or punitive damages, or for lost profits, lost revenue, lost business, lost data, lost tokens or loss of goodwill, arising out of or relating to the Services.

To the maximum extent permitted by law, P2Flux will also not be liable for loss caused by the failure, unavailability, congestion, reorganisation or misbehaviour of a public blockchain network, a token contract, a third-party wallet, a node or RPC provider, or other third-party infrastructure outside the reasonable control of P2Flux.

To the maximum extent permitted by law, the total aggregate liability of P2Flux arising out of or relating to the Services will not exceed the greater of (a) USD 500, or (b) the total P2Flux service fees actually received in connection with the relevant use of the Services during the twelve months immediately preceding the event giving rise to the claim.

For that calculation, “P2Flux service fees” means the service fees actually received by P2Flux. It does not include the payment amount itself, funds paid by a buyer, amounts settled to a merchant, or blockchain network costs, none of which are P2Flux revenue and none of which P2Flux holds.

Nothing in these Terms excludes or limits liability for fraud or wilful misconduct, or any other liability that cannot lawfully be excluded or limited under applicable law.

19. Suspension or Restriction of Access

P2Flux may suspend or restrict access to the Services, including API access, where there is evidence of:

• abuse of the Services or infrastructure;
• fraud;
• a security attack or attempted attack;
• a breach of these Terms;
• a requirement under applicable law or a binding legal order.

Where practical and lawful, P2Flux will inform you of a suspension and of what is required to restore access. A suspension of API access does not affect funds, because P2Flux does not hold them.

20. Changes to These Terms

P2Flux may update these Terms. The date of the current version is shown at the top of this page. Where a change is material, P2Flux will aim to give reasonable notice. Continued use of the Services after a change takes effect constitutes acceptance of the updated Terms.

21. Governing Law and Jurisdiction

These Terms, and any dispute arising out of or relating to these Terms or the Services, are governed by the laws of the State of Wyoming, United States, without regard to its conflict-of-law principles.

The state and federal courts located in the State of Wyoming have exclusive jurisdiction over any such dispute, and you and P2Flux each submit to the personal jurisdiction of those courts.

This section does not override mandatory rights, protections or remedies that applicable law does not permit to be waived, and does not deprive you of the protection of mandatory consumer law where that law applies to you.

22. Contact

The Services are provided by Modulout LLC, a Wyoming limited liability company, operating as P2Flux.

Legal and privacy enquiries: contact@p2flux.com
Integration enquiries: integration enquiry form