Operating ProcedureExecution layer

Remitz SPI Licence Applicant Sandbox Setup (Onboarding)

A sequence with 8 steps: Confirm the client's FCA authorisation status or SPI application reference before opening a Remitz account.

By InnovaAI ResearchPublished Updated

What are the steps?

sequence

Remitz SPI Licence Applicant Sandbox Setup (Onboarding)

  1. 01

    Confirm the client's FCA authorisation status or SPI application reference before opening a Remitz account.

    Remitz requires the reseller to hold an active FCA money transfer licence or be an SPI applicant. Capture the application reference in the client file so the sandbox configuration matches the corridors declared on the application.

  2. 02

    Subscribe to the SPI Licence Applicant plan at £79 per month and provision the hosted sandbox environment.

    There is no setup fee on this tier, and the sandbox converts to the production platform on upgrade, so no rebuild is needed when the licence is granted. Record the billing date against the client's onboarding schedule.

  3. 03

    Load the client's branding assets into the white-label portal configuration.

    Logo, colour tokens, and sender-facing copy are set here. The same branding carries through to the mobile app and agent dashboards on upgrade, so get it right at sandbox stage rather than reworking it later.

  4. 04

    Build the AML/KYC practice flows using the sandbox's compliance workflow templates.

    Mirror the exact identity checks the client will run in production, including the Onfido, Yoti, or Trulioo connector the client intends to use. These flows double as evidence for the SPI application pack.

  5. 05

    Configure corridor and FX logic for the corridors named in the licence application.

    Set per-corridor fees and FX margin rules in the back office. Keep the corridor list identical to the application to avoid a mismatch between what the regulator approved and what the platform can price.

  6. 06

    Connect payout provider APIs in test mode.

    Wire up TerraPay, Fincra, or Trust Payments credentials against the sandbox and run a small number of test transfers per corridor. Log the reference numbers as application evidence.

  7. 07

    Train the client team on the back-office dashboard and compliance reporting screens.

    Walk through transaction monitoring, agent management, and how to export compliance reports. Two sessions is usually enough for a small MSB team; leave them with a written runbook.

  8. 08

    Export the application evidence pack and schedule the upgrade path.

    Pull the sandbox activity log, KYC flow screenshots, and test transfer records into a single pack for the regulator submission. Agree in writing when the client moves to the Starter tier at £299 per month once authorisation lands.