HULO Payments

npm install @huloglobal/vendure-plugin-payments

Version0.2.7

Compatibility>=3.5.0 <4.0.0

Categorypayment-provider

Downloads713 monthly

Last updatedSep 25, 2026

View source View on NPM

One payments plugin for Vendure. Stripe, Adyen, PayPal, Mollie, Square, Braintree, GoCardless, Checkout.com, Coinbase Commerce, bank transfer and pay-later behind a single contract, so every provider gets the same features and every payment lands in the same ledger:

Hosted checkout page — one mutation and a redirect; the plugin's own page shows every enabled method, drives each provider's client and brings the customer back paid. Nothing provider-specific in your storefront.
Hosted / embedded sessions — Stripe Payment Element, Adyen Drop-in, PayPal buttons, Mollie hosted checkout; cards, Apple Pay, Google Pay, Link, iDEAL, Klarna, Bancontact, SEPA and whatever the provider enables. 3-D Secure / SCA handled by the provider.
Server-side verification — the storefront never decides a payment state; the plugin re-reads the intent / session / order from the provider and checks amount, currency and order code before addPaymentToOrder.
Capture control — automatic or manual capture per method, partial captures, cancels, full and partial refunds from the normal Vendure refund flow.
Signed, idempotent webhooks — Stripe signatures, Adyen HMAC (+ basic auth), PayPal signature verification, Mollie fetch-back. Duplicate deliveries are ignored; results update Vendure payments and refunds.
Disputes — chargebacks land in the ledger and alert ops.
Saved cards — Stripe Customers and Adyen stored payment methods for signed-in customers; list and remove from the shop API.
Subscriptions — mark any product variant as billed daily / weekly / monthly / yearly (with a trial); the order charges the first period, then Stripe, PayPal and Mollie bill natively and Adyen renewals are charged by the plugin's scheduler from the stored card. Customers see and cancel their subscriptions through the shop API; admins pause, resume, cancel and see MRR.
Pay by link — one click in the admin creates a provider-hosted payment link for any unpaid order (draft orders, accepted quotes, phone orders); the webhook settles it.
Routing, rules and surcharges — provider order per channel with fallback on decline, an eligibility checker (amount band, currencies, countries, customer groups, signed-in only) usable on any payment method, and optional per-provider surcharges.
Ledger + dashboard — authorisations, captures, refunds, disputes, failures, renewals and pay-links by provider and day, success rate, webhook deliveries, subscriptions, settings — under Sales → Payments.

Works on MySQL, MariaDB and PostgreSQL. No provider SDKs: each provider is a few REST calls on the platform fetch.

In the admin

Payments (Sales → Payments): dashboard, a Payment methods tab (every provider × every channel, Add / Connect per cell), transactions, subscriptions, pay-by-link, the Providers tab with one-step Connect, and Settings.
Settings → Payment methods: a Connect a payment provider button; every HULO method in the list shows a brand mark, one status word (Live / Test mode / Ready, disabled / Not set up) and the first line of its description; and under each method a panel that explains the provider, lists what customers can pay with, tests the keys you typed, shows the webhook URL to paste and whether its secret is saved, and walks through going live.

Install

Bash

yarn add @huloglobal/vendure-plugin-payments

// vendure-config.tsimport { HuloPaymentsPlugin } from '@huloglobal/vendure-plugin-payments';plugins: [  HuloPaymentsPlugin.init({    publicBaseUrl: 'https://shop.example.com',        // webhook + return URLs    licenceKey: process.env.HULO_LICENCE_KEY_PAYMENTS, // optional — or activate in the admin    ops: { email: 'ops@example.com', webhookUrl: process.env.OPS_SLACK_WEBHOOK },  }),  AdminUiPlugin.init({    app: compileUiExtensions({ extensions: [HuloPaymentsPlugin.uiExtensions /* … */] }),  }),]

Then open Sales → Payments → Providers and click Connect on a provider: paste the keys from its dashboard (linked from the card), click Test connection to see which account they belong to, then Connect. The plugin verifies the keys with the provider, registers the webhook itself (Stripe, PayPal, and Adyen when the credential has the Management API webhook role), stores the signing secret, and creates the Vendure payment method on the channel you chose — nothing to copy back by hand. Mollie needs no webhook setup at all.

Prefer the standard route? Settings → Payment methods → Create and pick the handler HULO Payments — Stripe / Adyen / PayPal / Mollie; every field explains where to find its value. Tables are created on boot; the only migration is Vendure's own for the three subscription custom fields on ProductVariant (npx vendure migrate on installs that use migrations).

Storefront

The simplest integration is the hosted page:

Graphql

mutation { huloHostedCheckout(returnUrl: "https://shop.example.com/checkout/return", cancelUrl: "https://shop.example.com/checkout", methodCode: "paypal") { url expiresAt } }# methodCode is optional: it preselects that method on the page (one button per provider in your checkout).# → redirect the customer to `url`; they return to returnUrl?order=CODE&result=paid|pending

For an embedded checkout, drive the providers yourself:

Graphql

# 1. What to offer (preferred first, with public keys and capabilities)query { huloPaymentProviders { methodCode provider name publicConfig capabilities surcharge preferred } }# 2. A session for the active ordermutation { huloCreatePaymentSession(methodCode: "stripe", options: { returnUrl: "https://shop.example.com/checkout/return", savePaymentMethod: true }) {  provider clientSecret sessionId sessionData checkoutUrl publicKey environment config amount currency } }# 3. After the provider's client reports success, the normal Vendure step:mutation { addPaymentToOrder(input: { method: "stripe", metadata: { paymentIntentId: "pi_…" } }) { ... on Order { id state } ... on ErrorResult { errorCode message } } }

Provider	Client library	`metadata` for `addPaymentToOrder`
Stripe	`@stripe/stripe-js` Payment Element with `clientSecret`	`{ paymentIntentId }`
Adyen	`@adyen/adyen-web` Drop-in with `sessionId` + `sessionData`, `clientKey`, `environment`	`{ sessionId, sessionResult }` from `onPaymentCompleted`
PayPal	`@paypal/paypal-js` buttons with `createOrder: () => sessionId`	`{ paypalOrderId }`
Mollie	redirect to `checkoutUrl`; on return	`{ molliePaymentId }` (the `sessionId`)
Square	Web Payments SDK with `config.applicationId` / `locationId`	`{ sourceId }` (the card token)
Braintree	Drop-in with `clientSecret` as the authorization	`{ nonce, deviceData }`
GoCardless	redirect to `checkoutUrl`; on return	`{ billingRequestId }` (the `sessionId`)
Checkout.com	redirect to `checkoutUrl`; on return	`{ sessionId }`
Coinbase Commerce	redirect to `checkoutUrl`; on return	`{ chargeCode }` (the `sessionId`)
Bank transfer / pay later	show `instructions`	`{}`

Also available: huloSavedPaymentMethods, huloRemoveSavedPaymentMethod, huloMySubscriptions, huloCancelSubscription(id, atPeriodEnd), huloApplyPaymentSurcharge(methodCode).

Subscriptions

Set Subscription billing interval (and optionally every N intervals and free trial days) on a product variant. Its price is the price per period. When an order containing it is paid through a HULO method the plugin creates the subscription with the provider (or schedules it itself for Adyen), records renewals in the ledger, alerts on failed renewals and cancels after the configured number of failed daily attempts. PayPal subscriptions need one customer approval; the approval link is exposed on huloMySubscriptions and in the admin.

Tiers

Free tier	Licensed
Stripe: sessions, wallets, 3-D Secure, automatic/manual capture, refunds, disputes, signed webhooks; bank transfer; pay later	Adyen, PayPal, Mollie, Square, Braintree, GoCardless, Checkout.com, Coinbase Commerce
Hosted checkout page
Ledger, dashboard, webhook log	Subscriptions and the renewal scheduler
`hulo-payment-rules` eligibility checker	Saved cards, pay-by-link, provider routing, surcharges

Unlicensed installs run everything for 14 days; the trial (card required, nothing charged until day 15) and the licence are bought from the admin banner. Details and pricing: https://huloglobal.com/vendure-plugins/payments/

Webhook events handled

Stripe payment_intent.succeeded / amount_capturable_updated / payment_failed / canceled, charge.refunded, charge.refund.updated, charge.dispute.created / closed, checkout.session.completed, invoice.paid / payment_failed, customer.subscription.updated / deleted / paused. Adyen AUTHORISATION, CAPTURE, CAPTURE_FAILED, CANCELLATION, REFUND, REFUND_FAILED, CHARGEBACK, NOTIFICATION_OF_CHARGEBACK, CHARGEBACK_REVERSED, RECURRING_CONTRACT. PayPal CHECKOUT.ORDER.APPROVED, PAYMENT.CAPTURE.*, PAYMENT.AUTHORIZATION.*, CUSTOMER.DISPUTE.*, BILLING.SUBSCRIPTION.*, PAYMENT.SALE.COMPLETED. Mollie: every payment webhook (status, refunds, chargebacks, subscription payments).

Changelog

All notable changes to @huloglobal/vendure-plugin-payments are documented here. The format follows Keep a Changelog and this project adheres to semantic versioning.

[0.2.7] — 2026-09-25

Fixed

Payments → Payment methods tab: every channel cell stacks its status chip and buttons left-aligned with the same widths, columns are fixed-width and rows vertically centred, so nothing drifts out of line on multi-channel installs.

[0.2.6] — 2026-09-25

Fixed

Settings → Payment methods: the status chips sit in their own fixed column (mark · status · name), so they line up down the page whatever the method name length; the Payment methods tab's status chips and buttons share fixed widths for the same reason.

[0.2.5] — 2026-09-25

Fixed

Sharing a Stripe account with Vendure's own Stripe plugin no longer produces webhook errors. Events for PaymentIntents the plugin did not create (they lack its vendureOrderId stamp) are acknowledged and ignored instead of being applied to the order; the plugin never adds a payment to an order that already carries another method's payment.
A configured but disabled method still answers its webhook endpoint with 200 after verifying the signature, so the provider does not mark the endpoint as failing while the method is switched off.
Enabling, disabling or editing a payment method in Settings takes effect immediately (the plugin's method cache is cleared on the Vendure event) instead of after up to 30 seconds.

[0.2.4] — 2026-09-23

Added

Payment methods tab on the Payments page: every provider for every channel in one table, one status word per cell (Not added / Not set up / Ready, disabled / Test mode / Live). Add creates the payment method on that channel — disabled, no keys, with a descriptive name such as "Adyen · cards, wallets & 100+ local methods" — so it is visible under Settings → Payment methods straight away; Connect opens the Connect panel for that channel. "Add every missing method" fills the whole table in one click. The button on Settings → Payment methods now opens this tab.
POST /hulo-payments/methods { provider, channelId } behind it (admin, CreatePaymentMethod), idempotent per provider and channel.

[0.2.3] — 2026-09-23

Added

huloHostedCheckout(methodCode): the storefront can preselect one of the enabled methods, so a "Pay with PayPal" button opens the hosted page straight on PayPal. Without it the page opens on the first method in the channel's order, as before.

[0.2.2] — 2026-09-23

Changed

Settings → Payment methods reads at a glance. The Name column of the list now shows, for every HULO method, a brand mark, the name, one status word (Live / Test mode / Ready, disabled / Not set up) and the first line of the description — so twenty methods scan in seconds without opening each one. Other plugins' methods are untouched.
Providers tab regrouped. Providers are listed under four plain headings — Cards & wallets; PayPal, bank & local methods; Crypto; Offline & on account — as compact rows (mark, name, what customers can pay with, one status word). A row expands to the details, dashboard links, its payment methods and the Connect panel; nothing else is on screen until you ask for it.

[0.2.1] — 2026-09-23

Added

Settings → Payment methods explains itself. Any payment method that uses a HULO handler now shows a panel under the form: what the provider is, what customers can pay with, what the method supports (holds, refunds, subscriptions, saved cards, pay-by-link), where the keys come from with links to the provider dashboard, a Test these keys button that checks the unsaved form values, the webhook URL with a copy button and a saved/not-saved status, and the go-live checklist. Offline methods (bank transfer, pay later) get a plain-language "how it works" instead of keys and webhooks.
Connect a payment provider button on the payment-methods list, opening the Payments page on the Providers tab. The Payments page accepts ?tab= and ?connect=<provider> deep links.

[0.2.0] — 2026-09-22

Added

Hosted checkout page. huloHostedCheckout(returnUrl) returns a URL the storefront redirects to; the page shows every enabled method in the channel's preferred order, drives each provider's own client (Stripe Payment Element, Adyen Drop-in, PayPal buttons, Square Web Payments, Braintree Drop-in, hosted redirects, bank-transfer instructions), records the payment and sends the customer back with ?order=&result=. No provider code in the storefront. Branding (name, colour, logo) per channel in Settings.
Seven more payment systems, all behind the same contract: Square (cards, Apple Pay, Google Pay, Cash App Pay, Afterpay; holds, refunds, payment links, signed webhooks), Braintree (cards, PayPal, Venmo, wallets; holds, refunds), GoCardless (Bacs, SEPA, ACH direct debit, Instant Bank Pay; native subscriptions), Checkout.com (hosted payments page; holds, refunds, disputes, payment links, workflow webhooks), Coinbase Commerce (crypto), bank transfer and pay-later / invoice (offline methods settled from the order page, free tier).
Get-started wizard on the Payments page until the first provider is connected; Connect works for every provider, including automatic webhook setup for Square and Checkout.com.

[0.1.0] — 2026-09-21

Added

Four providers, one contract. Stripe (Payment Intents + Payment Element), Adyen (Sessions + Drop-in), PayPal (Orders v2) and Mollie (Payments API) as Vendure payment method handlers with server-side verification of amount, currency and order code.
Capture control and refunds. Automatic or manual capture per method, partial capture, cancel, full and partial refunds through Vendure's refund flow.
Signed, idempotent webhooks per provider at /hulo-payments/webhook/<provider>, updating payments, refunds and subscriptions; disputes recorded and alerted.
Saved cards (Stripe Customers, Adyen stored methods) with shop-API listing and removal.
Subscriptions from product-variant custom fields: native billing on Stripe, PayPal and Mollie, scheduler-billed renewals for Adyen, dunning, MRR, customer self-service.
Pay by link for any unpaid order from the admin (Stripe Checkout, Adyen Pay by Link, PayPal approve links, Mollie Payment Links).
Routing and rules. Provider order per channel with fallback, the hulo-payment-rules eligibility checker, optional surcharges.
One-step Connect on every provider card: verifies the keys with the provider, creates the webhook through the provider's API (Stripe, PayPal, Adyen Management API) and stores its secret, then creates the Vendure payment method — with links straight into each provider's dashboard, API keys and webhook pages.
Ledger and dashboard under Sales → Payments: volume by provider and day, success rate, refunds, disputes, subscriptions, webhook log, settings, licence card.

HULO Payments

npm install @huloglobal/vendure-plugin-payments

Version0.2.7

Compatibility>=3.5.0 <4.0.0

Categorypayment-provider

Downloads713 monthly

Last updatedSep 25, 2026

View source View on NPM

Hosted checkout page — one mutation and a redirect; the plugin's own page shows every enabled method, drives each provider's client and brings the customer back paid. Nothing provider-specific in your storefront.
Hosted / embedded sessions — Stripe Payment Element, Adyen Drop-in, PayPal buttons, Mollie hosted checkout; cards, Apple Pay, Google Pay, Link, iDEAL, Klarna, Bancontact, SEPA and whatever the provider enables. 3-D Secure / SCA handled by the provider.
Server-side verification — the storefront never decides a payment state; the plugin re-reads the intent / session / order from the provider and checks amount, currency and order code before addPaymentToOrder.
Capture control — automatic or manual capture per method, partial captures, cancels, full and partial refunds from the normal Vendure refund flow.
Signed, idempotent webhooks — Stripe signatures, Adyen HMAC (+ basic auth), PayPal signature verification, Mollie fetch-back. Duplicate deliveries are ignored; results update Vendure payments and refunds.
Disputes — chargebacks land in the ledger and alert ops.
Saved cards — Stripe Customers and Adyen stored payment methods for signed-in customers; list and remove from the shop API.
Subscriptions — mark any product variant as billed daily / weekly / monthly / yearly (with a trial); the order charges the first period, then Stripe, PayPal and Mollie bill natively and Adyen renewals are charged by the plugin's scheduler from the stored card. Customers see and cancel their subscriptions through the shop API; admins pause, resume, cancel and see MRR.
Pay by link — one click in the admin creates a provider-hosted payment link for any unpaid order (draft orders, accepted quotes, phone orders); the webhook settles it.
Routing, rules and surcharges — provider order per channel with fallback on decline, an eligibility checker (amount band, currencies, countries, customer groups, signed-in only) usable on any payment method, and optional per-provider surcharges.
Ledger + dashboard — authorisations, captures, refunds, disputes, failures, renewals and pay-links by provider and day, success rate, webhook deliveries, subscriptions, settings — under Sales → Payments.

Works on MySQL, MariaDB and PostgreSQL. No provider SDKs: each provider is a few REST calls on the platform fetch.

In the admin

Payments (Sales → Payments): dashboard, a Payment methods tab (every provider × every channel, Add / Connect per cell), transactions, subscriptions, pay-by-link, the Providers tab with one-step Connect, and Settings.
Settings → Payment methods: a Connect a payment provider button; every HULO method in the list shows a brand mark, one status word (Live / Test mode / Ready, disabled / Not set up) and the first line of its description; and under each method a panel that explains the provider, lists what customers can pay with, tests the keys you typed, shows the webhook URL to paste and whether its secret is saved, and walks through going live.

Install

Bash

yarn add @huloglobal/vendure-plugin-payments

// vendure-config.tsimport { HuloPaymentsPlugin } from '@huloglobal/vendure-plugin-payments';plugins: [  HuloPaymentsPlugin.init({    publicBaseUrl: 'https://shop.example.com',        // webhook + return URLs    licenceKey: process.env.HULO_LICENCE_KEY_PAYMENTS, // optional — or activate in the admin    ops: { email: 'ops@example.com', webhookUrl: process.env.OPS_SLACK_WEBHOOK },  }),  AdminUiPlugin.init({    app: compileUiExtensions({ extensions: [HuloPaymentsPlugin.uiExtensions /* … */] }),  }),]

Storefront

The simplest integration is the hosted page:

Graphql

mutation { huloHostedCheckout(returnUrl: "https://shop.example.com/checkout/return", cancelUrl: "https://shop.example.com/checkout", methodCode: "paypal") { url expiresAt } }# methodCode is optional: it preselects that method on the page (one button per provider in your checkout).# → redirect the customer to `url`; they return to returnUrl?order=CODE&result=paid|pending

For an embedded checkout, drive the providers yourself:

Graphql

# 1. What to offer (preferred first, with public keys and capabilities)query { huloPaymentProviders { methodCode provider name publicConfig capabilities surcharge preferred } }# 2. A session for the active ordermutation { huloCreatePaymentSession(methodCode: "stripe", options: { returnUrl: "https://shop.example.com/checkout/return", savePaymentMethod: true }) {  provider clientSecret sessionId sessionData checkoutUrl publicKey environment config amount currency } }# 3. After the provider's client reports success, the normal Vendure step:mutation { addPaymentToOrder(input: { method: "stripe", metadata: { paymentIntentId: "pi_…" } }) { ... on Order { id state } ... on ErrorResult { errorCode message } } }

Provider	Client library	`metadata` for `addPaymentToOrder`
Stripe	`@stripe/stripe-js` Payment Element with `clientSecret`	`{ paymentIntentId }`
Adyen	`@adyen/adyen-web` Drop-in with `sessionId` + `sessionData`, `clientKey`, `environment`	`{ sessionId, sessionResult }` from `onPaymentCompleted`
PayPal	`@paypal/paypal-js` buttons with `createOrder: () => sessionId`	`{ paypalOrderId }`
Mollie	redirect to `checkoutUrl`; on return	`{ molliePaymentId }` (the `sessionId`)
Square	Web Payments SDK with `config.applicationId` / `locationId`	`{ sourceId }` (the card token)
Braintree	Drop-in with `clientSecret` as the authorization	`{ nonce, deviceData }`
GoCardless	redirect to `checkoutUrl`; on return	`{ billingRequestId }` (the `sessionId`)
Checkout.com	redirect to `checkoutUrl`; on return	`{ sessionId }`
Coinbase Commerce	redirect to `checkoutUrl`; on return	`{ chargeCode }` (the `sessionId`)
Bank transfer / pay later	show `instructions`	`{}`

Also available: huloSavedPaymentMethods, huloRemoveSavedPaymentMethod, huloMySubscriptions, huloCancelSubscription(id, atPeriodEnd), huloApplyPaymentSurcharge(methodCode).

Subscriptions

Tiers

Free tier	Licensed
Stripe: sessions, wallets, 3-D Secure, automatic/manual capture, refunds, disputes, signed webhooks; bank transfer; pay later	Adyen, PayPal, Mollie, Square, Braintree, GoCardless, Checkout.com, Coinbase Commerce
Hosted checkout page
Ledger, dashboard, webhook log	Subscriptions and the renewal scheduler
`hulo-payment-rules` eligibility checker	Saved cards, pay-by-link, provider routing, surcharges

Webhook events handled

Changelog

All notable changes to @huloglobal/vendure-plugin-payments are documented here. The format follows Keep a Changelog and this project adheres to semantic versioning.

[0.2.7] — 2026-09-25

Fixed

Payments → Payment methods tab: every channel cell stacks its status chip and buttons left-aligned with the same widths, columns are fixed-width and rows vertically centred, so nothing drifts out of line on multi-channel installs.

[0.2.6] — 2026-09-25

Fixed

Settings → Payment methods: the status chips sit in their own fixed column (mark · status · name), so they line up down the page whatever the method name length; the Payment methods tab's status chips and buttons share fixed widths for the same reason.

[0.2.5] — 2026-09-25

Fixed

Sharing a Stripe account with Vendure's own Stripe plugin no longer produces webhook errors. Events for PaymentIntents the plugin did not create (they lack its vendureOrderId stamp) are acknowledged and ignored instead of being applied to the order; the plugin never adds a payment to an order that already carries another method's payment.
A configured but disabled method still answers its webhook endpoint with 200 after verifying the signature, so the provider does not mark the endpoint as failing while the method is switched off.
Enabling, disabling or editing a payment method in Settings takes effect immediately (the plugin's method cache is cleared on the Vendure event) instead of after up to 30 seconds.

[0.2.4] — 2026-09-23

Added

Payment methods tab on the Payments page: every provider for every channel in one table, one status word per cell (Not added / Not set up / Ready, disabled / Test mode / Live). Add creates the payment method on that channel — disabled, no keys, with a descriptive name such as "Adyen · cards, wallets & 100+ local methods" — so it is visible under Settings → Payment methods straight away; Connect opens the Connect panel for that channel. "Add every missing method" fills the whole table in one click. The button on Settings → Payment methods now opens this tab.
POST /hulo-payments/methods { provider, channelId } behind it (admin, CreatePaymentMethod), idempotent per provider and channel.

[0.2.3] — 2026-09-23

Added

huloHostedCheckout(methodCode): the storefront can preselect one of the enabled methods, so a "Pay with PayPal" button opens the hosted page straight on PayPal. Without it the page opens on the first method in the channel's order, as before.

[0.2.2] — 2026-09-23

Changed

Settings → Payment methods reads at a glance. The Name column of the list now shows, for every HULO method, a brand mark, the name, one status word (Live / Test mode / Ready, disabled / Not set up) and the first line of the description — so twenty methods scan in seconds without opening each one. Other plugins' methods are untouched.
Providers tab regrouped. Providers are listed under four plain headings — Cards & wallets; PayPal, bank & local methods; Crypto; Offline & on account — as compact rows (mark, name, what customers can pay with, one status word). A row expands to the details, dashboard links, its payment methods and the Connect panel; nothing else is on screen until you ask for it.

[0.2.1] — 2026-09-23

Added

Settings → Payment methods explains itself. Any payment method that uses a HULO handler now shows a panel under the form: what the provider is, what customers can pay with, what the method supports (holds, refunds, subscriptions, saved cards, pay-by-link), where the keys come from with links to the provider dashboard, a Test these keys button that checks the unsaved form values, the webhook URL with a copy button and a saved/not-saved status, and the go-live checklist. Offline methods (bank transfer, pay later) get a plain-language "how it works" instead of keys and webhooks.
Connect a payment provider button on the payment-methods list, opening the Payments page on the Providers tab. The Payments page accepts ?tab= and ?connect=<provider> deep links.

[0.2.0] — 2026-09-22

Added

Hosted checkout page. huloHostedCheckout(returnUrl) returns a URL the storefront redirects to; the page shows every enabled method in the channel's preferred order, drives each provider's own client (Stripe Payment Element, Adyen Drop-in, PayPal buttons, Square Web Payments, Braintree Drop-in, hosted redirects, bank-transfer instructions), records the payment and sends the customer back with ?order=&result=. No provider code in the storefront. Branding (name, colour, logo) per channel in Settings.
Seven more payment systems, all behind the same contract: Square (cards, Apple Pay, Google Pay, Cash App Pay, Afterpay; holds, refunds, payment links, signed webhooks), Braintree (cards, PayPal, Venmo, wallets; holds, refunds), GoCardless (Bacs, SEPA, ACH direct debit, Instant Bank Pay; native subscriptions), Checkout.com (hosted payments page; holds, refunds, disputes, payment links, workflow webhooks), Coinbase Commerce (crypto), bank transfer and pay-later / invoice (offline methods settled from the order page, free tier).
Get-started wizard on the Payments page until the first provider is connected; Connect works for every provider, including automatic webhook setup for Square and Checkout.com.

[0.1.0] — 2026-09-21

Added

Four providers, one contract. Stripe (Payment Intents + Payment Element), Adyen (Sessions + Drop-in), PayPal (Orders v2) and Mollie (Payments API) as Vendure payment method handlers with server-side verification of amount, currency and order code.
Capture control and refunds. Automatic or manual capture per method, partial capture, cancel, full and partial refunds through Vendure's refund flow.
Signed, idempotent webhooks per provider at /hulo-payments/webhook/<provider>, updating payments, refunds and subscriptions; disputes recorded and alerted.
Saved cards (Stripe Customers, Adyen stored methods) with shop-API listing and removal.
Subscriptions from product-variant custom fields: native billing on Stripe, PayPal and Mollie, scheduler-billed renewals for Adyen, dunning, MRR, customer self-service.
Pay by link for any unpaid order from the admin (Stripe Checkout, Adyen Pay by Link, PayPal approve links, Mollie Payment Links).
Routing and rules. Provider order per channel with fallback, the hulo-payment-rules eligibility checker, optional surcharges.
One-step Connect on every provider card: verifies the keys with the provider, creates the webhook through the provider's API (Stripe, PayPal, Adyen Management API) and stores its secret, then creates the Vendure payment method — with links straight into each provider's dashboard, API keys and webhook pages.
Ledger and dashboard under Sales → Payments: volume by provider and day, success rate, refunds, disputes, subscriptions, webhook log, settings, licence card.