Changelog

Checkout is more reliable across older and newer accounts, keeps merchant references intact, and honors the shopper's final payment method and provider choice, including the correct Paystack flow

Payments Intelligence now opens normally when a report has no exclusions instead of showing an error page

Two-factor sign-in now keeps the active challenge while you move through the login flow, and backup codes work as expected

List requests in the Node.js, Python, Go, PHP, and Rust SDKs now handle paginated API responses consistently

What's New notices can now be dismissed and automatically leave the sidebar 24 hours after being read

The rebuilt reevit init wizard now detects the framework, router, and installer; creates separate scoped project test credentials; configures the sandbox simulator and checkout origin; installs the right SDKs; generates runnable checkout, server, and signed-webhook integrations; and verifies the new credentials before handing off exact local commands

reevit doctor now checks the project manifest, credential scopes, simulator, allowed origin, generated files, checkout route, and signed webhook behavior; --strict makes runtime warnings fail in CI

The official Rust SDK is now part of the developer toolkit, with an async Rustls client for payments, checkout sessions, connections, subscriptions, fraud, customers, payment links, webhooks, routing rules, and invoices

Moolre is now available as a Ghana mobile-money connection for direct MTN, Telecel, and AT collections, with separate sandbox/live credentials and OTP continuation through the payment confirm endpoint

Moolre callbacks are verified against the provider's status API before payment state changes are applied; the provider remains explicit-routing-only during its pilot

Product analytics now connects the full Reevit journey, from signup and the onboarding questionnaire through provider setup, developer tooling, payments, routing, workflows, subscriptions, and the product tour. It masks rendered text, inputs, attributes, secrets, and dynamic route identifiers

Session replay, heatmaps, organization-level funnels, browser error context, and privacy-safe same-origin event delivery are now available for diagnosing where customers get stuck without collecting payment details or customer data

Set up Reevit in one command: reevit init logs you in from the browser (no key copying), detects your stack, installs the right SDK, wires your environment, and writes working webhook and checkout code. Then reevit doctor proves it all works, including that your webhook handler accepts genuine signed events and rejects tampered ones

reevit login now opens your dashboard to authorize the CLI with a freshly minted test-mode key. Approve in the browser, and the key lands in your terminal without ever being shown on screen

reevit doctor --e2e fires a real sandbox payment through the simulator and delivers the platform-generated event to your local handler with a production signature, verifying your entire integration pipeline before you go live

The CLI reports anonymous usage (command, version, OS; never file contents or keys) so we can improve it; opt out any time with REEVIT_TELEMETRY=0 or DO_NOT_TRACK=1

The compare page joins the site's new dark look, a cleaner feature-by-feature table against direct integrations and other orchestrators, with provider counts that stay in sync with what we actually support