Product updates
A clear record of new features, reliability improvements, and merchant experience updates.
Be the first to know when new features and reliability improvements are released. Unsubscribe at any time.
Visitors can now subscribe to HandyPay product updates from the public changelog, while signed-in merchants can subscribe in one click using their account email. Every message includes a direct unsubscribe option.
Routine background events no longer create vague account activity notifications, and repeated webhook deliveries no longer duplicate the same alert. Mobile transaction history also resets cleanly when a merchant signs out or switches accounts.
Developers can now download an OpenAPI 3.1 contract covering every public endpoint, including embedded payments, refunds, disputes, and payout account details. Webhook guidance now uses raw-body, timing-safe signature checks and explains independent endpoint secrets, event deduplication, and reliable payment reconciliation. Existing API keys and request paths are unchanged.
Linked Google, Apple, and password identities now return to one authoritative merchant account without restarting setup. Existing onboarding, payment history, API keys, webhooks, and payout settings remain intact, while a new database guard prevents active duplicate accounts from being created again.
API and WHMCS integrations can now retrieve completed checkout sessions consistently, receive additional success and failure events for delayed payment methods, and rely on signed merchant webhook deliveries that retry after temporary endpoint failures. Existing API keys and integrations continue to work.
Payout details now use the expected bank-arrival date supplied by our payment network, show a clearer stage-by-stage timeline, and reflect automatic, manual, or review-paused payout schedules consistently across web and mobile.
HandyPay mobile now confirms sign-in, verification, and account setup status with the server before choosing the next screen. This reduces stale sessions, repeated setup screens, and sign-in loops across email, Google, and Apple.
Refund request decision emails now retry automatically if an initial delivery is interrupted, helping merchants receive a clear status update after each review.
Merchants and developers can now change the quantity on an active subscription. Each update includes a clear choice to prorate on the next invoice, charge the adjustment immediately, or make the change without proration.
Test API keys now use a dedicated test account with separate products, customers, payments, subscriptions, and webhook endpoints. The merchant portal includes a Test Mode workspace so test activity never appears beside live business activity.
E-commerce and WHMCS checkouts can now show additional payment methods when they are eligible for the merchant, currency, and customer. Card checkout remains available as a safe fallback for account and currency combinations that do not support dynamic methods.
Successful payments now remain visible in Payouts while they settle. Merchants can distinguish funds available to pay out from pending settlement and, when available, see the date each pending amount is expected to become available on web and mobile.
Password recovery and login verification now work more reliably, verification codes can be pasted as a complete code, and language switching works on public sign-in pages. Mobile web inputs no longer trigger unwanted focus zoom, while normal pinch-to-zoom remains available.
The merchant portal and mobile app now refresh transaction activity when a payment update arrives and when merchants return to the app or revisit key screens. Dashboard totals and recent activity are less likely to show stale pending states.
Merchants in these newly supported countries can now select their country during onboarding, enter the appropriate bank details, and see settlement amounts in their local currency. The expanded country picker is available on web and mobile.
Payouts now separate pending settlement from available balance, show expected arrival and payout schedule, and list the payments, refunds, fees, and adjustments included in each payout when available. The same clearer wording is available on web and mobile.
If an account is placed under review, merchants can still read existing transactions and account history while payment actions, account changes, and automatic payouts are paused. A persistent notice explains the restriction and how to contact support.
Returning from secure account setup now distinguishes completed setup, pending review, and actions still required. Expired setup links refresh safely, reducing repeated forms and false onboarding loops.
HandyPay now publishes service availability and product updates in the merchant portal and on public pages, with a live status indicator in navigation.
When HandyPay Support needs more information, merchants can use a secure request link to review the request, upload supported files, add context, and submit everything in one place.
Declined attempts now appear in transaction history with status, reason, and attempt context, helping merchants understand why a customer payment did not complete.
Merchants can request refunds from web or mobile, see a pending state while the request is reviewed, and receive updates when the refund is processed.
HandyPay now supports English and Spanish across core merchant journeys, selects a sensible language for each merchant, and displays dates in the browser’s local time zone.
Transaction details opened from Home now match Activity, charts and controls fit smaller screens more reliably, and Android layouts receive the same responsive behavior.
Webhook, ledger, refund, dispute, and reconciliation paths now fail safely and retry more predictably. Completed payments are less likely to remain pending when a downstream update is interrupted.
A persistent feedback control is available across sign-in, onboarding, and the merchant portal, making it easier to report a problem with the current page and include useful context for support.
