AcquirerOS Payment Gateway for WooCommerce

AcquirerOS Payment Gateway for WooCommerce adds the AcquirerOS-compatible payment method to WooCommerce, with support for both classic checkout and the WooCommerce Checkout Block.

For most merchants, Redirect / Hosted Checkout is the recommended payment mode. Customers complete card entry on the hosted payment page instead of entering card details directly into WordPress.

S2S / Direct API is also available as an advanced integration option for merchants whose payment environment and compliance requirements support direct card-data processing.

Payment modes

• Redirect / Hosted Checkout (Recommended): WooCommerce sends the required order and customer information to the configured Hosted Checkout endpoint and redirects the customer to the returned secure payment URL. Card number, expiry date and CVV/CVC are not collected by this plugin in Redirect mode.
• S2S / Direct API (Advanced): Card number, expiry date and CVV/CVC are entered during WooCommerce checkout and transmitted server-to-server to the configured payment endpoint for payment processing. Merchants using this mode are responsible for confirming their PCI DSS scope and compliance obligations with their payment provider and qualified compliance advisers.

WooCommerce integration

The plugin integrates with standard WooCommerce payment and order workflows and includes support for:

• Classic WooCommerce checkout.
• WooCommerce Checkout Block.
• High-Performance Order Storage (HPOS).
• Redirect / Hosted Checkout payment flows.
• S2S / Direct API payment flows.
• 3D Secure payment returns.
• Asynchronous payment notifications.
• WooCommerce order status updates.
• Duplicate callback protection.
• Diagnostic logging for troubleshooting.

External service

This plugin connects to the payment endpoint configured by the merchant in WooCommerce > Settings > Payments > AcquirerOS. This external service is required to create and process payment transactions.

Depending on the selected payment mode and transaction requirements, information sent to the configured payment endpoint can include:

• Order number and transaction identifiers.
• Order amount and currency.
• Product and order item information.
• Billing and shipping details.
• Customer name, email address and phone number.
• Customer IP address.
• Browser and user-agent information.
• Payment return and notification callback URLs.

In S2S / Direct API mode only, card number, expiry date and CVV/CVC are also transmitted to the configured payment endpoint for payment processing.

AcquirerOS service: https://acquireros.com/

AcquirerOS Privacy Policy: https://acquireros.com/privacy/

AcquirerOS Terms of Service: https://acquireros.com/terms/

Merchants should publish appropriate privacy disclosures and ensure that their use of the configured payment service complies with applicable laws, contractual requirements and payment-card security requirements.

Security notes

• Redirect / Hosted Checkout is the recommended mode for most merchants.
• Hosted Checkout is the default payment mode for new installations.
• Card numbers and CVV/CVC are not stored in WordPress order metadata by this plugin.
• Card numbers and CVV/CVC are not written to the plugin diagnostic log.
• In Redirect mode, card details are not collected by the plugin in WordPress.
• Payment callbacks use per-order random callback tokens.
• Asynchronous notification callbacks require a valid gateway signature.
• Callback merchant, gateway, order number, amount and currency are validated before an order is updated.
• Asynchronous notification callbacks accept POST requests only.
• Configured payment endpoints must use public HTTPS URLs.
• Duplicate successful callbacks are handled idempotently through WooCommerce payment status checks.
• Payment requests use the WordPress HTTP API.