Failure PatternDecision layer

The Remitz Sandbox Trap: Why Agencies Fail With Remitz Before the FCA Licence Lands

Symptom: The client's Remitz sandbox is fully branded and demo-ready, but the FCA authorisation or SPI application is still pending, so no live corridor can be switched on. Root cause: Remitz is built for operators who already hold an active FCA money transfer licence or are SPI applicants, so the platform cannot substitute for the authorisation itself. Agencies that sell a launch date before the licence is confirmed are selling a capability the client does not yet legally have.

By InnovaAI ResearchPublished Updated

Invoicing Payments
How do you recognize it?
  • •The client's Remitz sandbox is fully branded and demo-ready, but the FCA authorisation or SPI application is still pending, so no live corridor can be switched on.
  • •Agencies bill the client for configuration work on the £79 SPI Licence Applicant plan and then discover the sandbox cannot process real payouts until the account is upgraded to a production tier.
  • •The client team has been trained on the back-office dashboard but has never run a live KYC check through Onfido, Yoti, or Trulioo, so the first real applicant file stalls in review.
  • •Corridor fee logic was configured for five corridors on the Starter plan, and the client now needs ten, forcing a mid-engagement jump to the £799 Growth tier that was never scoped or quoted.
  • •The agency's monthly managed service invoice goes out while the client is still in application-evidence preparation, and the client asks what they are paying for.
Why does it happen?
  • •Remitz is built for operators who already hold an active FCA money transfer licence or are SPI applicants, so the platform cannot substitute for the authorisation itself. Agencies that sell a launch date before the licence is confirmed are selling a capability the client does not yet legally have.
  • •The £79 SPI Licence Applicant plan is a hosted sandbox for compliance workflow practice and application evidence preparation, not a live remittance environment. Configuration work done there looks identical to production work, which hides the fact that no revenue-generating corridor exists yet.
  • •Plan limits are corridor-counted. Starter caps at five corridors and Growth removes that cap at £799 monthly, so an agency that scopes a fixed retainer around Starter pricing absorbs the upgrade cost or renegotiates mid-delivery.
  • •Provider integrations with TerraPay, Fincra, and Trust Payments require the operator's own provider relationships and API credentials. Agencies that assume Remitz supplies the payout rails discover the client must still contract and be approved by each provider separately.
How do you fix it?
  • •Before any configuration hours are logged, confirm the client's FCA authorisation status or SPI application reference and record it in the engagement file. If it is pending, scope the work explicitly as sandbox and evidence preparation on the £79 plan.
  • •Audit the client's corridor list against the current Remitz plan tier. If the count exceeds five, quote the £799 Growth tier in the proposal rather than absorbing the difference into the retainer.
  • •Run one end-to-end test transaction in the sandbox using the client's own KYC vendor credentials (Onfido, Yoti, or Trulioo) and one payout provider, so the team has handled a real applicant file before go-live.
  • •Separate the managed service invoice into platform licensing, configuration, and compliance advisory lines, so the client can see what is being delivered while the licence is still in application.
Open the Remitz courseRemitz decision recordBrowse the Academy

More on Remitz

More for Invoicing Payments