This page lists what people can currently do with PayCow, what each flow requires, and what the system does not claim to do. No animation. No demo statistics. No hidden feature language.
Language: EnglishProduct scope: current implementationLast reviewed: October 2026
A merchant can register with a company name, email address, password, business sector, company size, and an email verification code.
New merchant accounts can choose what they plan to use PayCow for. The dashboard can then hide unrelated pages.
A merchant can skip the setup assistant, reopen the Customize page later, show or hide pages, move them, and assign them to navigation categories.
Dashboard preferences are attached to the merchant account, not only to one browser.
A merchant signs in to a protected dashboard and can sign out from the sidebar.
Password reset uses a one-time code sent by email. Rate limits apply.
Account access can be suspended or restricted. A suspended account cannot use protected merchant features.
PayCow offers Trial, Starter, Plus, Pro, Scale, and Enterprise subscription handling. Available limits and prices are shown on the pricing and subscription screens.
Subscription status and volume limits can prevent new payment sessions from being created.
02
Creating and tracking crypto payments
Merchants can create hosted payment sessions through the dashboard or server API.
The implemented payment asset is USDT on TRON (TRC20) and Ethereum (ERC20).
A payment session contains a reference, requested amount, exact payable amount, destination wallet, network, status, checkout link, and expiry time.
PayCow monitors supported blockchain transfers and updates payment states.
Payment states can include pending, detected, confirming, processing, paid, expired, rejected, and failed.
Merchants can view recent payments and a larger transaction ledger.
Transaction search supports filters and pagination. Merchant transaction data can be exported as CSV.
A merchant can manually reject an eligible payment from the dashboard.
Idempotency keys can be used to avoid intentionally creating the same payment session more than once.
PayCow uses subscription fees instead of deducting a PayCow percentage commission from each merchant payment. Blockchain network fees remain separate.
03
What the paying customer sees
The customer opens a hosted PayCow checkout page for one payment session.
The checkout shows the amount, supported network, destination address, payment reference, expiry information, and payment status.
The customer sends funds with an external wallet. PayCow does not hold the customer's wallet keys.
The page can display detection and confirmation progress while the payment is being processed.
If a customer believes they underpaid or their transfer was not recognized, they can submit a payment claim with transaction details, contact information, a description, and optional evidence.
An accepted claim can open a 72-hour Awake Mode review window. It is not an automatic refund and does not guarantee approval.
A checkout link can expire. Sending funds late or using the wrong network can require manual review and can result in loss.
04
Donation pages
Eligible merchants can create a public page at /donate/your-name.
The merchant can add a display name, profile image, biography, donation purpose, description, and optional funding goal.
The public page can show goal progress based on confirmed donations.
Supporters can choose a suggested amount or enter their own amount within the allowed range.
Supporters can choose an available TRC20 or ERC20 destination, add an optional name, and leave an optional note.
The supporter continues from the donation page to the normal PayCow checkout.
A supporter can request a monthly email reminder on a chosen day. This is a reminder, not an automatic recurring charge.
The reminder requires confirmation after a paid donation and includes a cancellation link.
Short months use their final day when the chosen reminder day does not exist.
The dashboard shows confirmed donation totals and recent supporter messages.
Merchants can use a private, rotatable browser-source link for OBS or Streamlabs donation alerts.
The merchant can decide whether supporter notes are shown in stream alerts.
05
Storefronts and branding
A merchant can configure a public storefront with its own slug.
The storefront can include a headline, description, support email, and merchant identity.
The merchant can publish or unpublish the storefront.
A published storefront can list eligible digital products and show product availability.
Visitors can browse and paginate storefront products.
Store branding controls let merchants change customer-facing merchant name, business information, and checkout biography.
06
Digital products and order delivery
Eligible merchants can create digital products with a title, description, price, network preference, category, and destination wallet.
A product can deliver a file or a license key after an eligible payment is completed.
Merchants can upload product cover images and select cover themes.
Products can be activated, deactivated, edited, deleted, published to a storefront, and listed in the marketplace when eligible.
File downloads use access tokens with expiry and download-count checks.
License-key inventory can be tracked and assigned after payment.
Fulfillment records reduce accidental repeat delivery by the same delivery routine.
Delivery emails depend on the configured email service and are not a guarantee that every recipient provider will place a message in the inbox.
The implemented delivery system is for digital files and license keys. It is not a shipping, warehouse, or physical delivery service.
07
Public marketplace
Visitors can browse published, eligible digital products from multiple merchants.
Marketplace browsing supports text search, categories, category filters, pagination, and sorting.
Sorting options include newest, popularity, and lowest price.
Listings can show merchant information, product information, price, category, cover art, and availability.
A visitor opens a product page and creates a checkout session before receiving a digital order.
Marketplace policies and acceptable-use rules apply to sellers and listings.
08
Wallets and non-custodial settlement
PayCow is designed as non-custodial payment infrastructure.
Merchants configure external destination wallets. PayCow does not provide a custodial merchant balance for customer payments.
A merchant can maintain multiple destination wallets with labels, serial numbers, provider information, and a primary-wallet choice.
The dashboard can display supported on-chain wallet balances when the network and address type allow it.
Exchange-managed pooled wallets and smart-contract systems may not expose a user's exchange balance through a normal address balance lookup.
PayCow maintains a public wallet-blacklist lookup and can prevent reuse of wallets associated with banned merchant records.
Merchants remain responsible for wallet security, private keys, network selection, and access to their external wallet provider.
09
Merchant dashboard
The dashboard provides an overview of transaction count, volume, customers, subscription usage, recent payments, and wallet information.
Pages cover payment links, transactions, donations, storefront, branding, digital delivery, wallets, subscription plans, API keys, webhooks, API logs, support, and navigation customization.
Merchants can hide pages they do not use without deleting the underlying data.
Merchants can reorder pages and move them between Main, Payments, Sell & Grow, Account, Developer, and Support categories.
The Overview page cannot be hidden, and the Customize page remains available so the navigation can be restored.
The dashboard can show subscription expiry or restriction notices.
API secrets are only revealed in the intended one-time credential flow and are not returned by the normal profile endpoint.
10
APIs, webhooks, SDKs, and plugins
Merchant server-to-server payment requests use an API key and API secret.
The API can create payment sessions and return merchant-owned payment status information.
Merchants can configure an HTTPS webhook endpoint and receive signed event payloads.
Webhook events include identifiers, timestamps, and an HMAC-SHA256 signature that the merchant should verify against the raw request body.
Supported events include payment status events and webhook tests.
The dashboard contains webhook settings, webhook delivery history, and API request logs.
Documentation pages include API guidance, marketplace and delivery guidance, SDK pages, and integration examples.
The repository contains PHP, JavaScript, and Java SDK projects, plus WooCommerce and WHMCS integration projects.
The presence of integration source code does not guarantee compatibility with every hosting environment or third-party version.
11
Support, notices, and public information
Authenticated merchants can use dashboard support chat.
The public support hub provides contact routes and links to policy and safety information.
Public pages include announcements, careers, blog posts, pricing, product explanations, technical documentation, and policies.
Career applications can include uploaded application material where the job flow allows it.
Operational email features depend on the configured email provider. A message being accepted by that provider is not proof of delivery to the recipient's inbox.
12
Affiliate portal
Affiliates have a separate registration and login area.
An affiliate can use a referral relationship connected to merchant registrations.
The affiliate dashboard can show account summaries and subscription-related commission records.
An affiliate can submit a withdrawal request after applicable balance checks.
A recorded withdrawal request is not the same as an automatic on-chain payout.
13
Important limits and things PayCow is not
PayCow does not provide fiat bank transfers or card acquiring.
PayCow does not operate a cryptocurrency exchange or trading service.
PayCow does not claim support for every token or network. The implemented merchant payment flow is USDT on TRON and Ethereum.
PayCow does not hold merchant payment funds or merchant private keys.
PayCow does not guarantee that a blockchain transfer, email, webhook, file download, or third-party integration will always complete without interruption.
Public policy permission for a business category does not mean PayCow operates that business. PayCow supplies payment and commerce infrastructure.
Use of PayCow does not remove a merchant's legal, tax, consumer-protection, sanctions, security, or regulatory responsibilities.
This page describes implemented product behavior. Commercial availability, pricing, and limits can change; the pricing page and merchant dashboard show the applicable account information.