[WordPress] 外掛分享: Nephila Payment Gateway for Epoch

首頁 › 外掛目錄 › Nephila Payment Gateway for Epoch
WordPress 外掛 Nephila Payment Gateway for Epoch 的封面圖片
全新外掛
安裝啟用
—
尚無評分
37 天前
最後更新
—
問題解決
WordPress 6.5+ PHP 7.4+ v1.0.1 上架:2026-09-08

內容簡介

Nephila Payment Gateway for Epoch 是一款獨立的 WooCommerce 整合外掛,專為已獲得 Epoch 商戶帳戶的商家設計。此外掛可將交易資訊發送至 Epoch 的支付服務,並將顧客重定向至 Epoch 的結帳頁面,確保安全的支付流程。

【主要功能】
• 支援 Epoch 主機結帳的 WooCommerce 支付方式
• 一次性 WooCommerce 付款處理
• Epoch 測試與生產環境支援
• JWT 簽名的動態定價發票請求
• 成功與拒絕回傳處理
• Epoch PostBack 處理

外掛標籤

開發者團隊

⬇ 下載最新版 (v1.0.1) 或搜尋安裝

① 下載 ZIP → 後台「外掛 › 安裝外掛 › 上傳外掛」
② 後台搜尋「Nephila Payment Gateway for Epoch」→ 直接安裝(推薦)

原文外掛簡介

Nephila Payment Gateway for Epoch is an independent WooCommerce integration for merchants who already have an approved Epoch merchant account.
The plugin sends the required transaction information to Epoch’s hosted payment service and redirects the customer to the Epoch hosted checkout page. Payment card details are entered on the hosted Epoch payment page rather than on the merchant’s WordPress site.
After payment, the plugin can receive Epoch PostBack notifications and use the verified payment response to update the related WooCommerce order.
This plugin is independently developed and is not affiliated with, endorsed by, sponsored by, or officially maintained by Epoch. Epoch is the payment service provider. Merchants must establish and maintain their own merchant relationship with Epoch.
Features

WooCommerce payment method for Epoch hosted checkout.
One-time WooCommerce payments.
Epoch staging and production environments.
JWT-signed Dynamic Pricing invoice requests.
Hosted payment redirect.
Success and denial return handling.
Epoch PostBack handling.
Optional epoch_digest HMAC verification when provided by Epoch.
Epoch IP allowlist verification.
Decline-reason mapping.
WooCommerce order notes and logging.
WooCommerce HPOS compatibility.
Local testing tools for order-status and callback-flow testing.

Requirements

WordPress 6.5 or newer.
WooCommerce 8.0 or newer.
PHP 7.4 or newer.
An approved Epoch merchant account.
Epoch merchant-specific Dynamic Pricing Client ID and JWT shared key.
HTTPS is strongly recommended for production stores and is required by many payment environments.

Payment Confirmation
The plugin treats a verified Epoch PostBack as the authoritative payment confirmation signal.
A customer returning to the store after checkout does not by itself mark the order as paid. This helps prevent an unverified browser return from being treated as a successful payment.
External Services
This plugin connects to Epoch’s external payment service to create hosted payment transactions and receive payment status notifications.
Service provider: Epoch
Website: https://epoch.com/
The plugin may send transaction and customer information required to create a payment, which can include:

WooCommerce order/invoice reference.
Payment amount and currency.
Customer name and email address.
Billing/postal information when required by the configured payment request.
Merchant site hostname.
Success, denial, and PostBack URLs.

Payment card information is entered on Epoch’s hosted payment page and is not collected or stored by this plugin.
The information sent to Epoch is subject to the merchant’s agreement with Epoch and Epoch’s applicable policies. Review the provider’s current privacy information before enabling the integration:
https://epoch.com/legal_docs/privacy_policy.html
For Epoch merchant/account terms and payment-service requirements, merchants should use the current agreements and documentation supplied by Epoch for their account.
This plugin does not send analytics, advertising, telemetry, or unrelated tracking data to its developer.
Data and Privacy
The plugin stores WooCommerce order-related information and payment transaction references in the normal WooCommerce order and logging mechanisms needed to operate the gateway.
It does not intentionally collect or store payment card numbers, CVV/CVC values, or other card-entry data.
When the merchant enables and uses the gateway, required transaction information is transmitted to Epoch as part of the payment service. By configuring the integration, the merchant authorizes those service requests as necessary to process payments.
Security

Never share the Epoch JWT shared key.
Use staging before production.
PostBack verification is required for payment confirmation.
Prefer epoch_digest verification when Epoch provides the required key for the merchant account.
Otherwise use the Epoch IP allowlist verification supported by the plugin.
Keep WordPress, WooCommerce, PHP, and the plugin updated.

Testing
Without live Epoch credentials, administrators can test plugin activation, settings validation, checkout availability, simulated callback/order-status flows, and local behavior.
A real Epoch staging account and merchant-specific credentials are required to test the complete hosted payment flow against Epoch.
The built-in simulation tools are for local/staging testing only. They do not represent real payment processing and must not be used as evidence of a completed payment.
Support
For plugin-specific issues, use the support forum on the plugin’s WordPress.org page.
For merchant-account approval, credentials, transaction disputes, payment processing, or Epoch account configuration, contact Epoch directly.

延伸相關外掛

文章
Filter
Mastodon