Tracked steps replace the invisible inbox project
Company profile, merchant and partner data, acquirer credentials, parallel testing, and go-live — all in one workspace.
Tell us which workflows you want to fix first and we will shape the walkthrough around those modules. Thirty minutes, no obligation.
We will be in touch within one working day to arrange a time that suits you.
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.
Company profile, merchant and partner data, acquirer credentials, parallel testing, and go-live — all in one workspace.
Documents get buried in email, credentials arrive late, and go-live feels improvised. The workspace makes every step visible and accountable.
Uploads, submissions and admin review stay attached to the onboarding record rather than living in one person’s inbox.
The later stages cover parallel testing against your own figures, and a handover step recording your account manager and support window.
The workspace starts with company detail — registration, address, and the nominated onboarding contact. No chasing this information through email later.
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.
The platform runs alongside existing reporting so each month’s figures can be compared. The workspace records clean months and where numbers disagree.
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.
Uploads, submissions and admin review stay attached to the onboarding record, so what was provided and when is visible rather than remembered.
The workspace records clean months achieved, discrepancy counts, tolerance levels, and whether the ISO has met the bar for sign-off.
Account manager, support window and first-live-cycle status are recorded against the account rather than living in one person’s memory.
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.
Order terminals for a boarding merchant without leaving the platform — the request stays attached to the merchant and the MID it belongs to.
Which devices you hold, which are deployed and where — instead of a spreadsheet that is right most of the time.
What the estate is earning, by device and by merchant — feeding the same residual reporting as the rest of the book.
A consistent onboarding structure makes it possible to scale implementation quality across multiple ISOs without adding headcount.
Step status, evidence, and sign-off are visible in the workspace — not buried in inboxes or private trackers that nobody else can see.
The ISO has a defined workspace, a named onboarding lead, and a clear sense of what happens next at each step.
2 clean months of parallel testing, 8 readiness checks, and director sign-off make the move into live use planned and defensible.
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.