
內容簡介
外掛允許在 WordPress 使用 woocommerce 外掛的商家,透過 PayLolly 支付通道進行付款。
**問題與答案:**
問題:此外掛適用於哪種類型的商家?
答案:此外掛適用於使用 WordPress 和 woocommerce 外掛的商家。
問題:這個外掛提供了什麼功能?
答案:這個外掛使商家能夠使用 PayLolly 支付通道進行付款。
問題:商家如何使用這個外掛?
答案:商家需要先安裝並啟用這個外掛,然後在其 WordPress 網站上設定 PayLolly 的支付通道。接著,商家就可以使用 PayLolly 進行付款。
外掛標籤
開發者團隊
② 後台搜尋「PayLolly Payment Gateway AddOn」→ 直接安裝(推薦)
📦 歷史版本下載
原文外掛簡介
Take card payments in your WooCommerce store through the PayLolly gateway.
Works with the block checkout (the default in current WooCommerce) and with the classic checkout.
The card is sent from the customer’s browser straight to PayLolly, which gives back a token: card numbers never reach your server and are never stored.
Saved cards for logged in customers (optional), refunds from the WooCommerce order screen, and subscription renewals with WooCommerce Subscriptions (optional).
Compatible with High-Performance Order Storage (HPOS).
Clear reporting when PayLolly refuses something: a private note on the order, a notice for administrators after repeated failures, and plain instructions for the shopper when the card details need correcting.
The payment method is only offered at checkout when it is set up (merchant id and key present, HTTPS in live mode); the configuration problems are shown to administrators only.
You need a PayLolly merchant account. The plugin is translation ready: translations are contributed on translate.wordpress.org.
External services
This plugin sends payment data to the PayLolly payment service. Without it the plugin cannot take payments.
PayLolly API (https://api.paylolly.app for live payments, https://api.stg.paylolly.app when “Enable Test Mode” is on)
What it is used for: creating card payments, refunds and subscription renewals, and getting a short-lived session key for the card form.
What is sent, and when:
At checkout, when the customer places an order: the order amount and currency, the order number, the billing name, email address, phone number and address, the customer’s IP address, the merchant id, the card token and the encrypted security code made by the card form (never the card number), the address of the thank you page and of the store’s notification URL.
When a refund is made from the order screen: the merchant id, the amount and the PayLolly payment id.
When a subscription renewal is charged (WooCommerce Subscriptions): the merchant id, the amount, the currency and the saved card token.
When a checkout page is shown (and when a page that has been open too long asks for a new key): a request for a session key, authenticated with your merchant key. Your merchant key is only ever sent from your server and is never shown to visitors.
Every request from the server carries a User-Agent that names the plugin version and the WordPress, WooCommerce and PHP versions. It contains no store address, merchant id or customer data.
The customer’s browser calls PayLolly directly from the checkout page: the card form sends the card number, the expiry date and the security code to PayLolly’s tokenisation endpoint (https://api.paylolly.app/api/rest/v1.0/TokenJS/, or the api.stg.paylolly.app equivalent in test mode) using the short-lived session key, and receives a token and an encrypted security code in return. No other script is loaded from another host: the scripts of the plugin are part of the plugin.
PayLolly also posts a signed notification to your store when a payment is approved. The plugin checks the signature before it marks an order as paid.
Terms of service: https://paylolly.com/legal/terms-of-service
Privacy policy: https://paylolly.com/legal/privacy-policy
