Skip to main content

Pilot and activation

In one sentence

A trial is self-serve in the Test environment on your own sandbox credentials, it is measured against six concrete events rather than a feeling, and going live is a separate, gated, two-administrator step.

Written for the person sponsoring a trial.

How a trial starts​

Nobody sits through a slide deck. The path is the product:

  1. Open the seeded demo. A full workspace, already populated with synthetic sellers, payments, decisions and cases. No account needed. About two minutes.
  2. Create an account and a workspace. Enrol two-factor; connecting a provider is refused until you do.
  3. Connect your own sandbox: a Stripe restricted test key, a HitPay sandbox key, or an Airwallex sandbox. The credential is validated with the provider before it is stored. A live key, a secret key or an under-scoped key is refused with the reason named.
  4. Run test traffic from the dashboard or from code, and read the decisions, the traces and the payout workflow on your own keys.

The acceptance bar the product is built to: a stranger goes from a link to a routed test payment in under thirty minutes without talking to anyone. The manual is the walkthrough.

What counts as a qualified trial​

The product uses a strict definition, measured from events the system recorded. It is never ticked by hand, and a demo workspace never counts.

  • ProvidersTwo provider connections that you own, active.
  • TrafficOne hundred payment intents through the Gate and the router.
  • WebhooksA webhook endpoint of yours configured and at least one delivery received.
  • RulesA policy of your own, published through the full lifecycle.
  • PeopleA second person invited into the workspace.
  • EvidenceA savings report generated from your own imported history and reviewed.

The overview screen keeps score. If you reach all six you have seen every part of the product working on your own data, and the conversation about a pilot order has something to stand on.

What going live requires​

Live is not a switch. It is a separate environment, and the entitlement to use it is granted under dual control by two platform administrators against evidence that has to match anchors deployed with the software. The Environment screen lists the requirements:

  • a counsel opinion on file,
  • safety acceptance tests passed,
  • a signed pilot order with volume limits in it,
  • per-merchant caps: a daily send cap, a per-payout cap, a daily refund cap and a per-refund cap, all four required (an absent limit is not "unlimited"; it refuses live dispatch entirely),
  • two platform administrators, each with a fresh second factor.

Then live connections are created, each with live credentials, each dual-approved. Nothing from Test is promoted. Today no workspace holds the entitlement and the deployment-wide live switch is off.

What is not yet published​

Pricing is not published; the trial is the pitch and the commercial conversation follows a qualified trial. A written service-level agreement, a data-residency commitment and third-party certifications are not published either. Boundaries keeps that list current.

Who to talk to​

The marketing site at pehmen.huper.technology is the front door. The product itself is at pehmen.huper.technology/dashboard.