How to Install and Configure SecureHold WP: Complete Setup GuideFrom plugin installation to your first test security deposit hold

Before you install SecureHold WP

SecureHold WP is a WooCommerce extension. Before installing it, confirm that the following are already in place on your site.

• WordPress is installed and running a recent, supported version.
• WooCommerce is installed, activated and configured with at least one product.
• WooCommerce Stripe Gateway is installed and configured with your Stripe API keys.
• Stripe account is active and accessible. You will need both your test and live API keys during setup.
• SSL is enabled. Stripe requires HTTPS for live payment processing. Confirm your site is served over HTTPS before going live.
• WordPress admin access with the ability to install and activate plugins.
• Start in test mode. It is strongly recommended to complete your initial setup and testing using Stripe test mode before accepting any real customer payments with deposits.

Install SecureHold WP

Once the prerequisites are confirmed, installation follows the standard WordPress plugin process.

1. 1Download the SecureHold WP plugin package from your account or the distribution link provided after purchase.
2. 2Log in to your WordPress admin dashboard.
3. 3Go to Plugins, then Add New, then Upload Plugin.
4. 4Select the SecureHold WP ZIP file and click Install Now.
5. 5Activate SecureHold WP once the installation is complete.
6. 6Open the SecureHold WP settings or setup page to begin configuration.

Connect or verify Stripe configuration

SecureHold WP works with your existing WooCommerce Stripe Gateway connection. You do not need to add separate API keys unless your setup requires it.

• Test mode vs live mode. Start in test mode. Stripe test mode uses a separate set of API keys and test card numbers. Deposits created in test mode do not affect real funds.
• API keys. Confirm that the WooCommerce Stripe Gateway has your correct publishable and secret keys for the mode you are testing in. Using test keys in live mode or live keys in test mode will cause failures.
• WooCommerce Stripe Gateway version. Ensure the gateway is up to date. Older versions may not support the PaymentIntent capture flow that SecureHold WP requires.
• Webhook endpoint. Stripe needs to deliver events to your store. Before going live, configure a Stripe webhook for WooCommerce security deposits and use SecureHold WP’s Health Check to help verify delivery.
• Avoid mixing test and live objects. Do not create orders in test mode, then switch to live keys. Stripe objects created in one mode are not accessible in the other.

Configure your first deposit rule

After activation and Stripe connection, configure how deposits are created for your orders. If you are still planning the workflow, start with the guide to add a security deposit to WooCommerce.

• Deposit amount. Set a global deposit amount (fixed value or percentage) that applies to all qualifying orders. This is the amount that will be held on the customer’s card at checkout.
• Hold creation trigger. Choose at which point in the order lifecycle the hold is created. Typically this is at checkout when the customer submits payment.
• Expected order status. Configure which WooCommerce order status should trigger or confirm deposit hold creation.
• Manual capture. By default, SecureHold WP requires you to manually capture the hold from the order admin. This gives you control over when funds are collected.
• Manual release. Release actions are also manual by default. You review the order and release the hold when appropriate.
• Pro plan product and category rules. If you are using the Pro plan, you can configure different deposit amounts per product or category, useful for stores with varied rental inventory or service types.

Run Health Check before your first test order

Before placing a test order, run the SecureHold WP Health Check. It reviews the most common configuration points that can silently cause deposit workflows to fail.

1. 1Open the Health Check from the SecureHold WP admin page.
2. 2Review Stripe status: API connection, mode (test or live) and key validity.
3. 3Review WooCommerce status: gateway active, required settings in place.
4. 4Check webhook configuration: endpoint URL, registered events and recent delivery status.
5. 5Fix any warnings or errors before proceeding. Do not skip warnings and assume they will not cause issues in production.

Create your first test order

With Health Check passing, place a complete test order to verify the deposit workflow end-to-end. Use the dedicated checklist to test WooCommerce security deposits in Stripe test mode before accepting live orders.

• Use Stripe test mode. Use a Stripe test card number to place a real WooCommerce test order from the front end of your store.
• Verify the main order payment. Confirm that the order payment processes correctly and the order reaches the expected WooCommerce status.
• Verify the deposit hold. Check the WooCommerce order admin to confirm the deposit hold is active and shows the correct amount.
• Test capture. From the order admin, capture the deposit hold. Confirm that the captured amount appears in your Stripe test dashboard.
• Test release. Place a second test order and release the hold from the order admin. Confirm the hold disappears from both the Stripe dashboard and the order admin.
• Review order notes or logs. If SecureHold WP records deposit events in order notes, review them to confirm the expected actions were logged.

What to do before going live

Before switching to live mode and accepting real customer orders with deposits, work through this checklist.

• Test mode successful. At least one full test order completed: checkout, deposit hold created, capture tested, release tested.
• Webhooks working. Health Check confirms the webhook endpoint is receiving and processing Stripe events correctly.
• Deposit amount correct. The configured deposit amount matches what your business model requires.
• Order admin actions verified. You have confirmed that capture and release work from the WooCommerce order screen in test mode.
• Customer communication reviewed. If your store communicates deposit details to customers in order emails, product descriptions or checkout text, review that messaging for accuracy before going live.
• Support process ready. Have a plan for handling customer questions about deposit holds, particularly for customers who are unfamiliar with pending charges on their bank statement.