Description
Solidgate Card Payments and Other for WooCommerce integrates the Solidgate payment platform into your WooCommerce store with support for card payments and a range of alternative payment methods (APMs).
Card Payments
- Solidgate Card (
sg_card) — An inline card form powered by the Solidgate Payment Form SDK. Card details are entered directly on your checkout page inside a secure Solidgate-hosted iframe. Supports 3-D Secure, refunds, and async webhook confirmation.
Alternative Payment Methods
- MB WAY (
sg_mbway) — Push-notification payments for Portugal. The customer enters their MB WAY phone number and approves the payment on their MB WAY app. Available for EUR orders to Portuguese billing addresses. - Bizum (
sg_bizum) — Mobile payments for Spain. The customer is redirected to Bizum’s hosted page and returns to your site after approval. Available for EUR orders to Spanish billing addresses. - BLIK (
sg_blik) — One-click payments for Poland. The customer enters a 6-digit BLIK code from their banking app. Available for PLN orders to Polish billing addresses. - iDEAL (
sg_ideal) — Bank transfer payments for the Netherlands. Available for EUR orders to Dutch billing addresses. - Pay by Bank (
sg_openbanking) — Open Banking payments available across supported regions.
All payment methods share a single admin plugin, one REST namespace (solidgate/v1), and a unified webhook setup.
Webhook URL
All payment methods share a single webhook endpoint. Configure this URL in Solidgate Hub (Settings → Webhooks):
https://yoursite.com/wp-json/solidgate/v1/webhook
The plugin automatically identifies which gateway a webhook belongs to by trying each configured key pair in turn.
Requirements
- WooCommerce 6.0 or higher
- A Solidgate merchant account
- API keys from Solidgate Hub (separate keys for Card vs APM gateways)
- PHP 7.4+
External Services
This plugin communicates with the Solidgate payment gateway to process payments, refunds, and order status updates.
Service endpoint: https://gate.solidgate.com
Data sent:
- Payment details (amount, currency, order ID) when a customer initiates a payment.
- Refund requests initiated by the merchant from the WooCommerce order screen.
- Webhook signature validation on incoming payment status events.
When data is sent: Only when a customer places an order using a Solidgate payment method, or when the merchant requests a refund.
Solidgate Terms of Service: https://solidgate.com/terms-of-service/
Solidgate Privacy Policy: https://solidgate.com/privacy-policy/
No payment data is stored on your server. All sensitive card data is handled by Solidgate’s PCI-DSS compliant infrastructure.
Installation
- Upload the
solidgate-payments-for-woocommercefolder to/wp-content/plugins/. - Activate the plugin via Plugins → Installed Plugins.
- Go to WooCommerce → Settings → Payments.
- Enable and configure each payment method you want to use.
- Enter your Solidgate API keys and webhook keys for each method.
- Add the webhook URL above to your Solidgate Hub account.
FAQ
Where do I get my API keys?
Log in to Solidgate Hub, go to Settings → API Keys. You will need a separate key pair for Card payments and for APM (Alternative Payment Methods) payments.
How do I test the integration?
Use Solidgate’s sandbox environment. Contact Solidgate support to enable sandbox mode for your account, then use the sandbox API keys in the plugin settings.
Changelog
1.0.10
- Fix: Card payments could be charged twice on a single checkout attempt. The Solidgate Payment Form SDK can report a client-side “fail” (e.g. after timing out on a slow 3-D Secure/issuer round-trip) even though the authorization actually completes — and later settles — moments after. The plugin previously trusted that “fail” verdict blindly and immediately opened a brand-new, unrelated payment session for retry, leaving the original (now-successful) transaction unlinked to any WooCommerce order while the customer paid again on the new session. A new
/card/verify-failREST endpoint now checks Solidgate’s own record for the exact order_id before deciding: if it actually succeeded, that same transaction is reused to complete checkout instead of opening a new session; if it genuinely failed, the previous retry behavior applies. The same check now also coverscheckout_error(WooCommerce rejecting an already-charged submission for an unrelated reason, e.g. stock or coupon validation).
1.0.9
- Fix: gateway scripts/styles no longer enqueue on checkout when the payment method is disabled — previously every enabled AND disabled Solidgate gateway’s JS/CSS loaded on every checkout page load.
1.0.8
- Fix: Card payment form no longer fails to render on checkout —
rest_init_payment()/rest_update_payment()now force-load the WooCommerce cart/session (wc_load_cart()) before readingWC()->cart, since custom REST routes don’t get it auto-initialised the way WooCommerce’s own Store API does. Previously every init request 400’d with a false “Cart is empty” and the card iframe never mounted.
1.0.7
- Fix:
order_description/order_id/customer_emailfixes documented in 1.0.6 are now actually applied in code (see 1.0.6 entry below).
1.0.6
- Fixed:
order_descriptionis now built from WooCommerce cart item names instead of a generic label, making orders identifiable in the Solidgate dashboard. - Fixed: All string fields are clamped to their API maximum before submission (
order_description→ 255 chars,order_id→ 255 chars,customer_email→ 100 chars) — prevents error 2.01 length validation failures.
1.0.5
- Security: webhook routing now extracts the order_id prefix from the raw request body via regex rather than from parsed JSON, eliminating the possibility of routing decisions being influenced by attacker-controlled input before signature verification.
- Security: APM webhook handlers (MB WAY, BLIK, Bizum, iDEAL, Open Banking) now deduplicate by Solidgate event-ID using a transient, the same guard already in place for the Card webhook handler. Duplicate webhook retries from Solidgate are acknowledged and discarded without re-processing.
- Security: card payment init token is now bound to the WC session customer ID. A token created in one browser session cannot be replayed by a different session.
1.0.4
- Fix: Hub-initiated refunds (via Solidgate dashboard) now correctly create a WC refund record — previously the order status flipped to “refunded” but no refund amount was recorded in WooCommerce accounting or order history.
- Fix: Added duplicate refund submission guard for BLIK, Bizum, iDEAL, and Open Banking — submitting a second refund while one is already awaiting webhook confirmation now returns an error instead of sending a second API call.
- Fix: Duplicate webhook protection for Hub-initiated refunds via
_sg_processed_refund_idsorder meta — a second webhook for the same refund transaction no longer creates a duplicate WC refund record.
1.0.3
- Security: card payment init and update endpoints now always read amount/currency from the server-side WC cart — client-provided values are ignored to prevent price manipulation.
1.0.2
- Renamed plugin display name to “Solidgate Card Payments and Other for WooCommerce”.
1.0.1
- Security: poll-status REST endpoints now require
order_keyfor order enumeration protection. - Compliance: added
== External Services ==section documenting Solidgate API usage. - Compliance: text domain and class prefix updated for WordPress.org submission requirements.
1.0.0
- Initial release — unified plugin combining Card, MB WAY, Bizum, BLIK, iDEAL, and Pay by Bank gateways.
- REST namespace:
solidgate/v1. - HPOS (High-Performance Order Storage) compatible.