Ruba
Sign inApply for early access ›

Ruba product infrastructure

Let evaluation convert into billing

Capture the payment method first, grant access, and charge only when the trial completes.

Read the technical guide ›

A trial starts as a real subscription in the trialing state. The customer receives benefits immediately while the first payment waits for the end of the configured period.

Capability matrix

The closest configuration wins

Set a broad default, then override it for a narrower checkout when needed.

Product

Default trial

Sets the baseline unit and duration for every checkout of that product.

Checkout Link

Campaign override

Replaces the product value for customers arriving through one durable link.

Checkout Session

Request-specific override

Takes precedence when your application creates a customer-specific purchase.

Execution workflow

From card capture to conversion

  1. 01

    Checkout

    Ruba saves the payment method without collecting the plan amount.

  2. 02

    Trialing

    The subscription is live and all product benefits are available.

  3. 03

    Reminder

    Eligible trials notify the customer before the conversion charge.

  4. 04

    Charge

    At expiry, Ruba attempts payment and begins the regular billing period.

  5. 05

    Recovery branch

    A decline enters the normal past-due retry process instead of ending access immediately.

Deep dive specifications

Reminder timing follows trial length

  1. 01

    Three days or longer

    The conversion reminder is sent three days before expiry.

  2. 02

    One to three days

    The reminder is sent one day before expiry.

  3. 03

    Less than one day

    No conversion reminder is scheduled for the short window.

  4. 04

    Organization preference

    Disable these messages under Settings → Billing → Customer notifications when your product communicates instead.

01

Automatic conversion

Move into the first paid period without an application job.

02

Live edits

Extend, shorten, or end an active trial from the API or dashboard.

03

Expected charging

Notify eligible customers before the saved card is used.

04

Repeat-use checks

Detect prior trials through normalized identity and payment signals.

A repeat trial becomes a regular checkout

When prevention is enabled, Ruba compares the normalized email address and payment-method fingerprint with prior redemptions. An email alias such as user+alias@example.com is matched to its base address.

A match removes the trial from that checkout rather than blocking the customer from purchasing. The session refreshes at the regular paid terms so the customer can still continue.

Build with Ruba

Configure an evaluation period

Start with the product default and override only where the offer requires it.