HULO Payments Wordpress Plugin - Rating, Reviews, Demo & Download
Plugin Description
HULO Payments takes payments through your own Stripe account on any WordPress site. Put a payment form on a page or send someone a pay link; the payer pays on a hosted payment page, and every payment lands in one payments list and ledger, with refunds, manual capture and disputes.
Taking payments
- Payment forms: the “HULO payment form” block or the
[hulo_payment_form amount="12.50" currency="GBP" description="Workshop ticket"]shortcode, for a fixed amount or one the payer chooses (allow_custom_amount="1", up to a maximum you set). The payer enters their name and e-mail and continues to the hosted payment page. The form itself needs no JavaScript, and a fixed amount cannot be changed in the browser. If a payment cannot be started (for example an amount above your maximum), the payer is sent back to the form with the reason shown above it. - Pay links: create a payment for any amount under HULO Payments Pay links, copy its link and send it to the payer. Pay links stay open for 30 days.
- Hosted payment page with Stripe’s Payment Element: cards, Apple Pay, Google Pay, Link, Klarna and the other methods you switch on in your Stripe dashboard, with 3-D Secure handled by Stripe. Apple Pay shows only once your site’s domain is added in the Stripe dashboard (Settings Payment method domains), as Stripe requires. The page is never indexed or framed and sends a Content-Security-Policy with a per-request nonce (report-only to start with; switch it to enforce under Settings).
Built to be safe
- Server-side verification: the browser never decides that a payment is paid. The plugin reads the payment back from Stripe and checks that it belongs to that payment and matches its amount and currency.
- Signed, idempotent webhooks: Stripe’s signature is checked on the raw body with a 5-minute tolerance, each event is applied once, and an event that fails is released so Stripe sends it again. “Register webhook” creates the endpoint in your Stripe account and saves its signing secret.
- Card details are typed into Stripe’s own fields and never reach your server.
- The public endpoints (payment forms, the hosted page, webhooks) are rate-limited per visitor. Behind a proxy or CDN, list its addresses under Settings so the real visitor address is used.
Managing payments
- Payments: every payment in one list, with status and source filters, search, and a page for each payment.
- Refunds, full or partial, from the payment’s page. Refunds made in the Stripe dashboard are added to the payment once each. Releasing an authorisation, or the part of one that was not captured, is never counted as a refund.
- Authorise only (manual capture): reserve the money, then capture or release it from the payment’s page (the PHP API can also capture part of it).
- Disputes are recorded in the ledger and e-mailed to the ops address you set.
- Overview: money taken, payments settled, refunds, disputes, success rate and money paid by link for the last 7 and 30 days, with each currency shown on its own. The Transactions tab is the full ledger and the Webhooks tab logs every delivery.
- Rules: offer a payment method only for an amount band or certain currencies.
For developers
- A PHP API for other plugins: create, find, capture, release and refund payments, a filter before every charge and actions on every status change. See README.md in the plugin folder.
With WooCommerce (optional)
- Stripe becomes a payment method for the classic checkout, the Checkout block and the pay-for-order page (HPOS compatible), and order payments join the same payments list.
- Pay later by invoice for orders, on the payment terms you set.
- The rules also cover the store’s other payment methods, and at the checkout they can check the customer’s country, user role and whether they are signed in.
- Each order follows its payment: status, notes and refunds, with capture and release in the order actions and full or partial refunds from the order’s refund button. Refunds made in the Stripe dashboard are added to the order too.
- The store currency is the default for payment forms and pay links, in place of the Currency setting.
HULO Payments Pro
Everything above is free, with no limits. HULO Payments Pro is a separate add-on from huloglobal.com that adds Adyen, PayPal, Mollie, Square, Braintree, GoCardless, Checkout.com and Coinbase Commerce (for payment forms, pay links and the checkout), provider-hosted payment links, fallback to another method after a decline, payment surcharges, a weekly e-mail report and, with WooCommerce, saved cards.
External services
This plugin connects to Stripe (Stripe, Inc. and its affiliates, for example Stripe Payments Europe, Ltd.) to take payments. It sends nothing to Stripe until you enter your Stripe API keys under HULO Payments Payment methods, and it only ever uses your own Stripe account.
What your server sends to the Stripe API (api.stripe.com), and when:
- When a payer opens a payment on the hosted payment page: the amount, currency and capture mode, the payment’s description, its number and reference (or, for an order, the order number), your site’s host name, the statement descriptor suffix if you set one, and the payer’s e-mail address (for Stripe’s receipt). This creates a Stripe PaymentIntent.
- When the payment is completed, or the payer comes back to the page: the PaymentIntent id, to read the payment’s status, amount and card result back from Stripe.
- When you capture, release or refund a payment: the PaymentIntent id and the amount, and for a refund the reason you typed.
- When Stripe reports a refund this site did not make (for example one made in your Stripe dashboard) without naming it: the PaymentIntent id, to read that payment’s refunds back.
- When you click “Test keys”: a request for your Stripe account’s name. When you click “Register webhook”: a request for your webhook endpoints, then this site’s webhook address (/wp-json/hulo-payments/v1/webhook/stripe) and the list of events Stripe should send to it. An endpoint this plugin registered before, whose signing secret is saved, keeps that secret and gets the events it is missing (and is switched back on if Stripe disabled it). Any other endpoint for the same address (one you added by hand, or one whose secret was not saved) is deleted and replaced with a new one, because Stripe shows an endpoint’s signing secret only when it is created.
- Other HULO plugins you install (for example HULO Checkout Guard or HULO Fraud Prevention) can make their own Stripe API calls through HULO Payments with your keys; their readmes describe those calls.
In the payer’s browser, the hosted payment page loads Stripe.js from js.stripe.com. It shows Stripe’s payment fields, in frames from Stripe’s own domains (js.stripe.com and its subdomains, hooks.stripe.com for 3-D Secure, and link.com when the payer uses Link), and sends the card or wallet details straight to Stripe.
Stripe sends signed webhook events (payments, refunds, disputes) to this site’s /wp-json/hulo-payments/v1/webhook/stripe address.
Stripe Services Agreement: https://stripe.com/legal/ssa — Stripe Privacy Policy: https://stripe.com/privacy
Payment forms, pay links, the rules, the ledger and pay later by invoice use no external service. The plugin makes no other external requests: no tracking, no licence checks and no remote updates.
Screenshots
HULO → Payments → Overview: money taken, payments settled, refunds, disputes, success rate and money paid by link for the last 7 and 30 days.
Payments: every payment from payment forms, pay links and the API, with status and source filters and search.
A payment’s page: its details and card result, the refund form for what is left to refund, and its ledger entries (the capture and a partial refund).
Pay links: create a payment for any amount, in a currency chosen from the list, and send its link; recent pay links with their status and link.
Payment methods: Stripe in test mode, offered on payment forms and pay links, with its webhook and saved signing secret.
The “HULO payment form” block on a page, as a visitor sees it before continuing to the hosted payment page.
