WooCommerce

Overview

This documentation covers the Acquired WooCommerce Plugin


Installation

Download & Install

  1. Download the plug-in zip file ‘acquired-com-for-woocommerce.zip’ from:
    https://wordpress.org/plugins/acquired-payments-gateway-for-woocommerce/
  2. In WooCommerce go to Plugins > Add New > Upload Plug-in

Activate Plug-in

  1. In WordPress Admin, navigate to Plugins.
  2. Click Activate under Acquired WooCommerce - Version X.X.X.

Configuration

Configuration is split between the Plugin Settings in WooCommerce and your Acquired Hub Settings.

Plugin Settings (WooCommerce Admin)

  1. Enable Acquired Gateway
    1. Tick to enable or disable the payment gateway.
  2. Title & Description
    1. Title: Displayed option name at checkout (e.g.,“Credit Card, Apple Pay”).
      1. Recommended: "Pay by Card, Apple Pay or Google Pay"
    2. Description: Shown under the title and in order confirmation emails.
      1. Recommended: "Checkout securely with Card, Apple Pay or Google Pay"
  3. Environment
    1. QA Environment: For QA/Sandbox testing (qahub.acquired.com).
    2. Production: For live transactions (hub.acquired.com).
  4. Company-Id
    1. Retrieve from the Acquired Hub → Settings → Reference IDs → Company-Id.
    2. Use the correct ID matching your environment.
  5. API Credentials
    1. In theAcquired Hub → Settings → API Access, copy your App ID and App Key for
      each environment.
  6. Signing Keys
    1. In the Acquired Hub -> Settings -> API Access, copy your Signing Key for each environment.
  7. Transaction Type
    1. Capture: Charge immediately.
    2. Authorise: Place a hold without immediate capture.
  8. Payment Reference
    1. Enter your website name (alphanumeric, no special characters).
  9. Debug Log
    1. Enable for detailed request/response logging.
    2. Disable in production to conserve server resources.
  10. Save Payment Methods
    1. Allows customers to save cards for future purchases.
    2. Also enable Save Cards in the Acquired Hub → Hosted Checkout → Cards →
      Settings.
  11. 3-D Secure
    1. Mandatory for UK/Europe in production.
    2. Ensure this toggle is ON to avoid failed transactions.
  12. Challenge Preferences
    1. Set your 3DSv2 challenge preference; note that issuing banks may override.
  13. Contact URL
    1. URL for customer support or “Need help?” links during checkout.
  14. Submit Type
    1. Customise the label on the hosted checkout’s submit button (e.g.,“Pay Now”).
  15. Update Card Webhook
    1. For Account Updater or Network Tokens:
      1. In the Acquired Hub → Hosted Checkout → Cards → Settings, enable Save Cards.
      2. Copy the provided webhook URL into this plugin field.

Acquired Hub Settings

  1. Hosted Checkout Configuration
    1. Follow the step-by-step guide here.
  2. Webhook Setup
    1. Go to the Hub → Settings → Webhooks, add your endpoint URL.
    2. Verify it responds with HTTP 200.
  3. IP Whitelisting
    1. Whitelist your WooCommerce server IPs in the Hub to allow payment requests to be accepted.
📘

IP Whitelisting

Please ensure your IP address is whitelisted. If this is not completed, all requests to Acquired will be blocked and prevent transaction processing.

Order Settings (Plugin)

Cancel Refunded Orders

Automatically mark orders as Canceled in WooCommerce when a refund occurs.

📘

Required

Enable this if you support lottery products.

Wallet for Failed Orders

Allows customers to retry payments on failed orders.

📘

Required

Enable this if you support lottery products.


Checkout Flow

  1. Customer chooses Acquired Hosted Checkout at WooCommerce checkout.
  2. Redirected to the hosted page for payment details.
  3. After successful payment, customer returns to the WooCommerce confirmation page.
  4. Order status updates automatically via webhooks (processing, completed, etc.).

Testing

  1. In plugin settings, turn on Staging Mode.
  2. Use test card numbers from your Acquired QA dashboard.
  3. Inspect logs under WooCommerce → Status → Logs and select acquired_gateway.

Troubleshooting

  1. Webhook Failures:
  • Confirm your endpoint is accessible publicly and returns HTTP 200.
  1. Signature Mismatch:
  • Verify the webhook secret in the plugin matches Acquired Hub.
  1. Payment Declines:
  • Check your debug log for provider-specific error codes.

Did this page help you?