How can we help?

1. Download the current stable BluePay WP ZIP.
2. Open your WordPress administration area.
3. Go to Plugins → Add Plugin → Upload Plugin.
4. Select the BluePay ZIP without extracting it.
5. Install and activate the plugin.

The official stable package is available from the BluePay WP Download page.

After activation, open the BluePay area in WordPress and choose the connection option. Sign in with the Blueway/BluePay identity that should control the website.

The website is then matched to the correct business relationship and its available website allowance.

No. Website ownership must be explicitly connected to the correct BluePay business account. BluePay should not assume that the WordPress administrator email is automatically the owner of the BluePay account.

In a WooCommerce environment, the customer completes the normal store checkout and selects BluePay where that payment method is enabled.

The payment then follows the BluePay payment flow and the connected provider. Once the payment is confirmed, the associated WooCommerce order can be updated accordingly.

A Blueway ID identifies the person or durable user identity.

A Business ID identifies the business relationship or organisation being operated.

One person may therefore have a Blueway identity while participating in one or more business relationships according to their authorised role.

Where supported by the account flow, BluePay login accepts the user's email, username or Blueway ID.

Yes, where your plan and team permissions allow it. Business members can be given roles appropriate to their work instead of sharing the business owner's credentials.

Business staff access is different from Blueway's own internal Staff Operations system.

Use the appropriate payment request or billing workflow inside BluePay. Enter the customer and payment details, generate the request, and then share the resulting payment link through an appropriate channel.

BluePay payment links have their own lifecycle and may be open, paused, cancelled, replaced or expired according to the request state.

BluePay coordinates the billing and payment workflow, while the connected payment provider processes the actual transaction according to that provider's service.

Provider credentials must therefore be correctly connected and active before provider-based payment collection can operate.

BluePay should not be understood as claiming custody of merchant funds. Payment providers and financial institutions process and settle funds according to their own arrangements.

Direct EFT can be used as a collection route where the business receives payment through its banking arrangement. Depending on the workflow, confirmation may require the appropriate reconciliation or confirmation process rather than assuming that every bank transfer is automatically verified.

Recurring billing creates an ongoing billing schedule rather than a single one-off payment request.

The schedule determines when collection activity should occur and keeps the customer billing relationship organised over time.

A mandate records the customer's authority or arrangement relevant to a recurring collection workflow.

The exact collection capability still depends on the connected provider, payment method and applicable operating requirements.

Failed recurring activity should remain visible for operational follow-up. BluePay can organise retries, collection status and customer follow-up according to the available billing workflow and provider capability.

A customer account can bring together billing activity such as invoices, charges, credits, payment requests, recurring arrangements, collections and account history.

This helps establish the customer's account position rather than viewing each transaction in isolation.

Depending on the available workflow, an invoice can be prepared, viewed, shared with the customer, printed and associated with an appropriate payment route.

A statement provides an account-level view of relevant customer billing activity over a period, helping the business and customer understand charges, credits, payments and outstanding position.

Depending on the verification process, evidence may include items such as proof of banking, proof of address, identity documentation or other supporting information required for the account review.

Pending means the review has not yet reached a completed decision. Ensure the requested information was submitted correctly and remains readable.

Where additional review is required, support may need to inspect the evidence before the status changes.

You should not provide your account password or Super Control Action PIN to support staff through ordinary support communication.

The Action PIN is a short approval credential used for sensitive Super Control actions such as publishing an authorised release or performing privileged platform changes.

It is an administrative control and is not the same as the normal BluePay account password.

1. Confirm that only the current BluePay WP version is active.
2. Check that the website is connected to the intended BluePay business account.
3. Clear WordPress/page cache where cached scripts may be stale.
4. Refresh the browser and retry the affected action.
5. Record the exact error message before contacting support.

Check the request status first. A payment request may have been paused, cancelled, replaced or expired.

Also confirm that the payment provider required by that request is connected and operational.

Check that the credentials correspond to the correct provider environment and account. Test and live credentials may not be interchangeable.

If the credentials are correct but the status still fails, capture the exact connection message before escalating it.

The official download page reads the currently published stable release from BluePay Central. If the release channel is temporarily unavailable, do not download an unofficial copy from another source.