外掛標籤
開發者團隊
原文外掛簡介
JangoPay for WooCommerce adds a stablecoin payment method for one-time USD orders. Customers continue to JangoPay hosted checkout to select an account-enabled asset and network and complete payment.
Classic checkout and WooCommerce Checkout Blocks, with local JangoPay branding.
Traditional order storage (CPT) and High-Performance Order Storage (HPOS).
Merchant-configurable checkout text and enabled assets/networks.
Authenticated invoice and transaction checks, encrypted notifications and reconciliation.
Local RSA-OAEP-SHA256 / AES-256-GCM notification decryption, without an OpenSSL executable or process execution.
One-time USD orders only. Subscriptions, automatic gateway refunds, payouts, exchange services and other fiat order currencies are not supported. WooCommerce manual refunds are local bookkeeping; they do not send cryptocurrency.
External services
This plugin requires an eligible JangoPay merchant account. It uses WordPress HTTP APIs over verified HTTPS with redirects disabled; it does not use AI services, telemetry, remote scripts or remote fonts.
Merchant API: https://api.jangopay.org
When: enabled checkout creates an invoice; a customer explicitly resumes a safely retryable invoice; the merchant runs the connection test or re-verification; a store return or encrypted webhook triggers verification; the hourly WordPress cron reconciles outstanding ledger records. Connection tests also request supported assets. Authentication can occur before these requests.
Data: the API key is sent server-to-server as the authentication credential and exchanged for a bearer token. Invoice creation sends a merchant order reference, USD amount, enabled asset/network pairs, minimal local order ID metadata and the HTTPS return URL. This URL contains the WooCommerce order key, which grants access to that order’s payment page. Read-only recovery and verification send invoice/transaction/reference IDs and pagination parameters. Retained legacy quote recovery can also send asset, network and payment-session fields. The API sees the store server IP and normal HTTPS request metadata. The plugin does not include customer email, billing/shipping addresses or product line items in invoice creation. The API key and RSA private key are never embedded in buyer pages; the private key is not sent to JangoPay.
Hosted payment page: https://app.jangopay.org
When: a buyer follows the payment redirect. The invoice ID is included in the hosted URL. The buyer communicates directly with JangoPay, whose page may collect payment information and receives the buyer’s IP and browser request metadata under its policies. This plugin does not control the hosted page’s separate processing. Store return links must be treated as sensitive.
JangoPay sends an encrypted payment notification to the merchant-configured store callback. The store decrypts locally and verifies invoice and transaction data using the merchant API before fulfillment. Browser return parameters or notification hints alone do not confirm payment.
Service/network fees and merchant eligibility follow JangoPay policies. Review them before enabling collection:
* Service: https://www.jangopay.org/
* Documentation: https://doc.jangopay.org/documentation
* Terms of service: https://www.jangopay.org/en/legal/terms
* Privacy policy: https://www.jangopay.org/en/legal/privacy
* Official support: https://www.jangopay.org/zh/about
