Merchant360 for WooCommerce
| 开发者 | elecpayments |
|---|---|
| 更新时间 | 2026年9月5日 00:36 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
Merchant360 for WooCommerce lets your store accept credit and debit cards through your Merchant360 account from Electronic Payments.
Unlike a traditional gateway that collects the card number on your own checkout page, Merchant360 renders a secure, PCI-compliant card form hosted on merchant360.net — shown inline (embedded in your checkout) or in a pop-up modal. The card number never touches your WordPress server, which keeps your store in the simplest PCI scope (SAQ-A).
Highlights
- One-key setup. Connect with a single click ("Connect with Merchant360"), or paste one API key. No user name, password, reg key, or separate dev/prod keys.
- PCI-friendly. The shopper enters the card on Merchant360's hosted surface. Your server never sees the card number or CVV.
- Two checkout styles. Show the card form inline in your checkout, or as a branded pop-up — your choice.
- Saved cards. Logged-in customers can securely save a card and reuse it on their next order (managed under My Account → Payment methods).
- Surcharge display. If your Merchant360 account runs a compliant credit-card surcharge program, the surcharge is shown as its own labeled line and reconciled to the amount actually charged.
- Refunds from WooCommerce. Issue full or partial refunds right from the order screen.
- Gift cards (optional). Accept Merchant360 gift cards at checkout, sell gift cards as products, and refund to store credit. Shown only for Merchant360 accounts that have gift cards.
- Classic and Block checkout. Works with both the classic checkout shortcode and the newer Checkout block.
- An active Merchant360 account (contact Electronic Payments if you do not have one).
- WooCommerce 8.0 or newer.
- What is sent, and when: when a shopper pays, the order amount, currency, order number, line-item names, and the shopper's name, email, and billing phone are sent to Merchant360 to create a secure checkout session and process the payment. Card details are entered by the shopper directly on Merchant360's hosted surface and are never sent through your server. Refunds send the payment reference and amount. Gift-card features send the gift-card number, amount, and recipient name/email. Every request carries your store URL in its User-Agent so Merchant360 can attribute traffic to your store. Merchant360 sends your store payment-status notifications (webhooks). Nothing is sent until you connect the store to your Merchant360 account.
- Scripts loaded from Merchant360: on the checkout and order-pay pages the plugin loads Merchant360's checkout script (https://www.merchant360.net/m360-checkout.js) and embeds the hosted card form from merchant360.net. This is how the card form stays on Merchant360's PCI-compliant servers instead of your site.
- Service endpoints: https://www.merchant360.net (API and hosted pay surface).
- Terms and Privacy: https://www.merchant360.net/legal/terms and https://www.merchant360.net/legal/privacy
安装:
Automatic installation
- In your WordPress dashboard go to Plugins → Add New.
- Search for "Merchant360 for WooCommerce".
- Click Install Now, then Activate.
- Upload the
merchant360-for-woocommercefolder to/wp-content/plugins/. - Activate the plugin through the Plugins menu in WordPress.
- Go to WooCommerce → Settings → Payments → Merchant360.
- Click Connect with Merchant360 and approve the connection (this creates the correct API key and registers the payment webhook automatically). Or choose Enter API key manually and paste a key from Merchant360 → Integrations.
- Click Test connection, choose Inline, Modal, or Redirect card entry, and Enable the gateway.
屏幕截图:
常见问题:
Does the card number touch my server?
No. The card is entered on Merchant360's hosted surface (an iframe or pop-up served from merchant360.net). Your server only ever sees a reference to the completed payment.
Which PCI level does this put me in?
Because the card is captured on Merchant360's hosted surface, most merchants qualify for SAQ-A. Your acquirer determines your exact obligations.
Can customers save a card for next time?
Yes. Logged-in customers can opt to save a card; it is stored as a reusable token (the card number is never stored on your site) and offered on their next checkout and under My Account → Payment methods.
How do refunds work?
Open the order in WooCommerce and use the standard Refund button. Full and partial refunds are supported and are sent to Merchant360.
Does it support the WooCommerce Checkout block?
Yes. The gateway registers a Blocks integration and also works with the classic checkout shortcode.
更新日志:
2.3.5
- WordPress.org review: the settings-screen "Test connection" handler is now a static file loaded with wp_enqueue_script (no inline script tag), and the gift-card helper line no longer names a card vendor.
- Security hardening (defense in depth): the classic-checkout inline container and error banner are now built with DOM APIs and plain-text insertion instead of string-concatenated HTML. No functional change.
- WordPress.org readiness: passes the Plugin Check tool with no errors. Escaped gift-card error messages, sanitized the store-credit amount field, removed the unused block gift-card script, and cleaned up every plugin option on uninstall.
- Tested up to WordPress 7.1.
- Readme: fuller disclosure of what is sent to Merchant360 and which Merchant360 script the checkout loads.
- New setting: "Order status after approved payment" — WooCommerce default (Processing; Completed for virtual orders), Always Processing, or Always Completed. Every approved payment completes the order automatically on all checkout modes; webhooks keep orders in sync even when a shopper closes the tab right after paying.
- Pay with Vault: the buyer's billing phone now rides on checkout sessions (order and inline), so saved cards verify by text message on first use instead of email.
- Pay with Vault: the Merchant360 network wallet now works on the inline (embedded) checkout. Returning customers can enter their email, verify a one-time code, and pay with a saved card without typing card details. Both the classic checkout and the block checkout accept the wallet payment and finish the order automatically.
- Fix: resolves the "no such namespace registered: merchant360-egift" error for good — the gift-card handler is now registered at plugin load, before WooCommerce fires its block-load event, so it's always available on the block checkout.
- Added a gift-card icon and a helper line to the gift-card field.
- Fix: the "no such namespace registered" gift-card error is resolved for good — gift cards now initialize independently of the card gateway, so the handler is registered on every request the block checkout uses.
- Fix: the gift-card field no longer appears/disappears intermittently — it now uses the same reliable availability check that never hides it on a momentary hiccup.
- Fix: applying a gift card on the block checkout could fail with "no such namespace registered: merchant360-egift." The gift-card handler is now always registered so the block checkout can always reach it.
- Fix: the Merchant360 gift-card field now shows reliably on the block checkout — it appears inside the Merchant360 payment option, under the card fields (previously it used an experimental area that isn't present on all WooCommerce versions, so it never appeared).
- A gift card that covers the whole order now completes with no card charge — "click Place order to finish."
- Checkout label is now "Credit/Debit Card".
- Gift-card field is now clearly labeled "Have a Merchant360 gift card?" so it isn't confused with other gift-card plugins (e.g. WooCommerce Gift Cards).
- Block checkout now shows the real reason a gift card can't be applied (e.g. "no balance left", "not found") instead of failing silently, and never shows a false "applied".
- Fix: the Gift cards section no longer disappears after a Disconnect → Connect. A failed or mid-reconnect availability check can never hide the section now — it only hides on a confirmed "no gift cards" answer.
- Fix: the block-based checkout now also shows the fixed "Payments by Merchant360" label (it was still showing an old saved title).
- Fix: the Gift cards settings section now reliably appears for accounts that have gift cards. The settings screen checks gift-card availability on a fresh, short-lived lookup instead of a shared 6-hour cache, so it can't be hidden by a stale reading.
- Checkout label is now fixed: the payment method shows as "Payments by Merchant360" (title and description are no longer editable, for a consistent look).
- Fix: the Gift cards settings now appear right after upgrading for accounts that have gift cards, instead of waiting behind a cached lookup.
- Gift cards: the Gift cards settings (Accept / Sell / Refund to store credit) now appear only when your Merchant360 account is actually set up for gift cards, so stores without them aren't shown options that do nothing.
- Gift cards (eGift): accept gift cards at checkout, sell gift cards as products, and refund to store credit (emails a new card). Uses your existing Merchant360 connection — reconnect once to grant gift-card access.
- Checkout polish: card-brand and credit/debit labels, masked card number, and Merchant360 branding on the inline and modal card windows.
- Rebuilt as Merchant360 for WooCommerce.
- Card capture moved to Merchant360's hosted surface (inline iframe or pop-up modal) — the PAN no longer passes through the store (SAQ-A).
- One-click "Connect with Merchant360" plus single-key manual setup and a Test connection button.
- Saved cards via WooCommerce payment tokens.
- Compliant surcharge display with order-total reconciliation.
- Full and partial refunds from the order screen.
- Classic and Checkout-block support; HPOS compatible.