HOW IT WORKS

Try it. Make it yours. Go live

Start a DemoSee integration process

Start in a real product environment. Configure it for your business. When you are ready, activate production without starting from scratch. This page is the whole process, prerequisites included.

01 / THE SEQUENCE

Understand → Try → Configure → Price → Buy → Launch

Six steps, in this order, for every product. The same sequence whether you buy one product or several.

01
Understand

What the product does, what it integrates with, what it needs. The product pages, in plain terms.

02
Try

A demo environment provisioned for your company — a real product tenant, not a mock-up. Every one of the seven products.

03
Configure

Supported settings, permissions, sample data and standard integrations. Saved to your tenant.

04
Price

The actual pricing or quote logic for your configuration. Where conditions need manual review, the flow says so instead of inventing a number.

05
Buy

Terms and agreement; KYC, compliance and payment steps where your case requires them.

06
Launch

A guided activation once agreement, payment and compliance checks are complete. Where eligible, your configured demo tenant becomes production; where separate production is mandatory, the configuration is transferred.

02 / DEMO TO PRODUCTION

The environment you configure is the one you launch

What carries over

Your tenant, its configuration, permissions and connected integrations. If a separate production deployment is required for your product or jurisdiction, the configuration is transferred without being redone — that reuse is the point.

Activation prerequisites and timing

Activation is a guided commercial step after the required agreement, payment and compliance checks. Where eligible, it uses the configured demo tenant; where separate production is mandatory, the configuration is transferred. Go-live timing follows your integrations and regulatory dependencies: fewer repeated setups and quicker product-controlled steps, not a fixed number of days. Retention of demo data is confirmed per product.

03 / INTEGRATION

Connect to the systems you already use

Integration is part of the demo, not a project that starts after the contract.

01
Get API access and documentation

Credentials and docs for the product tenant you created.

02
Connect your systems and providers

Your platform, data sources, PSPs or feeds — through documented APIs and the connectors live for your product.

03
Validate in the demo tenant

Run the integration against real product behaviour before anything is commercial.

04
Carry the configuration into production

Activation keeps what you validated; a ported deployment keeps the configuration.

THREE WAYS TO RUN IT
STANDALONE

One product on its own. The product tenant is the whole system.

CONNECTED R* PRODUCTS

Native integrations where products meet: accounts, payments, risk, execution, experience.

YOUR EXISTING OR THIRD-PARTY STACK

Documented APIs. Which third-party connectors already exist is stated per product in the demo; the rest is scoped engineering, and we say so.

04 / PRICING & PREREQUISITES

Transparent where it can be, explicit where it cannot

Pricing and quote logic are shown per product inside the flow, for the configuration you built. There is no universal rate on this site — and no fake instant price when a condition still needs a person.

01
Business email and company details

To create the tenant.

02
Agreement and compliance checks

As your product, jurisdiction and activity require — before activation, never silently skipped.

03
Credentials for your own integrations

PSPs, feeds, KYC providers or platforms you connect yourself.

TWO WAYS TO START

Start a demo, or talk to a specialist first

Product fit, integration planning, regulatory dependencies and deployment choices — when your case needs more than the standard setup, a person is part of the process, not a workaround for it.

Start a DemoSpeak to a specialist