TIER 01
Standard
Business-hours response, quarterly reviews and ticketed issue tracking.
SERVICE · INTEGRATION & SUPPORT
Onboarded in weeks, supported for life.
A five-stage onboarding programme, versioned documentation access and three support tiers aligned to your launch profile.
Onboarding timeline
- 1
Kickoff & scope
Technical discovery, jurisdiction scope, certification inventory and integration contract selection.
- 2
Sandbox access
Signed credentials, OpenAPI and WebSocket schemas, mock wallet and test driver.
- 3
Integration build
Joint engineering sprints, contract tests, regression suite and replay harness wired up.
- 4
Certification run
Lab submission pack, evidence review and regulator liaison for your jurisdiction.
- 5
Go-live & monitoring
Production switchover, observability dashboards and post-launch hypercare period.
Documentation access
Versioned REST and WebSocket schemas, event catalogue, settlement contracts and a changelog that never breaks semver silently.
Support tiers
TIER 02
Premium
Named technical liaison, weekly syncs and accelerated change windows.
TIER 03
24 / 7 Critical
Round-the-clock on-call, dedicated bridge and production incident command.
Frequently asked
How long does onboarding take?
How long does onboarding take?
Typical engagements run 8–12 weeks from kickoff to certified go-live, depending on jurisdiction count and aggregator path. Sandbox access is issued within 5 business days of NDA.
What does sandbox access include?
What does sandbox access include?
Signed credentials, OpenAPI and WebSocket schemas, a mock wallet, a deterministic test driver and a replay harness. Sandbox parity with production is asserted on every release.
Do you support direct operator integrations?
Do you support direct operator integrations?
Yes. Operators running their own platform connect via signed REST endpoints with idempotency keys plus a WebSocket session layer. One contract covers every certified title.
How do you version contract changes?
How do you version contract changes?
Versioned schemas with a public changelog. Breaking changes are gated behind a major version and an overlap window; we never break semver silently.
What is the SLA on hyper-care after go-live?
What is the SLA on hyper-care after go-live?
Premium and 24/7 tiers receive a named bridge for 30 days post-launch, with hourly response targets on production-blocking incidents. Standard tier follows business-hours response.
GET STARTED
Ready to launch with certified RGS technology?
Share your jurisdiction profile and target launch date, we will reply within one business day.