Auto-save enabled
Onboarding Workflow v2.0
Logo

SPC Onboarding Portal

A complete list of all information and assets your team must provide before the project can begin. Please review each section carefully and prepare the required items in advance.

1. Company and Contact Information

This information is used to set up your white-label environment and ensure we are communicating with the right stakeholders throughout the project.

Short commercial name used across the project

Primary country of operation

Full registered legal entity name, as it appears in official documents

Primary point of contact for business decisions

Used for all formal project communication

May be the same as main contact or a dedicated technical person

A brief description of how your business operates and who your end users are

2. Project Scope — Phase 1 Confirmation

Please confirm which components are included in Phase 1. Only the platforms and features listed as included will be configured.

Scope confirmed here directly determines which subsequent items are required.

3. Branding Assets

Your brand assets are used to build all white-label components — the portal, mobile apps, and any communications.

3.1 Brand Identity

The commercial name displayed across all platforms

Main brand color

Complementary brand color

Used for highlights or buttons

PNG format, transparent background preferred, min 1024x1024 px

Used for app icons and favicons

3.2 Display Names

Applies if Portal in scope

Applies if Android in scope

Applies if iOS in scope

4. Legal Documents

Provide a public URL for each document, or upload the file — uploads are stored in Google Drive with a shareable view link that can be embedded in the app and portal.

Mandatory — blocking

Mandatory — blocking

Required only if in-app payments are in scope

5. Business & Functional Requirements

The following decisions affect how the platform is configured.

List all required languages

6. Registration and Account Model

The registration flow must be defined explicitly before development begins.

6.1 Registration Type

6.2 Mandatory User Fields

Indicate which fields should be visible and required during registration.

FieldEnd User Required?Reseller Required?
Email
Password
Phone Number
Date of Birth
First / Last Name
Address Fields

7. Google Cloud & reCAPTCHA

Each SPC must use its own dedicated Google Cloud project. Keys not in scope will not be requested.

7.1 Google Cloud Project

Unique project identifier

Descriptive name for the project

Required for backend reCAPTCHA verification

7.2 reCAPTCHA Keys — Web / Portal

7.3 reCAPTCHA Keys — Android

7.4 reCAPTCHA Keys — iOS

8. Transatel Requirements

Required to connect the platform to your eSIM catalog and provisioning services. Missing credentials will block the project.

8.1 Transatel Account and API

Customer-of-service reference

MVNO reference identifier

OAuth grant type

List all applicable rate plans that should be visible to end users

8.2 SFTP Credentials

9. Email Configuration

The platform sends transactional emails to end users. Please provide your SMTP settings.

The sender address that end users will see

10. Technical & Infrastructure Information

Required to configure the backend environment, reverse proxy, and SSL setup.

Must be DNS-configured before deployment

Backend API endpoint domain

Any infrastructure access, VPN, or server configurations required before the project can start

11. Supporting Documents (Optional)

Upload any additional files we should have on hand — brand guidelines, service account JSON keys, contracts, or rate plan sheets. Files are stored in Google Drive and linked inside your submission.

12. Validation and Delivery Dependencies

Please review carefully and flag anything that may be delayed or unavailable.

What Happens When a Blocker Is Raised?

  • Log the item as a formal blocker.
  • Notify you of the dependency in writing.
  • Place the affected deliverable on hold.
  • Resume work as soon as the item is received and validated.