WP Manifestindependent plugin directory
manifest / ecommerce / givewp

Paymos Stablecoin Donations

GiveWP crypto donations plugin for WordPress — accept one-time USDT, USDC, USD1, DAI, and XAUT donations with hosted checkout, signed webhooks, and refunds.

★ 0stars

Install

Download source zip No release zip yet

This is the repository archive. It installs, but the folder name will carry the branch suffix and updates will not flow.

Install straight from GitHub with WP-CLI:

wp plugin install https://github.com/paymos-labs/givewp/archive/refs/heads/main.zip
No built-in updater. New versions won't appear under Dashboard → Updates. Install new releases yourself, or let Git Updater track the repository.

Accept one-time stablecoin donations through Paymos hosted checkout in GiveWP.

Description

Paymos adds a stablecoin payment method to GiveWP Visual and legacy donation forms. Donors open Paymos checkout from a status page on your site. GiveWP records a confirmed donation and offers its native receipt after the plugin verifies the payment with Paymos.

The plugin requires an HTTPS WordPress site, GiveWP 4.19.1.1 or later, and a Paymos project. Activate the plugin on each site individually. It supports one-time donations.

Installation

  1. Install and activate GiveWP, then install and activate Paymos Stablecoin Donations.
  2. Open GiveWP → Settings → Payment Gateways → Paymos. Choose Sandbox or Live to match GiveWP's payment mode.
  3. Click Connect Paymos and approve the site and project on the Paymos approval page.
  4. Enable Paymos on the Visual or legacy forms where you want to accept stablecoins.

External services

Paymos provides the hosted checkout and merchant API used by this gateway. Read the Paymos Terms and Privacy Policy.

Connection. When an administrator starts Connect, WordPress sends client_id=paymos-cms and scope=cms:bootstrap to https://app.paymos.io/connect/cms/device. The browser approval link carries the givewp plugin identifier, the site URL, a user code, and the admin return URL when it shares the site's origin. During approval WordPress polls https://app.paymos.io/connect/token with the device-code grant, client_id, and the secret device_code. WordPress stores the selected environment's credentials in an encrypted option and discards the short-lived OAuth token.

Donations. When the donor opens Paymos checkout, WordPress sends POST /v1/invoices to https://api.paymos.io with project_id, amount, currency, and a random external_order_id. Donor details and GiveWP receipt credentials stay in WordPress. The plugin checks the exact invoice with GET /v1/invoices/{invoice_id} and can look up an interrupted request with GET /v1/invoices using the project and original reference. These requests carry a key ID, timestamp, and HMAC signature. The signing secret stays on your site.

Payment and confirmation. Donors open the hosted invoice at https://checkout.paymos.io. Paymos sends signed invoice notifications to the WordPress webhook associated with the connected Paymos project. The plugin verifies the signature, retrieves the exact invoice from the API, and checks its scope and payment before updating GiveWP. The WordPress scheduled reconciliation job also checks pending work through the API.

Refunds. Authorized staff can request a full or overpayment refund from GiveWP → Paymos refunds. WordPress sends a signed POST /v1/refunds with invoice_id, mode, and a random external_order_id. Paymos determines the destination from the original payment. The plugin checks the operation with GET /v1/refunds/{withdrawal_id} and, when needed, the invoice-scoped GET /v1/refunds list. GiveWP records a full refund after verifying the completed Paymos operation. A refund of the excess preserves the original donation status.

Frequently Asked Questions

How can a donor resume a donation after a page reload?

When the browser can save the recovery link, the donor can choose Resume your previous Paymos donation on the same form. The link opens the site's status page and expires within 12 hours. The site verifies the original browser and GiveWP binding before showing the status or receipt. A regular new submission starts a separate donation.

What happens when I disconnect or delete the plugin?

Disabling the gateway stops new Paymos donations and preserves the credentials needed to check unresolved operations. Deactivating the plugin stops its scheduled checks. Deleting it removes local credentials, browser access to its status pages, and scheduled work. GiveWP keeps its donation history. The plugin keeps minimal references for unresolved payments and refunds so an administrator can review them manually. Manage remote keys and webhooks in the Paymos project.

Where can I get help?

Contact support@paymos.io for help with Paymos checkout, connection, or refunds.

Changelog

1.0.0

  • Added Paymos checkout for one-time GiveWP donations, signed payment verification, and full and overpayment refund reconciliation.