A payment solution for the business behind the store
We offer merchant payment solutions for eligible businesses using WooCommerce. Our assessment combines the product catalogue, entity and customer markets with your checkout requirements. A store platform alone does not determine eligibility, so we review the commercial operation as well as the technology. The proposal should address the actual goods or services being sold and the payment experience your customers need.
Gateway and checkout compatibility
We review the gateway route against your WooCommerce configuration and available integration options. Hosted checkout, supported extensions or an API approach depend on the selected provider. We establish the implementation scope before launch rather than presenting an unverified official eLotPay plugin. Your team should understand which components are supported and who maintains them as the store changes.
Subscription requirements
If your store uses subscriptions, we address manual and automatic renewals separately. Payment-method changes, retries, cancellations and plan updates are identified as specific requirements. We confirm those capabilities for the proposed extension and gateway combination. A successful one-off purchase is not treated as evidence that every later subscription event will behave correctly without additional testing.
Order states and reconciliation
We support the integration discussion around the connection between payment status and WooCommerce order records. Testing should include pending and failed outcomes, duplicate attempts, refunds and interrupted sessions. The agreed implementation needs a reliable way to associate provider references with orders. This gives support and finance a common basis for investigating a transaction or settlement enquiry.
Maintenance and commercial scope
We address the responsibilities for configuration, credentials, extension updates and escalation. Changes to the checkout need technical review, while changes to products, markets or the business model may affect the approved processing scope. We keep those workstreams connected so the store’s payment requirements remain clear after activation.
Scope the store before selecting a gateway connection
We review the products, seller entity, customer markets and checkout environment behind your WooCommerce store. Bring the relevant platform version, essential extensions, subscription requirements and existing payment setup into the discussion. Explain how orders are delivered and which staff manage refunds. We assess the merchant and the proposed connection together. Compatibility with your precise checkout, extensions and business model needs confirmation for the selected gateway rather than an assumption based on the WooCommerce name.
Separate store extensions from payment services
Your proposal should identify which acquiring and gateway functions are included and which store-side tools remain your responsibility. We review setup, payment and settlement requirements alongside the expected commercial charges. Subscription management, recurring collection and stored-payment functions need to be confirmed individually when relevant. Keep plugin or development costs separate from processing fees when comparing an offer. The approved products, markets and operating conditions should be clear before your team builds the live connection.
Test the order lifecycle your store uses
We support a practical implementation discussion around checkout, payment status, fulfilment and refunds. Test accepted and declined payments, a customer leaving checkout, repeated notifications and a refund started by an authorised staff member. Your team should know which provider reference belongs to each order and how unresolved results are investigated. Use the selected gateway's supported integration and documentation. A successful test purchase alone does not establish that all order and subscription exceptions work correctly.
Maintain compatibility through store releases
Theme changes, checkout redesigns, platform updates and additional extensions can affect an existing payment connection. We address the intended integration scope and support responsibilities so your team can plan changes sensibly. Keep a record of the live versions, enabled methods and relevant provider contacts. Before adding product categories or new customer markets, review the account scope as well as the store configuration. Never put live keys, passwords or card details into the downloadable business brief.
Start your eLotPay enquiry
Prepare your company country, website, customer markets, expected activity and essential payment requirements. Include the issue you are trying to solve, such as a new checkout, additional methods or a different settlement need. Our business-brief tool organises those details into a download for your next discussion. It currently saves the file on your device rather than submitting an application online. Do not include card details, passwords or identity documents in the brief. Any subsequent document sharing should use the agreed secure onboarding channel.
An integration your store team can maintain
We address the responsibilities behind the live checkout, including configuration changes, payment status messages and the records needed by support. The selected extension or connection should work within the agreed store setup. We review relevant test cases with the implementation scope so an order does not depend on an ambiguous browser return to establish its payment state.
Payment planning for the next store release
We consider catalogue changes and checkout changes as related but distinct workstreams. A new plugin may alter the integration, while a new product category or customer country may affect eligibility. We keep both in view so your store team understands what needs technical testing and what needs further business approval before launch. We keep the next step practical: define the business requirement, establish the available structure and set out the responsibilities in writing. The review should give your team a clear basis for evaluating the arrangement, including what is included and what remains conditional. Our focus is a payment relationship that reflects the business you operate.
Frequently asked questions
Will any WooCommerce payment plugin fit the account?
Compatibility with your checkout, platform version, extensions and approved business must be confirmed for the selected gateway. Do not assume an arbitrary plugin supplies the required connection.
What should be retested after a store update?
Review the checkout and affected payment functions, including order status, unsuccessful attempts, refunds and subscriptions where relevant. Keep the live versions and support responsibilities documented.