DOCUMENTATION
Understand the integration before enabling live checkout.
Start with the responsibility model, choose the product path, configure matching test credentials and validate the full status lifecycle.
Start with the operating model
- Public statements and responsibilities: roles, boundaries and approved language.
- WooCommerce: public connector, data flow, test/live modes and callbacks.
- Mobile Counter: assisted cart, handoff and status tracking.
- Support: safe identifiers and operational ownership.
Go-live acceptance checklist
- Confirm merchant and PSP accounts, agreements and supported methods.
- Configure matching test credentials.
- Test success, partial/failed, cancelled and returned flows.
- Confirm order status and signed callback verification.
- Review customer copy, privacy, refunds and support ownership.
- Document acceptance, monitoring and rollback before live credentials.
WordPress and implementation questions
Can I sell products on WordPress without WooCommerce?
Not with the public WooCommerce connector alone. That connector is designed for WooCommerce; another WordPress commerce flow would need a separately confirmed HustlePay integration. Use matching test credentials and document success, partial, failed, cancelled, callback, monitoring and rollback behavior before production credentials are enabled.
What are the public plugin requirements?
The public listing at this snapshot states WordPress 6.1 or later and a WooCommerce checkout flow. Confirm the current listing before production. Use matching test credentials and document success, partial, failed, cancelled, callback, monitoring and rollback behavior before production credentials are enabled.
Can I switch directly to live mode?
No. Configure matching test credentials and validate successful, partial, failed, cancelled and callback flows before enabling live credentials. Use matching test credentials and document success, partial, failed, cancelled, callback, monitoring and rollback behavior before production credentials are enabled.
How are order updates returned to WordPress?
The connector uses return and callback context to reconcile the HustlePay session with the WooCommerce order. Signed callback handling must be tested. Use matching test credentials and document success, partial, failed, cancelled, callback, monitoring and rollback behavior before production credentials are enabled.
Where should I store API credentials?
Use the connector’s protected configuration and normal secret-management practices. Never send API secrets through contact or support forms. Use matching test credentials and document success, partial, failed, cancelled, callback, monitoring and rollback behavior before production credentials are enabled.
Where can I verify the current connector version?
Use the official WordPress.org listing and release notes, then confirm compatibility with the HustlePay team before production. Use matching test credentials and document success, partial, failed, cancelled, callback, monitoring and rollback behavior before production credentials are enabled.
Need account-specific documentation?
Request current onboarding material for the product, environment and PSP configuration.