WavePay Payments

io.github.t3ratechPublished by GitHub account t3ratechv1.0.0Updated Oct 25, 2026

Payments MCP: self-serve merchant key, PayNow + PayPal checkouts.

The publisher's own server: Payments Ai Mcp

VerifiedStreamable HTTPWeb executableFinanceBusiness & Commerce

Overview

AI-generated overview

WavePay Payments lets an assistant register a merchant account, list payment rails, price products, start hosted checkouts and poll payment status.

What you can do
Register a merchant account and receive a live merchant key once, with a free tier of 25 payments per 30 days (wavepay_register). List the payment rails the deployment supports, such as PayNow channels and PayPal (wavepay_providers). Look up live plans and prices for a product per rail, including the active promotion (wavepay_pricing). Start a checkout on a chosen rail and get a hosted checkout URL to hand to the buyer (wavepay_checkout). Poll a payment by reference for pending, collected or expired status (wavepay_checkout_status). Browse the merchant catalog of sites, plans, prices and coupons visible to the merchant key (wavepay_catalog).
When to use it
Use it when an assistant should help set up a WavePay merchant account, quote prices for a product, create a checkout link for a buyer, or check whether a payment has been collected. It suits small merchant and storefront workflows that take PayNow rails or PayPal.
Requirements
A remote streamable HTTP endpoint; no local package is needed. The catalog tool requires the x-wavepay-service-key header carrying a merchant key (mk_live_… or mk_test_…). Registration works unsigned and returns the key once. Network access to the WavePay endpoint is required.
Before you install
The merchant key is a live payment credential: it is returned only once and only its hash is stored, so losing it means losing access. The key is sent in the x-wavepay-service-key header. Checkout creates real payment requests for buyers, and the free tier is limited to 25 payments per 30 days. Treat the key as a secret and avoid exposing it in shared logs.

Installation

In SourceWeft

  1. Open WavePay Payments in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.t3ratech%2Fwavepay/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "wavepay-payments": {
      "type": "http",
      "url": "https://t3rnel-wavepay-production.t3ratech.workers.dev/mcp"
    }
  }
}

Tools

6

wavepay_register

Register a WavePay merchant account. Returns a live merchant key once — save it; only its hash is stored. Free tier: 25 payments per 30 days.

ParametersnamerequiredownerEmailrequired

wavepay_providers

List the payment rails this deployment can take — PayNow (EcoCash, OneMoney, InnBucks, Telecash, O'mari, ZimSwitch, cards) and PayPal.

Takes no parameters.

wavepay_pricing

Live plans and prices for a product, per rail, with the active promotion.

ParametersproductIdrequired

wavepay_checkout

Start a checkout for a product/plan on a rail; returns the hosted checkoutUrl to hand the buyer.

ParametersemailrequiredphoneplanIdrequiredproviderrequiredproductIdrequired

wavepay_checkout_status

Poll a payment by reference: pending | collected | expired.

Parametersreferencerequired

wavepay_catalog

Merchant self-service catalog — the sites, plans, prices and coupons your merchant key can see. Requires the x-wavepay-service-key header carrying an mk_live_… or mk_test_… key.

Takes no parameters.

Version history

1
  1. v1.0.0LatestSep 27, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Payments integrations