WooCommerce v2
Overview
This documentation covers version 2 of the Acquired WooCommerce Plugin — a complete rewrite of the original integration. It now uses the Acquired REST API and delivers a fully hosted checkout experience.
v2 Highlights:
- Significantly improved performance and reliability.
- Enhanced security, including mandatory 3-D Secure for applicable regions.
- Greater flexibility and configurability.
Importantv2 must be installed separately from the legacy plugin. They cannot run side-by-side.
Key Differences from the Legacy Plugin
- Separate Installation: Deactivate and remove the legacy plugin before installing v2.
- Legacy Payments: Transactions via the old HPP integration remain on the legacy API and cannot be
refunded or modified by v2. - Manual Configuration: No automatic migration; you must manually set up credentials and webhooks for v2.
- New API & Hosted Checkout: v2 uses our RESTful API plus a fully hosted checkout, replacing the legacy HPP flow.
Compatibility & Migration Notes
- Uninstall Legacy Plugin:
- Log in to WordPress Admin → Plugins.
- Deactivate and delete Acquired WooCommerce Plugin (legacy).
- Existing Payments:
- Historical transactions remain on the legacy system.
- To refund or void, log in to the Acquired Hub (hub.acquired.com) and process
refunds there.
- Sandbox vs Production Credentials:
- Acquire separate Company-Id, App ID, and App Key for sandbox (qahub.acquired.com) and production (hub.acquired.com).
Upgrade Path for Existing Merchants
If you already have our legacy Acquired plugin installed and active, follow these pre-activation upgrade steps to minimise downtime (~10 seconds):
- Add New Plugin (Do Not Activate):
- Download the Plug-in Zip file
acquired-com-for-woocommerce.zip
from:
https://github.com/acquiredcom/acquired-payments-woocommerce/releases/tag/2.0.0-beta.5 - In WooCommerce go to Plugins > Add New > Upload plug-in
- Do not activate the new plugin yet.
- Download the Plug-in Zip file
- Configure Hosted Checkout:
- In your Acquired Hub, complete the Hosted Checkout setup as detailed here.
- Configure New Plugin Settings:
- In WooCommerce Admin → Acquired.com Gateway settings, enter your Company‑Id, App ID, App Key, and other required settings as outlined here.
- Switch Plugins:
- Deactivate the legacy Acquired plugin.
- Activate the Acquired WooCommerce Plugin v2. This transition will cause a brief downtime of approximately 10 seconds.
Installation
Download & Install
- Download the plug-in zip file ‘acquired-com-for-woocommerce.zip’ from:
https://github.com/acquiredcom/acquired-payments-woocommerce/releases/tag/2.0.0-beta.5 - In WooCommerce go to Plugins > Add New > Upload Plug-in
Activate Plug-in
- In WordPress Admin, navigate to Plugins.
- Click Activate under Acquired WooCommerce - Version 2.0.0-beta.5.
Configuration
Configuration is split between the Plugin Settings in WooCommerce and your Acquired.com Hub Settings.
Plugin Settings (WooCommerce Admin)
- Enable Acquired.com Gateway
- Tick to enable or disable the payment gateway.
- Title & Description
- Title: Displayed option name at checkout (e.g.,“Credit Card, Apple Pay”).
- Description: Shown under the title and in order confirmation emails.
- Environment
- Staging: For QA/Sandbox testing (qahub.acquired.com).
- Production: For live transactions (hub.acquired.com).
- Company-Id
- Retrieve from the Acquired.com Hub → Settings → Reference IDs → Company-Id.
- Use the correct ID matching your environment.
- API Credentials
- In theAcquired.com Hub → Settings → API Access, copy your App ID and App Key for
each environment.
- In theAcquired.com Hub → Settings → API Access, copy your App ID and App Key for
- Transaction Type
- Capture: Charge immediately.
- Authorise: Place a hold without immediate capture.
- Payment Reference
- Enter your website name (alphanumeric, no special characters).
- Debug Log
- Enable for detailed request/response logging.
- Disable in production to conserve server resources.
- Save Payment Methods
- Allows customers to save cards for future purchases.
- Also enable Save Cards in the Acquired.com Hub → Hosted Checkout → Cards →
Settings.
- 3-D Secure
- Mandatory for UK/Europe in production.
- Ensure this toggle is ON to avoid failed transactions.
- Challenge Preferences
- Set your 3DSv2 challenge preference; note that issuing banks may override.
- Contact URL
- URL for customer support or “Need help?” links during checkout.
- Submit Type
- Customise the label on the hosted checkout’s submit button (e.g.,“Pay Now”).
- Update Card Webhook
- For Account Updater or Network Tokens:
- In the Acquired.com Hub → Hosted Checkout → Cards → Settings, enable Save Cards.
- Copy the provided webhook URL into this plugin field.
- For Account Updater or Network Tokens:
Acquired.com Hub Settings
- Hosted Checkout Configuration
- Follow the step-by-step guide here.
- Webhook Setup
- Go to the Hub → Settings → Webhooks, add your endpoint URL.
- Verify it responds with HTTP 200.
- IP Whitelisting
- Whitelist your WooCommerce server IPs in the Hub to ensure webhook events
are not blocked.
- Whitelist your WooCommerce server IPs in the Hub to ensure webhook events
Order Settings (Plugin)
Cancel Refunded Orders
Automatically mark orders as Canceled in WooCommerce when a refund occurs.
RequiredEnable this if you support lottery products.
Wallet for Failed Orders
Allows customers to retry payments on failed orders.
RequiredEnable this if you support lottery products.
Checkout Flow
- Customer chooses Acquired Hosted Checkout at WooCommerce checkout.
- Redirected to the hosted page for payment details.
- After successful payment, customer returns to the WooCommerce confirmation page.
- Order status updates automatically via webhooks (processing, completed, etc.).
Testing
- In plugin settings, turn on Staging Mode.
- Use test card numbers from your Acquired QA dashboard.
- Inspect logs under WooCommerce → Status → Logs and select
acquired_gateway
.
Troubleshooting
- Webhook Failures:
- Confirm your endpoint is accessible publicly and returns HTTP 200.
- Signature Mismatch:
- Verify the webhook secret in the plugin matches Acquired Hub.
- Payment Declines:
- Check your debug log for provider-specific error codes.
Updated 4 days ago