Log in to your Simplero account to give feedback

Feature Requests

Include Transaction data in Triggers to Webhooks when Trials and Manual Payment is used
Currently, when a product is configured with a free trial followed by manual (invoice) payment, Simplero does not generate a transaction object at the time of order or at the moment the customer confirms "pay by invoice" post-trial. This creates a significant gap in workflows that rely on webhook data to generate and send invoices through external billing systems like Xero or QuickBooks. As a result: No transaction data is included in the initial webhook. No second webhook is triggered unless the admin manually registers payment. This prevents external systems from issuing time-sensitive invoices, tracking accounts receivable, or automating financial compliance processes. Proposed Solution ------------------- When a customer selects a manual payment method (e.g., invoice) at the end of a free trial, Simplero should: Immediately create a transaction object representing the expected payment. Include that transaction data in a webhook (e.g., purchase.payment_due or purchase.updated) even if the payment is pending or unpaid. Benefits --------- Enables external invoice generation and accounting system integration. Avoids requiring manual admin action just to trigger automation. Supports B2B workflows where invoice-based billing is the standard. Provides better transparency for customers and finance teams alike. Use Case Example ------------------- A customer signs up for Price that includes a 7-day trial. We need to automatically issue an invoice to the purchaser. But Simplero doesn't send the transaction info until we manually mark the payment, breaking any ability to automate a key business process. Request -------- Please support inclusion of transaction data at the point where the customer confirms payment intention (even if it's unpaid), or consider adding a new webhook trigger for this specific case.
1
Add support for Stripe Sandboxes so customers can run end-to-end payment tests inside Simplero without touching live data or moving real money.
Problem --------- Simplero only connects to a live Stripe account. If you switch your Stripe account Test Mode, payment attempts with test cards will fail. If you attempt to use a Stripe Sandbox, Simplero will fail the "test access" step, as Simplero does not use Stripe Connect. Stripe has deprecated the account-wide test mode toggle in favour of per-environment Sandboxes. Teams now get up to five fully isolated environments, each with its own API keys and webhooks, and recommend Sandboxes over test mode for most QA tasks. Because Simplero cannot connect to either test mode or a Sandbox, merchants must run risky one-cent live charges or clone the product in a separate Stripe account, adding friction for every launch or price change. Why this matters ----------------- Risk reduction: No accidental live charges during checkout or subscription testing. Faster QA: Customers, marketers, and support staff can test pricing, coupons, failed payments, and webhooks in minutes instead of waiting for refunds or reconciling live transactions. Parity with peers: Platforms like Shopify, WooCommerce, and MemberPress already expose Stripe test environments, making this gap more visible to prospects evaluating Simplero. Feature proposal ------------------ Environment selector in Settings → Payment Processors → Stripe with two options: Live, Sandbox. Credential fields for each environment: Publishable key Secret key Toggle between Live + Sandbox mode for payment process configuration. Visual indicator (banner or badge) on checkout screens when an order form is using a non-live environment, similar to Stripe’s own purple “Test data” strip.
1
Load More