SecurePay Bridge - Frequently Asked Questions

SecurePay Bridge is a system that connects a high-risk WooCommerce site with a low-risk site for secure payment handling.

Yes, both Site A (high-risk) and Site B (low-risk) must have WooCommerce installed and configured.

No. All payments are processed on Site B using its own gateways.

Yes, the plugin on Site B requires a valid license key for redirection and order syncing to work correctly.

Yes, you can configure the product selection logic in Site B settings based on conditions like price, categories, or specific products.

Yes, customer and order data are securely passed as encoded parameters and processed internally on both WordPress sites.

If the payment fails on Site B, the status is sent back to Site A via the REST API and the order is marked accordingly.

Yes, SecurePay Bridge works with WordPress multisite, but each subsite must have its own separate plugin setup and license if needed.

Generally yes, as the plugin uses standard WooCommerce hooks. However, some themes with heavily customized checkouts may require adjustments.

Yes, affiliate or tracking parameters can be passed and preserved during the redirection using the supported query string fields.

The order remains in the original status on Site A. Site B will not send status updates unless the customer reaches the payment and completes it.