Skip to content
Platform Module

Replace inbox-driven implementation with a tracked path from sign-up to go-live

Every ISO knows the cost of onboarding that disappears into email chains. The onboarding workspace replaces that with defined steps — company profile, merchant and partner data, acquirer credentials, parallel testing, and go-live — all tracked in one visible workspace with evidence and sign-off at each stage.

What it does

Tracked steps replace the invisible inbox project

Company profile, merchant and partner data, acquirer credentials, parallel testing, and go-live — all in one workspace.

Why you need it

Without structure, onboarding depends on one person remembering everything

Documents get buried in email, credentials arrive late, and go-live feels improvised. The workspace makes every step visible and accountable.

Evidence

Every step carries its own evidence and sign-off

Uploads, submissions and admin review stay attached to the onboarding record rather than living in one person’s inbox.

Go-live confidence

Testing and readiness are evidenced — not assumed

The later stages cover parallel testing against your own figures, and a handover step recording your account manager and support window.

The Steps

From sign-up to live use in a structured workspace

01

Company profile

The workspace starts with company detail — registration, address, and the nominated onboarding contact. No chasing this information through email later.

02–03

Data setup and acquirer credentials

Merchant and partner data, then the acquirer credentials for the providers being used. The operating inputs Valtura needs are gathered through dedicated steps instead of scattered inbox requests.

04

Validation and parallel testing

The platform runs alongside existing reporting so each month’s figures can be compared. The workspace records clean months and where numbers disagree.

05

Handover

Accounts activate when the Direct Debit is set up, so the final step is handover: your account manager, support window, and how the first live cycle goes are recorded against the account.

Readiness

What gets signed off before live use

5
tracked steps
2
target clean months

Evidence attached to every step

Uploads, submissions and admin review stay attached to the onboarding record, so what was provided and when is visible rather than remembered.

2 clean months of parallel testing

The workspace records clean months achieved, discrepancy counts, tolerance levels, and whether the ISO has met the bar for sign-off.

Handover is recorded, not assumed

Account manager, support window and first-live-cycle status are recorded against the account rather than living in one person’s memory.

Terminal estate

The hardware side, handled on the same record.

Boarding a merchant usually means putting a terminal on their counter. The terminal estate module orders hardware through Service Logistics, tracks the stock you hold, and reports what every device is earning — against the same merchant record as the quote and the commission run.

Ordering through Service Logistics

Order terminals for a boarding merchant without leaving the platform — the request stays attached to the merchant and the MID it belongs to.

Inventory, tracked

Which devices you hold, which are deployed and where — instead of a spreadsheet that is right most of the time.

Terminal sales analytics

What the estate is earning, by device and by merchant — feeding the same residual reporting as the rest of the book.

Why It Matters

Structured onboarding creates value across the business

Repeatable delivery at scale

A consistent onboarding structure makes it possible to scale implementation quality across multiple ISOs without adding headcount.

No more hidden implementation delays

Step status, evidence, and sign-off are visible in the workspace — not buried in inboxes or private trackers that nobody else can see.

A clearer experience for the ISO being onboarded

The ISO has a defined workspace, a named onboarding lead, and a clear sense of what happens next at each step.

Go-live confidence backed by evidence

2 clean months of parallel testing, 8 readiness checks, and director sign-off make the move into live use planned and defensible.

See the onboarding workspace in the live portal

We can walk through the step sequence, review states, service sign-off, testing workflow, and go-live readiness exactly as it appears in the portal.